Re: [Django] #29573: Add link from per-item aggregation topic discussion to `annotate()` ref.

[Django]

#29573: Add link from per-item aggregation topic discussion to `annotate()` ref.
-+-
 Reporter:  Thomas Güttler   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 Vishvajit Pathak):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/10369 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.04818b4d7106d84b544af764f1f336f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29732: Form field for comma separated value from the list of choices

[Django]

#29732: Form field for comma separated value from the list of choices
-+-
 Reporter:  Greatxam |Owner:  Greatxam
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  forms, comma | Triage Stage:
  separated, |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 I don't think we'll be adding any new form fields without a consensus on
 the DevelopersMailingList. The proposal needs to be more detailed than
 what you outlined here.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.25f6e3485c6fae55a29fb15ac47dd219%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29735: MRO of DeleteView need to be changed.

[Django]

#29735: MRO of DeleteView need to be changed.
-+-
   Reporter:  seokhun|  Owner:  nobody
  kim|
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Generic|Version:  2.1
  views  |   Keywords:  deletemixin,
   Severity:  Normal |  basedeleteview, deleteview, generic
   Triage Stage: |  view
  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 (Please refer to Pull Request: MRO of DeleteView was changed)

 I think MRO of DeleteView need to be changed in order to clarify the
 inheritance hierarchy.
 So I refactored BaseDeleteView and DeleteMixin.

 * (1) What is better as the super class of BaseDeleteView ?
   * Currently BaseDeleteView inherits from BaseDetailView.
   * I think SingleObjectMixin is sufficient.
   * I think Inheritance of Mixin is better than generic view itself.
   * So I deleted BaseDetailView in the super class of BaseDeleteView.
 * In order to inherit SingleObjectMixin instead of BaseDetailView,
   * BaseDeleteView inherits from DeletionMixin.
   * DeletionMixin inherits from SingleObjectMixin.
 * (2) Where is better on the location of get(), post(), delete() methods ?
   * Currently DeleteMixin provides those methods.
   * It is bad that Mixin class provides those methods, I think.
   * So My change is that BaseDeleteView provides get(), post() and
 delete() methods.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.fea3efa5d2dd1f4af6d891b56513ab17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29529: Allow FilePathField path to accept a callable.

[Django]

#29529: Allow FilePathField path to accept a callable.
-+-
 Reporter:  Sebastiaan Arendsen  |Owner:  rootart
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migration,   | Triage Stage:  Accepted
  filepathfield, makemigrations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by rootart):

 * owner:  (none) => rootart
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.145495d24d4acf5361544c66f6539381%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29733: update_or_create - documentation misleading

[Django]

#29733: update_or_create - documentation misleading
-+-
 Reporter:  David Pratten|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexander Holmbäck):

 Hi David,

 I can't replicate this behavior and the update works as expected. Make
 sure that there isn't another record where the value of qbac is set to 'A'
 (in case an IntegrityError is rightfully raised), if the problem persist,
 please provide the message and stacktrace of your error so that I can test
 this further.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.ae22bc0292188ff72ac2871f0c5b3f02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29229: QuerySet.values_list() combined with .extra() or .annotate() may produce wrong .union()

[Django]

#29229: QuerySet.values_list() combined with .extra() or .annotate() may produce
wrong .union()
-+-
 Reporter:  master   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  union values_list| 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 master):

 The regression test added by the PR
 (test_union_with_two_annotated_values_list()) seems to have an
 unnecessarily complex combination, just to comply with a mandatory
 ordering of fields imposed by the union.
 Instead of:

 {{{
 .annotate(count=F('num'),).annotate(num=Value(1, IntegerField()),
 }}}
 This writing is more understandable:

 {{{
 .annotate(num=F('num'),).annotate(count=Value(1, IntegerField()),
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6b5380dc4604a2afcc76c0a6b34d2c14%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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
-+-

Comment (by Vishvajit Pathak):

 We definitely need to improve the documentations. Coercing the language
 code is something we have to take call on.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.5de3a925c58d73a3e3acdd387f5e8079%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29734: Added option to sort message strings for translations by msgid

[Django]

#29734: Added option to sort message strings for translations by msgid
-+-
   Reporter:  Eugene |  Owner:  nobody
  Bespaly|
   Type:  New| Status:  new
  feature|
  Component: |Version:  master
  Internationalization   |
   Severity:  Normal |   Keywords:  i18n, makemessages
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 gettext utils support `--sort-output` argument

 PR: https://github.com/django/django/pull/9295

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.b0754effce9d764e32038e08cd08dfd3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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
-+-

Comment (by Claude Paroz):

 Improving documentation is welcome, but silently accepting a wrong
 language code also look a bit suspicious. I think I would be happy with a
 warning without coercing anything.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.5e9e128a64598bb3363f0a04aef2475b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29529: Allow FilePathField path to accept a callable.

[Django]

#29529: Allow FilePathField path to accept a callable.
-+-
 Reporter:  Sebastiaan Arendsen  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migration,   | Triage Stage:  Accepted
  filepathfield, makemigrations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Nicolas Noé):

 * status:  assigned => new
 * owner:  Nicolas Noé => (none)


Comment:

 Sure, sorry for blocking the ticket while I was too busy...

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b1ddb3eb7255d0c8f9625f980407bf43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29733: update_or_create - documentation misleading

[Django]

#29733: update_or_create - documentation misleading
+
   Reporter:  DavidPratten  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  2.1
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 When update_or_create searches the table for a record to update it
 searches all fields marked 'unique' or 'primary_key'.

 In the case where a record has two candidate keys the update_or_create
 function will fail to update either the primary key or the candidate key,
 leading to an Integrity Error.

 https://docs.djangoproject.com/en/2.1/ref/models/querysets/#update-or-
 create

 This behavour is not 'wrong'. But it is surprising and a time waster.

 {{{
 class Coa(models.Model):
 def __str__(self):
 return f'{self.qbac}'
 trantype = models.CharField(max_length=255, db_column=u'TranType',
 blank=True)
 qbac = models.CharField( unique=True, max_length=255,
 db_column=u'QBAc')
 guid = models.CharField(max_length=32, primary_key=True)
 account_type=models.CharField(max_length=20)
 }}}

 Containing the following record:
 {{{
 "ACCNT", "Advantage Saver", "c6f30c15c9dd1e5af9143fd7bed99315", "A"
 }}}

 The following, otherwise sensible, code fails with an IntegrityError

 {{{
 obj, created =
 Coa.objects.update_or_create(guid='c6f30c15c9dd1e5af9143fd7bed99315',
 defaults={'trantype': 'ACCNT', 'qbac': 'A', 'account_type': 'A' },)
 }}}

 because the search is on both guid AND qbac rather than just on guid as
 requested by the single field in the !**kwargs.

 Recommend clarification in the docu that it is not possible to search only
 on one field if there are multiple unique constraints in the model.

 David

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/055.7ca3a3a3aaeee11d2de39eb8ce7ad45a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29732: Form field for comma separated value from the list of choices

[Django]

#29732: Form field for comma separated value from the list of choices
-+-
 Reporter:  Greatxam |Owner:  Greatxam
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  forms, comma | Triage Stage:
  separated, |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Greatxam):

 * status:  new => assigned
 * owner:  nobody => Greatxam


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.6f222f4f860da34b9cc5d7a039bee30f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29732: Form field for comma separated value from the list of choices

[Django]

#29732: Form field for comma separated value from the list of choices
-+-
   Reporter:  Greatxam   |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component:  Forms  |Version:  master
   Severity:  Normal |   Keywords:  forms, comma
   Triage Stage: |  separated,
  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Create a form field to handle comma separated value selected from list of
 choices.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.3e0e67b82fcece5d8c7dff659370127e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29711: Add system check to ensure uniqueness of admin actions' __name__.

[Django]

#29711: Add system check to ensure uniqueness of admin actions' __name__.
-+-
 Reporter:  Przemysław   |Owner:
  Buczkowski |  Przemysław Buczkowski
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 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 Przemysław Buczkowski):

 * owner:  nobody => Przemysław Buczkowski
 * status:  new => assigned


Comment:

 Gladly.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.004a8b59e6b6aaf78d47f45987368764%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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
-+-

Comment (by Nick Pope):

 Trying to coerce ''any'' input to something like a
 [https://www.w3.org/International/articles/language-tags/ language tag]
 only to hack it back to a
 [https://www.gnu.org/software/libc/manual/html_node/Locale-Names.html
 locale] using {{{to_locale()}}} feels like a kludge. It would be better to
 improve documentation.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.138d6373831e54501f9b80fb70f45559%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29243: Improve efficiency of migration graph algorithm

[Django]

#29243: Improve efficiency of migration graph algorithm
-+-
 Reporter:  Krzysztof|Owner:  nobody
  Gogolewski |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * version:  2.0 => master
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.b1443fdc698eb736fe25de188849d2aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29713: Add a django check to ensure the LANGUAGE_CODE setting uses the standard language ID format

[Django]

#29713: Add a django check to ensure the LANGUAGE_CODE setting uses the standard
language ID format
-+-
 Reporter:  Ian Foote|Owner:  David
 Type:  New feature  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nick Pope):

 Follow up [https://github.com/django/django/pull/10367 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7b43f6bddf53fdf18837fb82daa1bb74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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
-+-

Comment (by Vishvajit Pathak):

 Warning added when a language code is normalized.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.cd29dba7688e72450c442785e66a4c15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29725: Inefficient SQL generated when counting a ManyToMany

[Django]

#29725: Inefficient SQL generated when counting a ManyToMany
-+-
 Reporter:  Gavin Wahl   |Owner:  oliver
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by oliver):

 * has_patch:  0 => 1
 * needs_tests:  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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0e41d2d0ecac939abc319368f15b586f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29725: Inefficient SQL generated when counting a ManyToMany

[Django]

#29725: Inefficient SQL generated when counting a ManyToMany
-+-
 Reporter:  Gavin Wahl   |Owner:  oliver
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by oliver):

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

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f5678af330f825b6c531daddab8d458c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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
-+-

Comment (by Claude Paroz):

 I think I would still output a warning when a language code is normalized,
 just to inform the user that its input has been corrected.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.c18e75466798ce63e00dd4f26cfec151%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29688: ModelAdmin: Add attribute to override manager used by ModelAdmin.get_queryset()

[Django]

#29688: ModelAdmin: Add attribute to override manager used by
ModelAdmin.get_queryset()
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Replying to [comment:10 Tim Graham]:
 > For the record, my inaction wasn't meant to convey an opinion. I was
 merely occupied with some other priorities.

 Yes. Of course. My comment wasn't meant to imply otherwise. Merely that
 it's not reasonable to expect you always to be the arbiter.
 Thanks Tim!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0d24d1e5b8a9e27a1dfbc7bf9ddc558a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29729: Update "Writing your first patch for Django" tutorial

[Django]

#29729: Update "Writing your first patch for Django" tutorial
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  2.1
 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 Carlton Gibson):

 Yes, as you say. 

 * Happy for you to suggest what you think is best.
 * Not sure ‘'anything’’ would survive without maintanence indefinitely.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.485191d8d0173b6fc76bb3c6904750bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.