Re: [Django] #18150: Uploading a file ending with a backslash fails

[Django]

#18150: Uploading a file ending with a backslash fails
-+-
 Reporter:  Peter Kuma   |Owner:
 Type:  Bug  |  supersteve9219
Component:  File |   Status:  assigned
  uploads/storage|  Version:  1.4
 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 supersteve9219):

 * cc: supersteve9219 (added)
 * owner:  nobody => supersteve9219
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16176: Overwriting a property with field during model inheritance.

[Django]

#16176: Overwriting a property with field during model inheritance.
-+-
 Reporter:  czepiel.artur@…  |Owner:
 Type:  Bug  |  Thomas_Moronez
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Thomas_Moronez):

 * owner:  nobody => Thomas_Moronez
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19619: BooleanField returning integer instead of Boolean

[Django]

#19619: BooleanField returning integer instead of Boolean
-+-
 Reporter:  brian|Owner:  anonymous
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 Thanks for reporting this but since it's fixed on master
 (f3a2bcdee906f7ca1434b6275fdc09b3a454cf46) and 1.5.X
 (f3a2bcdee906f7ca1434b6275fdc09b3a454cf46) I'll close as duplicate of
 #15040.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19619: BooleanField returning integer instead of Boolean

[Django]

#19619: BooleanField returning integer instead of Boolean
-+-
 Reporter:  brian|Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by marissaselfmadesf@…):

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


Comment:

 https://code.djangoproject.com/ticket/15040

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17008: makemessages too eager to cleanup, makes it hard to debug errors

[Django]

#17008: makemessages too eager to cleanup, makes it hard to debug errors
-+-
 Reporter:  airstrike|Owner:  airstrike
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  makemessages .pot|  checkin
  .po gettext xgettext translation   |  Needs documentation:  0
  debug  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by charettes):

 Maybe we could also add a release note about this new option.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15624: aggregate produces incorrect sql statement

[Django]

#15624: aggregate produces incorrect sql statement
-+-
 Reporter:  zeroos <232002@…>|Owner:
 Type:  Bug  |   Status:  new
Component:  ORM aggregation  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  aggregate sql| Triage Stage:  Accepted
  syntax error   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by stefano@…):

 Hello! Any news on that? I see there's a patch, now oldish, but nothing
 happened since and nobody from core has commented on it... is that patch a
 viable solution?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |Owner:  jakul
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Fixed on
 Keywords:  i18n makemessages|  a branch
  compilemessages|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Ramiro Morales ):

 In [changeset:"6158c79dbef832bc8530107ab2d34f04a04471da"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6158c79dbef832bc8530107ab2d34f04a04471da"
 Made (make|compile)messages commands accept multiple locales at once.

 Thanks Craig Blaszczyk for the initial patch. Refs #17181.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6158c7: Made (make|compile)messages commands accept multip...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6158c79dbef832bc8530107ab2d34f04a04471da
  
https://github.com/django/django/commit/6158c79dbef832bc8530107ab2d34f04a04471da
  Author: Craig Blaszczyk 
  Date:   2013-01-16 (Wed, 16 Jan 2013)

  Changed paths:
M AUTHORS
M django/core/management/commands/compilemessages.py
M django/core/management/commands/makemessages.py
M docs/ref/django-admin.txt
M tests/regressiontests/i18n/commands/compilation.py
M tests/regressiontests/i18n/commands/extraction.py
A tests/regressiontests/i18n/commands/locale/hr/LC_MESSAGES/django.po
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  Made (make|compile)messages commands accept multiple locales at once.

Thanks Craig Blaszczyk for the initial patch. Refs #17181.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 295650: Simplified i18n commands tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 295650bd01bc4d68e918b483a2366a092dae6636
  
https://github.com/django/django/commit/295650bd01bc4d68e918b483a2366a092dae6636
  Author: Ramiro Morales 
  Date:   2013-01-16 (Wed, 16 Jan 2013)

  Changed paths:
M tests/regressiontests/i18n/commands/compilation.py
M tests/regressiontests/i18n/commands/extraction.py

  Log Message:
  ---
  Simplified i18n commands tests.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19552: makemessages ignores translations in templates with inline comment tags

[Django]

#19552: makemessages ignores translations in templates with inline comment tags
-+-
 Reporter:  juneih@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.4
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  makemessages,|  checkin
  template, gettext, xgettext|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by ramiro):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19619: BooleanField returning integer instead of Boolean

[Django]

#19619: BooleanField returning integer instead of Boolean
-+-
 Reporter:  brian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by brian):

 So far it looks like the git master version does fix the problem.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16493: Windows: makemessages generate django.po should use forward slashes too (was: winodws: makemessages generate django.po should use forward slashes too)

[Django]

#16493: Windows:  makemessages generate django.po should use forward slashes too
-+-
 Reporter:  raidsan@…|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django]

[GitHub]

  Branch: refs/heads/create-pot-only-once
  Home:   https://github.com/django/django

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 248aee: Modified makemessages so it creates .pot files onc...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 248aee16066b2a336f16c844580cf043d853874b
  
https://github.com/django/django/commit/248aee16066b2a336f16c844580cf043d853874b
  Author: Ramiro Morales 
  Date:   2013-01-16 (Wed, 16 Jan 2013)

  Changed paths:
M django/core/management/commands/makemessages.py
M tests/regressiontests/i18n/commands/extraction.py

  Log Message:
  ---
  Modified makemessages so it creates .pot files once per invocation.

It creates a `locale/django.pot` file once instead of one
`locale//django.pot` file for every locale involved.

Thanks Michal Čihař for the report and patch.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ce308d: Fixed #17008 -- Added makemessages option to not r...

[GitHub]

  Branch: refs/heads/create-pot-only-once
  Home:   https://github.com/django/django
  Commit: ce308d7ead19c7af41acffe54fa271df1e01eae1
  
https://github.com/django/django/commit/ce308d7ead19c7af41acffe54fa271df1e01eae1
  Author: Ramiro Morales 
  Date:   2013-01-16 (Wed, 16 Jan 2013)

  Changed paths:
M django/core/management/commands/makemessages.py
M docs/ref/django-admin.txt
M tests/regressiontests/i18n/commands/extraction.py
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  Fixed #17008 -- Added makemessages option to not remove .pot files.


  Commit: 223d4a3151f24d8512a165dcae9347f9e2474e58
  
https://github.com/django/django/commit/223d4a3151f24d8512a165dcae9347f9e2474e58
  Author: Ramiro Morales 
  Date:   2013-01-16 (Wed, 16 Jan 2013)

  Changed paths:
M django/core/management/commands/makemessages.py
M tests/regressiontests/i18n/commands/extraction.py

  Log Message:
  ---
  Modified makemessages so it creates a locale/django.pot file once instead of 
a locale//django.pot for every locale involved.


Compare: https://github.com/django/django/compare/ce308d7ead19^...223d4a3151f2

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] eee865: Fixed #17008 -- Added makemessages option to not r...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: eee865257aaa9005947a7b4994c475c2ad59d698
  
https://github.com/django/django/commit/eee865257aaa9005947a7b4994c475c2ad59d698
  Author: Ramiro Morales 
  Date:   2013-01-16 (Wed, 16 Jan 2013)

  Changed paths:
M django/core/management/commands/makemessages.py
M docs/ref/django-admin.txt
M tests/regressiontests/i18n/commands/extraction.py
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  Fixed #17008 -- Added makemessages option to not remove .pot files.

Thanks airstrike for the report and initial patch, Julien for an
enhanced patch and Jannis for reviewing.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17008: makemessages too eager to cleanup, makes it hard to debug errors

[Django]

#17008: makemessages too eager to cleanup, makes it hard to debug errors
-+-
 Reporter:  airstrike|Owner:  airstrike
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  makemessages .pot|  checkin
  .po gettext xgettext translation   |  Needs documentation:  0
  debug  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"eee865257aaa9005947a7b4994c475c2ad59d698"]:
 {{{
 #!CommitTicketReference repository=""
 revision="eee865257aaa9005947a7b4994c475c2ad59d698"
 Fixed #17008 -- Added makemessages option to not remove .pot files.

 Thanks airstrike for the report and initial patch, Julien for an
 enhanced patch and Jannis for reviewing.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19620: Use ISO 8601 as default date format

[Django]

#19620: Use ISO 8601 as default date format
-+-
 Reporter:  vzima|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:   |  Version:  1.4
  Internationalization   |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by russellm):

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


Comment:

 This is one of those weird times where I completely 100% agree, but I'm
 going to close wontfix for practical reasons.

 As a non-USAsian, the MDY date format is annoying (as is, for example, the
 default Chicago timezone). However, changing default behaviour like this
 would cause major problems -- every existing Django project which is
 depending on the default behavior would break.

 Yes, the default is annoying, but it's a default, and it's easily
 changeable. Unless you are able to propose a way of phasing in this change
 in a backwards compatible way, it's unfortunately a non-starter.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19385: Add support for multiple-column join

[Django]

#19385: Add support for multiple-column join
-+-
 Reporter:  cseibert |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  join |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 Could you make a pull request? There are various pieces of code I'd like
 to comment on, and the best tool to do that is the github PR on-line
 commenting. (While at it, could you remove the whitespace errors, git diff
 --check is your friend here).

 I did spend already some time reviewing the code. I think the changes are
 mostly good, though there are a couple of issues I'd like to tackle, best
 reviewed in a PR.

 Also, I still think the ForeignKeyEx doesn't belong into contrib, it
 should be defined in a test module. It is a good test case to see we
 really have working multicolumn joins, but it is unlikely that such a
 field would be accepted to django contrib. A discussion at django-
 developers is needed at least.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19619: BooleanField returning integer instead of Boolean

[Django]

#19619: BooleanField returning integer instead of Boolean
-+-
 Reporter:  brian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by brian):

 Hmmm. Does seem very similar. Only I don't use select_related(...). Unless
 its use is somehow implicit.

 Looks like my code breaks under git master, so I am going to have to fix
 some of these problems before I can test this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19623: Update inlines.js to use jQuery 1.9

[Django]

#19623: Update inlines.js to use jQuery 1.9
-+-
 Reporter:  jordanorc|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  jquery admin | Triage Stage:
  inlines.js |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mlavin):

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


Comment:

 This is more or less the same issue reported in #19598 though this has a
 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17600: Error in encapsulates filters (Q)

[Django]

#17600: Error in encapsulates filters (Q)
-+-
 Reporter:  pmartin  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * stage:  Accepted => Ready for checkin


Comment:

 I have rebased the
 https://github.com/akaariai/django/tree/refactor_utils_tree and done some
 additions, too. The biggest one is that we now have build_filter() instead
 of add_filter() which will create a WhereNode object ready to be added to
 the tree. By doing this the wherenode/havingnode additions suddenly happen
 naturally in the _add_q without the need to pass the target clause down to
 add_filter. I like this way.

 There is also a new add_filter() which is just
 self.where.add(self.build_filter(filterexpr), AND) - that is, a little
 helper which is used in various places of the ORM.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19399: Do not recreate RelatedObject instances

[Django]

#19399: Do not recreate RelatedObject instances
-+-
 Reporter:  KJ   |Owner:  KJ
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by akaariai):

 Actually, if you have two subclasses of a Book and you try to use them in
 inlineformset_factory in the same view, wouldn't the ID names conflict
 when they didn't before? On this ground I think we need to not do the form
 changes.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19399: Do not recreate RelatedObject instances

[Django]

#19399: Do not recreate RelatedObject instances
-+-
 Reporter:  KJ   |Owner:  KJ
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by akaariai):

 I took a look at the patch. It looks otherwise good, but I can't see why
 the change in the model_formsets is correct. Not saying it isn't, I just
 can't see why it is. On a quick look it seems we are really changing
 semantics here - the form uses the plain fk to Book, while the user asked
 for AlternateBook.

 It seems this change has (small) potential for breaking existing code, so
 there should at least be a good reason to do so. My initial feeling is to
 not commit this part of the code.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9800: Syndication Framework could implement isPermaLink": "false" to better follow the recommendations of the RSS Advisory Board

[Django]

#9800: Syndication Framework could implement isPermaLink": "false"  to better
follow the recommendations of the RSS Advisory Board
-+
 Reporter:  martin |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  contrib.syndication  |  Version:  master
 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 rtnpro):

 * cc: rtnpro (added)


Comment:

 Added support for 'isPermalink' attribute in a  element for an item
 in an RSS feed.

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

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19582: Add tutorial on static files

[Django]

#19582: Add tutorial on static files
--+
 Reporter:  jpic  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  docs, static files| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by alecperkins@…):

 I took a stab at rewriting the first part of the
 
[https://github.com/alecperkins/django/blob/60362cf7fda8d0ea3b190d2f7c66f84ac3273c3d/docs/howto
 /static-files.txt static files howto] ([http://show-
 em.net/b0595da44fc4302ab4d4/howto/static-files.html rendered]). This was
 based on, for the first time in literally years, trying to set up static
 files from scratch and finally wrapping my head around it.

 For those coming at staticfiles with the expectation of "put files in this
 folder, they get served at this URL", the app-specific static files idea
 is confusing. This rewrite makes it more clear what's necessary to get
 that outcome, and explain why the process is the way it 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17008: makemessages too eager to cleanup, makes it hard to debug errors

[Django]

#17008: makemessages too eager to cleanup, makes it hard to debug errors
-+-
 Reporter:  airstrike|Owner:  airstrike
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  makemessages .pot|  checkin
  .po gettext xgettext translation   |  Needs documentation:  0
  debug  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by ramiro):

 See https://github.com/ramiro/django/compare/17008-keep-pot for a
 refreshed patch.

 Thanks Jannis for remebering about this ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19624: Generic Detail View context contains object twice.

[Django]

#19624: Generic Detail View context contains object twice.
--+--
 Reporter:  mail@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Generic views |Version:  1.5-beta-1
 Severity:  Normal|   Keywords:  generic view
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 The (simplified and commented) code excerpt below, taken from
 django/views/generic/detail.py shows that the object is put into context
 twice, under different keywords. Is this intentional?

 The whole construction is most certainly not elegant and makes inheriting
 from SingleObjectMixin somewhat cumbersome as I have to explicitely set
 self.object if I don't have BaseDetailView in my class inheritance or
 override BaseDetailView.get()

 {{{
 #!python
 class SingleObjectMixin(ContextMixin):
 def get_context_data(self, **kwargs):
 # this puts self.object into context under keyword
 context_object_name
 context[context_object_name] = self.object
 context.update(kwargs)
 return super(SingleObjectMixin, self).get_context_data(**context)

 class BaseDetailView(SingleObjectMixin, View):
 def get(self, request, *args, **kwargs):
 # this puts self.object into context under 'object' --> is this
 redundancy intentional?
 self.object = self.get_object()
 context = self.get_context_data(object=self.object)
 return self.render_to_response(context)
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19623: Update inlines.js to use jQuery 1.9

[Django]

#19623: Update inlines.js to use jQuery 1.9
---+-
 Reporter:  jordanorc  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:  jquery admin inlines.js
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+-
 On line 44 in inlines.js, we have the code:
 {{{
 $(this).attr("tagName") == "TR"
 }}}
 In jQuery version 1.9, this code doesn't works.

 Is better to do:
 {{{
 $(this).is("tr")
 }}}

 So, it works on jQuery 1.4.2 and jQuery 1.9

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17854: Problem with DecimalField and big vlues of max_digits, decimal_places, sqlite3 backend

[Django]

#17854: Problem with DecimalField and big vlues of max_digits, decimal_places,
sqlite3 backend
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  DecimalField bug |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by wdoekes):

 I was assuming the problem is the same as the one I encountered. But
 perhaps this belongs in a different ticket.

 The decimal type is cast as string when constructing a query. But for
 larger values, MySQL doesn't cast the string to decimal properly. Instead
 it becomes a lossy float.

 That means you get this:
 {{{
 mysql> select 12345678901234567 as value, convert('12345678901234567' +
 0.0, decimal(31,0)) as truncated_value;
 +---+---+
 | value | truncated_value   |
 +---+---+
 | 12345678901234567 | 12345678901234570 |
 +---+---+
 1 row in set (0.01 sec)
 }}}

 When looking up a value, then comparison fails.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17008: makemessages too eager to cleanup, makes it hard to debug errors

[Django]

#17008: makemessages too eager to cleanup, makes it hard to debug errors
-+-
 Reporter:  airstrike|Owner:  airstrike
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  makemessages .pot|  checkin
  .po gettext xgettext translation   |  Needs documentation:  0
  debug  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by jezdez):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17854: Problem with DecimalField and big vlues of max_digits, decimal_places, sqlite3 backend

[Django]

#17854: Problem with DecimalField and big vlues of max_digits, decimal_places,
sqlite3 backend
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  DecimalField bug |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by wdoekes):

 * cc: wdoekes (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

[Django]

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |  Needs documentation:  1
  admin  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by 4glitch@…):

 * cc: 4glitch@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19622: can't create superuser

[Django]

#19622: can't create superuser
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

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


Comment:

 If you are getting a hashcompat DeprecationWarning, you are probably not
 running 1.5rc1. In any case, a full traceback would be required, but
 please, use support channel first.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19619: BooleanField returning integer instead of Boolean

[Django]

#19619: BooleanField returning integer instead of Boolean
-+-
 Reporter:  brian|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lukeplant):

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


Comment:

 This looks very similar to #15040, or at least could be fixed by the fix
 for that. Does this still happen with 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19616: QuerySet.__contains__ tries to check the length of a None

[Django]

#19616: QuerySet.__contains__ tries to check the length of a None
-+-
 Reporter:  kalugny@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Old description:

> This is the code from QuerySet (version 1.42).
> As you can see by the lines I've bolded, although _result_cache might be
> None, it is still being checked for len()
>
> def __contains__(self, val):
> # The 'in' operator works without this method, due to __iter__.
> This
> # implementation exists only to shortcut the creation of Model
> # instances, by bailing out early if we find a matching element.
> pos = 0
> '''if self._result_cache is not None:'''
> if val in self._result_cache:
> return True
> elif self._iter is None:
> # iterator is exhausted, so we have our answer
> return False
> # remember not to check these again:
> pos = len(self._result_cache)
> '''else:'''
> # We need to start filling the result cache out. The
> following
> # ensures that self._iter is not None and self._result_cache
> is not
> # None
> it = iter(self)
>
> # Carry on, one result at a time.
> while True:
>''' if len(self._result_cache) <= pos:'''
> self._fill_cache(num=1)

New description:

 This is the code from QuerySet (version 1.42).
 As you can see by the lines I've bolded, although _result_cache might be
 None, it is still being checked for len()
 {{{
 def __contains__(self, val):
 # The 'in' operator works without this method, due to __iter__.
 This
 # implementation exists only to shortcut the creation of Model
 # instances, by bailing out early if we find a matching element.
 pos = 0
 if self._result_cache is not None:
 if val in self._result_cache:
 return True
 elif self._iter is None:
 # iterator is exhausted, so we have our answer
 return False
 # remember not to check these again:
 pos = len(self._result_cache)
 else:
 # We need to start filling the result cache out. The following
 # ensures that self._iter is not None and self._result_cache
 is not
 # None
 it = iter(self)

 # Carry on, one result at a time.
 while True:
if len(self._result_cache) <= pos:
 self._fill_cache(num=1)
 }}}

--

Comment (by lukeplant):

 Looking at the code and the comments in the `else` branch, it actually
 seems very obvious that the function has covered it's bases about whether
 self._result_cache is `None` or not. We need either some further analysis
 as to why it is wrong, or a simple test case that ought to work.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19622: can't create superuser

[Django]

#19622: can't create superuser
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 1.5 rc1
 database:mysql

 manage.py createsuperuser
 D:\Python27\lib\site-packages\django\utils\hashcompat.py:9:
 DeprecationWarning:
 django.utils.hashcompat is deprecated; use hashlib instead
   DeprecationWarning)

 UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-1:
 ordin
 al not in range(128)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19621: templates suppress TypeErrors from comparisons

[Django]

#19621: templates suppress TypeErrors from comparisons
-+
 Reporter:  leftmoose|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 even with {{{ TEMPLATE_DEBUG = True }}},

 passing e.g. a {{{ DateTime }}} to a template and doing {{{ {% if now > 2
 %} }}} is silently coerced to false, rather than raising the {{{ TypeError
 }}}

 (in my case it was slightly less obvious, accidentally comparing naive and
 a time zone aware datetimes)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19620: Use ISO 8601 as default date format

[Django]

#19620: Use ISO 8601 as default date format
--+
 Reporter:  vzima |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Internationalization  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Only USA use format with reversed day and month whereas most of the world
 uses either DMY or YMD formats which are easy to distinguish from each
 other, see [http://en.wikipedia.org/wiki/Date_format_by_country#Map].

 I suggest to use ISO 8601 (or like) format as default, because current
 default `en_us` formats are confusing for most of the world. ISO format is
 well understood around the world and should not cause any confusion.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9800: Syndication Framework could implement isPermaLink": "false" to better follow the recommendations of the RSS Advisory Board

[Django]

#9800: Syndication Framework could implement isPermaLink": "false"  to better
follow the recommendations of the RSS Advisory Board
-+
 Reporter:  martin |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  contrib.syndication  |  Version:  master
 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 mpessas):

 * cc: mpessas@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.