search

bastibe / lunatic-python

A two-way bridge between Python and Lua
http://labix.org/lunatic-python
GNU Lesser General Public License v2.1
296 stars 82 forks source link

Request for a publish to pypi #15

Open gkgupta opened 11 years ago

gkgupta commented 11 years ago

Hi,

We are working on an implementation of mockredis which requires mocking the behaviour of Lua scripts (as executed by Redis)

We would like to use your project for the same as its a really cool bridge between Python and Lua. But we are not able to use it because the original project is shadowing it on pypi.

We are considering to fork and publish it under a different name/version. But wanted to check with you first if you had any plans to do the same.

Gaurav Location Labs

bastibe commented 11 years ago

Hi,

Personally, I do not have any plans to publish lunatic-python under a different name on pypi. However, our little fork here has evolved quite a bit and it would certainly be helpful to a few people to make this work available to a greater audience.

I would love to see this project be published and I would love for it to be developed further in a somewhat central place like this repo. Thus, if you want to, I would gladly give you contributer rights and have you publish this project on PyPi.

However, I do not feel like I am the owner of this code, hence I do not wish to make an authoritative decision here. Hopefully the other contributers will chime in shortly.

Cheers, Basti

gkgupta commented 11 years ago

Hi Bastian,

I really appreciate your support on this, and it would be a privilege if I could contribute to this project. So, I would gladly like to take forward publishing it on PyPi.

Since lunatic-python is already taken on PyPi, do you have any thoughts on what name you would like. Few candidates could be

thanks, Gaurav

greatwolf commented 11 years ago

I think it would be best if the same name can be kept as much as possible to avoid possible confusion. What if you try to contact the original author, Gustavo Niemeyer, and see if he's interested in having the original lunatic-python superseded by a more recent fork like this for example.

Failing that, (eg. you don't get a response or https://pypi.python.org/pypi/lunatic-python is abandoned), you can try contacting the maintainer of pypi to see if he can relinquish privileges for that package to us.

I would only consider a different name after all those avenues have been tried are exhausted.

bastibe commented 11 years ago

I have to agree with Greatwolf. Fragmentation should be avoided if at all possible.

gkgupta commented 11 years ago

I also think that would be preferable. I had put in my request here instead of just creating a fork to avoid a fragmentation. If we could connect this project back to previous Lunatic-Python work in PyPi that would be great.

So as per your suggestion, I have sent an email to @niemeyer. Lets hope he responds to it.

gkgupta commented 11 years ago

I haven't had any response to my email to Gustavo Niemeyer. And going to the maintainer of Pypi will take long, which I would have done if I had more time, and I have a deadline approaching for making the release of mockredis. Soon I will have no other choice than to fork and publish on Pypi myself. So I will appreciate that you guys let me know if you want me to proceed in a different direction.

bastibe commented 11 years ago

If he actually does not respond, I would recommend to use as descriptive a name as possible.

Say, something like lunatic-python-bugfix. I am hesitant to call it anything like lunatic-python-2 or lunatic-python-extended or lunatic-py, since that might confuse people -- what we have here is not much of an extension or new version or alternative. It is mostly bugfixes for the existing code and that should be made as clear as possible.

niemeyer commented 11 years ago

I'm in a sprint and slow, but I'll get back to you soon.

greatwolf commented 11 years ago

hey we got a response from the author himself. woot! :) :+1:

gkgupta commented 11 years ago

Awesome to hear from you man. Guys, I hate being the one to spoil the mood. As much as I want to avoid forking, we're trying not to block our internal development. Based on our scheduling, it looks like we'll have to fork as a workaround after Tuesday, 14th May. So I will appreciate, if a consensus could be reached before that.

bastibe commented 11 years ago

Well, if he does not respond until Tuesday, take this repo and publish it as lunatic-python-bugfix. I think that is the least offensive path to take.

gkgupta commented 11 years ago

I have forked this repo (as I need to update the package name/version & tag the release) and published it as lunatic-python-bugfix on pypi

hughperkins commented 8 years ago

How about publishing it as eg lunatic-python-bastibe? (And anyone else who wants to publish their particular fork can use the same convention).

bastibe commented 8 years ago

This version is not published on pypi. Whoever owns the version on pypi, it is not me.

beamerblvd commented 6 years ago

Throwing my hat in the ring to request this make its way into PyPi. With --process-dependency-links support deprecated and slated for removal with no replacement, and our project's being an OSS project that must work with setup.py, we have no way of using this library. :-(