Re: [Django] #26056: ArrayField does not work with ValueListQuerySet

[Django]

#26056: ArrayField does not work with ValueListQuerySet
--+
 Reporter:  Przemek   |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  dev
 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
--+

Comment (by Simon Charette):

 Now that #32776 landed in the main branch this issue should be
 straightforward to fix adjusting the `Overlap.lookup`
 
[https://github.com/django/django/blob/6a5ef557f80a8eb6a758ebe99c8bb477ca47459e/django/contrib/postgres/lookups.py#L17-L19
 lookup] by wrapping a `QuerySet` instance into an `ArraySubquery`.

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

Re: [Django] #32723: Add a GitHub action to run the Sphinx linkcheck builder.

[Django]

#32723: Add a GitHub action to run the Sphinx linkcheck builder.
-+-
 Reporter:  Nick Pope|Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  linkcheck, github,   | Triage Stage:
  action |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Nick Pope):

 Replying to [comment:3 Sarah Abderemane]:
 > [https://github.com/sphinx-doc/sphinx/issues/6525​ sphinx-
 doc/sphinx#6525] has been closed and merged in the last release of sphinx.
 Does the triage stage will be updated to ''accepted'' according to this ?

 I'll need to have a look as the entire proposal wasn't implemented with
 some work being left for a follow-up.

 We'll also need to wait for any changes to be released.

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

Re: [Django] #32723: Add a GitHub action to run the Sphinx linkcheck builder.

[Django]

#32723: Add a GitHub action to run the Sphinx linkcheck builder.
-+-
 Reporter:  Nick Pope|Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  linkcheck, github,   | Triage Stage:
  action |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Sarah Abderemane):

 [https://github.com/sphinx-doc/sphinx/issues/6525​ sphinx-doc/sphinx#6525]
 has been closed and merged in the last release of sphinx. Does the triage
 stage will be updated to ''accepted'' according to this ?

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

Re: [Django] #26056: ArrayField does not work with ValueListQuerySet

[Django]

#26056: ArrayField does not work with ValueListQuerySet
--+
 Reporter:  Przemek   |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  dev
 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
--+

Comment (by Peter Law):

 For anyone who ends up searching for this, the failure (as of 2.2 and
 possibly earlier) is a `ProgrammingError` from the database rather than
 the `TypeError` mentioned above.

 The workaround mentioned in
 https://github.com/django/django/pull/7838#issuecomment-337223376
 continues to work:
 {{{#!python
 A.objects.filter(
 array_field__overlap=models.Func(
 B.objects.values('pk'),
 function='array',
 ),
 )
 }}}

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

Re: [Django] #32904: Tighten up the regular expression used by parse_time to accept less 'invalid' options.

[Django]

#32904: Tighten up the regular expression used by parse_time to accept less
'invalid' options.
--+
 Reporter:  Keryn Knight  |Owner:  Abhyudai
 Type:  Bug   |   Status:  assigned
Component:  Utilities |  Version:  dev
 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 Abhyudai):

 * owner:  nobody => Abhyudai
 * 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/067.45faae7b7e2c7b724b6cd81fcd150579%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mateo Radman):

 * owner:  nobody => Mateo Radman
 * 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.1eb8c8758daf2de9fae4dbaab0e04e76%40djangoproject.com.

Re: [Django] #32899: enhance JSONResponse safe=True kwarg docs

[Django]

#32899: enhance JSONResponse safe=True kwarg docs
-+-
 Reporter:  Thomas Grainger  |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.2
 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 Hasan Ramezani):

 * needs_better_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/067.412ef0c578e48325372b8a004665d491%40djangoproject.com.

Re: [Django] #32840: Micro-optimisation possibility in Field.get_col

[Django]

#32840: Micro-optimisation possibility in Field.get_col
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 Keryn Knight):

 * needs_better_patch:  0 => 1


Comment:

 Updating state based on initial review on the PR.

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

Re: [Django] #32907: Allow duplicate headers while sending email

[Django]

#32907: Allow duplicate headers while sending email
+--
 Reporter:  Shrawan Poudel  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Core (Mail) |  Version:  3.2
 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 Mariusz Felisiak):

 Thanks Adam for extra details.

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

Re: [Django] #32907: Allow duplicate headers while sending email

[Django]

#32907: Allow duplicate headers while sending email
+--
 Reporter:  Shrawan Poudel  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Core (Mail) |  Version:  3.2
 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
+--
Changes (by Mariusz Felisiak):

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


Comment:

 IMO there is no need for a new API, you should be able to pass multiple
 values in a single string, e.g. `'X-SES-MESSAGE-TAGS ': 'uid=uid, sub=sub,
 dom=dom'`, see also TicketClosingReasons/UseSupportChannels for ways to
 get help.

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

Re: [Django] #32907: Allow duplicate headers while sending email

[Django]

#32907: Allow duplicate headers while sending email
+--
 Reporter:  Shrawan Poudel  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Mail) |  Version:  3.2
 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 Johnson):

 I checked the RFC (
 https://datatracker.ietf.org/doc/html/rfc5322#section-3.6 ) and only
 certain email headers are listed as allowed to occur more than one time.
 The SES header does not appear there.

 I checked the SES documentation and it recommends passing multiple tags in
 one header, separated by commas. This may be what you want to do:
 https://docs.aws.amazon.com/ses/latest/DeveloperGuide/event-publishing-
 send-email.html#event-publishing-using-ses-headers

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

[Django] #32907: Allow duplicate headers while sending email

[Django]

#32907: Allow duplicate headers while sending email
--+
   Reporter:  Shrawan Poudel  |  Owner:  nobody
   Type:  New feature | Status:  new
  Component:  Core (Mail) |Version:  3.2
   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   |
--+
 Currently, for sending custom headers while sending email we create up a
 dict and pass it to the **EmailMessage**

 for example:

 {{{
 from django.core.mail import EmailMessage

 email = EmailMessage(
 'Example Subject',
 'Here is the message.',
 'f...@example.com',
 to=['t...@example.com'],
 headers={'x-unique-id':  'unique_id',
  'X-email-id-trace ':'trace_id'},
 )
 email.send(fail_silently=False)
 }}}

 Since we pass **headers** using a **dict** i need to create up unique keys
 for headers so this is the reason i am not being able to send duplicate
 email headers,
 i came across this case when i tried to implement AWS SES Logging where i
 need to send multiple headers of same name like,


 {{{
 headers={'X-SES-CONFIGURATION-SET':  'emailLogs',
  'X-SES-MESSAGE-TAGS ':'uid=uid',
'X-SES-MESSAGE-TAGS':'sub=sub',
 'X-SES-MESSAGE-TAGS':'dom=dom'},

 }}}

 There are/can be multiple workarounds to deal with it but i will be happy
 to see this implemented in django core itself

 I am happy to work on it if it needs to be implemented as a new feature to
 allow duplicate headers name

-- 
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/051.eaf61cca9e82bf63de94d3bd8492180b%40djangoproject.com.

[Django] #32906: Explain JSONBAgg benefit

[Django]

#32906: Explain JSONBAgg benefit
+
   Reporter:  Claude Paroz  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  dev
   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 |
+
 When reading current Django docs and tests, I can't see how `JSONBAgg` has
 any advantage over `ArrayAgg`. It would be great to add both in docs and
 tests examples showing benefits/differences between  `ArrayAgg` and
 `JSONBAgg`, if any.

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

Re: [Django] #32892: Optimisation for parse_datetime by preferring datetime.fromisoformat for well-formed values.

[Django]

#32892: Optimisation for parse_datetime by preferring datetime.fromisoformat for
well-formed values.
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  dev
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"f35ab74752adb37138112657c1bc8b91f50e799b" f35ab74]:
 {{{
 #!CommitTicketReference repository=""
 revision="f35ab74752adb37138112657c1bc8b91f50e799b"
 Fixed #32892 -- Optimized django.utils.dateparse functions by using
 fromisoformat().
 }}}

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

Re: [Django] #32891: runserver serve static files cached in debug

[Django]

#32891: runserver serve static files cached in debug
-+-
 Reporter:  TZanke   |Owner:  TZanke
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  3.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by TZanke):

 Hello Carlton,

 my (and my coworkers) expected behavior, with DEBUG=True, was a non-cached
 js/css file. So while developing, new colleges always struggle debugging,
 cause "my files does not get refreshed, but debug is on! Help me!". Yeah
 no problem, we always use the "disable browser cache" but maybe we are not
 alone with this problem, and this could easily be fixed. Cause `static.py
 serve` only is used in Debug mode by Django.

 But we will respect the decision made.

 > If you really wanted to add no cache headers you could do so in a
 middleware, but I don't think it's appropriate for projects in general.

 I've tried, but its not working. `static.py serve` is called within the
 'StaticFilesHandler', skipping the Middlewares from `BaseHandler`.
 See:
 
https://github.com/django/django/blob/main/django/contrib/staticfiles/handlers.py#L53
 No super call, no Middleware execution.

 But keep in mind, i am not able to test with a new Django version right
 now. Maybe i am wrong 'just lookin at github'. But in Django 1.11
 Middlewares are skipped.
 (And yees, we are are nearly finished with Python3 conversion, so Django
 2/3 is coming...soon ;)

 Best regards
 Tobias

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

Re: [Django] #32891: runserver serve static files cached in debug

[Django]

#32891: runserver serve static files cached in debug
-+-
 Reporter:  TZanke   |Owner:  TZanke
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  3.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 Hi Tobias — Welcome aboard!

 > Possible fix: Add add_never_cache_headers to the static.py serve method

 I don't think this is the right approach. As far as I can see the browser
 behaviour is correct and as desired, serving static assets from the
 browser cache when possible.

 When working on a file this behaviour can be undesired. For that all the
 browsers allow disabling the caches (at least while the dev tools are
 open) by accessing the settings (normally via the little cog or hamburger
 menu on in the dev tools, or via the Develop menu in Safari). If you check
 this static assets are fetched on each request.

 If you **really** wanted to add no cache headers you could do so in a
 middleware, but I don't think it's appropriate for projects in general.

 I hope that makes sense.

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

Re: [Django] #32904: Tighten up the regular expression used by parse_time to accept less 'invalid' options.

[Django]

#32904: Tighten up the regular expression used by parse_time to accept less
'invalid' options.
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Utilities |  Version:  dev
 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
--+

Comment (by Nick Pope):

 Replying to [comment:2 Mariusz Felisiak]:
 > IMO the main issue is that `$` is missing.

 I came to the same conclusion:
 https://github.com/django/django/pull/14582#discussion_r664075337

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

Re: [Django] #32892: Optimisation for parse_datetime by preferring datetime.fromisoformat for well-formed values.

[Django]

#32892: Optimisation for parse_datetime by preferring datetime.fromisoformat for
well-formed values.
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  dev
 Severity:  Normal   |   Resolution:
 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 Mariusz Felisiak):

 * 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/067.8adde6f790ee1e2e14db7555f3188c4a%40djangoproject.com.

Re: [Django] #32904: Tighten up the regular expression used by parse_time to accept less 'invalid' options.

[Django]

#32904: Tighten up the regular expression used by parse_time to accept less
'invalid' options.
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Utilities |  Version:  dev
 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 Mariusz Felisiak):

 * type:  Cleanup/optimization => 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/067.ac68b17fe95a3fae369d3a330f74b7b8%40djangoproject.com.

Re: [Django] #32904: Tighten up the regular expression used by parse_time to accept less 'invalid' options.

[Django]

#32904: Tighten up the regular expression used by parse_time to accept less
'invalid' options.
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  dev
 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 Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 IMO the main issue is that `$` is missing.

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

Re: [Django] #32776: Support Array subqueries on PostgreSQL

[Django]

#32776: Support Array subqueries on PostgreSQL
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  dev
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"a06b977a91f043c509df781670fb4cf35cb437b7" a06b977a]:
 {{{
 #!CommitTicketReference repository=""
 revision="a06b977a91f043c509df781670fb4cf35cb437b7"
 Fixed #32776 -- Added support for Array subqueries on 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.6ee0b4ecd5c64534d495cabba8554a8a%40djangoproject.com.