At 05:16 PM 6/28/2006 -0400, Jim Fulton wrote: >Interesting. I thought that --tag-svn-revision was a common/recommended >practice.
It *is* -- but not for releases being sent to PyPI. a dev-rNNNN release is a development snapshot rather than an official release. > I followed the advice to have a setup.cfg like: > >[egg_info] >tag_build = .dev >tag_svn_revision = 1 > >But I noticed that the release with the meta data didn't have the >subversion information or the .dev tag, which is consistent with >register not being aware of the extra information. > >Is this a bug? :) Probably. :) A workaround would be to either put "egg_info" before "register", or to move the "register" after the "bdist_egg". I'll add this to the bug list nonetheless. >If it isn't, then I recommend that you either stop recommending that >people use setup.cfg this way or stop recommending that they upload >their files to PyPI. Do you really need to upload every development snapshot to PyPI? Common practice for the dev-rNNNN stuff is that you either remove it from setup.cfg when you create a release branch, or temporarily remove it when issuing a release snapshot. Admittedly, this procedure is awkward, and in 0.7 there will be some kind of options you can give to egg_info like --no-revision and --release-build to indicate that the svn revision and build tag should be omitted. The use in this case would be something like "setup.py egg_info --release-build --no-revision register bdist_egg upload" -- which of course you could create a shortcut for (using "setup.py alias"), maybe something like "release". _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
