Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#12773 closed (fixed)

Update FAQ to indicate supported Python versions

Reported by: russellm Owned by: kmtracey
Component: Documentation Version: 1.1
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Current FAQ indicates that Django supports 2.3-2.6. With Django 1.2, we will be dropping support for 2.3, and it's possible that 2.7 might be out.

Change History (11)

comment:1 Changed 5 years ago by russellm

  • Component changed from Uncategorized to Documentation
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

Just making a ticket so that we don't forget to update this bit of documentation.

comment:2 Changed 5 years ago by djansoft

  • Owner changed from nobody to djansoft

comment:3 Changed 5 years ago by djansoft

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

The FAQ is correctly showing what versions of Python are supported. See file install.txt in trunk.

comment:4 Changed 5 years ago by Alex

  • Resolution invalid deleted
  • Status changed from closed to reopened

Please don't close tickets filed by core developers

comment:5 Changed 5 years ago by kmtracey

Note djansoft is right: the dos have already been updated to remove any claim of supporting Python 2.3 (see r11640). The question of what, if anything, to say about Python 2.7 is still up in the air since 2.7 is not yet out. I did run the test suite with the 2.7 beta and it ran fine (excepting a few minor test problems which have been fixed). We could probably update the docs now and claim 2.7 support, even though it is a bit early. There don't appear to be any major issues with running under 2.7.

comment:6 Changed 5 years ago by Alex

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

Bah, my apologies.

comment:7 Changed 5 years ago by kmtracey

  • Resolution fixed deleted
  • Status changed from closed to reopened

Note I intentionally left it open as a to-do for the 2.7 question. Not as critical as the removing the claim to supporting 2.3, but we should probably do something to mention 2.7 before 1.2 goes out.

comment:8 Changed 5 years ago by kmtracey

  • milestone 1.2 deleted
  • Owner changed from djansoft to kmtracey
  • Status changed from reopened to new

Python 2.7 is targeted for June, so it's unlikely (I hope) we need to say anything in the FAQ before 1.2 goes out. We can update the FAQ when Python 2.7 is released.

comment:9 Changed 5 years ago by russellm

  • milestone set to 1.2

comment:10 Changed 5 years ago by russellm

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

Looks like we're going to release before Python 2.7, so we can close this.

comment:11 Changed 4 years ago by jacob

  • milestone 1.2 deleted

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top