#35127: Model.full_clean() errors with GeneratedField
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* cc: Mariusz Felisiak, Lily Foote, Paolo Melchiorre (added)
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Hello, thank you for your report! And thank you for providing a failing
test.
I'm accepting given the failing test and that there is nothing in the docs
stating that `full_clean` would not be supported for models including a
`GeneratedField`s, so while more expert input is needed (adding them as
CC), this seems like a valid issue.
Regression in f333e3513e8bdf5ffeb6eeb63021c230082e6f95
--
Ticket URL: <https://code.djangoproject.com/ticket/35127#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d1dd13b5e-ead20901-b394-46ea-9aae-d24beb651e39-000000%40eu-central-1.amazonses.com.
