Documentation inconsistency for URLField verify_exists param for v1.2
|Reported by:||anonymous||Owned by:||nobody|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
"class URLField([verify_exists=False, max_length=200, options])
A CharField for a URL. Has one extra optional argument:
If True (the default), the URL given will be checked for existence (i.e., the URL actually loads and doesn't give a 404 response).
Note that when you're using the single-threaded development server, validating a URL being served by the same server will hang. This should not be a problem for multithreaded servers.
Changed in Django 1.2: Please, see the release notes"
The description suggests that the default value for this parameter is True, but the declaration suggests that it's False. Additionally, there is no mention of verify_exists in the Django 1.2 release notes.
Change History (4)
comment:1 Changed 5 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Ready for checkin|