Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#7804 closed (invalid)

newforms.fields.UploadedFile Invalid Deprecation warning.

Reported by: Collin Anderson Owned by:
Component: Forms Version: master
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: UI/UX:


I'm not sure if anyone has noticed this yet, but in [7814],
newforms.fields.UploadedFile.content was changed to without being listed on
BackwardsIncompatibleChanges or raising a deprecation warning. However
the [7859] change has a deprecation warning for the
attribute, which was only in there for 45 revisions. It would be nice
to also have a deprecation warning for UploadedFile.content.

Change History (7)

comment:1 Changed 10 years ago by Eric Holscher

milestone: post-1.0
Owner: changed from nobody to Eric Holscher
Status: newassigned

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 :)

comment:2 Changed 10 years ago by Eric Holscher

Owner: Eric Holscher deleted
Status: assignednew
Triage Stage: UnreviewedSomeday/Maybe

comment:3 Changed 10 years ago by Collin Anderson

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 Changed 10 years ago by Collin Anderson

Component: Uncategorizeddjango.newforms
milestone: post-1.0
Summary: newforms.fields.UploadedFile Undocumented Backwards Incompatible changenewforms.fields.UploadedFile Invalid Deprecation warning.
Triage Stage: Someday/MaybeUnreviewed

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 Changed 10 years ago by Eric Holscher

milestone: 1.0 maybe
Triage Stage: UnreviewedDesign decision needed

comment:6 Changed 10 years ago by Jacob

Resolution: invalid
Status: newclosed

We've since removed (or should have removed) all the deprecation warnings in prep for 1.0, so this is no longer valid.

comment:7 Changed 10 years ago by (none)

milestone: 1.0 maybe

Milestone 1.0 maybe deleted

Note: See TracTickets for help on using tickets.
Back to Top