Re: [Django] #32905: Add `nonform` CSS class for non form errors in FormSets

[Django]

#32905: Add `nonform` CSS class for non form errors in FormSets
-+-
 Reporter:  Ties Jan Hefting |Owner:  Ties Jan
 |  Hefting
 Type:  New feature  |   Status:  closed
Component:  Forms|  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:"84400d2e9db7c51fee4e9bb04c028f665b8e7624" 84400d2e]:
 {{{
 #!CommitTicketReference repository=""
 revision="84400d2e9db7c51fee4e9bb04c028f665b8e7624"
 Fixed #32905 -- Added CSS class for non-form errors of formsets.
 }}}

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

Re: [Django] #32929: AsyncRequestFactory.get() ignores data parameter

[Django]

#32929: AsyncRequestFactory.get() ignores data parameter
-+-
 Reporter:  Pochang Lee  |Owner:  Pochang
 |  Lee
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  AsyncTestClient, | Triage Stage:  Accepted
  AsyncRequestFactory|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pochang Lee):

 * has_patch:  0 => 1


Comment:

 Replying to [comment:2 Mariusz Felisiak]:
 > Would you like to prepare a patch? (tests are also required).

 Yes, I have submitted a pull request.

 https://github.com/django/django/pull/14639

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

Re: [Django] #32905: Add `nonform` CSS class for non form errors in FormSets

[Django]

#32905: Add `nonform` CSS class for non form errors in FormSets
-+-
 Reporter:  Ties Jan Hefting |Owner:  Ties Jan
 |  Hefting
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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/065.10f219ae7bf60096765513b23056c874%40djangoproject.com.

Re: [Django] #32929: AsyncRequestFactory.get() ignores data parameter

[Django]

#32929: AsyncRequestFactory.get() ignores data parameter
-+-
 Reporter:  Pochang Lee  |Owner:  Pochang
 |  Lee
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  AsyncTestClient, | Triage Stage:  Accepted
  AsyncRequestFactory|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Andrew Godwin, Carlton Gibson (added)
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report, good catch. I think the following should do the
 trick:

 {{{
 diff --git a/django/test/client.py b/django/test/client.py
 index 4a0b6b45f4..b4c091aa5c 100644
 --- a/django/test/client.py
 +++ b/django/test/client.py
 @@ -547,6 +547,8 @@ class AsyncRequestFactory(RequestFactory):
  follow = extra.pop('follow', None)
  if follow is not None:
  s['follow'] = follow
 +if query_string := extra.pop('QUERY_STRING', None):
 +s['query_string'] = query_string
  s['headers'] += [
  (key.lower().encode('ascii'), value.encode('latin1'))
  for key, value in extra.items()
 }}}

 Would you like to prepare a patch? (tests are also required).

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

Re: [Django] #31596: ForeignKey.validate() should validate using the base manager.

[Django]

#31596: ForeignKey.validate() should validate using the base manager.
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  model form   | 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):

 Replying to [comment:8 Damian Nardelli]:
 > Hello. The documentation for v2.2
 (https://docs.djangoproject.com/en/2.2/topics/db/managers/#using-managers-
 for-related-object-access) is stating that the base manager will be used
 in that version too instead of the default manager. We just saw that this
 fix has been released 12 days ago for v3.2.5, we were wondering when it'll
 be released for v2.2? Thanks!

 It is not a regression, per our backporting policy this means it doesn't
 qualify for a backport to 2.2.x (see
 [https://docs.djangoproject.com/en/stable/internals/release-process/
 Django’s release process] for more details). Moreover Django 2.2 is in
 extended support so it doesn't get bugfixes (except security issues)
 anymore.

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

Re: [Django] #32929: AsyncRequestFactory.get() ignores data parameter

[Django]

#32929: AsyncRequestFactory.get() ignores data parameter
-+-
 Reporter:  Pochang Lee  |Owner:  Pochang
 |  Lee
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  AsyncTestClient, | Triage Stage:
  AsyncRequestFactory|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pochang Lee):

 * version:  3.2 => dev


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

[Django] #32929: AsyncRequestFactory.get() ignores data parameter

[Django]

#32929: AsyncRequestFactory.get() ignores data parameter
-+-
   Reporter:  Pochang|  Owner:  Pochang Lee
  Lee|
   Type:  Bug| Status:  assigned
  Component:  Testing|Version:  3.2
  framework  |   Keywords:  AsyncTestClient,
   Severity:  Normal |  AsyncRequestFactory
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When passing data to AsyncRequestFactory.get(),
 the resulting request.GET always gives an empty QueryDict

 {{{
 >>> request_factory = AsyncRequestFactory()
 >>> request = request_factory.get('/somewhere/', {'var': '100'})
 >>> request.GET
 
 }}}

 while in synchronous

 {{{

 >>> request_factory = RequestFactory()
 >>> request = request_factory.get('/somewhere/', {'var': '100'})
 >>> request.GET
 

 }}}

 This also prevents AsyncClient.get() from passing GET parameters to view
 function.

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

Re: [Django] #25264: Misleading list of options available for manage.py commands

[Django]

#25264: Misleading list of options available for manage.py commands
-+-
 Reporter:  Maxime Lorant|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 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 Yuneui Jeong):

 * owner:  Yuneui Jeong => (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/065.759d90241760c5a91a698d9afe4b7cab%40djangoproject.com.

Re: [Django] #32905: Add `nonform` CSS class for non form errors in FormSets

[Django]

#32905: Add `nonform` CSS class for non form errors in FormSets
-+-
 Reporter:  Ties Jan Hefting |Owner:  Ties Jan
 |  Hefting
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 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 Ties Jan Hefting):

 * 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/065.16dd0fc9a5b537385d76b9adc332b733%40djangoproject.com.

Re: [Django] #32902: CsrfViewMiddleware.process_response()'s csrf_cookie_needs_reset and csrf_cookie_set logic isn't right

[Django]

#32902: CsrfViewMiddleware.process_response()'s csrf_cookie_needs_reset and
csrf_cookie_set logic isn't right
+--
 Reporter:  Chris Jerdonek  |Owner:  Chris Jerdonek
 Type:  Bug |   Status:  assigned
Component:  CSRF|  Version:  dev
 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 Mariusz Felisiak):

 * stage:  Ready for checkin => Accepted


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

Re: [Django] #32910: Different plural forms for some languages.

[Django]

#32910: Different plural forms for some languages.
-+-
 Reporter:  Martin Svoboda   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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 Mariusz Felisiak):

 * stage:  Ready for checkin => Accepted


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

Re: [Django] #32910: Different plural forms for some languages.

[Django]

#32910: Different plural forms for some languages.
-+-
 Reporter:  Martin Svoboda   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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
-+-

Comment (by Mariusz Felisiak):

 Claude, if you think that backport is not necessary, I'd be more than
 happy to merge this to the `main` branch only.

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

Re: [Django] #29865: Add logical XOR support to Q() and QuerySet().

[Django]

#29865: Add logical XOR support to Q() and QuerySet().
-+-
 Reporter:  Griffith Rees|Owner:  Ryan
 |  Heard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  xor  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ryan Heard):

 Replying to [comment:14 Mariusz Felisiak]:
 > Tim asked for starting a discussion on DevelopersMailingList, as far as
 I'm aware we don't have any. Also I'm not sure how widely `XOR` is used in
 queries, I never needed this.
 Mariusz, thank you for taking a look at this. As far I know there is no
 discussion on the mailing list but I welcome one.

 I have needed this in one instance and it would've helped, as one part of
 the operation was a large complex subquery that I would've liked to have
 only once. Unfortunately I found out doing this that my backend, Postgres,
 doesn't even support the XOR operator. It would still be nice to have to
 clean up the code though, and users of MySQL can still benefit from 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/063.965662fccd4224107088e704f9bd5e53%40djangoproject.com.

Re: [Django] #32928: Confirm support for GDAL 3.3.

[Django]

#32928: Confirm support for GDAL 3.3.
--+---
 Reporter:  Mariusz Felisiak  |Owner:  David Smith
 Type:  New feature   |   Status:  assigned
Component:  GIS   |  Version:  4.0
 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 David Smith):

 * owner:  nobody => David Smith
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 I tried to have look at this earlier in the week but ran into all sorts of
 issues trying to get the gis tests to pass. Surprising as I was able to do
 it earlier in the year.

 I'm happy to keep going with this if that would be helpful.

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

Re: [Django] #32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with gdal 3.3.1

[Django]

#32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with
gdal 3.3.1
-+-
 Reporter:  szunami  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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:   => duplicate
 * component:  Uncategorized => Database layer (models, ORM)
 * type:  Uncategorized => Bug


Comment:

 It's a duplicate #32600 where we believe Django is not at fault.

 I also added a separate ticket to confirm support for GDAL 3.3, see
 #32928.

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

[Django] #32928: Confirm support for GDAL 3.3.

[Django]

#32928: Confirm support for GDAL 3.3.
+
   Reporter:  Mariusz Felisiak  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  GIS   |Version:  4.0
   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 |
+
 https://www.osgeo.org/foundation-news/gdal-3-3-0-is-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/050.2f27b4239e0dac95253ddaa22236a390%40djangoproject.com.

Re: [Django] #32600: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU

[Django]

#32600: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU
-+-
 Reporter:  Aapo Rista   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  3.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  MultiPoint,  | Triage Stage:
  MultiLinestring, MultiPolygon, |  Unreviewed
  Segmentation fault, GIS,   |
  GeoDjango  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * resolution:  duplicate => invalid


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

[Django] #32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with gdal 3.3.1

[Django]

#32927: Multi geometries cause Segmentation fault 11 on Macbook with M1 CPU with
gdal 3.3.1
-+
   Reporter:  szunami|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |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  |
-+
 I am able to exactly reproduce the issue described here:
 https://code.djangoproject.com/ticket/32600 , however I am using gdal
 3.3.1 which is the current stable version of gdal supplied via homebrew.

 I'll note that gdal 3.3.1 is not officially supported (cf
 https://docs.djangoproject.com/en/3.2/ref/contrib/gis/install/geolibs/).
 However, homebrew does not make it easy to install older versions of
 tools.

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

Re: [Django] #32910: Different plural forms for some languages.

[Django]

#32910: Different plural forms for some languages.
-+-
 Reporter:  Martin Svoboda   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:8 Claude Paroz]:
 > I don't think the backports are needed, isn't this only an optimization?

 I assumed that e3e48b00127c09eafe6439d980a82fc5c591b673 broke the previous
 behavior for users using multiple contrib apps, but I'm not an expert in
 this area.

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

Re: [Django] #32910: Different plural forms for some languages.

[Django]

#32910: Different plural forms for some languages.
-+-
 Reporter:  Martin Svoboda   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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
-+-

Comment (by Claude Paroz):

 I don't think the backports are needed, isn't this only an optimization?

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

Re: [Django] #29865: Add logical XOR support to Q() and QuerySet().

[Django]

#29865: Add logical XOR support to Q() and QuerySet().
-+-
 Reporter:  Griffith Rees|Owner:  Ryan
 |  Heard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  xor  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:12 Nick Pope]:
 > I'd missed that this was triaged as "Someday/Maybe", but I'm accepting
 based on the fact that we have a plausible implementation in
 [https://github.com/django/django/pull/14480 this PR].

 Tim asked for starting a discussion on DevelopersMailingList, as far as
 I'm aware we don't have any. Also I'm not sure how widely `XOR` is used in
 queries, I never needed 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/063.33b1fa599a537a7b3ee3d63fd82bea7c%40djangoproject.com.

Re: [Django] #32910: Different plural forms for some languages.

[Django]

#32910: Different plural forms for some languages.
-+-
 Reporter:  Martin Svoboda   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 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):

 * has_patch:  0 => 1
 * type:  Cleanup/optimization => Bug


Comment:

 [https://github.com/django/django/pull/14636 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/071.7508861ec21cf7abf215334843981bf9%40djangoproject.com.

Re: [Django] #24462: Add a new QuerySet operation to use current results as a subquery

[Django]

#24462: Add a new QuerySet operation to use current results as a subquery
-+-
 Reporter:  trosos   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  distinct order_by| Triage Stage:  Accepted
  subquery   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Paolo Melchiorre):

 * cc: Paolo Melchiorre (added)


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

Re: [Django] #29865: Add logical XOR support to Q() and QuerySet(). (was: Add XOR for use in Q Queries)

[Django]

#29865: Add logical XOR support to Q() and QuerySet().
-+-
 Reporter:  Griffith Rees|Owner:  Ryan
 |  Heard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  xor  | Triage Stage:  Accepted
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/063.f0cdfb8b64f160492a8e7af7af449297%40djangoproject.com.

Re: [Django] #29865: Add XOR for use in Q Queries

[Django]

#29865: Add XOR for use in Q Queries
-+-
 Reporter:  Griffith Rees|Owner:  Ryan
 |  Heard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  xor  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * stage:  Someday/Maybe => Accepted


Comment:

 I'd missed that this was triaged as "Someday/Maybe", but I'm accepting
 based on the fact that we have a plausible implementation in
 [https://github.com/django/django/pull/14480 this 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/063.44b1afdd5ad51575d5659328048dbcac%40djangoproject.com.

Re: [Django] #32910: Different plural forms for some languages. (was: Contrib apps: Different plural forms for Slovak (SK))

[Django]

#32910: Different plural forms for some languages.
-+-
 Reporter:  Martin Svoboda   |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  2.2
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned


Comment:

 There are more affected languages I will fetch translations from Transifex
 and prepare 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/071.a989e282ab2169008d61aed8e3686589%40djangoproject.com.

Re: [Django] #32910: Contrib apps: Different plural forms for Slovak (SK)

[Django]

#32910: Contrib apps: Different plural forms for Slovak (SK)
-+-
 Reporter:  Martin Svoboda   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  2.2
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * version:  3.2 => 2.2
 * stage:  Accepted => Ready for checkin


Comment:

 I think we should update plural forms for all languages and backport this
 changes.

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

Re: [Django] #21936: Allow delete to provide a success message through a mixin.

[Django]

#21936: Allow delete to provide a success message through a mixin.
-+-
 Reporter:  david.fischer.ch@…   |Owner:  Demetris
 |  Stavrou
 Type:  New feature  |   Status:  closed
Component:  contrib.messages |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  mixin| 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 Carlton Gibson ):

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


Comment:

 In [changeset:"3a45fea0832c5910acee6e0d29f230f347a50462" 3a45fea0]:
 {{{
 #!CommitTicketReference repository=""
 revision="3a45fea0832c5910acee6e0d29f230f347a50462"
 Fixed #21936 -- Allowed DeleteView to work with custom Forms and
 SuccessMessageMixin.

 Thanks to Mariusz Felisiak for review.

 Co-authored-by: Demetris Stavrou 
 Co-authored-by: Caroline Simpson 
 }}}

-- 
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/084.21d34f4ce8de2db8cad33e46da9ee577%40djangoproject.com.

Re: [Django] #21936: Allow delete to provide a success message through a mixin.

[Django]

#21936: Allow delete to provide a success message through a mixin.
-+-
 Reporter:  david.fischer.ch@…   |Owner:  Demetris
 |  Stavrou
 Type:  New feature  |   Status:  assigned
Component:  contrib.messages |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  mixin| 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/084.ae4d6939e266c03d05ecf8bb3be65909%40djangoproject.com.

Re: [Django] #470: Add Field.db_default for defining database defaults

[Django]

#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  Ian Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:  sql schema   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/061.e2946a8e48e5db91ee5abae9cf75ea42%40djangoproject.com.