[Django] #28483: Possible typo on the docs.djangoproject.com website
Django
-----------------------------------------+------------------------
Reporter: Vasili Korol | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version:
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
On the page with Django 2.0 release notes
(https://docs.djangoproject.com/en/dev/releases/2.0/#python-
compatibility), in the section "Python compatibility" at the top of the
page, it is written:
Django 2.0 supports Python 3.5+. Since Django **1.11**, support for
Python 2.7 and 3.4 is removed.
On the other hand, in the release notes for Django 1.11
(https://docs.djangoproject.com/en/1.11/releases/1.11/#python-
compatibility) it is stated:
Django 1.11 requires Python 2.7, 3.4, 3.5, or 3.6. Django 1.11 is the
first release to support Python 3.6. We highly recommend and only
officially support the latest release of each series. The Django 1.11.x
series is the last to support Python 2. The next major release, Django
2.0, will only support Python 3.5+.
Therefore, i believe, there is a typo in the Django 2.0 release notes, and
it should read as ''"Since Django** 2.0**, support for Python 2.7 and 3.4
is removed"''. Is this correct?
--
Ticket URL: <https://code.djangoproject.com/ticket/28483>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------+--------------------------------------
Reporter: Vasili Korol | Owner: nobody
Component: Documentation | Version:
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
* type: Uncategorized => Bug
Comment:
It's correct as is. "Since Django 1.11" means "compared to Django 1.11."
--
Ticket URL: <https://code.djangoproject.com/ticket/28483#comment:1>
Django
-------------------------------+--------------------------------------
Component: Documentation | Version:
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Keryn Knight):
* cc: Keryn Knight (added)
Comment:
Not to bikeshed on it overly, but "correct as is" is subjective, because
the phrasing is ambiguous (as may be apparent given the ticket being
filed).
"Since Django 1.11, support for Python 2.7 and 3.4 is removed." can be
read in 2 ways:
- Subsequent to 1.11 being released, support for ... has been removed"
[Tim's reading, by my understanding]
- As of release 1.11, support ... has been removed. [Vasili's reading, by
my understanding]
Whilst it is ''correct'' as it currently stands, it relies on parsing of
English in a specific manner to know what it actually means, and for that
reason I'd side with the suggestion of re-considering the wording.
--
Ticket URL: <https://code.djangoproject.com/ticket/28483#comment:2>
Django
-------------------------------+--------------------------------------
Component: Documentation | Version:
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Vasili Korol):
Replying to [comment:2 Keryn Knight]:
Yes, I understood it as'' "starting from 1.11, support has been
removed''". I can see Tim's point, but I still think that the phrase can
be misunderstood. It was confusing to me, though I was almost sure that
1.11 still **does** support Python 2.7 and 3.4.
--
Ticket URL: <https://code.djangoproject.com/ticket/28483#comment:3>
Django
support
-------------------------------+------------------------------------
Reporter: Vasili Korol | Owner: nobody
Component: Documentation | Version:
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* resolution: invalid => fixed
* stage: Unreviewed => Accepted
Comment:
I've changed the language in the
[https://github.com/django/django/pull/8884 PR] to document Python 3.4
support for Django 2.0.
--
Ticket URL: <https://code.djangoproject.com/ticket/28483#comment:4>