Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#25886 closed Bug (worksforme)

Release notes confusion and Django 1.8.8/Python 3.2-3.3 import error

Reported by: Ivan Ven Osdel Owned by: nobody
Component: Uncategorized Version: 1.8
Severity: Normal Keywords: python3.2 python3.3 find_spec
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I am seeing this in the Django 1.9 release notes:

Since Django 1.8, we’ve dropped support for Python 3.2 and 3.3.

However on the Django 1.8 release notes page it's listed as supported.

My own testing shows that Python 3.3 works for 1.8.0 - 1.8.7 but not 1.8.8. On that version it fails in the same way 1.9 would.

My guess is that the 3.2/3.3-unfriendly code was accidentally introduced in 1.8.8 and the 1.9 release notes author (reasonably) checked the 1.8.8 code rather than the wiki when formulating that statement above.

Change History (10)

comment:1 by Tim Graham, 9 years ago

Resolution: worksforme
Status: newclosed

We have continuous integration for Django 1.8 and it's passing on Python 3.2 and 3.3. Also, Django 1.8.8 isn't released so how are you testing?

comment:2 by Ivan Ven Osdel, 9 years ago

Yes, my mistake on the testing (but please read to end). I had a problem with my tox syntax that brought in Django 1.9 by mistake. So I can confirm that there is no code issue.

However, the statements in the docs still seem in conflict to me. "Since Django 1.8, we’ve dropped support for Python 3.2 and 3.3." Maybe it's a locale specific thing but I read that statement as both 1.8 and 1.9 dropped 3.2 and 3.3 support. My wife says I am not crazy. :)

comment:3 by Tim Graham, 9 years ago

It basically means "changes since Django 1.8 are...". We used similar phrasing in the 1.7 release notes. If you want write something that included 1.8 and 1.9, I'd say "As of Django 1.8 ...." If we get more complaints, I'm open to rewording it though.

comment:4 by Claude Paroz, 9 years ago

I admit that the current formulation is also ambiguous for me (as non-native speaker). If we can find something clearer, it would be nice.

comment:5 by Tim Graham, 9 years ago

Proposal: "The Django 1.8 series is the last to support Python 3.2 and 3.3."

comment:6 by Claude Paroz, 9 years ago

+1 from a poor English speaker

comment:7 by Tim Graham <timograham@…>, 9 years ago

In 26c26e83:

Refs #25886 -- Improved language in Python compatibility section of the release notes.

comment:8 by Tim Graham <timograham@…>, 9 years ago

In 975a451:

[1.8.x] Refs #25886 -- Improved language in Python compatibility section of the release notes.

Backport of 26c26e83081d68035d6411b1acc17ba033e1876d from master

comment:9 by Tim Graham <timograham@…>, 9 years ago

In e4354d8:

[1.9.x] Refs #25886 -- Improved language in Python compatibility section of the release notes.

Backport of 26c26e83081d68035d6411b1acc17ba033e1876d from master

comment:10 by Ivan Ven Osdel, 9 years ago

I am a bit late but, yes, the new version is great.

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