[issue11819] '-m unittest' should not pretend it works on Python 2.5/2.6

Éric Araujo added the comment: > I need a "why-python-suxx" keyword to point people with dumb > questions about why they should not use specific Python versions to a > query that lists all sensitive issues for this specific version that > won't be fixed due to security fix only mode. You may no

[issue11819] '-m unittest' should not pretend it works on Python 2.5/2.6

anatoly techtonik added the comment: I know. But stuff like this is necessary for proper release management and future planning. Using "why-python-suxx per module" ™ metric, it is possible to pinpoint badly designed parts that should be removed or replaced in Python4. --

[issue11819] '-m unittest' should not pretend it works on Python 2.5/2.6

Ezio Melotti added the comment: At some point we have to draw the line, otherwise we would have to backport things to 2.3 and 2.4 too. We are already maintaining 4 branches (2.7, 3.1, 3.2, 3.3). -- ___ Python tracker

[issue11819] '-m unittest' should not pretend it works on Python 2.5/2.6

anatoly techtonik added the comment: I need a "why-python-suxx" keyword to point people with dumb questions about why they should not use specific Python versions to a query that lists all sensitive issues for this specific version that won't be fixed due to security fix only mode. -

[issue11819] '-m unittest' should not pretend it works on Python 2.5/2.6

Michael Foord added the comment: 2.5 / 2.6 are in security fix only mode. So this won't get fixed. Please don't reopen. -- stage: -> committed/rejected status: open -> closed ___ Python tracker _

[issue11819] '-m unittest' should not pretend it works on Python 2.5/2.6

anatoly techtonik added the comment: #6514 is to make `-m unittest` work run on 2.5/2.6. This bug is not to fix it, but to stop displaying confusing messages. It will be enough to exit with a message like: "`-m unittest` call is not supported in Python 2.5/2.6 - use something else (nose?)