Re: [Django] #31891: Remove cached value of reverse side of 020 relation when updating attname. (was: Inconsistent related field cache invalidation)

[Django]

#31891: Remove cached value of reverse side of 020 relation when updating 
attname.
-+-
 Reporter:  Josh |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  orm,related,onetoone   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for this ticket, I can see inconsistency but I'm not sure if it's
 feasible. Tentatively accepting for investigation.

 The main difference is that `profile.user = b` uses one-to-one descriptors
 and has access to both side instances, on the other hand `profile.user_id
 = b.id` uses a deferred attribute.

 > This is a contrived example but the real use-case was cloning a model
 instance.

 This is probably fixed by #31863.

-- 
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.8f6019da6d7fdf360aaa26eecfca34f5%40djangoproject.com.

Re: [Django] #31881: Raise Index name limit for postgres

[Django]

#31881: Raise Index name limit for postgres
-+-
 Reporter:  Jarek Glowacki   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  postgres index   | Triage Stage:
  max_name_length|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => needsinfo


-- 
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.3792debde4d41f9242254c35f55d508d%40djangoproject.com.

Re: [Django] #31893: Django admin panel has weird look

[Django]

#31893: Django admin panel has weird look
-+-
 Reporter:  AlanTheKnight|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  admin, admin panel,  | Triage Stage:
  css, bug, issue|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I cannot reproduce this issue, it looks that `nav_sidebar.css` is not
 loaded properly. Please use one of
 [https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
 support channels].

-- 
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.4097389253d60e91114a53c1cf516560%40djangoproject.com.

Re: [Django] #31891: Inconsistent related field cache invalidation

[Django]

#31891: Inconsistent related field cache invalidation
-+-
 Reporter:  Josh |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  orm,related,onetoone   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Josh):

 * component:  Uncategorized => Database layer (models, ORM)


-- 
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.83429ad7289475b4fee08e65f1571394%40djangoproject.com.

Re: [Django] #31891: Inconsistent related field cache invalidation

[Django]

#31891: Inconsistent related field cache invalidation
-+-
 Reporter:  Josh |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  orm,related,onetoone   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Josh):

 * type:  Uncategorized => Bug


-- 
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.6ca5b5940e1f5c85ac9a3d9788407a0c%40djangoproject.com.

Re: [Django] #31890: Use keyring for setting SECRET_KEY. (was: if SECRET_KEY is not set and "keyring" is installed, use "keyring" to get_or_create a secret key)

[Django]

#31890: Use keyring for setting SECRET_KEY.
-+--
 Reporter:  Thomas Grainger  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  3.1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => wontfix
 * type:  Uncategorized => New feature
 * component:  Uncategorized => Core (Other)


Comment:

 Thanks for this ticket, however there are many possible solutions and I
 don't think that we should include a few lines hook to recommend any of
 them. You can start a discussion on DevelopersMailingList if you don't
 agree.


 I've also never used `keyring`, but that's only a comment, not an argument
 for closing this ticket.

-- 
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.878ab906dee787bad70620bfa78c98dc%40djangoproject.com.

Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.

[Django]

#20024: QuerySet.exclude() does not work with lists containing a 'None' element.
-+-
 Reporter:  stillwater.ke@…  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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 Simon Charette):

 * owner:  (none) => Simon Charette
 * 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/081.51e8fb850c6f785abd5dbdb4d5c2c724%40djangoproject.com.

Re: [Django] #31892: Added release notes about removing "type" attribute from rendered

[Django]

#31892: Added release notes about removing "type" attribute from rendered

Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.

[Django]

#20024: QuerySet.exclude() does not work with lists containing a 'None' element.
-+-
 Reporter:  stillwater.ke@…  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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 felixxm):

 * has_patch:  1 => 0


-- 
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/081.817bde8b8d9873bd223d3d4461eacd9c%40djangoproject.com.

Re: [Django] #31884: nav-sidebar ui optimization

[Django]

#31884: nav-sidebar ui optimization
-+-
 Reporter:  007  |Owner:  nobody
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:
 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 007):

 rollback to button and add blur() when mouseup

-- 
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.56893e87a880594a9c9ab45aa6eb7fe8%40djangoproject.com.

Re: [Django] #27679: Document that empty formsets display min_num+extra forms

[Django]

#27679: Document that empty formsets display min_num+extra forms
-+-
 Reporter:  Lorenzo Peña |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Smith):

 * owner:  nobody => David Smith
 * status:  new => assigned
 * 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/066.91d40b00c73467fd619f3da9bef3ef23%40djangoproject.com.

Re: [Django] #31892: [Undocumented][Widgets][Media] render_js (was: [Regression][Widgets][Media] render_js)

[Django]

#31892: [Undocumented][Widgets][Media] render_js
---+--
 Reporter:  Buky   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

-- 
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.5a8057b226cde7cb0f327d87e3b464ae%40djangoproject.com.

Re: [Django] #31892: [Regression][Widgets][Media] render_js

[Django]

#31892: [Regression][Widgets][Media] render_js
---+--
 Reporter:  Buky   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Buky):

 Great idea. That will be useful for other packages who deal with
 statistics.

-- 
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.f1cc13bd33b151ea878d00696286e44d%40djangoproject.com.

[Django] #31893: Django admin panel has weird look

[Django]

#31893: Django admin panel has weird look
-+-
   Reporter: |  Owner:  nobody
  AlanTheKnight  |
   Type:  Bug| Status:  new
  Component: |Version:  3.1
  contrib.admin  |   Keywords:  admin, admin panel,
   Severity:  Normal |  css, bug, issue
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 My admin panel in any project looks like that:
 https://i.stack.imgur.com/B1QIa.png
 My problem copies this stackoverflow question with no answer:
 https://stackoverflow.com/questions/63398552/django-admin-look-strange
 Both me and my friend have this issue and also our server with Ubuntu
 does.
 How can I fix it? Is it my fault or it's Django bug?

-- 
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/056.0e6beaa1d6713d172a4882743b0c5df0%40djangoproject.com.

Re: [Django] #31892: [Regression][Widgets][Media] render_js

[Django]

#31892: [Regression][Widgets][Media] render_js
---+--
 Reporter:  Buky   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Jon Dufresne):

 * has_patch:  0 => 1


Comment:

 I'm open to including a mention in release notes. Here is a go at that:
 https://github.com/django/django/pull/13312

 Let me know if that would have helped.

-- 
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.2d1cfce97c6a1f2b49609a2e6e683b6e%40djangoproject.com.

Re: [Django] #31892: [Regression][Widgets][Media] render_js

[Django]

#31892: [Regression][Widgets][Media] render_js
---+--
 Reporter:  Buky   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.1
 Severity:  Normal |   Resolution:
 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 Buky):

 it's just breaking news tests in django-pipeline and I don't find any
 information about this in the release notes

 Thank you for the quick answer, I will do what is necessary to update the
 package

-- 
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.9e8f409c4689dd331225214824a606b9%40djangoproject.com.

Re: [Django] #31892: [Regression][Widgets][Media] render_js

[Django]

#31892: [Regression][Widgets][Media] render_js
---+--
 Reporter:  Buky   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.1
 Severity:  Normal |   Resolution:
 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 Jon Dufresne):

 This behavior intentionally changed in
 e703b93a656b78b9b444bb3a9980e305ed002a70 for ticket #31080. As noted in
 that ticket, specifying the default type is not recommend.

 From https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script
 #attr-type

 > Omitted or a JavaScript MIME type: This indicates the script is
 JavaScript. The HTML5 specification urges authors to omit the attribute
 rather than provide a redundant MIME type.

 From https://html.spec.whatwg.org/multipage/scripting.html#the-script-
 element

 > Authors should omit the type attribute instead of redundantly setting
 it.

 Beyond simply being different, how is this causing an issue in practice?

 If there is no practical issue then I think we should stick with the
 smaller, simplified form recommended by upstream authorities.

-- 
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.94255eae8554498976ab471a3c3ba0a9%40djangoproject.com.

Re: [Django] #31667: Avoid passing NULL to the IN lookup

[Django]

#31667: Avoid passing NULL to the IN lookup
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam Sołtysik):

 There is also an inconsistency between `In` and `RelatedIn` lookups. The
 latter seems to be working consistenly with this change (details in
 #20024).

-- 
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.5a8735e090620f48be4c11575877f960%40djangoproject.com.

Re: [Django] #31892: [Regression][Widgets][Media] render_js

[Django]

#31892: [Regression][Widgets][Media] render_js
---+--
 Reporter:  Buky   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Forms  |  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by Buky:

Old description:

> Hi,
>
> For Django in 3.0 and before when **Media** is used (forms.widgets.py),
> the method **render_js** will produce:
> {{{
> 
> }}}
>
> but in Django 3.1 we get:
> {{{
> 
> }}}
>

> This change is uncovered in Django 3.1 release
> notes(https://docs.djangoproject.com/en/3.1/releases/3.1/). Does it a
> regression?
>
> **Django > 3.1:**
> {{{
> def render_js(self):
> return [
> format_html(
> '',
> self.absolute_path(path)
> ) for path in self._js
> ]
> }}}

New description:

 Hi,

 For Django in 3.0 and before when **Media** is used (forms.widgets.py),
 the method **render_js** will produce:
 {{{
 
 }}}

 but in Django 3.1 we get:
 {{{
 
 }}}


 This change is uncovered in Django 3.1 release notes
 (https://docs.djangoproject.com/en/3.1/releases/3.1/). Does it a
 regression?

 **Media.render_js before Django 3.1:**
 {{{
 def render_js(self):
 return [
 format_html(
 '',
 self.absolute_path(path)
 ) for path in self._js
 ]
 }}}

--

-- 
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.e77c324c1a4ff4a736f1961e53e50200%40djangoproject.com.

[Django] #31892: [Regression][Widgets][Media] render_js

[Django]

#31892: [Regression][Widgets][Media] render_js
-+
   Reporter:  Buky   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Forms  |Version:  3.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Hi,

 For Django in 3.0 and before when **Media** is used (forms.widgets.py),
 the method **render_js** will produce:
 {{{
 
 }}}

 but in Django 3.1 we get:
 {{{
 
 }}}


 This change is uncovered in Django 3.1 release
 notes(https://docs.djangoproject.com/en/3.1/releases/3.1/). Does it a
 regression?

 **Django > 3.1:**
 {{{
 def render_js(self):
 return [
 format_html(
 '',
 self.absolute_path(path)
 ) for path in self._js
 ]
 }}}

-- 
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/050.cae91ca80bd2b53709dfb02b9e2cd60b%40djangoproject.com.

Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.

[Django]

#20024: QuerySet.exclude() does not work with lists containing a 'None' element.
-+-
 Reporter:  stillwater.ke@…  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Sołtysik):

 * owner:  Adam Sołtysik => (none)
 * status:  assigned => new


Comment:

 It would be best to make the behaviour of `In` lookup consistent with
 `RelatedIn`. Sadly, I wasn't able to understand how the latter works. So
 my patch currently crashes with window functions, and it also crashes with
 `OuterRef` due to #31714. As much as I'd like to finish this, I don't have
 enough time and knowledge to look into it further. If anyone comes up with
 a solution, feel free to claim this issue.

-- 
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/081.bf668e0ad7f3abdf3354b08ed6cdba28%40djangoproject.com.

Re: [Django] #31890: if SECRET_KEY is not set and "keyring" is installed, use "keyring" to get_or_create a secret key

[Django]

#31890: if SECRET_KEY is not set and "keyring" is installed, use "keyring" to
get_or_create a secret key
-+--
 Reporter:  Thomas Grainger  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  3.1
 Severity:  Normal   |   Resolution:
 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 Adam (Chainz) Johnson):

 The keyring module you refer to is: https://pypi.org/project/keyring/

 I've not worked on any projects using the system keyring like this. It
 looks neat but I think some evidence of use in the Django ecosystem via a
 third party package would be warranted before merging to core.

-- 
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.1b80354e2f46123a767e9c31630ede51%40djangoproject.com.

Re: [Django] #20024: QuerySet.exclude() does not work with lists containing a 'None' element.

[Django]

#20024: QuerySet.exclude() does not work with lists containing a 'None' element.
-+-
 Reporter:  stillwater.ke@…  |Owner:  Adam
 |  Sołtysik
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Sołtysik):

 * has_patch:  0 => 1


Comment:

 I've created a
 
[https://github.com/adamsol/django/commit/f50e315ce315ead117bfe4335a9fda758e88ae6f
 patch]. No PR yet, though, because one test fails:
 `WindowFunctionTests.test_window_expression_within_subquery`. SQL doesn't
 support filtering by window functions, so I guess the code should be
 corrected to use another subquery (or maybe an `EXISTS` query).
 Unfortunately I don't know how to write this without using QuerySet
 utilities.

 As for `RelatedIn`, the things are weird here. It seems this case is
 handled differently and already works correctly, and worked even before
 #31667 (`test_ticket20024_related_in`). It was probably fixed in #13815
 long ago. There is `IS NOT NULL` in the subquery, actually there are two
 next to each other. One is coming from `split_exclude()` (called in
 `build_filter()`), but the other one -- I couldn't find. Also, what looks
 like another thing to take a closer look at -- there is `NOT IN (None)`
 instead of `NOT IN (NULL)` in the SQL for the first query in that test,
 when the `rhs.discard(None)` line is removed.

-- 
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/081.11339f62a20dc73d3ff39538a05f49de%40djangoproject.com.