Re: [Django] #14766: ordering by a field that does not exists returns an empty QuerySet

[Django]

#14766: ordering by a field that does not exists returns an empty QuerySet
---+
  Reporter:  robhudson | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.2
   
Resolution:|  Keywords:  
sprintdec2010 order_by
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by Aramgutang):

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

Comment:

 I was able to replicate the issue with Python 2.7.1 (MacPorts build on
 Snow Leopard). Reopening until I (or someone else) run some tests with
 different Python versions to confirm.

-- 
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] #14997: Confusing wording on the note "Overriding Delete"

[Django]

#14997: Confusing wording on the note "Overriding Delete"
+---
  Reporter:  phunehehe  | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by phunehehe):

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

Comment:

 Sorry I forgot to include a link to the page with the problem, here it is
 http://docs.djangoproject.com/en/1.2/topics/db/models/#overriding-
 predefined-model-methods

-- 
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] #14997: Confusing wording on the note "Overriding Delete"

[Django]

#14997: Confusing wording on the note "Overriding Delete"
---+
 Reporter:  phunehehe  |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 To be exact, the problem is with the sentence[[BR]]
 To ensure customized delete logic gets executed, you can use pre_save
 and/or post_save signals.

 I think the correct version is[[BR]]
 To ensure customized delete logic gets executed, you can use
 '''pre_delete''' and/or '''post_delete''' signals.

-- 
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] #14991: SQL injection in quote_name()

[Django]

#14991: SQL injection in quote_name()
---+
  Reporter:  EvoTech   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:  invalid   |  Keywords:  sql 
injection
 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:

 First off, for future reference: if you want to report a security issue,
 PLEASE use our [http://docs.djangoproject.com/en/1.2/faq/help/#i-think-i
 -ve-found-a-security-problem-what-should-i-do security issue reporting
 procedure]. Reporting potential security issues into the wild is very poor
 form.

 Secondly, as far as I can make out from the information you've provided,
 this isn't a plausible injection attack.

 Yes, `quote_name` is weak, and easily exploited. Which would be a problem
 if it was used anywhere to sanitize user-provided input. Which it isn't.
 At least, not anywhere that I can find, providing you follow the advice of
 the documentation.

 order_by() only accepts existing columns (annotated with a very small
 number of allowed extra bits like '-' and '?') for sorting. You can't
 insert arbitrary content, even if you *were* using user-provided data to
 drive that clause -- which it itself a pretty unlikely set of
 circumstances. The error is hidden under some circumstances by #14766, but
 if you inspect the SQL log, or you attempt to print the underlying query,
 you'll see the error that is generated:
 {{{
 >>> print MyModel.objects.order_by('`column_name!`; DROP database
 `dbname!`').query
 FieldError: "Invalid order_by arguments: ['`column_name!`; DROP database
 `dbname!`']"
 }}}

 extra() is a slightly different beast, but as long as you use it right
 (that is to say, as documented), you're safe. If, for example, you allow
 user-provided input to be used in the "where=" argument, you can construct
 an injection attack:
 {{{
 MyModel.objects.extra(where=['"column_name!"="foo"; DROP database
 "dbname!"'])
 }}}
 ...but if you use params, the user-provided data is correctly escaped by
 the database cursor. Our docs tell you to do this, too. They could say it
 a little more emphatically, perhaps, but it is there in black and white,
 with an example. Given that extra() is one step away from raw SQL, there
 really isn't anything else we can do here. Raw SQL is, by definition,
 exposing the bare metal, so we rely on people using it the right way. If
 you hold a sword by the blade, you're going to cut your hand, no matter
 how many warnings and safety catches are on the scabbard.

 In summary: I (and several other members of the core team) can't find an
 in-principle attack here, or in any code related to what you describe. The
 examples you have provided are either incomplete or incorrect. Closing
 this ticket as invalid.

 If you think we have missed something, and you can present an actual in-
 principle or in-practice attack (including a complete example, not just
 vague handwaving at the order_by clause), we're happy to reopen this. But,
 repeating the first point -- if you even *think* you have found a security
 issue, *PLEASE* report it to secur...@djangoproject.com, not on Trac.

-- 
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] #14996: Incorrect persistent help_text for ModelMultipleChoiceField if widget is overridden in Modelform class Meta:

[Django]

#14996: Incorrect persistent help_text for ModelMultipleChoiceField if widget is
overridden in Modelform class Meta:
---+
 Reporter:  daryl  |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Forms  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 For example, I have the following:

 {{{
 class SomeAdminModelForm(forms.ModelForm):
 class Meta:
 widgets = {
 'm2m_field': forms.CheckboxSelectMultiple(),
 }
 }}}

 ... which alters the m2m field multiple select to a series of checkboxes.

 Which is fine, except the help_text is still appended with 'Hold down
 "Control", or "Command" on a Mac, to select more than one.'

 ... which is obviously not necessary in this context.

-- 
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] #14877: ModelFormSet.save() with a deleted form should work even if the model has already been deleted

[Django]

#14877: ModelFormSet.save() with a deleted form should work even if the model 
has
already been deleted
+---
  Reporter:  andornaut  | Owner:  nobody   
Status:  new| Milestone:   
 Component:  Forms  |   Version:  1.3-alpha
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14878: Issues in generic views (list)

[Django]

#14878: Issues in generic views (list)
+---
  Reporter:  diegueus9  | Owner:  nobody   
Status:  new| Milestone:  1.3  
 Component:  Generic views  |   Version:  1.3-alpha
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  1
Needs_better_patch:  1  |  
+---
Changes (by russellm):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14879: Aggregates (Min, Max) for CharField fails with Postgresql

[Django]

#14879: Aggregates (Min, Max) for CharField fails with Postgresql
---+
  Reporter:  wejaay| Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:|  Keywords:  aggregate, 
postgresql, charfield
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 Marking has-patch because there is a proposed fix, but it needs tests, and
 needs to be turned into a diff.

-- 
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] #14857: has_results cleanup

[Django]

#14857: has_results cleanup
+---
  Reporter:  wkornewald | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * status:  new => closed
  * resolution:  => wontfix
  * summary:  [patch] has_results cleanup => has_results cleanup

Comment:

 Sorry - not a duplicate -- pasted a comment into the wrong tab.

 However, I'm going to mark this wontfix. NoSQL support isn't something
 that needs to be addressed piecemeal. This isn't the only place that raw
 SQL leaks out of the compiler; these leaks need to be addressed as a
 whole, not  piecemeal. As I've told you *many* times Waldemar, NoSQL
 support is on my radar for 1.4, when we address merging Alex's query-
 refactor SoC branch.

-- 
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] #14856: Cleanup of ForeignKey.db_type

[Django]

#14856: Cleanup of ForeignKey.db_type
---+
  Reporter:  wkornewald| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * status:  new => closed
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  [patch] cleanup of ForeignKey.db_type => Cleanup of
  ForeignKey.db_type
  * milestone:  1.3 =>
  * needs_docs:  => 0
  * resolution:  => duplicate

Comment:

 Duplicate of #13774

-- 
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] #14857: [patch] has_results cleanup

[Django]

#14857: [patch] has_results cleanup
+---
  Reporter:  wkornewald | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Duplicate of #13774

-- 
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] #14845: Refactor backend connection-creation process

[Django]

#14845: Refactor backend connection-creation process
---+
  Reporter:  Xof   | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.3-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Absent of any code, it seems like a reasonable proposal.

-- 
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] #14832: Impossible to create inline objects if form validates but is unchanged

[Django]

#14832: Impossible to create inline objects if form validates but is unchanged
---+
  Reporter:  julien| Owner:  nobody   
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.2  
Resolution:|  Keywords:  sprintdec2010
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 This is a messy problem, and needs some UX love to work out the right
 solution.

-- 
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] #14814: Check for file binding in FieldFile.delete()

[Django]

#14814: Check for file binding in FieldFile.delete()
---+
  Reporter:  dimier| Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:  wontfix   |  Keywords:  field 
file, FieldFile
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I am in agreement with Luke and Alex. It isn't a good thing to be silently
 hiding an error check.

-- 
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] #14801: Support for string methods with lazy translations

[Django]

#14801: Support for string methods with lazy translations
---+
  Reporter:  bronger   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Internationalization  |   Version:  1.2   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I might be missing something here, but doesn't seem like something that is
 in Django's court. Django just uses GNU gettext for translations. There's
 a bunch of wrappers around the outside to enable and disable various
 translation contexts, but the core translation calls (gettext / _()) are
 proxied directly to gettext. lower/upper etc aren't features exposed by
 gettext, so they're not features exposed by Django, either.

 There's also the issue of what "Upper" means; in a raw python string,
 "foo".upper() -> "FOO", not "Foo". "foo".capitalize() -> "Foo" but full
 capitalization rules are locale specific, and aren't even implemented
 consistently for English.

 Marking wontfix, since this appears to be somewhere between an intractable
 problem and a problem that isn't Django's domain.

-- 
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] #14765: Unnecessary usage of NodeList in ForNode (template rendering)

[Django]

#14765: Unnecessary usage of NodeList in ForNode (template rendering)
--+-
  Reporter:  anonymous| Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:  ForNode render
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  1.3 =>

Comment:

 Yes, it should be marginally faster, but I doubt it will be a major
 performance improvement. However, every little bit helps. If you provide a
 patch, we'll apply it.

 The line numbers have gotten messed up since this was reported;
 permalinked line numbers are
 
[http://code.djangoproject.com/browser/django/trunk/django/template/defaulttags.py?rev=14656#L146
 146]
 
[http://code.djangoproject.com/browser/django/trunk/django/template/defaulttags.py?rev=14656#L178
 178] and
 
[http://code.djangoproject.com/browser/django/trunk/django/template/defaulttags.py?rev=14656#L187
 187] of defaulttags.py, and
 
[http://code.djangoproject.com/browser/django/trunk/django/template/__init__.py?rev=14595#L796
 796 of template/__init__.py], which is now in base.py.

-- 
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] #7018: Make ModelForm multiple inheritance possible

[Django]

#7018: Make ModelForm multiple inheritance possible
-+--
  Reporter:  bear330 | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by carbonXT):

 * cc: carbonXT (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] #14761: URL resolving / reversing design doesn't allow alternate specs

[Django]

#14761: URL resolving / reversing design doesn't allow alternate specs
-+--
  Reporter:  samuel337   | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  url resolve reverse
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  1  
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

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

Comment:

 Of course tests are required; you're adding a new piece of functionality.
 You need to test that the new functionality works, and will continue to
 work. As it stands, if this patch were applied, a future patch could go
 back to just calling normalize instead of calling get_possibilities, and
 the test suite would continue to run, but any custom URLPattern classes
 would be broken.

-- 
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] #14753: Accessing (Get)HttpRequest.raw_post_data in view results in exception during testing

[Django]

#14753: Accessing (Get)HttpRequest.raw_post_data in view results in exception
during testing
+---
  Reporter:  zimnyx | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This has been introduced as a result of the streaming HTTPRequest changes,
 so this is a regression.

-- 
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] #14722: @last_modified should ignore lack of etag method when USE_ETAGS is enabled

[Django]

#14722: @last_modified should ignore lack of etag method when USE_ETAGS is 
enabled
-+--
  Reporter:  lamby   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

  * needs_better_patch:  => 1
  * component:  Uncategorized => Core framework
  * needs_tests:  => 1
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14995: from django.views.generic import FormView

[Django]

#14995: from django.views.generic import FormView
---+
 Reporter:  carbonXT   |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Generic views  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 All class-based generic views that aren't documented to be mixins are made
 available via django.views.generic - save one.  !FormView.  I'd propose
 that it be made available as well.

 See attached patch.  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.

Re: [Django] #14882: copy as request param is incorrectly parsed

[Django]

#14882: copy as request param is incorrectly parsed
-+--
  Reporter:  pma_| Owner:  nobody
Status:  closed  | Milestone:
 Component:  Core framework  |   Version:  1.2   
Resolution:  worksforme  |  Keywords:  request, parse
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

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

Comment:

 I can't reproduce this

 {{{
 In [1]: from django.http import QueryDict, HttpRequest

 In [2]: q = QueryDict('invoice_no=FVS%2F0004%2F12%2F2010&a=1&b=2©=3')

 In [3]: q.items()
 Out[3]:
 [(u'a', u'1'),
  (u'copy', u'3'),
  (u'invoice_no', u'FVS/0004/12/2010'),
  (u'b', u'2')]

 In [4]: q
 Out[4]: 

 In [5]: q['b']
 Out[5]: u'2'

 In [6]: q['copy']
 Out[6]: u'3'

 In [7]:
 }}}

-- 
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] #14928: manage runserver does not allow host name as address

[Django]

#14928: manage runserver does not allow host name as address
+---
  Reporter:  Karmel Allison | Owner:  lrekucki 
Status:  new| Milestone:  1.3  
 Component:  django-admin.py runserver  |   Version:  1.3-alpha
Resolution: |  Keywords:   
 Stage:  Design decision needed | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by jezdez):

  * stage:  Accepted => Design decision needed

Comment:

 Not really a regression since it was not only undocumented but also
 clearly defined as a IP:port pair

-- 
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] #14928: manage runserver does not allow host name as address

[Django]

#14928: manage runserver does not allow host name as address
+---
  Reporter:  Karmel Allison | Owner:  lrekucki 
Status:  new| Milestone:  1.3  
 Component:  django-admin.py runserver  |   Version:  1.3-alpha
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by lrekucki):

  * owner:  nobody => lrekucki

-- 
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] #14993: Please make clear, that filter_horizontal pertains to m2m fields

[Django]

#14993: Please make clear, that filter_horizontal pertains to m2m fields
+---
  Reporter:  jammon | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.3-beta
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 I agree, the description of these two admin options needs some revamping.

-- 
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] #14844: i18n blocktrans tag pluralization feature limited by gettext constraints and unique local tag context

[Django]

#14844: i18n blocktrans tag pluralization feature limited by gettext constraints
and unique local tag context
---+
  Reporter:  ramiro| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14934: Decimal errors not localized to LT because of dictionary interpolation

[Django]

#14934: Decimal errors not localized to LT because of dictionary interpolation
---+
  Reporter:  davidlmontgomery  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * 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] #14913: Romanian translation, including E date format

[Django]

#14913: Romanian translation, including E date format
+---
  Reporter:  mihneasim  | Owner:  nobody   
Status:  new| Milestone:  1.3  
 Component:  Translations   |   Version:  SVN  
Resolution: |  Keywords:  translations romanian
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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] #14948: Broken routers in 1.2.4: type object 'ModelBase' has no attribute '_meta'

[Django]

#14948: Broken routers in 1.2.4: type object 'ModelBase' has no attribute 
'_meta'
---+
  Reporter:  shell_dweller | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  router, 
ManyToManyField
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: typesh...@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] #14994: Example in auth docs emits DeprecationWarning

[Django]

#14994: Example in auth docs emits DeprecationWarning
+---
  Reporter:  kmike  | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jezdez):

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

[Django] #14994: Example in auth docs emits DeprecationWarning

[Django]

#14994: Example in auth docs emits DeprecationWarning
---+
 Reporter:  kmike  |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The 'SettingsBackend' auth backend in example (
 http://docs.djangoproject.com/en/dev/topics/auth/#writing-an-
 authentication-backend ) should have 'supports_anonymous_user',
 'supports_inactive_user' and 'supports_object_permissions' defined.

-- 
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] #14976: Add is_html flag to contrib.messages

[Django]

#14976: Add is_html flag to contrib.messages
---+
  Reporter:  tedtieken | Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Contrib apps  |   Version:  1.2 
Resolution:|  Keywords:  safe, messages, html
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by tedtieken):

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

Comment:

 I coded up a patch, and it is passing previous tests on my system.

 Need to write new tests:
 - ensure it is accurately recovering legacy messages
 - test that the is_html tag is being set and retrieved as expected

 Passing legacy tests says to me that api backward compatibility has been
 achieved.

 Of note:  In base test_multiple_posts(): had to reduce the number of test
 messages per level from 10 to 9 (from 50 to 45 messages total.  10
 appeared to be pushing past the cookie size limit.)

 Also of note:  To get backward compatibility I had to write the api
 functions as

 {{{
 def debug(request, message, extra_tags='', fail_silently=False,
 is_html=False):
 instead of
 def debug(request, message, extra_tags='', is_html=False,
 fail_silently=False):
 }}}

 The later would be more intuitive [request], [message_content],
 [optional_message_content], [optional_message_content], [behavior_flag].

 Given that positional arguments are now non-intuitively ordered, the docs
 should probably encourage or at least show examples using keyword
 arguments:
 {{{
 messages.debug(request, "my message", extra_tags="markup this_way",
 is_html=True)
 }}}

-- 
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] #14993: Please make clear, that filter_horizontal pertains to m2m fields

[Django]

#14993: Please make clear, that filter_horizontal pertains to m2m fields
---+
 Reporter:  jammon |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.3-beta  
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In the documentation of ModelAdmin options please mention, that
 filter_horizontal (and filter_vertical) pertains to m2m fields on the edit
 page.
 (I got confused with that option until I realized, that list_filter was
 what I was looking for.)

-- 
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] #14960: Write tests for inclusion_tag

[Django]

#14960: Write tests for inclusion_tag
--+-
  Reporter:  julien   | Owner:  nobody   
Status:  new  | Milestone:   
 Component:  Template system  |   Version:  1.2  
Resolution:   |  Keywords:  easy-pickings
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by rasca):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Template system
  * needs_tests:  => 0
  * keywords:  => easy-pickings
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

Comment:

 Accepting the ticket and marking it as easy-picking

-- 
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] #14928: manage runserver does not allow host name as address

[Django]

#14928: manage runserver does not allow host name as address
+---
  Reporter:  Karmel Allison | Owner:  nobody   
Status:  new| Milestone:  1.3  
 Component:  django-admin.py runserver  |   Version:  1.3-alpha
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by rasca):

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

Comment:

 I can confirm the behavior. Accepting the ticket.

 This should be fixed before releasing 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.

Re: [Django] #14966: ValueError: Incorrect timezone setting: Amsterdam/Netherlands

[Django]

#14966: ValueError: Incorrect timezone setting: Amsterdam/Netherlands
--+-
  Reporter:  duikboot | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by rasca):

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

Comment:

 That's because there's no 'Amsterdam/Netherlands' time zone..

 Theres a brief explanation in the settings.py template, that tells you to
 check [http://en.wikipedia.org/wiki/List_of_tz_zones_by_name] for the
 timezones.

 You should be using 'Europe/Amsterdam'

-- 
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] #14955: URLField validation should use HEAD requet instead of GET

[Django]

#14955: URLField validation should use HEAD requet instead of GET
+---
  Reporter:  claudep| Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Core framework |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by rasca):

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

Comment:

 I've applied it cleanly, tested it in a demo app and run the tests OK.
 Marking it as RFC.

-- 
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] #14825: LocaleMiddleware should store language preferences if possible

[Django]

#14825: LocaleMiddleware should store language preferences if possible
-+--
  Reporter:  vzima   | Owner:  nobody
Status:  new | Milestone:
 Component:  Internationalization|   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by rasca):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 1
  * needs_docs:  => 1

Comment:

 Marking this as Design Decision Needed, cause despite I understand your
 use case when the session is flushed one might argue that the chosen
 language is sensitive data that needs to be flushed.

 Another solution to your problem would be to render the "logged out"
 template before flushing the session.

-- 
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] #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:  elbarto
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by elbarto):

  * has_patch:  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] #14642: save_as=True and generic inline in admin gives IndexError

[Django]

#14642: save_as=True and generic inline in admin gives IndexError
--+-
  Reporter:  si...@hostit.se  | Owner:  nobody
Status:  new  | Milestone:  1.3   
 Component:  Forms|   Version:  1.2   
Resolution:   |  Keywords:  save_as generic inline
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by brillgen):

 * cc: brillgen (added)

Comment:

 I have the same issue and I can confirm that the these two conditions will
 reproduce the bug in Django 1.0 as well as 1.2. Has any progress been made
 since?
 JohnRandom, do you need help with this to meet the 1.3 deadline?

-- 
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] #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:  elbarto
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by elbarto):

  * owner:  nobody => elbarto

-- 
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] #14817: ...models.sql.where.WhereNode.as_sql docstring is outdated

[Django]

#14817: ...models.sql.where.WhereNode.as_sql docstring is outdated
---+
  Reporter:  jonash| Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.2  
Resolution:|  Keywords:  docstring
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * 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] #14823: Unexpected behavior with core.serializers.register_serializer and unregister_serializer

[Django]

#14823: Unexpected behavior with core.serializers.register_serializer and
unregister_serializer
+---
  Reporter:  miker...@uw.edu| Owner:  nobody
Status:  new| Milestone:
 Component:  Serialization  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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] #14808: i18n is not safe.

[Django]

#14808: i18n is not safe.
--+-
  Reporter:  steveire | Owner:  nobody
Status:  new  | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * 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.

Re: [Django] #14768: es-MX locale, formats.py contribution

[Django]

#14768: es-MX  locale, formats.py contribution
-+--
  Reporter:  bautv...@gmail.com  | Owner:  nobody 
Status:  new | Milestone:  1.3
 Component:  Translations|   Version:  1.2
Resolution:  |  Keywords:  locale es es-MX
 Stage:  Accepted| Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14694: defer() doesn't work with reverse relations

[Django]

#14694: defer() doesn't work with reverse relations
---+
  Reporter:  sayane| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
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
  * needs_tests:  => 0
  * milestone:  1.3 =>
  * needs_docs:  => 0
  * resolution:  => invalid

Comment:

 Closing invalid because of the complete lack of helpful information in
 narrowing down this problem. You've provided a stack trace... with no
 example code that generated it. You've provided three sample queries...
 without any details of the models that are involved.

 Feel free to reopen if can provide a complete test case that would allow
 others to verify the bug without resorting to guesswork.

-- 
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] #14695: Field's `name` kwarg gets paved over

[Django]

#14695: Field's `name` kwarg gets paved over
---+
  Reporter:  erikrose  | 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:  1 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  0 => 1
  * 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.

Re: [Django] #14698: django.utils.module_loading.module_has_submodule yields false positives

[Django]

#14698: django.utils.module_loading.module_has_submodule yields false positives
+---
  Reporter:  lrekucki   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Core framework |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Ready for checkin
  * component:  Uncategorized => Core framework
  * 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.

Re: [Django] #14701: Meta attributes from abstract class

[Django]

#14701: Meta attributes from abstract class
---+
  Reporter:  sneakywombat  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  worksforme|  Keywords:  meta  
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

-- 
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] #14705: Model Field Order not influenced by MRO of superclasses

[Django]

#14705: Model Field Order not influenced by MRO of superclasses
+---
  Reporter:  vanschelven| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14688: BaseInlineFormSet does not support "auto_id"

[Django]

#14688: BaseInlineFormSet does not support "auto_id"
+---
  Reporter:  vicvicvic  | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Forms  |   Version:  SVN 
Resolution: |  Keywords:  formsets
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  1   
Needs_better_patch:  1  |  
+---
Changes (by russellm):

  * needs_better_patch:  => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 1
  * 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] #14677: tests.py cannot be split to package always

[Django]

#14677: tests.py cannot be split to package always
+---
  Reporter:  Ciantic| Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * 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] #14657: Extra select fields are merged into 'GROUP BY'

[Django]

#14657: Extra select fields are merged into 'GROUP BY'
---+
  Reporter:  Gregory   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.2
  
Resolution:  invalid   |  Keywords:  
extra_select,
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 qs.query.group_by (in fact, the entire qs.query structure) is an internal
 implementation detail. It isn't designed to be modified by end users. We
 don't (and won't) make any guarantees about how qs.query.group_by
 interacts with any other part of a query. We don't even guarantee that it
 will continue to exist.

-- 
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] #14673: MultipleHiddenInput unbound form

[Django]

#14673: MultipleHiddenInput unbound form
-+--
  Reporter:  humanfromearth  | Owner:  nobody   
  
Status:  closed  | Milestone:   
  
 Component:  Forms   |   Version:  1.2  
  
Resolution:  invalid |  Keywords:  MultipleHiddenInput 
widgets
 Stage:  Unreviewed  | Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  1
  
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

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

Comment:

 I don't think what you're describing makes sense. MultipleHiddenInput
 represents multiple values as a series of hidden inputs. If there aren't
 any currently selected values,then there aren't any hidden inputs. I'm not
 sure I see how it could be meaningfully interpreted any other way.

-- 
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] #14656: Atom1Feed should write atom:published element

[Django]

#14656: Atom1Feed should write atom:published element
-+--
  Reporter:  ttenc...@gmail.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  RSS framework   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * 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] #14651: ignored field index creation for fields with unique=True and db_index=True

[Django]

#14651: ignored field index creation for fields with unique=True and 
db_index=True
---+
  Reporter:  jordi | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I'm in agreement with Ramiro. A UNIQUE column *IS* indexed. You don't need
 to create an additional index. That's why it's optimized out of the table
 creation code.

-- 
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] #14649: .save_m2m() will override any Many-to-Many relationships created via signals/save method overloading.

[Django]

#14649: .save_m2m() will override any Many-to-Many relationships created via
signals/save method overloading.
+---
  Reporter:  chrischambers  | Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Forms  |   Version:  1.2   
   
Resolution:  wontfix|  Keywords:  save_m2m, signals, 
post_save, save_method
 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:  => wontfix
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I'm not sure I agree it's counterintuitive, because I can't see what
 *would* be intuitive in this case. The sequence of model saving and inline
 saving is inherently complicated, and I don't see how we could easily
 maintain the user-space code structure you have described *and* satisfy
 the basic saving requirements of m2m form elements.

 Even if it is counterintuitive, this ticket doesn't contain a proposal for
 what *would* be an intuitive interface.

 Closing wontfix; Looking at the example, #2750 would appear to be a better
 way to address this use case.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14648: Annotated date querysets fail if spatial backend is used

[Django]

#14648: Annotated date querysets fail if spatial backend is used
--+-
  Reporter:  codysoyland  | Owner:  jbronn
Status:  assigned | Milestone:  1.3   
 Component:  GIS  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  1|  
--+-
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14645: Exclude query with multiple conditions for the same multi-value relation not correct

[Django]

#14645: Exclude query with multiple conditions for the same multi-value relation
not correct
---+
  Reporter:  Ben Buchwald   | Owner:  
nobody
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  
1.1   
Resolution:|  Keywords:  
exclude manytomany
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * 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] #14609: __or__ method of queries does not return a correctly combined query.

[Django]

#14609: __or__ method of queries does not return a correctly combined query.
---+
  Reporter:  melinath  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Marking accepted; you could really help us out here by finding the minimum
 test case that reproduces this problem. That means the smallest set of
 models and queries that reproduces the problem.

-- 
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] #14518: Field.to_python not called on foreign key IDs

[Django]

#14518: Field.to_python not called on foreign key IDs
---+
  Reporter:  wolever   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * component:  Uncategorized => Database layer (models, ORM)
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Accepting, because it's clearly an inconsistency.

 However, I have a sneaking suspicion that this won't be easy to fix
 without breaking backwards compatibility. For historical reasons, it's
 possible to instantiate an object with string values, and those values
 aren't converted into field-appropriate values (integers, etc) until the
 object is saved to the database. This is an artefact of early-days Django
 form processing.

-- 
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] #14595: DATABASE DeprecationWarning includes new syntax.

[Django]

#14595: DATABASE DeprecationWarning includes new syntax.
---+
  Reporter:  CarlFK| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I disagree that this would be an improvement. The warning doesn't need to
 give the complete step-by-step instructions for fixing the problem --
 that's what release notes are for.

-- 
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] #14515: Can't pickle ValueQuerySet if query references fields, which aren't on the same model.

[Django]

#14515: Can't pickle ValueQuerySet if query references fields, which aren't on 
the
same model.
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted
  * milestone:  1.3 =>

Old description:

> This will work during pickle.dumps: http://paste.pocoo.org/show/278047/
> but will fail when I run loads.
>
>  The reason is that {{{ __getstate__ }}} of {{{ ValueQueryset }}} puts
> (in this case) {{{ ['name', 'deleted', 'id', 'id'] }}} into {{{
> obj_dict['search_fields'] }}}
> (http://code.djangoproject.com/browser/django/trunk/django/db/models/sql/query.py#L176);
> during loads it won't find Page.deleted etc… (full traceback:
> http://paste.pocoo.org/show/278050/)

New description:

 This will work during pickle.dumps:
 {{{
 pagelist = Page.objects.all().select_related('last_rev')\
 .order_by('name').values_list('name', 'last_rev__deleted',
 'last_rev__id', 'last_rev__attachment__id')
 # force a list, can't pickle ValueQueryset that way
 pagelist = list(pagelist)
 request_cache.set(key, pagelist, 1)
 }}}

 but will fail when I run loads.

 The reason is that {{{ __getstate__ }}} of {{{ ValueQueryset }}} puts (in
 this case) {{{ ['name', 'deleted', 'id', 'id'] }}} into {{{
 obj_dict['search_fields'] }}}
 
(http://code.djangoproject.com/browser/django/trunk/django/db/models/sql/query.py#L176);
 during loads it won't find Page.deleted etc… Full traceback:
 {{{
 Traceback (most recent call last):
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/application.py",
 line 52, in __call__
 return self.app(environ, start_response)
   File "/home/florian/.virtualenvs/inyoka/lib/python2.6/site-
 packages/Django-1.2.3-py2.6.egg/django/core/handlers/wsgi.py", line 241,
 in __call__
 response = self.get_response(request)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/application.py",
 line 88, in get_response
 return callback(request, *args, **kwargs)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/wiki/views.py",
 line 60, in show_page
 return PAGE_ACTIONS[action or 'show'](request, normalized_name)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/wiki/acl.py", line
 217, in oncall
 return f(request, name)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/utils/http.py",
 line 40, in proxy
 rv = f(request, *args, **kwargs)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/wiki/actions.py",
 line 99, in do_show
 return do_missing_page(request, name)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/utils/http.py",
 line 40, in proxy
 rv = f(request, *args, **kwargs)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/wiki/actions.py",
 line 199, in do_missing_page
 } for x in sorted(Page.objects.get_similar(name))],
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/wiki/models.py",
 line 346, in get_similar
 self._get_object_list(False) if not x[1]], n)]
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/wiki/models.py",
 line 200, in _get_object_list
 pagelist = request_cache.get(key)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/utils/cache.py",
 line 68, in get
 val = self.real_cache.get(key)
   File "/home/florian/.virtualenvs/inyoka/inyoka/inyoka/utils/cache.py",
 line 118, in get
 self.cache.get(key))
   File "/home/florian/.virtualenvs/inyoka/lib/python2.6/site-
 packages/Werkzeug-0.6.2-py2.6.egg/werkzeug/contrib/cache.py", line 229, in
 get
 return loads(value)
   File "/home/florian/.virtualenvs/inyoka/lib/python2.6/site-
 packages/Django-1.2.3-py2.6.egg/django/db/models/sql/query.py", line 200,
 in __setstate__
 for name in obj_dict['select_fields']
   File "/home/florian/.virtualenvs/inyoka/lib/python2.6/site-
 packages/Django-1.2.3-py2.6.egg/django/db/models/options.py", line 273, in
 get_field
 raise FieldDoesNotExist('%s has no field named %r' %
 (self.object_name, name))
 FieldDoesNotExist: Page has no field named 'deleted'
 }}}

Comment:

 Removed references to a pastebin. Trac provides perfectly adequate source
 code quoting tools, and has no risk of expiring, getting deleted etc.

-- 
Ticket URL: 
Django 
The Web framework for perfectio

Re: [Django] #14643: Readonly fields in GeoDjango admins

[Django]

#14643: Readonly fields in GeoDjango admins
-+--
  Reporter:  k...@gv.pl  | Owner:  nobody
Status:  new | Milestone:
 Component:  GIS |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Accepted

Comment:

 Seems reasonable to me.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14601: ValuesQuerySet join types not being promoted

[Django]

#14601: ValuesQuerySet join types not being promoted
---+
  Reporter:  ryanbutterfield   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
ValuesQuerySet promote_alias
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 Tests need to be updated to be unittests. Preferably, they should also be
 integrated into an existing test app, rather than starting a whole new
 test app. The regressiontest/queries test app would seem appropriate.

-- 
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] #14511: exclude() generates wrong query for ManyToManyField with a 'through' relationship

[Django]

#14511: exclude() generates wrong query for ManyToManyField with a 'through'
relationship
---+
  Reporter:  gsakkis   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * 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.

Re: [Django] #8391: slugify template filter poorly encodes non-English strings

[Django]

#8391: slugify template filter poorly encodes non-English strings
-+--
  Reporter:  bjornkri| Owner:  nobody
Status:  reopened| Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by RaceCondition):

 * cc: eallik+dja...@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] #14992: Template recursion

[Django]

#14992: Template recursion
--+-
  Reporter:  IsakovAN | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  duplicate|  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by lrekucki):

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

Comment:

 Duplicate of #3544.

-- 
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] #14766: ordering by a field that does not exists returns an empty QuerySet

[Django]

#14766: ordering by a field that does not exists returns an empty QuerySet
---+
  Reporter:  robhudson | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.2
   
Resolution:  wontfix   |  Keywords:  
sprintdec2010 order_by
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 The problem here is being caused by Python itself. For a couple of
 releases of Python 2.6, http://bugs.python.org/issue1242657 meant that
 exceptions raised during iteration were transparently swallowed by the
 iteration process. The field error *is* being raised; but the fact that
 you're iterating over the results means that the exception is eaten,
 resulting in an empty result set.

 If you're on a Mac with a default Snow Leopard Python install, you have
 Python 2.6.1, which is affected. If you have an up to date Python install
 (2.6.5 at time of writing), the problem has been fixed. I *think* it was
 fixed in Python 2.6.2, but I haven't got an install handy to check.

 Since this appears to be due to a bug in Python that has been addressed,
 and it's a non-trivial thing to work around, I'm going to mark this
 wontfix. If you are affected by this, the solution is to upgrade to Python
 2.6.5+.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14992: Template recursion

[Django]

#14992: Template recursion
-+--
 Reporter:  IsakovAN |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  SVN   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I'm trying to implement recursion of the template:

 test.html:
 {% if some.condition %}
 Some stuff
 {% include test.html with x=... %}

 {% endif %}

 Almost all works fine but...
 "maximum recursion depth exceeded while calling a Python object"

 It seems that "include" have been parsed irrespective of "if" condition. I
 think this shoud be fixed in because of:
 1. Performance
 2. Recursion

-- 
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] r15116 - django/branches/releases/1.2.X/docs/howto/deployment

[noreply]

Author: timo
Date: 2010-12-30 07:30:37 -0600 (Thu, 30 Dec 2010)
New Revision: 15116

Modified:
   django/branches/releases/1.2.X/docs/howto/deployment/modwsgi.txt
Log:
[1.2.X] Fixed #13912 - Fixed AliasMatch regex in modwsgi docs. Thanks 
SmileyChris for the report.

Backport of r15115 from trunk.

Modified: django/branches/releases/1.2.X/docs/howto/deployment/modwsgi.txt
===
--- django/branches/releases/1.2.X/docs/howto/deployment/modwsgi.txt
2010-12-30 13:29:57 UTC (rev 15115)
+++ django/branches/releases/1.2.X/docs/howto/deployment/modwsgi.txt
2010-12-30 13:30:37 UTC (rev 15116)
@@ -81,7 +81,7 @@
 Alias /robots.txt /usr/local/wsgi/static/robots.txt
 Alias /favicon.ico /usr/local/wsgi/static/favicon.ico
 
-AliasMatch /([^/]*\.css) /usr/local/wsgi/static/styles/$1
+AliasMatch ^/([^/]*\.css) /usr/local/wsgi/static/styles/$1
 
 Alias /media/ /usr/local/wsgi/static/media/
 

-- 
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] r15115 - django/trunk/docs/howto/deployment

[noreply]

Author: timo
Date: 2010-12-30 07:29:57 -0600 (Thu, 30 Dec 2010)
New Revision: 15115

Modified:
   django/trunk/docs/howto/deployment/modwsgi.txt
Log:
Fixed #13912 - Fixed AliasMatch regex in modwsgi docs. Thanks SmileyChris for 
the report.

Modified: django/trunk/docs/howto/deployment/modwsgi.txt
===
--- django/trunk/docs/howto/deployment/modwsgi.txt  2010-12-30 10:55:35 UTC 
(rev 15114)
+++ django/trunk/docs/howto/deployment/modwsgi.txt  2010-12-30 13:29:57 UTC 
(rev 15115)
@@ -83,7 +83,7 @@
 Alias /robots.txt /usr/local/wsgi/static/robots.txt
 Alias /favicon.ico /usr/local/wsgi/static/favicon.ico
 
-AliasMatch /([^/]*\.css) /usr/local/wsgi/static/styles/$1
+AliasMatch ^/([^/]*\.css) /usr/local/wsgi/static/styles/$1
 
 Alias /media/ /usr/local/wsgi/static/media/
 

-- 
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] #11383: Admin action 'Delete selected' check only global model delete permission

[Django]

#11383: Admin action 'Delete selected' check only global model delete permission
---+
  Reporter:  krej...@i3.cz | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  delete permission 
admin
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: ianmle...@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.

[Changeset] r15114 - django/trunk

[noreply]

Author: jezdez
Date: 2010-12-30 04:55:35 -0600 (Thu, 30 Dec 2010)
New Revision: 15114

Modified:
   django/trunk/MANIFEST.in
Log:
Fixed #14990 -- Added sitemaps tests templates to manifest template.

Modified: django/trunk/MANIFEST.in
===
--- django/trunk/MANIFEST.in2010-12-29 21:50:40 UTC (rev 15113)
+++ django/trunk/MANIFEST.in2010-12-30 10:55:35 UTC (rev 15114)
@@ -27,3 +27,4 @@
 recursive-include django/contrib/gis/tests/geoapp/fixtures *
 recursive-include django/contrib/gis/tests/geogapp/fixtures *
 recursive-include django/contrib/sitemaps/templates *
+recursive-include django/contrib/sitemaps/tests/templates *

-- 
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] #14991: SQL injection in quote_name()

[Django]

#14991: SQL injection in quote_name()
--+-
 Reporter:  EvoTech   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:
 Keywords:  sql injection |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 {{{
 183 def quote_name(self, name):
 184 if name.startswith("`") and name.endswith("`"):
 185 return name # Quoting once is enough.
 186 return "`%s`" % name
 }}}

 
http://code.djangoproject.com/browser/django/trunk/django/db/backends/mysql/base.py#L183

 name = '!`column_name!`; DROP database !`dbname!`' # take from request for
 sort table. Insert value to extra() or order_by()[[BR]]

 sql='SELECT * FROM... ORDER BY !`column_name!`; DROP database !`dbname!`'

-- 
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] #14990: Custom sitemap unittests failing for contrib.sitemaps in 1.3 Beta 1

[Django]

#14990: Custom sitemap unittests failing for contrib.sitemaps in 1.3 Beta 1
---+
  Reporter:  eKIK  | Owner:  nobody  
Status:  new   | Milestone:  1.3 
 Component:  Contrib apps  |   Version:  1.3-beta
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * version:  => 1.3-beta
  * 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] #10078: Document use of locales in management commands

[Django]

#10078: Document use of locales in management commands
+---
  Reporter:  gregoire   | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Documentation  |   Version:  SVN   
 
Resolution: |  Keywords:  LANCGUAGE_CODE 
management basecommand en-us
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by jezdez):

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