I have four packages on PyPI: antipathy, dbf, pandaemonium, and scription. `pip install --upgrade` works for three of them, but for scription it continually grabs an older release (0.53, I think). Any ideas what might be wrong? -- ~Ethan~
On Wed, Nov 05, 2014 at 10:24:00AM -0800, Ethan Furman wrote:
I have four packages on PyPI: antipathy, dbf, pandaemonium, and scription.
`pip install --upgrade` works for three of them, but for scription it continually grabs an older release (0.53, I think).
I cannot reproduce pip install scription fetches 0.70.4 for me. Marius Gedminas -- Never attribute to malloc that which can be adequately explained by stupidity. -- From the .sig of joerg@raleigh.ibm.com (Joerg Pommnitz)
On Wed, Nov 5, 2014 at 9:24 PM, Ethan Furman
I have four packages on PyPI: antipathy, dbf, pandaemonium, and scription.
`pip install --upgrade` works for three of them, but for scription it continually grabs an older release (0.53, I think).
Any ideas what might be wrong?
- CDN - proxy - not PyPI as package repository - --pre version - pip bug -- anatoly t.
On Wed, Nov 5, 2014 at 7:24 PM, Ethan Furman
I have four packages on PyPI: antipathy, dbf, pandaemonium, and scription.
`pip install --upgrade` works for three of them, but for scription it continually grabs an older release (0.53, I think).
Any ideas what might be wrong?
Maybe this would help – http://stackoverflow.com/questions/14617136/why-is-pip-installing-an-old-ver... Regards, Piotr Dobrogost
participants (4)
-
anatoly techtonik -
Ethan Furman -
Marius Gedminas -
Piotr Dobrogost