Ned Deily added the comment: You could make similar arguments about 2.5 or earlier releases (or 3.0), all of which have already been removed. More importantly, python-dev uses the version field to indicate "the known versions of Python that the issue affects and should be fixed for" (http://docs.python.org/devguide/triaging.html#versions), not all versions (supported or otherwise) that might be affected by the issue. Since at least the time 2.6 entered security-fix mode, we have routinely deselected 2.6 from those issues where is was set, so, even if we didn't remove 2.6 from the version list, you could not depend on searching the version field for 2.6.
_______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue532> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss
