[Django] #30082: https://docs.djangoproject.com/en/dev/releases/1.11/ - add to the docs

[Django]

#30082: https://docs.djangoproject.com/en/dev/releases/1.11/ - add to the docs
-------------------------------------+-------------------------------------
Reporter: uri- | Owner: nobody
rodberg |
Type: | Status: new
Uncategorized |
Component: | Version: 1.11
Documentation | Keywords: Python 3.7
Severity: Normal | DeprecationWarning
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
https://code.djangoproject.com/ticket/30078

1. https://docs.djangoproject.com/en/dev/releases/1.11/ should contain
something like "running Django 1.11.* with Python 3.7 with deprecation
warnings enabled will raise a DeprecationWarning." or similar.

2. Change from 1.11.17 to 1.11.18.

3. Change "will end in April 2018." to "ended in April 2018."

Same for all versions of this doc such as
https://docs.djangoproject.com/en/1.11/releases/1.11/.

--
Ticket URL: <https://code.djangoproject.com/ticket/30082>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#30082: Document that Django 1.11.x raises a deprecation warning with Python 3.7
-------------------------------------+-------------------------------------
Reporter: אורי | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.11
Severity: Normal | Resolution: wontfix
Keywords: Python 3.7 | Triage Stage:
DeprecationWarning | 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
* type: Uncategorized => Cleanup/optimization
* resolution: => wontfix

Old description:

> https://code.djangoproject.com/ticket/30078
>
> 1. https://docs.djangoproject.com/en/dev/releases/1.11/ should contain
> something like "running Django 1.11.* with Python 3.7 with deprecation
> warnings enabled will raise a DeprecationWarning." or similar.
>
> 2. Change from 1.11.17 to 1.11.18.
>
> 3. Change "will end in April 2018." to "ended in April 2018."
>
> Same for all versions of this doc such as
> https://docs.djangoproject.com/en/1.11/releases/1.11/.

New description:

1. https://docs.djangoproject.com/en/dev/releases/1.11/ should contain
something like "running Django 1.11.* with Python 3.7 with deprecation

warnings enabled will raise a DeprecationWarning." or similar (#30078).

2. Change from 1.11.17 to 1.11.18.

3. Change "will end in April 2018." to "ended in April 2018."

Same for all versions of this doc such as
https://docs.djangoproject.com/en/1.11/releases/1.11/.

--

Comment:

1. I don't see value in documenting this.
2. The documentation is correct that Python 3.7 support was added in
Django 1.11.17.
3. There isn't much value in this change and we avoid trivial updates
because it requires translators to update translated docs (and versions
other the the latest stable version of the docs, Django 2.1 as of now,
aren't retranslated).

--
Ticket URL: <https://code.djangoproject.com/ticket/30082#comment:1>

[Django]

#30082: Document that Django 1.11.x raises a deprecation warning with Python 3.7
-------------------------------------+-------------------------------------
Reporter: אורי | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.11
Severity: Normal | Resolution: wontfix
Keywords: Python 3.7 | Triage Stage:
DeprecationWarning | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Dylan Young):

NOTE that this isn't actually removed until version 3.10, so it shouldn't
bite anyone in any case. (See python 3.9 docs for the collections module)

--
Ticket URL: <https://code.djangoproject.com/ticket/30082#comment:2>