Re: [Django] #15712: authentication switching mid-session

[Django]

#15712: authentication switching mid-session
-+--
   Reporter:  ccurvey|Owner:  nobody
 Status:  closed |Milestone:
  Component:  Uncategorized  |  Version:  1.2
 Resolution:  needsinfo  | Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by russellm):

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


Comment:

 I'm going to mark this as closed:needsinfo, because this isn't an
 actionable task -- yet.

 Trac isn't the place for diagnosing problems; it's the place to log
 clearly identifiable issues that can be resolved. At the moment, we don't
 even know if it is your code or Django that is the problem (for example,
 some sort of problem with your usage of caching might be the root cause).

 So -- start a discussion on django-users and try to narrow down the
 problem; if the result of that discussion is a clear bug in Django, feel
 free to reopen this ticket.

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

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

[Django] #15715: Add a non-trivial decorator example to class-based views docs

[Django]

#15715: Add a non-trivial decorator example to class-based views docs
---+---
 Reporter:  toofishes  | Owner:  nobody
   Status:  new| Milestone:
Component:  Documentation  |   Version:  1.3
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  1  |
---+---
 To save someone the hassle I just had trying to go beyond the all-too-
 simple @login_required example. This seemed to work for me at least, so I
 hope it is correct:


 {{{
 (r'^delete/(?P\d+)/$',
 permission_required('main.delete_todolist')(DeleteTodolist.as_view())),

 }}}

 Attached a very simple suggestion for the docs, feel free to redo it if it
 is not in the style but I tried to look at other relevant examples.

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

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

[Django] #15714: Inconsistent capitalization of name_local in django.conf.locale.LANG_INFO

[Django]

#15714: Inconsistent capitalization of name_local in 
django.conf.locale.LANG_INFO
--+---
 Reporter:  claudep   | Owner:  nobody
   Status:  new   | Milestone:
Component:  Internationalization  |   Version:  1.3
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  0 |
--+---
 I think that name_local in LANG_INFO should be either globally capitalized
 or not (in languages where that makes sense).

 Currently, there is "Français" and "español", by instance.

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

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

Re: [Django] #15713: Adding new polish localflavor field PLNationalIDCardNumberField

[Django]

#15713: Adding new polish localflavor field PLNationalIDCardNumberField
---+-
   Reporter:  xtrqt|Owner:  xtrqt
 Status:  new  |Milestone:
  Component:  contrib.localflavor  |  Version:  SVN
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by lrekucki):

 * stage:  Ready for checkin => Accepted


Comment:

 You shouldn't mark your own patches 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15713: Adding new polish localflavor field PLNationalIDCardNumberField

[Django]

#15713: Adding new polish localflavor field PLNationalIDCardNumberField
---+-
   Reporter:  xtrqt|Owner:  xtrqt
 Status:  new  |Milestone:
  Component:  contrib.localflavor  |  Version:  SVN
 Resolution:   | Keywords:
   Triage Stage:  Ready for checkin|Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by xtrqt):

 * owner:  nobody => xtrqt
 * 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15713: Adding new polish localflavor field PLNationalIDCardNumberField

[Django]

#15713: Adding new polish localflavor field PLNationalIDCardNumberField
-+---
 Reporter:  xtrqt| Owner:  nobody
   Status:  new  | Milestone:
Component:  contrib.localflavor  |   Version:  SVN
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  1|
-+---
 I had to write that for one project. Since this number is quite important
 with ensuring peoples identity, I believe we can put it into polish
 localflavor. Patch with documentation and tests is attached.

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

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

[Django] #15712: authentication switching mid-session

[Django]

#15712: authentication switching mid-session
---+---
 Reporter:  ccurvey| Owner:  nobody
   Status:  new| Milestone:
Component:  Uncategorized  |   Version:  1.2
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+---
 When my Django system is under heavy load (system CPU > 90%), I start
 getting complaints to users that their authentication changes in the
 middle of a session.  For example:

 1) Bob logs in to the site.  The site says "Hello Bob" at the top of each
 page.

 2) Bob uses the site for a while without incident

 3) Bob notices that the top of the page now says "Hello Steve".

 The problem is intermittent, and I can't duplicate it (but I have seen it
 with my own eyes).  I'm running Django 1.2.5 on Windows, with
 SessionMiddleware installed.  I have django.contrib.sessions in my
 INSTALLED_APPS, and I believe that I'm using database-backed sessions,
 with a MySQL database.

 The only "odd" thing that I'm doing is that I have four instances of
 Apache running, with my Django app running via mod_wsgi in each of them.
 There is another apache server in front that does load-balancing, so
 multiple requests from a single user may get routed to different apache
 instances (which is what I want, to get maximum throughput on Ajax calls).
 But I thought that having the sessions be database-backed would deal with
 this (multiple session requests can hit the database at the same time).

 Any thoughts?  I'm sorry this is such a lousy, unrepeatable 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15711: Abstract model managers should return subclass instances

[Django]

#15711: Abstract model managers should return subclass instances
-+-
   Reporter:  jdunck |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database layer |  Version:  1.2
  (models, ORM)  | Triage Stage:
   Keywords:  pony   |  Unreviewed
  Has patch:  0  |  Needs documentation:  0
Needs tests:  0  |  Patch needs improvement:  0
-+-
 Suppose a base:

 {{{
 class Document(Model):
title = CharField()

class Meta:
  abstract = True

 class Presentation(Document):
num_kitten_pictures = IntegerField()

 class Spreadsheet(Document):
 num_pie_charts = IntegerField()
 }}}

 It would be useful if Documents.objects.filter(title='x') returned
 instances of both Presentation and Spreadsheet whose title was 'x'.

 I'd expect support only for base-class fields.  This should be safe, since
 inheritance should follow an is-a relationship.

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

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

Re: [Django] #15708: Regression in Forms: KeyError if trying to access nonvalid input from required field

[Django]

#15708: Regression in Forms: KeyError if trying to access nonvalid input from
required field
--+--
   Reporter:  jonescb |Owner:  nobody
 Status:  closed  |Milestone:
  Component:  Forms   |  Version:  1.3
 Resolution:  needsinfo   | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--

Comment (by kmtracey):

 Note it's quite easy to avoid a !KeyError in the case of a required field
 that has not been specified:
 http://docs.python.org/library/stdtypes.html#dict.get You do not have to
 riddle your code which try/excepts to handle these cases gracefully in
 your custom clean method.

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

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

Re: [Django] #15709: Duplicated group_by condition

[Django]

#15709: Duplicated group_by condition
-+-
   Reporter:  ziangsong  |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database   |  Version:  1.3
  layer (models, ORM)| Keywords:  group_by, annotate
 Resolution: |Has patch:  1
   Triage Stage:  Ready for  |  Needs tests:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ziangsong):

 * 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15708: Regression in Forms: KeyError if trying to access nonvalid input from required field

[Django]

#15708: Regression in Forms: KeyError if trying to access nonvalid input from
required field
--+--
   Reporter:  jonescb |Owner:  nobody
 Status:  closed  |Milestone:
  Component:  Forms   |  Version:  1.3
 Resolution:  needsinfo   | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--

Comment (by jonescb):

 Ok, you're right 1.2 behaves the same way, so it's not a regression, but I
 think it could be handled better.  At least for CharFields and fields that
 derive CharField, cleaned_data could default to an empty string.  Other
 fields could possibly default to other values.  AFAIK, a blank string
 won't raise an exception during any string processing just because it's
 blank.  If the field is set to required, Django should set the form as
 being invalid so that a custom clean() written by an amateur like myself
 that wasn't expecting an empty field won't end up with a 500 error and it
 can be handled more gracefully.  Custom clean()'s might have to call
 super.clean() to do this I believe.

 Django already does this for required=False.  Blank CharFields yield an
 empty string in cleaned_data.
 To me it seems like a strange behavior for Django to give a nice error
 message for invalid fields, but if your clean() method has to process a
 field, it will crash unless you catch the exception.  Maybe I'm just
 rationalizing my mistake in not catching the exception, but I think it
 would be more consistent and make life easier for developers if Django set
 a blank or default value.

 I'll leave the ticket as closed because I doubt anyone would agree with
 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #25: Filtering interface on ForeignKey boxes

[Django]

#25: Filtering interface on ForeignKey  boxes
-+
   Reporter:  adrian |Owner:  sebleier
 Status:  new|Milestone:
  Component:  contrib.admin  |  Version:  SVN
 Resolution: | Keywords:  feature
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+
Changes (by sebleier):

 * status:  assigned => new
 * owner:  cpharmston => sebleier


Comment:

 I added tests and documentation to the patch.  One thing to note is that
 the previous patch required a fk_filter attribute on the ModelAdmin class
 to specify which foreignkey fields are rendered using the new filter
 interface.  In this patch, you simply specify which foreignkey field needs
 the filtering interface in the ModelAdmin filter_vertical list.

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

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

Re: [Django] #15709: Duplicated group_by condition

[Django]

#15709: Duplicated group_by condition
-+-
   Reporter:  ziangsong  |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database   |  Version:  1.3
  layer (models, ORM)| Keywords:  group_by, annotate
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by mk):

 Could you promote this issue to "Ready for checkin" if it fixes the
 problem for you? 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15709: Duplicated group_by condition

[Django]

#15709: Duplicated group_by condition
-+-
   Reporter:  ziangsong  |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database   |  Version:  1.3
  layer (models, ORM)| Keywords:  group_by, annotate
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by ziangsong):

 Thank you! I really appreciate it!

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

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

Re: [Django] #15689: test --failfast doesn't stop on errors in _pre_setup()

[Django]

#15689: test --failfast doesn't stop on errors in _pre_setup()
-+--
   Reporter:  slinkp@…   |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Testing framework  |  Version:  1.2
 Resolution:  fixed  | Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by slinkp):

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


Comment:

 Re-closing. I just tested upgrading to Django 1.3 and it has apparently
 fixed this problem already.

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

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

Re: [Django] #15689: test --failfast doesn't stop on errors in _pre_setup() (was: test --failfast doesn't stop on errors)

[Django]

#15689: test --failfast doesn't stop on errors in _pre_setup()
-+--
   Reporter:  slinkp@…   |Owner:  nobody
 Status:  reopened   |Milestone:
  Component:  Testing framework  |  Version:  1.2
 Resolution: | Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by slinkp):

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


Comment:

 Sorry, I mis-reported. I've updated the title, though Trac won't let me
 edit the description (maybe I wasn't signed in before).

 The real problem was that if TestCase._pre_setup() raises an exception,
 all tests are still run but reported as errors.

 I did notice that exceptions raised by TestCase.setUp() *will* exit on the
 first error with --failfast.
 So far, _pre_setup() is the only place I've observed this problem with
 failfast.

 FWIW, the way that I discovered this was by having a multi-database
 configuration that worked on 1.2.3 but apparently wasn't compatible with
 the introduction of the TEST_DEPENDENCIES setting in 1.2.4.

 Demonstration: Drop this in your app's tests.py and run tests:

 {{{
 class SimpleTest(TestCase):


 def _pre_setup(self):
 super(SimpleTest, self)._pre_setup()
 raise Exception("oh nooo")

 def test_aaa_ok(self):
 pass

 def test_bbb_ok(self):
 pass

 def test_ccc_nameerror(self):
 return foo

 def test_ddd_zerodivisionerror(self):
 return 3 / 0

 def test_eee_failing(self):
 self.assertEqual(1, 2)

 def test_zzz_ok(self):
 pass

 }}}

 I see 6 errors reported, even with --failfast:

 {{{
 $ django-admin.py test --failfast testapp

 ... snip ...

 Ran 0 tests in 0.001s

 FAILED (errors=6)
 Destroying test database 'default'...

 }}}

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

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

Re: [Django] #12771: Humanize with natural time

[Django]

#12771: Humanize with natural time
-+
   Reporter:  phinpho|Owner:  djansoft
 Status:  new|Milestone:
  Component:  Template system|  Version:
 Resolution: | Keywords:
   Triage Stage:  Ready for checkin  |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+
Changes (by xtrqt):

 * needs_docs:  1 => 0
 * 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15624: aggregate produces incorrect sql statement

[Django]

#15624: aggregate produces incorrect sql statement
-+-
   Reporter:  zeroos |Owner:  marekw2143
  <232002@…> |Milestone:
 Status:  assigned   |  Version:  SVN
  Component:  ORM| Keywords:  aggregate sql syntax
  aggregation|  error
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by mk):

 * stage:  Unreviewed => Accepted


Comment:

 Attached patch with a unit test confirming this issue.

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

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

Re: [Django] #15709: Duplicated group_by condition

[Django]

#15709: Duplicated group_by condition
-+-
   Reporter:  ziangsong  |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database   |  Version:  1.3
  layer (models, ORM)| Keywords:  group_by, annotate
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by mk):

 * has_patch:  0 => 1
 * milestone:  1.3 =>


Comment:

 The attached patch fixes this problem (hopefully) by not letting group_by
 clause duplicates through. I don't think duplicated entries in GROUP BY
 ever make sense.

 Test included.

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

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

Re: [Django] #15709: Duplicated group_by condition

[Django]

#15709: Duplicated group_by condition
-+-
   Reporter:  ziangsong  |Owner:  nobody
 Status:  new|Milestone:  1.3
  Component:  Database   |  Version:  1.3
  layer (models, ORM)| Keywords:  group_by, annotate
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by mk):

 * stage:  Unreviewed => Accepted


Comment:

 Some quick testing shows that the issue even exists when the Count('id')
 is left away:

 {{{
 In [4]:
 Page.objects.values('parent').annotate(m_d=Max('title')).order_by()
 Out[4]: [{'parent': None, 'm_d': u'Test page 2'}, {'parent': 1, 'm_d':
 u'Maybe a subpage'}, {'parent': 2, 'm_d': u'Test page 2 wants a subpage
 too'}]

 In [5]: connection.queries
 Out[5]:
 [{'sql': u'SELECT "page_page"."parent_id", MAX("page_page"."title") AS
 "m_d" FROM "page_page" GROUP BY "page_page"."parent_id",
 "page_page"."parent_id" LIMIT 21',
   'time': '0.001'}]
 }}}

 Inside django.db.models.sql.compiler.SQLCompiler.get_grouping, both
 group_by and self.query.select contain ('page_page', 'parent_id') which
 causes the duplicated GROUP BY clause.

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

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

Re: [Django] #14671: Allow overriding of ModelChoiceField.choices

[Django]

#14671: Allow overriding of ModelChoiceField.choices
+-
   Reporter:  simon29   |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Forms |  Version:  SVN
 Resolution:| Keywords:  sprintdec2010
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  1 |  Needs tests:  1
Patch needs improvement:  1 |
+-
Changes (by mk):

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


Comment:

 The patch needs documentation, tests and reasons why BaseModelFormSet and
 BaseInlineFormset should be added to __all__.

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

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

[Changeset] r15943 - in django/branches/releases/1.3.X/docs/topics: db http

[noreply]

Author: timo
Date: 2011-03-29 03:25:18 -0700 (Tue, 29 Mar 2011)
New Revision: 15943

Modified:
   django/branches/releases/1.3.X/docs/topics/db/multi-db.txt
   django/branches/releases/1.3.X/docs/topics/http/shortcuts.txt
Log:
[1.2.X] Fixed #15710 - removed "that that" typos.

Backport of r15942 from trunk.

Modified: django/branches/releases/1.3.X/docs/topics/db/multi-db.txt
===
--- django/branches/releases/1.3.X/docs/topics/db/multi-db.txt  2011-03-29 
10:24:42 UTC (rev 15942)
+++ django/branches/releases/1.3.X/docs/topics/db/multi-db.txt  2011-03-29 
10:25:18 UTC (rev 15943)
@@ -454,7 +454,7 @@
 
 Django's admin doesn't have any explicit support for multiple
 databases. If you want to provide an admin interface for a model on a
-database other than that that specified by your router chain, you'll
+database other than that specified by your router chain, you'll
 need to write custom :class:`~django.contrib.admin.ModelAdmin` classes
 that will direct the admin to use a specific database for content.
 

Modified: django/branches/releases/1.3.X/docs/topics/http/shortcuts.txt
===
--- django/branches/releases/1.3.X/docs/topics/http/shortcuts.txt   
2011-03-29 10:24:42 UTC (rev 15942)
+++ django/branches/releases/1.3.X/docs/topics/http/shortcuts.txt   
2011-03-29 10:25:18 UTC (rev 15943)
@@ -24,7 +24,7 @@
 
:func:`render()` is the same as a call to
:func:`render_to_response()` with a `context_instance` argument that
-   that forces the use of a :class:`~django.template.RequestContext`.
+   forces the use of a :class:`~django.template.RequestContext`.
 
 Required arguments
 --

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

[Changeset] r15942 - in django/trunk/docs/topics: db http

[noreply]

Author: timo
Date: 2011-03-29 03:24:42 -0700 (Tue, 29 Mar 2011)
New Revision: 15942

Modified:
   django/trunk/docs/topics/db/multi-db.txt
   django/trunk/docs/topics/http/shortcuts.txt
Log:
Fixed #15710 - removed "that that" typos.

Modified: django/trunk/docs/topics/db/multi-db.txt
===
--- django/trunk/docs/topics/db/multi-db.txt2011-03-28 22:19:14 UTC (rev 
15941)
+++ django/trunk/docs/topics/db/multi-db.txt2011-03-29 10:24:42 UTC (rev 
15942)
@@ -454,7 +454,7 @@
 
 Django's admin doesn't have any explicit support for multiple
 databases. If you want to provide an admin interface for a model on a
-database other than that that specified by your router chain, you'll
+database other than that specified by your router chain, you'll
 need to write custom :class:`~django.contrib.admin.ModelAdmin` classes
 that will direct the admin to use a specific database for content.
 

Modified: django/trunk/docs/topics/http/shortcuts.txt
===
--- django/trunk/docs/topics/http/shortcuts.txt 2011-03-28 22:19:14 UTC (rev 
15941)
+++ django/trunk/docs/topics/http/shortcuts.txt 2011-03-29 10:24:42 UTC (rev 
15942)
@@ -24,7 +24,7 @@
 
:func:`render()` is the same as a call to
:func:`render_to_response()` with a `context_instance` argument that
-   that forces the use of a :class:`~django.template.RequestContext`.
+   forces the use of a :class:`~django.template.RequestContext`.
 
 Required arguments
 --

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

Re: [Django] #14091: PATCH: fix incorrect quoting in connection.queries for MySQL

[Django]

#14091: PATCH: fix incorrect quoting in connection.queries for MySQL
-+-
   Reporter:  danielr|Owner:  aaugustin
 Status:  new|Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

 * needs_tests:  1 => 0


Comment:

 Attached patch implements query retrieval for MySQL and Oracle, and proper
 query rebuilding for SQLite.

 With this patch, the postgresql (psycopg v1) backend still does not have
 proper escaping, but it is deprecated. A discussion on IRC determined that
 implementing a generic (SQL-92 style) parameter escaping function would be
 a bad idea, because it's extremely difficult to get right. For starters,
 mapping the Python types to database parameters is database dependent...
 So we will stick to database-specific implementations.

 I tested the patch under SQLite and MySQL.

 I do not have access to an Oracle server. My proposal is purely based on
 the doc. However, the change is trivial and could easily be reverted if
 the tests do not pass under Oracle.

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

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

Re: [Django] #361: Some Basic Math Filters

[Django]

#361: Some Basic Math Filters
---+---
   Reporter:  ilikeprivacy@…   |Owner:  adrian
 Status:  closed   |Milestone:
  Component:  Template system  |  Version:
 Resolution:  wontfix  | Keywords:  filter math
   Triage Stage:  Unreviewed   |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by lrekucki):

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


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

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

Re: [Django] #361: Some Basic Math Filters

[Django]

#361: Some Basic Math Filters
---+---
   Reporter:  ilikeprivacy@…   |Owner:  adrian
 Status:  reopened |Milestone:
  Component:  Template system  |  Version:
 Resolution:   | Keywords:  filter math
   Triage Stage:  Unreviewed   |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---

Comment (by lrekucki):

 Replying to [comment:6 anonymous]:
 > Django runs it's shop like the Third Reich... ADD MATH FILTERS

 Your behavior doesn't really deserve a comment, especially that you were
 brave enough not to sign it with your name. Normally people discuss this
 kind of stuff on the developers list, but I'm not sure if I want to
 discuss with this kind of offensive comments.

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

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

[Django] #15710: Typos in docs

[Django]

#15710: Typos in docs
---+---
 Reporter:  aaugustin  | Owner:  nobody
   Status:  new| Milestone:
Component:  Documentation  |   Version:  SVN
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  1  |
---+---
 See attached patch.

 No other instances of this error ("that that") exist:
 {{{
 for i in `find . -name '*.txt'`; do tr '\n' ' ' < $i | grep -q 'that
 *that' && echo $i; done
 }}}

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

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

Re: [Django] #361: Some Basic Math Filters

[Django]

#361: Some Basic Math Filters
---+---
   Reporter:  ilikeprivacy@…   |Owner:  adrian
 Status:  reopened |Milestone:
  Component:  Template system  |  Version:
 Resolution:   | Keywords:  filter math
   Triage Stage:  Unreviewed   |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by anonymous):

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


Comment:

 Django runs it's shop like the Third Reich... ADD MATH FILTERS

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

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

Re: [Django] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|Owner:  nobody
  Wassmann |Milestone:
 Status:  new|  Version:  SVN
  Component:  Database   | Keywords:
  layer (models, ORM)|Has patch:  1
 Resolution: |  Needs tests:  1
   Triage Stage:  Accepted   |
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-
Changes (by jpic):

 * cc: jpic (added)


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

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