Re: [Django] #18995: String formatting error when passing floats as values in {% blocktrans %} tags

[Django]

#18995: String formatting error when passing floats as values in {% blocktrans 
%}
tags
--+
 Reporter:  brutasse  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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
--+

Comment (by julien):

 I've done some digging and found that the issue isn't to do with floats.
 In fact, `ungettext` will happily work with floats without raising any
 exceptions.

 The root of the problem is that `floatformat` returns a string, which
 conflicts with the Russian plural rules. Indeed, those rules use the
 modulo sign `%`:

 {{{
 "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 &&
 n"
 "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
 }}}

 If you pass a string as a value for `n`, then the `%` sign will operate as
 string formatting instead of a modulo, therefore causing the `TypeError`.
 The same effect can be easily reproduced as follows:

 {{{
 >>> '123' % 10
 *** TypeError: not all arguments converted during string formatting
 }}}

 I suggest making `blocktrans` raise an exception upstream if the value
 provided for the counter is not a number.

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

[django/django] 0d0ccf: Moved a release note that I had accidentally mispl...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0d0ccf81a0c18f42866d914672469f720861988a
  
https://github.com/django/django/commit/0d0ccf81a0c18f42866d914672469f720861988a
  Author: Julien Phalip 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M docs/releases/1.6.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  Moved a release note that I had accidentally misplaced in bb145e2c47d71.



-- 
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/51f48795e86b3_239f695d4898998%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4e0ff3: Fixed #11195 -- Added CSS classes to the changelis...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4e0ff351466fc2d74cc8d1d40ea78da2b3859d0d
  
https://github.com/django/django/commit/4e0ff351466fc2d74cc8d1d40ea78da2b3859d0d
  Author: Julien Phalip 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M docs/releases/1.7.txt
M tests/admin_changelist/tests.py
M tests/admin_views/tests.py

  Log Message:
  ---
  Fixed #11195 -- Added CSS classes to the changelist cells to allow style 
customizations. Thanks to akaihola, Ramiro Morales and vdboor for their work on 
the patch.



-- 
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/51f4870b2e767_9d6d11d4878997%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11195: add fieldname to admin changelist tags -- eases CSS customization

[Django]

#11195: add fieldname to admin changelist  tags -- eases CSS customization
---+
 Reporter:  akaihola   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  css| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Julien Phalip ):

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


Comment:

 In [changeset:"4e0ff351466fc2d74cc8d1d40ea78da2b3859d0d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4e0ff351466fc2d74cc8d1d40ea78da2b3859d0d"
 Fixed #11195 -- Added CSS classes to the changelist cells to allow style
 customizations. Thanks to akaihola, Ramiro Morales and vdboor for their
 work on the 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/066.2f66d66aabf4e1675e862f4b077dce8b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20649: Add an easier way to override the blank option for CharFields with choices

[Django]

#20649: Add an easier way to override the blank option for CharFields with 
choices
-+--
 Reporter:  brillgen |Owner:  alexcouper
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by alexcouper):

 * needs_docs:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a76d73905ed1a6aa9e95dfcc421a4a9b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 47c755: Fixed a number of minor misspellings.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 47c755327be9a3b976f5f78fc21f336f27aa6413
  
https://github.com/django/django/commit/47c755327be9a3b976f5f78fc21f336f27aa6413
  Author: Julien Phalip 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M django/contrib/admin/filters.py
M django/contrib/formtools/wizard/views.py
M django/contrib/gis/geoip/prototypes.py
M django/core/management/__init__.py
M django/core/management/commands/dumpdata.py
M django/db/backends/oracle/compiler.py
M django/db/backends/sqlite3/base.py
M django/db/models/fields/__init__.py
M docs/howto/initial-data.txt
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/staticfiles.txt
M docs/ref/django-admin.txt
M docs/ref/models/instances.txt
M docs/releases/1.2.1.txt
M docs/releases/1.5-beta-1.txt
M docs/topics/class-based-views/mixins.txt
M docs/topics/db/transactions.txt
M docs/topics/http/sessions.txt
M docs/topics/http/urls.txt
M docs/topics/testing/advanced.txt
M docs/topics/testing/overview.txt
M tests/custom_managers/tests.py
M tests/forms_tests/tests/test_forms.py
M tests/model_formsets/tests.py
M tests/queries/tests.py
M tests/servers/tests.py
M tests/settings_tests/tests.py
M tests/template_tests/test_response.py

  Log Message:
  ---
  Fixed a number of minor misspellings.



-- 
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/51f4780d26261_23861147d548811d%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ca39c0: Fixed #18404 -- Added test for AppStaticStorage wi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ca39c0a6becf497880181b3a5ef6db84130f9723
  
https://github.com/django/django/commit/ca39c0a6becf497880181b3a5ef6db84130f9723
  Author: Florian Hahn 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  Fixed #18404 -- Added test for AppStaticStorage with non ascii path

(bug was already fixed in #19357)



-- 
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/51f463883c02b_670b125bd5863724%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18404: SuspiciousOperation exception is thrown if application static path contains non-ascii characters

[Django]

#18404: SuspiciousOperation exception is thrown if application static path 
contains
non-ascii characters
-+
 Reporter:  andkit@… |Owner:  fhahn
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sprint2013   | Triage Stage:  Accepted
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:"ca39c0a6becf497880181b3a5ef6db84130f9723"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ca39c0a6becf497880181b3a5ef6db84130f9723"
 Fixed #18404 -- Added test for AppStaticStorage with non ascii path

 (bug was already fixed in #19357)
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.14fd5b8686986069022ab8755824d8bc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] dd2a51: [1.5.x] assertEquals -> assertEqual

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: dd2a512f68fc61d10577f21a4dc367202b58fc08
  
https://github.com/django/django/commit/dd2a512f68fc61d10577f21a4dc367202b58fc08
  Author: Tim Graham 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  [1.5.x] assertEquals -> assertEqual



-- 
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/51f44dfc7dd67_6653b2fd5495142%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19607: prefetch_related crash

[Django]

#19607: prefetch_related crash
-+-
 Reporter:  av@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch |  Unreviewed
  prefetch_related   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"00b39e0145c5b9117503b20bba74948294a30e5a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="00b39e0145c5b9117503b20bba74948294a30e5a"
 [1.5.x] Fixed #19607 - prefetch_related crash

 Thanks to a...@rdf.ru and flarn...@yahoo.de for the report.

 Backport of 4fd94969d8 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.33d344fdb1a89c5b604c7427acd55db9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 00b39e: [1.5.x] Fixed #19607 - prefetch_related crash

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 00b39e0145c5b9117503b20bba74948294a30e5a
  
https://github.com/django/django/commit/00b39e0145c5b9117503b20bba74948294a30e5a
  Author: Luke Plant 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M django/db/models/query.py
M tests/modeltests/prefetch_related/models.py
M tests/modeltests/prefetch_related/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #19607 - prefetch_related crash

Thanks to a...@rdf.ru and flarn...@yahoo.de for the report.

Backport of 4fd94969d8 from master


  Commit: a2eb2195567e645c58ec20c382294b62640b9ea1
  
https://github.com/django/django/commit/a2eb2195567e645c58ec20c382294b62640b9ea1
  Author: Luke Plant 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M django/db/models/query.py

  Log Message:
  ---
  [1.5.x] Optimisation in prefetch_related_objects

Backport of 17559e6eb0 from master


Compare: https://github.com/django/django/compare/93564959365f...a2eb2195567e

-- 
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/51f44d84afffa_697b2bd582207e%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20815: daemonize.py: unbuffered text IO error (python3)

[Django]

#20815: daemonize.py: unbuffered text IO error (python3)
+--
 Reporter:  alex01@…|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Python 3|Version:  master
 Severity:  Normal  |   Keywords:  python3 runfcgi open
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 When trying to run fcgi server I get "ValueError: can't have unbuffered
 text I/O"

 My python version and django version:

 $ python --version
 Python 3.2.3

 >>> django.get_version()
 '1.7.dev20130726184538'

 Can't start server:
 (virtenv02)jsmith@thinkpad01:~/virtenv02/mysite$ python manage.py runfcgi
 host=127.0.0.1 port=8100
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/__init__.py", line 397, in
 execute_from_command_line
 utility.execute()
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/__init__.py", line 390, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/base.py", line 240, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/base.py", line 283, in execute
 output = self.handle(*args, **options)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/commands/runfcgi.py", line 22, in handle
 runfastcgi(args)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/servers/fastcgi.py", line 176, in runfastcgi
 become_daemon(our_home_dir=options["workdir"], **daemon_kwargs)
   File "/home/jsmith/virtenv02/django-trunk/django/utils/daemonize.py",
 line 28, in become_daemon
 so = open(out_log, 'a+', 0)
 ValueError: can't have unbuffered text I/O

 Server starts successfully and works if I give it daemonize=False option:
 (virtenv02)jsmith@thinkpad01:~/virtenv02/mysite$ python manage.py runfcgi
 host=127.0.0.1 port=8100 daemonize=False

 As far as I understand, this issue is specific to python3 and is related
 to changes in open function introduced in pep-3116

 Alex

-- 
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/059.071525e507e727544ce289bb8495b7ed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20814: model validation: misleading error message with model inheritance

[Django]

#20814: model validation: misleading error message with model inheritance
--+
 Reporter:  shai  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  model-
 Triage Stage:  Unreviewed|  validation check
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 Consider this little set of models. The idea is that there are "general"
 objects, but some of them are special: Each of the special objects holds
 pointers to other objects.

 {{{#!python
 class General(models.Model):
 name = models.CharField(max_length=30)

 class Special(General):
 pass

 class SpecialDetail(models.Model):
 parent = models.ForeignKey(Special)
 target = models.ForeignKey(General)
 }}}

 Model validation fails (as it should), but the error message is
 {{{
 specialdetail: accessor for field 'parent' clashes with
 'Special.specialdetail_set'
 }}}
 when in fact the clash is with `General.specialdetail_set` generated by
 the `target` field (and inherited by `Special`). Of course, when isolated
 like this, it is very easy to spot where the real problem is, but when the
 models have a little more content in them, this can be (and actually was)
 quite perplexing.

-- 
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/047.f78e9f383402a1e3a208d1edca455636%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18511: Admin Site: Error Message displays different for Changeforms and the Password Change screen.

[Django]

#18511: Admin Site: Error Message displays different for Changeforms and the
Password Change screen.
-+-
 Reporter:  serge_spaolonzi  |Owner:
 Type:   |  serge_spaolonzi
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e07e4030b9170d522a9670a80c4fd40acff369cb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e07e4030b9170d522a9670a80c4fd40acff369cb"
 Fixed #18511 -- Cleaned up admin password reset template titles.
 }}}

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

[django/django] e07e40: Fixed #18511 -- Cleaned up admin password reset te...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e07e4030b9170d522a9670a80c4fd40acff369cb
  
https://github.com/django/django/commit/e07e4030b9170d522a9670a80c4fd40acff369cb
  Author: Serge G. Spaolonzi 
  Date:   2013-07-27 (Sat, 27 Jul 2013)

  Changed paths:
M django/contrib/admin/templates/registration/password_change_done.html
M django/contrib/admin/templates/registration/password_change_form.html
M django/contrib/admin/templates/registration/password_reset_complete.html
M django/contrib/admin/templates/registration/password_reset_confirm.html
M django/contrib/admin/templates/registration/password_reset_done.html
M django/contrib/admin/templates/registration/password_reset_form.html
A django/contrib/auth/tests/test_templates.py
M django/contrib/auth/views.py

  Log Message:
  ---
  Fixed #18511 -- Cleaned up admin password reset template titles.



-- 
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/51f4103e74ceb_65910ffd4c4155f%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20774: Update the localflavor topic guide when django-localflavor is ready

[Django]

#20774: Update the localflavor topic guide when django-localflavor is ready
--+
 Reporter:  loic84|Owner:  jezdez
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  localflavor   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timo):

 Also probably a good idea to update the deprecation warning in
 `django.contrib.localflavor` to point to the new package instead of "the
 separate django-localflavor-* packages".

-- 
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.72ca0f9c99de2c9859d2b0739fb1a058%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20813: max_length incorrectly passed to MultiValueField-derived class

[Django]

#20813: max_length incorrectly passed to MultiValueField-derived class
-+-
 Reporter:  george_edison|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 You should either define your init method like this: `def __init__(self,
 fields, max_length=None, *args, **kwargs)` or pop the value in `**kwargs`
 (`self.max_length = kwargs.pop('max_length', None)`). See existing code in
 `django/forms/fields.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/071.484e2d4ca1cb2ee6967a662c636902ad%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20809: Python 2.7.3 Django 1.5.1 QueryDict.urlencode returns unicode

[Django]

#20809: Python 2.7.3 Django 1.5.1 QueryDict.urlencode returns unicode
---+--
 Reporter:  stargrave@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.5
 Severity:  Normal |   Resolution:  worksforme
 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 stargrave@…):

 Ah, I see. Thank you very much for the pointer! So we will use Django's
 built-in wrappers.

-- 
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/081.ea377f85a0e41c5c01e1ac70aff33bbd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20809: Python 2.7.3 Django 1.5.1 QueryDict.urlencode returns unicode

[Django]

#20809: Python 2.7.3 Django 1.5.1 QueryDict.urlencode returns unicode
---+--
 Reporter:  stargrave@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.5
 Severity:  Normal |   Resolution:  worksforme
 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
 * resolution:   => worksforme
 * component:  Core (Other) => HTTP handling


Comment:

 Thanks for explaining your use case, this is valuable.

 I think the error in the above example is to use Python standard `urllib`
 which is not unicode friendly (on Python 2). That's why Django is
 providing wrappers for most of these functions in `django.utils.http`
 (https://docs.djangoproject.com/en/dev/ref/utils/#module-
 django.utils.http):
 {{{
 >>> from django.utils.http import urlunquote_plus
 >>> urlunquote_plus(ENCODED)
 u'hello=\u043f\u0440\u0438\u0432\u0435\u0442'
 }}}

 In Python 3, we should be able to use the standard library again:
 {{{
 >>> q = QueryDict({}, mutable=True)
 >>> q["hello"] = "привет"
 >>> q.urlencode()
 'hello=%D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82'
 >>> from urllib import parse
 >>> parse.unquote_plus(q.urlencode())
 'hello=привет'
 }}}

-- 
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/081.7645ef51d26ba2b6c83d892a32514708%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20768: Create a reference of public Manager methods

[Django]

#20768: Create a reference of public Manager methods
---+
 Reporter:  ramiro |Owner:  nobody
 Type:  New feature|   Status:  new
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
---+

Comment (by loic84):

 IMO `ref/models/managers.txt` should take over a fair chunk from the topic
 guide `topics/db/managers.txt`.

 The reference would include the stock `Manager` methods and attributes and
 everything one needs to know about '''using''' managers (either the stock
 `Manager` or subclasses like `CurrentSiteManager`). I suggest the
 following:

 - A section about `QuerySet` methods. I'm not sure if we should list them
 all or just mention that all `QuerySet` public methods but `delete()` are
 available from `Manager`.
 - Reference the `from_queryset()`, `get_queryset()`, `raw()` methods and
 the `model`, `db`, `use_for_related_fields` attributes.
 - Get "Manager names" from the topic guide.
 - Split "Modifying initial Manager QuerySets" from the topic guide into
 two parts, one that goes within the `get_queryset()` definition and the
 other one into a new section "Using multiple managers on the same model".
 - Get "Custom managers and model inheritance" from the topic guide.

 The topic guide would then stick to the ins and outs of creating a custom
 Manager:

 - "Calling custom QuerySet methods from the Manager"
 - "Creating Manager with QuerySet methods" (linked from
 `Manager.from_queryset` and `QuerySet.as_manager`)
 - A new section about creating a `Manager` by compositing `QuerySets` like
 the example in
 https://github.com/django/django/pull/1328#issuecomment-21439470
 - "Implementation concerns"
 - "Controlling automatic Manager types" (Linked from
 `Manager.use_for_related_fields`)
 - "Writing correct Managers for use in automatic Manager instances"
 (Linked from `Manager.use_for_related_fields`)

 While we are at it, we should remove the Male/Female distinction from the
 examples.

 Feedback welcome.

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

Re: [Django] #19607: prefetch_related crash

[Django]

#19607: prefetch_related crash
-+-
 Reporter:  av@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch |  Unreviewed
  prefetch_related   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ppetrid):

 I would also appreciate merging this fix into Django 1.5.x

-- 
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.0460f2ab72f56e230a26c103d5bb162d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.