#24707: urls: error messages for broken views are better for
deprecated-old-style
than they are for new-style
-------------------------------------+-------------------------------------
Reporter: hjwp | Owner: hjwp
Type: | Status: assigned
Cleanup/optimization |
Component: Core (URLs) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by hjwp):
It's definitely a grey area, I agree. Still, if you're prepared to
entertain the argument that it's a maybe-sortof-regression-in-the-ux, then
the fact that the deprecation happened in 1.7 doesn't matter, it's still a
regression... I guess, in theory, you could apply to it to 1.7.x as well
as 1.8.x!? Anyways, irrespective of what the specific guidelines are, I'd
still like to asking you guys to consider it. It really would make my
life lots easier for the move to 1.8, and it'll help me tell a better
story to my readers, lots of which are meeting django for the first time.
So if there's some leeway to interpret the rules and make someone happy,
well...
--
Ticket URL: <https://code.djangoproject.com/ticket/24707#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/062.00c46208b28232787bacd3c2c54b77df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
