Re: [Django] #27818: Use contextlib.suppress to suppress exceptions.

2017-08-17 Thread Django 
#27818: Use contextlib.suppress to suppress exceptions.
-+-
 Reporter:  Mads Jensen  |Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  new
Component:  Core (Other) |  Version:  master
 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 Mads Jensen):

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


Comment:

 If a change slows down things, please revert the change.

-- 
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.a80e15200baa7133067df2925123b387%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27515: Make AuthenticationForm use the username length from the user model

2017-08-17 Thread Django 
#27515: Make AuthenticationForm use the username length from the user model
-+-
 Reporter:  Ramin Farajpour  |Owner:  Lucas
  Cami   |  Connors
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.10
 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
-+-

Comment (by Lucas Connors):

 Sorry for the spam. I thought unchecking and rechecking would
 automatically find the PR on Github. This is it here:
 https://github.com/django/django/pull/8925

-- 
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.d615c1f76e6d327957b80deb8c9cf15b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27515: Make AuthenticationForm use the username length from the user model

2017-08-17 Thread Django 
#27515: Make AuthenticationForm use the username length from the user model
-+-
 Reporter:  Ramin Farajpour  |Owner:  Lucas
  Cami   |  Connors
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.10
 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 Lucas Connors):

 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.517991e5e8d25a6871d54149f489aa7b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27515: Make AuthenticationForm use the username length from the user model

2017-08-17 Thread Django 
#27515: Make AuthenticationForm use the username length from the user model
-+-
 Reporter:  Ramin Farajpour  |Owner:  Lucas
  Cami   |  Connors
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.10
 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 Lucas Connors):

 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.60348adf929133595395e3081875%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

2017-08-17 Thread Django 
#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
--+
 Reporter:  Thomas Recouvreux |Owner:  Shun Yu
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  migrations m2m mysql  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Shun Yu):

 * owner:  nobody => Shun Yu
 * 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/066.a2e8ea7b6994587b5b8beca16af6f623%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28505: Django admin many to many recursive field widget shows identical objects

2017-08-17 Thread Django 
#28505: Django admin many to many recursive field widget shows identical objects
-+-
   Reporter:  Darshan|  Owner:  nobody
  Singh Khalsa   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.10
  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  |
-+-
 I have a scheduling app with a backend managed via Django Admin. This
 production app runs okay on a dedicated server using Ubuntu 14.04 LTS,
 Python2.7.3 with Django1.7.1 on a MySQL 5.5 database where the datatables
 evolved with the app through scores of code updates and migrations.

 The Members table for managing people and their role includes two
 recursive fields that indicate whether a particular person has an employer
 (ForeignKey) or is associated with one or more customers (ManyToMany).

 I subsequently discovered that when creating a brand new MySQL database,
 the Members table has flaws that render the Django Admin unuseable on that
 table. The Members table in its original model had two recursive fields
 that referred to fields within the "Member" table; current Django syntax
 requires recursive fields to be in the "self" table.

 The problem is that when adding or editing a Member via Django Admin, the
 employer picklist and customers picklist fields display "Member object"
 for each row instead of the desired list of various company names.

 Same problem in Python2.7.3 with Django1.7.1 and in Python3.4.3 with
 Django1.10.3.

 I posted this problem 8 month ago on StackOverflow.com at
 https://stackoverflow.com/questions/40954339/django-admin-many-to-many-
 recursive-field-widget-shows-identical-objects but no one volunteered a
 solution. The code snippets below create a minimum database that
 illustrates the problem. I can provide more documentation and screenshots
 if desired.


 {{{
 # models.py
 class Member(models.Model):
 first_name = models.CharField(max_length = 30)
 last_name = models.CharField(max_length = 30)

 role_choices = (
 ('Attendee', 'Attendee'),
 ('Customer', 'Customer'),
 ('Registrar', 'Registrar'),
   )

 now = timezone.now()

 role = models.CharField(choices=role_choices, max_length=50)
 created_date = models.DateTimeField(default=now)
 employer = models.ForeignKey('self', null=True, blank=True,
  limit_choices_to={'role': "Customer"})
 customers = models.ManyToManyField('self', limit_choices_to=
 {'role': "Customer"}, related_name="registrar_customers",
 null=True, blank=True)
 company_name = models.CharField(max_length=100, null=True, blank=True)

 def __unicode__(self):
 if self.role == "Customer":
 name = self.company_name
 elif self.role == "Attendee":
 name = "{} - {}{}".format(self.employer.company_name,
 self.first_name, self.last_name)
 else:
 name = self.first_name + " " + self.last_name

 return name

 # admin.py
 class MemberAdminForm(forms.ModelForm):
 class Meta:
 model = Member

 # Form override to force company names into picklists. This code
 section does not work.
 customers = forms.MultipleChoiceField(required=False)

 def __init__(self, *args, **kwargs):
 super(MemberAdminForm, self).__init__(*args, **kwargs)
 cust_choices = ((obj.id, obj.company_name) for obj
 in Member.objects.filter(role = 'Customer'))

 self.fields['employer'].choices = cust_choices
 self.fields['customers'].choices = cust_choices

 fields = ['first_name', 'last_name', 'role',
 'created_date', 'employer', 'customers',
 'company_name']

 class MemberAdmin(admin.ModelAdmin):
 list_display = ('first_name', 'last_name', 'role',
 'created_date', 'employer', 'company_name')

 form = MemberAdminForm

 admin.site.register(Member, MemberAdmin)
 }}}

-- 
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.googl

Re: [Django] #28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST setting in self.client.get

2017-08-17 Thread Django 
#28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST
setting in self.client.get
-+-
 Reporter:  Roland van Laar  |Owner:  Patrick
 Type:   |  Jenkins
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  1.11
 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 Patrick Jenkins):

 * has_patch:  0 => 1


Comment:

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

-- 
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.3b548a1922e81bb885c8969a56c20762%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST setting in self.client.get

2017-08-17 Thread Django 
#28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST
setting in self.client.get
-+-
 Reporter:  Roland van Laar  |Owner:  Patrick
 Type:   |  Jenkins
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  1.11
 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 Patrick Jenkins):

 The problem with the provided example is that under certain conditions
 assertRedirect will replay the request with different parameters than
 originally specified. The conditions necessary for this to occur are
 passing follow=False to the original client.get and also passing 'extra'
 parameters that will be interpreted as HTTP header's. Assert redirect
 (version 1.11.4:
 
https://github.com/django/django/blob/1a34dfcf797640d5d580d261694cb54e6f97c552/django/test/testcases.py#L317)
 makes an assumption that it is possible to exactly recreate the original
 request with the information that is available.

 To properly recreate the the original request it would be necessary to
 pass ALL method parameters AND all of the kwarg parameters that were
 originally passed in. This would require storing the 'extras' in the
 Client (django.test.client.py) so they could be acccessed in
 assertRedrrects and properly replayed.

 I believe this is the proper solution because it removes the assumptions
 present when assertRedirect attempts to recreate the request. Although
 this is a corner case, it is certainly acceptable for Django users to
 utilize the infinite space that is HTTP headers and provide varying logic
 depending on the values present. The downside of this implementation is
 that it bloats the Client by requiring it to store the extra parameters
 passed in. These extra parameters will rarely be used but I believe the
 tradeoff of adding properties to Client and potentially increasing memory
 footprint are small enough to warrant this change.

-- 
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.ac87f0293365d242f0c7c224a843559d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28050: TemplateSyntaxError should contain template name

2017-08-17 Thread Django 
#28050: TemplateSyntaxError should contain template name
-+-
 Reporter:  Petr Dlouhý  |Owner:  Roger
 |  Masse
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  TemplateSyntaxError  | Triage Stage:  Accepted
  template   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Roger Masse):

 * cc: Roger Masse (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 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.58d574c54c05e14c82cd23c48f8a6a20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28050: TemplateSyntaxError should contain template name

2017-08-17 Thread Django 
#28050: TemplateSyntaxError should contain template name
-+-
 Reporter:  Petr Dlouhý  |Owner:  Roger
 |  Masse
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  TemplateSyntaxError  | Triage Stage:  Accepted
  template   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Roger Masse):

 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.058159fbe8cb94b690c6a315c4c629dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28050: TemplateSyntaxError should contain template name

2017-08-17 Thread Django 
#28050: TemplateSyntaxError should contain template name
-+-
 Reporter:  Petr Dlouhý  |Owner:  Roger
 |  Masse
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  TemplateSyntaxError  | Triage Stage:  Accepted
  template   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Roger Masse):

 * has_patch:  1 => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.487c937ceb4200a03fc3b47eef542956%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21429: BaseCommand should use logging instead of custom output wrappers

2017-08-17 Thread Django 
#21429: BaseCommand should use logging instead of custom output wrappers
-+-
 Reporter:  Nical|Owner:  John Kang
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  command output   | Triage Stage:  Accepted
  logger |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by John Kang):

 * status:  new => assigned
 * owner:  (none) => John Kang


-- 
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/063.5635bbb163fa029ff88ed6438eef6a23%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28050: TemplateSyntaxError should contain template name

2017-08-17 Thread Django 
#28050: TemplateSyntaxError should contain template name
-+-
 Reporter:  Petr Dlouhý  |Owner:  Roger
 |  Masse
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  TemplateSyntaxError  | Triage Stage:  Accepted
  template   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Roger Masse):

 * 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 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.a150f2689a414df079c9d15107c57f2d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28493: Foreign keys break on migration if models are renamed in a different app

2017-08-17 Thread Django 
#28493: Foreign keys break on migration if models are renamed in a different app
-+-
 Reporter:  Christopher  |Owner:  Jeremy
  Neugebauer |  Satterfield
 Type:  Uncategorized|   Status:  assigned
Component:  Migrations   |  Version:  1.11
 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 Jeremy Satterfield):

 * owner:  nobody => Jeremy Satterfield
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 This seems to me the exact reason for the dependencies list in migrations.

-- 
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.d0a45f80907fb5946b7a926eca45b630%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28504: Add hooks into schema alter_field and reduce complexity

2017-08-17 Thread Django 
#28504: Add hooks into schema alter_field and reduce complexity
-+-
 Reporter:  Rachel Tobin |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.11
  (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 Rachel Tobin):

 * type:  New feature => Cleanup/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 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.85c628237c9ed1a25d9b114cee08f9df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28504: Add hooks into schema alter_field and reduce complexity

2017-08-17 Thread Django 
#28504: Add hooks into schema alter_field and reduce complexity
-+-
   Reporter:  Rachel |  Owner:  nobody
  Tobin  |
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  1.11
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 This patch adds in hooks into the base `alter_field` method in
 `BaseDatabaseSchemaEditor` so backends are able to augment or override the
 various actions that occur when altering a field. This also cuts
 complexity in half, and clarifies the various actions.

 PR is https://github.com/django/django/pull/8922

-- 
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/050.3e08b6cf6f80de7eb97bfc09ddc69100%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10761: ModelAdmin.queryset() is missing a mechanism for specifying different querysets for changelist and change object views

2017-08-17 Thread Django 
#10761: ModelAdmin.queryset() is missing a mechanism for specifying different
querysets for changelist and change object views
-+
 Reporter:  mrts |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  efficient-admin  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Pablo Ricco):

 * status:  assigned => new
 * owner:  Pablo Ricco => (none)


-- 
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/062.6f18f73077e3027ea256de4e7565%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28306: Complete test coverage for django/utils/lorem_ipsum.py

2017-08-17 Thread Django 
#28306: Complete test coverage for django/utils/lorem_ipsum.py
-+-
 Reporter:  Idan Melamed |Owner:
 Type:   |  luiscberrocal
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Testing, lorem   | Triage Stage:  Accepted
  ipsum  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by luiscberrocal):

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


-- 
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.41cd1c41d2261fa843c0526aee546aa3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10761: ModelAdmin.queryset() is missing a mechanism for specifying different querysets for changelist and change object views

2017-08-17 Thread Django 
#10761: ModelAdmin.queryset() is missing a mechanism for specifying different
querysets for changelist and change object views
-+---
 Reporter:  mrts |Owner:  Pablo Ricco
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  efficient-admin  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by Pablo Ricco):

 * owner:  nobody => Pablo Ricco
 * 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/062.e888942fbbf7447325f4e61745293db6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28147: Saving parent object after setting on child leads to unexpected data loss

2017-08-17 Thread Django 
#28147: Saving parent object after setting on child leads to unexpected data 
loss
-+-
 Reporter:  Erwin Junge  |Owner:  Amy Mok
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Amy Mok):

 * owner:  Erwin Junge => Amy Mok


-- 
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.66e365ac83f6100c269d24bca709f0bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27515: Make AuthenticationForm use the username length from the user model

2017-08-17 Thread Django 
#27515: Make AuthenticationForm use the username length from the user model
-+-
 Reporter:  Ramin Farajpour  |Owner:  Lucas
  Cami   |  Connors
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.10
 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 Lucas Connors):

 * owner:  Andrey Kuzminov => Lucas Connors


-- 
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.cb3a9c16f62d76561eca6a9606794004%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27877: Management command exceptions should be logged

2017-08-17 Thread Django 
#27877: Management command exceptions should be logged
-+-
 Reporter:  karyon   |Owner:  John Kang
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.11
  commands)  |
 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 John Kang):

 * owner:  (none) => John Kang
 * 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/064.9f09cce3c5641641c53c1e9285c932ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28332: Diamond multiple inheritance example in docs gives a clashing field check error

2017-08-17 Thread Django 
#28332: Diamond multiple inheritance example in docs gives a clashing field 
check
error
-+-
 Reporter:  Luc Saffre   |Owner:  Jeremy
 |  Satterfield
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.11
 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 Jeremy Satterfield):

 * owner:  nobody => Jeremy Satterfield
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 The `PizzeriaBar` model is inheriting the `restaurant_ptr` field from both
 `Pizzeria` and `Bar`, so you need to specify the parent link field on at
 least one of them, per
 https://docs.djangoproject.com/en/dev/topics/db/models/#specifying-the-
 parent-link-field. This gets a little complicated if you are creating this
 child model and overriding these field names at a later date than the
 parent since you are changing the field name, it is going to require using
 the `db_column` arg on the field or more complex migrations.

 This seems to me to have a lot of caveats to be provided as an example in
 the docs; however, here is a PR that updates the existing example to be
 working.

-- 
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.6ee60cdc8740484da61412f7515717ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST setting in self.client.get

2017-08-17 Thread Django 
#28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST
setting in self.client.get
-+-
 Reporter:  Roland van Laar  |Owner:  Patrick
 Type:   |  Jenkins
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  1.11
 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 Patrick Jenkins):

 * owner:  nobody => Patrick Jenkins
 * 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/066.00a0ef4d9193fca4d4efc2e14012b2c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28050: TemplateSyntaxError should contain template name

2017-08-17 Thread Django 
#28050: TemplateSyntaxError should contain template name
-+-
 Reporter:  Petr Dlouhý  |Owner:  Roger
 |  Masse
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  TemplateSyntaxError  | Triage Stage:  Accepted
  template   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Roger Masse):

 * owner:  kapil garg => Roger Masse


Comment:

 My plan is to improve the patch as described in the pull request with the
 suggestion by timgraham:

 ''There might be a possibility for the debug view to modify
 TemplateDoesNotExist's message so the redundant template names aren't
 added. In any case, a test is 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 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.f65c5af4ead3daafe67fa99a79e48c1d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28082: BaseDateListView should pass all context to subclasses

2017-08-17 Thread Django 
#28082: BaseDateListView should pass all context to subclasses
-+-
 Reporter:  Leon Matthews|Owner:  Sebastián
 Type:   |  Sassi
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  BaseDateListView | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sebastián Sassi):

 * owner:  nobody => Sebastián Sassi
 * 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/071.86b41982cd38a05c5973ff16b2e708f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21442: Configurable request parsing.

2017-08-17 Thread Django 
#21442: Configurable request parsing.
---+
 Reporter:  Tom Christie   |Owner:  Tom Christie
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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 Mark Lavin):

 * cc: Mark Lavin (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 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/069.545f1485b5fb397d3852beaee1f4b69f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28005: normalize usage of terms 'argument' and 'parameter'

2017-08-17 Thread Django 
#28005: normalize usage of terms 'argument' and 'parameter'
-+-
 Reporter:  Sergey Fedoseev  |Owner:  lachilles
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 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 lachilles):

 * owner:  ChillarAnand => lachilles


Comment:

 Will give this a try at Djangocon2017 today!

-- 
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.8beb53f2d5f47871e967fe8638b969ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28488: Django 1.11 to 1.11.4 raises CSRF verification failed if settings.DEBUG is False

2017-08-17 Thread Django 
#28488: Django 1.11 to 1.11.4 raises CSRF verification failed if settings.DEBUG 
is
False
-+-
 Reporter:  Ruben Alves  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  CSRF |  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:  csrf failed  | Triage Stage:
  settings debug false production|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mark Lavin):

 Based on the root cause of this problem, it sounds to be very similar to
 #22961 (StaticFilesHandler should not run middleware on 404). It has a
 patch to make that change but didn't include any tests for that new
 behavior.

-- 
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.655bc827e0e3bd6812db712d31078782%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28118: reverse() and get_absolute_url() may return different output for same FlatPage

2017-08-17 Thread Django 
#28118: reverse() and get_absolute_url() may return different output for same
FlatPage
---+-
 Reporter:  Pat|Owner:  Michal
 Type:  Bug|   Status:  closed
Component:  contrib.flatpages  |  Version:  1.8
 Severity:  Normal |   Resolution:  duplicate
 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 Mark Lavin):

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


Comment:

 From what I can tell this is a duplicate of #22261 which was discussed a
 few years ago. The resolution was that it seemed reasonable to change to
 use {{{reverse}}} for {{{get_absolute_url}}}. A PR
 https://github.com/django/django/pull/2554 was submitted but never updated
 after an initial review. If you are looking to move this forward then
 starting from that PR branch and updating it would be a good start.

-- 
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.4bea72dff8f80a3e07d5750ab016ee40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.