> I encountered an issue that I think will require a post2 release to be > generated. The tar.gz and zip packages built on Linux have "1.0.6post1" in > the filename. The win32 and win-amd64 packages built on Windows have > "1.0.6.post1" and "1.0.6.post1" in the filename (note the extra "."). This > resulted in separate pages being created when the files were uploaded to > PyPI using Twine: > https://pypi.python.org/pypi?:action=display&name=Trac&version=1.0.6.post1 > https://pypi.python.org/pypi?:action=display&name=Trac&version=1.0.6post1 > > I was using setuptools 2.2 on Linux, but setuptools 15.0 on Windows. I > upgraded the virtualenv on Linux to setuptools 16.0 and now the tar.gz and > zip packages have "1.0.6.post1" in the filename.
In PEP 440, version strings are normalized, e.g. 1.0.6post1 -> 1.0.6.post1 https://www.python.org/dev/peps/pep-0440/#normalization PEP 440 is implemented and versions are normalized since setuptools 8.0. https://pythonhosted.org/setuptools/history.html#id52 >>> import setuptools >>> setuptools.__version__ '8.0' >>> from pkg_resources import parse_version >>> parse_version('1.0.6post1') <Version('1.0.6.post1')> >>> parse_version('1.0.6.post1') <Version('1.0.6.post1')> > I considered just renaming the files on Linux, but it seems like there is > too high of risk of unexpected issues with that, and it would be safer to > just regenerate a "post2" release. Yeah, I agree to `.post2` release. -- Jun Omae <[email protected]> (大前 潤) -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
