#35358: Rename BaseConstraint._check() to check()
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: 6.0 | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sourav Kumar):
So sorry for not paying attention. Got carried away with the excitement of
solving my first issue.
Replying to [comment:7 Mariusz Felisiak]:
> Replying to [comment:6 Sourav6971]:
> > The above issue has been resolved in the below PR.
> > https://github.com/django/django/pull/18448
>
> Ticket is fixed when PR is merged. Secondly, as Simon already
[https://code.djangoproject.com/ticket/35358?replyto=6#comment:5
mentioned], this ticket cannot be worked on until Django 6.0. Please work
on "Accepted" tickets, not tickets marked as "Someday/maybe".
--
Ticket URL: <https://code.djangoproject.com/ticket/35358#comment:8>
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/010701912273030c-e9104622-3569-4d02-b7af-7e88d80f4b17-000000%40eu-central-1.amazonses.com.
