Tarek Ziadé wrote: > 2009/12/23 "Martin v. Löwis" <[email protected]>: >>>> BTW: how is "==" specified? Is "2.5.4" == "2.5"? >>>> If not, would >>>> "2.5, 2.6" really mean "either Python 2.5 or Python 2.6, but neither >>>> 2.5.1 nor 2.6.1"? >>> Yes, 2.5 concerns all 2.5.x versions, but a micro version could be given as >>> well >>> I am changing this >> Are you sure this is a good idea? > > The use case I see is : an important ssl security version is released > in 2.6.5 and a project > that uses ssl updates its metadata and releases a new version that > makes sure Python 2.5 users have that security patch > > Requires-Python: >=2.6.5
Why is that a use case for "2.5 concerns all 2.5.x versions"? In this example, the version string "2.5" isn't used at all. > Then encourages its users to update their versions. Specifying micro versions is fine with me. I'm worried about the "2.5 concerns all 2.5.x versions" part. >> Does that apply to all PEP 386 version numbers? > > Not sure what you mean here, If I specify Requires-Dist: zope.interface (3.6) and I have zope.interface 3.6.1b4, is the requirement satisfied? What if I have 3.6b4: is it then satisfied? Regards, Martin _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
