Opened 13 years ago
Closed 13 years ago
#16900 closed Bug (wontfix)
utils.dictconfig and utils.unittest don't work with python 3.0 and 3.1
Reported by: | adsworth | Owned by: | adsworth |
---|---|---|---|
Component: | Python 3 | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | adsworth | Triage Stage: | Design decision needed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
utils.log imports the django specific copy of dictconfig is the import from the stdlib fails.
The copy is a copy of the 2.X version of dictconfig.py and this version does not work with py3k.
We can now either:
- adapt the copy to work with py3k
- also copy the py3k version of dictconfig and if the import from the stdlib fails make a conditional import depending on if we are running a version >= 3 or not.
Change History (6)
comment:1 by , 13 years ago
Summary: | utls.dictconfig doesn't work with python 3 → utils.dictconfig doesn't work with python 3 |
---|
comment:2 by , 13 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:3 by , 13 years ago
The same applies to utils.unittest. It has a work around for python 2.7, but fails for 3.0 and 3.1 as unittest2 was added in 3.2.
comment:4 by , 13 years ago
Cc: | added |
---|
comment:5 by , 13 years ago
Summary: | utils.dictconfig doesn't work with python 3 → utils.dictconfig and utils.unittest don't work with python 3.0 and 3.1 |
---|
comment:6 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This is a good reason to assume that Django starts Python 3 support with 3.2.
Note:
See TracTickets
for help on using tickets.
This is a problem only on python 3.0 and 3.1, because since 3.2 dictconfig is part of the standard library.
To the best of my knowledge, nobody has decided which versions of python 3 would be supported by Django. It would be reasonable to start support at Python 3.2 (by the time the py3k branch is merged in trunk). In this case, this ticket wouldn't be necessary.
Marking as DDN, the decision to take is "which versions of Python are targeted by the py3k branch?"