Re: [Django] #31839: Add additional database functions.

[Django]

#31839: Add additional database functions.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  functions, random,   | Triage Stage:
  truncate, log2, log10, bit |  Unreviewed
  length, octet length, hyperbolic   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nick Pope):

 Will you still take `Random` and `Truncate`?

 In the case of `Random` there is also a nice bit of simplification:

 
https://github.com/django/django/commit/c8913d41e74859747893dc21356a1fb6906c56e9

-- 
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/065.7c371ff0df926ffe33542664f78574bc%40djangoproject.com.

Re: [Django] #31839: Add additional database functions.

[Django]

#31839: Add additional database functions.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  functions, random,   | Triage Stage:
  truncate, log2, log10, bit |  Unreviewed
  length, octet length, hyperbolic   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  assigned => closed
 * resolution:   => wontfix


Comment:

 I think we need to decide at what point we say enough is enough here, and
 recommend users create their own functions like we did with template tags.
 For me hyperbolic functions cross that line. You can start a discussion on
 DevelopersMailingList if you don't agree. Personally I've never used any
 of proposed database functions.

-- 
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/065.983d10abe9776f6a1dde3c7fd76d5c64%40djangoproject.com.

Re: [Django] #31822: Add support for item_comments to syndication framework

[Django]

#31822: Add support for item_comments to syndication framework
-+-
 Reporter:  Viktor Garske|Owner:  Viktor
 |  Garske
 Type:  New feature  |   Status:  closed
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"1173db4a16bb2938ba62a6cd50372a76a7f9e05f" 1173db4a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1173db4a16bb2938ba62a6cd50372a76a7f9e05f"
 Fixed #31822 -- Added support for comments URL per feed item.

 The item_comments hook returns a comments URL which is then used by the
 feed builder.
 }}}

-- 
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/064.339f6c0a1c88ccb848e394eaa4b0718a%40djangoproject.com.

Re: [Django] #31822: Add support for item_comments to syndication framework

[Django]

#31822: Add support for item_comments to syndication framework
-+-
 Reporter:  Viktor Garske|Owner:  Viktor
 |  Garske
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


-- 
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/064.b6640f0cf9653378b2ed317782cddeda%40djangoproject.com.

Re: [Django] #31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup instead of overridden lookup

[Django]

#31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup 
instead of
overridden lookup
-+-
 Reporter:  sage |Owner:  sage
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"32cb1fe1c66645671681407d47e8370b4afbfc3f" 32cb1fe1]:
 {{{
 #!CommitTicketReference repository=""
 revision="32cb1fe1c66645671681407d47e8370b4afbfc3f"
 [3.1.x] Refs #31829 -- Added
 DatabaseFeatures.json_key_contains_list_matching_requires_list.

 CockroachDB's behavior matches PostgreSQL.
 Backport of 184a6eebb0ef56d5f1b1315a8e666830e37f3f81 from master
 }}}

-- 
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/067.c26919dd2532434ecb9380715752af21%40djangoproject.com.

Re: [Django] #31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup instead of overridden lookup

[Django]

#31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup 
instead of
overridden lookup
-+-
 Reporter:  sage |Owner:  sage
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"184a6eebb0ef56d5f1b1315a8e666830e37f3f81" 184a6eeb]:
 {{{
 #!CommitTicketReference repository=""
 revision="184a6eebb0ef56d5f1b1315a8e666830e37f3f81"
 Refs #31829 -- Added
 DatabaseFeatures.json_key_contains_list_matching_requires_list.

 CockroachDB's behavior matches PostgreSQL.
 }}}

-- 
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/067.9f02a8b8c25412320b3e1abfe60387d5%40djangoproject.com.

Re: [Django] #31839: Add additional database functions.

[Django]

#31839: Add additional database functions.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  functions, random,   | Triage Stage:
  truncate, log2, log10, bit |  Unreviewed
  length, octet length, hyperbolic   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Nick Pope:

Old description:

> I propose adding some additional database functions:
>
> - `Random`  -- generate random numbers in the range `[0.0, 0.1)`.
> - `Truncate` -- round number towards zero. (SQL function is `TRUNC`, but
> `Trunc` is used for date truncation in Django.)
> - `Log2` and `Log10` -- simple logarithm functions without needing to
> provide the base.
> - `ACosh`, `ASinh`, `ATanh`, `Cosh`, `Sinh`, and `Tanh` -- hyperbolic
> functions.
> - `BitLength` and `OctetLength` -- length of string in bits and bytes,
> complement to `Length` which is character length.

New description:

 I propose adding some additional database functions:

 - `Random`  -- generate random numbers in the range `[0.0, 0.1)`.
 - `Truncate` -- round number towards zero. (SQL function is `TRUNC`, but
 `Trunc` is used for date truncation in Django.)
 - `Log2` and `Log10` -- simple logarithm functions without needing to
 provide the base.
 - `ACosh`, `ASinh`, `ATanh`, `Cosh`, `Sinh`, and `Tanh` -- hyperbolic
 functions.
 - `BitLength` and `ByteLength` -- length of string in bits and bytes,
 complement to `Length` which is character length.

--

-- 
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/065.59de556bbf2b2de6d7e2cbf38d3760c3%40djangoproject.com.

Re: [Django] #29336: No docs for circular template inheritance

[Django]

#29336: No docs for circular template inheritance
-+-
 Reporter:  Adrian Turjak|Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by David Smith):

 * has_patch:  0 => 1


-- 
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/071.623753eda9c06ce7a5d5c3091fa95224%40djangoproject.com.

Re: [Django] #31840: Adding Support for Cross-Origin Opener Policy

[Django]

#31840: Adding Support for Cross-Origin Opener Policy
-+-
 Reporter:  meggles711   |Owner:
 |  meggles711
 Type:  New feature  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  COOP, security,  | Triage Stage:
  headers|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by meggles711):

 * owner:  nobody => meggles711
 * 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/068.45eae7f9fa9be346fcc397b6c0cb649b%40djangoproject.com.

[Django] #31840: Adding Support for Cross-Origin Opener Policy

[Django]

#31840: Adding Support for Cross-Origin Opener Policy
-+-
   Reporter: |  Owner:  nobody
  meggles711 |
   Type:  New| Status:  new
  feature|
  Component:  HTTP   |Version:  master
  handling   |   Keywords:  COOP, security,
   Severity:  Normal |  headers
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I would like to add support for the cross-origin Opener Policy header in
 Django.

 **What is Cross-Origin Opener Policy?**
 Cross-origin opener policy (COOP) is an HTTP header that protects against
 cross-origin attacks when set. This is a relatively new security feature
 that would add protection to Django

 Historically, CORS has been sufficient in protecting against these attacks
 by confirming that a server intends to share a resource with a given
 origin. Spectre, a vulnerability in modern processors, has made any data
 loaded into the same browsing context potentially vulnerable. COOP is used
 to tell browsers to open resources so that they are loaded within separate
 browsing contexts preventing information leaks.

 COOP isolates top level windows from other documents by loading them in a
 different browsing context. This means that all cross-origin requests can
 be vetted by the server that owns the resource.

 This header can be set to same-origin, same-origin-allow-popups, or
 unsafe-none.  Documents marked same-origin can only be in the same
 browsing context as other documents from the same origin that are also
 marked same-origin. Documents marked as same-origin-allow-popups can
 maintain references to pop ups if they do not have the COOP header set or
 if they are marked as unsafe-none. Documents marked as unsafe-none can be
 added to the opener’s browsing context unless the opener is marked same-
 origin.

 With COOP, developers can finely control cross origin access to each
 document in their application. You can read more about COOP in the
 [https://html.spec.whatwg.org/multipage/origin.html#the-cross-origin-
 opener-policy-header spec].


 **Proposed Changes to Django**

 Django users should have the ability to set the COOP header. This can be
 implemented in a similar way to the Referrer-Policy header in the security
 middleware. The header will be added to the response in the
 process_response function. The header should default to same-origin as
 this is the most secure setting.

-- 
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/053.056836eb8217207d138476234b27ea8e%40djangoproject.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+
 Reporter:  Alex Rothberg  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Abhishek Bera):

 * owner:  Abhishek Bera => (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/067.653d4b4c31e53c8a0f6ec61cf3a5fe44%40djangoproject.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+-
 Reporter:  Alex Rothberg  |Owner:  Abhishek Bera
 Type:  New feature|   Status:  assigned
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Abhishek Bera):

 Update: This is the commit if someone needs it
 
https://github.com/berabhishek/django/pull/1/commits/2a92314a3effca22a43219fcbdfdc6add9ccaf66

-- 
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/067.3e03587ae0f31eb0130434ef3fdca5ea%40djangoproject.com.

Re: [Django] #31826: AlterField with db_column addition should be a noop.

[Django]

#31826: AlterField with db_column addition should be a noop.
-+-
 Reporter:  Iuri de Silvio   |Owner:  Iuri de
 Type:   |  Silvio
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1


-- 
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/068.36b10a363b98fcf6e528cc5948d68f88%40djangoproject.com.

Re: [Django] #28507: Allow ValidationErrors to equal each other when created identically

[Django]

#28507: Allow ValidationErrors to equal each other when created identically
-+-
 Reporter:  kamni|Owner:  David
 |  Smith
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ValidationError  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"95da207bdb7550922781bbdb3a7b993db0dfc4cf" 95da207]:
 {{{
 #!CommitTicketReference repository=""
 revision="95da207bdb7550922781bbdb3a7b993db0dfc4cf"
 Fixed #28507 -- Made ValidationError.__eq__() ignore messages and params
 ordering.

 Co-authored-by: caleb logan 
 }}}

-- 
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/063.266d43ed64d1eddbbf57a39c8cd07209%40djangoproject.com.

Re: [Django] #31825: RenameField with db_column should be a noop.

[Django]

#31825: RenameField with db_column should be a noop.
-+-
 Reporter:  Iuri de Silvio   |Owner:  Iuri de
 Type:   |  Silvio
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1


-- 
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/068.05d9d40c946e7d3b9e6354f174b5a4c0%40djangoproject.com.

Re: [Django] #27395: Allow generating '

[Django]

#27395: Allow generating '):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"16218c20606d8cd89c5393970c83da04598a3e04" 16218c20]:
 {{{
 #!CommitTicketReference repository=""
 revision="16218c20606d8cd89c5393970c83da04598a3e04"
 Fixed #27395 -- Added sitemap 'alternates' generation.

 Updated the sitemap generator and default template to optionally
 include link elements with hreflang attribute to alternate language
 URLs.
 }}}

-- 
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/062.23adf4fd582df59640c538d3381ff0dc%40djangoproject.com.

Re: [Django] #27395: Allow generating '

[Django]

#27395: Allow generating '):

 In [changeset:"50e1ccbbea4c6f8e14a186149dd757483f0f0da5" 50e1ccbb]:
 {{{
 #!CommitTicketReference repository=""
 revision="50e1ccbbea4c6f8e14a186149dd757483f0f0da5"
 Refs #27395 -- Added XML namespace declaration to sitemap template.

 As per Google recommendations:
 https://support.google.com/webmasters/answer/189077?hl=en
 }}}

-- 
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/062.7f9b3effa6e2f7e20d6f50d61ecce789%40djangoproject.com.

Re: [Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
+--
 Reporter:  Gordon Wrigley  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Migrations  |  Version:  3.0
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Gordon Wrigley):

 Thank you for walking me through that. I had missed the bit about the
 default manager.
 Maybe we should change the fake models to fail with an explanation when
 the objects manager isn't included migrations and the user tries to access
 it.

-- 
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/065.d97d0d9c6a5e339872a92738fdb10a44%40djangoproject.com.

Re: [Django] #27395: Allow generating '

[Django]

#27395: Allow generating ' Ready for checkin


-- 
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/062.b1cc6ee60cfabc69ce8e92b2ccf561df%40djangoproject.com.

Re: [Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
+--
 Reporter:  Gordon Wrigley  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Migrations  |  Version:  3.0
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by felixxm):

 > 2: They are both actually instances of the Django base manager so they
 have the same setting for use_in_migrations (I presume True)

 No, by default the `use_in_migrations` attribute is `False`.

 Let's start from the beginning. Django includes in migrations a base
 manager, a default manager and managers with `use_in_migrations` set to
 `True`. The order matters because the first `Manager` Django encounters
 (in the order in which they’re defined in the model) has a special status,
 it's interpreted as the “default” Manager (see
 [https://docs.djangoproject.com/en/3.0/topics/db/managers/#default-
 managers docs]). Moreover to prevent unnecessary migrations we added in
 #26643 check to omit migrations if only one manager meet requirements and
 it's called `objects`.

 > 3: If you swap the order of the manager declarations around in the
 source code it no longer generates any migration.

 Yes because the first (and the default) manager is called `objects`, and
 it's the only manager that meets requirements to be included in
 migrations. In such cases we omit it to prevent unnecessary migrations
 (see #26643). The second manager doesn't have `use_in_migrations` set to
 `True` so it's ignored.

 > 4: If you leave the order as is in the linked commit but additionally
 redeclare the objects manager in the concrete model classes it again
 decides no migration is needed

 Yes because that changes the default manager to `objects`.

 >
 > If this example seems a lil simplistic that's because I was trying to
 get a minimal reproduction, here's one that is structurally equivalent to
 what I actually have:
 > https://github.com/tolomea/django-
 tutorial/commit/f247b6ddc5b2b689ec7ec0ede7cb0bc28c99db0c
 > Where everything prefixed lib is in a 3rd party library.
 >
 > In there you can see that overriding objects on the concrete model
 causes both to be added to the migration.
 > Switching the order of the managers around also leads to a migration
 adding both managers to both concrete models.

 `lib_manager` is added because it's declared as a base manager, `objects`
 is added because it's a default manager, so we have two managers which
 meets requirements. That's why both are included in migrations.

-- 
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/065.a9d45eb137f16590663c72a94f4f9bb0%40djangoproject.com.

Re: [Django] #30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and ungettext_lazy()

[Django]

#30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and
ungettext_lazy()
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson ):

 In [changeset:"e0397e11b560a502933fbffd84ff069b4dcbd31b" e0397e1]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0397e11b560a502933fbffd84ff069b4dcbd31b"
 [3.0.x] Refs #30165 -- Removed leftover 'u' prefix.

 Backport of bac5777bff8e8d8189193438b5af52f158a3f2a4 from master
 }}}

-- 
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/067.dbece25d3c2bea45b98c3a795620d295%40djangoproject.com.

Re: [Django] #30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and ungettext_lazy()

[Django]

#30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and
ungettext_lazy()
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson ):

 In [changeset:"06474e929f49c4db165b7e9c7b1e1f3c8c4d1354" 06474e9]:
 {{{
 #!CommitTicketReference repository=""
 revision="06474e929f49c4db165b7e9c7b1e1f3c8c4d1354"
 [3.1.x] Refs #30165 -- Removed leftover 'u' prefix.

 Backport of bac5777bff8e8d8189193438b5af52f158a3f2a4 from master
 }}}

-- 
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/067.6825b1908169b44ba404e82fcc309a71%40djangoproject.com.

Re: [Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
+--
 Reporter:  Gordon Wrigley  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Migrations  |  Version:  3.0
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Gordon Wrigley):

 Well:
 1: Both managers are declared in exactly the same way so why is one in and
 one out?
 2: They are both actually instances of the Django base manager so they
 have the same setting for use_in_migrations (I presume True)
 3: If you swap the order of the manager declarations around in the source
 code it no longer generates any migration
 4: If you leave the order as is in the linked commit but additionally
 redeclare the objects manager in the concrete model classes it again
 decides no migration is needed

 If this example seems a lil simplistic that's because I was trying to get
 a minimal reproduction, here's one that is structurally equivalent to what
 I actually have:
 https://github.com/tolomea/django-
 tutorial/commit/f247b6ddc5b2b689ec7ec0ede7cb0bc28c99db0c
 Where everything prefixed lib is in a 3rd party library.

 In there you can see that overriding objects on the concrete model causes
 both to be added to the migration.
 Switching the order of the managers around also leads to a migration
 adding both managers to both concrete models.

-- 
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/065.e9055a4ad26371f70f0c31fbd72993a4%40djangoproject.com.

Re: [Django] #3461: DatabaseWrapper should pass through args and kwargs to underlying database adapter

[Django]

#3461: DatabaseWrapper should pass through args and kwargs to underlying 
database
adapter
-+-
 Reporter:  Jack Moffitt |Owner:  Asif
 |  Saifuddin Auvi
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Asif Saifuddin Auvi):

 * needs_better_patch:  0 => 1


Comment:

 needs retarget 3.2 and add missing docs :( hopefully, make this happen
 this time!

-- 
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/091.22a7a633ba6851910eeacc3dd316752c%40djangoproject.com.

Re: [Django] #29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not initialization

[Django]

#29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not
initialization
-+-
 Reporter:  Jon Dufresne |Owner:  Florian
 Type:   |  Apolloner
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"948a874425e7d50a8fa3b6598d9e34a4b861" 948a8744]:
 {{{
 #!CommitTicketReference repository=""
 revision="948a874425e7d50a8fa3b6598d9e34a4b861"
 Fixed #29324 -- Made SECRET_KEY validation lazy (on first access).
 }}}

-- 
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/067.023deca2145efdb1006b3be8ddbb9309%40djangoproject.com.

Re: [Django] #31783: Filtering on a field named `negate` raises a TypeError

[Django]

#31783: Filtering on a field named `negate` raises a TypeError
-+-
 Reporter:  Aaron Kirkbride  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"9c9a3fe1180fc92fbd4c3302dbe0b3e083bf0381" 9c9a3fe1]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c9a3fe1180fc92fbd4c3302dbe0b3e083bf0381"
 Fixed #31783 -- Fixed crash when filtering againts "negate" field.

 Thanks Simon Charette for the initial patch.
 }}}

-- 
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/064.c933758150d1d25d5ae4d7946112f545%40djangoproject.com.