#11716: Various methods in django.db.models.fields don't wrap ValueErrors and
allow
them to escape
---------------------------------------------------+------------------------
Reporter: Leo | Owner: Leo
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by adamnelson):
@kmtracey While it may in theory be true that milestone:1.2 is 'minor',
that's not true in practice. Python 2.3 support is being dropped as well
as all sorts of major backwards incompatible changes. Anybody who wrote a
workaround for this behavior can stick with milestone:1.1 for an extended
period of time while updating their codebase. Well maintained apps can
move to this format in short order without losing milestone:1.0
compatibility. I would understand not making a backwards incompatible
change in milestone:1.1.1 , but for something as big as milestone:1.2 with
so many other major incompatibilities, we're wasting time.
In addition, russelm accepted the ticket and assigned it to milestone:1.2
. That should be sufficient to get the ticket merged.
--
Ticket URL: <http://code.djangoproject.com/ticket/11716#comment:17>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
