Re: [Django] #16851: Accessing a forms field value in a template

[Django]

#16851: Accessing a forms field value in a template
---+--
 Reporter:  from_a_far@…   |Owner:  yasar11732
 Type:  Uncategorized  |   Status:  assigned
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 aaugustin):

 * stage:  Ready for checkin => Accepted


Comment:

 See #16758 - same comment. Also, note that you don't need to add yourself
 in Cc explicitly. If you've contributed to a ticket (written a comment,
 uploaded a patch...) Trac will always notify you of updates.

-- 
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] #16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional warning.

[Django]

#16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional 
warning.
-+-
 Reporter:  cyclops  |Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
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 aaugustin):

 * stage:  Ready for checkin => Accepted


Comment:

 Please don't mark your own patches as RFC — the rule is that patches must
 be reviewed by someone who isn't the author. For more information see the
 contributing guide in the docs.

 Documentation patches are reviewed on a regular basis, so don't worry,
 your patch will get attention eventually.

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

[Django]

#16955: Querying on the reverse of a FK with the wrong class silently returns 
bad
data
-+-
 Reporter:  jdunck   |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:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bpeschier):

 * stage:  Unreviewed => Accepted


Comment:

 Indeed, when using a Foo with an id also available in Author:
 {{{
 >>> foo2 = Foo.objects.create(pk=1)
 >>> Author.objects.filter(books=foo2)
 []
 }}}

-- 
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] #16933: Make it more obvious on screen which version of the doc is being viewed

[Django]

#16933: Make it more obvious on screen which version of the doc is being viewed
-+-
 Reporter:  julien   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Djangoproject.com|   Resolution:
  Web site   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by julien):

 And #16954 was another one...

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

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

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

[Django]

#9025: Nested Inline Support in Admin
-+-
 Reporter:  pixelcort|Owner:  nobody
 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
-+-
Changes (by danny.adair@…):

 * cc: danny.adair@… (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.

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

[Django]

#16955: Querying on the reverse of a FK with the wrong class silently returns 
bad
data
-+-
   Reporter:  jdunck |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.3
  layer (models, ORM)|   Keywords:
   Severity:  Normal |  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 {{{
 class Author(Model):
 pass

 class Book(Model):
 author = ForeignKey(Author, related_name='books')

 class Foo(Model):
 pass

 >>> a = Author.objects.create()
 >>> b  = Book.objects.create(author=a)
 >>> foo = Foo.objects.create(pk=999)
 >>> Author.objects.filter(books=foo)
 []
 }}}

 I would expect this to throw an exception because a Foo is not a Book.
 Instead, the Foo is coerced to its ID, which is then used as the PK for
 the reverse query.

 This also affects ManyToManyField with through (effectively a reverse FK).

-- 
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] #16948: Django DB backends hid information in database exceptions

[Django]

#16948: Django DB backends hid information in database exceptions
-+-
 Reporter:  jamesh   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  SVN
  (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
-+-
Changes (by jamesh):

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


Comment:

 and of course, I meant issubclass() rather than isinstance() in the code
 snippet in the initial comment.

-- 
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] #16954: https://docs.djangoproject.com/en/dev/intro/tutorial03/

[Django]

#16954: https://docs.djangoproject.com/en/dev/intro/tutorial03/
---+--
 Reporter:  tcornish@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  invalid
 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 Alex):

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


Comment:

 You're reading the documentation for the development version of Django,
 but using an older DJango (probably 1.3), please follow the documentation
 for the version of Django you're using.

-- 
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] #16954: https://docs.djangoproject.com/en/dev/intro/tutorial03/

[Django]

#16954: https://docs.djangoproject.com/en/dev/intro/tutorial03/
---+
 Reporter:  tcornish@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I was rolling along with the tutorial when it suddenly broke.  I had to
 change my url.py(s) from

 from django.conf.urls import patterns, include, url

 to

 from django.conf.urls.defaults import patterns, include, url

 to get things working again -- typo?

-- 
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] #16519: mimetype used with HttpResponse should be deprecated

[Django]

#16519: mimetype used with HttpResponse should be deprecated
-+-
 Reporter:  PaulM|Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  1.3
 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
-+-

Comment (by ramiro):

 Replying to [comment:5 yasar11732]:
 > I am new to contributing, and I shoud ask if I should fix contrib
 packages too. I mean replacing mimetype with content_type where needed?

 If you are talking about `django.contrib.*` then the answer is yes. Thanks
 for looking at 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] #16519: mimetype used with HttpResponse should be deprecated

[Django]

#16519: mimetype used with HttpResponse should be deprecated
-+-
 Reporter:  PaulM|Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  1.3
 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 yasar11732):

 * cc: yasar11732 (added)


Comment:

 Ok. A patch would be available in couple of days I guess. I am excited as
 this will be my first actual contrib to 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] #16519: mimetype used with HttpResponse should be deprecated

[Django]

#16519: mimetype used with HttpResponse should be deprecated
-+-
 Reporter:  PaulM|Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  1.3
 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
-+-

Comment (by PaulM):

 Yes, you'll need to fix it everywhere it occurs in the Django codebase,
 including the tests. You'll also probably need to write some new tests. If
 you swap the order of mimetype and content_type in the definition, the
 functions that are using mimetype as a positional argument will transition
 more easily.

-- 
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] #16851: Accessing a forms field value in a template

[Django]

#16851: Accessing a forms field value in a template
-+-
 Reporter:  from_a_far@… |Owner:
 Type:  Uncategorized|  yasar11732
Component:  Documentation|   Status:  assigned
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by yasar11732):

 * cc: yasar11732 (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] #16851: Accessing a forms field value in a template

[Django]

#16851: Accessing a forms field value in a template
-+-
 Reporter:  from_a_far@… |Owner:
 Type:  Uncategorized|  yasar11732
Component:  Documentation|   Status:  assigned
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by yasar11732):

 * cc: yasar11732 (removed)


-- 
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] #16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional warning.

[Django]

#16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional 
warning.
-+-
 Reporter:  cyclops  |Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
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 yasar11732):

 * cc: yasar11732 (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] #1908: Having an app name the same as project name breaks manage.py ( unable to import projectname.settings )

[Django]

#1908: Having an app name the same as project name breaks manage.py ( unable to
import projectname.settings )
-+-
 Reporter:  simon@…  |Owner:  adrian
 Type:  Bug  |   Status:  reopened
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  1|
-+-
Changes (by yasar11732):

 * ui_ux:  0 => 1
 * easy:  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] #1908: Having an app name the same as project name breaks manage.py ( unable to import projectname.settings )

[Django]

#1908: Having an app name the same as project name breaks manage.py ( unable to
import projectname.settings )
-+-
 Reporter:  simon@…  |Owner:  adrian
 Type:  Bug  |   Status:  reopened
Component:  Core (Management |  Version:  SVN
  commands)  |   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 yasar11732):

 * cc: yasar11732 (added)
 * ui_ux:   => 0
 * easy:   => 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] #16519: mimetype used with HttpResponse should be deprecated

[Django]

#16519: mimetype used with HttpResponse should be deprecated
-+-
 Reporter:  PaulM|Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  1.3
 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
-+-

Comment (by yasar11732):

 I am new to contributing, and I shoud ask if I should fix contrib packages
 too. I mean replacing mimetype with content_type where needed?

-- 
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] #16519: mimetype used with HttpResponse should be deprecated

[Django]

#16519: mimetype used with HttpResponse should be deprecated
-+-
 Reporter:  PaulM|Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  1.3
 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 yasar11732):

 * status:  new => assigned
 * owner:   => yasar11732


-- 
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] #16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional warning.

[Django]

#16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional 
warning.
-+-
 Reporter:  cyclops  |Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
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 yasar11732):

 * has_patch:  0 => 1
 * 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] #16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional warning.

[Django]

#16758: Documentation for TEMPLATE_CONTEXT_PROCESSORS could use additional 
warning.
-+-
 Reporter:  cyclops  |Owner:
 Type:   |  yasar11732
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.3
 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 yasar11732):

 * owner:  nobody => yasar11732
 * status:  new => assigned


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

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

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

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
 Reporter:  Manfred Wassmann |Owner:  jgelens
   |   Status:  assigned
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  dceu2011 |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jgelens):

 * 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] #16851: Accessing a forms field value in a template

[Django]

#16851: Accessing a forms field value in a template
-+-
 Reporter:  from_a_far@… |Owner:
 Type:  Uncategorized|  yasar11732
Component:  Documentation|   Status:  assigned
 Severity:  Normal   |  Version:  1.3
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by yasar11732):

 * has_patch:  0 => 1
 * 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] #16851: Accessing a forms field value in a template

[Django]

#16851: Accessing a forms field value in a template
---+--
 Reporter:  from_a_far@…   |Owner:  yasar11732
 Type:  Uncategorized  |   Status:  assigned
Component:  Documentation  |  Version:  1.3
 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 yasar11732):

 * owner:  nobody => yasar11732
 * cc: yasar11732 (added)
 * status:  new => assigned


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

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

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

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
 Reporter:  Manfred Wassmann |Owner:  jgelens
   |   Status:  assigned
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  dceu2011 |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by jgelens):

 * needs_better_patch:  1 => 0


Comment:

 Added a new version of the patch.

-- 
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] #16945: Extend LazyObject to accept constructor parameters

[Django]

#16945: Extend LazyObject to accept constructor parameters
--+--
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:  1.3
 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
--+--

Comment (by mitar):

 It is in utils.functional? But probably it was not meant to be used
 outside. But it is one "batter included" which developers could use/reuse.

-- 
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] #8060: Admin Inlines do not respect user permissions

[Django]

#8060: Admin Inlines do not respect user permissions
-+-
 Reporter:  p.patruno@…  |Owner:  sjaensch
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  inlines User | Triage Stage:  Accepted
  authentication |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by sjaensch):

 * needs_better_patch:  1 => 0


Comment:

 I changed the GitHub repository as requested in the IRC channel. There is
 now a separate branch that contains all changes for this issue:
 https://github.com/sjaensch/django/tree/admin_inline_perm. I'll
 periodically rebase the branch.
 I also added a release note as suggested by carljm. I'm not really happy
 about the wording, maybe a native speaker could check it? I also feels
 this should be documented in the admin documentation. I'll work on that
 tomorrow.

 If anybody can try out the patch, that would be great. Django's testsuite
 does not produce any failures.

-- 
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] #16945: Extend LazyObject to accept constructor parameters

[Django]

#16945: Extend LazyObject to accept constructor parameters
--+--
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:  1.3
 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
--+--

Comment (by Alex):

 Is LazyObject even part of the public API?

-- 
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] #16945: Extend LazyObject to accept constructor parameters

[Django]

#16945: Extend LazyObject to accept constructor parameters
--+--
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Core (Other)  |  Version:  1.3
 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 mitar):

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


-- 
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] #16945: Extend LazyObject to accept constructor parameters

[Django]

#16945: Extend LazyObject to accept constructor parameters
--+--
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  1.3
 Severity:  Normal|   Resolution:  needsinfo
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by mitar):

 Oh, sorry. Currently it is possible only to use LazyObject on classes
 where constructors do not take arguments. But if constructors do take
 arguments, then above version of LazyObject is needed.

 I have come above this problem in my Django project where I have one class
 for URL dispatching/manipulating and it cannot yet be created at load time
 (because URLs are not loaded). So using LazyObject was an easy way to
 solve the problem. But my class requires some constructor arguments. So I
 had to extend LazyObject.

 So this addition is not directly needed for Django, but if we ship such
 utility class, we can make it a bit more generic for other its uses when
 developing with Django (so that you do not have to reimplement).

 Example is then:

 {{{
 class LazyHref(lazy.LazyObject):
 def _setup(self):
 self._wrapped = web.href.Href(*self._wrapped_args,
 **self._wrapped_kwargs)
 }}}

-- 
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] #16952: Django installed in different directory than stated.

[Django]

#16952: Django installed in different directory than stated.
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  duplicate
 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 bpeschier):

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


Comment:

 This was already observed and fixed in #16287. The development version of
 the docs already contains the updated information.

-- 
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] #16952: Django installed in different directory than stated.

[Django]

#16952: Django installed in different directory than stated.
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I downloaded Django-1.3.1.tar.gz, extracted it, then in the extracted
 directory Django-1.3.1 executed "sudo python setup.py install" as directed
 by the document https://docs.djangoproject.com/en/1.3/topics/install
 /#installing-official-release (item 4 under "Installing an official
 release").  The directory "django" and file "Django-1.3.1.egg-info" were
 created under /usr/local/lib/python2.6/dist-packages, not the site-
 packages directory as stated by the documentation.  The My OS is Linux
 Mint.

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

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

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

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
 Reporter:  Manfred Wassmann |Owner:  jgelens
   |   Status:  assigned
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  dceu2011 |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by jgelens):

 I'll update it to match the current trunk in a couple of hours. It will be
 great if you could apply the patch soon after that, as it seems this part
 of the code is changing rapidly.

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

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

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

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|  Owner:  jgelens
  Wassmann | Status:  assigned
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  dceu2011
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-
Changes (by jacob):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Sadly the patch doesn't apply any more; bumping back to accepted.

 I'm really sorry we dallied so long that the patch grew stale. I'll try to
 get it updated myself but if someone wants to save me a bit of time and
 update the patch that'd make me very happy.

-- 
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] #11333: ORA-01830 date format picture ends before converting entire input

[Django]

#11333: ORA-01830 date format picture ends before converting entire input
-+-
   Reporter:  jtiai  |  Owner:  nobody
   Type: | Status:  closed
  Uncategorized  |  Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution:  wontfix|   Keywords:  oracle date formats
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by jtiai):

 Thanks for the info. Though it doesn't solve problem when you update non-
 date fields (Django updates still whole record) problem still exists.

 I agree with ikelly, it's better to do it right than trying to hack around
 someway. Though it could be useful to mention that workaround in official
 docs as well.

-- 
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] #16951: Example for dumpdata of permissions

[Django]

#16951: Example for dumpdata of permissions
---+---
 Reporter:  googol |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Documentation
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+---
 Would be great if you could provide an example for dumpdata of permissions
 at:

 https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-
 option---natural

 e.g.: ./manage.py dumpdata contenttypes auth >fixtures/permission.json
 --indent 4 --natural

-- 
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] #11707: limit_choices_to on a ForeignKey can render duplicate options in formfield

[Django]

#11707: limit_choices_to on a ForeignKey can render duplicate options in 
formfield
-+-
   Reporter: |  Owner:  charstring
  Chris.Wesseling@…  | Status:  new
   Type:  Bug|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  ForeingKey
 Resolution: |  limit_choices_to, dceu2011
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by jacob):

 Discussion from IRC:

 {{{
 [02:24am] I don't see a test case here that emulates the failures seen
 when the previous (committed then reverted) approach. Am I just missing
 it?
 [09:26am] jacobkm: I also can't say I'm particularly happy with the patch,
 particularly iterating over the qs in distinct_choices().
 [09:26am] chars:It's pretty hard to test for me. It's a case where
 Postgres can't compare the values.
 [09:26am] chars: So it can't test for uniqueness
 [09:26am] jacobkm: It also needs additions to documentation to mention
 that Q() objects are acceptable in limit_choices_to.
 }}}

-- 
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] #16763: code.djangoproject.com won't stop emailing me (doesn't abide by cc/reporter/etc)

[Django]

#16763: code.djangoproject.com won't stop emailing me (doesn't abide by
cc/reporter/etc)
-+-
   Reporter:  ferringb   |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Djangoproject.com
Version: |  Web site
 Resolution:  wontfix|   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
-+-

Comment (by RaceCondition):

 As my similar issue was marked as dupe, please manually remove me from the
 CC of https://code.djangoproject.com/ticket/16950 as I'm having the same
 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] #16950: Unwanted notifications from code.djangoproject.com

[Django]

#16950: Unwanted notifications from code.djangoproject.com
-+-
   Reporter: |  Owner:  nobody
  RaceCondition  | Status:  closed
   Type:  Bug|  Component:  Djangoproject.com
  Milestone: |  Web site
Version:  1.3|   Severity:  Normal
 Resolution:  duplicate  |   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 Alex):

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


Comment:

 Dupe of #16763

-- 
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] #16950: Unwanted notifications from code.djangoproject.com

[Django]

#16950: Unwanted notifications from code.djangoproject.com
---+
 Reporter:  RaceCondition  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Djangoproject.com Web site
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
 I keep getting nofications about an issue whose CC list I'm not in.

 The URL of the issue is https://code.djangoproject.com/ticket/9025.
 It should be possible to deduce my e-mail address from there, as I do not
 want to disclose it here publicly.

 Possibly related to/caused by http://trac.edgewall.org/ticket/8597

 What I ask is that somebody manually remove this CC entry from the SQLite
 database that Trac is using.

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

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

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

[Django]

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

Comment (by aaugustin):

 Replying to [comment:70 RaceCondition]:
 > Why do I keep receiving e-mails about this ticket? I've removed myself
 from CC. Please fix this issue, whoever is responsible for it.

 See #16763.

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

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

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

[Django]

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

Comment (by jacob):

 RaceCondition: sorry, it's a "feature" of Trac. Let me know which email
 you're getting emails to and I'll take care of it. You can post a comment
 here or email me at `jacob at jacobian dot org`.

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

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

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

[Django]

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

Comment (by RaceCondition):

 Why do I keep receiving e-mails about this ticket? I've removed myself
 from CC. Please fix this issue, whoever is responsible for 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] #9275: ORA-01830 date format picture ends before converting entire input... admin

[Django]

#9275: ORA-01830 date format picture ends before converting entire input... 
admin
-+-
   Reporter:  hollerith  |  Owner:  nobody
   Type: | Status:  closed
  Uncategorized  |  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.0|   Severity:  Normal
 Resolution:  fixed  |   Keywords:  oracle date formats
   Triage Stage: |  Has patch:  1
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by anurag.chourasia@…):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 If the issue still persists and If the model field is a DateTimeField and
 the Database field is of DATE Type then you could try this to overcome
 this error

 Look for the statement where you are updating the Date field. Over there,
 replace the microseonds to Zero and Oracle will start treating it
 gracefully.

 For example, if you model field is called date_field

 and if you are updating it as
 date_field=datetime.datetime.now()

 then change it to
 date_field=datetime.datetime.now().replace(microsecond=0)

 And that will solve the issue

 Regards
 Guddu

-- 
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] #11333: ORA-01830 date format picture ends before converting entire input

[Django]

#11333: ORA-01830 date format picture ends before converting entire input
-+-
   Reporter:  jtiai  |  Owner:  nobody
   Type: | Status:  closed
  Uncategorized  |  Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution:  wontfix|   Keywords:  oracle date formats
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by anurag.chourasia@…):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 If the model field is a DateTimeField and the Database field is of DATE
 Type then you could try this to overcome this error

 Look for the statement where you are updating the Date field. Over there,
 replace the microseonds to Zero and Oracle will start treating it
 gracefully.

 For example, if you model field is called date_field

 and if you are updating it as
 date_field=datetime.datetime.now()

 then change it to
 date_field=datetime.datetime.now().replace(microsecond=0)

 And that will solve the issue

 Regards
 Guddu

-- 
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] #16949: "different" word repeated twice

[Django]

#16949: "different" word repeated twice
-+-
   Reporter:  jgomo3 |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution:  fixed  |   Keywords:  geodjango
   Triage Stage:  Ready for  |  Has patch:  0
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by julien):

 Thanks charettes for uploading a patch too!

-- 
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] #14319: Add signals test_setup and test_teardown to Django test suite runner Options

[Django]

#14319: Add signals test_setup and test_teardown to Django test suite runner
Options
---+---
   Reporter:  jsdalton |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:  1.4  |  Component:  Testing framework
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:  signals
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
Changes (by jsdalton):

 * needs_better_patch:  1 => 0


Comment:

 Replying to [comment:6 ptone]:
 > It is unclear why the patch is removing the global setup and tear down
 calls setup_test_environment and  teardown_test_environment

 I mentioned this up in the ticket description:

 "The second most significant change is that the django.test.utils
 functions setup_test_environment() and tear_down_environment() calls are
 executed by connecting to the signal rather than being called directly
 from the methods of the test runner. This serves as a way to test that the
 signals are being fired, as Django tests will fail if those two functions
 do not execute. (Thanks to Russell Keith-Magee for this suggestion)."

 Basically those functions are hooked to the new global setup/teardown
 signals here rather than being called directly. Makes sense?

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

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

[Changeset] r16911 - django/trunk/docs/ref/contrib/gis

[noreply]

Author: julien
Date: 2011-09-28 07:00:43 -0700 (Wed, 28 Sep 2011)
New Revision: 16911

Modified:
   django/trunk/docs/ref/contrib/gis/tutorial.txt
Log:
Fixed #16949 -- Fixed a small typo in the GIS tutorial and also made some minor 
PEP8 fixes and added some code-block directives while I was at it. Thanks to 
jgomo3 for the report.

Modified: django/trunk/docs/ref/contrib/gis/tutorial.txt
===
--- django/trunk/docs/ref/contrib/gis/tutorial.txt  2011-09-28 02:26:12 UTC 
(rev 16910)
+++ django/trunk/docs/ref/contrib/gis/tutorial.txt  2011-09-28 14:00:43 UTC 
(rev 16911)
@@ -7,7 +7,8 @@
 
 GeoDjango is an add-on for Django that turns it into a world-class geographic
 Web framework.  GeoDjango strives to make it as simple as possible to create
-geographic Web applications, like location-based services.  Some features 
include:
+geographic Web applications, like location-based services.  Some features
+include:
 
 * Django model fields for `OGC`_ geometries.
 * Extensions to Django's ORM for the querying and manipulation of spatial data.
@@ -16,8 +17,8 @@
 * Editing of geometry fields inside the admin.
 
 This tutorial assumes a familiarity with Django; thus, if you're brand new to
-Django please read through the :doc:`regular tutorial ` to 
introduce
-yourself with basic Django concepts.
+Django please read through the :doc:`regular tutorial ` to
+introduce yourself with basic Django concepts.
 
 .. note::
 
@@ -52,16 +53,21 @@
 
 First, a spatial database needs to be created for our project.  If using
 PostgreSQL and PostGIS, then the following commands will
-create the database from a :ref:`spatial database template 
`::
+create the database from a :ref:`spatial database template
+`:
 
+.. code-block:: bash
+
 $ createdb -T template_postgis geodjango
 
 .. note::
 
 This command must be issued by a database user that has permissions to
 create a database.  Here is an example set of commands to create such
-a user::
+a user:
 
+.. code-block:: bash
+
 $ sudo su - postgres
 $ createuser --createdb geo
 $ exit
@@ -76,20 +82,25 @@
 Create GeoDjango Project
 
 
-Use the ``django-admin.py`` script like normal to create a ``geodjango`` 
project::
+Use the ``django-admin.py`` script like normal to create a ``geodjango``
+project:
 
+.. code-block:: bash
+
 $ django-admin.py startproject geodjango
 
 With the project initialized, now create a ``world`` Django application within
-the ``geodjango`` project::
+the ``geodjango`` project:
 
+.. code-block:: bash
+
 $ cd geodjango
 $ python manage.py startapp world
 
 Configure ``settings.py``
 -
 
-The ``geodjango`` project settings are stored in the ``settings.py`` file.  
Edit
+The ``geodjango`` project settings are stored in the ``settings.py`` file. Edit
 the database connection settings appropriately::
 
 DATABASES = {
@@ -126,10 +137,12 @@
 World Borders
 -
 
-The world borders data is available in this `zip file`__.  Create a data 
directory
-in the ``world`` application, download the world borders data, and unzip.
-On GNU/Linux platforms the following commands should do it::
+The world borders data is available in this `zip file`__.  Create a data
+directory in the ``world`` application, download the world borders data, and
+unzip. On GNU/Linux platforms the following commands should do it:
 
+.. code-block:: bash
+
 $ mkdir world/data
 $ cd world/data
 $ wget http://thematicmapping.org/downloads/TM_WORLD_BORDERS-0.3.zip
@@ -138,7 +151,8 @@
 
 The world borders ZIP file contains a set of data files collectively known as
 an `ESRI Shapefile`__, one of the most popular geospatial data formats.  When
-unzipped the world borders data set includes files with the following 
extensions:
+unzipped the world borders data set includes files with the following
+extensions:
 
 * ``.shp``: Holds the vector data for the world borders geometries.
 * ``.shx``: Spatial index file for geometries stored in the ``.shp``.
@@ -154,8 +168,10 @@
 ---
 
 The GDAL ``ogrinfo`` utility is excellent for examining metadata about
-shapefiles (or other vector data sources)::
+shapefiles (or other vector data sources):
 
+.. code-block:: bash
+
 $ ogrinfo world/data/TM_WORLD_BORDERS-0.3.shp
 INFO: Open of `world/data/TM_WORLD_BORDERS-0.3.shp'
   using driver `ESRI Shapefile' successful.
@@ -163,8 +179,10 @@
 
 Here ``ogrinfo`` is telling us that the shapefile has one layer, and that
 layer contains polygon data.  To find out more we'll specify the layer name
-and use the ``-so`` option to get only important summary information::
+and use the ``-so`` option to get only important summary information:
 
+.. code-block:: bash
+
 $ ogrinfo -so world/data/TM_WORLD_BORDERS-0.3.shp TM_WORLD_BORDERS-0.3
 INFO: Open of `world/data/TM_WORLD_BORD

Re: [Django] #16949: "different" word repeated twice

[Django]

#16949: "different" word repeated twice
-+-
   Reporter:  jgomo3 |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution:  fixed  |   Keywords:  geodjango
   Triage Stage:  Ready for  |  Has patch:  0
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by julien):

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


Comment:

 In [16911]:
 {{{
 #!CommitTicketReference repository="" revision="16911"
 Fixed #16949 -- Fixed a small typo in the GIS tutorial and also made some
 minor PEP8 fixes and added some code-block directives while I was at it.
 Thanks to jgomo3 for the report.
 }}}

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

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

Re: [Django] #16949: "different" word repeated twice

[Django]

#16949: "different" word repeated twice
-+-
   Reporter:  jgomo3 |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  geodjango
   Triage Stage:  Ready for  |  Has patch:  0
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by julien):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Ready for checkin
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Well spotted, thanks!

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

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

Re: [Django] #15649: Doc buliding fails with: DjangoHTMLTranslator instance has no attribute '_table_row_index'

[Django]

#15649: Doc buliding fails with: DjangoHTMLTranslator instance has no attribute
'_table_row_index'
-+---
   Reporter:  bmihelac   |  Owner:  nobody
   Type:  Uncategorized  | Status:  reopened
  Milestone: |  Component:  Documentation
Version:  SVN|   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 gavenkoa@…):

 * status:  closed => reopened
 * severity:   => Normal
 * type:   => Uncategorized
 * easy:   => 0
 * ui_ux:   => 0
 * resolution:  invalid =>


Comment:

 $ make html
 sphinx-build -b djangohtml -d _build/doctrees   . _build/html
 Running Sphinx v1.0.8
 loading pickled environment... not yet created
 building [djangohtml]: targets for 205 source files that are out of date
 updating environment: 205 added, 0 changed, 0 removed
 reading sources... [100%] topics/testing
 looking for now-outdated files... none found
 pickling environment... done
 checking consistency... done
 preparing documents... done
 writing output... [  7%] howto/custom-management-commands
 Exception occurred:
   File "/usr/lib/python2.6/site-
 packages/Sphinx-1.0.8-py2.6.egg/sphinx/writers/html.py", line 120, in
 visit_desc_parameter
 self.body.append(self.param_separator)
 AttributeError: DjangoHTMLTranslator instance has no attribute
 'param_separator'

-- 
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] #15802: Django stops functioning when the database (PostgreSQL) closes the connection

[Django]

#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-+-
   Reporter: |  Owner:  Honza_Kral
  Rick.van.Hattem@…  | Status:  reopened
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  database, postgres,
   Triage Stage:  Accepted   |  postgresql, connection, closed
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by dekkers):

 Replying to [comment:11 Honza_Kral]:
 > And does it occur then at every request or just once? If just once I
 consider that fine - we wouldn't want to hide the fact that something bad
 happened to the connection from the user.

 It happens at every request. With my patch I still get a DatabaseError in
 execute() once, but I agree that that is fine.

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

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

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

[Django]

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

Comment (by info.ksamuel@…):

 +1 but obviously not as easy as it sounds. Really improves usability
 though.

-- 
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] #16949: "different" word repeated twice

[Django]

#16949: "different" word repeated twice
---+---
 Reporter:  jgomo3 |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Documentation
  Version:  1.3|   Severity:  Normal
 Keywords:  geodjango  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+---
 "Importing Spatial Data

 ... There are many '''different different''' ways to import data in to a
 spatial database -- besides the tools included within GeoDjango, you may
 also use the following to populate your spatial database: ..."

 https://docs.djangoproject.com/en/1.3/ref/contrib/gis/tutorial/#importing-
 spatial-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.

Re: [Django] #16870: CSRF too strict when no referer is present

[Django]

#16870: CSRF too strict when no referer is present
--+--
   Reporter:  rtux|  Owner:  nobody
   Type:  Bug | Status:  closed
  Milestone:  |  Component:  contrib.csrf
Version:  1.3 |   Severity:  Normal
 Resolution:  wontfix |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+--

Comment (by lukeplant):

 For reference, this Firefox add-on looks like it implements the kind of
 referer blocking you need: https://addons.mozilla.org/en-US/firefox/addon
 /smart-referer/

 (I do not know if you are using Firefox or not).

-- 
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] #661: New function: batch save of objects would make for more efficient processing

[Django]

#661: New function: batch save of objects would make for more efficient
processing
---+--
   Reporter:  Lllama   |  Owner:  adrian
   Type:  enhancement  | Status:  closed
  Milestone:   |  Component:  Core (Other)
Version:   |   Severity:  normal
 Resolution:  wontfix  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  1|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+--
Changes (by kmtracey):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 Just a note, while this one was closed wontfix the request was made again
 in #7596 and that one was fixed.

-- 
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] #661: New function: batch save of objects would make for more efficient processing

[Django]

#661: New function: batch save of objects would make for more efficient
processing
--+
   Reporter:  Lllama  |  Owner:  adrian
   Type:  Bug | Status:  closed
  Milestone:  1.4 |  Component:  contrib.markup
Version:  1.3-beta|   Severity:  normal
 Resolution:  wontfix |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  1   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
Changes (by anonymous):

 * component:  Core (Other) => contrib.markup
 * version:   => 1.3-beta
 * easy:   => 1
 * milestone:   => 1.4
 * has_patch:  0 => 1
 * ui_ux:   => 0
 * type:  enhancement => Bug


-- 
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] #16776: jQuery.noConflict(false) in jquery.init.js leaks the admin jQuery into the global namespace

[Django]

#16776: jQuery.noConflict(false) in jquery.init.js leaks the admin jQuery into 
the
global namespace
-+-
   Reporter:  anonymous  |  Owner:
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  contrib.admin
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  jQuery admin
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * owner:  jezdez =>


Comment:

 Removing myself again since I simply don't know what problems cause r16415
 in detail to decide what's best.

-- 
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] #16776: jQuery.noConflict(false) in jquery.init.js leaks the admin jQuery into the global namespace

[Django]

#16776: jQuery.noConflict(false) in jquery.init.js leaks the admin jQuery into 
the
global namespace
-+-
   Reporter:  anonymous  |  Owner:  jezdez
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  contrib.admin
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  jQuery admin
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jezdez):

 Ah, another piece of the puzzle, this is what had in mind:
 http://groups.google.com/group/django-
 developers/browse_thread/thread/c91da363ef335629

-- 
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] #16674: Django's WSGI Handler should report exceptions to the start_response() callback

[Django]

#16674: Django's WSGI Handler should report exceptions to the start_response()
callback
-+--
   Reporter:  jamesh |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Milestone: |  Component:  Core (Other)
Version:  SVN|   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  |
-+--

Comment (by jamesh):

 For what it is worth, I haven't noticed any problems using the patch I
 attached to the bug report (both for normal Django error pages and the
 developer debug error page).

 The wsgiref module ignores the exc_info argument provided that the
 response headers haven't been sent (not a problem for Django, since it
 only calls start_response once).

 The same seems to be true for mod_wsgi:

 http://code.google.com/p/modwsgi/source/browse/mod_wsgi/mod_wsgi.c#2600

 And similar for Paste:

 https://bitbucket.org/ianb/paste/src/852439f67241/paste/httpserver.py#cl-153
 https://bitbucket.org/ianb/paste/src/852439f67241/paste/modpython.py#cl-176

 And Twisted:

 http://twistedmatrix.com/trac/browser/trunk/twisted/web/wsgi.py#L256

-- 
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] #16948: Django DB backends hid information in database exceptions

[Django]

#16948: Django DB backends hid information in database exceptions
---+--
 Reporter:  jamesh |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Database layer (models, ORM)
  Version:  SVN|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+--
 The Django DB backends replace the exceptions raised by the underlying
 adapter with standard ones from django.db.utils.

 I understand the reason for doing this (provide standard exceptions that
 calling code can catch), but it can lose information provided by those
 exceptions.  For example, the psycopg2 adapter exposes the SQL error code
 as a "code" attribute on exceptions, and this is lost.

 Perhaps using the same strategy as Storm would help: rather than catching
 the adapter's exceptions and re-raising equivalent standard ones, it
 patches the adapter's exceptions so that they subclass from the standard
 ones.  This could be done with a method like the following:

 {{{
 def install_exceptions(module):
 if not isinstance(module.DatabaseError,
 django.db.utils.DatabaseError):
 module.DatabaseError.__bases__ += (django.db.utils.DatabaseError,)
 if not isinstance(module.IntegrityError,
 django.db.utils.IntegrityError):
 module.IntegrityError.__bases__ +=
 (django.db.utils.IntegrityError,)
 }}}

 Once the adapter's exceptions have been patched it would no longer be
 necessary to wrap the adapter's cursors, since the standard cursor would
 raise exceptions that could be caught by generic code.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #16947: wrong ordering of a column with list_editable

[Django]

#16947: wrong ordering of a column with list_editable
--+---
   Reporter:  anonymous   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  contrib.admin
Version:  SVN |   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 makovick):

 * cc: makovick (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 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] #16947: wrong ordering of a column with list_editable

[Django]

#16947: wrong ordering of a column with list_editable
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  contrib.admin
  Version:  SVN|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+---
 When there are no ordering options specified in the request, the column
 with list_editable still behaves as if the table were sorted by the
 primary key. This causes the editable items being displayed in the wrong
 rows.

 Tested with SQLite. A simple testcase is here:

 
https://sites.google.com/site/makovick/junkyard/testcase.tar.gz?attredirects=0&d=1

 - http://localhost:8000/admin/testapp/configuration
 - login as admin/admin
 - see the Configuration table containing key/value pairs
 - key 'zzz' is paired with value '999' but after clicking on 'zzz' one can
 see there is '555' as a value

-- 
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] #7469: Provide a link for many-to-one relations in the admin interface

[Django]

#7469: Provide a link for many-to-one relations in the admin interface
-+-
   Reporter:  aeby   |  Owner:  nobody
   Type:  New| Status:  closed
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  link many-to-one
 Resolution:  duplicate  |  relation field admin interface
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
Changes (by julien):

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


Comment:

 Oops, wrong copy/paste. This is a dupe of #13165.

-- 
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] #7469: Provide a link for many-to-one relations in the admin interface

[Django]

#7469: Provide a link for many-to-one relations in the admin interface
-+-
   Reporter:  aeby   |  Owner:  nobody
   Type:  New| Status:  reopened
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  link many-to-one
 Resolution: |  relation field admin interface
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
Changes (by jezdez):

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


Comment:

 Seems like this was closed accidentally.

-- 
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] #16945: Extend LazyObject to accept constructor parameters

[Django]

#16945: Extend LazyObject to accept constructor parameters
---+--
   Reporter:  mitar|  Owner:  nobody
   Type:  New feature  | Status:  closed
  Milestone:   |  Component:  Core (Other)
Version:  1.3  |   Severity:  Normal
 Resolution:  needsinfo|   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 jezdez):

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


Comment:

 I don't exactly understand what this is useful for as the code example
 doesn't show how `_wrapped_args` and `_wrapped_kwargs` are used. Please
 provide a specific use case this would be useful for.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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.