date:20121024

Re: [Django] #19101: Non ascii chars in form cause Internal Server Error

2012-10-24 Thread Django

#19101: Non ascii chars in form cause Internal Server Error
-+-
 Reporter:  kristall |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  encoding | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19181: Document caveats about using DateQuerySet in templates when time zone support is enabled.

2012-10-24 Thread Django

#19181: Document caveats about using DateQuerySet in templates when time zone
support is enabled.
-+--
 Reporter:  wiliamsouza83@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  docs | 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:

 I still plan to fix this at some point, see #17260.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18169: NoReverseMatch silenced in template Variable

2012-10-24 Thread Django

#18169: NoReverseMatch silenced in template Variable
+
 Reporter:  jasisz  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Template system |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  template exception  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by d1ffuz0r):

 * cc: d1fffuz0r@… (added)
 * needs_tests:  1 => 0


Comment:

 Patch can't applied
 {{{
 (django)django|master⚡ ⇒ git apply 18169.2.patch
 error: patch failed: django/template/base.py:774
 error: django/template/base.py: patch does not apply
 }}}

 I made some improvements and tests for this patch in attached file.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19182: ModelAdmin.lookup_allowed should also check for ('fieldname', ClassName) syntax

2012-10-24 Thread Django

#19182: ModelAdmin.lookup_allowed should also check for ('fieldname', ClassName)
syntax
---+---
 Reporter:  gauss  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:  modeladmin lookup_allowed
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 Admin raises SuspiciousOperation on using complex query like
 {{{ghi__jkl__contains}}} in custom list filter described by
 {{{('fieldpath', ClassName )}}} syntax.

 {{{#!python
 class MyModelAdmin(ModelAdmin):
 ...
 list_filter = (
 'abc', 'def',
 ( 'ghi__jkl__contains', MyListFilter )
 )
 ...
 }}}

 Simple but ugly fix by replacing last line of
 {{{ModelAdmin.lookup_allowed}}} (around line 270 in
 contrib/admin/options.py):

 {{{#!diff
 clean_lookup = LOOKUP_SEP.join(parts)
 --- return clean_lookup in self.list_filter or clean_lookup ==
 self.date_hierarchy
 +++ return any([ ( clean_lookup == ( i[0] if isinstance(i, tuple)
 else i ) ) for i in self.list_filter ]) or clean_lookup ==
 self.date_hierarchy
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 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 ptone):

 No problem - that is why a test is always a great way to validate a bug
 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

2012-10-24 Thread Django

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by ptone):

 * severity:  Normal => Release blocker


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #17991: Prefetch_related fails with GenericRelation

2012-10-24 Thread Django

#17991: Prefetch_related fails with GenericRelation
-+-
 Reporter:  okke@…   |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:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by carmandrew@…):

 * needs_tests:  1 => 0


Comment:

 I ran into the same issue. There is a bug with the way that
 prefetch_related is handling GenericRelations where the
 GenericForeignKey's object_id is a different type than the primary key of
 the model it's pointing to. I've attached a test case.

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

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

Re: [Django] #19179: No mention of Multiiple Inheritance required for NamedUrlWizardView

2012-10-24 Thread Django

#19179: No mention of Multiiple Inheritance required for NamedUrlWizardView
-+-
 Reporter:  tom@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  SessionWizardView,   | Triage Stage:
  NamedUrlWizardView |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tom@…):

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


Comment:

 After looking at the code it's now clear that NamedUrlSessionWizard or
 NamedUrlCookieWizard should be used in place of NamedUrlWizard instead of
 inheriting from two classes.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19181: Document caveats about using DateQuerySet in templates when time zone support is enabled.

2012-10-24 Thread Django

#19181: Document caveats about using DateQuerySet in templates when time zone
support is enabled.
-+
 Reporter:  wiliamsouza83@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Documentation|Version:  1.4
 Severity:  Normal   |   Keywords:  docs
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Improve the the warning in
 
https://docs.djangoproject.com/en/dev/ref/models/querysets/#django.db.models.query.QuerySet.dates
 adding a example that when time zone settings.USE_TZ support is enabled
 and your time zone settings.TIME_ZONE is settled to America / Sao Paulo
 wich is UTC - 3 in BRT and UTC - 2 in BRST and DateQuerySet return "Oct.
 10, 2012, midnight" you will get "Oct. 9, 2012, 9, 00, 00". You should
 turn off local time when displaying DateQuerySet to avoid problems:

 {% load tz %}
 {% localtime off %}
 {% for month in date_list %}
 {{ month }}
 {% endfor %}
 {% endlocaltime %}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19180: Inaccurate documentation regarding "frozen docs"

2012-10-24 Thread Django

#19180: Inaccurate documentation regarding "frozen docs"
---+
 Reporter:  timo   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  master
 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 russellm):

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


Comment:

 Agreed - this is misleading. It was true(er) in the days of 0.9X, but it
 certainly isn't now. We shouldn't just delete it, though -- we should
 point out that we maintain different versions of the docs, one for each
 major release, so it's important to make sure you're looking at the right
 version of the docs, etc.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19180: Inaccurate documentation regarding "frozen docs"

2012-10-24 Thread Django

#19180: Inaccurate documentation regarding "frozen docs"
---+
 Reporter:  timo   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Doesn't seem accurate to me, but wanted to get a +1 before removing:

 {{{
 Documentation for a particular Django release is frozen once the version
 has been released officially. It remains a snapshot of the docs as of the
 moment of the release. We will make exceptions to this rule in
 the case of retroactive security updates or other such retroactive
 changes. Once documentation is frozen, we add a note to the top of each
 frozen document that says "These docs are frozen for Django version XXX"
 and links to the current version of that document.
 }}}

 https://docs.djangoproject.com/en/1.4/intro/whatsnext/

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19031: Using @override_settings doesn't override DATABASES in threads +SQLite

2012-10-24 Thread Django

#19031: Using @override_settings doesn't override DATABASES in threads +SQLite
---+
 Reporter:  jonash |Owner:  nobody
 Type:  Bug|   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:  1  |UI/UX:  0
---+

Comment (by jonash):

 It's not since then I either need to run the tests twice (with `:memory:`
 and a real database) or my test is not run at all.

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

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

[django/django] ce1eb3: Remove a case that is no longer reachable in encod...

2012-10-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ce1eb320e59b577a600eb84d7f423a1897be3576
  
https://github.com/django/django/commit/ce1eb320e59b577a600eb84d7f423a1897be3576
  Author: Alex Gaynor 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
M django/utils/encoding.py

  Log Message:
  ---
  Remove a case that is no longer reachable in encodings.py.

This case was originally designed to handle Exception's which didn't gracefully 
support coercing themselves to unicode. However, because it lives in the `else` 
case of `if hasattr(s, '__unicode__'):` we can be sure it's no longer reachable 
in djanog anymore, because since Python 2.5 exception has subclassed object, 
which means Exception objects always have an __unicode__ method.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #10554: Response.set_cookie should allow setting two cookies of the same name.

2012-10-24 Thread Django

#10554: Response.set_cookie should allow setting two cookies of the same name.
---+
 Reporter:  jdunck |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 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:  ccahoon => nobody
 * version:  1.0 => master


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #15098: SiteProfileNotAvailable needs silent_variable_failure=True

2012-10-24 Thread Django

#15098: SiteProfileNotAvailable needs silent_variable_failure=True
-+-
 Reporter:  tkolar   |Owner:  tkolar
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Ready for
  SiteProfileNotAvailable|  checkin
  silent_variable_failure|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by apollo13):

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


Comment:

 Django 1.5 will ship with a new method to add data to the user model and
 as such the current AUTH_PROFILE_MODULE is deprecated and will go away
 (including stuff like get_profile). As a result of the deprecation we
 won't fix any non critical bugs. Sry that we couldn't get this in earlier.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9471: Documentation Admin classes with raw_id_fields

2012-10-24 Thread Django

#9471: Documentation Admin classes with raw_id_fields
---+
 Reporter:  adroffne@… |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.0
 Severity:  Normal |   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
---+

Comment (by Tim Graham ):

 In [changeset:"baf1f1dcde1f318fdb6514eaa8497fc958aa69d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="baf1f1dcde1f318fdb6514eaa8497fc958aa69d3"
 [1.4.X] Fixed #9471 - Expanded ModelAdmin.raw_id_fields docs; thanks
 adroffne for the suggestion.

 Backport of da958eb209 from master
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] baf1f1: [1.4.X] Fixed #9471 - Expanded ModelAdmin.raw_id_f...

2012-10-24 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: baf1f1dcde1f318fdb6514eaa8497fc958aa69d3
  
https://github.com/django/django/commit/baf1f1dcde1f318fdb6514eaa8497fc958aa69d3
  Author: Tim Graham 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
A docs/ref/contrib/admin/_images/raw_id_fields.png
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  [1.4.X] Fixed #9471 - Expanded ModelAdmin.raw_id_fields docs; thanks adroffne 
for the suggestion.

Backport of da958eb209 from master



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9471: Documentation Admin classes with raw_id_fields

2012-10-24 Thread Django

#9471: Documentation Admin classes with raw_id_fields
---+
 Reporter:  adroffne@… |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.0
 Severity:  Normal |   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 Tim Graham ):

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


Comment:

 In [changeset:"da958eb2098372c20cc3aaf905777b1a8d3144eb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="da958eb2098372c20cc3aaf905777b1a8d3144eb"
 Fixed #9471 - Expanded ModelAdmin.raw_id_fields docs; thanks adroffne for
 the suggestion.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] da958e: Fixed #9471 - Expanded ModelAdmin.raw_id_fields do...

2012-10-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: da958eb2098372c20cc3aaf905777b1a8d3144eb
  
https://github.com/django/django/commit/da958eb2098372c20cc3aaf905777b1a8d3144eb
  Author: Tim Graham 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
A docs/ref/contrib/admin/_images/raw_id_fields.png
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  Fixed #9471 - Expanded ModelAdmin.raw_id_fields docs; thanks adroffne for the 
suggestion.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18717: Setting attributes on deferred objects should trigger field's descriptor's set()

2012-10-24 Thread Django

#18717: Setting attributes on deferred objects should trigger field's 
descriptor's
__set__()
---+
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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
---+
Changes (by lrekucki):

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


Comment:

 The patch failes as {{{DeferredAttribute}}} no longer has {{{model_ref}}}.
 On a side note, {{{_meta.get_field_by_name}} can be used instead of
 iterating.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #13068: The "Add another [inline object]" javascript doesn't respect prepopulated_fields settings

2012-10-24 Thread Django

#13068: The "Add another [inline object]" javascript doesn't respect
prepopulated_fields settings
-+-
 Reporter:  hejsan   |Owner:  seanbrant
 Type:  Bug  |   Status:  reopened
Component:  contrib.admin|  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:  prepopulated_field   | Triage Stage:  Accepted
  inline add |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by frankwiles):

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


Comment:

 I'm still seeing this in 1.4.2.  It works for any Inlines that are created
 because of 'extra', but adding additional ones the slug prepopulation
 doesn't 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19031: Using @override_settings doesn't override DATABASES in threads +SQLite

2012-10-24 Thread Django

#19031: Using @override_settings doesn't override DATABASES in threads +SQLite
---+
 Reporter:  jonash |Owner:  nobody
 Type:  Bug|   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:  1  |UI/UX:  0
---+

Comment (by Architekt):

 I don't think that overriding DATABASE settings is too much. It depends on
 what do you expect from it. I can imagine proper use cases for it.

 In the docs is described that the test database is created before running
 tests. And every time you run tests you see in the output: Creating test
 database... -> runing tests -> Destoying test database... This should be
 enough to understand that overriding DATABASE will not change test
 database in the middle of running tests.

 Overriding settings is always tricky. Situation described in this ticket
 is just one case out of many others. I think this particular situation
 does not need any special documentation.

 jonash: Right solution for your problem is skippping the test for SQLite's
 :memory: database.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19025: FormWizard.get_context_data() doesn't include "form" in context

2012-10-24 Thread Django

#19025: FormWizard.get_context_data() doesn't include "form" in context
---+--
 Reporter:  kenth  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.formtools  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by kenth):

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


Comment:

 Patch on github: https://github.com/django/django/pull/466

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18707: Test client doesn't allow testing 500 responses content

2012-10-24 Thread Django

#18707: Test client doesn't allow testing 500 responses content
---+
 Reporter:  ricardokirkner@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  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:  0  |UI/UX:  0
---+
Changes (by lrekucki):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Bug => New feature
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 The test client works as documented, so it's not a bug.

 In most cases this behavior is more useful then returning getting a
 generic error page. Using selenium is probably a better choice for testing
 your 500 pages, but I guess that having an option in the Client class
 could also be 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18672: Model hooks for custom sql on syncdb and flush

2012-10-24 Thread Django

#18672: Model hooks for custom sql on syncdb and flush
-+-
 Reporter:  niwi |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lrekucki):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Design decision 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18533: makemessages command fails on windows

2012-10-24 Thread Django

#18533: makemessages command fails on windows
-+-
 Reporter:  pasha.savchenko@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  needsinfo
 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 lrekucki):

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


Comment:

 I also can't reproduce this problem. Example command passed to Popen:

 {{{#!python
 '''
 xgettext -d django -L Python
 --keyword=gettext_noop --keyword=gettex_lazy --keyword=ngettext_lazy:1,2
 --keyword=ugettext_noop --keyword=ugettext_lazy
 --keyword=ungettext_lazy:1,2
 --keyword=pgettext:1c,2 --keyword=npgettext:1c,2,3
 --keyword=pgettext_lazy:1c,2
 --keyword=npgettext_lazy:1c,2,3 --from-code UTF-8 --add-
 comments=Translators
 -o - ".\\manage.py"
 '''
 }}}

 This works fine with or without {{{shell=True}}} (which, btw, isn't a
 security issue here because Django generates all input passed to it). We
 don't need to pass {{{executable}}}, it is inferred from the command
 string.

 Unless given more details about the environment and a way to reproduce the
 problem, there is not much we can 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 https://groups.google.com/groups/opt_out.

[django/django] 1b096a: Removed a function that is already fully implement...

2012-10-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1b096ad77362441d22c3eb7bfa03e9e221af2236
  
https://github.com/django/django/commit/1b096ad77362441d22c3eb7bfa03e9e221af2236
  Author: Alex Gaynor 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
M django/core/handlers/wsgi.py

  Log Message:
  ---
  Removed a function that is already fully implemented by a base class.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19177: Add some ems to the width of username label at login page.

2012-10-24 Thread Django

#19177: Add some ems to the width of username label at login page.
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 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:  1
--+

Comment (by claudep):

 If we care for i18n, either use top-aligned labels (http://css-tricks.com
 /label-placement-on-forms/) or simply a table, yes, a table.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #5622: Empty ipaddress raises an error (invalid input syntax for type inet: "")

2012-10-24 Thread Django

#5622: Empty ipaddress raises an error (invalid input syntax for type inet: "")
-+-
 Reporter:  anonymous|Owner:  aashu_dwivedi
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sprintdec01  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kace):

 For users facing this irritating issue, there is a quick, effective work-
 around (based on one of toke's patches (thank you)).  Put this into
 "models.py":
 {{{
 class IPAddressFieldNullable(models.IPAddressField) :
 def get_db_prep_save(self, value):
 return value or None
 }}}
 Then change your IP attribute to use this modified field.  E.g.:
 {{{
 -   someip = models.IPAddressField(blank=True, null=True )
 +   someip = IPAddressFieldNullable(blank=True, null=True )
 }}}

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

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

Re: [Django] #19165: add first and last page to paginator

2012-10-24 Thread Django

#19165: add first and last page to paginator
-+-
 Reporter:  ciro.santilli@…  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  paginator, last  | Triage Stage:  Design
  page, first page   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

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


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18976: problem with datepicker django widget

2012-10-24 Thread Django

#18976: problem with datepicker django widget
-+-
 Reporter:   |Owner:  nobody
  lukasz.z.grabowski@…   |   Status:  closed
 Type:  Bug  |  Version:  1.4
Component:  Forms|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  django admin,|  Unreviewed
  django jquery, datepicker, |  Needs documentation:  0
  DateTimeShortcuts  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by lrekucki):

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


Comment:

 {{{AdminDateWidget}}} isn't a part of public API, so we can't guarantee it
 will work outside of the admin app. In this particular case, you don't
 have a django.jQuery object which is created in {{{jquery.init.js}}}
 included on every admin page.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

2012-10-24 Thread Django

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by claudep):

 Adding `@override_settings(DEBUG_PROPAGATE_EXCEPTIONS=True)` for each of
 those tests solves this particular 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19177: Add some ems to the width of username label at login page.

2012-10-24 Thread Django

#19177: Add some ems to the width of username label at login page.
--+
 Reporter:  void  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 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:  1
--+
Changes (by lrekucki):

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


Comment:

 It would be best if the layout just scaled with the width of the text in
 the label.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19179: No mention of Multiiple Inheritance required for NamedUrlWizardView

2012-10-24 Thread Django

#19179: No mention of Multiiple Inheritance required for NamedUrlWizardView
-+-
 Reporter:  tom@…|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:   |Version:  1.4
  Documentation  |   Keywords:  SessionWizardView,
 Severity:  Normal   |  NamedUrlWizardView
 Triage Stage:   |  Has patch:  0
  Unreviewed |  UI/UX:  0
Easy pickings:  0|
-+-
 When creating a formtools.wizard.views.NamedUrlWizardView you must
 subclass both SessionWizardView and NamedUrlWizardView. This is ran me for
 a bit of a loop today, and their is no mention of this in the
 documentation.

 Example of a view:
 {{{
 class SubClassOfFormWizard(SessionWizardView, NamedUrlWizardView):
 def done(self, form_list, **kwargs):
 return render_to_response('finished.html', {
 'form_data': [form.cleaned_data for form in form_list],
 })
 }}}

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

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

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

2012-10-24 Thread Django

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

Comment (by Gargamel):

 @rugbyjock: I was able to reproduce the first bug now, I forgot to set
 extra=0. The problem is, I don't really see how this is fixable... The
 root of the problem is that when extra is 0, the inline templates only
 insert the 'empty-form', but these forms do not contain the nested forms,
 because this would break all previous javascript code for inlines. I think
 to fix this bug I would have to rewrite nearly all of my code and the
 inline code in general... For this reason I will probably just disable the
 option of putting 0 in the extra field when nested inlines are used. Maybe
 one day I'll feel like rewriting the entire thing, but not now :).

 The second bug was indeed fixed for the most, but I just uploaded the
 wrong diff >.<

 I'll do some more fixing and then I'll upload the file again.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 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
--+--
Changes (by mariocesar):

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


Comment:

 *!

 May the earth swallow me ... Sorry for making lose your time, running the
 tests I realize that error was about packing incorrectly the tuples in my
 models.

 My fix will solve the problem is someone do something like

 {{{
 permissions = (
   ('can_approve', 'Can approve')
 )
 }}}

 permissions, will be end as ('can_approve', 'Can approve'), as it's
 tuple(tuple()). Of course all (not me) sane people do.

 {{{
 permissions = (
   ('can_approve', 'Can approve'),
 )
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  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
--+--

Comment (by mariocesar):

 I added a new test, here is the stacktrace if there is no patch

 {{{
 ==
 ERROR: test_bug_19178
 (django.contrib.auth.tests.management.PermissionDuplicationTestCase)
 --
 Traceback (most recent call last):
   File "/home/mariocesar/Proyectos/Django/.env/local/lib/python2.7/site-
 packages/django/contrib/auth/tests/management.py", line 228, in
 test_bug_19178
 create_permissions(models, [], verbosity=0)
   File "/home/mariocesar/Proyectos/Django/.env/local/lib/python2.7/site-
 packages/django/contrib/auth/management/__init__.py", line 73, in
 create_permissions
 for perm in _get_all_permissions(klass._meta, ctype):
   File "/home/mariocesar/Proyectos/Django/.env/local/lib/python2.7/site-
 packages/django/contrib/auth/management/__init__.py", line 28, in
 _get_all_permissions
 _check_permission_clashing(custom, builtin, ctype)
   File "/home/mariocesar/Proyectos/Django/.env/local/lib/python2.7/site-
 packages/django/contrib/auth/management/__init__.py", line 48, in
 _check_permission_clashing
 for codename, _name in custom:
 ValueError: too many values to unpack
 }}}

 will be pushing the patch in a minute

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  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
--+--

Comment (by ptone):

 tests probably should go in contrib/auth/tests/management.py

 the create_permission function really should be part of a permissions API
 that is defined outside of the management/management command context - but
 that is where it is for now.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  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
--+--

Comment (by mariocesar):

 My case is something like, having first created with syncdb this model:

 {{{
 class UserProfile(models.Model):
 user = models.ForeignKey(User)

 class Meta:
 permissions = (
 ('can_approve', 'Can approve'),
 ('can_dismiss', 'Can dismiss')
 )
 }}}

 If later I add a single new permission

 {{{
 class UserProfile(models.Model):
 user = models.ForeignKey(User)

 class Meta:
 permissions = (
 ('can_approve', 'Can approve'),
 ('can_dismiss', 'Can dismiss'),
 ('can_dance', 'Can dance')
 )
 }}}

 It fails.

 Where do I put the test case? I'm kind of lost about how write a test 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  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
--+--

Comment (by anonymous):

 Could you attack a sample model with failing Meta.permissions (a test case
 in pull request would be even better...).

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9519: Add QuerySet.bulk_delete() that issues only a single SQL query

2012-10-24 Thread Django

#9519: Add QuerySet.bulk_delete() that issues only a single SQL query
-+-
 Reporter:  Tarken   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, queryset,  |  Needs documentation:  0
  delete |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by ptone):

 Replying to [comment:17 akaariai]:
 > The idea in comment:15 has been implemented - is there still need for
 separate bulk_delete()?

 I agree about ignoring cascades being a non-starter - if you need that
 level of manipulation, drop to SQL.

 The question is whether there are times you have a non-cascading model,
 you have signals, but you want to just delete a batch of objects.  This is
 analogous to update method not firing signals.

 whether this is bulk_delete or delete(signals=False) might be a minor
 point, I'd lean slightly toward a separate method as being cleaner to
 document as a special case, and to not introduce the concept of
 signals=False as being something that people would request be a general
 pattern for other methods.

 If we wanted to offer some disabling signals more generally, perhaps we
 could look into a context manager for that.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+--
 Reporter:  mariocesar|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  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 mariocesar):

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


Comment:

 I just made a draft patch → https://github.com/django/django/pull/465

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19019: UserAdmin.user_change_password does not log the change

2012-10-24 Thread Django

#19019: UserAdmin.user_change_password does not log the change
--+--
 Reporter:  Tuttle|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by fanatid):

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


Comment:

 Patch on github https://github.com/django/django/pull/464

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19178: create_permissions method fails if the model has a single new permission

2012-10-24 Thread Django

#19178: create_permissions method fails if the model has a single new permission
--+
 Reporter:  mariocesar|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I notice this by using this command → https://gist.github.com/3946353, it
 list all apps and update the permissions in the db if there is any new.

 The stacktrace is:

 {{{
 Traceback (most recent call last):
   File "/home/mariocesar/Proyectos/Crowddeals/env/local/lib/python2.7
 /site-packages/django/core/management/base.py", line 222, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/mariocesar/Proyectos/Crowddeals/env/local/lib/python2.7
 /site-packages/django/core/management/base.py", line 252, in execute
 output = self.handle(*args, **options)
   File
 
"/home/mariocesar/Proyectos/Crowddeals/crowddeals/core/management/commands/update_permissions.py",
 line 29, in handle
 create_permissions(app, get_models(), options.get('verbosity', 0))
   File "/home/mariocesar/Proyectos/Crowddeals/env/local/lib/python2.7
 /site-packages/django/contrib/auth/management/__init__.py", line 74, in
 create_permissions
 for perm in _get_all_permissions(klass._meta, ctype):
   File "/home/mariocesar/Proyectos/Crowddeals/env/local/lib/python2.7
 /site-packages/django/contrib/auth/management/__init__.py", line 28, in
 _get_all_permissions
 _check_permission_clashing(custom, builtin, ctype)
   File "/home/mariocesar/Proyectos/Crowddeals/env/local/lib/python2.7
 /site-packages/django/contrib/auth/management/__init__.py", line 49, in
 _check_permission_clashing
 for codename, _name in custom:
 ValueError: too many values to unpack
 }}}


 I see that in ´contrib/auth/management/__init__.py´ the method
 _check_permission_clashing unpack the custom new methods. Normally the
 list of permissions will be a list of list, however if there is just one
 new permission, when getting the permissiosn it returns just a list of
 strings.

 Making the _get_all_permissios code aware of that will fix the problem.

 {{{
 def _get_all_permissions(opts, ctype):
 """
 Returns (codename, name) for all permissions in the given opts.
 """
 builtin = _get_builtin_permissions(opts)
 custom = list(opts.permissions)
 _check_permission_clashing(custom, builtin, ctype)
 return builtin + custom
 }}}

 {{{
 def _get_all_permissions(opts, ctype):
 """
 Returns (codename, name) for all permissions in the given opts.
 """
 builtin = _get_builtin_permissions(opts)
 custom = list(opts.permissions)

 if any(isinstance(el, basestring) for el in custom):
 custom = [custom]

 _check_permission_clashing(custom, builtin, ctype)
 return builtin + custom
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18796: Refactor HttpResponse.iter / _get_content

2012-10-24 Thread Django

#18796: Refactor HttpResponse.__iter__ / _get_content
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  HTTP handling|   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 aaugustin):

 See also #16494 and #10190.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #6527: A bug in HttpResponse with iterators

2012-10-24 Thread Django

#6527: A bug in HttpResponse  with iterators
-+-
 Reporter:  daonb   |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  http iterators   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"495a8b8107dbd4fb511954bcd2322d125addd94e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="495a8b8107dbd4fb511954bcd2322d125addd94e"
 Fixed #6527 -- Provided repeatable content access

 in HttpResponses instantiated with iterators.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #13222: unexpected HttpResponse iteration behavior

2012-10-24 Thread Django

#13222: unexpected HttpResponse iteration behavior
-+-
 Reporter:  teepark  |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  1.3-rc1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"82b3e6ffcb9d810cc0e3ec27d25f89ce1fd525e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="82b3e6ffcb9d810cc0e3ec27d25f89ce1fd525e0"
 Fixed #13222 -- Made HttpResponse iterable once

 response.content can be accessed many times as desired, and always
 returns the same result.

 iter(response) works only once and consumes the iterator.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 83041c: Fixed a DeprecationWarning under Python 3.

2012-10-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 83041ca8025425530fcd32b50f247077ac0a5b74
  
https://github.com/django/django/commit/83041ca8025425530fcd32b50f247077ac0a5b74
  Author: Aymeric Augustin 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
M tests/modeltests/delete/tests.py

  Log Message:
  ---
  Fixed a DeprecationWarning under Python 3.


  Commit: 495a8b8107dbd4fb511954bcd2322d125addd94e
  
https://github.com/django/django/commit/495a8b8107dbd4fb511954bcd2322d125addd94e
  Author: Aymeric Augustin 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
M django/http/response.py
M docs/internals/deprecation.txt
M docs/ref/request-response.txt
M docs/releases/1.5.txt
M tests/regressiontests/httpwrappers/tests.py

  Log Message:
  ---
  Fixed #6527 -- Provided repeatable content access

in HttpResponses instantiated with iterators.


  Commit: 82b3e6ffcb9d810cc0e3ec27d25f89ce1fd525e0
  
https://github.com/django/django/commit/82b3e6ffcb9d810cc0e3ec27d25f89ce1fd525e0
  Author: Aymeric Augustin 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
M django/http/response.py
M django/test/testcases.py
M tests/regressiontests/httpwrappers/tests.py

  Log Message:
  ---
  Fixed #13222 -- Made HttpResponse iterable once

response.content can be accessed many times as desired, and always
returns the same result.

iter(response) works only once and consumes the iterator.


Compare: https://github.com/django/django/compare/c736a1a9f8f1...82b3e6ffcb9d

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #10190: Charset should be customizable with HttpResponse

2012-10-24 Thread Django

#10190: Charset should be customizable with HttpResponse
-+-
 Reporter:  Wonlay   |Owner:  aaugustin
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  HttpResponse,| Triage Stage:  Fixed on
  charset, runtime   |  a branch
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  ccahoon => aaugustin


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19176: MySQL backend: typo on adapt_datetime_with_timezone_support warning message

2012-10-24 Thread Django

#19176: MySQL backend: typo on adapt_datetime_with_timezone_support warning 
message
--+
 Reporter:  maxirobaina@… |  Owner:  nobody
 Type:  Bug   | Status:  closed
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"c736a1a9f8f1b70adcbbce8a098fa7c0c4062785"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c736a1a9f8f1b70adcbbce8a098fa7c0c4062785"
 Fixed #19176 -- Typo in copy-pasted error message.

 Thanks maxirobaina 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 https://groups.google.com/groups/opt_out.

[django/django] c736a1: Fixed #19176 -- Typo in copy-pasted error message.

2012-10-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c736a1a9f8f1b70adcbbce8a098fa7c0c4062785
  
https://github.com/django/django/commit/c736a1a9f8f1b70adcbbce8a098fa7c0c4062785
  Author: Aymeric Augustin 
  Date:   2012-10-24 (Wed, 24 Oct 2012)

  Changed paths:
M django/db/backends/mysql/base.py

  Log Message:
  ---
  Fixed #19176 -- Typo in copy-pasted error message.

Thanks maxirobaina 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19160: Make ungettext_lazy really usable

2012-10-24 Thread Django

#19160: Make ungettext_lazy really usable
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by void):

 Patch without `resolve()` method: https://gist.github.com/3945679

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18234: ValueError attempting to save a flatpage with no sites

2012-10-24 Thread Django

#18234: ValueError attempting to save a flatpage with no sites
---+
 Reporter:  kmtracey   |Owner:  kmtracey
 Type:  Bug|   Status:  closed
Component:  contrib.flatpages  |  Version:  1.4
 Severity:  Normal |   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
---+

Comment (by anonymous):

 It's not a data-loss bug, and it has an easy workaround (specify a site
 for the flatpage) so the fix was not backported to 1.4 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 https://groups.google.com/groups/opt_out.

[Django] #19177: Add some ems to the width of username label at login page.

2012-10-24 Thread Django

#19177: Add some ems to the width of username label at login page.
--+
 Reporter:  void  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.admin |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  1
--+
 Recent landing of the Russel's work contains one small, but important
 change:
 
https://github.com/django/django/commit/70a0de37d132e5f1514fb939875f69649f103124#L5L33

 It makes the username label of the login form to be the same as user model
 username field's verbose_name. Previously it was just a translated "User"
 string. I'm fine with that, but that change cause a tiny layout issue.
 "Username" is two words in some languages, and some languages have longer
 words than others, and now in the number of languages username label have
 shifted to the second line.

 My proposal is to increase the width of username label by 3em, based on
 the following screenshots:
 http://dl.dropbox.com/u/302516/Screenshots/18.png (Czech, +1em required)
 http://dl.dropbox.com/u/302516/Screenshots/19.png (Spanish, +1em required)
 http://dl.dropbox.com/u/302516/Screenshots/1a.png (Georgian, +3em
 required)
 http://dl.dropbox.com/u/302516/Screenshots/1b.png (Kazakh, +1em required)
 http://dl.dropbox.com/u/302516/Screenshots/1c.png (Mongolian, +1em
 required)
 http://dl.dropbox.com/u/302516/Screenshots/1d.png (Russian, +1em required)
 http://dl.dropbox.com/u/302516/Screenshots/1e.png (Slovak, +2em required)

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18234: ValueError attempting to save a flatpage with no sites

2012-10-24 Thread Django

#18234: ValueError attempting to save a flatpage with no sites
---+
 Reporter:  kmtracey   |Owner:  kmtracey
 Type:  Bug|   Status:  closed
Component:  contrib.flatpages  |  Version:  1.4
 Severity:  Normal |   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
---+

Comment (by margusholland):

 I still get this error in Django 1.4.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 https://groups.google.com/groups/opt_out.

[Django] #19176: MySQL backend: typo on adapt_datetime_with_timezone_support warning message

2012-10-24 Thread Django

#19176: MySQL backend: typo on adapt_datetime_with_timezone_support warning 
message
--+
 Reporter:  maxirobaina@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In MySQL backend (base.py) there is a typo on
 adapt_datetime_with_timezone_support function
 The warnning message say:

  warnings.warn("SQLite received a naive datetime (%s)"
   " while time zone support is active." % value,
   RuntimeWarning)

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9519: Add QuerySet.bulk_delete() that issues only a single SQL query

2012-10-24 Thread Django

#9519: Add QuerySet.bulk_delete() that issues only a single SQL query
-+-
 Reporter:  Tarken   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, queryset,  |  Needs documentation:  0
  delete |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 The idea in comment:15 has been implemented - is there still need for
 separate bulk_delete()?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9519: Add QuerySet.bulk_delete() that issues only a single SQL query

2012-10-24 Thread Django

#9519: Add QuerySet.bulk_delete() that issues only a single SQL query
-+-
 Reporter:  Tarken   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database, queryset,  |  Needs documentation:  0
  delete |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by kkumler):

 * cc: kkumler (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 https://groups.google.com/groups/opt_out.

Re: [Django] #19167: When running tests, Django accesses the database referred to in settings

2012-10-24 Thread Django

#19167: When running tests, Django accesses the database referred to in settings
---+
 Reporter:  EvilDMP|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
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
---+

Comment (by EvilDMP):

 I've made a pull request for the documentation:
 https://github.com/django/django/pull/463

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19058: Inserting NULL value in Oracle spatial backend causes crash.

2012-10-24 Thread Django

#19058: Inserting NULL value in Oracle spatial backend causes crash.
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  gis oracle orm   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 First, there is a way to install Oracle "full edition" with spatial
 support using https://code.djangoproject.com/wiki/OracleSpatialTestSetup

 The current proposal is to alter the code around line 890 in
 sql/compiler.py from:
 {{{
 else:
 placeholders = [
 [self.placeholder(field, v) for field, v in zip(fields,
 val)]
 for val in values
 ]
 }}}
 to
 {{{
 else:
 placeholders = [
 [self.placeholder(field, v) for field, v in zip(fields,
 val)]
 for val in values
 ]
 # Oracle GIS needs to remove some values due to #10888
 values = connection.ops.modify_insert_values(placeholders,
 values)
 }}}

 Default implementation of modify_insert_values is to just return values,
 Oracle gis would need to loop the placeholders and values in sync and
 remove values for 'NULL' placeholders.

 This way we could fix this issue, and also get rid of Oracle GIS
 compiler.py.

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

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

Re: [Django] #19165: add first and last page to paginator

2012-10-24 Thread Django

#19165: add first and last page to paginator
-+-
 Reporter:  ciro.santilli@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  paginator, last  | Triage Stage:  Design
  page, first page   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Ciro Duran Santilli ):

 Aw, should have read better the tutorial, I hadn't seen that the Page
 object (which is what is usually passed to templates) has a Paginator
 field.

 In this case, we can just write:

 page.paginator.num_pages

 for the last page.

 So I agree adding more fields to the Page object would be a minor
 improvement.

 This ticket can be closed on my part.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

2012-10-24 Thread Django

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 have the same problem

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

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

Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

2012-10-24 Thread Django

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 have the same problem

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

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

Re: [Django] #18315: QueryDict.pop is inconsistent

2012-10-24 Thread Django

#18315: QueryDict.pop is inconsistent
-+-
 Reporter:  gcbirzan |Owner:  nobody
 Type:  Uncategorized|   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
-+-

Comment (by anonymous):

 This confused me to no end before I found out that doing QueryDict['key']
 would not return the same value as QueryDict.pop('key'). This hardly seems
 like it conform with other uses of pop.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19160: Make ungettext_lazy really usable

2012-10-24 Thread Django

#19160: Make ungettext_lazy really usable
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 There are interesting parts in your implementation. However, the fact that
 you have to call a method (`resolve()`) is creating a special case for
 translatable strings and defeats the ability to swap a ungettext_lazy
 object with any other string.

 Basically, the use case of lazy gettext strings is to have a string
 defined at class/module level (defined at compilation time), and then use
 that string somewhere later at runtime. So it should be totally acceptable
 to have the string redefined somewhere in the code. Therefore, you don't
 know for sure at runtime if the string is an `ungettext_lazy` or any other
 string object. So having to call a special method on the string is a no-go
 for me.

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

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

65 matches

Mail list logo