On Tuesday, May 19, 2015 at 5:08:47 PM UTC-7, RjOllos wrote: > > > > On Tuesday, May 19, 2015 at 10:03:32 AM UTC-7, Jun Omae wrote: >> >> On Tue, May 19, 2015 at 9:41 PM, RjOllos <rjo...@gmail.com> wrote: >> > I made an error uploading a package to PyPI yesterday and discovered >> that >> > there has been a change that prevents re-uploading a file with the same >> > name, even after deleting that file from PyPI. >> > >> > >> https://mail.python.org/pipermail/distutils-sig/2015-January/025683.html >> > >> > My plan is to use the version 1.0.6.1 in the filename, e.g. >> > Trac-1.0.6.1.tar.gz, but not change the package metadata. Please let me >> know >> > if you have any suggestions. >> >> I consider versions in the filename and the metadata should be same. >> Otherwise, "pip freeze" would generate Trac==1.0.6 in the output >> however "pip install Trac==1.0.6" would fail, e.g. "pip install -r" >> with the output. >> >> I think we could use post-releases, .post{N} suffix. However we should >> use the same version in both the filename and the metadata even with >> the use of .post{N} suffix. >> >> https://www.python.org/dev/peps/pep-0440/#post-releases >> >> >> distribute 0.6.24 >> >>> import setuptools >> >>> from pkg_resources import parse_version >> >>> setuptools.__version__ >> '0.6' >> >>> parse_version('1.0.6') < parse_version('1.0.6.post1') >> True >> >>> parse_version('1.0.6.post1') < parse_version('1.0.6.1') >> True >> >>> parse_version('1.0.6.1') < parse_version('1.0.7') >> True >> >> setuptools 16.0 >> >>> import setuptools >> >>> from pkg_resources import parse_version >> >>> setuptools.__version__ >> '16.0' >> >>> parse_version('1.0.6') < parse_version('1.0.6.post1') >> True >> >>> parse_version('1.0.6.post1') < parse_version('1.0.6.1') >> True >> >>> parse_version('1.0.6.1') < parse_version('1.0.7') >> True >> > > Thanks, that sounds good. Setting "tag_build = post1" in setup.cfg I get a > filename "Trac-1.1.6.post1.zip". > > I've captured this contingency in the documentation, along with some other > details about our versioning scheme: > > http://trac.edgewall.org/wiki/TracDev/ReleaseChecklist#Versionidentification > > - Ryan >
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. 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. - Ryan -- 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 trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
