Opened 16 years ago
Closed 16 years ago
#8943 closed (fixed)
Discuss starting to phase out support for Python 2.3
Reported by: | simon | Owned by: | nobody |
---|---|---|---|
Component: | Uncategorized | Version: | 1.0 |
Severity: | Keywords: | djangocon | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
Change History (2)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
We've discussed this on django-dev; 1.1 will be the last version to support 2.3.
Note:
See TracTickets
for help on using tickets.
Russell gave a list of reasons for why 2.3 is still necessary when I asked about it here:
http://code.djangoproject.com/ticket/7786#comment:6
We do have people quite recently reporting they are running Django on 2.3: #8910, #8606, #8577, #8226, #7734, #7608, #7418, #7365, #7354, etc. (Those are not all problems identified with Django on 2.3, they just indicate the users -- who I think are all different, I tried to skip ones from the same people, and ones opened just to get the test suite running on 2.3 -- are running Python 2.3.)
Not trying to throw a damper on the idea (I was hoping 2.3 could be dropped when I asked the question in #7786), just provide some data.