#27025: Python 3.6 compatibility
     Reporter:  Tim Graham    |                    Owner:  nobody
         Type:  New feature   |                   Status:  new
    Component:  Core (Other)  |                  Version:  master
     Severity:  Normal        |               Resolution:
     Keywords:                |             Triage Stage:  Accepted
    Has patch:  0             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  0             |                    UI/UX:  0

Comment (by Tim Graham):

 I setup a more complete test environment that includes all of the test
 suite dependencies and identified a few more failures fixed in the above

 2 failures remain as of Django b5aac66b28c615b2bda63548cbd695dbb5a0c381
 and cpython
 d614d687d9db1100d0a4ec8c67e0cb3ce773342b] due to a sqlparse
 incompatibility with Python 3.6. I submitted a
 [https://github.com/andialbrecht/sqlparse/pull/292 PR] to fix it and it's
 merged awaiting the next release.

Ticket URL: <https://code.djangoproject.com/ticket/27025#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to