Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
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 Simon Charette):

 To make it clear, this ticket cannot be worked on until Django 6.0 which
 will remove the deprecation shim for `CheckConstraint.check` in favor of
 `.condition` which will allow `BaseConstraint.check` to be reclaimed.
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ed4e95816-096add39-c70f-4a6c-a2e9-a9bd44b1957c-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
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
-+-
Changes (by avish mehta):

 * owner:  (none) => avish mehta
 * status:  new => assigned

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ed4caad8a-89cd34df-edfb-437d-917b-d43d88959636-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#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
-+-
Changes (by avish mehta):

 * owner:  avish mehta => (none)
 * status:  assigned => new

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ed4ca658c-a8d21d7d-7d65-4cfa-8bc2-f60a5270415c-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check()

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  avish
 Type:   |  mehta
  Cleanup/optimization   |   Status:  assigned
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
-+-
Changes (by avish mehta):

 * owner:  nobody => avish mehta
 * status:  new => assigned

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ed4c8af31-fb96bb01-d3d2-42dd-9962-2aea5138cf4f-00%40eu-central-1.amazonses.com.

Re: [Django] #35358: Rename BaseConstraint._check() to check() (was: Rename BaseConstraint._check to check once the deprecation period)

[Django]

#35358: Rename BaseConstraint._check() to check()
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 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
-+-
Changes (by Tim Graham):

 * keywords:   => 6.0
 * stage:  Unreviewed => Someday/Maybe
 * summary:  Rename BaseConstraint._check to check once the deprecation
 period => Rename BaseConstraint._check() to check()


Old description:

> [https://github.com/django/django/pull/17876/files#r1508517275 Per this
> comment] this is tracking renaming the `BaseConstraint._check` method to
> `check` when the ungoing deprecation period for `BaseConstraint.check`
> (now `.condition`) ends.
>
> Not sure if there is a better way to categorize this ticket so it doesn't
> fall between the cracks when the deprecation period ends.

New description:

 [https://github.com/django/django/pull/17876/files#r1508517275 Per this
 comment] , `BaseConstraint._check()` should be renamed to `check()` in
 Django 6.0 when the deprecation period for `BaseConstraint.check` (now
 `.condition`) ends.

--
Comment:

 For past releases, I put the Django version number in the keywords field
 and used that Trac query
 
([https://code.djangoproject.com/query?keywords=~1.11=Accepted=assigned=closed=new=changetime=1=id=summary=status=owner=type=version=changetime
 example]).
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ebb92cc6c-6fe85cbd-cf0e-4dee-b2a9-01afb98db203-00%40eu-central-1.amazonses.com.

[Django] #35358: Rename BaseConstraint._check to check once the deprecation period

[Django]

#35358: Rename BaseConstraint._check to check once the deprecation period
-+-
   Reporter:  Simon  |  Owner:  nobody
  Charette   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  dev
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 [https://github.com/django/django/pull/17876/files#r1508517275 Per this
 comment] this is tracking renaming the `BaseConstraint._check` method to
 `check` when the ungoing deprecation period for `BaseConstraint.check`
 (now `.condition`) ends.

 Not sure if there is a better way to categorize this ticket so it doesn't
 fall between the cracks when the deprecation period ends.
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018eb50a74ca-93c019d7-1e5e-48c0-8c36-ac9af364705c-00%40eu-central-1.amazonses.com.