Re: [Django] #12031: Make django.core.context_processors.auth lazy

[Django]

#12031: Make django.core.context_processors.auth lazy
+---
  Reporter:  Suor   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Suor):

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

Comment:

 it relates to #6552

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

[Django] #12031: Make django.core.context_processors.auth lazy

[Django]

#12031: Make django.core.context_processors.auth lazy
---+
 Reporter:  Suor   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 django.core.context_processors.auth breakes laziness of session and
 request.user.
 It also calls user.get_and_delete_messages() for all pages which is
 usually pointless when not in admin.

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

Re: [Django] #6552: django.core.context_processors.auth causes "Vary: Cookie" header no matter what

[Django]

#6552: django.core.context_processors.auth causes "Vary: Cookie" header no 
matter
what
-+--
  Reporter:  o...@iola.dk| Owner: 
Status:  new | Milestone: 
 Component:  Authentication  |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  1   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by Suor):

 * cc: s...@metadesign.ru (added)

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

Re: [Django] #6552: django.core.context_processors.auth causes "Vary: Cookie" header no matter what

[Django]

#6552: django.core.context_processors.auth causes "Vary: Cookie" header no 
matter
what
-+--
  Reporter:  o...@iola.dk| Owner: 
Status:  new | Milestone: 
 Component:  Authentication  |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  1   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by Suor):

 django.core.context_processors.auth should return lazy user and messages
 fields.
 It would almost solve this ticket

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

[Django] #12030: PositiveIntegerField in model form does not validate max value

[Django]

#12030: PositiveIntegerField in model form does not validate max value
+---
 Reporter:  p...@meebo-inc.com  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Forms   | Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Entering in a value of more than 4294967295 for a PositiveIntegerField in
 a model form causes an error to be thrown trying to insert the value into
 the database.  Ideally this would get validated by the model form.

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

Re: [Django] #12029: Error when running django tests with postgresql 8.3

[Django]

#12029: Error when running django tests with postgresql 8.3
+---
  Reporter:  msaelices  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Works fine for me, using Postgres 8.3.1, psycopg2 2.0.7, under OSX 10.5.

 Based on the error, I'm guessing this is a psycopg2 problem - if you can
 provide more details of your specific failing environment, feel free to
 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12024: error with limit_choices_to with complex queries (Q object) and raw_id_fields

[Django]

#12024: error with limit_choices_to with complex queries (Q object) and
raw_id_fields
---+
  Reporter:  anonymous | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:3 russellm]:
 I didn't realize it either until I went to point the django-user's query
 to the doc on `limit_choice_to`, and there it was, documented.  Not sure
 how this can be fixed, as I think the raw widget is trying to build a URL
 for the popup to select from the limited set of related objects. Not sure
 a Q object can be encoded into a URL query string for an admin filter
 lookup...but I'm also exhausted at the moment so I could be missing
 something obvious.

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

Re: [Django] #12024: error with limit_choices_to with complex queries (Q object) and raw_id_fields

[Django]

#12024: error with limit_choices_to with complex queries (Q object) and
raw_id_fields
---+
  Reporter:  anonymous | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 Replying to [comment:2 kmtracey]:
 > The code in `ForeignKeyRawIdWidget` is assuming that `limit_choices_to`
 will be a dict, or at least support `items()`, and that's not a valid
 assumption since `limit_choices_to` may also be a Q object.

 Huh - you learn something new every day. I wasn't aware that this usage of
 Q was documented (or even possible). In which case, yes, there is
 something unusual going on here.

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 I'd say my work is completed. Any comments welcome.

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by mrts):

  * needs_better_patch:  1 => 0
  * version:  1.0 => SVN
  * needs_tests:  1 => 0

Comment:

 Tried my best to create a clean representation of the intent:
 {{{
 yield mark_safe(u'<%s%s>%s' %
 (table_tag, row_class, url,
 (cl.is_popup
 and ' onclick='
 '"opener.dismissRelatedLookupPopup(window, %s,
 '
 "'%s\'); return false;"' %
 (result_id, result_url, result_name)
 or ''),
 conditional_escape(result_repr), table_tag))
 }}}

 Commit:
 http://github.com/mrts/django/commit/e95f27ad4b74eef3a9d4e9553e5cfb58f159c10a

 Tests pass, also tested to be working in a real site.

 Patch upcoming.

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

Re: [Django] #12024: error with limit_choices_to with complex queries (Q object) and raw_id_fields

[Django]

#12024: error with limit_choices_to with complex queries (Q object) and
raw_id_fields
---+
  Reporter:  anonymous | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Unless I'm missing something, this is a bug in Django, not a user error.
 A perfectly valid `limit_choices_to` specified as a Q object, that works
 fine with the seclect box interface, causes an exception if the field is
 included in `raw_id_fields`:

 {{{
 Environment:

 Request Method: GET
 Request URL: http://localhost:8000/admin/crossword/puzzles/14310/
 Django Version: 1.2 pre-alpha SVN-11616
 Python Version: 2.5.2
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.admin',
  'django.contrib.admindocs',
  'django.contrib.sites',
  'django.contrib.humanize',
  'xword.crossword']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.middleware.locale.LocaleMiddleware',
  'django.middleware.doc.XViewMiddleware')


 Template error:
 [snip irrelevant template context and rendering traceback]

 Exception Type: TemplateSyntaxError at /admin/crossword/puzzles/14310/
 Exception Value: Caught an exception while rendering: 'Q' object has no
 attribute 'items'

 Original Traceback (most recent call last):
   File "d:\u\kmt\django\trunk\django\template\debug.py", line 71, in
 render_node
 result = node.render(context)
   File "d:\u\kmt\django\trunk\django\template\debug.py", line 87, in
 render
 output = force_unicode(self.filter_expression.resolve(context))
   File "d:\u\kmt\django\trunk\django\utils\encoding.py", line 71, in
 force_unicode
 s = unicode(s)
   File "d:\u\kmt\django\trunk\django\forms\forms.py", line 356, in
 __unicode__
 return self.as_widget()
   File "d:\u\kmt\django\trunk\django\forms\forms.py", line 391, in
 as_widget
 return widget.render(name, data, attrs=attrs)
   File "d:\u\kmt\django\trunk\django\contrib\admin\widgets.py", line 113,
 in render
 params = self.url_parameters()
   File "d:\u\kmt\django\trunk\django\contrib\admin\widgets.py", line 145,
 in url_parameters
 params = self.base_url_parameters()
   File "d:\u\kmt\django\trunk\django\contrib\admin\widgets.py", line 134,
 in base_url_parameters
 for k, v in self.rel.limit_choices_to.items():
 AttributeError: 'Q' object has no attribute 'items'

 }}}

 The code in `ForeignKeyRawIdWidget` is assuming that `limit_choices_to`
 will be a dict, or at least support `items()`, and that's not a valid
 assumption since `limit_choices_to` may also be a Q object.

 If I am missing something please point it out, I'm just not seeing the
 user error here.

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by mrts):

 Tests pass, looks more or less OK to me.

 One thing that needs to be resolved is whether the object link should open
 in a pop-up. That would be more consistent, but would make the
 corresponding code horrible -- imagine embedding yet another `showPopup`
 into the `\'`-quoted part:
 {{{
 ' onclick="opener.dismissRelatedLookupPopup(window, %s, \'%s\'); return false;"'
 }}}

 I'll probably implement this nevertheless.

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

[Django] #12029: Error when running django tests with postgresql 8.3

[Django]

#12029: Error when running django tests with postgresql 8.3
---+
 Reporter:  msaelices  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I followed [wiki:RunningDjangoTests running Django tests wiki], but with
 {{{postgresql_psycopg2}}} as database backend. I've get an error on
 [11620] Django revision.

 The error was this:
 {{{
 Creating test database...
 Traceback (most recent call last):
   File "runtests.py", line 191, in 
 django_tests(int(options.verbosity), options.interactive, args)
   File "runtests.py", line 161, in django_tests
 failures = test_runner(test_labels, verbosity=verbosity,
 interactive=interactive, extra_tests=extra_tests)
   File "/usr/lib/python2.5/site-packages/django/test/simple.py", line 191,
 in run_tests
 connection.creation.create_test_db(verbosity, autoclobber=not
 interactive)
   File "/usr/lib/python2.5/site-packages/django/db/backends/creation.py",
 line 332, in create_test_db
 can_rollback = self._rollback_works()
   File "/usr/lib/python2.5/site-packages/django/db/backends/creation.py",
 line 393, in _rollback_works
 self.connection._rollback()
 TypeError: _new_rollback() takes exactly 1 argument (0 given)
 }}}

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

[Django] #12028: Generic Inline doesn't validate unique_together

[Django]

#12028: Generic Inline doesn't validate unique_together
--+
 Reporter:  diverman
  |   Owner:  nobody
   Status:  new 
  |   Milestone:
Component:  Contrib apps
  | Version:  SVN   
 Keywords:  content type generic inline unique validation formset admin 
modeladmin model  |   Stage:  Unreviewed
Has_patch:  0   
  |  
--+
 Hello, consider these models:
 {{{
 ### models.py
 class Tag(models.Model):
 tag = models.CharField(max_length=256)

 class TaggedItem(BaseModel):
 tag = models.ForeignKey('Tag')
 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField(db_index=True)
 content_object = generic.GenericForeignKey()

 class Meta:
 unique_together = (('content_type', 'object_id', 'tag'),)

 class Page(models.Model):
 text = models.TextField()

 ### admin.py
 class TaggedItemInline(generic.GenericTabularInline):
  model = TaggedItem

 class PageAdmin(admin.ModelAdmin):
 inlines = ( TaggedItemInline, )

 admin.site.register(Tag)
 admin.site.register(TaggedItem)
 admin.site.register(Page, PageAdmin)
 }}}

 When I edit Page in Admin and try to set non-unique values, it falls into
 IntegrityError. When I modify TaggedItem in Admin directly, validation of
 unique_together works fine.

 {{{
 Traceback:
 File "/usr/lib/python2.5/site-packages/django/core/handlers/base.py" in
 get_response
   92. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/usr/lib/python2.5/site-packages/django/contrib/admin/sites.py" in
 root
   490. return self.model_page(request, *url.split('/', 2))
 File "/usr/lib/python2.5/site-packages/django/views/decorators/cache.py"
 in _wrapped_view_func
   70. response = view_func(request, *args, **kwargs)
 File "/usr/lib/python2.5/site-packages/django/contrib/admin/sites.py" in
 model_page
   509. return admin_obj(request, rest_of_url)
 File "/usr/lib/python2.5/site-packages/django/contrib/admin/options.py" in
 __call__
   1098. return self.change_view(request, unquote(url))
 File "/usr/lib/python2.5/site-packages/django/db/transaction.py" in
 _commit_on_success
   240. res = func(*args, **kw)
 File "/usr/lib/python2.5/site-packages/django/contrib/admin/options.py" in
 change_view
   833. self.save_formset(request, form, formset,
 change=True)
 File "/usr/lib/python2.5/site-packages/django/contrib/admin/options.py" in
 save_formset
   563. formset.save()
 File "/usr/lib/python2.5/site-packages/django/forms/models.py" in save
   522. return self.save_existing_objects(commit) +
 self.save_new_objects(commit)
 File "/usr/lib/python2.5/site-packages/django/forms/models.py" in
 save_new_objects
   657. self.new_objects.append(self.save_new(form,
 commit=commit))
 File "/usr/lib/python2.5/site-
 packages/django/contrib/contenttypes/generic.py" in save_new
   335. return save_instance(form, new_obj, commit=commit)
 File "/usr/lib/python2.5/site-packages/django/forms/models.py" in
 save_instance
   78. instance.save()
 File "/usr/lib/python2.5/site-packages/django/db/models/base.py" in save
   410. self.save_base(force_insert=force_insert,
 force_update=force_update)
 File "/usr/lib/python2.5/site-packages/django/db/models/base.py" in
 save_base
   495. result = manager._insert(values,
 return_id=update_pk)
 File "/usr/lib/python2.5/site-packages/django/db/models/manager.py" in
 _insert
   177. return insert_query(self.model, values, **kwargs)
 File "/usr/lib/python2.5/site-packages/django/db/models/query.py" in
 insert_query
   1087. return query.execute_sql(return_id)
 File "/usr/lib/python2.5/site-packages/django/db/models/sql/subqueries.py"
 in execute_sql
   320. cursor = super(InsertQuery, self).execute_sql(None)
 File "/usr/lib/python2.5/site-packages/django/db/models/sql/query.py" in
 execute_sql
   2369. cursor.execute(sql, params)
 File "/usr/lib/python2.5/site-packages/django/db/backends/util.py" in
 execute
   19. return self.cursor.execute(sql, params)

 Exception Type: IntegrityError at /admin/web/page/1/
 Exception Value: duplicate key value violates unique constraint
 "tag_taggeditem_content_type_id_key"
 }}}

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

Re: [Django] #10777: AuthenticationForm.is_valid after validation should reset password field for security reason

[Django]

#10777: AuthenticationForm.is_valid after validation should reset password field
for security reason
-+--
  Reporter:  trebor74hr  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  security
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by SmileyChris):

 Hi kc9ddi,

 If you want to promote tickets, the django-dev google group is a better
 place to do 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-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10777: AuthenticationForm.is_valid after validation should reset password field for security reason

[Django]

#10777: AuthenticationForm.is_valid after validation should reset password field
for security reason
-+--
  Reporter:  trebor74hr  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  security
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by kc9ddi):

 Would strongly encourage adopting the suggested type of behavior.  Not
 only is it potentially more secure, but it seems to be the most common
 behavior in use for most login forms users encounter on the internet.

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

Re: [Django] #11993: ValueError: Cannot convert NaN to integer in regressiontests.defaultfilters.tests using Python 2.6.3

[Django]

#11993: ValueError: Cannot convert NaN to integer in
regressiontests.defaultfilters.tests using Python 2.6.3
+---
  Reporter:  kklimonda  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  fixed  |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by anonymous):

 Correction, fixed in r11619.

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

Re: [Django] #12020: Template tests fail if they take longer than 60 seconds

[Django]

#12020: Template tests fail if they take longer than 60 seconds
--+-
  Reporter:  jacob| Owner:  jacob
Status:  closed   | Milestone:  1.2  
 Component:  Template system  |   Version:  1.1  
Resolution:  invalid  |  Keywords:   
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by jacob):

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

Comment:

 On further inspection, this is actually not exactly the template tests'
 fault: turns out these tests only take this long when using the `file://`
 `CACHE_BACKEND`. When doing so, the file cache backend is responsible for
 over 90% of the time spent running the template tests. When using a real
 cache backend the template tests take just over a second, which means that
 this issue is mostly moot.

 So I'm marking this invalid.

 #11260 already is tracking the inefficiency of the file-based cache
 backend.

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

[Django] #12027: EmailField validation is incorrect

[Django]

#12027: EmailField validation is incorrect
---+
 Reporter:  Klas H |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Core framework | Version:  SVN   
 Keywords:  email, regular expression, validation  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 When the [http://www.djangoproject.com/weblog/2009/oct/09/security/ email
 field related denial-of-service attack] was patched the new code suddenly
 allowed email addresses to end with a '.' character. For example,
 according to the new regular expression {{{'t...@test.com.'}}} is a valid
 email address (please note the trailing period character).

 I attach a patch that fixes this.

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

[Django] #12026: widthratio rounding option/filter

[Django]

#12026: widthratio rounding option/filter
--+-
 Reporter:  openinformation   |   Owner:  
nobody
   Status:  new   |   Milestone:

Component:  Uncategorized | Version:  1.1   

 Keywords:  widthratio, feature request   |   Stage:  
Unreviewed
Has_patch:  0 |  
--+-
 The widthratio tag is great for displaying quick graphs and percentages.
 The only "problem" is that it rounds to 0 digits after the decimal point.
 That often adds up to percentages > 100%.

 It would be great if one could specify a filter that controls the number
 of digits behind the decimal point.

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

Re: [Django] #11701: [patch] DateInput widget: allow uggettext_lazy in format attr

[Django]

#11701: [patch] DateInput widget: allow uggettext_lazy in format attr
-+--
  Reporter:  carsten | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by hejsan):

 * cc: hr.bjarni+dja...@gmail.com (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

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

[Django] #12025: Show generic relation on deleted objects

[Django]

#12025: Show generic relation on deleted objects
--+-
 Reporter:  rui.coe...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Uncategorized | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Generic foreign key relations are deleted but not shown in confirmation
 page.

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

Re: [Django] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+--
  Reporter:  pixelcort   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by ruosteinen):

 * cc: to...@syneus.fi (added)

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

Re: [Django] #12022: Download instructions refer to wrong version of downloaded archive

[Django]

#12022: Download instructions refer to wrong version of downloaded archive
+---
  Reporter:  EvilDMP| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  fixed  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Fixed. Thanks for the report.

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

Re: [Django] #12024: error with limit_choices_to with complex queries (Q object) and raw_id_fields

[Django]

#12024: error with limit_choices_to with complex queries (Q object) and
raw_id_fields
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Trac isn't for solving end-user questions - it's for tracking bugs in
 Django itself. In this case, you have misunderstood what Q is for. If you
 want more explanation, follow up with a message on django-users.

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

Re: [Django] #12023: admin actions: link from current docs to 1.0 docs, is broken

[Django]

#12023: admin actions: link from current docs to 1.0 docs, is broken
---+
  Reporter:  danstad...@gmail.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Uncategorized |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Those links are automatically generated.  The page doesn't exist, admin
 actions are new in 1.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-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12024: error with limit_choices_to with complex queries (Q object) and raw_id_fields

[Django]

#12024: error with limit_choices_to with complex queries (Q object) and
raw_id_fields
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 hello

 I have a model.py like this :

 {{{
 class secondaryGroup(models.Model):
 id = models.AutoField(primary_key = True)
 idGroup = models.ForeignKey(Group,db_column = 'idGroup',verbose_name =
 'Groupe',limit_choices_to = Q(state='valid') | Q(state='modify'))
 idUser = models.ForeignKey(User,db_column = 'idUser',verbose_name =
 'Utilisateur',limit_choices_to = Q(state='valid') | Q(state='modify'))
 }}}
 and in admin.py :
 {{{
 class SecondaryGroupAdmin(admin.ModelAdmin):
 form = SecondaryGroupAdminForm
 list_display = ('idUser','idGroup')
 raw_id_fields = ('idUser','idGroup',)
 }}}

 and I obtain this error in Admin edit form :

 Caught an exception while rendering: 'Q' object has no attribute 'items'

 Thanks in advance.

 Bye.

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

[Django] #12023: admin actions: link from current docs to 1.0 docs, is broken

[Django]

#12023: admin actions: link from current docs to 1.0 docs, is broken
--+-
 Reporter:  danstad...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Uncategorized | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 clicked this
 http://docs.djangoproject.com/en/1.0/ref/contrib/admin/actions/

 from here:
 http://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/

 and got the nice "page not found" page.

 -dan

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

Re: [Django] #11402: exists() method on QuerySets

[Django]

#11402: exists() method on QuerySets
---+
  Reporter:  Alex  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Vlada Macek):

 On duplicate #12021 I proposed the name any() for this method. Submitting
 it again for consideration.

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

Re: [Django] #11402: exists() method on QuerySets

[Django]

#11402: exists() method on QuerySets
---+
  Reporter:  Alex  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: t.dja...@sandbox.cz (added)

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

Re: [Django] #12021: .any() method on QuerySet using a known trick

[Django]

#12021: .any() method on QuerySet using a known trick
---+
  Reporter:  Vlada Macek   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Duplicate of #11402

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

[Django] #12022: Download instructions refer to wrong version of downloaded archive

[Django]

#12022: Download instructions refer to wrong version of downloaded archive
---+
 Reporter:  EvilDMP|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The instructions at http://www.djangoproject.com/download/ say:

 {{{
 tar xzvf Django-1.1.tar.gz

 }}}

 but the file downloaded in the previous line is Django-1.1.1.tar.gz

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

Re: [Django] #2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql)

[Django]

#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
---+
  Reporter:  scan...@nominum.com   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: t.dja...@sandbox.cz (added)

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Changes (by guettli):

 * cc: h...@tbz-pariv.de (added)

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

Re: [Django] #12021: .any() method on QuerySet using a known trick

[Django]

#12021: .any() method on QuerySet using a known trick
---+
  Reporter:  Vlada Macek   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: t.dja...@sandbox.cz (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

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

[Django] #12021: .any() method on QuerySet using a known trick

[Django]

#12021: .any() method on QuerySet using a known trick
--+-
 Reporter:  Vlada Macek   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 While inspecting the Django code, I found this trick:
 {{{
 #!python
 # This cute trick with extra/values is the most efficient way to
 # tell if a particular query returns any results.
 if qs.extra(select={'a': 1}).values('a').order_by():
 }}}
 It apparently turns off the ordering as well as retrieving and parsing any
 real value from the db, resulting in something very cheap like:
 {{{
 #!sql
 SELECT (1) AS "a" FROM  WHERE 
 }}}

 Which is what we wanted to get the any/none info.

 I think many of us frequently need this, but build unnecessarily complex
 constructs, while this can easily make it to a new QuerySet method called,
 say, .any().

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

Re: [Django] #7923: Add links when using raw_id_fields in admin

[Django]

#7923: Add links when using raw_id_fields in admin
---+
  Reporter:  julianb   | Owner:  julianb
Status:  closed| Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:  duplicate |  Keywords:  admin raw_id_fields
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by guettli):

 * cc: h...@tbz-pariv.de (removed)
  * status:  assigned => closed
  * resolution:  => duplicate

Comment:

 See #7028

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