date:20130215

Re: [Django] #14881: [nonrel] Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

2013-02-15 Thread Django

#14881: [nonrel] Do not assume ``User.id`` to be an integer in
django.contrib.auth's pasword reset feature
--+
 Reporter:  jonash|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  nonrel| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Russell Keith-Magee ):

 In [changeset:"461d6e22957770449cd99367358c5e419bc3a86d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="461d6e22957770449cd99367358c5e419bc3a86d"
 [1.5.x] Refs #14881 -- Document that User models need to have an integer
 primary key.

 Thanks to Kaloian Minkov for the reminder about this undocumented
 requirement.

 (cherry picked from commit 91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4)
 }}}

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

[django/django] 461d6e: [1.5.x] Refs #14881 -- Document that User models n...

2013-02-15 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 461d6e22957770449cd99367358c5e419bc3a86d
  
https://github.com/django/django/commit/461d6e22957770449cd99367358c5e419bc3a86d
  Author: Russell Keith-Magee 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  [1.5.x] Refs #14881 -- Document that User models need to have an integer 
primary key.

Thanks to Kaloian Minkov for the reminder about this undocumented requirement.

(cherry picked from commit 91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4)



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

Re: [Django] #14881: [nonrel] Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

2013-02-15 Thread Django

#14881: [nonrel] Do not assume ``User.id`` to be an integer in
django.contrib.auth's pasword reset feature
--+
 Reporter:  jonash|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  nonrel| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Russell Keith-Magee ):

 In [changeset:"91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4"
 Refs #14881 -- Document that User models need to have an integer primary
 key.

 Thanks to Kaloian Minkov for the reminder about this undocumented
 requirement.
 }}}

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

[django/django] 91c26e: Refs #14881 -- Document that User models need to h...

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4
  
https://github.com/django/django/commit/91c26eadc9b4efa5399ec0f6c84b56a3f8eb84f4
  Author: Russell Keith-Magee 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  Refs #14881 -- Document that User models need to have an integer primary key.

Thanks to Kaloian Minkov for the reminder about this undocumented requirement.



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

Re: [Django] #19833: Django's test framework fails when using unicode strings in settings.py

2013-02-15 Thread Django

#19833: Django's test framework fails when using unicode strings in settings.py
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  unicode, test| Triage Stage:  Accepted
  runner, py3k   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dbrgn):

 Yes, `force_str` solves the issue in this case.

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

Re: [Django] #19825: URLValidator

2013-02-15 Thread Django

#19825: URLValidator
-+-
 Reporter:  agestart@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  urlvalidator url | Triage Stage:
  field validator|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akiala):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19833: Django's test framework fails when using unicode strings in settings.py

2013-02-15 Thread Django

#19833: Django's test framework fails when using unicode strings in settings.py
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  unicode, test| Triage Stage:  Accepted
  runner, py3k   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by claudep):

 I wonder if your test runner path is correct. Try to use
 `force_str(test_path[-1])` and see if you are not getting an
 `AttributeError`. In any case, I admit the `AttributeError` is more
 friendly than the `TypeError`, so let's go for this change (waiting for
 your tests, still).

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

[django/django] 5a803c: [1.5.x] Fixed geos test to prevent random failure

2013-02-15 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5a803ce10ef0c1b3777fb781d6feba72610c4265
  
https://github.com/django/django/commit/5a803ce10ef0c1b3777fb781d6feba72610c4265
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/gis/geos/tests/test_geos.py

  Log Message:
  ---
  [1.5.x] Fixed geos test to prevent random failure

Points in the test fixtures have 20 as max coordinate.
Backport of 87854b0bdf3 from master.



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

[django/django] 87854b: Fixed geos test to prevent random failure

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 87854b0bdf354059f949350a4d63a0ed071d564c
  
https://github.com/django/django/commit/87854b0bdf354059f949350a4d63a0ed071d564c
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/gis/geos/tests/test_geos.py

  Log Message:
  ---
  Fixed geos test to prevent random failure

Points in the test fixtures have 20 as max coordinate.



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

Re: [Django] #19812: Duplicate phrase in documentation of MultiWidget

2013-02-15 Thread Django

#19812: Duplicate phrase in documentation of MultiWidget
-+-
 Reporter:  diegueus9|Owner:
 Type:   |  itsallvoodoo
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.5-rc-1
 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 itsallvoodoo):

 I am sorry, going through the learning process here. Thanks for pointing
 that out.

 Pull request link:
 [https://github.com/django/django/pull/727]

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

Re: [Django] #19828: "How to contribute to Django" points to a removed page

2013-02-15 Thread Django

#19828: "How to contribute to Django" points to a removed page
-+-
 Reporter:  jonathanl|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


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

Re: [Django] #19828: "How to contribute to Django" points to a removed page

2013-02-15 Thread Django

#19828: "How to contribute to Django" points to a removed page
-+-
 Reporter:  jonathanl|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 Fixed. Thanks for reporting 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19833: Django's test framework fails when using unicode strings in settings.py

2013-02-15 Thread Django

#19833: Django's test framework fails when using unicode strings in settings.py
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  unicode, test| Triage Stage:  Accepted
  runner, py3k   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dbrgn):

 Sorry for forgetting about the traceback, here it is:

 {{{
 $ cat config/settings.py | grep TEST_
 TEST_RUNNER = 'discover_runner.DiscoverRunner'
 TEST_DISCOVER_TOP_LEVEL = PROJECT_ROOT
 TEST_DISCOVER_ROOT = PROJECT_ROOT
 TEST_DISCOVER_PATTERN = 'test*.py'

 $ ./manage.py test
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/danilo/.virtualenvs/pcf/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 453, in
 execute_from_command_line
 utility.execute()
   File "/home/danilo/.virtualenvs/pcf/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 392, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/danilo/.virtualenvs/pcf/lib/python2.7/site-
 packages/django/core/management/commands/test.py", line 49, in
 run_from_argv
 super(Command, self).run_from_argv(argv)
   File "/home/danilo/.virtualenvs/pcf/lib/python2.7/site-
 packages/django/core/management/base.py", line 218, in run_from_argv
 parser = self.create_parser(argv[0], argv[1])
   File "/home/danilo/.virtualenvs/pcf/lib/python2.7/site-
 packages/django/core/management/commands/test.py", line 52, in
 create_parser
 test_runner_class = get_runner(settings, self.test_runner)
   File "/home/danilo/.virtualenvs/pcf/lib/python2.7/site-
 packages/django/test/utils.py", line 129, in get_runner
 test_module = __import__(test_module_name, {}, {}, test_path[-1])
 TypeError: Item in ``from list'' not a string
 }}}

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

Re: [Django] #19833: Django's test framework fails when using unicode strings in settings.py

2013-02-15 Thread Django

#19833: Django's test framework fails when using unicode strings in settings.py
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  unicode, test| Triage Stage:  Accepted
  runner, py3k   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by dbrgn):

 So `django.utils.encoding.force_str(test_path[-1])` would be an acceptable
 solution? If yes, I'll provide a pull request on Github.

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

Re: [Django] #19828: "How to contribute to Django" points to a removed page

2013-02-15 Thread Django

#19828: "How to contribute to Django" points to a removed page
-+-
 Reporter:  jonathanl|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by jonathanl):

 Sorry claude, I found the broken link at
 https://code.djangoproject.com/#Gettinginvolved

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

Re: [Django] #19834: Bad index entries in the documentation section

2013-02-15 Thread Django

#19834: Bad index entries in the documentation section
-+-
 Reporter:  matthias@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Djangoproject.com|   Resolution:  fixed
  Web site   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  docs broken link |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Documentation => Djangoproject.com Web site
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 The fix is deployed. Thanks for taking the time to report this bug.

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

Re: [Django] #19834: Bad index entries in the documentation section

2013-02-15 Thread Django

#19834: Bad index entries in the documentation section
--+
 Reporter:  matthias@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  1.4
 Severity:  Normal| Resolution:  fixed
 Keywords:  docs broken link  |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In
 [changeset:"28cfdc6039875b74cfd7d2cbe67c8a7a48a11991/djangoproject.com"]:
 {{{
 #!CommitTicketReference repository="djangoproject.com"
 revision="28cfdc6039875b74cfd7d2cbe67c8a7a48a11991"
 Fix #19834 -- Adapt to Sphinx' new genindex JSON.
 }}}

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

Re: [Django] #19832: DecimalField validation shoud use plural forms

2013-02-15 Thread Django

#19832: DecimalField validation shoud use plural forms
-+-
 Reporter:  clay.evil@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  DecimalField | Triage Stage:  Accepted
  validation |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by clay.evil@…):

 Yes, I know its annoying, but devil is in the detail, and since Django
 uses plural forms in many parts, this will add to Django's perfection.
 I'm very happy that i can use Django, you have done a very very good &
 great & marvelous job. Thank you all. I'm coding right now, so i just felt
 the need to thank you.

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

Re: [Django] #19833: Django's test framework fails when using unicode strings in settings.py

2013-02-15 Thread Django

#19833: Django's test framework fails when using unicode strings in settings.py
-+-
 Reporter:  dbrgn|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  unicode, test| Triage Stage:  Accepted
  runner, py3k   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by claudep):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 > Are there any helper functions in Django to do a conversion that works
 both in py2 and py3 (str() vs bytes())?

 Yes, see `django.utils.encoding.force_str`

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

Re: [Django] #17840: Overriding form field error messages without argument causes string formatting error.

2013-02-15 Thread Django

#17840: Overriding form field error messages without argument causes string
formatting error.
+
 Reporter:  klein4  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.3
 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 claudep):

 See also #19832

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

Re: [Django] #19832: DecimalField validation shoud use plural forms

2013-02-15 Thread Django

#19832: DecimalField validation shoud use plural forms
-+-
 Reporter:  clay.evil@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  DecimalField | Triage Stage:  Accepted
  validation |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I guess you are targeting those strings:
 {{{
 'max_digits': _('Ensure that there are no more than %s digits in
 total.'),
 'max_decimal_places': _('Ensure that there are no more than %s decimal
 places.'),
 'max_whole_digits': _('Ensure that there are no more than %s digits
 before the decimal point.')
 }}}

 #17840 is related.

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

Re: [Django] #17066: Exception TypeError when using GeoIP

2013-02-15 Thread Django

#17066: Exception TypeError when using GeoIP
+-
 Reporter:  mitar   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.4
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"35185495e3f70f900b542bf95d744f51e5c5cb92"]:
 {{{
 #!CommitTicketReference repository=""
 revision="35185495e3f70f900b542bf95d744f51e5c5cb92"
 Fixed #17066 -- Prevented TypeError in GeoIP.__del__

 When garbaging GeoIP instances, it happens that GeoIP_delete is
 already None.
 Thanks mitar for the report and stefanw for tests.
 }}}

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

[django/django] 351854: Fixed #17066 -- Prevented TypeError in GeoIP.__del...

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 35185495e3f70f900b542bf95d744f51e5c5cb92
  
https://github.com/django/django/commit/35185495e3f70f900b542bf95d744f51e5c5cb92
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/gis/geoip/base.py

  Log Message:
  ---
  Fixed #17066 -- Prevented TypeError in GeoIP.__del__

When garbaging GeoIP instances, it happens that GeoIP_delete is
already None.
Thanks mitar for the report and stefanw for tests.



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

Re: [Django] #19818: Request Add to Hosting Page

2013-02-15 Thread Django

#19818: Request Add to Hosting Page
-+-
 Reporter:  encivallc|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Djangoproject.com|  Version:  1.4
  Web site   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * status:  new => closed
 * type:  Uncategorized => New feature
 * resolution:   => fixed
 * stage:  Unreviewed => Accepted


Comment:

 You have been 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19834: Bad index entries in the documentation section

2013-02-15 Thread Django

#19834: Bad index entries in the documentation section
--+--
 Reporter:  matthias@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  docs broken link
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 Clicking on a link in the  General Index
 [https://docs.djangoproject.com/en/1.4/genindex/] does not show up the
 correct page.

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

Re: [Django] #17217: Set nbsp instead of space as thousand separator

2013-02-15 Thread Django

#17217: Set nbsp instead of space as thousand separator
-+-
 Reporter:  fadeyev  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Translations |  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

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


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

Re: [Django] #17217: Set nbsp instead of space as thousand separator

2013-02-15 Thread Django

#17217: Set nbsp instead of space as thousand separator
-+-
 Reporter:  fadeyev  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Translations |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"b19d83fc12ebbabbaa9d72286f2e4bfa071ff784"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b19d83fc12ebbabbaa9d72286f2e4bfa071ff784"
 Improved input sanitizing with thousand separators

 For languages with non-breaking space as thousand separator,
 standard space input should also be allowed, as few people know
 how to enter non-breaking space on keyboards. Refs #17217.
 Thanks Alexey Boriskin for the report and initial 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b19d83: Improved input sanitizing with thousand separators

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b19d83fc12ebbabbaa9d72286f2e4bfa071ff784
  
https://github.com/django/django/commit/b19d83fc12ebbabbaa9d72286f2e4bfa071ff784
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/utils/formats.py
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  Improved input sanitizing with thousand separators

For languages with non-breaking space as thousand separator,
standard space input should also be allowed, as few people know
how to enter non-breaking space on keyboards. Refs #17217.
Thanks Alexey Boriskin for the report and initial 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1b54c8: [1.5.x] Avoided unneeded assertion on Python 3

2013-02-15 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1b54c85a53edec2f802223c702cb1dfde6be9aa5
  
https://github.com/django/django/commit/1b54c85a53edec2f802223c702cb1dfde6be9aa5
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/auth/tests/basic.py

  Log Message:
  ---
  [1.5.x] Avoided unneeded assertion on Python 3

Fixes failure introduced in 02e5909f7a.



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

[django/django] a8d142: Avoided unneeded assertion on Python 3

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a8d1421dd9d0ada64b9d8a3e96ed0b431c66ac97
  
https://github.com/django/django/commit/a8d1421dd9d0ada64b9d8a3e96ed0b431c66ac97
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/auth/tests/basic.py

  Log Message:
  ---
  Avoided unneeded assertion on Python 3

Fixes failure introduced in 02e5909f7a.



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

Re: [Django] #19807: Creating a superuser doesn't work

2013-02-15 Thread Django

#19807: Creating a superuser doesn't work
-+-
 Reporter:  Semmel   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Release blocker  | 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
-+-

Comment (by Claude Paroz ):

 In [changeset:"5921f15c113f41f3baca0b599ccb9dad83649682"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5921f15c113f41f3baca0b599ccb9dad83649682"
 [1.5.x] Fixed #19807 -- Sanitized getpass input in createsuperuser

 Python 2 getpass on Windows doesn't accept unicode, even when
 containing only ascii chars.
 Thanks Semmel for the report and tests.
 Backport of 02e5909f7a 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5921f1: [1.5.x] Fixed #19807 -- Sanitized getpass input in...

2013-02-15 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5921f15c113f41f3baca0b599ccb9dad83649682
  
https://github.com/django/django/commit/5921f15c113f41f3baca0b599ccb9dad83649682
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/auth/management/commands/createsuperuser.py
M django/contrib/auth/tests/basic.py

  Log Message:
  ---
  [1.5.x] Fixed #19807 -- Sanitized getpass input in createsuperuser

Python 2 getpass on Windows doesn't accept unicode, even when
containing only ascii chars.
Thanks Semmel for the report and tests.
Backport of 02e5909f7a from master.



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

Re: [Django] #19807: Creating a superuser doesn't work

2013-02-15 Thread Django

#19807: Creating a superuser doesn't work
-+-
 Reporter:  Semmel   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 Severity:  Release blocker  | 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 Claude Paroz ):

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


Comment:

 In [changeset:"02e5909f7ae436dab8e4d13370670c467163b8aa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02e5909f7ae436dab8e4d13370670c467163b8aa"
 Fixed #19807 -- Sanitized getpass input in createsuperuser

 Python 2 getpass on Windows doesn't accept unicode, even when
 containing only ascii chars.
 Thanks Semmel for the report and tests.
 }}}

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

[django/django] 02e590: Fixed #19807 -- Sanitized getpass input in creates...

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 02e5909f7ae436dab8e4d13370670c467163b8aa
  
https://github.com/django/django/commit/02e5909f7ae436dab8e4d13370670c467163b8aa
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/contrib/auth/management/commands/createsuperuser.py
M django/contrib/auth/tests/basic.py

  Log Message:
  ---
  Fixed #19807 -- Sanitized getpass input in createsuperuser

Python 2 getpass on Windows doesn't accept unicode, even when
containing only ascii chars.
Thanks Semmel for the report and tests.



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

Re: [Django] #19807: Creating a superuser doesn't work

2013-02-15 Thread Django

#19807: Creating a superuser doesn't work
-+-
 Reporter:  Semmel   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Release blocker  | 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 claudep):

 * stage:  Accepted => Ready for checkin


Comment:

 Thanks for testing.

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

[Django] #19833: Django's test framework fails when using unicode strings in settings.py

2013-02-15 Thread Django

#19833: Django's test framework fails when using unicode strings in settings.py
--+
 Reporter:  dbrgn |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Testing   |Version:  1.4
  framework   |   Keywords:  unicode, test runner, py3k
 Severity:  Normal|  Has patch:  0
 Triage Stage:  Unreviewed|  UI/UX:  0
Easy pickings:  1 |
--+
 When specifying a non-standard test runner using an unicode string in
 settings.py (`TEST_RUNNER = u'disccover_runner.DiscoverRunner'`) or when
 using `from __future__ import unicode_literals`, the `test` management
 command breaks.

 This is the "faulty" code snippet (`test/utils.py`):

 {{{#!python
 def get_runner(settings, test_runner_class=None):
 if not test_runner_class:
 test_runner_class = settings.TEST_RUNNER

 test_path = test_runner_class.split('.')
 # Allow for Python 2.5 relative paths
 if len(test_path) > 1:
 test_module_name = '.'.join(test_path[:-1])
 else:
 test_module_name = '.'
 test_module = __import__(test_module_name, {}, {}, test_path[-1])
 test_runner = getattr(test_module, test_path[-1])
 return test_runner
 }}}

 The problem is that a unicode string gets passed to `__import__`s
 `fromlist` argument. Apparently that won't work.

 I'm not sure what the right solution is. Is it enough to just convert
 `test_path[-1]` to a `str` type? Are decoding errors possible in that
 case? Are there any helper functions in Django to do a conversion that
 works both in py2 and py3 (str() vs bytes())?

 Bug tested on 1.4 and 1.5.

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

Re: [Django] #19807: Creating a superuser doesn't work

2013-02-15 Thread Django

#19807: Creating a superuser doesn't work
-+-
 Reporter:  Semmel   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Semmel):

 Sounds good + the tests run fine. And of course - this fixes the issue.
 Great 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19831: django.utils.functional.lazy return proxy object

2013-02-15 Thread Django

#19831: django.utils.functional.lazy return __proxy__ object
--+--
 Reporter:  dydek |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.5-rc-1
 Severity:  Normal|   Resolution:  invalid
 Keywords:  lazy  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by aaugustin):

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


Comment:

 Assuming your example is under Python 2, and `unicode_literals` isn't in
 effect, you're seeing the expected behavior. `test()` returns a bytestring
 and you tell `lazy` to resolve it only as `unicode` (ie. `six.text_type`).
 Besides, `lazy` isn't documented, it's a private 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19832: DecimalField validation shoud use plural forms

2013-02-15 Thread Django

#19832: DecimalField validation shoud use plural forms
-+-
 Reporter:  clay.evil@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Forms|Version:  1.4
 Severity:  Normal   |   Keywords:  DecimalField validation
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 The django.forms.fields.DecimalField line 260 - shlud use plural forms for
 decimal places and digis errors. Thank you.

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

[Django] #19831: django.utils.functional.lazy return proxy object

2013-02-15 Thread Django

#19831: django.utils.functional.lazy return __proxy__ object
--+--
 Reporter:  dydek |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.5-rc-1
 Severity:  Normal|   Keywords:  lazy
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 There is a problem with lazy wrapper used in fe.
 django.core.context_processors in csrf function.
 Let me show You an example:

 ''In [23]: def test():
 return "test string"

 In [24]: t = lazy(test, six.text_type)

 In [25]: print t()
 ''

 t() should return proper value from function test.

 This situation cause a problem with setting csrftoken cookie. It's only
 possible when You are using function
 ''_get_val''  without lazy wrapper.

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

Re: [Django] #19830: staff_member_required decorator should use 'admin.site.login_form' and not

2013-02-15 Thread Django

#19830: staff_member_required decorator should use 'admin.site.login_form' and 
not
-+-
 Reporter:  rene@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  staff_member_required  |  Patch needs improvement:  0
  authentication_form template_name  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * version:  1.4 => master
 * needs_tests:   => 0
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I think that instead of `login`, the decorator should use the
 `redirect_to_login` view, unless I've missed something...

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

[Django] #19830: staff_member_required decorator should use 'admin.site.login_form' and not

2013-02-15 Thread Django

#19830: staff_member_required decorator should use 'admin.site.login_form' and 
not
-+-
 Reporter:  rene@…   |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.4
Component:  contrib.admin|   Keywords:  staff_member_required
 Severity:  Normal   |  authentication_form template_name
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 The staff_member_required decorator in django.contrib.admin.views checks
 if the user is logged in and is staff. If not it will display the admin
 login page instead of the decorated view.

 If the user is not logged in and not staff, a 'defaults' dictionary is
 build with the following keys: 'template_name', 'authentication_form' and
 'extra_context'.

 The 'template_name' refers to the template to use for the login screen.
 The 'authentication_form' refers to the form class to use to handle the
 login form.

 The two values are now: 'admin/login.html' and 'AdminAuthenticationForm'.
 See the code block below:


 {{{

 defaults = {
 'template_name': 'admin/login.html',
 'authentication_form': AdminAuthenticationForm,
 'extra_context': {
 'title': _('Log in'),
 'app_path': request.get_full_path(),
 REDIRECT_FIELD_NAME: request.get_full_path(),
 },
 }

 }}}

 According to this documentation:
 [https://docs.djangoproject.com/en/1.4/ref/contrib/admin/#root-and-login-
 templates] a developer can provide it's own login-template and own login-
 form class to handle 'admin' logins.

 Should the 'staff_member_required' decorator not refer to these two
 settings instead of the hard-coded values in the current implementation?
 Like this:

 {{{

 defaults = {
 'template_name':  site.login_template or 'admin/login.html',
 'authentication_form': site.login_form or
 AdminAuthenticationForm,
 'extra_context': {
 'title': _('Log in'),
 'app_path': request.get_full_path(),
 REDIRECT_FIELD_NAME: request.get_full_path(),
 },
 }

 }}}

 These is a problem in the above codeblock. The 'site' variable does not
 exists. I am not sure how to get a reference to the 'admin' site object.

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

[django/django] dcf8cd: Updated FormattingTests test case to use settings ...

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dcf8cd30aed682d42f388c3e8a03098403ef3a16
  
https://github.com/django/django/commit/dcf8cd30aed682d42f388c3e8a03098403ef3a16
  Author: Claude Paroz 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

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

  Log Message:
  ---
  Updated FormattingTests test case to use settings contexts



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

Re: [Django] #19829: Index lookup fails for NumPy arrays in templates

2013-02-15 Thread Django

#19829: Index lookup fails for NumPy arrays in templates
-+-
 Reporter:  julien   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Julien Phalip ):

 In [changeset:"42e87c17f27f68ea43c78938d4972211b141ede3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="42e87c17f27f68ea43c78938d4972211b141ede3"
 [1.5.x] Fixed #19829 -- Fixed index lookups for NumPy arrays in templates.
 Backport of 7d5e35cdb46124e2471
 }}}

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

[django/django] 42e87c: [1.5.x] Fixed #19829 -- Fixed index lookups for Nu...

2013-02-15 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 42e87c17f27f68ea43c78938d4972211b141ede3
  
https://github.com/django/django/commit/42e87c17f27f68ea43c78938d4972211b141ede3
  Author: Julien Phalip 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/template/base.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #19829 -- Fixed index lookups for NumPy arrays in templates.
Backport of 7d5e35cdb46124e2471



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

Re: [Django] #19829: Index lookup fails for NumPy arrays in templates

2013-02-15 Thread Django

#19829: Index lookup fails for NumPy arrays in templates
-+-
 Reporter:  julien   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Julien Phalip ):

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


Comment:

 In [changeset:"7d5e35cdb46124e2471833b9570add1a00a1d9e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7d5e35cdb46124e2471833b9570add1a00a1d9e0"
 Fixed #19829 -- Fixed index lookups for NumPy arrays in templates.
 }}}

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

Re: [Django] #19829: Index lookup fails for NumPy arrays in templates

2013-02-15 Thread Django

#19829: Index lookup fails for NumPy arrays in templates
-+-
 Reporter:  julien   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Julien Phalip ):

 In [changeset:"400fba9ca847c40310491c560c9ce71144deec20"]:
 {{{
 #!CommitTicketReference repository=""
 revision="400fba9ca847c40310491c560c9ce71144deec20"
 Merge pull request #728 from jphalip/ticket-19829

 Fixed #19829 -- Fixed index lookups for NumPy arrays in templates.
 }}}

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

[django/django] 7d5e35: Fixed #19829 -- Fixed index lookups for NumPy arra...

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7d5e35cdb46124e2471833b9570add1a00a1d9e0
  
https://github.com/django/django/commit/7d5e35cdb46124e2471833b9570add1a00a1d9e0
  Author: Julien Phalip 
  Date:   2013-02-14 (Thu, 14 Feb 2013)

  Changed paths:
M django/template/base.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Fixed #19829 -- Fixed index lookups for NumPy arrays in templates.


  Commit: 400fba9ca847c40310491c560c9ce71144deec20
  
https://github.com/django/django/commit/400fba9ca847c40310491c560c9ce71144deec20
  Author: Julien Phalip 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/template/base.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Merge pull request #728 from jphalip/ticket-19829

Fixed #19829 -- Fixed index lookups for NumPy arrays in templates.


Compare: https://github.com/django/django/compare/b8061397eac0...400fba9ca847

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

[django/django] b80613: Put unicode_literals into all formats.py

2013-02-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b8061397eac019f42f875b6fff99b26a6dfdf229
  
https://github.com/django/django/commit/b8061397eac019f42f875b6fff99b26a6dfdf229
  Author: Alexey Boriskin 
  Date:   2013-02-15 (Fri, 15 Feb 2013)

  Changed paths:
M django/conf/locale/bn/formats.py
M django/conf/locale/bs/formats.py
M django/conf/locale/ca/formats.py
M django/conf/locale/cy/formats.py
M django/conf/locale/da/formats.py
M django/conf/locale/de/formats.py
M django/conf/locale/el/formats.py
M django/conf/locale/en/formats.py
M django/conf/locale/en_GB/formats.py
M django/conf/locale/es/formats.py
M django/conf/locale/es_AR/formats.py
M django/conf/locale/es_NI/formats.py
M django/conf/locale/eu/formats.py
M django/conf/locale/fy_NL/formats.py
M django/conf/locale/ga/formats.py
M django/conf/locale/hi/formats.py
M django/conf/locale/hr/formats.py
M django/conf/locale/id/formats.py
M django/conf/locale/is/formats.py
M django/conf/locale/it/formats.py
M django/conf/locale/ka/formats.py
M django/conf/locale/kn/formats.py
M django/conf/locale/mk/formats.py
M django/conf/locale/ml/formats.py
M django/conf/locale/mn/formats.py
M django/conf/locale/nl/formats.py
M django/conf/locale/pt/formats.py
M django/conf/locale/ro/formats.py
M django/conf/locale/sl/formats.py
M django/conf/locale/sq/formats.py
M django/conf/locale/sr/formats.py
M django/conf/locale/sr_Latn/formats.py
M django/conf/locale/ta/formats.py
M django/conf/locale/te/formats.py
M django/conf/locale/th/formats.py
M django/conf/locale/tr/formats.py
M django/conf/locale/zh_CN/formats.py
M django/conf/locale/zh_TW/formats.py

  Log Message:
  ---
  Put unicode_literals into all formats.py



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

49 matches

Mail list logo