kiddouk / redisco

A Python Library for Simple Models and Containers Persisted in Redis
MIT License
439 stars 78 forks source link

Update PyPi Package #61

Open prologic opened 8 years ago

prologic commented 8 years ago

Can we get an updated version of Redisco up on PyPi?

kiddouk commented 8 years ago

This should happen now since we have unit tests back on track.

prologic commented 8 years ago

That would be great because I use Redisco in a few projects and have concerns over its longevity such that I have an issue that says "migrate away from Redisco" :) I'd rather note though :)

kiddouk commented 8 years ago

Beware that it will have a new name as the the creator of the project lost his pypi account a looooong time ago.

In the mean time, I encourage you to migrate to v0.2 which fixes a BIG memory leak. You can simply add the following line in your requirements.txt

-e git://github.com/kiddouk/redisco.git@0.2#egg=redisco

Should help the transition.

kiddouk commented 8 years ago

Although, remember that 0.2 is not compatible with v0.1.4 that you may be using at the moment. I should maybe write a small migration tool for this.

prologic commented 8 years ago

Can we please rename the project if we're going to republish a new name to PyPi?

James Mills / prologic

E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

On Mon, Jun 6, 2016 at 11:41 AM, sebastien requiem <notifications@github.com

wrote:

Although, remember that 0.2 is not compatible with v0.1.4 that you may be using at the moment. I should maybe write a small migration tool for this.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kiddouk/redisco/issues/61#issuecomment-224049365, or mute the thread https://github.com/notifications/unsubscribe/ABOv-tf0bmX3fvOc82HmMjJOH3TOowkKks5qJGnTgaJpZM4IulkX .

kiddouk commented 8 years ago

I am afraid not. Since this is the same project all in all (we really share a lot of common code). But since pypi wont allow us to publish any project with the same name, better call it something like "redisco2" or something like that so people dont get confused when searching for it.

prologic commented 8 years ago

I think redisco2 is an 'okay" compromise; otherwise couldn't we contact the PyPi admins to get "redisco" deleted so a new version can be republished? (Seeing a the original author has forgotten/lost his/her password!)

James Mills / prologic

E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

On Mon, Jun 6, 2016 at 10:39 PM, sebastien requiem <notifications@github.com

wrote:

I am afraid not. Since this is the same project all in all (we really share a lot of common code). But since pypi wont allow us to publish any project with the same name, better call it something like "redisco2" or something like that so people dont get confused when searching for it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kiddouk/redisco/issues/61#issuecomment-224183281, or mute the thread https://github.com/notifications/unsubscribe/ABOv-vnQN7MDEoiH8UR6T1rnGdmxraZZks5qJQQXgaJpZM4IulkX .

prologic commented 8 years ago

ping

linuxlewis commented 8 years ago

👍 for redisco2