#28613: Document that GenericForeignKey returns None when referring to
nonexistent
pk
--------------------------------------+------------------------------------
Reporter: Sjoerd Job Postmus | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: genericforeignkey | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* component: contrib.contenttypes => Documentation
* stage: Unreviewed => Accepted
* type: Uncategorized => Cleanup/optimization
Comment:
There's
[https://github.com/django/django/blob/6da140724dba546d2f3aced1308e617747b0385c/tests/generic_relations/tests.py#L398-L401
one assertion] in Django's test suite that fails with the exception
catching removed. I doubt it's appropriate to raise a warning for properly
working code (assuming the test represents a valid use case -- I didn't
study it in much detail). Accepting at least as a documentation
enhancement.
--
Ticket URL: <https://code.djangoproject.com/ticket/28613#comment:1>
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/067.77944ea576e6e53888630d5b1443a219%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
