Code

Opened 6 years ago

Closed 5 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: UI/UX:

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 (0)

Change History (2)

comment:1 Changed 6 years ago by kmtracey

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

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.

comment:2 Changed 5 years ago by jacob

  • Resolution set to fixed
  • Status changed from new to closed

We've discussed this on django-dev; 1.1 will be the last version to support 2.3.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.