[Django] #19760: adsf

[Django]

#19760: adsf
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 adsf [https://code.djangoproject.com/newticket google] asdf

-- 
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] 5ba768: [1.5.x] Fixed a typo in the test suite that was ca...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5ba76825cfe3fbc0967f38ac57fee4f09d6f2ead
  
https://github.com/django/django/commit/5ba76825cfe3fbc0967f38ac57fee4f09d6f2ead
  Author: Julien Phalip 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

  Changed paths:
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  [1.5.x] Fixed a typo in the test suite that was causing some spurious 
failures with pypy.
Backport of 6afc85af47f7d9f44



-- 
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] 6afc85: Fixed a typo in the test suite that was causing so...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6afc85af47f7d9f4494519de8842111734a61459
  
https://github.com/django/django/commit/6afc85af47f7d9f4494519de8842111734a61459
  Author: Julien Phalip 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

  Changed paths:
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  Fixed a typo in the test suite that was causing some spurious failures with 
pypy.



-- 
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] #19757: syncdb untranslated prompts for creating superuser

[Django]

#19757: syncdb untranslated prompts for creating superuser
-+--
 Reporter:  eukreign |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 ptone):

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


Comment:

 This should be fixed with
 
https://github.com/django/django/commit/2390fe3f4f8f52e24157d79b0c60247207c9716f

 if you can reproduce with a checkout later than that version - please do
 reopen.

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 abraham@…):

 Hey anonymous... I think we're running into the same issue... here's my
 guardian setup error:

 {{{

 ERROR 2013-02-06 01:26:23,372 mlogging 3343 139807877195520 Traceback
 (most recent call last):
   File "/site-packages/django/core/handlers/wsgi.py", line 255, in
 __call__
 response = self.get_response(request)
   File "/site-packages/django/core/handlers/base.py", line 178, in
 get_response
 response = self.handle_uncaught_exception(request, resolver,
 sys.exc_info())
   File "/site-packages/django/core/handlers/base.py", line 220, in
 handle_uncaught_exception
 if resolver.urlconf_module is None:
   File "/site-packages/django/core/urlresolvers.py", line 342, in
 urlconf_module
 self._urlconf_module = import_module(self.urlconf_name)
   File "/site-packages/django/utils/importlib.py", line 35, in
 import_module
 __import__(name)
   File "./urls.py", line 4, in 
 admin.autodiscover()
   File "/site-packages/django/contrib/admin/__init__.py", line 29, in
 autodiscover
 import_module('%s.admin' % app)
   File "/site-packages/django/utils/importlib.py", line 35, in
 import_module
 __import__(name)
   File "/site-packages/guardian/admin.py", line 13, in 
 from guardian.forms import UserObjectPermissionsForm
   File "/site-packages/guardian/forms.py", line 4, in 
 from guardian.shortcuts import assign
   File "/site-packages/guardian/shortcuts.py", line 11, in 
 from guardian.core import ObjectPermissionChecker
   File "/site-packages/guardian/core.py", line 6, in 
 from guardian.utils import get_identity
   File "/site-packages/guardian/utils.py", line 19, in 
 from guardian.compat import AnonymousUser
   File "/site-packages/guardian/compat.py", line 12, in 
 User = get_user_model()
   File "/site-packages/django/contrib/auth/__init__.py", line 125, in
 get_user_model
 user_model = get_model(app_label, model_name)
   File "/site-packages/django/db/models/loading.py", line 230, in
 get_model
 self._populate()
   File "/site-packages/django/db/models/loading.py", line 75, in _populate
 self.load_app(app_name)
   File "/site-packages/django/db/models/loading.py", line 96, in load_app
 models = import_module('.models', app_name)
   File "/site-packages/django/utils/importlib.py", line 35, in
 import_module
 __import__(name)
   File "/site-packages/guardian/models.py", line 11, in 
 from guardian.compat import User
 ImportError: cannot import name User

 }}}

-- 
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] #19759: asdf

[Django]

#19759: asdf
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 asdf

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 anonymous):

 The error I'm seeing is with the admin module and django-guardian, which
 supposedly has Django 1.5 support. It has a foreign key reference to the
 custom user model somewhere, but the very fact that it programatically
 chooses which User model to use seems to be the problem. I'll get the
 trace for you guys later tonight. It may very well be something I am doing
 wrong.

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 russellm):

 @anon - the problem isn't "Any third party module that is dependent on a
 custom User". You can write a module that has foreign keys to the custom
 User, for example. What you can't do is have module level initialization
 logic that depends on the pluggable user. The docs already reference one
 specific case where this is an issue -- signals -- but if there are other
 common use cases for this, then perhaps they need to be documented. As
 @charettes and @aaugustin have pointed out, this is a fundamental problem
 with the load sequence for Django apps, which should be addressed by
 #3591.

 So - What's the use case (beyond signals) that requires a module-level
 reference to the swappable User model?

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 abraham@…):

 I agree with what both of the guys above me are saying. I too ran into
 this problem when updating a third-party module. It will make dependency
 on a custom user model very difficult.

-- 
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] #19758: Password reset form should not leak information

[Django]

#19758: Password reset form should not leak information
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 The provided password reset form leaks information about enrolled users by
 providing information as to whether an email is enrolled. This is
 obviously untenable for any site with even moderate confidentiality
 requirements.

 Correct behavior is to display the same result regardless of whether an
 email is found in the database.

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 anonymous):

 Right. I ran into this problem when updating django-guardian for my own
 purposes. Any third-party module that is dependent on a custom User model
 will have problems. I see what you guys are saying about the app loading
 mechanism. Is there no way to lazily load apps?

-- 
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] #19757: syncdb untranslated prompts for creating superuser

[Django]

#19757: syncdb untranslated prompts for creating superuser
-+--
 Reporter:  eukreign |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Release blocker  |   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 eukreign):

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


Comment:

 Actually, looks like the password is fine, it's just the username and
 email that are not being translated:


 ubuntu:~/project$ ./manage.py syncdb
 Creating tables ...
 Creating table django_admin_log
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table django_content_type
 Creating table django_session
 Creating table account_user_groups
 Creating table account_user_user_permissions
 Creating table account_user

 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): yes
 : lex
 : l...@damoti.com
 Password:
 Password (again):
 Superuser created successfully.
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)

-- 
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] #19757: syncdb untranslated prompts for creating superuser

[Django]

#19757: syncdb untranslated prompts for creating superuser
-+
 Reporter:  eukreign |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.auth |Version:  master
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Using latest checkout of django-trunk with Python 2.7:


 ubuntu:~/project$ ./manage.py syncdb
 Creating tables ...
 Creating table django_admin_log
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table django_content_type
 Creating table django_session
 Creating table account_user_groups
 Creating table account_user_user_permissions
 Creating table account_user

 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): yes
 :


 ^ the prompts of username, email, password are displayed as proxy objects
 instead of translated strings.

-- 
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] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   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 ptone):

 I've implemented a patch here:

 https://github.com/ptone/django/compare/ticket/19662-modelbackend

 This may still need a note in the custom user docs but the note in model
 backend ref is probably enough.  Really I think this is something many
 people will just expect.

 I think we can leave AuthenticationForm set to username. Or at least that
 is a different ticket.

 One thing I almost missed is that authenticate works currently with
 username/password as positional args, so a check is made for that.

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

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

Re: [Django] #15363: get_queryset & get_query_set

[Django]

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 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
--+

Comment (by akaariai):

 It is still possible to break this by mixins or plain method assignment.
 Of these mixins might be actually used in the wild.

 The mixins example is:
 {{{
 class ManagerMixin(object):
 def get_query_set(self):
 ...

 class MyManager(ManagerMixin, models.Manager):
 pass
 }}}
 according to very quick testing this doesn't work similarly in master and
 after patch.

 It is likely possible to make mixins work with some mro introspection. I
 don't think the direct assignment case needs to be supported, it is likely
 extremely rare.

 Apart of the above cases I can't think of any case that will not work - as
 long as each class in the inheritance chain is subclass of Manager they
 will get both the get_queryset and get_query_set methods, and things will
 work. But, Python allows for some crazy constructs so I am not surprised
 if other problematic constructs are found.

 I am not sure if this kind of renaming is the best idea in the world. But,
 I don't care enough to actually put a -0 here (let alone -1). I guess we
 could do this renaming, and if we want to do other similar ones, then lets
 first wait for 1.6 and see how this one actually worked out. Of course, if
 something similar has been done already and it worked well, then put me
 into +0 camp.

-- 
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] #14930: `values_list()` fails on queryset ordered by extra column

[Django]

#14930: `values_list()` fails on queryset ordered by extra column
-+-
 Reporter:  lsaffre  |Owner:  vicould
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by fhahn):

 * cc: fhahn (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.

Re: [Django] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 charettes):

 I know it can't be called from the application containing the swapped for
 user model

 {{{
 #!python
 # myapp/models.py
 from django.contrib.auth import get_user_model
 from django.contrib.auth.models import AbstractUser

 class CustomUser(AbstractUser):
 pass

 get_user_model() # Will fail because the app "myapp" is not installed
 }}}

 But that's not really an issue since you can refer to it directly.

 The main problem is that every third-party that has to call
 `get_user_model` (signal attaching for example) must be placed after
 `'myapp'` in your `INSTALLED_APPS`.

 As pointed out by @aaugustin this a limitation of the current app loading
 mechanism.

-- 
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] #5652: Straightforward use of startproject command results in broken "Show on Site" link in admin

[Django]

#5652: Straightforward use of startproject command results in broken "Show on
Site" link in admin
-+-
 Reporter:  Leo Hourvitz |Owner:  nobody
     |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  SITE_ID  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 `django.contrib.sites` is no longer in the default INSTALLED_APPS
 (3f1c7b70537330435e2ec2fca9550f7b7fa4372e).

-- 
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] #15363: get_queryset & get_query_set

[Django]

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 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 sorl):

 * cc: mikko@… (removed)


-- 
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] #15363: get_queryset & get_query_set

[Django]

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 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
--+

Comment (by loic84):

 This approach is pretty clever and seems to work well.

 Should we aim at removing the last few occurrences of `query_set` for the
 sake of consistency? There are only a few variables and methods left after
 this patch, mostly private APIs.

 Also `BaseModelAdmin.queryset` is what brought me to this ticket: I wasted
 a bunch of time and resorted to some crazy hacks to access the admin
 queryset because I failed to notice this method since I was looking for a
 `get_queryset`. All similar methods in `ModelAdmin` have a `get_` prefix.

 For completeness I'll also mention `ListFilter.queryset` but I believe
 this one is acceptable since it is consistent with the surrounding
 methods.

 I think this patch is a good opportunity to solve the rest of the queryset
 accessor inconsistencies.

-- 
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] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Internationalization  |  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
--+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"d18f796a481e79a3800d4672d6189e4c496cce3d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d18f796a481e79a3800d4672d6189e4c496cce3d"
 Fixed #19704 -- Make use of new ungettext_lazy function at appropriate
 places
 }}}

-- 
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] d18f79: Fixed #19704 -- Make use of new ungettext_lazy fun...

[GitHub]

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

  Changed paths:
M django/contrib/comments/admin.py
M django/utils/timesince.py
M tests/regressiontests/comment_tests/tests/moderation_view_tests.py

  Log Message:
  ---
  Fixed #19704 -- Make use of new ungettext_lazy function at appropriate places



-- 
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] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by void):

 I updated pull request, fixing problems you've pointed out

-- 
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] #19741: Procedure in README.txt for setting up djangoproject locally doesn't work

[Django]

#19741: Procedure in README.txt for setting up djangoproject locally doesn't 
work
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:  master
  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 Aymeric Augustin ):

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


Comment:

 In
 [changeset:"ccde1930c05f90bbc28278a379d6e1ad60e1f29c/djangoproject.com"]:
 {{{
 #!CommitTicketReference repository="djangoproject.com"
 revision="ccde1930c05f90bbc28278a379d6e1ad60e1f29c"
 Updated installation instructions in README.

 Fixed #19741.
 }}}

-- 
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] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
--+---
 Reporter:  chris.khoo@…  |Owner:  khoomeister
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by claudep):

 * severity:  Release blocker => Normal


Comment:

 So I reverted the fix in 1.5, and commit my proposed fix in 1.6.

 Surely, the next step is to provide more tests. I have no religion about
 the use of regex or an HTML parser to strip tags, only tests will convince
 me!

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

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

Re: [Django] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+---
 Reporter:  chris.khoo@… |Owner:  khoomeister
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   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 Claude Paroz ):

 In [changeset:"d7504a3d7b8645bdb979bab7ded0e9a9b6dccd0e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d7504a3d7b8645bdb979bab7ded0e9a9b6dccd0e"
 Improved regex in strip_tags

 Thanks Pablo Recio for the report. Refs #19237.
 }}}

-- 
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] d7504a: Improved regex in strip_tags

[GitHub]

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

  Changed paths:
M django/utils/html.py
M tests/regressiontests/utils/html.py

  Log Message:
  ---
  Improved regex in strip_tags

Thanks Pablo Recio for the report. Refs #19237.



-- 
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] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+---
 Reporter:  chris.khoo@… |Owner:  khoomeister
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   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 Claude Paroz ):

 In [changeset:"20ac33100cd20c17d1ceab075d96698974cc4778"]:
 {{{
 #!CommitTicketReference repository=""
 revision="20ac33100cd20c17d1ceab075d96698974cc4778"
 Partially revert 9efe1a721, strip_tags improvements

 The new regex seems not stable enough for being released. Stripping
 with regex might need reevaluation for the next release.
 Refs #19237.
 }}}

-- 
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] 20ac33: Partially revert 9efe1a721, strip_tags improvement...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 20ac33100cd20c17d1ceab075d96698974cc4778
  
https://github.com/django/django/commit/20ac33100cd20c17d1ceab075d96698974cc4778
  Author: Claude Paroz 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

  Changed paths:
M django/utils/html.py
M tests/regressiontests/utils/html.py

  Log Message:
  ---
  Partially revert 9efe1a721, strip_tags improvements

The new regex seems not stable enough for being released. Stripping
with regex might need reevaluation for the next release.
Refs #19237.



-- 
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] #8408: add a new meta option: don't do count(*) in admin

[Django]

#8408: add a new meta option: don't do count(*) in admin
---+
 Reporter:  lidaobing  |Owner:  nobody
 Type:  New feature|   Status:  reopened
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by bb@…):

 +1 because I ran into this problem today.

 Using PostgreSQL and django 1.4 with a table that contains about 15
 million rows. executing "select count(*) from mytable" in the psql console
 takes about 40 seconds, even with an index on the primary key. This leads
 to timeouts and huge lag.

 I'm going to try MySQL to see if this is any better.

-- 
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] #19756: .add or .create on ManyToManyField doc page

[Django]

#19756: .add or .create on ManyToManyField doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 https://docs.djangoproject.com/en/1.4/topics/db/examples/many_to_many/

 "Add a Publication directly via publications.add by using keyword
 arguments:
 >>> new_publication = a2.publications.create(title='Highlights for
 Children')"

 Which is it, .add or .create?

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 abraham@…):

 I don't think get_model should be changed... rather... get_user_model
 should use something else. Basically, get_user_model can't be called when
 creating models (IE: Referencing the user object in another model) .

-- 
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] #19707: TransactionMiddleware leaks transaction state

[Django]

#19707: TransactionMiddleware leaks transaction state
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 A cleaned up implementation is attached. The tests are still ugly, but
 they do catch the errors.

 Should we log possible problems in transaction.abort()? And could there be
 situations where del connections[alias] isn't safe to do. We haven't ever
 deleted connections before. Still, in situations where del
 connections[alias] is called the connection will be in unknown state. It
 is hard to see how things could get worse than that (famous last
 words...).

 This one needs a review, as the plan is to backpatch the code to 1.4. The
 testing code will not apply cleanly, but the changes to django.* will
 apply to 1.4.

-- 
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] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+---
 Reporter:  chris.khoo@… |Owner:  khoomeister
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   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):

 It seems the current agreement among Django devs is to revert the change
 for 1.5 and switch to a non-regex technique for 1.6 (or maybe fallback to
 regex when content is not valid HTML).

-- 
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] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Thanks, notes added on the pull request.

-- 
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] #17001: Allow usage of custom querysets in prefetch_related

[Django]

#17001: Allow usage of custom querysets in prefetch_related
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  prefetch_related |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Pretty neat stuff!

-- 
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] #19755: Incremental filter

[Django]

#19755: Incremental filter
---+---
 Reporter:  paulox@…   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:  filter, admin
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+---
 Would be a good feature to have filter's value that change incrementally
 when user select one of them.


 I try to explain with an example:


 {{{
 class Person(models.Model):
 name = models.CharField()
 hair_color = models.CharField()
 eye_color = models.CharField()

 class PersonAdmin(admin.ModelAdmin):
 list_filter = ["hair_color", "eye_color"]
 }}}

 At first I'll see all hair color and eye color values in the filter.

 When I select an hair color value from the filter I'll see only person
 with that hair color.

 I would view in the eye color filter only distinct values of eye colors of
 person that have hair color I selected from the filter.

-- 
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] #19743: Document limitations of django.contrib.auth

[Django]

#19743: Document limitations of django.contrib.auth
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 Tim Graham ):

 In [changeset:"3b952123ac29f66371f5c51a00026faf7cb945c1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3b952123ac29f66371f5c51a00026faf7cb945c1"
 [1.5.x] Fixed #19743 - Documented some limitations of contrib.auth.

 Thanks Aymeric for the suggestion.

 Backport of afa3e16334 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] 3b9521: [1.5.x] Fixed #19743 - Documented some limitations...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 3b952123ac29f66371f5c51a00026faf7cb945c1
  
https://github.com/django/django/commit/3b952123ac29f66371f5c51a00026faf7cb945c1
  Author: Tim Graham 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

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

  Log Message:
  ---
  [1.5.x] Fixed #19743 - Documented some limitations of contrib.auth.

Thanks Aymeric for the suggestion.

Backport of afa3e16334 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] #19743: Document limitations of django.contrib.auth

[Django]

#19743: Document limitations of django.contrib.auth
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 Tim Graham ):

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


Comment:

 In [changeset:"afa3e1633431137f4e76c7efc359b579f4d9c08e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="afa3e1633431137f4e76c7efc359b579f4d9c08e"
 Fixed #19743 - Documented some limitations of contrib.auth.

 Thanks Aymeric for the suggestion.
 }}}

-- 
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] afa3e1: Fixed #19743 - Documented some limitations of cont...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: afa3e1633431137f4e76c7efc359b579f4d9c08e
  
https://github.com/django/django/commit/afa3e1633431137f4e76c7efc359b579f4d9c08e
  Author: Tim Graham 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

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

  Log Message:
  ---
  Fixed #19743 - Documented some limitations of contrib.auth.

Thanks Aymeric for the suggestion.



-- 
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] #19743: Document limitations of django.contrib.auth

[Django]

#19743: Document limitations of django.contrib.auth
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 Typo: "implmented". Otherwise that looks good!

-- 
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] #19743: Document limitations of django.contrib.auth

[Django]

#19743: Document limitations of django.contrib.auth
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * has_patch:  0 => 1
 * 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 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] #19728: Update API stability doc

[Django]

#19728: Update API stability doc
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 I'm not sure if the backwards compatibility note about contrib apps is
 still valid either?

-- 
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] #19704: Make use of new ungettext_lazy function at appropriate places

[Django]

#19704: Make use of new ungettext_lazy function at appropriate places
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by void):

 * has_patch:  0 => 1


Comment:

 I made pull request for the ticket:
 https://github.com/django/django/pull/702

-- 
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] #19750: Postgres conflict on CREATE INDEX: "relation exists"

[Django]

#19750: Postgres conflict on CREATE INDEX: "relation exists"
-+-
 Reporter:  pricco@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by pricco):

 * version:  1.4 => 1.5-beta-1


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

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

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

[Django]

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

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


Comment:

 In [changeset:"5449240c548bb6877923791d02e800c6b25393f5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5449240c548bb6877923791d02e800c6b25393f5"
 Fixed #9800 -- Allow "isPermaLink" attribute in  element of an RSS
 item.

 Thanks @rtnpro for the patch!
 }}}

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

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

[django/django] 544924: Fixed #9800 -- Allow "isPermaLink" attribute in

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5449240c548bb6877923791d02e800c6b25393f5
  
https://github.com/django/django/commit/5449240c548bb6877923791d02e800c6b25393f5
  Author: Simon Charette 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

  Changed paths:
M django/contrib/syndication/views.py
M django/utils/feedgenerator.py
M docs/ref/contrib/syndication.txt
M tests/regressiontests/syndication/feeds.py
M tests/regressiontests/syndication/tests.py
M tests/regressiontests/syndication/urls.py

  Log Message:
  ---
  Fixed #9800 -- Allow "isPermaLink" attribute in  element of an RSS item.

Thanks @rtnpro for the patch!



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

Re: [Django] #19754: Missing surrounding quotes

[Django]

#19754: Missing surrounding quotes
-+-
 Reporter:  aves@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  misprint |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 It's legal (and possibly a good practice) to pass the view functions
 themselves in URLconfs.

-- 
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] #19754: Missing surrounding quotes

[Django]

#19754: Missing surrounding quotes
--+--
 Reporter:  aves@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  misprint
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+--
 I think there are missing quotes on the third code block at
 
https://docs.djangoproject.com/en/1.4/ref/models/instances/#django.db.models.permalink

 (r'/archive/(?P\d{4})/(?P\d{2})/(?P\d{2})/$',
 archive_view)

 Should certainly be:

 (r'/archive/(?P\d{4})/(?P\d{2})/(?P\d{2})/$',
 'archive_view')

-- 
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] #17001: Allow usage of custom querysets in prefetch_related

[Django]

#17001: Allow usage of custom querysets in prefetch_related
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  prefetch_related |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (added)
 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 I would love this feature!

-- 
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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 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 aaugustin):

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


Comment:

 That's the behavior of Django's app loading mechanism. Improving it is a
 huge endeavor. See #3591.

 You didn't describe any concrete drawback that could justify this amount
 of 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] #15363: get_queryset & get_query_set

[Django]

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 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):

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


Comment:

 I gave a try at the metaclass approach and it works great. Have a look at
 the added 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] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+
 Reporter:  abraham@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.auth   |Version:  1.5-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 function calls: 'get_user_model' => 'get_model' => _populate

 _populate loads all installed apps. It seems like get_user_model should
 only rely on the app defining the custom user model.

-- 
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] #19745: Wrong prompt for `createuser` management command ()

[Django]

#19745: Wrong prompt for `createuser` management command
()
-+-
 Reporter:  bmispelon|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  createuser repr py3  |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  1|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"933e956ba4b1ad5f8823f0a294ffc795e949edf1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="933e956ba4b1ad5f8823f0a294ffc795e949edf1"
 [1.5.x] Fixed #19745 -- Forced resolution of verbose names in
 createsupersuser

 Thanks Baptiste Mispelon for the report and Preston Holmes for the review.
 Backport of 2390fe3f4 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] 933e95: [1.5.x] Fixed #19745 -- Forced resolution of verbo...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 933e956ba4b1ad5f8823f0a294ffc795e949edf1
  
https://github.com/django/django/commit/933e956ba4b1ad5f8823f0a294ffc795e949edf1
  Author: Claude Paroz 
  Date:   2013-02-06 (Wed, 06 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 #19745 -- Forced resolution of verbose names in createsupersuser

Thanks Baptiste Mispelon for the report and Preston Holmes for the review.
Backport of 2390fe3f4 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] #19745: Wrong prompt for `createuser` management command ()

[Django]

#19745: Wrong prompt for `createuser` management command
()
-+-
 Reporter:  bmispelon|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  createuser repr py3  |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  1|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"2390fe3f4f8f52e24157d79b0c60247207c9716f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2390fe3f4f8f52e24157d79b0c60247207c9716f"
 Fixed #19745 -- Forced resolution of verbose names in createsupersuser

 Thanks Baptiste Mispelon for the report and Preston Holmes for the review.
 }}}

-- 
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] 2390fe: Fixed #19745 -- Forced resolution of verbose names...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2390fe3f4f8f52e24157d79b0c60247207c9716f
  
https://github.com/django/django/commit/2390fe3f4f8f52e24157d79b0c60247207c9716f
  Author: Claude Paroz 
  Date:   2013-02-06 (Wed, 06 Feb 2013)

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

  Log Message:
  ---
  Fixed #19745 -- Forced resolution of verbose names in createsupersuser

Thanks Baptiste Mispelon for the report and Preston Holmes for the review.



-- 
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] #19752: Latest version of Postgresql is 9.2 on EnterpriseDB

[Django]

#19752: Latest version of Postgresql is 9.2 on EnterpriseDB
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 On the documentation :
 https://docs.djangoproject.com/en/1.5/ref/contrib/gis/install/#postgresql

 It says: First, download the latest PostgreSQL 9.0 installer from the
 EnterpriseDB Web site.

 It should be 9.2

-- 
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] #19749: Documentation needed: stdout.write line endings in management commands changed.

[Django]

#19749: Documentation needed: stdout.write line endings in management commands
changed.
-+-
 Reporter:  xian@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Management |  1.5-beta-1
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by aaugustin):

 * severity:  Normal => Release blocker


-- 
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.