#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: Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Comment (by [EMAIL PROTECTED]):
I'm kinda leery of adding the module check: if the name check is hackish,
wouldn't it be more of the same? I concede that the only cases that would
defeat it are pathological.
I'm sorry about not getting a patch up yesterday; (a tapas bar viciously
leaped on me, I barely escaped with my life.) I've got an (untested) one
here just to show what I meant a few comments ago. (I can't run the new
test (or the others) atm, but maybe Chris would give it a crack?)
--
Ticket URL: <http://code.djangoproject.com/ticket/2363#comment:8>
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
-~----------~----~----~----~------~----~------~--~---
