#7804 closed (invalid)
newforms.fields.UploadedFile Invalid Deprecation warning.
Reported by: | Collin Anderson | Owned by: | |
---|---|---|---|
Component: | Forms | Version: | dev |
Severity: | Keywords: | 2070-fix | |
Cc: | cmawebsite@… | 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
I'm not sure if anyone has noticed this yet, but in [7814],
newforms.fields.UploadedFile.content was changed to
newforms.fields.UploadedFile.data without being listed on
BackwardsIncompatibleChanges or raising a deprecation warning. However
the [7859] change has a deprecation warning for the UploadedFile.data
attribute, which was only in there for 45 revisions. It would be nice
to also have a deprecation warning for UploadedFile.content.
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Uploa...
http://code.djangoproject.com/changeset/7814
http://code.djangoproject.com/changeset/7859
Change History (7)
comment:1 by , 16 years ago
milestone: | → post-1.0 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 16 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
Triage Stage: | Unreviewed → Someday/Maybe |
comment:3 by , 16 years ago
Well what I am saying is that the change listed on the wiki is that [7814] changed the newforms uploaded file interface from .content to .data, and [7859] changes the interface from .data to read(), and only the .data to read() backwards incompatibility is listed. It seems to me that either the documented backwards incompatibility should be from .content to .data, and .data to .read(), or just .content to .read(), but the .content to .data change is not listed at all.
comment:4 by , 16 years ago
Component: | Uncategorized → django.newforms |
---|---|
milestone: | post-1.0 |
Summary: | newforms.fields.UploadedFile Undocumented Backwards Incompatible change → newforms.fields.UploadedFile Invalid Deprecation warning. |
Triage Stage: | Someday/Maybe → Unreviewed |
The deprecated .data attribute that was only in there for 45 revisions gives a warning if you use it, but the .content attribute that has been in there for almost a year gives an attribute error.
comment:5 by , 16 years ago
milestone: | → 1.0 maybe |
---|---|
Triage Stage: | Unreviewed → Design decision needed |
comment:6 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
We've since removed (or should have removed) all the deprecation warnings in prep for 1.0, so this is no longer valid.
This change was only in for 45 revisions, I don't think it needs to be in the wiki. If you can find a good place to put it in, go ahead and change it. It's a wiki afterall :)