Can you use underscores instead of hyphen's in your releases?
davedash opened this issue · 5 comments
In this pip issue we see that hyphens are converted to underscores in the wheel building process, but during lookup 1.0.5-beta does not equal 1.0.5_beta. pip is going to be retooled, but it sounds like (you can read the rest of the issue for more context) that - in version strings are just problematic and possibly not in spec.
sure - thanks for the tip - we can do that the next time we push a new release (should be happening soon).
question (we are pip n00bs) - I changed the version name in setup.py to 1.0.7_beta. but on pip - i see it's still showed up as 1.0.7-beta. this is the version of setuptools on my machine:
setuptools-0.6c11-py2.6
any ideas on what i am doing wrong?
Odd that happens with me as well using a newer setuptools. But my guess is that this is will still be an improvement, since matching 1.0.7_beta I think will look at filenames with 1.0.7-beta. Maybe @carljm can shed some light though.
The interaction of hyphen and underscore in Python packaging is a bit complex; probably best to just read the linked pip issue in full if you want the full picture. The short version is: yes, the underscore should work in practice, but really the best solution is to not use either hyphens or underscores in Python package versions. Instead use a version number that complies with the new PEP 440 standard: http://www.python.org/dev/peps/pep-0440/#version-scheme
The PEP 440 compliant version string here would be 1.0.7b1.
This is fixed in the latest version 1.0.11b1.
Thanks!