Re: [Django] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+--
  Reporter:  etianen | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by DrMeers):

 > Proxy models should also proxy the permissions of the model they are
 shadowing

 Are you sure about that Malcolm? Proxy models could be quite useful for
 limiting permissions to a subset of objects.

 For example, I could make a {{{Student}}} proxy for {{{User}}} with a
 manager whose {{{get_query_set}}} returns only {{{Users}}} in the
 "student" {{{Group}}}, and a {{{save}}} method which automatically assigns
 {{{User}}}s to that group. What if I'd then like to restrict
 {{{Teacher}}}s to only being able to add/change/delete {{{Student}}}s and
 not {{{User}}}s in general?

-- 
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-upda...@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] #14354: Check password is not None in User.check_password

[Django]

#14354: Check password is not None in User.check_password
-+--
  Reporter:  berryp  | Owner:  laurentluce
Status:  assigned| Milestone:  1.3
 Component:  Authentication  |   Version:  1.2
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

  * needs_better_patch:  0 => 1

Comment:

 Looks good, Laurent. Some minor review comments:

  * As discussed on the list, the check for invalidity should allow empty
 string, and use None to mark an unusable password.

  * Empty setup/teardown methods aren't needed. There's no need to formally
 declare a no-op.

  * The tests for the createsuperuser management commands output to stdout
 - tests shouldn't have any visible manifestation. As part of the migration
 to use unittests, we're modifying the admin commands to take stdout/stderr
 arguments, and writing output to those streams. See loaddata/dumpdata for
 examples. This allows the test commands (or any other programmatic usage)
 to provide a stream that will be used for output (which provides a second
 way to fix this test problem -- invoke the test with verbosity=0).

  * While you're in that areas, the "superuser created" text should also be
 covered by a verbosity check; verbosity=0 should output nothing.

-- 
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-upda...@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] #10970: auto_now_add for DateField evaluetes to datetime.datetime instance

[Django]

#10970: auto_now_add for DateField evaluetes to datetime.datetime instance
---+
  Reporter:  summerisgone  | Owner:  nobody 

Status:  new   | Milestone:  1.3

 Component:  Database layer (models, ORM)  |   Version:  1.0

Resolution:|  Keywords:  DateField, 
auto_now_add
 Stage:  Ready for checkin | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by ericholscher):

  * stage:  Accepted => Ready for checkin
  * milestone:  => 1.3

-- 
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-upda...@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] #14418: lazy instances are not resolved to string when used as Exception value

[Django]

#14418: lazy instances are not resolved to string when used as Exception value
---+
 Reporter:  djoume |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hi,

 If in my django application I raise an Exception with a lazy string as
 value, the django 500 handler won't display the Exception class but will
 display instead ""

 Here is what I believe to be the minimal code to reproduce the issue
 {{{
 >>> from django.utils.translation import ugettext, ugettext_lazy
 >>> print Exception(ugettext(u'test'))
 test
 >>> print Exception(ugettext_lazy(u'test'))
 
 }}}

 Should this be considered a bug in django or lazy string are not supported
 as exception value?

-- 
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-upda...@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] #14330: Test failure with get_image_dimensions since [13715]

[Django]

#14330: Test failure with get_image_dimensions since [13715]
---+
  Reporter:  gabrielhurley | Owner:  gabrielhurley  
  
Status:  closed| Milestone:  1.3
  
 Component:  File uploads/storage  |   Version:  SVN
  
Resolution:  fixed |  Keywords:  
get_image_dimensions PIL mode
 Stage:  Ready for checkin | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Fixed by [14001].

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

[Changeset] r14002 - django/branches/releases/1.2.X/tests/regressiontests/file_storage

[noreply]

Author: lukeplant
Date: 2010-10-07 18:49:31 -0500 (Thu, 07 Oct 2010)
New Revision: 14002

Modified:
   django/branches/releases/1.2.X/tests/regressiontests/file_storage/tests.py
Log:
[1.2.X] Fixed #14430 - Test failure on Windows with get_image_dimensions since 
[13715]

Thanks to gabrielhurley for report and patch.

Backport of [14001] from trunk.

Modified: 
django/branches/releases/1.2.X/tests/regressiontests/file_storage/tests.py
===
--- django/branches/releases/1.2.X/tests/regressiontests/file_storage/tests.py  
2010-10-07 23:48:25 UTC (rev 14001)
+++ django/branches/releases/1.2.X/tests/regressiontests/file_storage/tests.py  
2010-10-07 23:49:31 UTC (rev 14002)
@@ -375,7 +375,7 @@
 """
 from django.core.files.images import ImageFile
 img_path = os.path.join(os.path.dirname(__file__), "test.png")
-image = ImageFile(open(img_path))
+image = ImageFile(open(img_path, 'rb'))
 image_pil = Image.open(img_path)
 size_1, size_2 = get_image_dimensions(image), 
get_image_dimensions(image)
 self.assertEqual(image_pil.size, size_1)

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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.

[Changeset] r14001 - django/trunk/tests/regressiontests/file_storage

[noreply]

Author: lukeplant
Date: 2010-10-07 18:48:25 -0500 (Thu, 07 Oct 2010)
New Revision: 14001

Modified:
   django/trunk/tests/regressiontests/file_storage/tests.py
Log:
Fixed #14430 - Test failure on Windows with get_image_dimensions since [13715]

Thanks to gabrielhurley for report and patch.

Modified: django/trunk/tests/regressiontests/file_storage/tests.py
===
--- django/trunk/tests/regressiontests/file_storage/tests.py2010-10-07 
23:36:02 UTC (rev 14000)
+++ django/trunk/tests/regressiontests/file_storage/tests.py2010-10-07 
23:48:25 UTC (rev 14001)
@@ -375,7 +375,7 @@
 """
 from django.core.files.images import ImageFile
 img_path = os.path.join(os.path.dirname(__file__), "test.png")
-image = ImageFile(open(img_path))
+image = ImageFile(open(img_path, 'rb'))
 image_pil = Image.open(img_path)
 size_1, size_2 = get_image_dimensions(image), 
get_image_dimensions(image)
 self.assertEqual(image_pil.size, size_1)

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #7722: EMail Message with CC - Carbon CopyFixed patch

[Django]

#7722: EMail Message with CC - Carbon CopyFixed patch
-+--
  Reporter:  roberto.digirolamo   | Owner:  
nobody
Status:  closed  | Milestone:   
 
 Component:  django.core.mail|   Version:  
SVN   
Resolution:  fixed   |  Keywords:   
 
 Stage:  Ready for checkin   | Has_patch:  
1 
Needs_docs:  0   |   Needs_tests:  
0 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

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

Comment:

 Fixed in [14000], thanks.

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

[Changeset] r14000 - in django/trunk: django/core/mail docs/topics tests/regressiontests/mail

[noreply]

Author: lukeplant
Date: 2010-10-07 18:36:02 -0500 (Thu, 07 Oct 2010)
New Revision: 14000

Modified:
   django/trunk/django/core/mail/message.py
   django/trunk/docs/topics/email.txt
   django/trunk/tests/regressiontests/mail/tests.py
Log:
Fixed #7722 - added support for CC in EmailMessage.

Thanks to roberto.digirolamo for the report and initial patch, and
dougvanhorn and SmileyChris for further work on the patch.

Modified: django/trunk/django/core/mail/message.py
===
--- django/trunk/django/core/mail/message.py2010-10-07 22:33:02 UTC (rev 
13999)
+++ django/trunk/django/core/mail/message.py2010-10-07 23:36:02 UTC (rev 
14000)
@@ -105,7 +105,7 @@
 encoding = None # None => use settings default
 
 def __init__(self, subject='', body='', from_email=None, to=None, bcc=None,
- connection=None, attachments=None, headers=None):
+ connection=None, attachments=None, headers=None, cc=None):
 """
 Initialize a single email message (which can be sent to multiple
 recipients).
@@ -119,6 +119,11 @@
 self.to = list(to)
 else:
 self.to = []
+if cc:
+assert not isinstance(cc, basestring), '"cc" argument must be a 
list or tuple'
+self.cc = list(cc)
+else:
+self.cc = []
 if bcc:
 assert not isinstance(bcc, basestring), '"bcc" argument must be a 
list or tuple'
 self.bcc = list(bcc)
@@ -145,6 +150,8 @@
 msg['Subject'] = self.subject
 msg['From'] = self.extra_headers.get('From', self.from_email)
 msg['To'] = ', '.join(self.to)
+if self.cc:
+msg['Cc'] = ', '.join(self.cc)
 
 # Email header names are case-insensitive (RFC 2045), so we have to
 # accommodate that when doing comparisons.
@@ -162,9 +169,9 @@
 def recipients(self):
 """
 Returns a list of all recipients of the email (includes direct
-addressees as well as Bcc entries).
+addressees as well as Cc and Bcc entries).
 """
-return self.to + self.bcc
+return self.to + self.cc + self.bcc
 
 def send(self, fail_silently=False):
 """Sends the email message."""
@@ -252,7 +259,8 @@
 alternative_subtype = 'alternative'
 
 def __init__(self, subject='', body='', from_email=None, to=None, bcc=None,
-connection=None, attachments=None, headers=None, 
alternatives=None):
+connection=None, attachments=None, headers=None, alternatives=None,
+cc=None):
 """
 Initialize a single email message (which can be sent to multiple
 recipients).
@@ -261,7 +269,7 @@
 bytestrings). The SafeMIMEText class will handle any necessary encoding
 conversions.
 """
-super(EmailMultiAlternatives, self).__init__(subject, body, 
from_email, to, bcc, connection, attachments, headers)
+super(EmailMultiAlternatives, self).__init__(subject, body, 
from_email, to, bcc, connection, attachments, headers, cc)
 self.alternatives=alternatives or []
 
 def attach_alternative(self, content, mimetype):

Modified: django/trunk/docs/topics/email.txt
===
--- django/trunk/docs/topics/email.txt  2010-10-07 22:33:02 UTC (rev 13999)
+++ django/trunk/docs/topics/email.txt  2010-10-07 23:36:02 UTC (rev 14000)
@@ -235,6 +235,9 @@
 All parameters are optional and can be set at any time prior to calling the
 ``send()`` method.
 
+.. versionchanged:: 1.3
+   The ``cc`` argument was added.
+
 * ``subject``: The subject line of the e-mail.
 
 * ``body``: The body text. This should be a plain text message.
@@ -261,6 +264,9 @@
   caller to ensure header names and values are in the correct format for
   an e-mail message.
 
+* ``cc``: A list or tuple of recipient addresses used in the "Cc" header
+  when sending the e-mail.
+
 For example::
 
 email = EmailMessage('Hello', 'Body goes here', 'f...@example.com',

Modified: django/trunk/tests/regressiontests/mail/tests.py
===
--- django/trunk/tests/regressiontests/mail/tests.py2010-10-07 22:33:02 UTC 
(rev 13999)
+++ django/trunk/tests/regressiontests/mail/tests.py2010-10-07 23:36:02 UTC 
(rev 14000)
@@ -417,4 +417,30 @@
 >>> settings.ADMINS = old_admins
 >>> settings.MANAGERS = old_managers
 
+# Add Cc to the email argument list (#7722)
+
+>>> email = EmailMessage('Subject', 'Content', 'f...@example.com', 
['t...@example.com'], cc=['c...@example.com'])
+>>> message = email.message()
+>>> message['Cc']
+'c...@example.com'
+>>> email.recipients()
+['t...@example.com', 'c...@example.com']
+
+>>> email = EmailMessage('Subject', 'Content', 'f...@example.com', 
['t...@example.com','ot...@example.com'], cc=['c...@example.com', 
'cc.ot..

Re: [Django] #5590: JSON encoding fails on Promise (result of gettext_lazy)

[Django]

#5590: JSON encoding fails on Promise (result of gettext_lazy)
+---
  Reporter:  jdunck | Owner:  nobody
 
Status:  closed | Milestone:
 
 Component:  Serialization  |   Version:  SVN   
 
Resolution:  duplicate  |  Keywords:  unicode json 
serialization i18n
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

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

Comment:

 Malcolm closed the almost identical #5868 with a documentation fix, and
 commented that we don't need this kind of change applied to Django's
 serializers on the grounds that we won't ever pass a lazy translation
 object to Django's serializers. I also can't see how a queryset should
 ever contain lazy translation objects - a queryset represents data from
 the database, and so shouldn't ever have that kind of object. It's not at
 all obvious to me that you '''can''' serialize such data, in terms of
 semantics - a lazy translation object is not equal to that object
 translated into a specific language, and you can't convert back. So
 raising an exception seems like good default behaviour for this situation,
 rather than silently losing information.

 So we had Jacob who set Accepted on this ticket, but Malcolm who closed an
 almost identical ticket with a documentation fix.  I'm going to go with
 the latter, because it seems like Malcolm thought about it more and I
 agree with his reason, and close this as a duplicate. If normal Django
 querysets do indeed return lazy translation objects, please re-open with
 details of how this happens, preferably a test case. If it is some custom
 unusual behaviour that has resulted in this, I think we should start a
 thread on django-devs so we can decide whether that is useful behaviour to
 support in our serializers.

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

[Changeset] r13999 - django/branches/releases/1.2.X/django/contrib/admin/templates/admin

[noreply]

Author: lukeplant
Date: 2010-10-07 17:33:02 -0500 (Thu, 07 Oct 2010)
New Revision: 13999

Modified:
   
django/branches/releases/1.2.X/django/contrib/admin/templates/admin/pagination.html
Log:
[1.2.X] Fixed #5425 - Incorrect plurals in admin pagination template.

Thanks to Petr Marhoun for the report, and mk for the patch.

Backport of [13998] from trunk

Modified: 
django/branches/releases/1.2.X/django/contrib/admin/templates/admin/pagination.html
===
--- 
django/branches/releases/1.2.X/django/contrib/admin/templates/admin/pagination.html
 2010-10-07 22:30:38 UTC (rev 13998)
+++ 
django/branches/releases/1.2.X/django/contrib/admin/templates/admin/pagination.html
 2010-10-07 22:33:02 UTC (rev 13999)
@@ -6,7 +6,7 @@
 {% paginator_number cl i %}
 {% endfor %}
 {% endif %}
-{{ cl.result_count }} {% ifequal cl.result_count 1 %}{{ cl.opts.verbose_name 
}}{% else %}{{ cl.opts.verbose_name_plural }}{% endifequal %}
+{% blocktrans with cl.opts.verbose_name as verbose_name and 
cl.opts.verbose_name_plural as verbose_name_plural count cl.result_count as 
count %}{{ count }} {{ verbose_name }}{% plural %}{{ count }} {{ 
verbose_name_plural }}{% endblocktrans %}
 {% if show_all_url %}  {% trans 'Show all' %}{% endif %}
 {% if cl.formset and cl.result_count %}{% endif %}
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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.

[Changeset] r13998 - django/trunk/django/contrib/admin/templates/admin

[noreply]

Author: lukeplant
Date: 2010-10-07 17:30:38 -0500 (Thu, 07 Oct 2010)
New Revision: 13998

Modified:
   django/trunk/django/contrib/admin/templates/admin/pagination.html
Log:
Fixed #5425 - Incorrect plurals in admin pagination template.

Thanks to Petr Marhoun for the report, and mk for the patch.

Modified: django/trunk/django/contrib/admin/templates/admin/pagination.html
===
--- django/trunk/django/contrib/admin/templates/admin/pagination.html   
2010-10-07 15:50:36 UTC (rev 13997)
+++ django/trunk/django/contrib/admin/templates/admin/pagination.html   
2010-10-07 22:30:38 UTC (rev 13998)
@@ -6,7 +6,7 @@
 {% paginator_number cl i %}
 {% endfor %}
 {% endif %}
-{{ cl.result_count }} {% ifequal cl.result_count 1 %}{{ cl.opts.verbose_name 
}}{% else %}{{ cl.opts.verbose_name_plural }}{% endifequal %}
+{% blocktrans with cl.opts.verbose_name as verbose_name and 
cl.opts.verbose_name_plural as verbose_name_plural count cl.result_count as 
count %}{{ count }} {{ verbose_name }}{% plural %}{{ count }} {{ 
verbose_name_plural }}{% endblocktrans %}
 {% if show_all_url %}  {% trans 'Show all' %}{% endif %}
 {% if cl.formset and cl.result_count %}{% endif %}
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14370: Adding support for Autocomplete in contrib.admin

[Django]

#14370: Adding support for Autocomplete in contrib.admin
---+
  Reporter:  tyrion| Owner:  nobody  
Status:  new   | Milestone:  
 Component:  django.contrib.admin  |   Version:  1.2 
Resolution:|  Keywords:  autocomplete
 Stage:  Unreviewed| Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by tyrion):

 Now the autocomplete feature can be used with any type of field.[[BR]]
 i.e. (email is an EmailField)
 {{{
 #!python
 class MyModelAdmin(admin.ModelAdmin):
 autocomplete_fields = dict(
 email = dict(
 queryset = User.objects.all(),
 fields = ('^email', '^username'),
 id = 'email',
 value = 'email',
 ),
 )
 }}}

-- 
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-upda...@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] #14354: Check password is not None in User.check_password

[Django]

#14354: Check password is not None in User.check_password
-+--
  Reporter:  berryp  | Owner:  laurentluce
Status:  assigned| Milestone:  1.3
 Component:  Authentication  |   Version:  1.2
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by laurentluce):

 Reformat the description.

 I attached a patch with the following changes:

 - in set_password(), check for raw_password and if None or , call
 set_unusable_password(), otherwise same as before[[BR]]

 - in has_usable_password(), return True only if password is not None, or
 '!'[[BR]]

 - because of the 2 changes above, we can simplify a bit create_user() by
 just calling set_password() for all cases. No need to test password and
 branch out.[[BR]]

 - basic.py tests are now unittests and not doctests

-- 
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-upda...@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] #14354: Check password is not None in User.check_password

[Django]

#14354: Check password is not None in User.check_password
-+--
  Reporter:  berryp  | Owner:  laurentluce
Status:  assigned| Milestone:  1.3
 Component:  Authentication  |   Version:  1.2
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by laurentluce):

  * has_patch:  0 => 1

Comment:

 I attached a patch with the following changes:

 - in set_password(), check for raw_password and if None or '', call
 set_unusable_password(), otherwise same as before
 - in has_usable_password(), return True only if password is not None, ''
 or '!'
 - because of the 2 changes above, we can simplify a bit create_user() by
 just calling set_password() for all cases. No need to test password and
 branch out.
 - basic.py tests are now unittests and not doctests

-- 
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-upda...@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] #14417: UnicodeDecodeError exception in recent actions

[Django]

#14417: UnicodeDecodeError exception in recent actions
---+
  Reporter:  ctetruite | Owner:  nobody 
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.2
Resolution:|  Keywords:  unicode
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by ctetruite):

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

Comment:

 Stack trace

 {{{
 Traceback:
 File "/usr/lib/python2.6/site-packages/django/core/handlers/base.py" in
 get_response
   100. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/usr/lib/python2.6/site-packages/django/contrib/admin/sites.py" in
 wrapper
   207. return self.admin_view(view, cacheable)(*args,
 **kwargs)
 File "/usr/lib/python2.6/site-packages/django/utils/decorators.py" in
 _wrapped_view
   76. response = view_func(request, *args, **kwargs)
 File "/usr/lib/python2.6/site-packages/django/views/decorators/cache.py"
 in _wrapped_view_func
   69. response = view_func(request, *args, **kwargs)
 File "/usr/lib/python2.6/site-packages/django/contrib/admin/sites.py" in
 inner
   190. return view(request, *args, **kwargs)
 File "/usr/lib/python2.6/site-packages/django/views/decorators/cache.py"
 in _wrapped_view_func
   69. response = view_func(request, *args, **kwargs)
 File "/usr/lib/python2.6/site-packages/django/contrib/admin/sites.py" in
 index
   396. context_instance=context_instance
 File "/usr/lib/python2.6/site-packages/django/shortcuts/__init__.py" in
 render_to_response
   20. return HttpResponse(loader.render_to_string(*args, **kwargs),
 **httpresponse_kwargs)
 File "/usr/lib/python2.6/site-packages/django/template/loader.py" in
 render_to_string
   186. return t.render(context_instance)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 render
   173. return self._render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 _render
   167. return self.nodelist.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 render
   796. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.6/site-packages/django/template/debug.py" in
 render_node
   72. result = node.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/loader_tags.py" in
 render
   125. return compiled_parent._render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 _render
   167. return self.nodelist.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 render
   796. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.6/site-packages/django/template/debug.py" in
 render_node
   72. result = node.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/loader_tags.py" in
 render
   125. return compiled_parent._render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 _render
   167. return self.nodelist.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 render
   796. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.6/site-packages/django/template/debug.py" in
 render_node
   72. result = node.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/loader_tags.py" in
 render
   62. result = block.nodelist.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 render
   796. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.6/site-packages/django/template/debug.py" in
 render_node
   72. result = node.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py" in
 render
   260. return self.nodelist_false.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/__init__.py" in
 render
   796. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.6/site-packages/django/template/debug.py" in
 render_node
   72. result = node.render(context)
 File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py" in
 render
   174. nodelist.append(node.render(context))
 File "/usr/lib/python2.6/site-packages/django/template/defaulttags.py" in
 render
   258. return self.nodelist_

Re: [Django] #14354: Check password is not None in User.check_password

[Django]

#14354: Check password is not None in User.check_password
-+--
  Reporter:  berryp  | Owner:  laurentluce
Status:  assigned| Milestone:  1.3
 Component:  Authentication  |   Version:  1.2
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by laurentluce):

  * status:  new => assigned

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14354: Check password is not None in User.check_password

[Django]

#14354: Check password is not None in User.check_password
-+--
  Reporter:  berryp  | Owner:  laurentluce
Status:  new | Milestone:  1.3
 Component:  Authentication  |   Version:  1.2
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by laurentluce):

  * owner:  nobody => laurentluce
  * milestone:  => 1.3

-- 
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-upda...@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] #14417: UnicodeDecodeError exception in recent actions

[Django]

#14417: UnicodeDecodeError exception in recent actions
--+-
 Reporter:  ctetruite |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.2   
 Keywords:  unicode   |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Here is my situation.

 I have a model with this verbose_name in meta data : u"Matériel
 d'occasion". The thing is this is a non ascii string. I do some stuff on
 an object of this model. Then, when I go the the admin page, I get this
 server error :
 {{{
 Caught UnicodeDecodeError while rendering: ('ascii', "Mat\xc3\xa9riel
 d'occasion", 3, 4, 'ordinal not in range(128)')
 }}}

 It occurs in the template
 ''django/contrib/admin/templates/admin/index.html'' at line 70 :
 {{{
 {% filter capfirst %}{% trans
 entry.content_type.name %}{% endfilter %}
 }}}

-- 
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-upda...@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] #13910: Add generator version of Template.render(Context)

[Django]

#13910: Add generator version of Template.render(Context)
--+-
  Reporter:  rooney   | Owner:  nobody
Status:  reopened | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by EmilStenstrom):

 Some context to why I think this is important:

 For performance reasons it's good to have your static media files accessed
 as fast as possible. In PHP you can achieve this by calling flush()
 directly after the  tag. This make sure the media files start
 loading as fast as possible, even though the rest of the page is still
 doing expensive db operations. This is also mentioned in Yahoo's
 guidelines for performance:
 http://developer.yahoo.com/performance/rules.html#flush

-- 
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-upda...@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] #14405: problem in login view

[Django]

#14405: problem in login view
-+--
  Reporter:  bayazee | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  1.2   
Resolution:  |  Keywords:  login 
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * has_patch:  0 => 1
  * needs_tests:  0 => 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 post to this group, send email to django-upda...@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] #14405: problem in login view

[Django]

#14405: problem in login view
-+--
  Reporter:  bayazee | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  1.2   
Resolution:  |  Keywords:  login 
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by christandiono):

 Hmm, so it does. This patch would seem to fix it...

-- 
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-upda...@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] #14416: ImageField forms require an enctype, not documented

[Django]

#14416: ImageField forms require an enctype, not documented
+---
  Reporter:  airstrike  | Owner:  nobody
  
Status:  new| Milestone:
  
 Component:  Documentation  |   Version:
  
Resolution: |  Keywords:  ImageField enctype form 
HTML
 Stage:  Unreviewed | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by lrekucki):

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

Comment:

 This is documented: http://docs.djangoproject.com/en/dev/ref/forms/api
 /#binding-uploaded-files. Description of both FileField and ImageField
 link to that page. There is also a link in "Working with forms" article.

-- 
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-upda...@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] #11297: In admin, no always EMPTY_CHANGELIST_VALUE is used when item value is None

[Django]

#11297: In admin, no always EMPTY_CHANGELIST_VALUE is used when item value is 
None
---+
  Reporter:  spinyol   | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mk):

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

Comment:

 I think this problem has been fixed while fixing #342 in [11965]

-- 
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-upda...@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] #14416: ImageField forms require an enctype, not documented

[Django]

#14416: ImageField forms require an enctype, not documented
--+-
 Reporter:  airstrike |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:
 Keywords:  ImageField enctype form HTML  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Well, this may very well not be a Django issue, but I can't help but
 suggest that this small caveat be documented somewhere.

 Forms with ImageField require an enctype attribute such as . Yes, it's HTML,
 not Django. But frustrating nonetheless.

 As you can see by reactions in http://stackoverflow.com/questions/680770
 /django-imagefield-not-working-properly-via-modelform many new developers
 have a tough time when dealing with this issue. I'm not bold enough to
 submit a documentation patch, but it should be fairly simple to explain.

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

[Changeset] r13997 - in django/trunk: django/forms tests/regressiontests/forms

[noreply]

Author: adrian
Date: 2010-10-07 10:50:36 -0500 (Thu, 07 Oct 2010)
New Revision: 13997

Modified:
   django/trunk/django/forms/fields.py
   django/trunk/tests/regressiontests/forms/fields.py
Log:
Fixed #11907 -- EmailField now runs strip() on its input. This means mistakenly 
including leading or trailing spaces will not cause a validation error, and 
clean() will remove those spaces. Thanks, krisneuharth, djansoft and SmileyChris

Modified: django/trunk/django/forms/fields.py
===
--- django/trunk/django/forms/fields.py 2010-10-07 15:13:00 UTC (rev 13996)
+++ django/trunk/django/forms/fields.py 2010-10-07 15:50:36 UTC (rev 13997)
@@ -448,6 +448,10 @@
 }
 default_validators = [validators.validate_email]
 
+def clean(self, value):
+value = self.to_python(value).strip()
+return super(EmailField, self).clean(value)
+
 class FileField(Field):
 widget = ClearableFileInput
 default_error_messages = {

Modified: django/trunk/tests/regressiontests/forms/fields.py
===
--- django/trunk/tests/regressiontests/forms/fields.py  2010-10-07 15:13:00 UTC 
(rev 13996)
+++ django/trunk/tests/regressiontests/forms/fields.py  2010-10-07 15:50:36 UTC 
(rev 13997)
@@ -430,6 +430,7 @@
 self.assertEqual(u'', f.clean(''))
 self.assertEqual(u'', f.clean(None))
 self.assertEqual(u'per...@example.com', f.clean('per...@example.com'))
+self.assertEqual(u'exam...@example.com', f.clean('  
exam...@example.com  \t   \t '))
 self.assertRaisesErrorWithMessage(ValidationError, "[u'Enter a valid 
e-mail address.']", f.clean, 'foo')
 self.assertRaisesErrorWithMessage(ValidationError, "[u'Enter a valid 
e-mail address.']", f.clean, 'foo@')
 self.assertRaisesErrorWithMessage(ValidationError, "[u'Enter a valid 
e-mail address.']", f.clean, 'f...@bar')

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #12889: Using annotation unexpectedly returns DecimalFields as floats

[Django]

#12889: Using annotation unexpectedly returns DecimalFields as floats
---+
  Reporter:  KyleMac   | Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  SVN 
Resolution:|  Keywords:  annotate
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by mk):

 This is a related issue: #12889 Errors when using character fields for
 aggregation

-- 
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-upda...@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] #13844: Errors when using character fields for aggregation

[Django]

#13844: Errors when using character fields for aggregation
---+
  Reporter:  zeg...@gmail.com  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by mk):

 This is a related issue: #12889 Using annotation unexpectedly returns
 DecimalFields as floats

-- 
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-upda...@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] #14193: prepopulated_fields should concatenate fields in given order

[Django]

#14193: prepopulated_fields should concatenate fields in given order
---+
  Reporter:  bmihelac  | Owner:  bmihelac
Status:  assigned  | Milestone:  1.3 
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Ready for checkin | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by mk):

  * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14411: Inline delete not prompting cascade delete warning

[Django]

#14411: Inline delete not prompting cascade delete warning
+---
  Reporter:  subsume| Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by Ubercore):

 None of the options are perfect, agreed, but I'd rather see a solution
 that minimizes data loss. Better to document that a user may lose changed
 data on the admin form than document that a user may lose an entire
 table's worth of data to a cascading delete. A failure on the user's part
 to heed the warning is far less catastrophic.

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

[Changeset] r13996 - django/trunk/django/conf

[noreply]

Author: adrian
Date: 2010-10-07 10:13:00 -0500 (Thu, 07 Oct 2010)
New Revision: 13996

Modified:
   django/trunk/django/conf/global_settings.py
Log:
Set default PROFANITIES_LIST setting to an empty tuple. This is technically 
backwards-compatible if you rely on a Web framework providing you with a 
woefully incomplete list of naughty words. Fixes #8794

Modified: django/trunk/django/conf/global_settings.py
===
--- django/trunk/django/conf/global_settings.py 2010-10-06 22:56:52 UTC (rev 
13995)
+++ django/trunk/django/conf/global_settings.py 2010-10-07 15:13:00 UTC (rev 
13996)
@@ -439,7 +439,7 @@
 
 # The profanities that will trigger a validation error in the
 # 'hasNoProfanities' validator. All of these should be in lowercase.
-PROFANITIES_LIST = ('asshat', 'asshead', 'asshole', 'cunt', 'fuck', 'gook', 
'nigger', 'shit')
+PROFANITIES_LIST = ()
 
 # The group ID that designates which users are banned.
 # Set to None if you're not using it.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #3100: Support for arguments on intermediate tag tokens (ex. {% if arg %}{% elif arg %}{% endif %})

[Django]

#3100: Support for arguments on intermediate tag tokens (ex. {% if arg %}{% elif
arg %}{% endif %})
---+
  Reporter:  Eric Van Dewoestine   | Owner: 
 adrian
Status:  reopened  | Milestone: 
   
 Component:  Template system   |   Version: 
 SVN   
Resolution:|  Keywords: 
   
 Stage:  Accepted  | Has_patch: 
 1 
Needs_docs:  1 |   Needs_tests: 
 0 
Needs_better_patch:  1 |  
---+
Changes (by mk):

  * needs_docs:  0 => 1
  * needs_tests:  1 => 0

Comment:

 A differentiation between intermediate tags which accept arguments and
 tags who don't seems to be necessary to support this use case properly
 (without breaking backwards-compatibility or deleting tests).

 The attached patch adds another argument to django.template.Parser.parse;
 parse_until is complemented by parse_until_args_allowed. The included if-
 tag supporting {% elif %} makes use of this. The previously deleted "extra
 endblock" tests have been restored and they pass, as they should.

 The documentation about writing custom tags would have to be extended for
 this, though.

-- 
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-upda...@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] #12886: .aggregate() does not honour sliced queryset

[Django]

#12886: .aggregate() does not honour sliced queryset
--+-
  Reporter:  t...@subnetz.org  | Owner:  
Status:  new  | Milestone:  
 Component:  ORM aggregation  |   Version:  1.2-beta
Resolution:   |  Keywords:  
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by gruszczy):

 * cc: gruszczy (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-upda...@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] #14411: Inline delete not prompting cascade delete warning

[Django]

#14411: Inline delete not prompting cascade delete warning
+---
  Reporter:  subsume| Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: subsume (removed)
 * cc: subs...@gmail.com, jdu...@gmail.com (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-upda...@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] #12886: .aggregate() does not honour sliced queryset

[Django]

#12886: .aggregate() does not honour sliced queryset
--+-
  Reporter:  t...@subnetz.org  | Owner:  
Status:  new  | Milestone:  
 Component:  ORM aggregation  |   Version:  1.2-beta
Resolution:   |  Keywords:  
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by gruszczy):

 I have managed to patch this, but encountered larger problem, that I have
 problems with. I have added following test to
 modeltests/aggregation/tests.py:

 {{{
 def test_join_annotate_aggregate(self):
 vals =
 Book.objects.all().annotate().aggregate(Max("authors__age"))
 self.assertEqual(len(vals), 1)
 self.assertEqual(vals["authors__age__max"], 57)
 }}}

 and it causes following exception:

 {{{
 ==
 ERROR: test_join_annotate_aggregate
 (modeltests.aggregation.tests.BaseAggregateTestCase)
 --
 Traceback (most recent call last):
   File
 "/home/gruszczy/Programy/django/tests/modeltests/aggregation/tests.py",
 line 21, in test_join_annotate_aggregate
 vals = Book.objects.all().annotate().aggregate(Max("authors__age"))
   File "/home/gruszczy/Programy/django/django/db/models/query.py", line
 312, in aggregate
 return query.get_aggregation(using=self.db)
   File "/home/gruszczy/Programy/django/django/db/models/sql/query.py",
 line 366, in get_aggregation
 result = query.get_compiler(using).execute_sql(SINGLE)
   File "/home/gruszczy/Programy/django/django/db/models/sql/compiler.py",
 line 729, in execute_sql
 cursor.execute(sql, params)
   File
 "/home/gruszczy/Programy/django/django/db/backends/sqlite3/base.py", line
 200, in execute
 return Database.Cursor.execute(self, query, params)
 DatabaseError: no such column: T5.age

 }}}

 Generated SQL looks like this:


 {{{
 SELECT "aggregation_book"."id" AS "id", "aggregation_book"."isbn" AS
 "isbn", "aggregation_book"."name" AS "name", "aggregation_book"."pages" AS
 "pages", "aggregation_book"."rating" AS "rating",
 "aggregation_book"."price" AS "price", "aggregation_book"."contact_id" AS
 "contact_id",
 "aggregation_book"."publisher_id" AS "publisher_id",
 "aggregation_book"."pubdate" AS "pubdate" FROM "aggregation_book" LEFT
 OUTER JOIN
 "aggregation_book_authors" ON ("aggregation_book"."id" =
 "aggregation_book_authors"."book_id") LEFT OUTER JOIN "aggregation_author"
 T5 ON
 ("aggregation_book_authors"."author_id" = T5."id") GROUP BY
 "aggregation_book"."id", "aggregation_book"."isbn",
 "aggregation_book"."name",
 "aggregation_book"."pages", "aggregation_book"."rating",
 "aggregation_book"."price", "aggregation_book"."contact_id",
 "aggregation_book"."publisher_id", "aggregation_book"."pubdate"

 }}}

 I am posting my partial patch with tests, so maybe someone could direct
 me, where I should go from here and how can I solve the encountered bug.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14190: images, news and keywords in sitemap.xml

[Django]

#14190: images, news and keywords in sitemap.xml
---+
  Reporter:  aronchi   | Owner:  Twidi  
Status:  assigned  | Milestone: 
 Component:  Contrib apps  |   Version:  1.2
Resolution:|  Keywords:  sitemap.xml news images
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by Twidi):

  * status:  new => assigned
 * cc: s.an...@twidi.com (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => Twidi
  * needs_docs:  => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14415: Multiple aliases for one database: testing problems

[Django]

#14415: Multiple aliases for one database: testing problems
+---
  Reporter:  shai   | Owner:  nobody
   
Status:  new| Milestone:
   
 Component:  Testing framework  |   Version:  1.2   
   
Resolution: |  Keywords:  multidb, multiple 
databases, multiple aliases
 Stage:  Accepted   | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13211: More Group Documentation in the Auth Page

[Django]

#13211: More Group Documentation in the Auth Page
+---
  Reporter:  b14ck  | Owner:  nobody
  
Status:  new| Milestone:
  
 Component:  Documentation  |   Version:  SVN   
  
Resolution: |  Keywords:  group, authentication, 
documentation
 Stage:  Accepted   | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * component:  Authentication => Documentation

-- 
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-upda...@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] #14405: problem in login view

[Django]

#14405: problem in login view
-+--
  Reporter:  bayazee | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Authentication  |   Version:  1.2   
Resolution:  |  Keywords:  login 
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by bayazee):

 Replying to [comment:1 christandiono]:
 > What's your settings.LOGIN_REDIRECT_URL? The default login view should
 redirect you automatically...

 yes, it is work. but whats happen if some user use login url or we have
 some links to login page.
 in this situation we can see empty login page again !!
 and i think this is a bug.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #2016: [patch] Decorator for template tags that load objects

[Django]

#2016: [patch] Decorator for template tags that load objects
+---
  Reporter:  ja...@pengale.com  | Owner:  nobody
Status:  assigned   | Milestone:
 Component:  Template system|   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 Updated patch for current trunk.

-- 
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-upda...@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] #14167: Using Instances in Generic Create/Update/Delete

[Django]

#14167: Using Instances in Generic Create/Update/Delete
+---
  Reporter:  monokrome  | Owner:  nobody
Status:  new| Milestone:
 Component:  Generic views  |   Version:  1.2   
Resolution: |  Keywords:  generic views DRY instance
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Changes (by mk):

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

Comment:

 I'm not sure whether working on this ticket makes sense at all with the
 upcoming class-based generic views (#6735).

 I'll still comment on the given patch though.

 * Documentation is missing.
 * Passing instance and model at the same time should be forbidden.
 * The instance should be used to initialize the form on GET requests too,
 not only with POST.
 * No 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-upda...@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] #12418: object_detail ObjectDoesNotExist message isn't unicode

[Django]

#12418: object_detail ObjectDoesNotExist message isn't unicode
+---
  Reporter:  mk | Owner:  nobody
Status:  new| Milestone:
 Component:  Generic views  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

  * needs_tests:  1 => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #11907: EmailField should run strip()

[Django]

#11907: EmailField should run strip()
+---
  Reporter:  whatcould  | Owner:  SmileyChris
Status:  new| Milestone: 
 Component:  Forms  |   Version:  1.1
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * owner:  djansoft => SmileyChris
  * status:  reopened => new
  * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #12064: Impossible to conditionally include potentially non-existant templates

[Django]

#12064: Impossible to conditionally include potentially non-existant templates
-+--
  Reporter:  mkruisselbrink  | Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by mk):

 Ticket #3544 is related too (Fix {% include %} to allow recursive
 includes) and could be solved at the same time.

-- 
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-upda...@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] #9456: Extend with tag to support multiple bindings

[Django]

#9456: Extend with tag to support multiple bindings
-+--
  Reporter:  eibaan  | Owner:  lrekucki
Status:  new | Milestone:  
 Component:  Template system |   Version:  1.0 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by lrekucki):

  * owner:  nobody => lrekucki
  * status:  reopened => new

Comment:

 Ok, I'm goning to split the with part form #7817. It's diffrent from patch
 on this ticket, that it resolves all variables in the outer context, so
 you can do
 {{{
   {% with x as y and y as x %}{% endwith %}
 }}}
 to swap the variables. It's also with line how Python does assignment and
 how most languages handle "let" statement (which I find very similar in
 semantic to the with 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-upda...@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] #14415: Multiple aliases for one database: testing problems

[Django]

#14415: Multiple aliases for one database: testing problems
---+
 Reporter:  shai   |   Owner:  
nobody
   Status:  new|   Milestone:   
 
Component:  Testing framework  | Version:  1.2  
 
 Keywords:  multidb, multiple databases, multiple aliases  |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 In a setting where the multiple-databases feature is used to create
 multiple aliases for one database, the testing framework can get a little
 confused.

 For ease of reference, assume we have the following dictionary defining
 database parameters:
 {{{
 db_params = dict (
 NAME = 'main',
 ENGINE = 'django.db.backends.whatever',
 USER = 'user',
 PASSWORD = 'password',
 HOST = '',
 PORT = ''
 )
 }}}

 == The relatively benign cases ==

 In these cases, the test framework just treats the two aliases as separate
 databases; which means it first creates the test database for one alias,
 then tries to create the test database for the second one, running into an
 error because (of course) it already exists. The user is asked to choose
 between destroying the existing database (in order to recreate it) and
 canceling the test. In cases where database routers constrict models to a
 specific alias, this may completely prevent testing (or at least some of
 the tests).

 This happens if at least one of two conditions hold:

 === The dictionaries used to define the alias are distinct ===

 That is, the databases are defined by
 {{{
 DATABASES = {
 'default' : db_params,
 'other' :   db_params.copy()
 }
 }}}
 or some equivalent

 === Test name is explicitly specified ===

 That is, `db_params` looks like:
 {{{
 db_params = dict (
 NAME = 'main',
 TEST_NAME = 'test_main',
 ... # same as above
 )
 }}}

 The databases may then be specified by the more natural
 {{{
 DATABASES = {
 'default' : db_params,
 'other' :   db_params
 }
 }}}

 == The more dangerous case ==

 In this case, the testing framework creates spurious databases and
 finalizes be destroying the main, non-test database.

 This happens when none of the above applies -- that is, `db_params` does
 not include
 the `TEST_NAME` entry, relying on the default `test_` prefix addition, and
 databases
 are specified by two references to the same dictionary (as in the last
 definition above).
 Regretfully, one may expect this to be the common use case in a multiple-
 aliases-for-one-database
 approach.

 In detail: With the definitions above, the testing framework first creates
 a `test_main` database, then a `test_test_main` database, and runs its
 tests with both of them present; then, during tear-down, it drops the
 `test_test_main` and *`main`* databases, leaving `test_main` in place.

 == A word for fixers ==

 For whoever wants to work on this ticket (perhaps myself...), Russel
 Keith-Magee has [http://groups.google.com/group/django-
 developers/browse_thread/thread/f3fac51f7ec56dfa said] that
 {{{
 #!html
 
  ...this almost rates as an 'easy pickings' ticket. This
  is a situation where you'll get a pass on having a test as part of the
  patch; testing test setup is one of those areas that's almost
  impossible to validate, so whoever commits (probably me) will just
  take it for a very good walk before checking in.
 
 }}}

-- 
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-upda...@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] #11907: EmailField should run strip()

[Django]

#11907: EmailField should run strip()
+---
  Reporter:  whatcould  | Owner:  djansoft
Status:  reopened   | Milestone:  
 Component:  Forms  |   Version:  1.1 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Comment:

 This is in the same basket as #5714 (also originally marked as a dupe of
 #6362).

 Malcolm reopened that one, so I'm going to reopen this one.

-- 
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-upda...@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] #5714: Date/Time fields' clean methods need strip()

[Django]

#5714: Date/Time fields' clean methods need strip()
--+-
  Reporter:  Simon Litchfield   | Owner:  
nobody
Status:  reopened | Milestone:  
  
 Component:  Forms|   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by mk):

  * needs_tests:  1 => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #7817: {% include "tpl" with foo=x bar=y %}

[Django]

#7817: {% include "tpl" with foo=x bar=y %}
-+--
  Reporter:  emulbreh| Owner:  lrekucki
Status:  new | Milestone:  
 Component:  Template system |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by anonymous):

 * cc: mlo...@gmail.com (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-upda...@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] #9456: Extend with tag to support multiple bindings

[Django]

#9456: Extend with tag to support multiple bindings
-+--
  Reporter:  eibaan  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Template system |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * status:  closed => reopened
  * resolution:  duplicate =>
  * stage:  Unreviewed => Design decision needed

Comment:

 #7817 dealt with two separate feature requests here, one for `{% with %}`
 and one for `{% include %}`.

 I'm leaving that one to deal with just `{% include %}` and reopening this
 one to track `{% with %}`

-- 
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-upda...@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] #7817: {% include "tpl" with foo=x bar=y %}

[Django]

#7817: {% include "tpl" with foo=x bar=y %}
-+--
  Reporter:  emulbreh| Owner:  lrekucki
Status:  new | Milestone:  
 Component:  Template system |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by SmileyChris):

  * needs_better_patch:  0 => 1
  * summary:  {% with foo as x, bar as y %}, {% include "tpl" with foo as
  x, bar as y %} => {% include "tpl" with foo=x
  bar=y %}

Comment:

 There are two separate feature requests here, one for `{% with %}` and one
 for `{% include %}`.

 Although similar, they are separate requests which may have separate
 resolutions. Let's use this one for `{% include %}` - I'm reopening #9456
 to track `{% with %}`.
 I'm more keen on this one, ambivalent about the other one.

-- 
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-upda...@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] #6580: Default argument to `getlist` on QueryDict

[Django]

#6580: Default argument to `getlist` on QueryDict
+---
  Reporter:  dcramer| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

  * needs_better_patch:  1 => 0

Comment:

 Docstring updated, patch ported to trunk.

-- 
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-upda...@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] #5425: Incorrect plurals in admin pagination template

[Django]

#5425: Incorrect plurals in admin pagination template
+---
  Reporter:  Petr Marhoun   | Owner:  
nobody 
Status:  reopened   | Milestone:
 
 Component:  django.contrib.admin   |   Version:
 
Resolution: |  Keywords:  
admin, internationalization
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by mk):

  * needs_better_patch:  1 => 0
  * stage:  Accepted => Ready for checkin

Comment:

 We have a blocktrans tag supporting pluralization now. Trivial one-line
 patch attached, test suite still passes.

-- 
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-upda...@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] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

[Django]

#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
--+-
  Reporter:  mattbennett  | Owner:  nobody  
 
Status:  new  | Milestone:  
 
 Component:  Forms|   Version:  SVN 
 
Resolution:   |  Keywords:  datetime, forms, 
datetimefield, timefield
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  1   
 
Needs_better_patch:  1|  
--+-
Comment (by mk):

 This patch not only needs tests, but also other improvements. It will fall
 on the face with dates f.e. in german format. The stupid check for '.' in
 the string representation will not do the right thing with "03.11.2009
 12:21:10".

-- 
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-upda...@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] #1946: [patch] to allow overriding of default sequence name

[Django]

#1946: [patch] to allow overriding of default sequence name
---+
  Reporter:  ab...@cabal.org.uk| Owner:  shmengie
Status:  assigned  | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: boton...@gmail.com (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-upda...@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] #14390: set_password functionality outside of the User model

[Django]

#14390: set_password functionality outside of the User model
--+-
  Reporter:  k...@lysator.liu.se  | Owner:  lrekucki
Status:  new  | Milestone:  
 Component:  Authentication   |   Version:  1.2 
Resolution:   |  Keywords:  
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by lrekucki):

  * owner:  nobody => lrekucki
  * status:  reopened => new
  * stage:  Unreviewed => Accepted

Comment:

 I'll try to redeem myself ;)

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