[django/django] e9497a: Corrected way to get URL of object in admin histor...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e9497a3803c2da2d099ad1ca403a98cdb0ee322f
  
https://github.com/django/django/commit/e9497a3803c2da2d099ad1ca403a98cdb0ee322f
  Author: Luke Plant 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M django/contrib/admin/templates/admin/object_history.html

  Log Message:
  ---
  Corrected way to get URL of object in admin history template



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

Re: [Django] #18416: Query fails when SimpleLazyObject evaluates to None

[Django]

#18416: Query fails when SimpleLazyObject evaluates to None
-+-
 Reporter:  bouke|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lukeplant):

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


Comment:

 WONTFIX, I'm afraid. There is nothing we could do apart from putting a
 special case for `SimpleLazyObject` in `get_prep_value()` where the `is
 None` test gets done, which would be horrible.

 It is **Simple** Lazy Object after all.

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

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

Re: [Django] #17498: meta option "no_index"

[Django]

#17498: meta option "no_index"
---+
 Reporter:  kace   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by julien):

 * needs_better_patch:  0 => 1
 * easy:  1 => 0


Comment:

 Thank you all for your work on this ticket.

 While I understand and appreciate the need for excluding certain models
 from the general index and app indexes, I'm not sold on the suggested
 approach. The long-term goal for the admin is to provide more flexibility
 around the admin's structure and workflows, and adding a 'no_index' option
 would tie `ModelAdmin` to the idea that an index would systematically be
 part of the structure.

 On this basis, I'm going to reject the current pull request.

 The index functionality is currently already tied to
 `contrib.admin.sites.AdminSite`. It should already be possible to exclude
 models from the index by overriding the `index()` and `app_index()`
 methods, although I admit it probably wouldn't be pretty. A new API could
 be designed to make it prettier and easier, but I believe that should be
 done in `AdminSite`, not `ModelAdmin`.

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

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

Re: [Django] #18447: LazyObject doesn't unwrap on dict access

[Django]

#18447: LazyObject doesn't unwrap on dict access
---+
 Reporter:  FunkyBob   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by lukeplant):

 * needs_docs:  1 => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #18414: queryset.exists() returns False when queryset is distinct and sliced

[Django]

#18414: queryset.exists() returns False when queryset is distinct and sliced
-+-
 Reporter:  bitrut   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by lukeplant):

 * stage:  Unreviewed => Accepted


Comment:

 `QuerySet.exists()`  should throw an exception for this case, and possibly
 for any case involving slicing - I don't think it was designed to be
 correct in the presence of LIMIT/OFFSET. However, for the moment probably
 best to limit to the distinct()+slicing()+exists() combination.

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

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

Re: [Django] #18403: Issue with redefined SimpleCookie with invalid cookie name

[Django]

#18403: Issue with redefined SimpleCookie with invalid cookie name
-+-
 Reporter:  Stefano Crosta   |Owner:  nobody
  |   Status:  new
 Type:  Bug  |  Version:  1.4
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cookie   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by lukeplant):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #18364: Can't server static files with version information

[Django]

#18364: Can't server static files with version information
-+--
 Reporter:  f@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by lukeplant):

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


Comment:

 I presume this is by design - so that, for instance, you can download
 files that have a '?' in the name. The workaround is simple - put the
 version part outside the `{% static %}` tag.

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

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

Re: [Django] #9245: Using choices in a mode field forces use of TypedChoiceField in a form field

[Django]

#9245: Using choices in a mode field forces use of TypedChoiceField in a form
field
+
 Reporter:  Tarken  |Owner:  badri
 Type:  Bug |   Status:  reopened
Component:  Forms   |  Version:  1.0
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by julien):

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


Comment:

 Thank you for your work and sorry for the late review.

 In the revised patch attached, I've moved the logic to a new, separate
 method called `choices_formfield()`. This complicates the API slightly,
 but at least it removes the necessity for all subclasses of `Field` to
 modify their logic based on `self.choices`.

 I'll seek some feedback. If this approach is approved then some
 documentation will be needed.

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

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

Re: [Django] #18157: Document that setting PASSWORD_HASHERS for tests can make them much faster

[Django]

#18157: Document that setting PASSWORD_HASHERS for tests can make them much 
faster
---+
 Reporter:  carljm |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 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 Claude Paroz ):

 In [b0d8085c67884f36c8fb4af5f1fdae844e4700f7]:
 {{{
 #!CommitTicketReference repository=""
 revision="b0d8085c67884f36c8fb4af5f1fdae844e4700f7"
 Added note about including fixtures hashing algorithm

 Refs #18157.
 }}}

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

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

[django/django] b0d808: Added note about including fixtures hashing algori...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b0d8085c67884f36c8fb4af5f1fdae844e4700f7
  
https://github.com/django/django/commit/b0d8085c67884f36c8fb4af5f1fdae844e4700f7
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M docs/topics/testing.txt

  Log Message:
  ---
  Added note about including fixtures hashing algorithm

Refs #18157.



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

Re: [Django] #18157: Document that setting PASSWORD_HASHERS for tests can make them much faster

[Django]

#18157: Document that setting PASSWORD_HASHERS for tests can make them much 
faster
---+
 Reporter:  carljm |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 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 mjtamlyn):

 Big +1 on this, but it may be worth mentioning that if you have fixtures
 generated with a different password hasher you'll get errors if you don't
 include that hasher. Same speed up can be gained just by putting the MD5
 hasher at the top of your existing setting. Obviously we shouldn't be
 using fixtures but...

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

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

Re: [Django] #14827: Authentication Backends should be responsible for checking and setting passwords

[Django]

#14827: Authentication Backends should be responsible for checking and setting
passwords
--+-
 Reporter:  andornaut |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  1.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Someday/Maybe
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:   => fixed


Comment:

 I think and hope that the recently added password hashers mechanism should
 fulfill this use case.

 https://docs.djangoproject.com/en/dev/topics/auth/#how-django-stores-
 passwords

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

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

Re: [Django] #16256: More class based views: formsets derived generic views

[Django]

#16256: More class based views: formsets derived generic views
---+
 Reporter:  rasca  |Owner:  rasca
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by charettes):

 * cc: charette.s@… (added)


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

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

Re: [Django] #18157: Document that setting PASSWORD_HASHERS for tests can make them much faster

[Django]

#18157: Document that setting PASSWORD_HASHERS for tests can make them much 
faster
---+
 Reporter:  carljm |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz ):

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


Comment:

 In [17d6cd90299e39823e80a005e7a04bc24ee8af4c]:
 {{{
 #!CommitTicketReference repository=""
 revision="17d6cd90299e39823e80a005e7a04bc24ee8af4c"
 Fixed #18157 -- Documented that setting PASSWORD_HASHERS can speed up
 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 17d6cd: Fixed #18157 -- Documented that setting PASSWORD_H...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 17d6cd90299e39823e80a005e7a04bc24ee8af4c
  
https://github.com/django/django/commit/17d6cd90299e39823e80a005e7a04bc24ee8af4c
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M docs/topics/testing.txt

  Log Message:
  ---
  Fixed #18157 -- Documented that setting PASSWORD_HASHERS can speed up tests



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

Re: [Django] #18455: Form media rendering doesn't respect STATICFILES_STORAGE

[Django]

#18455: Form media rendering doesn't respect STATICFILES_STORAGE
+--
 Reporter:  djw |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by claudep):

 Please try also to write a test which doesn't pass with the current code,
 to demonstrate this ticket's rationale.

 About tests not passing in full run, try to see which global variable is
 the culprit and reset this variable in the test setUp method (or use the
 settings_change signal).

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

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

Re: [Django] #18453: Unknown password hashing algorithm error if password is blank

[Django]

#18453: Unknown password hashing algorithm error if password is blank
--+
 Reporter:  Leo   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * stage:  Unreviewed => Accepted


Comment:

 This should be fixed if current patch of #18182 is committed, however let
 this one open until then.

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

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

Re: [Django] #16637: Admin site gives DoesNoteExist at /admin/

[Django]

#16637: Admin site gives DoesNoteExist at /admin/
---+--
 Reporter:  camey@…|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by charettes):

 * cc: charette.s@… (added)
 * status:  reopened => closed
 * resolution:   => invalid


Comment:

 As pointed out by @aaugustin the
 
[https://github.com/django/django/blob/master/django/contrib/sites/management.py#L12-L36
 default site is supposed to be added during syncdb when the table is
 created].

 Running `python manage.py sqlall sites` doesn't output the full SQL
 executed for the `contrib.sites` app -- only the SQL needed for table and
 constraint creation related to models. Did you actually run `syncdb` or
 just manually executed SQL returned by `sqlall` for all your
 `INSTALLED_APPS`?

 I just tested it with a clean 1.4 install and the default site is
 correctly created when running `syncdb`.

 {{{
 simon@simon-laptop:~/Bureau$ virtualenv ticket_16637_venv --no-site-
 packages
 New python executable in ticket_16637_venv/bin/python
 Installing setuptoolsdone.
 Installing pip...done.
 simon@simon-laptop:~/Bureau$ source ticket_16637_venv/bin/activate
 (ticket_16637_venv)simon@simon-laptop:~/Bureau$ pip install django==1.4
 Downloading/unpacking django==1.4
   Downloading Django-1.4.tar.gz (7.6Mb): 7.6Mb downloaded
   Running setup.py egg_info for package django

 Installing collected packages: django
   Running setup.py install for django
 changing mode of build/scripts-2.7/django-admin.py from 664 to 775

 changing mode of /home/simon/Bureau/ticket_16637_venv/bin/django-
 admin.py to 775
 Successfully installed django
 Cleaning up...
 (ticket_16637_venv)simon@simon-laptop:~/Bureau$ django-admin.py
 startproject ticket_16637
 (ticket_16637_venv)simon@simon-laptop:~/Bureau$ cd ticket_16637
 (ticket_16637_venv)simon@simon-laptop:~/Bureau/ticket_16637$ vim
 ticket_16637/settings.py
 (ticket_16637_venv)simon@simon-laptop:~/Bureau/ticket_16637$ chmod +x
 manage.py
 (ticket_16637_venv)simon@simon-laptop:~/Bureau/ticket_16637$ ./manage.py
 syncdb
 Creating tables ...
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table django_content_type
 Creating table django_session
 Creating table django_site

 You just installed Django's auth system, which means you don't have any
 superusers defined.
 Would you like to create one now? (yes/no): no
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)
 (ticket_16637_venv)simon@simon-laptop:~/Bureau/ticket_16637$ ./manage.py
 shell
 Python 2.7.3 (default, Apr 20 2012, 22:39:59)
 [GCC 4.6.3] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django.contrib.sites.models import Site
 >>> Site.objects.get()
 
 }}}

 Note that deleting the default `Site` instance and re-running `syncdb`
 won't re-create a new one.

 Resolving as `invalid` until you can provide steps to reproduce you issue.

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

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

[django/django] 514e82: Fixed pagination example wrt new next_page_number ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 514e82702232139ec76f36a6e1fa4b63f47c6990
  
https://github.com/django/django/commit/514e82702232139ec76f36a6e1fa4b63f47c6990
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M docs/topics/pagination.txt

  Log Message:
  ---
  Fixed pagination example wrt new next_page_number behavior



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

Re: [Django] #7231: New "join" parameter for the "extra" QuerySet method

[Django]

#7231: New "join" parameter for the "extra" QuerySet method
-+-
 Reporter:  Davide "Design"  |Owner:  nobody
  Muzzarelli |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  queryset extra left  |  Needs documentation:  1
  join   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by charettes):

 * status:  reopened => closed
 * type:  Uncategorized => New feature
 * resolution:   => wontfix


Comment:

 Please don't anonymously re-open tickets closed by a core developer. If
 you want to argue about why this ticket should be re-opened feel free to
 discuss [https://groups.google.com/forum/?fromgroups#!topic/django-
 developers/B0GeDnJJCqI here]. However I think there's already a clear
 consensus on not adding this parameter.

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

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

Re: [Django] #17159: Paginator.Page() should throw an exception for invalid [next|previous]_page_number()

[Django]

#17159: Paginator.Page() should throw an exception for invalid
[next|previous]_page_number()
-+-
 Reporter:  mehta.apurva@…   |Owner:  neaf
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  paginator core   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [fc40a6504b78e604a6ba90a3b85b1ed54ee238a2]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc40a6504b78e604a6ba90a3b85b1ed54ee238a2"
 Fixed #17159 -- Validated returned number of next|previous_page_number

 Thanks mehta.apurva at gmail.com for the report and the initial patch
 and neaf for the complete patch.
 }}}

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

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

[django/django] fc40a6: Fixed #17159 -- Validated returned number of next|...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fc40a6504b78e604a6ba90a3b85b1ed54ee238a2
  
https://github.com/django/django/commit/fc40a6504b78e604a6ba90a3b85b1ed54ee238a2
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M django/core/paginator.py
M docs/releases/1.5.txt
M docs/topics/pagination.txt
M tests/modeltests/pagination/tests.py

  Log Message:
  ---
  Fixed #17159 -- Validated returned number of next|previous_page_number

Thanks mehta.apurva at gmail.com for the report and the initial patch
and neaf for the complete patch.



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

Re: [Django] #18453: Unknown password hashing algorithm error if password is blank

[Django]

#18453: Unknown password hashing algorithm error if password is blank
--+--
 Reporter:  Leo   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Leo):

 Sorry, to clarify, it hits the ValueError which results in a 500:

 {{{
 File "/foo/lib/python2.7/site-packages/django/contrib/auth/hashers.py",
 line 115, in get_hasher
   "setting?" % algorithm)

 File "/foo/lib/python2.7/site-packages/django/contrib/auth/hashers.py",
 line 42, in check_password
   hasher = get_hasher(algorithm)

 File "/foo/lib/python2.7/site-packages/django/contrib/auth/models.py",
 line 304, in check_password
   return check_password(raw_password, self.password, setter)
 }}}

 That happens because the algorithm ends up being !''

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

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

[django/django] ef906b: Removed test of connection features before setting...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ef906b163202679413f1fdae7106b8de86477dbe
  
https://github.com/django/django/commit/ef906b163202679413f1fdae7106b8de86477dbe
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

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

  Log Message:
  ---
  Removed test of connection features before setting up databases



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

Re: [Django] #18455: Form media rendering doesn't respect STATICFILES_STORAGE

[Django]

#18455: Form media rendering doesn't respect STATICFILES_STORAGE
+--
 Reporter:  djw |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by djw):

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


Comment:

 I've created a patch here:

 https://github.com/djw/django/tree/ticket_18455

 All the tests in 'forms' pass with this patch applied. However, they fail
 when running as part of the full test suite, and I need some advice on how
 to fix this.

 The issue is that the tests in forms/tests/media.py run with overridden
 STATIC_URL and MEDIA_URL. When run in isolation, the static files storage
 backend is initialised based on these settings. However if the backend has
 been initialised before these tests run, it doesn't respect the new values
 of STATIC_URL and MEDIA_URL, so the tests fail. What's the best way to go
 about fixing this?

 Also the `absolute_path()` method has an optional `prefix` argument — I
 can't see where that's used, so I dont know how to support it properly.

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

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

Re: [Django] #17760: connection.features.supports_transactions is None

[Django]

#17760: connection.features.supports_transactions is None
-+-
 Reporter:  cdestigter   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [ad47364dd324508e8332ea853da59772431398aa]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad47364dd324508e8332ea853da59772431398aa"
 Reverted 905e33f, now that DatabaseFeatures does not need confirm

 Connection.features does not need to be confirmed any more, after
 commit aa42357, rendering obsolete the workaround when using
 TEST_MIRROR (Refs #16885, #17760).
 }}}

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

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

Re: [Django] #16885: django.test.testcases.connections_support_transactions always returns False if TEST_MIRROR is used

[Django]

#16885: django.test.testcases.connections_support_transactions always returns 
False
if TEST_MIRROR is used
---+
 Reporter:  grimfandjango  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Claude Paroz ):

 In [ad47364dd324508e8332ea853da59772431398aa]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad47364dd324508e8332ea853da59772431398aa"
 Reverted 905e33f, now that DatabaseFeatures does not need confirm

 Connection.features does not need to be confirmed any more, after
 commit aa42357, rendering obsolete the workaround when using
 TEST_MIRROR (Refs #16885, #17760).
 }}}

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

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

[django/django] ad4736: Reverted 905e33f, now that DatabaseFeatures does n...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ad47364dd324508e8332ea853da59772431398aa
  
https://github.com/django/django/commit/ad47364dd324508e8332ea853da59772431398aa
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M django/test/simple.py
M tests/regressiontests/test_runner/tests.py

  Log Message:
  ---
  Reverted 905e33f, now that DatabaseFeatures does not need confirm

Connection.features does not need to be confirmed any more, after
commit aa42357, rendering obsolete the workaround when using
TEST_MIRROR (Refs #16885, #17760).



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

[Django] #18455: Form media rendering doesn't respect STATICFILES_STORAGE

[Django]

#18455: Form media rendering doesn't respect STATICFILES_STORAGE
+
 Reporter:  djw |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 When constructing the URLs for form media, django simply prepends the
 asset path with MEDIA_URL or STATIC_URL. Instead it should use
 `staticfiles_storage.url(path)`.

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

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

Re: [Django] #16637: Admin site gives DoesNoteExist at /admin/

[Django]

#16637: Admin site gives DoesNoteExist at /admin/
---+--
 Reporter:  camey@…|Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Bill Ellis):

 * status:  closed => reopened
 * version:  1.3 => 1.4
 * resolution:  invalid =>


Comment:

 This caught me out too.

 In 1.4, default INSTALLED_APPS includes django.contrib.sites.
 If we do syncdb, this sql is executed:
 {{{
 a$ python manage.py sqlall sites
 BEGIN;
 CREATE TABLE `django_site` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `domain` varchar(100) NOT NULL,
 `name` varchar(50) NOT NULL
 )
 ;
 COMMIT;
 }}}

 Note that the table is empty. If following the polls tutorial (like I was
 doing) the presence of this empty table leads to the "DoesNoteExist at
 /admin/".

 There are loads of fixes/workarounds ; chuck some data into the table, use
 the one liner above, comment out "django.contrib.sites" before the first
 syncdb -- but for new folk like me, this was a bit confusing, and not easy
 to google.


 Perhaps, for 1.4 documentation, adjust the polls tutorial to tell user to
 comment out "django.contrib.sites" before the first syncdb.
 Perhaps, for next version, don't have "django.contrib.sites" as a default
 / or get it to have nicer syncdb behaviour.

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

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

Re: [Django] #17760: connection.features.supports_transactions is None

[Django]

#17760: connection.features.supports_transactions is None
-+-
 Reporter:  cdestigter   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [aa423575e7b464433fcfc4bf4b8e1d7627b17ce6]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa423575e7b464433fcfc4bf4b8e1d7627b17ce6"
 Fixed #17760 -- Implemented callable database features as cached
 properties

 This does remove the requirement to call features.confirm() method
 before checking the properties.
 Thanks cdestiger and Ramiro Morales 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] aa4235: Fixed #17760 -- Implemented callable database feat...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aa423575e7b464433fcfc4bf4b8e1d7627b17ce6
  
https://github.com/django/django/commit/aa423575e7b464433fcfc4bf4b8e1d7627b17ce6
  Author: Claude Paroz 
  Date:   2012-06-09 (Sat, 09 Jun 2012)

  Changed paths:
M django/contrib/gis/db/backends/spatialite/creation.py
M django/db/backends/__init__.py
M django/db/backends/creation.py
M django/db/backends/mysql/base.py
M django/db/backends/sqlite3/base.py
M tests/regressiontests/backends/tests.py
M tests/regressiontests/transactions_regress/tests.py

  Log Message:
  ---
  Fixed #17760 -- Implemented callable database features as cached properties

This does remove the requirement to call features.confirm() method
before checking the properties.
Thanks cdestiger and Ramiro Morales for their work on the patch.



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

Re: [Django] #18421: Pagination documentation contains error when no GET request provided

[Django]

#18421: Pagination documentation contains error when no GET request provided
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by claudep):

 * status:  new => closed
 * resolution:   => invalid
 * stage:  Ready for checkin => Unreviewed


Comment:

 If 'page' is not provided in the request, the page variable will be None.
 Then paginator.page will raise !PageNotAnInteger which will lead to the
 paginator.page(1) code path. Same scenario if page is set to anything
 other than a integer.

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

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

Re: [Django] #18182: Raw password echoed on authentication if no hashing used

[Django]

#18182: Raw password echoed on authentication if no hashing used
--+
 Reporter:  danielr   |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 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):

 Note to self: "Unusable password, the user cannot login." should probably
 simply be "No password set."

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

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

Re: [Django] #18450: Remove default values for i18n JavaScript URLs in Admin templates

[Django]

#18450: Remove default values for i18n JavaScript URLs in Admin templates
--+
 Reporter:  dhepper   |Owner:  dhepper
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by apollo13):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #18453: Unknown password hashing algorithm error if password is blank

[Django]

#18453: Unknown password hashing algorithm error if password is blank
--+--
 Reporter:  Leo   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

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


Comment:

 Could you please specify at which point does the crash occurs? I've worked
 on #18182, and I would like to be sure that your use case is addressed.

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

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

Re: [Django] #18182: Raw password echoed on authentication if no hashing used

[Django]

#18182: Raw password echoed on authentication if no hashing used
--+
 Reporter:  danielr   |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 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 claudep):

 * needs_better_patch:  1 => 0


Comment:

 Now !ReadOnlyPasswordHashWidget is still displaying an error message if
 encoded is not valid.

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

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

Re: [Django] #18182: Raw password echoed on authentication if no hashing used

[Django]

#18182: Raw password echoed on authentication if no hashing used
--+
 Reporter:  danielr   |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * needs_better_patch:  0 => 1


Comment:

 The current problem with altering is_usable_password is that the error
 message "Invalid password format or unknown hashing algorithm" is not
 displayed in the user change form. This should be addressed.

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

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

Re: [Django] #18182: Raw password echoed on authentication if no hashing used

[Django]

#18182: Raw password echoed on authentication if no hashing used
--+
 Reporter:  danielr   |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.4
 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 claudep):

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


Comment:

 hashers.py does now contain a identify_hasher function. In this patch, I
 suggest to use this function in is_password_usable.

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

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

Re: [Django] #7231: New "join" parameter for the "extra" QuerySet method

[Django]

#7231: New "join" parameter for the "extra" QuerySet method
-+-
 Reporter:  Davide "Design"  |Owner:  nobody
  Muzzarelli |   Status:  reopened
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  queryset extra left  |  Needs documentation:  1
  join   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by anonymous):

 * status:  closed => reopened
 * resolution:  wontfix =>


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

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

Re: [Django] #17209: Dogfood class-based views in contrib.auth

[Django]

#17209: Dogfood class-based views in contrib.auth
-+-
 Reporter:  melinath |Owner:  andrews
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  class-based views|  Needs documentation:  0
  admin auth |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by bmispelon):

 I've made some more improvements and reached a point where I'm pretty
 satisfied with the code.

 I'm going to attempt writing some documentation now, using the work done
 by pydanny in the pull request #144 (it hasn't been accepted yet as I'm
 writing this).

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

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

[Django] #18454: Add ability to pass several signals to `receiver`

[Django]

#18454: Add ability to pass several signals to `receiver`
--+--
 Reporter:  dmedvinsky|  Owner:  dmedvinsky
 Type:  New feature   | Status:  new
Component:  Core (Other)  |Version:  1.4
 Severity:  Normal|   Keywords:  signal, receiver
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+--
 Pull Request: https://github.com/django/django/pull/136

 This adds ability to use receiver in the following way:

 {{{
 @receiver([post_save, post_delete], sender=MyModel)
 def signals_receiver(sender, **kwargs):
 ...
 }}}


 Quite often I want to connect both post_save and post_delete signals
 for some particular sender.

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

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