Re: [Django] #8716: When a authenticated user post a comments, the field's form is not populate with data of user

[Django]

#8716: When a authenticated user post a comments, the field's form is not 
populate
with data of user
-+-
 Reporter:  jmad |Owner:  jmad
 Type:  Uncategorized|   Status:  closed
Component:  contrib.comments |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Cheap Polo, Ralph| Triage Stage:  Accepted
  Lauren,cheap lacoste polo toms |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

 * keywords:  toms shoes ,cheap toms => Cheap Polo, Ralph Lauren,cheap
 lacoste polo toms


Comment:

 http://www.ralphlauren2012polo.com/;>Cheap PoloGive As
 GiftsWhen you need to give gifts to clients or employees, one way to do so
 it so givehttp://www.ralphlauren2012polo.com/;> Ralph
 Lauren.When made with high quality custom embroidery,  http://www.ralphlauren2012polo.com/;>cheap lacoste polothese
 shirts will last a long time. http://www.ralphlauren2012polo.com/;>Wholesale Polo Shirt Unlike
 http://www.ralphlauren2012polo.com/;>cheap Ralph Lauren that
 are made with transfers, custom polo shirts made with custom embroidery
 last for as long as the shirt and give the wearer an air of distinction.
 http://www.ralphlauren2012polo.com/;>lacoste poloThese are
 quality shirts and will represent your business in a positive light. http://www.ralphlauren2012polo.com/;>cheap lacoste poloNot only
 can you give a gift to others by ordering custom polo shirts, http://www.ralphlauren2012polo.com/;>Customize Polo Shirtbut you
 can also gain free advertising every time they wear your
 

Re: [Django] #8716: When a authenticated user post a comments, the field's form is not populate with data of user

[Django]

#8716: When a authenticated user post a comments, the field's form is not 
populate
with data of user
-+-
 Reporter:  jmad |Owner:  jmad
 Type:  Uncategorized|   Status:  closed
Component:  contrib.comments |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  toms shoes ,cheap| Triage Stage:  Accepted
  toms   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

 * keywords:
 Wholesale Polo Shirt,, cheap Ralph Lauren, , lacoste polo, cheap
 lacoste polo, Customize Polo Shirt. Cheap Polo, Ralph Lauren,cheap
 lacoste polo
 => toms shoes ,cheap toms


Comment:

 Tom�s shoes are all about the fairness in business that seems to be
 lacking in most enterprises now a days.
 [url=http://www.tomsshoesoutlet.com/] toms shoes [/url]The company,
 founded by Blake Mycoskie in 2006 is based on the principle of serving
 those in need.[url=http://www.tomsshoesoutlet.com/]cheap toms[/url] For
 every Toms shoes that you buy, a pair is donated to a child without shoes.
 It has declared that it is a non-profit
 company.[url=http://www.tomsshoesoutlet.com/]toms footwear[/url]
 It works on a mission of �one for one�. The company also works on the fair
 trade policy where the laborers get fair wages and do not have to work
 under inhuman working conditions. They currently manufacture in Argentina,
 Ethiopia and China.http://www.tomsshoesoutlet.com/;>www.tomsshoesoutlet.com/

-- 
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] #8716: When a authenticated user post a comments, the field's form is not populate with data of user

[Django]

#8716: When a authenticated user post a comments, the field's form is not 
populate
with data of user
-+-
 Reporter:  jmad |Owner:  jmad
 Type:  Uncategorized|   Status:  closed
Component:  contrib.comments |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Wholesale Polo   | Triage Stage:  Accepted
  Shirt,, cheap Ralph Lauren, ,  |  Needs documentation:  0
  lacoste polo, cheap lacoste polo,  |  Patch needs improvement:  0
  Customize Polo Shirt. Cheap Polo,  |UI/UX:  0
  Ralph Lauren,cheap lacoste polo|
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by anonymous):

 * keywords:   =>
 Wholesale Polo Shirt,, cheap Ralph Lauren, , lacoste polo, cheap
 lacoste polo, Customize Polo Shirt. Cheap Polo, Ralph Lauren,cheap
 lacoste polo
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 The style of Ralph Lauren polo shirts is suitable for both men and women
 alike. http://www.poloralphlaurenabc.com/;>ralph lauren polo
 shirtsThese t-shirts come in a wide range of colors and patterns. http://www.poloralphlaurenabc.com/;>cheap polo shirtsThe
 t-shirts for men come in colors that are popular among men and young boys
 as well. colors like black and red are mainly used, as these colors look
 good on almost all skin complexions, and also do not get spoiled easily
 and are thus easy to maintain. http://www.poloralphlaurenabc.com/;>polo outletOther colors like
 orange, crème, navy blue, dark green, blue, green, yellow, white, pink,
 light blue, electric blue, and pink among
 

Re: [Django] #18614: https://docs.djangoproject.com/en/1.4/topics/forms/ missing some sample code

[Django]

#18614: https://docs.djangoproject.com/en/1.4/topics/forms/ missing some sample
code
-+-
 Reporter:  xarses@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  from csrf missing|  Needs documentation:  0
  imports|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by kevinlondon):

 * has_patch:  0 => 1


Comment:

 Fork: https://github.com/kevinlondon/django/tree/ticket_18614_1_4

 Pull Request: https://github.com/django/django/pull/212

-- 
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] #18616: New auth signal: user_login_failed

[Django]

#18616: New auth signal: user_login_failed
--+
 Reporter:  micolous  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by micolous):

 Brad, the documentation looks good, however the use of the sender
 parameter isn't correct there (it appears copy-pasted from the logout
 signal?)

 The sender parameter sends the name of the auth module.  Because the login
 failure isn't tied directly to a request (`authenticate` doesn't provide
 such a parameter), it doesn't know about where it came from.

 This comes back to my note in the OP that I'm unsure if this should be
 something fixed in the signal or if the `traceback` module is a better
 option.  Or perhaps the signal should just set the sender to `None`.

-- 
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] #18633: Can't use parenthesis in Documentation search bar

[Django]

#18633: Can't use parenthesis in Documentation search bar
-+-
 Reporter:  kevinlondon  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Djangoproject.com|  Version:  1.4
  Web site   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  website, search, |  Unreviewed
  documentation  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by bmess):

 I was able to reproduce this.  Used Google Chrome Version 20.0.1132.57

-- 
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] #18629: Adding methods/attributes to editing views

[Django]

#18629: Adding methods/attributes to editing views
--+
 Reporter:  pydanny   |Owner:  donigian
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  cbv   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by pydanny):

 The developer working this ticket ended up working on Date CBVs. Can we
 get a title change on this ticket to reflect that?

 I'm working #18632 which is the one on editing CBVs.

-- 
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] #18633: Can't use parenthesis in Documentation search bar

[Django]

#18633: Can't use parenthesis in Documentation search bar
-+-
 Reporter:  kevinlondon  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Djangoproject.com|  Version:  1.4
  Web site   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  website, search, |  Unreviewed
  documentation  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by kevinlondon):

 * keywords:  website => website, search, documentation
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #18632: Cleanup on methods/attributes associated with editing views

[Django]

#18632: Cleanup on methods/attributes associated with editing views
-+-
 Reporter:  pydanny  |Owner:  pydanny
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by pydanny):

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


Comment:

 Argh. Ticket named for this one. :P

-- 
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] #18632: Cleanup on methods/attributes associated with editing views

[Django]

#18632: Cleanup on methods/attributes associated with editing views
-+-
 Reporter:  pydanny  |Owner:  pydanny
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by pydanny):

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


Comment:

 Dupe of #18629

-- 
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] #18633: Can't use parenthesis in Documentation search bar

[Django]

#18633: Can't use parenthesis in Documentation search bar
+-
 Reporter:  kevinlondon |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Djangoproject.com Web site  |Version:  1.4
 Severity:  Normal  |   Keywords:  website
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  1
+-
 If I use the search bar in the right side of the Documentation section, I
 cannot search for methods or other text that contains parenthesis. For
 instance, if I search for "delete", I get a number of search results. If I
 search for "delete()", however, I do not get any results.

-- 
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] #18632: Cleanup on methods/attributes associated with editing views

[Django]

#18632: Cleanup on methods/attributes associated with editing views
--+-
 Reporter:  pydanny   |  Owner:  pydanny
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 The current docs have improved, but they still need work.

-- 
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] #18628: Adding methods/attributes to display views

[Django]

#18628: Adding methods/attributes to display views
--+
 Reporter:  pydanny   |Owner:  pydanny
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  cbv   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by pydanny):

 Work for this ticket is taking place in this Django fork/branch on github:
 https://github.com/pydanny/django/tree/ticket_18628

-- 
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] #18631: A way to get handle to the generated query for terminal queryset methods

[Django]

#18631: A way to get handle to the generated query for terminal queryset methods
-+-
   Reporter:  akaariai   |  Owner:  nobody
   Type:  New| Status:  new
  feature|Version:  1.4
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 When debugging or testing generated ORM queries it is often useful to get
 a handle to generated queryset from terminal qs methods (like .update() or
 .aggregate()) instead of executing the query.

 The attached proof-of-concept shows a way to achieve this.

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

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

Re: [Django] #18580: Avoiding SQLite update+annotations "only a single result allowed for a SELECT that is part of an expression"

[Django]

#18580: Avoiding SQLite update+annotations "only a single result allowed for a
SELECT that is part of an expression"
-+
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  ORM aggregation  |  Version:  1.4
 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
-+

Comment (by akaariai):

 I created an evil little patch to debug this further: patch attached, the
 problematic SQL is this:
 {{{
 UPDATE "update_datapoint" SET "value" = foo WHERE "update_datapoint"."id"
 IN
 (SELECT U0."id", COUNT(U1."name") AS "relatedpoint__name__count"
  FROM "update_datapoint" U0 LEFT OUTER JOIN "update_relatedpoint" U1
ON (U0."id" = U1."data_id")
 GROUP BY U0."id", U0."name", U0."value", U0."another_value")
 }}}

 I don't see any reason to keep the aggregation in the inner query set.
 Maybe just getting rid of the annotation in the inner qs will solve this
 ticket?

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

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

Re: [Django] #18580: Avoiding SQLite update+annotations "only a single result allowed for a SELECT that is part of an expression"

[Django]

#18580: Avoiding SQLite update+annotations "only a single result allowed for a
SELECT that is part of an expression"
-+
 Reporter:  jonash   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  ORM aggregation  |  Version:  1.4
 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 aaugustin):

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


Comment:

 With these models:
 {{{
 class Foo(models.Model):
 name = models.CharField(max_length=10)

 class Bar(models.Model):
 foo = models.ForeignKey(Foo)
 }}}
 I could reproduce the problem:
 {{{

 >>> Foo.objects.annotate(bar_count=Count('bar')).update(name='blah')
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/myk/Documents/dev/django-trunk/django/db/models/query.py",
 line 544, in update
 rows = query.get_compiler(self.db).execute_sql(None)
   File "/Users/myk/Documents/dev/django-
 trunk/django/db/models/sql/compiler.py", line 990, in execute_sql
 cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
   File "/Users/myk/Documents/dev/django-
 trunk/django/db/models/sql/compiler.py", line 822, in execute_sql
 cursor.execute(sql, params)
   File "/Users/myk/Documents/dev/django-trunk/django/db/backends/util.py",
 line 42, in execute
 return self.cursor.execute(sql, params)
   File "/Users/myk/Documents/dev/django-
 trunk/django/db/backends/sqlite3/base.py", line 342, in execute
 return Database.Cursor.execute(self, query, params)
 DatabaseError: only a single result allowed for a SELECT that is part of
 an expression
 >>>
 Foo.objects.annotate(bar_count=Count('bar')).values('id').update(name='blah')
 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.

Re: [Django] #18501: Custom fields as foreign keys fix

[Django]

#18501: Custom fields as foreign keys fix
-+-
 Reporter:  msopacua |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  RelatedField |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Could you provide a test case ? Or at least a minimal code sample and
 instructions to reproduce the problem?

 That would be much easier for us than trying to rebuild an example from
 your description.

-- 
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] #18595: Wrong table used in get_query_set when two Models have ManyToMany Fields to a common third Model using related_name='+'

[Django]

#18595: Wrong table used in get_query_set when two Models have ManyToMany 
Fields to
a common third Model using related_name='+'
-+-
 Reporter:  sean@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Oops - I read "I can verify" instead of "I can't verify".

 This ticket reports a bug after applying a patch that wasn't committed in
 Django yet -- and probably won't.

-- 
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] #18595: Wrong table used in get_query_set when two Models have ManyToMany Fields to a common third Model using related_name='+'

[Django]

#18595: Wrong table used in get_query_set when two Models have ManyToMany 
Fields to
a common third Model using related_name='+'
-+-
 Reporter:  sean@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting per Anssi's comment. See also #15932.

-- 
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] #18621: Two ManyToMany fields without backwards relation

[Django]

#18621: Two ManyToMany fields without backwards relation
-+-
 Reporter:  anonymous|Owner:  anonymous
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  backwards relation   |  Needs documentation:  0
  model  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 Actually a duplicate of #15932.

-- 
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] #15932: related_name='+' ignored in ManyToManyField validation

[Django]

#15932: related_name='+' ignored in ManyToManyField validation
---+--
 Reporter:  Fredde |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | 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):

 * component:  Database layer (models, ORM) => Documentation


Comment:

 #18621 was a duplicate. I had forgotten about this ticket. I think it's a
 documentation issue. `related_name` must be unique and can end with `'+'`
 if you don't want the reverse relation to be created (although I don't
 know in which circumstances you wouldn't want to -- I you don't use it it
 doesn't hurt!)

-- 
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] #18595: Wrong table used in get_query_set when two Models have ManyToMany Fields to a common third Model using related_name='+'

[Django]

#18595: Wrong table used in get_query_set when two Models have ManyToMany 
Fields to
a common third Model using related_name='+'
-+-
 Reporter:  sean@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 I can't verify this ticket - having two related_name='+' doesn't validate.
 A small problematic 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.

Re: [Django] #18621: Two ManyToMany fields without backwards relation

[Django]

#18621: Two ManyToMany fields without backwards relation
-+-
 Reporter:  anonymous|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  backwards relation   |  Needs documentation:  0
  model  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Database layer (models, ORM) => Documentation
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Set `related_name='foo+'` on one field and `related_name='bar+'` on the
 other. It will work.

 The documentation could explain that.

 

 That said, Frank's comment isn't wrong:
 > I would ask why you're bothered by having the backwards relation, just
 don't use it if you don't want it.
 [[BR]]

 To be honest, I'm not sure why this feature exists!

-- 
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] #18509: Bug: forms.DecimalField doesn't validate correctly when localized. (Unittest attached)

[Django]

#18509: Bug: forms.DecimalField doesn't validate correctly when localized.
(Unittest attached)
-+-
 Reporter:  serge_spaolonzi  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Design decision needed


Comment:

 The input isn't ambiguous: both `"123.45"` and `"123,45"` represent
 `Decimal("123.45").

 I don't see much value in rejecting the first form, especially Django
 historically accepts it. I would go as far as to say it isn't worth the
 backwards incompatibility.

-- 
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] #18391: Inline forms fail to delete objects when PK is a custom field

[Django]

#18391: Inline forms fail to delete objects when PK is a custom field
-+-
 Reporter:  max@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inline form custom   | Triage Stage:
  field  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 The patch doesn't contain a test case. Could you provide a minimal example
 that triggers the bug (custom field, model and admin definitions)? Or at
 least the full traceback? That would save us some 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-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] #18630: Update version in docs/intro/install.txt

[Django]

#18630: Update version in docs/intro/install.txt
--+
 Reporter:  kevinlondon   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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 aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 I could be better to add a sentence to the effect of "you may have another
 version installed" than to update the value for each minor release, in
 each 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-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] #18491: When deleting a proxy model, the admin does not show warning about cascade delete for object with foreign key on the proxied model

[Django]

#18491: When deleting a proxy model, the admin does not show warning about 
cascade
delete for object with foreign key on the proxied model
---+
 Reporter:  bdauvergne@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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 akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 I have verified this in HEAD.

-- 
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] #18628: Adding methods/attributes to display views

[Django]

#18628: Adding methods/attributes to display views
--+
 Reporter:  pydanny   |Owner:  pydanny
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  cbv   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * keywords:   => cbv
 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * 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] #18629: Adding methods/attributes to editing views

[Django]

#18629: Adding methods/attributes to editing views
--+
 Reporter:  pydanny   |Owner:  donigian
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  cbv   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * keywords:   => cbv
 * 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] #18629: Adding methods/attributes to editing views

[Django]

#18629: Adding methods/attributes to editing views
-+-
 Reporter:  pydanny  |Owner:  donigian
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 #18628 is about display view, this ticket is about editing views.

 And pydanny knows what he does :)

-- 
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] #18520: forms.ImageField loads entire file into memory, crashes server

[Django]

#18520: forms.ImageField loads entire file into memory, crashes server
-+-
 Reporter:  gregplaysguitar  |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 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 aaugustin):

 * owner:  nobody => aaugustin
 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * 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] #18491: When deleting a proxy model, the admin does not show warning about cascade delete for object with foreign key on the proxied model

[Django]

#18491: When deleting a proxy model, the admin does not show warning about 
cascade
delete for object with foreign key on the proxied model
---+--
 Reporter:  bdauvergne@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 Here's the history of bugs related to deletion of proxy models: #18083,
 #16128, #12208, #6.

-- 
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] #18174: Model inheritance pointers doesn't refer to parent to refer to grandparents

[Django]

#18174: Model inheritance pointers doesn't refer to parent to refer to 
grandparents
-+-
 Reporter:  phowe|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


Comment:

 Verified the issue, and added a patch containing tests for this.

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

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

Re: [Django] #18630: Update version in docs/intro/install.txt (was: Update version in install docs)

[Django]

#18630: Update version in docs/intro/install.txt
-+-
 Reporter:  kevinlondon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 kevinlondon):

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


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

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

[Django] #18630: Update version in install docs

[Django]

#18630: Update version in install docs
--+
 Reporter:  kevinlondon   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 Change 1.4 to 1.5 in the "Verifying" section at the bottom of
 intro/install.txt to reflect updated version.

-- 
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] #17952: Sqlite and mysql generating different queries with the same code

[Django]

#17952: Sqlite and mysql generating different queries with the same code
-+-
 Reporter:  glen.nelson.1@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 I tested this with a trivial test in regressiontests/aggregation_regress:
 {{{
 def test_range_filtering(self):
 start = datetime.datetime(1900, 1, 1)
 end = datetime.datetime(2100, 1, 1)
 qs = Book.objects.filter(pubdate__range=(start, end)).values(
 'contact').annotate(Count('id')).order_by()
 print qs
 print qs.query
 }}}
 I could not reproduce the reported error in HEAD. It might be I am missing
 some key piece of the puzzle. That piece should be provided by the
 original reporter. Closing as worksforme, please reopen with additional
 information about the used models if the error is still present for you in
 1.4 or HEAD.

-- 
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] #18168: formfield_for_choice_field() doesn't validate choices updated in method

[Django]

#18168: formfield_for_choice_field() doesn't validate choices updated in method
-+-
 Reporter:  Robert   |Owner:  nobody
   |   Status:  new
 Type:  Bug  |  Version:  1.3
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  admin, inlines   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 There is no traceback -- the validation error is displayed in the admin.

 The reporter's example uses inlines. I could reproduce the issue with the
 following code. Screenshot attached.

 {{{
 # models.py

 from django.db import models1

 class Variable(models.Model):
 NAME_CHOICES = (
 ('foo', 'foo'),
 ('bar', 'bar'),
 ('baz', 'baz'),
 )
 name  = models.CharField(max_length=3, choices=NAME_CHOICES)

 # admin.py

 from django.contrib import admin
 from .models import Variable

 class VariableAdmin(admin.ModelAdmin):

 def formfield_for_choice_field(self, db_field, request, **kwargs):
 if db_field.name == "name":
 kwargs['choices'] = (
 ('quux', 'quux'),
 ('quuux', 'quuux'),
 )
 return super(VariableAdmin,
 self).formfield_for_choice_field(db_field, request, **kwargs)

 admin.site.register(Variable, VariableAdmin)
 }}}

 

 I don't think it makes sense to allow in the form values that aren't
 allowed by the model. If I understand correctly this method can only be
 used to restrict changes, not to extend them. If that's true, it should be
 mentioned in the documentation of formfield_for_choice_field.

-- 
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] #18629: Adding methods/attributes to editing views

[Django]

#18629: Adding methods/attributes to editing views
-+-
 Reporter:  pydanny  |Owner:  donigian
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Dupe of #18628

-- 
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] #18404: SuspiciousOperation exception is thrown if application static path contains non-ascii characters

[Django]

#18404: SuspiciousOperation exception is thrown if application static path 
contains
non-ascii characters
-+-
 Reporter:  andkit@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.4
 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 aaugustin):

 I tried the sample project but `runserver` didn't even start:
 {{{
 (django-dev)myk@mYk bug18404 % locale
 ~/Downloads/kap%FCt/bug18404
 LANG="fr_FR.ISO-8859-1"
 LC_COLLATE="fr_FR"
 LC_CTYPE="fr_FR"
 LC_MESSAGES="fr_FR"
 LC_MONETARY="fr_FR"
 LC_NUMERIC="fr_FR"
 LC_TIME="fr_FR"
 LC_ALL="fr_FR"
 (django-dev)myk@mYk bug18404 % python manage.py runserver --traceback
 ~/Downloads/kap%FCt/bug18404
 Traceback (most recent call last):
   File "/Users/myk/Documents/dev/django-
 trunk/django/core/management/base.py", line 222, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/myk/Documents/dev/django-
 trunk/django/core/management/base.py", line 247, in execute
 translation.activate('en-us')
   File "/Users/myk/Documents/dev/django-
 trunk/django/utils/translation/__init__.py", line 89, in activate
 return _trans.activate(language)
   File "/Users/myk/Documents/dev/django-
 trunk/django/utils/translation/trans_real.py", line 179, in activate
 _active.value = translation(language)
   File "/Users/myk/Documents/dev/django-
 trunk/django/utils/translation/trans_real.py", line 168, in translation
 default_translation = _fetch(settings.LANGUAGE_CODE)
   File "/Users/myk/Documents/dev/django-
 trunk/django/utils/translation/trans_real.py", line 151, in _fetch
 apppath = os.path.join(os.path.dirname(app.__file__), 'locale')
   File "/Users/myk/.virtualenvs/django-
 dev/bin/../lib/python2.7/posixpath.py", line 71, in join
 path += '/' + b
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 24:
 ordinal not in range(128)
 }}}

 Apparently my terminal (under OS X) doesn't support `export
 LC_ALL=fr_FR.ISO-8859-1`; that activates the C locale instead.

-- 
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] #15084: Unnecessary imports lead to ImportError

[Django]

#15084: Unnecessary imports lead to ImportError
--+
 Reporter:  vanschelven   |Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by akaariai):

 I tested the supplied test code in this ticket (comment:20). The problem
 is gone when using the app-loading branch.

 However, there might be another problem: I added a debug print to
 trans_real.py line 150:
 {{{
 print app_cache.loaded_apps
 }}}
 Result: [].

 I do run a bare script. That is, I run the script with:
 {{{
 DJANGO_SETTINGS_MODULE=settings python test_trans.py
 }}}
 And the file contents are:
 {{{
 #from django.apps import app_cache
 #app_cache._populate()
 from defining_app import TranslatedClass
 }}}

 If I remove the comments from the file (ensure the app_cache is
 populated), I get more expected result from the debug print.

 It seems there is a deeper problem in the app-loading branch, that is
 there is one entry point which isn't ensured to do app-loading early
 enough. It seems the app-loading branch could break a bunch of current
 applications using bare scripts.

-- 
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/django] 35ddee: Removed debugging line left in previous commit

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 35ddeee45573de57ae3c791bf36496b4a7028ddf
  
https://github.com/django/django/commit/35ddeee45573de57ae3c791bf36496b4a7028ddf
  Author: Claude Paroz 
  Date:   2012-07-15 (Sun, 15 Jul 2012)

  Changed paths:
M django/contrib/gis/tests/test_geoforms.py

  Log Message:
  ---
  Removed debugging line left in previous commit



-- 
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/django] cdcdd1: Dropped support for GDAL < 1.5

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cdcdd131da950741fa74debc21bef8632fd3c684
  
https://github.com/django/django/commit/cdcdd131da950741fa74debc21bef8632fd3c684
  Author: Claude Paroz 
  Date:   2012-07-15 (Sun, 15 Jul 2012)

  Changed paths:
M django/contrib/gis/gdal/__init__.py
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/gdal/libgdal.py
M django/contrib/gis/gdal/prototypes/geom.py
M django/contrib/gis/gdal/tests/test_geom.py
M django/contrib/gis/geos/base.py
M django/contrib/gis/geos/geometry.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/tests/test_geoforms.py
M docs/ref/contrib/gis/gdal.txt
M docs/ref/contrib/gis/install.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  Dropped support for GDAL < 1.5

GDAL 1.5 has been released in December 2007.



-- 
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] #18629: Adding methods/attributes to editing views

[Django]

#18629: Adding methods/attributes to editing views
--+--
 Reporter:  pydanny   |  Owner:  donigian
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 The methods and attributes are being added in order to aid users of the
 Django Class Based Views.

-- 
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] #18628: Adding methods/attributes to display views

[Django]

#18628: Adding methods/attributes to display views
--+-
 Reporter:  pydanny   |  Owner:  pydanny
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 The methods and attributes are being added in order to aid users of the
 Django Class Based Views.

-- 
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] #18456: HttpRequest.get_full_path does not escape # sign in the url

[Django]

#18456: HttpRequest.get_full_path does not escape # sign in the url
-+-
 Reporter:  vlad.shcherbina@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by garrison):

 * cc: jim@… (added)


Comment:

 I have always found {{{request.get_full_path()}}} to be less than useful
 when dealing with tricky corner cases.  It doesn't escape anything itself,
 but if you escape its output, it also escapes the '{{{?}}}' used to
 assemble the path and the query string:

 {{{

 >>> from django.http import HttpRequest
 >>> from django.utils.http import urlquote
 >>> request = HttpRequest()
 >>> request.path = '/'
 >>> request.META['QUERY_STRING'] = 'q=a'
 >>> request.get_full_path()
 '/?q=a'
 >>> urlquote(request.get_full_path())
 u'/%3Fq%3Da'
 }}}

 In cases involving both query strings and unicode characters in urls, I
 have found that it is best simply to avoid {{{request.get_full_path()}}}
 altogether.  Instead, in my own projects I
 [https://code.ductus.us/ticket/32#comment:3 have defined a method] called
 {{{request.get_escaped_full_path()}}} as follows:

 {{{
 def get_escaped_full_path(self):
 return '%s%s' % (iri_to_uri(urlquote(self.path)),
 self.META.get('QUERY_STRING', '') and ('?' +
 iri_to_uri(self.META.get('QUERY_STRING', ''))) or '')
 }}}

 This turns out to be much more predictable (and useful).

-- 
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] #18627: Remove django-core uses of Model pre_init and post_init

[Django]

#18627: Remove django-core uses of Model pre_init and post_init
-+-
   Reporter:  jdunck |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  1.4
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 GenericForeignKey and ImageField use pre_init and post_init - signals
 which are fired on each model construction.

 The signal handling code is heavy relative to plain function dispatch, and
 is optimized for the zero-handler case.   It's unfortunate that Django
 ships with these signals being used, as it could instead use an internal
 hook for the needed initialization, and this approach would be faster.

 I'm working on a patch to switch to a more direct hook (which any field
 could use instead of pre/post_init).

 See also:
 
https://groups.google.com/forum/?fromgroups#!search/pre_init$2Fpost_init$20vs.$20performance
 /django-developers/GNQsvs8X9Gc/cegjyELUZt8J

 (Marking triage accepted since discussed and +1'd by some core folks.)

-- 
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] #15084: Unnecessary imports lead to ImportError

[Django]

#15084: Unnecessary imports lead to ImportError
--+
 Reporter:  vanschelven   |Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ptone):

 While I agree the right solution is to use the lazy translation, I believe
 this problem may be solved by the app-loading branch if it lands
 (hopefully for 1.5) as it will have imported all apps even earlier in
 Django's startup process.

 https://github.com/ptone/django/blob/app-
 loading/django/utils/translation/trans_real.py#L150

-- 
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] #18625: Docs contain examples that use old-style {% url %} syntax

[Django]

#18625: Docs contain examples that use old-style {% url %} syntax
-+
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by russellm):

 No, this should *not* be ported back to 1.4. In 1.4, the old style syntax
 was still the correct default; the new style syntax was an opt-in. If we
 were to use the new style syntax in the 1.4 docs, we'd have to explain the
 change every time the url tag was used.

-- 
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] #18625: Docs contain examples that use old-style {% url %} syntax

[Django]

#18625: Docs contain examples that use old-style {% url %} syntax
-+
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by aastrand):

 I think this should be backported to 1.4.

-- 
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] #17932: Test suite fails to run under Oracle

[Django]

#17932: Test suite fails to run under Oracle
-+
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 Anssi Kääriäinen ):

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


Comment:

 In [34340517fc2ac324114791d784502de2a4780757]:
 {{{
 #!CommitTicketReference repository=""
 revision="34340517fc2ac324114791d784502de2a4780757"
 Avoid using a column named "date" in tests

 Oracle can have problems with such columns. Fixed #17932 again.
 Thanks to Vinay Sajip for the report.
 }}}

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

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

[django/django] 343405: Avoid using a column named "date" in tests

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 34340517fc2ac324114791d784502de2a4780757
  
https://github.com/django/django/commit/34340517fc2ac324114791d784502de2a4780757
  Author: Anssi Kääriäinen 
  Date:   2012-07-15 (Sun, 15 Jul 2012)

  Changed paths:
M tests/regressiontests/admin_changelist/models.py

  Log Message:
  ---
  Avoid using a column named "date" in tests

Oracle can have problems with such columns. Fixed #17932 again.
Thanks to Vinay Sajip for the report.



-- 
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] #18626: Lack of scaping on howto / initial data

[Django]

#18626: Lack of scaping on howto / initial data
--+
 Reporter:  deniscostadsc@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  1.4
 Severity:  Normal| Resolution:  fixed
 Keywords:  Typo, Documentation   |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [bf9d5eff4cd74ffc8fcd1f610587e5ad00dc7f3f]:
 {{{
 #!CommitTicketReference repository=""
 revision="bf9d5eff4cd74ffc8fcd1f610587e5ad00dc7f3f"
 Fixed #18626 -- rst syntax collision.
 }}}

-- 
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/django] bf9d5e: Fixed #18626 -- rst syntax collision.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bf9d5eff4cd74ffc8fcd1f610587e5ad00dc7f3f
  
https://github.com/django/django/commit/bf9d5eff4cd74ffc8fcd1f610587e5ad00dc7f3f
  Author: Aymeric Augustin 
  Date:   2012-07-15 (Sun, 15 Jul 2012)

  Changed paths:
M docs/howto/initial-data.txt

  Log Message:
  ---
  Fixed #18626 -- rst syntax collision.



-- 
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] #18625: Docs contain examples that use old-style {% url %} syntax

[Django]

#18625: Docs contain examples that use old-style {% url %} syntax
-+
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by aaugustin):

 The audit was performed with a search for `\{% url [^'"]` in the docs
 source tree.

-- 
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] #18625: Docs contain examples that use old-style {% url %} syntax

[Django]

#18625: Docs contain examples that use old-style {% url %} syntax
-+
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Aymeric Augustin ):

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


Comment:

 In [fb46f243b4c48ab42ed2f33a2636f7c33f5861a9]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb46f243b4c48ab42ed2f33a2636f7c33f5861a9"
 Fixed #18625 -- Removed old-style use of url tag

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

[django/django] fb46f2: Fixed #18625 -- Removed old-style use of url tag

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fb46f243b4c48ab42ed2f33a2636f7c33f5861a9
  
https://github.com/django/django/commit/fb46f243b4c48ab42ed2f33a2636f7c33f5861a9
  Author: Aymeric Augustin 
  Date:   2012-07-15 (Sun, 15 Jul 2012)

  Changed paths:
M docs/ref/contrib/comments/index.txt
M docs/topics/http/urls.txt
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Fixed #18625 -- Removed old-style use of url tag

from the documentation.



-- 
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] #18414: queryset.exists() returns False when queryset is distinct and sliced

[Django]

#18414: queryset.exists() returns False when queryset is distinct and sliced
-+-
 Reporter:  bitrut   |Owner:  err
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 The pull request doesn't seem to do what Luke asked - it disallows the
 usage in any filtered situation, not just in conjunction with .distinct().
 It seems likely there are users relying on this currently.

 As for fixing the distinct() + limit + .exists() - it should be done by
 not doing select distinct(1) but instead select distinct {normal select
 fields} instead. I wonder if this would be straightforward to do?

-- 
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] #17856: Pass "obj" parameter to get_inline_instances

[Django]

#17856: Pass "obj" parameter to get_inline_instances
---+
 Reporter:  ybon   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by aaugustin):

 Pull requests are a accepted as well as patches.

-- 
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] #18478: Field.get_default will stringify everything that isn't a callable

[Django]

#18478: Field.get_default will stringify everything that isn't a callable
--+
 Reporter:  enrico|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  1.4
 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 aaugustin):

 * status:  closed => reopened
 * resolution:  duplicate =>
 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 Well, it took me a bit of time to find it, and I wasn't aware of this
 reason :)

 Accepting as a documentation 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] #17756: GeoDjango missing pyspatialite support

[Django]

#17756: GeoDjango missing pyspatialite support
-+
 Reporter:  danols   |Owner:  danols
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+

Comment (by akaariai):

 I tested the pull request 198 with pyspatialite on Ubuntu 12.04. What I
 did:
 {{{
 sudo apt-get install libgeos-dev
 sudo pip install pyspatialite
 ./runtests --settings=test_spatialite.py gis
 }}}
 Result was a core dump. Output (but not the actual dump) attached.

 Of course, I can't apply the PR as the above issue needs some resolution
 first.

 Additionally, please check the install.txt changes for whitespace errors,
 lines longer than 80 chars and use spaces instead of tabs.

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