redisco icon indicating copy to clipboard operation
redisco copied to clipboard

Update PyPi Package

Open prologic opened this issue 8 years ago • 9 comments

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

prologic avatar Jun 06 '16 06:06 prologic

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

kiddouk avatar Jun 06 '16 11:06 kiddouk

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 :)

prologic avatar Jun 06 '16 15:06 prologic

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/[email protected]#egg=redisco

Should help the transition.

kiddouk avatar Jun 06 '16 18:06 kiddouk

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.

kiddouk avatar Jun 06 '16 18:06 kiddouk

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

James Mills / prologic

E: [email protected] W: prologic.shortcircuit.net.au

On Mon, Jun 6, 2016 at 11:41 AM, sebastien requiem <[email protected]

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 .

prologic avatar Jun 06 '16 19:06 prologic

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.

kiddouk avatar Jun 07 '16 05:06 kiddouk

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: [email protected] W: prologic.shortcircuit.net.au

On Mon, Jun 6, 2016 at 10:39 PM, sebastien requiem <[email protected]

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 avatar Jun 07 '16 05:06 prologic

ping

prologic avatar Jul 05 '16 07:07 prologic

👍 for redisco2

linuxlewis avatar Oct 04 '16 17:10 linuxlewis