Opened at 2009-08-06T23:22:33Z
Closed at 2009-08-21T23:34:00Z
#26 closed defect (wontfix)
pypi doesn't know about current 0.5.16 release
| Reported by: | warner | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Version: | 0.5.1 | Keywords: | |
| Cc: | Launchpad Bug: |
Description
the python package index still thinks that 0.5.15 is the current release.. it needs to be updated.
Change History (1)
comment:1 Changed at 2009-08-21T23:34:00Z by zooko
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
v0.5.15 is fine. The additional changes in v0.5.16 are just to the build system:
[660], [661], [662], [663], [664], [665]
There are a bunch of binary eggs of pycryptopp v0.5.15 for various platforms on pypi: http://pypi.python.org/pypi/pycryptopp/0.5.15 . If I uploaded a v0.5.16 source distribution, then that would take precedence over the v0.5.15 binary eggs in the setuptools dependency logic ( http://bugs.python.org/setuptools/issue83 (I wish setuptools would prefer v1.4.1 in binary egg format over v1.4.5 in sdist format when I'm requiring >= v1.1.0)).
So I'd rather leave v0.5.15 as the most recent release on PyPI.