This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients BreamoreBoy, abbot, christian.heimes, eric.araujo, tarek, techtonik
Date 2010-09-20.23:31:32
SpamBayes Score 1.8785e-08
Marked as misclassified No
Message-id <>
distutils bugs follow standard Python rules: They are fixed in stable and development branches, now 2.7, 3.1 and py3k.  If there is a security hazard, the fix would go into 2.6 and possibly 2.5 too.

distutils2 has to work with 2.4-2.7 and (soon) 3.1-3.2, so Tarek told me to set all available versions for those bugs (2.5-py3k), even if I think “3rd party” is more appropriate and useful (since a distutils2 bug would not for example block a CPython 3.2 release).

When a bug applies to distutils and distutils2, I prefer to set only versions relevant for distutils.  distutils2 has only one branch which is tested with all supported Python version, and I actually consider distutils2 a version of distutils: It makes more sense to me to think “this bug exists in CPython 3.1, 3.2 and distutils2”.
Date User Action Args
2010-09-20 23:31:35eric.araujosetrecipients: + eric.araujo, techtonik, christian.heimes, tarek, abbot, BreamoreBoy
2010-09-20 23:31:35eric.araujosetmessageid: <>
2010-09-20 23:31:33eric.araujolinkissue2200 messages
2010-09-20 23:31:32eric.araujocreate