#2363: [patch] Tighten subclass check at top of
db.models.base.ModelBase.__new__.
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: reopened | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Ready for checkin
Comment:
In principle, this looks like the right solution. Thanks, guys. :-)
A shame that Python doesn't let use access the thing raising the name
error more easily for tighter checking (by including it as an attribute in
the NameError class), but I don't want to start matching against the
string version of the exception, so we'll leave that.
I'll check this in when I get a chance.
--
Ticket URL: <http://code.djangoproject.com/ticket/2363#comment:10>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
