Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#30082 closed Cleanup/optimization (wontfix)

Document that Django 1.11.x raises a deprecation warning with Python 3.7

Reported by: אורי Owned by: nobody
Component: Documentation Version: 1.11
Severity: Normal Keywords: Python 3.7 DeprecationWarning
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

  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).
  1. Change from 1.11.17 to 1.11.18.
  1. 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/.

Change History (2)

comment:1 by Tim Graham, 5 years ago

Description: modified (diff)
Resolution: wontfix
Status: newclosed
Summary: https://docs.djangoproject.com/en/dev/releases/1.11/ - add to the docsDocument that Django 1.11.x raises a deprecation warning with Python 3.7
Type: UncategorizedCleanup/optimization
  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).

comment:2 by Dylan Young, 3 years ago

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)

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