Django

Code

Ticket #8943 (new)

Opened 2 months ago

Last modified 2 months ago

Discuss starting to phase out support for Python 2.3

Reported by: simon Assigned to: nobody
Milestone: Component: Uncategorized
Version: 1.0 Keywords: djangocon
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Adrian and Jacob on stage at DjangoCon.

Jacob: "If there's some distro being used by millions of people maybe we won't do this just yet, but we need to start getting ready for Python 2.6 and the eventual migration to Python 3. Guido says we have 5 years".

Attachments

Change History

09/07/08 21:01:30 changed by kmtracey

  • needs_better_patch changed.
  • needs_tests changed.
  • needs_docs changed.

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.

Add/Change #8943 (Discuss starting to phase out support for Python 2.3)




Change Properties
Action