#12164 closed (fixed)
Remove Python 2.3 imports
| Reported by: | Tim Graham | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Since Python 2.3 is no longer supported beginning with Django 1.2, we can remove these imports on trunk.
Attachments (2)
Change History (9)
by , 16 years ago
| Attachment: | 12164.diff added |
|---|
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
In past we've said we didn't want to do this because it makes backporting patches harder, I don't think that's accurate. So we should do this (and delete the decimal backport).
comment:3 by , 16 years ago
I've refreshed the patch on current trunk. I also deleted the django/utils/_decimal.py file.
comment:4 by , 16 years ago
| milestone: | → 1.2 |
|---|---|
| Triage Stage: | Accepted → Design decision needed |
We need to get a design decision on this before 1.2RC
comment:5 by , 16 years ago
Russ, Karen and I discussed this the other day and I think the consensus was that it was probably a good idea, as we've had accidental backports that caused Python 2.3 breakages. Doing it in one fell-swoop avoids that possibility.
comment:6 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
We still need to import decimal in 2.4, we just don't need to the one in django.utils.