Modify ↓
Opened 14 years ago
Closed 14 years ago
#9660 closed enhancement (wontfix)
Scrap Support for Python 2.5/2.6 and go for 2.7 directly
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.13dev |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
see summary.
Since Python 2.7 will be last release for the Python 2 product line, we should directly move on towards 2.7.
2.7 should be backwards compatible to 2.6 and 2.5, so why not simply just skip the older releases?
The most recent distributions of Linux do support Python 2.7 out of the box, except for perhaps Ubuntu, but that should not hinder us, instead we must drive Canonical to include Python 2.7 into their product ASAP.
The main reason is that I would definitely like to use the extended property support included in the Python 2.7 parser, e.g.
@property def x():
pass
@x.setter def x(..):
pass
etc.
RFC here
Attachments (0)
Note:
See TracTickets
for help on using tickets.
This is not going to happen, sorry. Believe it or not, some distributions are still stuck with Python 2.4, and we have had some resistance against dropping support for 2.4 in 0.13dev. So Trac core will support 2.5 in 0.13, and probably 2.6 in 0.14.
You are free to require Python 2.6 or 2.7 for you plugins, though. The only consequence is that you will reduce your potential user base, which might or might not be acceptable for you.