#26821: 'NoneType' object has no attribute 'strip'
-------------------------------------+-------------------------------------
Reporter: vinaykrsharma | Owner: PriyWerry
Type: Bug | Status: assigned
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: error,form fields, | Triage Stage: Accepted
strip |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by PriyWerry):
Replying to [comment:10 timgraham]:
> Yes, this will be a backwards-incompatible change in the sense that
developers may have to remove useless `strip` arguments, but I don't think
it should affect many users -- `strip` was only added in 1.9 and
specifying `strip` doesn't have any effect, so there's no reason for a
developer to do it except if they don't realize that. I think this course
of action is less confusing than a deprecation path which changes the
behavior in the meantime and makes `strip=False` have an effect.
Sounds good to me! I've updated the pull-request to reflect your
suggestion. The deprecation warning and mentioning in the docs are removed
and replaced by a ..versionadd::.
--
Ticket URL: <https://code.djangoproject.com/ticket/26821#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.835d9b0df8a1f14a83b3ca876ff5ad8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
