Re: [Django] #24522: Add test command option to run tests in a random order

[Django]

#24522: Add test command option to run tests in a random order
-+-
 Reporter:  Andreas Savvides |Owner:  Chris
 |  Jerdonek
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  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/068.021f2b0054e95714eadd6fe9f0463366%40djangoproject.com.

Re: [Django] #32908: Add support for QuerySet.select_for_update()'s skip_locked options on MariaDB 10.6+

[Django]

#32908: Add support for QuerySet.select_for_update()'s skip_locked options on
MariaDB 10.6+
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (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
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"77b88fe621bb7828535a4c4cf37d9d4ac01b146b" 77b88fe6]:
 {{{
 #!CommitTicketReference repository=""
 revision="77b88fe621bb7828535a4c4cf37d9d4ac01b146b"
 Fixed #32908 -- Allowed select_for_update(skip_locked) on MariaDB 10.6+.
 }}}

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

Re: [Django] #32499: simplify_regex only removes some metacharacters from regex patterns

[Django]

#32499: simplify_regex only removes some metacharacters from regex patterns
-+-
 Reporter:  Rohith P R   |Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admindocs|  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 Nick Pope):

 * 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/066.0b97ac9b66988264a41d9af67ce607cd%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:  new
Component:  Migrations   |  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:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  fixed =>


Comment:

 When adding a PR, the correct action is to check "Has patch" rather than
 close the ticket. See
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/ Triaging tickets] and the "According to the ticket's flags, the
 next step(s) to move this issue forward are:" section of each open 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/068.e853c34ca051233104ead7fcf95d7fff%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:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 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):

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


Comment:

 [https://github.com/django/django/pull/14607 PR] is ready. Let me know if
 you have any suggestions regarding phrasing the questions.

-- 
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.70e78e0eab32d130f6a6fa6f48345ae8%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):

 * has_patch:  0 => 1


Old description:

> Forms add the `nonfield` CSS class for non field errors in ErrorClass
> instances. This is documented in a section on
> [https://docs.djangoproject.com/en/dev/topics/forms/#rendering-form-
> error-messages rendering form error messages]. Similarly, in FormSets I'd
> expect to see the `nonform` CSS class added for non form errors. This
> would allow a custom ErrorClass to make a distinction in form field
> errors, non field errors (forms) and non form errors (FormSets) when
> rendering error messages. Therefore I'd suggest to add this `nonform` CSS
> class and document it for developers to use.

New description:

 Forms add the `nonfield` CSS class for non field errors in ErrorList
 instances. This is documented in a section on
 [https://docs.djangoproject.com/en/dev/topics/forms/#rendering-form-error-
 messages rendering form error messages]. Similarly, in FormSets I'd expect
 to see the `nonform` CSS class added for non form errors. This would allow
 a custom ErrorList to make a distinction in form field errors, non field
 errors (forms) and non form errors (FormSets) when rendering error
 messages. Therefore I'd suggest to add this `nonform` CSS class and
 document it for developers to use.

--

Comment:

 [https://github.com/django/django/pull/14608 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/065.787dfffc0c4b64014824b630103593fd%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:  closed
Component:  Database layer   |  Version:  dev
  (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
-+-
Changes (by Mariusz Felisiak):

 * 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.658c2699759a16fd2f204f7307790652%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:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 GitHub ):

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


Comment:

 In [changeset:"5013798fe9a87b693ddb5589a8a408a04a873781" 5013798f]:
 {{{
 #!CommitTicketReference repository=""
 revision="5013798fe9a87b693ddb5589a8a408a04a873781"
 Fixed #32840 -- Optimized Field.get_col().

 get_col() used "self" as "output_field" when it was not given, and
 unnecessarily compared "self" to "self".

 Co-authored-by: Chris Jerdonek 
 Co-authored-by: Mariusz Felisiak 
 }}}

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

Re: [Django] #32903: admin page in Google-Chrome does not show the columns like in Firefox or Chrome

[Django]

#32903: admin page in Google-Chrome does not show the columns like in Firefox or
Chrome
---+--
 Reporter:  elnikej|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  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 elnikej):

 I did some more tests with CTRL+F5 and loading different project.
 - in Django3.2 after refresh it looks good in all Browsers
 - if I open a Django2.2.24 admin page and after that Django3.2 admin page
 I have the same situation again
 - You are right some css is in Browser Cache

 Thanks for sorting that out.

 BR Jens

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

[Django] #32911: django.forms.BaseFormSet.is_valid does not respect TOTAL_FORM_COUNT

[Django]

#32911: django.forms.BaseFormSet.is_valid does not respect TOTAL_FORM_COUNT
-+-
   Reporter: |  Owner:  nobody
  lorenzomorandini   |
   Type:  Bug| Status:  new
  Component:  Forms  |Version:  3.2
   Severity:  Normal |   Keywords:  form, formset
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 #29113 (ticket) does not respect TOTAL_FORM_COUNT variable anymore when
 validating a formset.

 Before:
 {{{#!python
 def is_valid(self):
 """Return True if every form in self.forms is valid."""
 if not self.is_bound:
 return False
 # We loop over every form.errors here rather than short circuiting on
 the
 # first failure to make sure validation gets triggered for every form.
 forms_valid = True
 # This triggers a full clean.
 self.errors
 for i in range(0, self.total_form_count()):
 form = self.forms[i]
 if self.can_delete and self._should_delete_form(form):
 # This form is going to be deleted so any of its errors
 # shouldn't cause the entire formset to be invalid.
 continue
 forms_valid &= form.is_valid()
 return forms_valid and not self.non_form_errors()
 }}}

 After:
 {{{#!python
 def is_valid(self):
 """Return True if every form in self.forms is valid."""
 if not self.is_bound:
 return False
 # Accessing errors triggers a full clean the first time only.
 self.errors
 # List comprehension ensures is_valid() is called for all forms.
 # Forms due to be deleted shouldn't cause the formset to be invalid.
 forms_valid = all([
 form.is_valid() for form in self.forms
 if not (self.can_delete and self._should_delete_form(form))
 ])
 return forms_valid and not self.non_form_errors()
 }}}

 The previous version used `total_form_count()` while the new version just
 iterates over `self.forms`.
 This broke a view in my case where I had:
 * a formset with some forms rendered in a page
 * the last form of the formset was hidden and did NOT count in
 `TOTAL_FORM_COUNT`

 Before the last form was ignored (and correctly not submitted), now it
 gets validated (even if it will not be submitted).
 Depending on the `can_delete` param of the formset, this issue could lead
 to two outcomes:
 * `can_delete=True`: `_should_delete_form()` throws `AttributeError:
  has no attribute cleaned_data`
 * `can_delete=False`: formset is invalid because of the last form

 I consider it a bug since all the rest of the code of `BaseFormset` takes
 `TOTAL_FORM_COUNT` in consideration

-- 
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/059.f24927c6e6aff129cf734bbfe84216ef%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:  Yuneui
 Type:   |  Jeong
  Cleanup/optimization   |   Status:  assigned
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:  (none) => Yuneui Jeong
 * status:  new => assigned


Comment:

 Can I have a look at and work on this ticket? This is my first
 contribution, but I'll try my best.

-- 
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.d945bbf7b033b2d410a7757c6ffab629%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:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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:  0 |UI/UX:  0
--+

Comment (by Martin Svoboda):

 Pull request https://github.com/django/django/pull/14604

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

Re: [Django] #32906: Explain JSONBAgg benefit

[Django]

#32906: Explain JSONBAgg benefit
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 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
-+-
Changes (by Mariusz Felisiak):

 * cc: Mads Jensen (added)


Comment:

 I don't think there is a significant difference between them.
 `ARRAY_AGG()` returns array and `JSONB_AGG()` return JSON array, so when
 you aggregate `JSONField`s with `JSONBAgg()` then you can use key and
 index transforms which don't work with `ArrayAgg()` annotations.

-- 
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.0616dec6d2480e007c3ad2f9d4e1c0dd%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:  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:"cf6774a53b40243d35183b4300a9385b68fd8c75" cf6774a5]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf6774a53b40243d35183b4300a9385b68fd8c75"
 Fixed #32904 -- Made parse_time() more strict.

 Thanks Keryn Knight for the report.
 }}}

-- 
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.6fb25bd7d48acbbc1ff400a86d5ea19e%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:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * cc: Claude Paroz (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/071.2c0618d49c4db10a9b2a876a333fc335%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:  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.2615d453b2d93171c8bd53b7bbdfc147%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:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 We backported #30439. We need to decide whether that's required here too
 (or if it's just a cleanup)

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

Re: [Django] #32908: Add support for QuerySet.select_for_update()'s skip_locked options on MariaDB 10.6+

[Django]

#32908: Add support for QuerySet.select_for_update()'s skip_locked options on
MariaDB 10.6+
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (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 Carlton Gibson):

 * stage:  Unreviewed => 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/065.f4ae80041ef86a3a7fb820a630cccb5e%40djangoproject.com.

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

[Django]

#32910: Contrib apps: Different plural forms for Slovak (SK)
-+-
 Reporter:  Martin Svoboda   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:   |  Version:  3.2
  Internationalization   |
 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 Martin Svoboda:

Old description:

> #30439 has cause translations with different plural forms definitions are
> loaded in a separated catalogue.
>
> Contrib apps Sites, Redirects and Sessions have different plural form
> definitions than other Slovak translations.

New description:

 #30439 has cause translations with different plural forms definitions are
 loaded in a separated catalogue.

 Contrib apps Sites, Redirects and Sessions have different plural form
 definitions than other Slovak (SK) translations.

--

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

[Django] #32910: Contrib apps: Different plural forms for Slovak

[Django]

#32910: Contrib apps: Different plural forms for Slovak
+
   Reporter:  Martin Svoboda|  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  Internationalization  |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 |
+
 #30439 has cause translations with different plural forms definitions are
 loaded in a separated catalogue.

 Contrib apps Sites, Redirects and Sessions have different plural form
 definitions than other Slovak translations.

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

Re: [Django] #32866: urlize() does not handle html escaped string and trailing punctuation correctly

[Django]

#32866: urlize() does not handle html escaped string and trailing punctuation
correctly
--+
 Reporter:  Shipeng Feng  |Owner:  Shipeng Feng
 Type:  Bug   |   Status:  closed
Component:  Utilities |  Version:  dev
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by GitHub ):

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


Comment:

 In [changeset:"68cc04887b3c5b7ce8f28eaae5de266db99ca9a6" 68cc0488]:
 {{{
 #!CommitTicketReference repository=""
 revision="68cc04887b3c5b7ce8f28eaae5de266db99ca9a6"
 Fixed #32866 -- Fixed trimming trailing punctuation from escaped string in
 urlize().
 }}}

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

Re: [Django] #32909: strftime got None on sqlite

[Django]

#32909: strftime got None on sqlite
-+-
 Reporter:  gojuukaze|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 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:

 Trac is not a support channel. If you're having trouble implementing a
 custom database function, see 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/067.4950705bbce534f5473cafcead34d84a%40djangoproject.com.

[Django] #32909: strftime got None on sqlite

[Django]

#32909: strftime got None on sqlite
-+-
   Reporter:  gojuukaze  |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  3.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Model:

 {{{
 from django.utils.timezone import now

 class AdV2Log(models.Model):

 adv2_id = models.IntegerField()
 app_id = models.CharField(max_length=50)
 device_id = models.CharField(max_length=50)

 create_time = models.DateTimeField(default=now)
 update_time = models.DateTimeField(auto_now_add=True)
 }}}

 Func:

 {{{
 from django.db.models import F, Func

 class DateFormatFun(Func):
 function = 'date_format'
 template = "%(function)s( %(expressions)s, 'Y-m-d')"

 def as_sqlite(self, compiler, connection, **extra_context):
 sql, params = self.as_sql(compiler, connection,
   function='strftime',
 template="%(function)s('Y-m-d', %(expressions)s)",
   **extra_context)
 try:
 if self.output_field.get_internal_type() == 'DecimalField':
 sql = 'CAST(%s AS NUMERIC)' % sql
 except FieldError:
 pass
 return sql, params
 }}}

 

 {{{

 # use DateFormatFun
 In [2]: AdV2Log.objects.values('adv2_id',
 date=DateFormatFun('create_time')).annotate(counts=Count('id'))
 Out[2]: 

 # use extra
 In [3]: AdV2Log.objects.extra(select={"date": "strftime(
 
'%%Y-%%m-%%d',create_time)"}).values('adv2_id','date').annotate(counts=Count('id'))
 Out[3]: 


 }}}

-- 
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/052.84a22393066962f0ca49ddb83fdedfca%40djangoproject.com.

Re: [Django] #32908: Add support for QuerySet.select_for_update()'s skip_locked options on MariaDB 10.6+

[Django]

#32908: Add support for QuerySet.select_for_update()'s skip_locked options on
MariaDB 10.6+
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 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 Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/14603 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/065.c4c4f0bb4d4d49fdda3341c27f41ad09%40djangoproject.com.

[Django] #32908: Add support for QuerySet.select_for_update()'s skip_locked options on MariaDB 10.6+

[Django]

#32908: Add support for QuerySet.select_for_update()'s skip_locked options on
MariaDB 10.6+
-+-
   Reporter:  Mariusz|  Owner:  Mariusz Felisiak
  Felisiak   |
   Type:  New| Status:  assigned
  feature|
  Component:  Database   |Version:  4.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 MariaDB 10.6+ supports the `skip_locked` option, see
 [https://mariadb.com/kb/en/select/#skip-locked MariaDB docs].

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

Re: [Django] #26142: Provide a way for model formsets to disallow new object creation

[Django]

#26142: Provide a way for model formsets to disallow new object creation
-+---
 Reporter:  Tim Graham   |Owner:  Parth Patil
 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:  1
Easy pickings:  0|UI/UX:  0
-+---
Changes (by Carlton Gibson):

 * 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/067.bb772d283e161dc5d33d7a0e580e888a%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:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Abhyudai):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/14602/ pull request]

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

Re: [Django] #10929: Support a default value for Sum (and possibly other aggregation functions)

[Django]

#10929: Support a default value for Sum (and possibly other aggregation 
functions)
-+-
 Reporter:  nolan|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  aggregate annotate   | Triage Stage:  Accepted
  default|
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/063.d293d52a9ee03f2b7fd22c30e9d77b68%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 Carlton Gibson):

 Hi Tobias.

 > ... is called within the 'StaticFilesHandler'...

 Yes, of course. (Doh.)

 In that case using the browser dev tools to disable caching is the way to
 go.
 Thanks.

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

Re: [Django] #32499: simplify_regex only removes some metacharacters from regex patterns

[Django]

#32499: simplify_regex only removes some metacharacters from regex patterns
-+-
 Reporter:  Rohith P R   |Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admindocs|  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
-+-
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/066.cad1fe06e9b980ed3c8f49fd1c853a49%40djangoproject.com.