#35284: PositiveIntegerField description is confusing
-------------------------------------+-------------------------------------
Reporter: Jon Ribbens | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:9 Jon Ribbens]:
> I rather think you're missing the point completely - the sentence
doesn't "provide a clarification", it misleads people and makes things
less clear, as I explained in my argument above that nobody has provided a
response to. But obviously I can't force you to improve your product. Oh
well.
Hey Jon, I beg to differ. Both bcail and myself are answering to your
argument: while there is ''not'' a proposal to deprecate allowing 0 in the
field, the sentence warns the users about potential unexpected outcomes.
It's easy to assume that a `PositiveIntegerField` would not allow 0, so
the note in the docs is making it clear that 0 ''is allowed'' and it will
be for the foreseeable future due to the backward compatibility goal.
I hope that helps!
--
Ticket URL: <https://code.djangoproject.com/ticket/35284#comment:10>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e2d890a5d-5a487fc8-fcd6-40a3-b8e4-4090a758e4d7-000000%40eu-central-1.amazonses.com.
