Phillip J. Eby wrote:
Kevin Dangoor wrote:
On 10/29/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
FYI, it looks like the Mac eggs for PyProtocols and RuleDispatch were
created without their 'dev-rXXX' tags, which means you're going to have
version skew there. You need to be careful about that sort of thing
when you're building eggs for unreleased versions of a package.
I fixed the Mac eggs... but, won't anyone on Linux run into this
problem? If they easy_install and it picks up the source zip, will the
version number come from the zip name or will it come from the setup
file?
From the setup file. It'd probably be a "best practice" for code
that's "in development" in Subversion to have a setup.cfg that sets the
right egg_info flags. Then, I suppose when you branch for a release
you can take those options out of the release branch. That way, if you
develop on the trunk, then a trunk checkout will always be properly
tagged with the version.
Incidentally, "paster create --template=basic_package" creates just such
a setup.cfg, and buildutils' "python setup.py svntag" removes those
settings for the tag.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
