date:20150616

Re: [Django] #13751: Avoid open redirect issue with whitelist

2015-06-16 Thread Django

#13751: Avoid open redirect issue with whitelist
-+-
 Reporter:  anonymous|Owner:
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  open redirect,   | Triage Stage:  Accepted
  security   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by marcaurele):

 * owner:  marcaurele =>
 * status:  assigned => new


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

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

Re: [Django] #13751: Avoid open redirect issue with whitelist

2015-06-16 Thread Django

#13751: Avoid open redirect issue with whitelist
-+-
 Reporter:  anonymous|Owner:
 |  marcaurele
 Type:  New feature  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  open redirect,   | Triage Stage:  Accepted
  security   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by marcaurele):

 After another thought on that fix, I must say that I share apollo13 point
 of view and don't see a good use case. I'm for a wontfixing.

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jdufresne):

 > If the login solution proposed in #20916 will meet your use case, I find
 that better than adding an attribute to test.Client as I think the latter
 will be difficult to use (requiring initializing the test client on your
 own).

 I agree. I will continue work on the other ticket/PR. If you prefer to
 close this, I have no problem with that.

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

Re: [Django] #12952: Models history doesn't use verbose names

2015-06-16 Thread Django

#12952: Models history doesn't use verbose names
--+
 Reporter:  acangiano |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 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:  1
--+

Comment (by RamezIssac):

 I think it's better to work with the form labels then model's verbose
 name,

 I think It's actually a more natural flow and more consistent if the label
 is different then the verbose name.

 My Approach would be to gather the changed fields' labels, then send it to
 get_text_list
 
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L925-L936

 {{{
 translated_changed_fields = [form.fields[f].label for f in
 form.changed_data]
 change_message.append(_('Changed %s.') %
 get_text_list(translated_changed_fields, _('and')))

 #again for formset
 for changed_object, changed_fields in formset.changed_objects:
 translated_changed_fields = [formset.fields[f].label for f in
 changed_fields]
 change_message.append(_('Changed %(list)s for %(name)s "%(object)s".')
   % {'list':
 get_text_list(translated_changed_fields, _('and')),
 #...

 }}}

 Created a duplicate [https://code.djangoproject.com/ticket/24990 24990]

 Regards;

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

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

2015-06-16 Thread Django

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F(), ORM, distinct   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by wbar):

 But when I use your solution I'm receiving:

 {{{
 AttributeError: 'ValuesQuerySet' object has no attribute 'distict'
 }}}

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

Re: [Django] #24990: Admin Log change message display changed fields names (not label text nor fields' verbose names )

2015-06-16 Thread Django

#24990: Admin Log change message display changed fields names (not label text 
nor
fields' verbose names )
---+--
 Reporter:  RamezIssac |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by timgraham):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 Duplicate of #12952

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

[Django] #24990: Admin Log change message display changed fields names (not label text nor fields' verbose names )

2015-06-16 Thread Django

#24990: Admin Log change message display changed fields names (not label text 
nor
fields' verbose names )
---+
 Reporter:  RamezIssac |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 When an object is edited from the admin,
 ModelAdmin.construct_change_message() report the changed fields by their
 form's name instead of their label value or even field verbose name.

 This 'might be ok' only if the field names are equal  to label text and in
 English
 If the active language is not English, change message looks wired like
 this:
 عدل name (i.e. changed name)

 You can see the cause of the issue here
 
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L925-L926
 And again with formsets 936
 
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L936

 Not sure how to write a test for this .

 My Proposed Fix:
 Instead of sending form.changed_data to get_text_list, send their labels
 {{{
 translated_changed_fields = [form.fields[f].label for f in
 form.changed_data]
 change_message.append(_('Changed %s.') %
 get_text_list(translated_changed_fields, _('and')))
 }}}
 And again with formset
 {{{
 translated_changed_fields = [formset.fields[f].label for f in
 changed_fields]
 #...
 % {'list': get_text_list(translated_changed_fields, _('and')),
 }}}




 Regards;

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

Re: [Django] #24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

2015-06-16 Thread Django

#24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured 
Error
-+-
 Reporter:  raiderrobert |Owner:
 Type:   |  raiderrobert
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  setting  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by raiderrobert):

 Going to make it a warning instead of a hard fail. It's going in
 `core/checks/security/base.py`.

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-16 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 rolo):

 Will do - I wasn't sure if it was my place to change those. Will do so
 next time :).

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

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

2015-06-16 Thread Django

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F(), ORM, distinct   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shaib):

 I believe the OP was only using `something` to point out that `name_lower`
 doesn't work in spite of being given as an option in the error message.

 On a separate note: You should be able to get the query you described
 initially with
 {{{
 Author.objects.annotate(
 name_lower=Func(F('name'), function='lower')
 ).values('name_lower').distinct()
 }}}
 or something similar.

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

Re: [Django] #24948: BMP Image File treated as invalid

2015-06-16 Thread Django

#24948: BMP Image File treated as invalid
-+-
 Reporter:  jerzyk   |Owner:  coldmind
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  bmp, image   | 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 Tim Graham ):

 In [changeset:"8abe2d0643a9ad9986e5b12644dbe0d0fc8b5f5d" 8abe2d0]:
 {{{
 #!CommitTicketReference repository=""
 revision="8abe2d0643a9ad9986e5b12644dbe0d0fc8b5f5d"
 [1.8.x] Fixed #24948 -- Fixed crash when uploading bitmap images in
 forms.ImageField

 Backport of cf6ce279c7671a4c83c960c5c526f92679a4fac8 from master
 }}}

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-16 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 * needs_docs:  1 => 0


Comment:

 Thanks, please don't forget to modify the "Has patch", "Needs
 documentation", etc. flags as necessary.

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

Re: [Django] #24948: BMP Image File treated as invalid

2015-06-16 Thread Django

#24948: BMP Image File treated as invalid
-+-
 Reporter:  jerzyk   |Owner:  coldmind
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  bmp, image   | 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 Tim Graham ):

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


Comment:

 In [changeset:"cf6ce279c7671a4c83c960c5c526f92679a4fac8" cf6ce279]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf6ce279c7671a4c83c960c5c526f92679a4fac8"
 Fixed #24948 -- Fixed crash when uploading bitmap images in
 forms.ImageField
 }}}

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 If the login solution proposed in #20916 will meet your use case, I find
 that better than adding an attribute to `test.Client` as I think the
 latter will be difficult to use (requiring initializing the test client on
 your own).

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

Re: [Django] #24988: Document raising a dictionary of ValidationErrors

2015-06-16 Thread Django

#24988: Document raising a dictionary of ValidationErrors
--+
 Reporter:  michaeljohnbarr   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  ValidationError   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * Attachment "24988-test.diff" 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/073.081d54723ccf35086c89fe531af5189b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24988: Document raising a dictionary of ValidationErrors (was: ValidationError fails to set code)

2015-06-16 Thread Django

#24988: Document raising a dictionary of ValidationErrors
--+
 Reporter:  michaeljohnbarr   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  ValidationError   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * type:  Bug => Cleanup/optimization
 * component:  Core (Other) => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 I'll attach the diff of my investigation, but it looks like this should be
 a documentation ticket then.

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"8050e6282e4daee24758a4a1c6c2fa938957bef2" 8050e62]:
 {{{
 #!CommitTicketReference repository=""
 revision="8050e6282e4daee24758a4a1c6c2fa938957bef2"
 [1.8.x] Refs #24987 -- Documented that Client.login() rejects inactive
 users.

 Backport of fbc618c13cc72b9c2f4c8dfd5ef8b8ab5a5d7caa from master
 }}}

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"fbc618c13cc72b9c2f4c8dfd5ef8b8ab5a5d7caa" fbc618c]:
 {{{
 #!CommitTicketReference repository=""
 revision="fbc618c13cc72b9c2f4c8dfd5ef8b8ab5a5d7caa"
 Refs #24987 -- Documented that Client.login() rejects inactive users.
 }}}

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

Re: [Django] #24948: BMP Image File treated as invalid

2015-06-16 Thread Django

#24948: BMP Image File treated as invalid
-+-
 Reporter:  jerzyk   |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:  bmp, image   | 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 timgraham):

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

Re: [Django] #24988: ValidationError fails to set code

2015-06-16 Thread Django

Comment (by loic):

`code` and `params` are really intended for single message
`ValidationError`, if we did pass `code=code` in the constructor we'd be
effectively creating an implicit shortcut, I don't think it's a good idea
(explicit better than implicit, TIMTOWTDI, etc.). Also it's ambiguous if
you pass a `dict` that mixes strings (which will be turned into
`ValidationError`) and `ValidationError` instances.

Raising `ValidationError` with `error_dict` is mostly useful in
`Model.clean()` because forms have better APIs (i.e. `Form.add_error()`),
but I guess we can still document it in
[https://docs.djangoproject.com/en/1.8/ref/forms/validation/#raising-
validationerror Raising ValidationError] if only for the sake of
exhaustivity.

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

Re: [Django] #24948: BMP Image File treated as invalid

2015-06-16 Thread Django

#24948: BMP Image File treated as invalid
-+
 Reporter:  jerzyk   |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:  bmp, image   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by coldmind):

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


Comment:

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

 I think setting `content_type` to None will be enough.

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

Re: [Django] #16860: Provide hooks for password policy

2015-06-16 Thread Django

#16860: Provide hooks for password policy
--+
 Reporter:  PaulM |Owner:  erikr
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 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
--+

Comment (by Tim Graham ):

 In [changeset:"09f2cdbe1a43e79e31f5ea509b59d4c87db29832" 09f2cdb]:
 {{{
 #!CommitTicketReference repository=""
 revision="09f2cdbe1a43e79e31f5ea509b59d4c87db29832"
 Refs #16860 -- Fixed a resource and deprecation warning in password
 validation.
 }}}

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-16 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by rolo):

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jdufresne):

 > However, your current change is backwards incompatible and will break
 many users' tests. I therefore don't consider it a bug but a feature
 request.
 >
 > One idea that comes to mind, of how to solve the problem in a backwards
 compatible manner, would be a flag on the client check_is_active=True that
 would allow to bypass the check.

 Understood about backwards incompatible concern. I can investigate coding
 this idea if there is agreement that it is the best approach.

 > How about documenting this for now?

 So long as the limitation exists, makes sense. You're diff looks good to
 me.

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

Re: [Django] #18580: Avoiding SQLite update+annotations "only a single result allowed for a SELECT that is part of an expression"

2015-06-16 Thread Django

#18580: Avoiding SQLite update+annotations "only a single result allowed for a
SELECT that is part of an expression"
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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 timgraham):

 All accepted tickets are good candidates to be fixed once we have a
 working patch.

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

Re: [Django] #18580: Avoiding SQLite update+annotations "only a single result allowed for a SELECT that is part of an expression"

2015-06-16 Thread Django

#18580: Avoiding SQLite update+annotations "only a single result allowed for a
SELECT that is part of an expression"
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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 chris-mccabe1988):

 I had the exact same issue, thanks jonash for the work around. I'm a
 little surprised that this hasn't been fixed in the 3 years since it's
 been raised, the work around is simple but not entirely obvious from the
 error message.

 Out of curiosity, will this be fixed in a future version?

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-16 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_docs:  0 => 1
 * 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/067.cb9315f31b6b866edae2b83476e881ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations (was: Introduce low-level documentation on Django's components)

2015-06-16 Thread Django

#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  MarkusH|Owner:  MarkusH
 Type:  New feature|   Status:  assigned
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:  0  |UI/UX:  0
---+
Changes (by MarkusH):

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


Old description:

> I first had the idea a Django: Under the Hood 2014, but abandoned it. A
> couple of days ago the idea came up in IRC again:
>
> It would be helpful for new contributors as well as for other core devs
> not involved in certain parts of Django, to have documentation that
> outlines how these components work.
>
> I.e. in migrations: you have a `ModelState` and to detect changes the
> autodetector takes all migrations and build the final model
> representation and then compares this `ProjectState` to the
> `ProjectState` constructed from all currently available models.
>
> Tim proposed to add that documentation to `docs/internals/`. I'd put it
> into `docs/internals/api/`

New description:

 It would be helpful for new contributors as well as for other core devs
 not involved in certain parts of Django, to have documentation that
 outlines how these components work. Tim proposed to add that documentation
 to `docs/internals/`. I'd put it into `docs/internals/api/`

 E.g. in migrations: you have a `ModelState` and to detect changes the
 autodetector takes all migrations and build the final model representation
 and then compares this `ProjectState` to the `ProjectState` constructed
 from all currently available models.

--

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

Re: [Django] #24988: ValidationError fails to set code

2015-06-16 Thread Django

Comment (by michaeljohnbarr):

I can confirm that using ValidationError as the value does work as
expected. Perhaps if we don't change how it works internally, we can
update the documentation. This particular use case is not covered in the
[https://docs.djangoproject.com/en/1.8/ref/forms/validation/#raising-
validationerror Raising ValidationError] documentation, but can be found
as an example in the

[https://docs.djangoproject.com/en/1.8/ref/models/instances/#django.db.models.Model.clean
Model.clean() 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/073.5e179ece73442eb2a7add4cdafbf83cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24989: Introduce low-level documentation on Django's components

2015-06-16 Thread Django

#24989: Introduce low-level documentation on Django's components
---+--
 Reporter:  MarkusH|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 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 timgraham):

 I think the idea is accepted, but a ticket is needed for each thing you
 want to document, not all of them in one ticket. Do you want to retitle
 this one to cover 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/065.707b7b400057a2fc26849fee8a48b567%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24989: Introduce low-level documentation on Django's components

2015-06-16 Thread Django

#24989: Introduce low-level documentation on Django's components
-+
Reporter: MarkusH| Owner: nobody
Type: New feature| Status: new
Component: Documentation |Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+
I first had the idea a Django: Under the Hood 2014, but abandoned it. A
couple of days ago the idea came up in IRC again:

It would be helpful for new contributors as well as for other core devs
not involved in certain parts of Django, to have documentation that
outlines how these components work.

I.e. in migrations: you have a `ModelState` and to detect changes the
autodetector takes all migrations and build the final model representation
and then compares this `ProjectState` to the `ProjectState` constructed
from all currently available models.

Tim proposed to add that documentation to `docs/internals/`. I'd put it
into `docs/internals/api/`

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-16 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  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
-+-

Comment (by rolo):

 Have created a pull request at https://github.com/django/django/pull/4867

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

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

2015-06-16 Thread Django

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F(), ORM, distinct   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jarshwah):

 Because `name_lower` is added to the field list when you use the
 annotation. The field "something" does not exist and was not annotated in
 your example.

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by srkunze):

 @timgraham We see if we can produce an example for 1.8.

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by srkunze):

 Thanks @bmispelon. TypeError was just a quick example. See comment:8, we
 actually do not appreciate the trial-and-error approach that will lead to
 an ever-growing except list.

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 How about documenting this for now?

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "24987-doc.diff" 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/067.1363f4753d941c5a779558ea933cace5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by timgraham):

 I still haven't managed to reproduce the "blank page" issue. Could you
 given an example?

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

Re: [Django] #24988: ValidationError fails to set code

2015-06-16 Thread Django

#24988: ValidationError fails to set code
-+--
 Reporter:  michaeljohnbarr  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ValidationError  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timgraham):

 * cc: loic (added)


Comment:

 I think it's preferred to use ValidationErrors as the values of the
 messages dict.
 {{{
 'start': ValidationError_(
 '{start} must come before {end}.'
 params={...},
 code='invalid',
 ),
 'end': ...
 }}}
 The change you suggested makes sense to me, but I'm not sure if we should
 do it. If not, might be helpful to issue a warning or exception rather
 than silently discarding the value from the code parameter.

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by bmispelon):

 For reference, I bisected the fix down to
 28a571348bca9c5a3c137e495e7d3c9349a5bd56 which was a fix for #20745.

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
Reporter: srkunze |Owner: nobody
Type: Bug | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: block.super blank| Triage Stage:
pages | Unreviewed
Has patch: 0| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 1
-+-

Comment (by srkunze):

In Django 1.6, render_to_string does not work. Maybe, in Django 1.8 this
is also another convenience layer.

Well, not sure if Django 1.8 fixes the original issue. Infact, when
programming, we simply do not know which errors might occur. So, just
because Django re-raises TypeErrors now, does not necessarily mean that we
cover all cases (all types of errors).

As soon as somebody raises another exception that is not covered, we are
going to see a blank page again. So, our suggestion was: why not check if
the given context variable might work in the first place?

Right now, all Django versions just call the variables, do the attribute,
do the list access etc. So, we mix up both cases:
1. wrong access or
2. internal error when evaluating

cf.
https://github.com/django/django/blob/1.8.2/django/template/base.py#L804

We actually do not want an ever-growing list of Errors (TypeError,
AttributeError, KeyError, ValueError, IndexError -- as you can see in
base.py) but a clean long-lasting solution.

For instance, Python provides the function 'has_attr' which can be used to
check whether an object has a certain attribute or not. The same goes for
list access and function calls.

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

Re: [Django] #24914: Include basic permission mixins into Django

2015-06-16 Thread Django

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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
--+

Comment (by jaysonsantos):

 Never mind I just saw that there is a pull request already :)

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

Re: [Django] #24914: Include basic permission mixins into Django

2015-06-16 Thread Django

#24914: Include basic permission mixins into Django
--+
 Reporter:  raphaelm  |Owner:  MarkusH
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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
--+

Comment (by jaysonsantos):

 Replying to [comment:13 MarkusH]:
 > Thanks for mentioning that, Rundll. The current implementation does not
 support stacking them (braces' `LoginRequired` and `PermissionRequired`
 mixins do, though). However, neither our `UserPassesTestMixin` nor braces'
 allows stacking inherited mixins, either.
 >
 > That makes me wonder how one is supposed to combine different permission
 checks that are used separately and together:
 >
 > {{{#!python
 > class CheckOneMixin(UserPassesTestMixin):
 > def test_func(self, user):
 > return something_is_true_or_false
 >
 > class CheckTwoMixin(UserPassesTestMixin):
 > def test_func(self, user):
 > return something_else_is_true_or_false
 >
 > class MyView1(CheckOneMixin, View):
 > pass
 >
 > class MyView2(CheckTwoMixin, View):
 > pass
 >
 > class MyView3(CheckOneMixin, CheckTwoMixin, View):
 > pass
 > }}}
 >
 > Effectively, `MyView3` will never bother about the value of
 `something_else_is_true_or_false` as that function is never called.

 About ensuring at least one valid response, I thought something like this:
 {{{#!python
 class CheckOneMixin:
 def test_func(self):
 print(self)
 return True


 class CheckTwoMixin:
 def test_func(self):
 print(self)
 return False


 class Dispatcher:
 def dispatch(self):
 validators = [b.test_func for b in self.__class__.__bases__ if
 hasattr(b, 'test_func')]
 for validator in validators:
 if validator(self):
 return 'Dispatch for real'

 return 'Invalid permissions'



 class MyView1(CheckOneMixin, Dispatcher):
 pass


 class MyView2(CheckTwoMixin, Dispatcher):
 pass


 class MyView3(CheckOneMixin, CheckTwoMixin, Dispatcher):
 pass


 for klass in (MyView1, MyView2, MyView3):
 print(klass().dispatch(), '\n')
 }}}

 In this case the class that act like the real dispatcher could call every
 function on View's bases.

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-16 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  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 rolo):

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

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

2015-06-16 Thread Django

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F(), ORM, distinct   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by wbar):

 I don't know why you'd think that'd work, especially since the error tells
 you that "something" isn't actually a field on the model. Am I missing
 something here?

 So why You can see `name_lower` on the choices list ?

 {{{
 Choices are: id, name, name_lower, src_id
 }}}

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

#24960: Blank pages due to {{ block.super }}
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  block.super blank| Triage Stage:
  pages  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by timgraham):

 Yes, my usage of `render_to_string()` isn't proper, but it seemed enough
 to test the code you provided.

 I'm not following what you are saying now. Django 1.8 fixes the original
 issue but there's another issue there? Please clarify what behavior you
 are seeing and what the expected behavior is.

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

Re: [Django] #24960: Blank pages due to {{ block.super }}

2015-06-16 Thread Django

Comment (by srkunze):

Are you sure that render_to_string(...) works as intended here? Should a
view not return a HttpResponse?

We used Django 1.6. We upgraded to Django 1.8 and it seems as if the error
is returned properly now.

We looked into the corresponding Django source code and found that Django
catches more errors as before and re-raises them. That approach seems a
bit error especially when using custom exceptions.

Don't you think that a check whether a context variable is callabed/has
attribute/has dictionary key should be handled not by trail and error but
by a check-before-do?

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

Re: [Django] #24971: Make startapp generate an apps.py

2015-06-16 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 Tim Graham ):

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


Comment:

 In [changeset:"e6dd7f995a5a785a5aa12378df209314b1d77d93" e6dd7f99]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6dd7f995a5a785a5aa12378df209314b1d77d93"
 Fixed #24971 -- Made startapp generate an apps.py
 }}}

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

Re: [Django] #24834: Optional port in Host request header breaks get_current_site()

2015-06-16 Thread Django

#24834: Optional port in Host request header breaks get_current_site()
---+
 Reporter:  ngnpope|Owner:  ngnpope
 Type:  Bug|   Status:  assigned
Component:  contrib.sites  |  Version:  1.5
 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 MarkusH):

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

Re: [Django] #24987: django.test.client.Client.login() rejects user with is_active=False

2015-06-16 Thread Django

#24987: django.test.client.Client.login() rejects user with is_active=False
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MarkusH):

 * needs_docs:  0 => 1
 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Someday/Maybe


Comment:

 I tend to follow Claude's reasoning in #19792. I, personally expect
 `client.login()` to behave like `contrib.auth.login()`, thus checking for
 `is_active=True`. I see your point though.

 However, your current change is backwards incompatible and will break many
 users' tests. I therefore don't consider it a bug but a feature request.

 One idea that comes to mind, of how to solve the problem in a backwards
 compatible manner, would be a flag on the client `check_is_active=True`
 that would allow to bypass the check.

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

Re: [Django] #11331: Memcached backend closes connection after every request

2015-06-16 Thread Django

#11331: Memcached backend closes connection after every request
--+
 Reporter:  booink@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Cache system)   |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MarkusH):

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


Comment:

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

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

Re: [Django] #24080: Sqlite segmentation fault regression when running tests (since 1.7.2)

2015-06-16 Thread Django

#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
---+
 Reporter:  stevejalim |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sqlite | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by chipx86):

 * cc: chipx86@… (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.5c5eabf13a8772f21277258b69370c05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

52 matches

Mail list logo