The way my project is set up right now, we have a setup.cfg that specifies .dev for tag_build. This way, we can have the file tagged properly when developing from source. We also have a Hudson CI server that will run the tests and then generate an sdist with the build number added (using the command "python setup.py egg_info -b dev-$BUILD_NUMBER sdist").
Now, suppose I use the following setup.cfg in my project: [egg_info] tag_build=.dev If I run the following commands, everything works as expected: $ python setup.py egg_info -b .dev-123 $ tar -xzvf dist/jiva_interface-3.0.1.dev-123.tar.gz $ cat jiva_interface-3.0.1.dev-123/setup.cfg [egg_info] tag_build = .dev-123 tag_date = 0 tag_svn_revision = 0 This is the appropriate behavior: I want the tag_build option to be overridden in the resulting setup.cfg file. However, I made a mistake and used tag-build instead of tag_build: [egg_info] tag-build=.dev If I run the same commands as above, the sdist is named the same, the egg_info version is the same, but the setup.cfg is different: $ python setup.py egg_info -b .dev-123 $ tar -xzvf dist/jiva_interface-3.0.1.dev-123.tar.gz $ cat jiva_interface-3.0.1.dev-123/setup.cfg [egg_info] tag_build = .dev-123 tag_date = 0 tag_svn_revision = 0 tag-build = .dev As you can see, it's creating both a tag-build and tag_build option. And it's going by the tag-build option, which isn't what I want. Is this a bug, or is there some kind of subtlety to this option that I don't know about?
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
