Re: [Django] #11305: Support for "Conditional Aggregates"

2012-01-17 Thread Django 
#11305: Support for "Conditional Aggregates"
-+-
 Reporter:  bendavis78   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  ORM aggregation  |  Version:  1.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 Fully support this being added to the core... conditional aggregate was
 the first type of aggregate I attempted to do using Django :)

-- 
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] #10060: Multiple table annotation failure

2012-01-17 Thread Django 
#10060: Multiple table annotation failure
-+
 Reporter:  svsharma@…   |Owner:
 Type:  Bug  |   Status:  new
Component:  ORM aggregation  |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Fak3):

 * cc: Fak3 (added)


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

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

Re: [Django] #16955: Querying on the reverse of a FK with the wrong class silently returns bad data

2012-01-17 Thread Django 
#16955: Querying on the reverse of a FK with the wrong class silently returns 
bad
data
-+-
 Reporter:  jdunck   |Owner:  dgouldin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by nate_b):

 * needs_better_patch:  0 => 1


Comment:

 Your patch still applies cleanly, and there are no unexpected test
 failures.  After careful consideration toying with alternatives, I agree
 with your solution.  Two things though:

 For the sake of PEP8ness, could you put your imports at the top?  Or did
 you have a good reason to do your imports immediately preceeding your
 check?

 Also, in the {{{OneToOneTests.test_foreign_key}}} edit, why delete that
 line, instead of change it from {{{p}}} to {{{r}}}?

 In fact, that whole section looks like it always ought to have been closer
 to this:

 {{{
 assert_filter_waiters(restaurant__exact=self.r.pk)
 assert_filter_waiters(restaurant__exact=self.r)
 assert_filter_waiters(restaurant__pk=self.r.pk)
 assert_filter_waiters(restaurant=self.r.pk)
 assert_filter_waiters(restaurant=self.r)
 assert_filter_waiters(id__exact=self.r.pk)
 assert_filter_waiters(pk=self.r.pk)
 # Delete the restaurant; the waiter should also be removed
 r = Restaurant.objects.get(pk=self.r.pk)
 }}}

 It was only passing by the fortuitous accident that {{{self.p1.pk ==
 self.r.pk}}}.  Fix that up, and this patch looks good 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-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

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

2012-01-17 Thread Django 
#9025: Nested Inline Support in Admin
-+-
 Reporter:  pixelcort|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  1
-+-

Comment (by anonymous):

 +1

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

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

Re: [Django] #17541: Unexpected ForeignKey Behavior with self.pk == None

2012-01-17 Thread Django 
#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by nate_b):

 I spent some time looking at the rest of {{{related.py}}}, namely
 {{{ManyRelatedManager}}}, and found that in that case, it raises a
 {{{ValueError}}} (and has for many years).  Check out lines 538-539,
 inside {{{ManyRelatedManager.__init__}}}, and see #1745.  One to one
 fields fail in this manner as well (this would need to be fixed in
 {{{SingleRelatedObjectDescriptor.__get__}}}, as it does not use a
 Manager).

 So, I'm going to change my position on this slightly: for this bug to be
 closed, they should all be consistent.  Either {{{ValueError}}} should be
 raised in all three cases, or it should silently succeed in all three
 cases.

-- 
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] #17558: filter_horizontal does not display selected objects

2012-01-17 Thread Django 
#17558: filter_horizontal does not display selected objects
-+-
 Reporter:  dustin   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.4-alpha-1
 Keywords:  filter_horizontal,   |   Resolution:  needsinfo
  grappelli  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ramiro):

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


Comment:

 Please try to reproduce this w/o usin Grappelli and is you can, reopne
 this ticket with more information about so others can try to reproduce 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] #17557: Refactor form CBV to remove some unnecessary complexity

2012-01-17 Thread Django 
#17557: Refactor form CBV to remove some unnecessary complexity
-+-
 Reporter:  tswicegood   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Generic views|  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by tswicegood):

 From a comment on my commit on GitHub:

 > How is this simplifying ? Now every subclass has to do the `None` check
 (lines 37, 38) instead of just creating the form. Plus, it's backwards
 incompatible as current implementations assume `form_class` is never
 `None`.

 Unfortunately, it does look like `get_form_class` does document it's
 behavior.  I happen to think this behavior is much more intuitive, but BC
 concerns should be weighed as well.  One potential fix is to revert `post`
 back to its original behavior and modify `get_context_data` to always pass
 in `get_form_class`'s results when adding the default `form` to the
 context.  That maintains backwards compatibility, but does end up with a
 net gain in LOC.

 It might help to understand my original thought process to see
 
[https://github.com/tswicegood/cbv_utils/blob/3acfb378b69b3f6907749f43a932133fb7dccb94/cbv_utils/views.py
 this code] which was my original motivation.  I was attempting to add in
 the inline formset behavior with minimal changes, but after looking at it
 again this evening I see a few ways I can refactor this code to limit the
 # of changes.  The only problem is that I will be implementing it
 differently than Django's `FormMixin`, which feels odd.

 Any thoughts?

-- 
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] #17558: filter_horizontal does not display selected objects

2012-01-17 Thread Django 
#17558: filter_horizontal does not display selected objects
---+--
 Reporter:  dustin |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4-alpha-1
 Severity:  Normal |   Keywords:  filter_horizontal, grappelli
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 I am using grappelli (which may or may not be affecting this).  See this
 screenshot 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.

Re: [Django] #17510: Typo at https://docs.djangoproject.com/en/1.3/topics/class-based-views/#dynamic-filtering

2012-01-17 Thread Django 
#17510: Typo at https://docs.djangoproject.com/en/1.3/topics/class-based-views
/#dynamic-filtering
-+-
 Reporter:  andrew@… |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  typo,| Triage Stage:  Accepted
  documentation, web |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by noria):

 * 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-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] #17554: Link to Spatialite resources broken

2012-01-17 Thread Django 
#17554: Link to Spatialite resources broken
---+
 Reporter:  jacob@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * easy:  0 => 1
 * needs_tests:   => 0
 * 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-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] #17453: IRC logs link is not reachable

2012-01-17 Thread Django 
#17453: IRC logs link is not reachable
-+-
 Reporter:  shantanoo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

 * 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] #17557: Refactor form CBV to remove some unnecessary complexity

2012-01-17 Thread Django 
#17557: Refactor form CBV to remove some unnecessary complexity
-+-
 Reporter:  tswicegood   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Generic views|  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by tswicegood):

 Nope -- nevermind.  Jumped the gun on that one.  It should use the
 explicit version here as that version has the cleaned data in it.  Also,
 it was `form_invalid` that's using `get_context_data(form=form)`.

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

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

Re: [Django] #17557: Refactor form CBV to remove some unnecessary complexity

2012-01-17 Thread Django 
#17557: Refactor form CBV to remove some unnecessary complexity
-+-
 Reporter:  tswicegood   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Generic views|  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by tswicegood):

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


Comment:

 This patch needs a little tweaking.  `form_valid()` should use the minimal
 `get_context_data()` call.

-- 
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] #16315: FileSystemStorage.listdir returns names with unicode normalization form that is different from names in database

2012-01-17 Thread Django 
#16315: FileSystemStorage.listdir returns names with unicode normalization form
that is different from names in database
-+-
 Reporter:  philomat |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  File |  Version:  1.3
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  storage unicode  |  Unreviewed
  normalization  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

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


Comment:

 - writing a file called u'\xe4', then listdir(), and see if it has turned
 into u'a\u0308'
 This indeed turns into  u'a\u0308'. The file system is Mac OS Extended
 (Journaled).

 - saving the string u'a\u0308' in the database (in any CharField), then
 retreive it, and see if it has turned into u'\xe4'
 This fails, MySQL gives me an OperationalError: (1267, "Illegal mix of
 collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE)
 for operation '='")

-- 
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] #16961: Unit tests 10 times slower on Linux if MySQL is used

2012-01-17 Thread Django 
#16961: Unit tests 10 times slower on Linux if MySQL is used
-+-
 Reporter:  aigarius@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  mysql|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by nate_b):

 * has_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #17557: Refactor form CBV to remove some unnecessary complexity

2012-01-17 Thread Django 
#17557: Refactor form CBV to remove some unnecessary complexity
--+-
 Reporter:  tswicegood|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Generic views |Version:  1.4-alpha-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+-
 While creating a CBV to work with inline formsets, I ran into a few places
 where copy-n-paste was the only way to adjust the behavior that I was
 after and keep the same feel of the internal Django CBV.  This refactor
 removes the need to copy-n-paste out of `get` in order to add additional
 data by moving the generation of the `form` context data into
 `get_context_data`.

-- 
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] #17556: Let Media classes to inherit

2012-01-17 Thread Django 
#17556: Let Media classes to inherit
-+-
 Reporter:  ojo  |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Forms|Version:  SVN
 Severity:  Normal   |   Keywords:  forms media
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+-
 Media classes in `ModelAdmin` or `Form` cannot inherit from other classes:

 {{{
 class BaseMedia:
 css = {"all": ["base.css", ] }

 class ExampleAdmin(ModelAdmin):
 class Media(BaseMedia):
 js = ["example.js, ]
 }}}

 In the example above, only js media will be available. This is because of
 the following code in django/forms/widgets.py:

 {{{
 class Media(StrAndUnicode):
 def __init__(self, media=None, **kwargs):
 if media:
 media_attrs = media.__dict__
 else:
 media_attrs = kwargs
 }}}

 `__dict__` doesn't include inherited properties.

 My proposal is to use `getmembers` from `inspect` module:

 {{{
 media_attrs = dict(getmembers(media))
 }}}

 I've attached a 2-lines patch. All unit tests passed against revision
 17377.

-- 
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] #17419: JSON template tag

2012-01-17 Thread Django 
#17419: JSON template tag
---+---
 Reporter:  lau|Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Template system|  Version:  1.4-alpha-1
 Severity:  Normal |   Resolution:
 Keywords:  json template tag  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+---

Comment (by olau):

 Sounds nice that it's going in, but playing it safe isn't necessarily that
 helpful. {{{escape}}} turns " into {{{"}}}, which means you can't
 output a string in that JSON without {{{safe}}} - including a simple
 object like {{{ { "a": 123 .

 I've tested a simple
 {{{
 
 var x = "foo";
 
 }}}
 with both an HTML5 doctype an XHTML 1 strict doctype, and it doesn't work
 in any of them. So it seems to me this filter is never useful in script
 tags without {{{safe}}}? It would perhaps be better to add a warning to
 the documentation?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #17552: The GZip Middleware's browser checking is too broad and misses versions of Netscape which have similar bugs

2012-01-17 Thread Django 
#17552: The GZip Middleware's browser checking is too broad and misses versions 
of
Netscape which have similar bugs
-+-
 Reporter:  cannona  |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  gzip middleware  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * stage:  Unreviewed => Accepted


Comment:

 This looks interesting.

-- 
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] #17419: JSON template tag

2012-01-17 Thread Django 
#17419: JSON template tag
---+---
 Reporter:  lau|Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Template system|  Version:  1.4-alpha-1
 Severity:  Normal |   Resolution:
 Keywords:  json template tag  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+---
Changes (by aaugustin):

 * owner:  nobody => aaugustin


Comment:

 Thanks for updating the patch.

 This is a new feature, so I need to check if I can slip it in 1.4 now or
 if it'll have to wait for 1.5. Anyway, I intend to commit it eventually,
 as I've felt the need for such a tag quite often.

-- 
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] #17555: LocaleMiddleware wrongly redirects paths without trailing slash

2012-01-17 Thread Django 
#17555: LocaleMiddleware wrongly redirects paths without trailing slash
-+-
 Reporter:  Tuttle   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  SVN
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tuttle):

 * version:  1.3 => SVN


-- 
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] #17555: LocaleMiddleware wrongly redirects paths without trailing slash

2012-01-17 Thread Django 
#17555: LocaleMiddleware wrongly redirects paths without trailing slash
-+-
 Reporter:  Tuttle   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by ramiro):

 * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #17555: LocaleMiddleware wrongly redirects paths without trailing slash

2012-01-17 Thread Django 
#17555: LocaleMiddleware wrongly redirects paths without trailing slash
-+-
 Reporter:  Tuttle   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tuttle):

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


Comment:

 Replying to [ticket:17555 Tuttle]:
 > ... translation.get_language_from_path() does a bad redirection...

 It causes it, not that it does it, of course.

-- 
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] #17555: LocaleMiddleware wrongly redirects paths without trailing slash

2012-01-17 Thread Django 
#17555: LocaleMiddleware wrongly redirects paths without trailing slash
--+
 Reporter:  Tuttle|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 On requests with path like '/en', the translation.get_language_from_path()
 does a bad redirection to, say, '/cs/en' in case the browser asks for
 Czech language.

 I think the language-code detection regexp should respect ending slash-
 less paths.
 Patch 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] #17554: Link to Spatialite resources broken

2012-01-17 Thread Django 
#17554: Link to Spatialite resources broken
---+
 Reporter:  jacob@…|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  SVN
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The link referred to under
 https://docs.djangoproject.com/en/dev/ref/contrib/gis/install/#create-
 spatialite-db as "SpatiaLite Resources" is broken, as well as the one
 referred to by the `wget` example directly underneath it (http://www.gaia-
 gis.it/spatialite/init_spatialite-2.3.sql.gz). They booth ends up at 404
 -pages.

-- 
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] #17541: Unexpected ForeignKey Behavior with self.pk == None

2012-01-17 Thread Django 
#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 Your approach is much better. That is the right spot to add the .none()
 call.

 Would there be a need for similar handling for M2M and `GenericRelations`.
 I don't know and do not have time to check this right now.

 As for .none() fixing: I think that could be fixed in an elegant way by
 introducing `EmptyClause` which you would add to the query's where when
 .none() is called. The `EmptyClause` would throw an `EmptyResultSet` from
 its .as_sql() method (which would be called by compiler.as_sql() ->
 where.as_sql() -> for each node, call as_sql()). Thus, you would not need
 the `EmptyQuerySet` class at all. You would get `EmptyResultSet` exception
 from print qs.query. I think that would work. Not sure, as I haven't
 tried. But as said, different ticket's 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-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] #17541: Unexpected ForeignKey Behavior with self.pk == None

2012-01-17 Thread Django 
#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by nate_b):

 * needs_better_patch:  1 => 0


Comment:

 Okay, I agree.  I had never noticed that behavior of {{{EmptyQuerySet}}}
 before.

 Taking those considerations into account, what do you think about throwing
 the {{{none()}}} onto the filtered result instead, as in my suggested
 patch?  That way, the {{{query}}} would at least no longer be peculiar.
 Then, if the {{{EmptyQuerySet}}} behavior is ever fixed, the correctness
 of this query will get fixed as a consequence.

 So, whether you like my suggested change, or reject it, you've convinced
 me, and I no longer think this patch needs improvement.

-- 
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] #17453: IRC logs link is not reachable

2012-01-17 Thread Django 
#17453: IRC logs link is not reachable
---+
 Reporter:  shantanoo  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by noria):

 * has_patch:  0 => 1


Comment:

 A part was already done in #16277.
 I have search others occurrences with grep.
 Here are two patches, one for the django app, and one for the
 djangoproject.com website.

-- 
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] #17541: Unexpected ForeignKey Behavior with self.pk == None

2012-01-17 Thread Django 
#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 I was preparing a response too, while akaariai posted his comment. So
 agreed on the peculiarity of the representation of the query attribute on
 EmptyQuerySet.

 I still think that at a semantic level, an unsaved model should have empty
 related sets, and querying those should not raise errors.

-- 
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] #17541: Unexpected ForeignKey Behavior with self.pk == None

2012-01-17 Thread Django 
#17541: Unexpected ForeignKey Behavior with self.pk == None
-+-
 Reporter:  sheats   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 About the `EmptyQuerySet` query string behaviour: That is how it works.
 That is a deficiency of .none(), and works just like any other query using
 .none(). Fixing that would be another ticket's problem.

 However, if raising error here is the correct thing to do is an
 interesting question. It does have its plus-sides: it would allow us to
 change the implementation later if need be, and it would be very obvious
 to the programmer what is happening. On the other hand, in this case
 .car_set would not behave like queryset. This could be a problem when you
 have a model like:

 {{{
 class SomeModel:
 id = models.AutoField(pk=True)
 some_f = models.CharField(max_length=200, unique=True, null=True)

 class RelatedModel:
 somemodel = models.ForeignKey(SomeModel, to_field='some_f', null=True)
 }}}

 Now, you could have an instance of somemodel in the DB, with some_f null
 and related models with null somemodel field. Now, that is a bit unlikely
 case, but here raising an error could be a little dangerous. I wonder what
 joys multicolumn primary keys and especially foreign keys will bring us in
 the future.

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