Changes between Initial Version and Version 2 of Ticket #28447


Ignore:
Timestamp:
Jul 28, 2017, 4:37:30 PM (7 years ago)
Author:
Tim Graham
Comment:

Per our ​supported versions policy, 1.10 is only receiving fixes for security and data loss issues, so we won't fix this issue there.

Closing as duplicate of #28441.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #28447

    • Property Owner changed from nobody to Lyle Scott III
    • Property Status new → closed
    • Property Resolution → duplicate

  • Ticket #28447 – Description

    initial v2  
    1 I updated Python via brew yesterday (3.6.1 to 3.6.2) and have been having problems running Django since then. https://code.djangoproject.com/ticket/28441 references the issue, but for Django 1.11.x. Looking at the PR for that ticket, https://github.com/django/django/pull/8817, it looks like that is not a clean patch to Django 1.10.x
     1I updated Python via brew yesterday (3.6.1 to 3.6.2) and have been having problems running Django since then. #28441 references the issue, but for Django 1.11.x. Looking at the PR for that ticket, https://github.com/django/django/pull/8817, it looks like that is not a clean patch to Django 1.10.x
    22
    33* macOS Sierra - 10.12.5 (16F73)
Back to Top