bdist_egg ignores tag_svn_revision
I've noticed that if I run a setup.py install, the svn revision shows up there. If I run setup.py bdist_egg, the filename generated does not have the revision. Is that on purpose? Kevin
At 11:23 AM 9/15/2005 -0400, Kevin Dangoor wrote:
I've noticed that if I run a setup.py install, the svn revision shows up there. If I run setup.py bdist_egg, the filename generated does not have the revision.
Is that on purpose?
No; bdist_egg should do exactly the same thing as the others, as they all use the 'egg_info' command to determine the tagging. I presume you have something like: [egg_info] tag_svn_revision = 1 in an appropriate config file?
On 9/15/05, Phillip J. Eby <pje@telecommunity.com> wrote:
No; bdist_egg should do exactly the same thing as the others, as they all use the 'egg_info' command to determine the tagging. I presume you have something like:
[egg_info] tag_svn_revision = 1
in an appropriate config file?
Yep, but I just figured out what happened. I ran sdist on the original svn checkout to get a snapshot that I could hang on to. I then ran a bdist_egg *on that snapshot*, which would logically not appear to be an svn checkout. I was thrown off by the fact that tag_build still worked... It might be nice if an sdist that is tagged with a revision number creates eggs with that number, but that'd be a pretty low priority I would think. The only reason I even took an sdist snapshot is that I'm always paranoid about things disappearing off the net for one reason or another and like to have a local copy of parts that I'm actively using. Kevin
participants (2)
-
Kevin Dangoor -
Phillip J. Eby