Re: [Django] #19513: Annotate broken django.db.backends.oracle while updating

[Django]

#19513: Annotate broken django.db.backends.oracle while updating
-+-
 Reporter:  mengzhuo1203@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mengzhuo):

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


Comment:

 I think that I know why MySQL and SQlite runs fine, cause both of them
 will query first then update the queried sets, however Oracle backend will
 not, it simply puts everything in the same query.

 Here is the buggy Oracle Query set
 {{{
 UPDATE "ITEM_COMBINATION" SET "ACTIVE" = :arg0 WHERE
 "ITEM_COMBINATION"."ID" IN (
 SELECT U0."ID", SUM(U8."PRICE") AS "PRICE"
FROM "ITEM_COMBINATION" U0
LEFT OUTER JOIN "ITEM_COMBINATION_ITEMS" U7 ON (U0."ID" =
 U7."COMBINATION_ID")
LEFT OUTER JOIN "ITEM_ITEM" U8 ON (U7."ITEM_ID" = U8."ID")
 WHERE U0."DURATION_ID" = :arg1
GROUP BY U0."ID", U0."ITEM_ID", U0."NAME", U0."SOMEDUMMYITEM",
 U0."SOMEDUMMYITEM", U0."SOMEDUMMYITEM", U0."SOMEDUMMYITEM",
 U0."SOMEDUMMYITEM", U0."SOMEDUMMYITEM", U0."ACTIVE", U0."SOMEDUMMYITEM",
 U0."SOMEDUMMYITEM", U0."CATEGORY_ID"); args=(False, 2)
 }}}

 Here is MySQL Query Set
 {{{
 SELECT U0.`id`, SUM(U8.`price`) AS `price`, MIN(U8.`store`) AS `store`
 FROM `item_combination` U0 LEFT OUTER JOIN `item_combination_items` U7 ON
 (U0.`id` = U7.`combination_id`) LEFT OUTER JOIN `item_item` U8 ON
 (U7.`item_id` = U8.`id`) GROUP BY U0.`id`, U0.`item_id`,
 U0.`SOMEDUMMYITEM`, U0.`SOMEDUMMYITEM`, U0.`SOMEDUMMYITEM`,
 U0.`SOMEDUMMYITEM`, U0.`SOMEDUMMYITEM`, U0.`SOMEDUMMYITEM`,
 U0.`SOMEDUMMYITEM`, U0.`active`, U0.`SOMEDUMMYITEM`, U0.`SOMEDUMMYITEM`,
 U0.`SOMEDUMMYITEM` ORDER BY NULL; args=()

 UPDATE `item_combination` SET `active` = 1 WHERE `item_combination`.`id`
 IN (1, 3); args=(True, 1, 3)
 }}}

-- 
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] #19519: Django fails to close db connections at end of request-response cycle

[Django]

#19519: Django fails to close db connections at end of request-response cycle
-+-
 Reporter:  amosonn@…|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.4
  (models, ORM)  |   Keywords:  connection, managment,
 Severity:  Normal   |  closing, mysql, innodb, signal,
 Triage Stage:  Unreviewed   |  generator
Easy pickings:  0|  Has patch:  0
 |  UI/UX:  0
-+-
 Under some circumstances (I'll get to guesses about this in the end), the
 db connection isn't closed at the end of the request, and resurfaces later
 on to service another request. Thus, one request writes to the database,
 and then the next request tries to look for that data and fails, because
 it uses an outdated connection that hasn't yet been notified of the db
 change (per [http://www.python.org/dev/peps/pep-0249/#connection-objects
 pep-249], different connections aren't required to see the same data.) The
 workaround solution for this is to add a django.db.connection.close()
 before that query, which brings to mind
 [https://code.djangoproject.com/ticket/13533 bug #13533]. Similarly, This
 bug manifests on mysql innodb; but I haven't checked other databases, so
 this might just be coincidence. It is also possible that the non-closing
 connection bug exists for all back-ends, but that auto-commit isn't enough
 to prevent the damage only on mysql innodb.

 The situation under which I've seen these connections retained is when
 sending an HttpResponse with a generator for content. It might be that
 when sending such content, the following lines (django.db:44-47)
 {{{
 def close_connection(**kwargs):
 for conn in connections.all():
 conn.close()
 signals.request_finished.connect(close_connection)
 }}}
 which are supposed to make sure the connection closes, don't work, because
 the signal isn't raised. It is, however, still a riddle how the old
 connection gets attached to a new request.
 [https://code.djangoproject.com/ticket/19117 Bug #19117] might also be
 related to 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.

[django/django] b70498: Updated installation FAQ entry on Python versions.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b70498d675bbd96849b466cdd45c1c189f227444
  
https://github.com/django/django/commit/b70498d675bbd96849b466cdd45c1c189f227444
  Author: Aymeric Augustin 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M docs/faq/install.txt

  Log Message:
  ---
  Updated installation FAQ entry on Python versions.

The 1.7 line is a reasonnable forecast, not a final decision.



-- 
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] #19514: form.fields.keyOrder is not supported for AdminForm

[Django]

#19514: form.fields.keyOrder is not supported for AdminForm
-+-
 Reporter:  scorpil  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  keyOrder, form,  | Triage Stage:
  django-admin   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lukeplant):

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


Comment:

 The admin has a much more powerful way of specifying field order for the
 form, and it doesn't make sense to encourage a different way of specifying
 field order, when it is going to be overridden if the `ModelAdmin` defines
 `fieldsets`. "Only one way to do it" seems to encourage a WONTFIX/INVALID
 here. Yes, we already have two potential ways to do it, but for the admin
 one has never worked and we've never advertised that it would 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.

[django/django] 8738da: [1.5.x] Updated Python versions supported FAQ entr...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 8738da03c623c702aa57a90216bde0e70f42a957
  
https://github.com/django/django/commit/8738da03c623c702aa57a90216bde0e70f42a957
  Author: Ramiro Morales 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M docs/faq/install.txt

  Log Message:
  ---
  [1.5.x] Updated Python versions supported FAQ entry.



-- 
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] #19436: ensure_csrf_cookie decorator issues a "CSRF token missing or incorrect" warning.

[Django]

#19436: ensure_csrf_cookie decorator issues a "CSRF token missing or incorrect"
warning.
--+
 Reporter:  wrr@… |Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  contrib.csrf  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  csrf  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by lukeplant):

 * component:  Uncategorized => contrib.csrf
 * stage:  Design decision needed => Accepted


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

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

Re: [Django] #19436: ensure_csrf_cookie decorator issues a "CSRF token missing or incorrect" warning.

[Django]

#19436: ensure_csrf_cookie decorator issues a "CSRF token missing or incorrect"
warning.
-+-
 Reporter:  wrr@…|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  csrf | 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 lukeplant):

 I agree with wrr - this is a clear (low priority) bug in the
 implementation. It also looks like the fix is trivial - move all the
 `logger` calls into the `_reject()` method. AFAICS from a brief review,
 this is straightforward and will reduce duplication and line count 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18970: Document that Django doesn't work with MySQL under Python 3

[Django]

#18970: Document that Django doesn't work with MySQL under Python 3
-+
 Reporter:  rajeevramdas@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   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 claudep):

 ... and Selenium (LiveServerTestCase),
 http://code.google.com/p/selenium/issues/detail?id=2139

-- 
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] #19518: Deprecation of localflavor not documented

[Django]

#19518: Deprecation of localflavor not documented
-+
 Reporter:  aaugustin|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Documentation|Version:  master
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 `django.contrib.localflavor` was deprecated in
 05b849162266c0df355bccdf53bd1e0617a19bb0.

 This should be documented:
 - in the 1.5 release notes (all the more since the deprecation was
 accelerated)
 - in the deprecation timeline, in the 1.6 section

-- 
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] #18970: Document that Django doesn't work with MySQL under Python 3

[Django]

#18970: Document that Django doesn't work with MySQL under Python 3
-+
 Reporter:  rajeevramdas@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   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 claudep):

 Another important current limitation to document is PIL (no ImageField on
 Python 3). Our best hope for a Python 3 port is with https://github.com
 /python-imaging/Pillow.

-- 
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] #19505: Clean up implementation of admin post-save redirects

[Django]

#19505: Clean up implementation of admin post-save redirects
--+
 Reporter:  julien|Owner:  julien
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  1.4
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Ramiro Morales ):

 In [changeset:"3b32e5cc2d4b6db22148cd7e51cdb735aeb25b13"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3b32e5cc2d4b6db22148cd7e51cdb735aeb25b13"
 [1.5.x] Expanded tests added when fixing #14529.

 To make sure changes in 35d1cd0 don't break anything. Refs #19505.

 ad769efa85e0296033572315025fed9fa9aefade 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] 3b32e5: [1.5.x] Expanded tests added when fixing #14529.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 3b32e5cc2d4b6db22148cd7e51cdb735aeb25b13
  
https://github.com/django/django/commit/3b32e5cc2d4b6db22148cd7e51cdb735aeb25b13
  Author: Ramiro Morales 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M tests/regressiontests/admin_views/admin.py
M tests/regressiontests/admin_views/models.py
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  [1.5.x] Expanded tests added when fixing #14529.

To make sure changes in 35d1cd0 don't break anything. Refs #19505.

ad769efa85e0296033572315025fed9fa9aefade 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] #18986: Improve error message for broken CSS in CachedStaticFilesStorage

[Django]

#18986: Improve error message for broken CSS in CachedStaticFilesStorage
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.staticfiles   |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * component:  Uncategorized => contrib.staticfiles


-- 
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] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by aaugustin):

 * component:  Uncategorized => Testing framework


-- 
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] #18127: Make *all* DeprecationWarnings stacklevel=2 or greater

[Django]

#18127: Make *all* DeprecationWarnings stacklevel=2 or greater
-+-
 Reporter:  MostAwesomeDude@…|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  nickmartini => aaugustin
 * status:  new => assigned


Comment:

 The pull request is out of date, and unfortunately, such patches are
 easier to redo than to review or update.

 The best time to do this is just after we advance the deprecation warnings
 in master for 1.6. At this point, there won't be any
 `PendingDeprecationWarning` left, and as few `DeprecationWarning` as
 possible.

-- 
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] #8001: Make redirection URLs customizable in ModelAdmin views

[Django]

#8001: Make redirection URLs customizable in ModelAdmin views
---+
 Reporter:  julien |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Ramiro Morales ):

 In [changeset:"3ad34c231bb6e13c29dd268f9557a9cb241280fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3ad34c231bb6e13c29dd268f9557a9cb241280fa"
 [1.5.x] Fixed #19505 -- A more flexible implementation for customizable
 admin redirect urls.

 Work by Julien Phalip.

 Refs #8001, #18310, #19505. See also
 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.

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

Re: [Django] #18310: Make named return URLs configurable

[Django]

#18310: Make named return URLs configurable
---+
 Reporter:  russellm   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 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 Morales ):

 In [changeset:"3ad34c231bb6e13c29dd268f9557a9cb241280fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3ad34c231bb6e13c29dd268f9557a9cb241280fa"
 [1.5.x] Fixed #19505 -- A more flexible implementation for customizable
 admin redirect urls.

 Work by Julien Phalip.

 Refs #8001, #18310, #19505. See also
 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.

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

Re: [Django] #19505: Clean up implementation of admin post-save redirects

[Django]

#19505: Clean up implementation of admin post-save redirects
--+
 Reporter:  julien|Owner:  julien
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  1.4
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Ramiro Morales ):

 In [changeset:"3ad34c231bb6e13c29dd268f9557a9cb241280fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3ad34c231bb6e13c29dd268f9557a9cb241280fa"
 [1.5.x] Fixed #19505 -- A more flexible implementation for customizable
 admin redirect urls.

 Work by Julien Phalip.

 Refs #8001, #18310, #19505. See also
 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.

 35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415 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] 3ad34c: [1.5.x] Fixed #19505 -- A more flexible implementa...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 3ad34c231bb6e13c29dd268f9557a9cb241280fa
  
https://github.com/django/django/commit/3ad34c231bb6e13c29dd268f9557a9cb241280fa
  Author: Julien Phalip 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/auth/admin.py
M docs/internals/deprecation.txt
M tests/regressiontests/admin_custom_urls/models.py
M tests/regressiontests/admin_custom_urls/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #19505 -- A more flexible implementation for customizable admin 
redirect urls.

Work by Julien Phalip.

Refs #8001, #18310, #19505. See also 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.

35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415 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] #17215: runtests doesn't clean up all temp files all the time

[Django]

#17215: runtests doesn't clean up all temp files all the time
---+
 Reporter:  kmtracey   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:
 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 aaugustin):

 #19206 was a duplicate.

-- 
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] #19206: Stale tmp files after running the testsuite.

[Django]

#19206: Stale tmp files after running the testsuite.
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Testing framework|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 This is a duplicate of #17215. Let's follow up over there.

-- 
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] #18970: Document that Django doesn't work with MySQL under Python 3 (was: Django Python 3 experimental support, python manage.py syncdb, 1064 error.)

[Django]

#18970: Document that Django doesn't work with MySQL under Python 3
-+
 Reporter:  rajeevramdas@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   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):

 * version:  1.4 => master
 * type:  New feature => Bug
 * severity:  Normal => Release blocker


Comment:

 We're about to release 1.5.

 We should say that MySQL is unsupported in the "Python 3 support"
 paragraph of the release notes.

 Does anyone know if Oracle works? cx_Oracle supports on Python 3, but I
 don't know if we ever ran the test suite with Oracle and Python 3.

-- 
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] #19505: Clean up implementation of admin post-save redirects

[Django]

#19505: Clean up implementation of admin post-save redirects
--+
 Reporter:  julien|Owner:  julien
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  1.4
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Ramiro Morales ):

 In [changeset:"ad769efa85e0296033572315025fed9fa9aefade"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad769efa85e0296033572315025fed9fa9aefade"
 Expanded tests added when fixing #14529.

 To make sure changes in 35d1cd0 don't break anything. Refs #19505.
 }}}

-- 
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] ad769e: Expanded tests added when fixing #14529.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ad769efa85e0296033572315025fed9fa9aefade
  
https://github.com/django/django/commit/ad769efa85e0296033572315025fed9fa9aefade
  Author: Ramiro Morales 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M tests/regressiontests/admin_views/admin.py
M tests/regressiontests/admin_views/models.py
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  Expanded tests added when fixing #14529.

To make sure changes in 35d1cd0 don't break anything. Refs #19505.



-- 
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] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   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
--+

Comment (by Tim Graham ):

 In [changeset:"5489fc47df76c3f25a959510b885fa9a28b495b4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5489fc47df76c3f25a959510b885fa9a28b495b4"
 [1.5.X] Fixed links to DATABASE ENGINE setting. refs #19516

 Backport of f56f6cfa58 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] 5489fc: [1.5.X] Fixed links to DATABASE ENGINE setting. re...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5489fc47df76c3f25a959510b885fa9a28b495b4
  
https://github.com/django/django/commit/5489fc47df76c3f25a959510b885fa9a28b495b4
  Author: Tim Graham 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M docs/howto/initial-data.txt
M docs/howto/legacy-databases.txt
M docs/intro/tutorial01.txt
M docs/releases/0.96.txt
M docs/releases/1.0-porting-guide.txt
M docs/releases/1.2-alpha-1.txt
M docs/releases/1.2.txt
M docs/topics/testing/overview.txt

  Log Message:
  ---
  [1.5.X] Fixed links to DATABASE ENGINE setting. refs #19516

Backport of f56f6cfa58 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] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   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
--+

Comment (by Tim Graham ):

 In [changeset:"f56f6cfa58345b964ceb2614e4366639381c8f6f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f56f6cfa58345b964ceb2614e4366639381c8f6f"
 Fixed links to DATABASE ENGINE setting. refs #19516
 }}}

-- 
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] f56f6c: Fixed links to DATABASE ENGINE setting. refs #1951...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f56f6cfa58345b964ceb2614e4366639381c8f6f
  
https://github.com/django/django/commit/f56f6cfa58345b964ceb2614e4366639381c8f6f
  Author: Tim Graham 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M docs/howto/initial-data.txt
M docs/howto/legacy-databases.txt
M docs/intro/tutorial01.txt
M docs/releases/0.96.txt
M docs/releases/1.0-porting-guide.txt
M docs/releases/1.2-alpha-1.txt
M docs/releases/1.2.txt
M docs/topics/testing/overview.txt

  Log Message:
  ---
  Fixed links to DATABASE ENGINE setting. refs #19516



-- 
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] #19517: Add support for X-Forwarded-Port to HttpRequest.get_host when USE_X_FORWARDED_HOST is in use

[Django]

#19517: Add support for X-Forwarded-Port to HttpRequest.get_host when
USE_X_FORWARDED_HOST is in use
-+-
 Reporter:   |  Owner:  nobody
  david_k_hess@… | Status:  new
 Type:   |Version:  1.4
  Uncategorized  |   Keywords:  httprequest, get_host, X-Forwarded-
Component:  HTTP |  Host, USE_X_FORWARDED_HOST
  handling   |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 The use case is an app served on ports 80, 443 (SSL) and 444 (SSL) served
 by gunicorn behind nginx. I'm sending X-Forwarded-Host and X-Forwarded-
 Port from nginx to gunicorn. Port 80 is open solely to redirect to 443 and
 both are open to the public internet. 444 is firewalled and reserved for
 the admin interface which is protected by this middleware component:

 {{{
 class ProtectAdminMiddleware(object):
 def process_request(self, request):
 if request.path.startswith("/admin") and
 request.META["HTTP_X_FORWARDED_PORT"] != "444":
 raise Http404
 }}}

 When turning on USE_X_FORWARDED_HOST, the code in HttpRequest.get_host
 does not take port into account:

 {{{
 [...]
 if settings.USE_X_FORWARDED_HOST and (
 'HTTP_X_FORWARDED_HOST' in self.META):
 host = self.META['HTTP_X_FORWARDED_HOST']
 elif 'HTTP_HOST' in self.META:
 host = self.META['HTTP_HOST']
 [...]
 }}}

 Because of this, at least two things in the admin interface on port 444
 don't function correctly; the CSRF token breaks saying there is a problem
 between referrer on 444 and token on 443 and you can't login. Also,
 redirects from say "/admin" on port 444 redirect to "/admin/" on 443
 instead of staying on 444. That's just what I was able to reach with
 logins broken.

 I monkey-patched HttpRequest.get_host to add support for X-Forwarded-Port
 when USE_X_FORWARDED_HOST is specified and it appears to have corrected
 these issues:

 {{{
 [...]
 if settings.USE_X_FORWARDED_HOST and (
 'HTTP_X_FORWARDED_HOST' in self.META):
 host = self.META['HTTP_X_FORWARDED_HOST']
 if 'HTTP_X_FORWARDED_PORT' in self.META:
 server_port = str(self.META['HTTP_X_FORWARDED_PORT'])
 if server_port != (self.is_secure() and '443' or '80'):
 host = '%s:%s' % (host, server_port)
 elif 'HTTP_HOST' in self.META:
 host = self.META['HTTP_HOST']
 [...]
 }}}

-- 
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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+-
 Reporter:  lrekucki |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 All known issues are fixed now.

 Please re-re-open if you find more.

-- 
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] #7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse objects.

[Django]

#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-+-
 Reporter:  mrmachine|Owner:  ccahoon
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  stream HttpResponse  | Triage Stage:  Accepted
  Content-Length |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"1c8be95a864540d416602577d1aa03d58ba33168"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c8be95a864540d416602577d1aa03d58ba33168"
 Prevented caching of streaming responses.

 The test introduced in 4b278131 accidentally passed because of a
 limitation of Python < 3.3.

 Refs #17758, #7581.
 }}}

-- 
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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+-
 Reporter:  lrekucki |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   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 Aymeric Augustin ):

 In [changeset:"1c8be95a864540d416602577d1aa03d58ba33168"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c8be95a864540d416602577d1aa03d58ba33168"
 Prevented caching of streaming responses.

 The test introduced in 4b278131 accidentally passed because of a
 limitation of Python < 3.3.

 Refs #17758, #7581.
 }}}

-- 
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] #7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse objects.

[Django]

#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-+-
 Reporter:  mrmachine|Owner:  ccahoon
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  stream HttpResponse  | Triage Stage:  Accepted
  Content-Length |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"cd914175c8209c5f366e87d94f8f6d050347757d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd914175c8209c5f366e87d94f8f6d050347757d"
 [1.5.x] Prevented caching of streaming responses.

 The test introduced in 4b278131 accidentally passed because of a
 limitation of Python < 3.3.

 Refs #17758, #7581.

 Backport of 1c8be95 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.

Re: [Django] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+-
 Reporter:  lrekucki |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   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 Aymeric Augustin ):

 In [changeset:"cd914175c8209c5f366e87d94f8f6d050347757d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd914175c8209c5f366e87d94f8f6d050347757d"
 [1.5.x] Prevented caching of streaming responses.

 The test introduced in 4b278131 accidentally passed because of a
 limitation of Python < 3.3.

 Refs #17758, #7581.

 Backport of 1c8be95 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] 1c8be9: Prevented caching of streaming responses.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1c8be95a864540d416602577d1aa03d58ba33168
  
https://github.com/django/django/commit/1c8be95a864540d416602577d1aa03d58ba33168
  Author: Aymeric Augustin 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M django/middleware/cache.py
M tests/regressiontests/cache/tests.py

  Log Message:
  ---
  Prevented caching of streaming responses.

The test introduced in 4b278131 accidentally passed because of a
limitation of Python < 3.3.

Refs #17758, #7581.



-- 
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] cd9141: [1.5.x] Prevented caching of streaming responses.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: cd914175c8209c5f366e87d94f8f6d050347757d
  
https://github.com/django/django/commit/cd914175c8209c5f366e87d94f8f6d050347757d
  Author: Aymeric Augustin 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M django/middleware/cache.py
M tests/regressiontests/cache/tests.py

  Log Message:
  ---
  [1.5.x] Prevented caching of streaming responses.

The test introduced in 4b278131 accidentally passed because of a
limitation of Python < 3.3.

Refs #17758, #7581.

Backport of 1c8be95 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] #18310: Make named return URLs configurable

[Django]

#18310: Make named return URLs configurable
---+
 Reporter:  russellm   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 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 Morales ):

 In [changeset:"35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415"]:
 {{{
 #!CommitTicketReference repository=""
 revision="35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415"
 Fixed #19505 -- A more flexible implementation for customizable admin
 redirect urls.

 Work by Julien Phalip.

 Refs #8001, #18310, #19505. See also
 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.
 }}}

-- 
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] #8001: Make redirection URLs customizable in ModelAdmin views

[Django]

#8001: Make redirection URLs customizable in ModelAdmin views
---+
 Reporter:  julien |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Ramiro Morales ):

 In [changeset:"35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415"]:
 {{{
 #!CommitTicketReference repository=""
 revision="35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415"
 Fixed #19505 -- A more flexible implementation for customizable admin
 redirect urls.

 Work by Julien Phalip.

 Refs #8001, #18310, #19505. See also
 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.
 }}}

-- 
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] #19505: Clean up implementation of admin post-save redirects

[Django]

#19505: Clean up implementation of admin post-save redirects
--+
 Reporter:  julien|Owner:  julien
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  1.4
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415"]:
 {{{
 #!CommitTicketReference repository=""
 revision="35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415"
 Fixed #19505 -- A more flexible implementation for customizable admin
 redirect urls.

 Work by Julien Phalip.

 Refs #8001, #18310, #19505. See also
 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.
 }}}

-- 
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] 35d1cd: Fixed #19505 -- A more flexible implementation for...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415
  
https://github.com/django/django/commit/35d1cd0b28d1d9cd7bffbfbc6cc2e02b58404415
  Author: Julien Phalip 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/auth/admin.py
M docs/internals/deprecation.txt
M tests/regressiontests/admin_custom_urls/models.py
M tests/regressiontests/admin_custom_urls/tests.py

  Log Message:
  ---
  Fixed #19505 -- A more flexible implementation for customizable admin 
redirect urls.

Work by Julien Phalip.

Refs #8001, #18310, #19505. See also 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.



-- 
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] #19515: Redirect path fields arbitrarily short

[Django]

#19515: Redirect path fields arbitrarily short
-+-
 Reporter:  s.shanabrook@…   |Owner:
 Type:   |  saulshanabrook
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * easy:  1 => 0
 * stage:  Unreviewed => Someday/Maybe


Comment:

 Thanks for the suggestion. The problem here isn't to change the max_size —
 it's to provide a suitable upgrade path for existing users. Otherwise,
 application-level and database-level constraints won't match any longer,
 which will result in uncaught errors.

 In general we've postponed this kind of requests to after Django gets
 built-in migrations — most likely 1.6 or 1.7.

-- 
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] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   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 aaugustin):

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


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

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

Re: [Django] #19515: Redirect path fields arbitrarily short

[Django]

#19515: Redirect path fields arbitrarily short
-+-
 Reporter:  s.shanabrook@…   |Owner:
 Type:   |  saulshanabrook
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by saulshanabrook):

 * has_patch:  0 => 1


Comment:

 Created fix at https://github.com/saulshanabrook/django/tree/ticket_19515

-- 
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] #19515: Redirect path fields arbitrarily short

[Django]

#19515: Redirect path fields arbitrarily short
-+-
 Reporter:  s.shanabrook@…   |Owner:
 Type:   |  saulshanabrook
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by saulshanabrook):

 * version:  1.4 => 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] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |  Owner:  timo
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I'd like to add -n (Run in nit-picky mode, warn about all missing
 references) to the sphinx make file. This involves some cleanup of
 legitimate failures as well as removing the annotations for example
 classes like AuthorDetail which I don't think are designed to be linked
 (nearly 900 warnings). Any objections to doing 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] #19515: Redirect path fields arbitrarily short

[Django]

#19515: Redirect path fields arbitrarily short
-+-
 Reporter:  s.shanabrook@…   |Owner:
 Type:   |  saulshanabrook
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.redirects|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by saulshanabrook):

 * owner:  anonymous => saulshanabrook


-- 
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] #19515: Redirect path fields arbitrarily short

[Django]

#19515: Redirect path fields arbitrarily short
-+-
 Reporter:  s.shanabrook@…   |Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.redirects|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Saul Shanabrook ):

 * status:  new => assigned
 * needs_better_patch:   => 1
 * needs_tests:   => 0
 * keywords:  redirects =>
 * owner:  nobody => anonymous
 * needs_docs:   => 0


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

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

[Django] #19515: Redirect path fields arbitrarily short

[Django]

#19515: Redirect path fields arbitrarily short
--+---
 Reporter:  s.shanabrook@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.redirects |Version:  1.4
 Severity:  Normal|   Keywords:  redirects
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+---
 In `django.contrib.redirects` the the `old_path` and `new_path` have
 `max_length=200`. This presents problems when either of the paths has a
 longer length than 200. `URLField` used to have a `max_length=200`, but
 this was resolved [1477] and isn't even applicable, since the path fields
 use `CharField`s, not `URLfield`s.

 I would recommend a `max_length=2000`. URL's with a length over 2000 are
 [http://stackoverflow.com/questions/417142/what-is-the-maximum-length-
 of-a-url not as well supported]. However since
 [https://docs.djangoproject.com/en/dev/ref/databases/#character-fields
 database enforcement of CharFields in MySQL is limited to 255 characters],
 the fields have to be also changed to `TextField`s.

-- 
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] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  localflavor  |   Resolution:
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by charettes):

 Both admonitions look good to me.

 @andreas_pelme, do you think this is correctly documenting the origin or
 the `DeprecationWarning`and how to get rid of it?

 Thanks for submitting the patches.

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

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

Re: [Django] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
-+-
 Reporter:  danbrwn  |Owner:  mitsuhiko
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  foreign,key,quoted,dceu2011|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by camilonova):

 I got this same error too with Django 1.4.2, uwsgi and nginx

 Maybe the changes were reverted or something?

-- 
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] #19353: Make it easier to extend UserCreationForm for custom user models

[Django]

#19353: Make it easier to extend UserCreationForm for custom user models
-+-
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:
 Severity:  Normal   |  1.5-alpha-1
 Keywords:  UserCreationForm |   Resolution:
  AUTH_USER_MODEL| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dp_wiz):

 * cc: aenor.realm@… (added)


Comment:

 On a related note, i've added some fields to my subclass of AbstractUser
 and admin fieldset setting now complains about missing fields from the
 [change] form. The fix is to use get_user_model() in Meta 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  localflavor  |   Resolution:
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by claudep):

 Here are some proposed updated snippets for localflavor documentation:

 For 1.5:
 {{{
 Internationalization of localflavor
 ===

 The legacy ``localflavor`` application has its own catalog of
 translations, in
 the directory ``django/contrib/localflavor/locale``, and it's not loaded
 automatically like Django's general catalog in ``django/conf/locale``. If
 you
 want localflavor's texts to be translated, like form fields error
 messages, you
 must include :mod:`django.contrib.localflavor` in the
 :setting:`INSTALLED_APPS`
 setting, so the internationalization system can find the catalog, as
 explained
 in :ref:`how-django-discovers-translations`.

 For the newly-created ``localflavor`` applications, their behaviour is
 identical
 to any standard Django application, that is the application name (e.g.
 ``django_localflavor_jp``) should be present in the
 :setting:`INSTALLED_APPS`
 setting to activate the translations.
 }}}

 For 1.6:
 {{{
 Internationalization of localflavors
 

 To activate translations for any ``localflavor`` application, it's the
 same
 procedure as with any other standard Django application, that is the
 application
 name (e.g. ``django_localflavor_jp``) should be present in the
 :setting:`INSTALLED_APPS` setting.
 }}}

-- 
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] #19511: Thread safe bound method weakrefs

[Django]

#19511: Thread safe bound method weakrefs
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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 apollo13):

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


Comment:

 Wth did the resolution get set to 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19510: Thread safe template cache

[Django]

#19510: Thread safe template cache
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by apollo13):

 * status:  closed => new
 * resolution:  duplicate =>
 * needs_tests:  0 => 1


Comment:

 Doesn't seem to be a duplicate, only the patch seems to be the same which
 wouldn't make sense. Can you get into more details about the error?

-- 
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] #19511: Thread safe bound method weakrefs

[Django]

#19511: Thread safe bound method weakrefs
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 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 apollo13):

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


Comment:

 Did you attach the wrong patch here?

-- 
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] #19511: Thread safe bound method weakrefs

[Django]

#19511: Thread safe bound method weakrefs
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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 apollo13):

 #19510 was a duplicate.

-- 
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] #19510: Thread safe template cache

[Django]

#19510: Thread safe template cache
---+--
 Reporter:  Kronuz |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 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 apollo13):

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


Comment:

 #19511 seems to be a duplicate but it contains more info so I'll close
 this 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  localflavor  |   Resolution:
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by claudep):

 Translations pushed, thanks Simon!

 Now the documentation can be updated.

-- 
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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+-
 Reporter:  lrekucki |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  reopened => new
 * owner:  Alex => aaugustin


Comment:

 The last failure actually reveals a bug in [4b278131].

-- 
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] #19204: Python2-style exception syntax is still used in django.utils.unittest (and should be updated)

[Django]

#19204: Python2-style exception syntax is still used in django.utils.unittest 
(and
should be updated)
-+---
 Reporter:  garrison |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  py3k | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---

Comment (by Florian Apolloner ):

 In [changeset:"ef98ae2910a6b5c86e1e0b003110455778e63324"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ef98ae2910a6b5c86e1e0b003110455778e63324"
 [1.5.X] Fixed #19204 -- Replaced python2-style exception syntax.

 Thanks to garrison for the report and patch.

 Backport of 4a71b842662162e0892a9269179421ff2191adba 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] ef98ae: [1.5.X] Fixed #19204 -- Replaced python2-style exc...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: ef98ae2910a6b5c86e1e0b003110455778e63324
  
https://github.com/django/django/commit/ef98ae2910a6b5c86e1e0b003110455778e63324
  Author: Florian Apolloner 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M django/utils/unittest/case.py
M django/utils/unittest/loader.py
M django/utils/unittest/main.py
M django/utils/unittest/suite.py

  Log Message:
  ---
  [1.5.X] Fixed #19204 -- Replaced python2-style exception syntax.

Thanks to garrison for the report and patch.

Backport of 4a71b842662162e0892a9269179421ff2191adba 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.

[django/django] 4a71b8: Fixed #19204 -- Replaced python2-style exception s...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4a71b842662162e0892a9269179421ff2191adba
  
https://github.com/django/django/commit/4a71b842662162e0892a9269179421ff2191adba
  Author: Florian Apolloner 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M django/utils/unittest/case.py
M django/utils/unittest/loader.py
M django/utils/unittest/main.py
M django/utils/unittest/suite.py

  Log Message:
  ---
  Fixed #19204 -- Replaced python2-style exception syntax.

Thanks to garrison for the report and patch.



-- 
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] #19204: Python2-style exception syntax is still used in django.utils.unittest (and should be updated)

[Django]

#19204: Python2-style exception syntax is still used in django.utils.unittest 
(and
should be updated)
-+---
 Reporter:  garrison |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  py3k | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---
Changes (by Florian Apolloner ):

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


Comment:

 In [changeset:"4a71b842662162e0892a9269179421ff2191adba"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4a71b842662162e0892a9269179421ff2191adba"
 Fixed #19204 -- Replaced python2-style exception syntax.

 Thanks to garrison for the report and 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 https://groups.google.com/groups/opt_out.

[Django] #19514: form.fields.keyOrder is not supported for AdminForm

[Django]

#19514: form.fields.keyOrder is not supported for AdminForm
---+--
 Reporter:  scorpil|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:  keyOrder, form, django-admin
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 When you have redefined ModelAdmin and redefined ModelForm for
 change_view/add_view, this form will be modified to AdminForm. In process,
 django will automatically create fieldset, if it's not already there, by
 calling get_fieldset (django.contrib.admin.options.py:425):

 {{{
 def get_fieldsets(self, request, obj=None):
 "Hook for specifying fieldsets for the add form."
 if self.declared_fieldsets:
 return self.declared_fieldsets
 form = self.get_form(request, obj)
 fields = list(form.base_fields) +
 list(self.get_readonly_fields(request, obj))
 return [(None, {'fields': fields})]
 }}}

 Obviously, this won't preserve any ordering that may have been specified
 in __self.fields.keyOrder__. I understand why this was implemented in such
 a way: keyOrder is specified (in most cases) when form is initialized, and
 AdminForm is created before that, but it would be great to have ordering
 functionality in place for django-admin, so i propose to think about the
 good way to fix this.

 Steps to reproduce:
 1. Create simple model called, for example, '''CustomModel'''
 2. Create '''ModelForm''' based on this model. Let's call it
 '''CustomModelForm'''.
 3. In the '''CustomModelForm.!__init!__'''
  specify something like '''self.fields.keyOrder =
 self.fields.keyOrder[::-1]'''
 4. Create '''CustomModelAdmin''' that inherits
 '''django.contrib.admin.ModelAdmin'''
 5. Set '''form = CustomModelForm''' under '''CustomModelAdmin'''
 6. Register '''CustomModel''' and '''CustomModelAdmin''' to the
 '''admin_site'''.
 7. Enter '''change_view''' or '''add_view''' from the browser. Order of
 fields stays as it is defined in model, while programmer expects it to be
 reversed.

-- 
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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  Alex
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   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 Aymeric Augustin ):

 In [changeset:"1114d8203ea48f4a1021f59a87954d321d8b1fa5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1114d8203ea48f4a1021f59a87954d321d8b1fa5"
 [1.5.x] Fixed a randomly failing test under Python 3.

 Refs #17758.

 Backport of e8f07f0 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] 1114d8: [1.5.x] Fixed a randomly failing test under Python...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1114d8203ea48f4a1021f59a87954d321d8b1fa5
  
https://github.com/django/django/commit/1114d8203ea48f4a1021f59a87954d321d8b1fa5
  Author: Aymeric Augustin 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M tests/regressiontests/multiple_database/tests.py

  Log Message:
  ---
  [1.5.x] Fixed a randomly failing test under Python 3.

Refs #17758.

Backport of e8f07f0 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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  Alex
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   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 Aymeric Augustin ):

 In [changeset:"e8f07f0378cef5a133028c502ff4064b91cd0611"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e8f07f0378cef5a133028c502ff4064b91cd0611"
 Fixed a randomly failing test under Python 3.

 Refs #17758.
 }}}

-- 
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] e8f07f: Fixed a randomly failing test under Python 3.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e8f07f0378cef5a133028c502ff4064b91cd0611
  
https://github.com/django/django/commit/e8f07f0378cef5a133028c502ff4064b91cd0611
  Author: Aymeric Augustin 
  Date:   2012-12-24 (Mon, 24 Dec 2012)

  Changed paths:
M tests/regressiontests/multiple_database/tests.py

  Log Message:
  ---
  Fixed a randomly failing test under Python 3.

Refs #17758.



-- 
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] #19204: Python2-style exception syntax is still used in django.utils.unittest (and should be updated)

[Django]

#19204: Python2-style exception syntax is still used in django.utils.unittest 
(and
should be updated)
-+---
 Reporter:  garrison |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  py3k | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---

Comment (by claudep):

 The required changes are really minor, go 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19204: Python2-style exception syntax is still used in django.utils.unittest (and should be updated)

[Django]

#19204: Python2-style exception syntax is still used in django.utils.unittest 
(and
should be updated)
-+---
 Reporter:  garrison |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  py3k | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  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] #19204: Python2-style exception syntax is still used in django.utils.unittest (and should be updated)

[Django]

#19204: Python2-style exception syntax is still used in django.utils.unittest 
(and
should be updated)
-+---
 Reporter:  garrison |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  1.5-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  py3k | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---
Changes (by aaugustin):

 * severity:  Normal => Release blocker


Comment:

 Eventually I've changed my mind on this.

 There are only 4 except statements to change. And the backport of
 unittest2 will go away as soon as we drop support for Python 2.6.

 If we agree to make this change, let's do it before 1.5 final.

-- 
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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  Alex
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   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 aaugustin):

 I managed to reproduce these failures locally:
 - `cache.CacheI18nTest.test_middleware_with_streaming_response` always
 fails
 - `multiple_database.AuthTestCase.test_dumpdata` fails randomly

-- 
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] #17758: Do not depend on dict order in test suite

[Django]

#17758: Do not depend on dict order in test suite
-+
 Reporter:  lrekucki |Owner:  Alex
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

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


Comment:

 Thanks Luke!

 I just set up the CI server to run the test suite under Python 3.3, and I
 got three failures during the first run:
 
http://ci.djangoproject.com/job/Django/2137/database=sqlite3,python=python3.3/testReport/

 In case that's relevant — the CI server uses Python 3.3 provided by
 http://ppa.launchpad.net/fkrull/deadsnakes/ubuntu/

-- 
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] #19513: Annotate broken django.db.backends.oracle while updating

[Django]

#19513: Annotate broken django.db.backends.oracle while updating
--+
 Reporter:  mengzhuo1203@…|  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
--+
 An QuerySet operation like:
 Combination.objects.all().update(tag='TagName')

 The structure like:
 {{{
 class Combination:
 items = ForeignKey(Item)
 }}}
 {{{
 CombinationManager:
 def get_query_set(self):
 qs = super(CombinationManager, self).get_query_set()
 qs = qs.annotate(price=Sum('items__price'))
 }}}
 The SQLite and MySQL runs fine with such structure, not with Oracle, it
 will encounter "ORA-00913: too many values"

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