Éric Araujo <mer...@netwok.org> added the comment: 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”. ---------- components: +Distutils2 versions: -Python 2.5, Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue2200> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
