TheFriendlyCoder

Also just to clarify / demonstrate some of the problems inherent with renaming the package file in the way I just described, consider this simple use case: pip3 install docutils This will install v0.15.1 of docutils in my virtual environment: > pip3 freeze docutils==0.15.1 But exporting the frozen versions to a requirements file will produce an invalid file that can not be used to re-deploy the pegged revisions of the dependencies. This believe this is a result of the renamed package file. To show...

Also just to clarify / demonstrate some of the problems inherent with renaming the package file in the way I just described, consider this simple use case: pip3 install docutils This will install v0.15.1 of docutils in my virtual environment: pip3 freeze docutils==0.15.1 But exporting the frozen versions to a requirements file will produce an invalid file that can not be used to re-deploy the pegged revisions of the dependencies. This believe this is a result of the renamed package file. To show...

Also just a quick rant: the fact that this defect adversely affects MANY python packages in the community in a significantly detrimental way, I would have hoped the fix would have been implemented within minutes or hours, not days. I sincerely hope a fix can be released to pypi sooner rather than later to help mitigate these problems.

Also worth noting, I did see that there was a v0.15.1 version of the Python 3 package deployed to pypi but it was named "0.15.1-post1" which causes even more confusion. From what I can tell the version number in the package manifest is set to 0.15.1 but there is some sort of manual step being done when the package is deployed to rename the file such that the version identifier that is embedded in the file name has a "-post1" suffix in it. The details of this appear to be documented here: https://sourceforge.net/p/docutils/code/8303/...

NOTE: This bug affects multiple packages in various ways so I would encourage you to publish a fix for this sooner rather than later. For example, we have a Python 3 build that does not use docutils directly (ie: it is included as a transitive dependency). When we pip install our project it reaches out to pypi to pull in the latest copies of all dependencies. In the process it attempts to install v0.15.1 because that is the latest version of this package, however because of the aforementioned problems...

I too ran into a similar problem running the latest version on my Ubuntu 13.04 OS....

I'm curious if you've ever received a reply on this issue or not? I just spent a...

I'm curious if you've ever received a reply on this issue or not? I just spent a...