Re: [Django] #16724: fix admin interface permission bug

[Django]

#16724: fix admin interface permission bug
--+---
   Reporter:  Kidwind |  Owner:  nobody
   Type:  Bug | Status:  closed
  Milestone:  |  Component:  contrib.admin
Version:  SVN |   Severity:  Normal
 Resolution:  duplicate   |   Keywords:  permission
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by julien):

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


Comment:

 Kidwind, it is appreciated that you're taking the time to report bugs or
 feature requests, however it is the second time after #16424 that you
 create a ticket without any description and that you post a whole file as
 attachment. In the future, please elaborate a bit more on your requests
 and please post diff files so that one can more easily see what it is
 exactly that you'd like to change.

 In this particular case, this is a duplicate of #11124.

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

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

[Django] #16724: fix admin interface permission bug

[Django]

#16724: fix admin interface permission bug
+---
 Reporter:  Kidwind |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  contrib.admin
  Version:  SVN |   Severity:  Normal
 Keywords:  permission  |   Triage Stage:  Unreviewed
Has patch:  1   |  Easy pickings:  0
UI/UX:  0   |
+---


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

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

Re: [Django] #16722: import psycopg2.Error breaks psycopg2 backend

[Django]

#16722: import psycopg2.Error breaks psycopg2 backend
-+-
   Reporter:  Ubercore   |  Owner:  anonymous
   Type:  Bug| Status:  closed
  Milestone:  1.4|  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution:  fixed  |   Severity:  Release blocker
   Triage Stage: |   Keywords:  psycopg2 Error
  Unreviewed |  postgresql import
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by russellm):

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


Comment:

 This has been resolved independently by [16710]

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

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

Re: [Django] #16722: import psycopg2.Error breaks psycopg2 backend

[Django]

#16722: import psycopg2.Error breaks psycopg2 backend
-+-
   Reporter:  Ubercore   |  Owner:  anonymous
   Type:  Bug| Status:  assigned
  Milestone:  1.4|  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Release blocker
   Triage Stage: |   Keywords:  psycopg2 Error
  Unreviewed |  postgresql import
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by anonymous):

 by removing the line 25, the django psycopg2 works again.
 Sad to see that the SVN is not working tonight :(

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

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

Re: [Django] #13: Related objects interface should be tighter (edit_inline)

[Django]

#13: Related objects interface should be tighter (edit_inline)
-+-
   Reporter:  adrian |  Owner:  barbuza
   Type:  New| Status:  reopened
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  nfa-someday nfa-
 Resolution: |  changelist
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by mhf@…):

 * cc: mhf@… (removed)
 * ui_ux:   => 0
 * easy:   => 0


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

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

[Changeset] r16710 - django/trunk/django/db/backends/postgresql_psycopg2

[noreply]

Author: Honza_Kral
Date: 2011-08-29 16:01:25 -0700 (Mon, 29 Aug 2011)
New Revision: 16710

Modified:
   django/trunk/django/db/backends/postgresql_psycopg2/base.py
Log:
Follow the same convention as the rest of the file.

Still cleanup after [16708]

Modified: django/trunk/django/db/backends/postgresql_psycopg2/base.py
===
--- django/trunk/django/db/backends/postgresql_psycopg2/base.py 2011-08-29 
17:28:15 UTC (rev 16709)
+++ django/trunk/django/db/backends/postgresql_psycopg2/base.py 2011-08-29 
23:01:25 UTC (rev 16710)
@@ -19,7 +19,6 @@
 try:
 import psycopg2 as Database
 import psycopg2.extensions
-import psycopg2.Error
 except ImportError, e:
 from django.core.exceptions import ImproperlyConfigured
 raise ImproperlyConfigured("Error loading psycopg2 module: %s" % e)
@@ -125,7 +124,7 @@
 try:
 self.connection.close()
 self.connection = None
-except psycopg2.Error:
+except Database.Error:
 # In some cases (database restart, network connection lost etc...)
 # the connection to the database is lost without giving Django a
 # notification. If we don't set self.connection to None, the error

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

Re: [Django] #16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 2

[Django]

#16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 
2
--+-
   Reporter:  rfugger |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Template system
Version:  SVN |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+-
Changes (by AdamG):

 * cc: adam@… (added)
 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Patch to fix w/ tests attached.

 I agree that it would make sense for 1.0 to also be pluralized, however, I
 didnt make that change in this patch for three reasons:

 * It turns this from a one-line change to something significantly more
 complex, since we have to treat the strings "1" and "1.0" differently
 * It could break people's existing code, if they don't realize they're
 passing in a float
 * Where "1.0 pounds" is desired instead of "1 pound"/"1.1 pounds",
 pluralize wouldn't be needed in the first place, the template would just
 be:

 {{{
 {{ weight|floatformat:1 }} pounds
 }}}

 With this patch, for "1 pound" & "1.1 pounds", we can do:

 {{{
 {{ weight|floatformat }} pound{{ weight|pluralize }}
 }}}
 This is consistent with the decision made in #12380.

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

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

[Django] #16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 2

[Django]

#16723: Pluralize filter shouldn't pluralize decimal/float values between 1 and 
2
-+-
 Reporter:  rfugger  |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  Template system
  Version:  SVN  |   Severity:  Normal
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+-
 The pluralize filter's support for floating point/decimal numbers is
 buggy.  Its check for plurality is:

 {{{
 if int(value) != 1
 }}}

 which unfortunately catches floats 1.0 < x < 2.0 that shouldn't be
 pluralized in English.

 Example:

 {{{
 pound{{ weight|pluralize:"s" }}
 }}}

 When `weight` is 1.3, this gives "1.3 pound", which is incorrect.  "1.3
 pounds" is the expected result.

 The filter should probably also pluralize 1.0 when it is given as a
 floating point/decimal number, because native speakers will generally
 pluralize all decimal numbers.  ("One-point-oh hours," not "One-point-oh
 hour".)

 Reference:
 http://www.englishforums.com/English/1119PluralOrSingular/wdvmb/post.htm#684376

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

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

Re: [Django] #16722: import psycopg2.Error breaks psycopg2 backend

[Django]

#16722: import psycopg2.Error breaks psycopg2 backend
-+-
   Reporter:  Ubercore   |  Owner:  anonymous
   Type:  Bug| Status:  assigned
  Milestone:  1.4|  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Release blocker
   Triage Stage: |   Keywords:  psycopg2 Error
  Unreviewed |  postgresql import
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by Ubercore):

 * keywords:   => psycopg2 Error postgresql import


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

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

Re: [Django] #16722: import psycopg2.Error breaks psycopg2 backend

[Django]

#16722: import psycopg2.Error breaks psycopg2 backend
-+-
   Reporter:  Ubercore   |  Owner:  anonymous
   Type:  Bug| Status:  assigned
  Milestone:  1.4|  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Release blocker
   Triage Stage: |   Keywords:
  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by apollo13):

 * milestone:   => 1.4


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

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

Re: [Django] #16722: import psycopg2.Error breaks psycopg2 backend

[Django]

#16722: import psycopg2.Error breaks psycopg2 backend
-+-
   Reporter:  Ubercore   |  Owner:  anonymous
   Type:  Bug| Status:  assigned
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Release blocker
   Triage Stage: |   Keywords:
  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by apollo13):

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


Comment:

 + a direct import seems to be impossible 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #16722: import psycopg2.Error breaks psycopg2 backend

[Django]

#16722: import psycopg2.Error breaks psycopg2 backend
--+--
 Reporter:  Ubercore  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Database layer (models, ORM)
  Version:  SVN   |   Severity:  Release blocker
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  0
UI/UX:  0 |
--+--
 The Error class doesn't need to be imported directly. Instead,
 Database.Error can be used.

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

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

Re: [Django] #4982: {% blocktrans %} does not escape % in text

[Django]

#4982: {% blocktrans %} does not escape % in text
-+-
   Reporter:  nostgard   |  Owner:  permon
     | Status:  closed
   Type: |  Component:
  Uncategorized  |  Internationalization
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  sprintsept14
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-
Changes (by claudep):

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


Comment:

 FYI, I've reopened the issue with patch/test case in #16721.

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

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

Re: [Django] #16721: Blocktrans does not handle correctly litteral percents (%) in content

[Django]

#16721: Blocktrans does not handle correctly litteral percents (%) in content
-+-
   Reporter:  claudep|  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:
Version:  SVN|  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  |
-+-
Changes (by claudep):

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


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

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

[Django] #16721: Blocktrans does not handle correctly litteral percents (%) in content

[Django]

#16721: Blocktrans does not handle correctly litteral percents (%) in content
-+--
 Reporter:  claudep  |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:  1.4  |  Component:  Internationalization
  Version:  SVN  |   Severity:  Normal
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+--
 When a string inside a blocktrans tag contains litteral percent signs, the
 matching translation is not retrieved, because escaping is done too late
 in the render code of blocktrans. Patch follows.

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

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

[Changeset] r16709 - django/trunk/django/db/backends/postgresql_psycopg2

[noreply]

Author: Honza_Kral
Date: 2011-08-29 10:28:15 -0700 (Mon, 29 Aug 2011)
New Revision: 16709

Modified:
   django/trunk/django/db/backends/postgresql_psycopg2/base.py
Log:
Forgotten import in [16708]

Modified: django/trunk/django/db/backends/postgresql_psycopg2/base.py
===
--- django/trunk/django/db/backends/postgresql_psycopg2/base.py 2011-08-29 
15:55:06 UTC (rev 16708)
+++ django/trunk/django/db/backends/postgresql_psycopg2/base.py 2011-08-29 
17:28:15 UTC (rev 16709)
@@ -19,6 +19,7 @@
 try:
 import psycopg2 as Database
 import psycopg2.extensions
+import psycopg2.Error
 except ImportError, e:
 from django.core.exceptions import ImproperlyConfigured
 raise ImproperlyConfigured("Error loading psycopg2 module: %s" % e)

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

Re: [Django] #16687: Several tests requiring internet fail on Ubuntu build machines

[Django]

#16687: Several tests requiring internet fail on Ubuntu build machines
-+---
   Reporter:  barry@…|  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Testing framework
Version:  1.3|   Severity:  Normal
 Resolution:  duplicate  |   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):

 These machines, which build packages from source for both the Ubuntu
 archive and PPAs.

 https://launchpad.net/builders/

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

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

Re: [Django] #15802: Django stops functioning when the database (PostgreSQL) closes the connection

[Django]

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

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


Comment:

 In [16708]:
 {{{
 #!CommitTicketReference repository="" revision="16708"
 Fixed #15802 -- pyscopg2 sometimes fail to close the connection when it's
 already closed by the server, Thanks Rick van Hattem
 }}}

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

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

[Changeset] r16708 - django/trunk/django/db/backends/postgresql_psycopg2

[noreply]

Author: Honza_Kral
Date: 2011-08-29 08:55:06 -0700 (Mon, 29 Aug 2011)
New Revision: 16708

Modified:
   django/trunk/django/db/backends/postgresql_psycopg2/base.py
Log:
Fixed #15802 -- pyscopg2 sometimes fail to close the connection when it's 
already closed by the server, Thanks Rick van Hattem

Modified: django/trunk/django/db/backends/postgresql_psycopg2/base.py
===
--- django/trunk/django/db/backends/postgresql_psycopg2/base.py 2011-08-28 
14:43:51 UTC (rev 16707)
+++ django/trunk/django/db/backends/postgresql_psycopg2/base.py 2011-08-29 
15:55:06 UTC (rev 16708)
@@ -14,6 +14,7 @@
 from django.db.backends.postgresql_psycopg2.version import get_version
 from django.db.backends.postgresql_psycopg2.introspection import 
DatabaseIntrospection
 from django.utils.safestring import SafeUnicode, SafeString
+from django.utils.log import getLogger
 
 try:
 import psycopg2 as Database
@@ -29,6 +30,8 @@
 psycopg2.extensions.register_adapter(SafeString, 
psycopg2.extensions.QuotedString)
 psycopg2.extensions.register_adapter(SafeUnicode, 
psycopg2.extensions.QuotedString)
 
+logger = getLogger('django.db.backends')
+
 class CursorWrapper(object):
 """
 A thin wrapper around psycopg2's normal cursor class so that we can catch
@@ -114,6 +117,24 @@
 self.cursor().execute('SET CONSTRAINTS ALL IMMEDIATE')
 self.cursor().execute('SET CONSTRAINTS ALL DEFERRED')
 
+def close(self):
+if self.connection is None:
+return
+
+try:
+self.connection.close()
+self.connection = None
+except psycopg2.Error:
+# In some cases (database restart, network connection lost etc...)
+# the connection to the database is lost without giving Django a
+# notification. If we don't set self.connection to None, the error
+# will occur a every request.
+self.connection = None
+logger.warning('psycopg2 error while closing the connection.',
+exc_info=sys.exc_info()
+)
+raise
+
 def _get_pg_version(self):
 if self._pg_version is None:
 self._pg_version = get_version(self.connection)

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

Re: [Django] #16659: Change-list toplinks (date drilldown) should not have fixed width

[Django]

#16659: Change-list toplinks (date drilldown) should not have fixed width
-+-
   Reporter:  mofle  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  contrib.admin
  Milestone:  1.4|   Severity:  Normal
Version:  SVN|   Keywords:  admin, list_filter,
 Resolution: |  default
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  1  |
-+-
Changes (by mofle):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---

Comment (by jsdalton):

 Patch wasn't applying cleanly 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16678: Write tests for django.contrib.redirects

[Django]

#16678: Write tests for django.contrib.redirects
-+-
   Reporter:  julien |  Owner:  martin.speleo
   Type: | Status:  new
  Cleanup/optimization   |  Component:  contrib.redirects
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by martin.speleo@…):

 * owner:  nobody => martin.speleo
 * cc: martin.speleo@… (added)


Comment:

 I will have a go at writing these tests, as long as that is not treading
 on anyones toes.

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

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

Re: [Django] #11603: Add an assertFormSetError function to django.test.TestCase

[Django]

#11603: Add an assertFormSetError function to django.test.TestCase
-+-
   Reporter: |  Owner:  martin_speleo
  martin_speleo  | Status:  new
   Type:  New|  Component:  Testing framework
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  formset
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by martin_speleo):

 * needs_better_patch:  1 => 0


Comment:

 I have modified the code and documentation, as suggested, to take a
 form_index parameter rather than a form parameter.

 I have resolved the failures of the test.  The issue was the default value
 of the longMessage variable (Boolean) in the unittest module.  I have now
 checked that the tests work using python 2.6 and python 2.7, with and
 without unittest2 available.  The documentation building has also been
 checked.

 For AssertFormsetError the error messages are slightly clearer with
 longMessage set to False, however I have not set this parameter in order
 to stay consistent with the other test functions eg. AssertFormError.

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

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

Re: [Django] #16720: staticfiles_urlpatterns looks for files in MEDIA_ROOT, not STATIC_ROOT

[Django]

#16720: staticfiles_urlpatterns looks for files in MEDIA_ROOT, not STATIC_ROOT
-+-
   Reporter:  dramon@…   |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  contrib.staticfiles
Version:  1.3|   Severity:  Normal
 Resolution:  invalid|   Keywords:  staticfiles
   Triage Stage: |  STATIC_ROOT
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by jezdez):

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


Comment:

 This works as expected; see
 https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles
 /#staticfiles-finders for

 STATIC_ROOT is the location the collectstatic management command deploys
 file **to**, not collects from.

 The `DefaultStorageFinder` finder is simply a helper to include the files
 stored by the default storage backend (which is used for file uploads).

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

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

[Django] #16720: staticfiles_urlpatterns looks for files in MEDIA_ROOT, not STATIC_ROOT

[Django]

#16720: staticfiles_urlpatterns looks for files in MEDIA_ROOT, not STATIC_ROOT
-+-
 Reporter:  dramon@… |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  contrib.staticfiles
  Version:  1.3  |   Severity:  Normal
 Keywords:  staticfiles STATIC_ROOT  |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+-
 {{{
 In new project I set this:
 MEDIA_ROOT = '/someprj/media/'
 MEDIA_URL = '/media/'
 STATIC_ROOT = '/someprj/static/'
 STATIC_URL = '/static/'
 STATICFILES_FINDERS = (
 #'django.contrib.staticfiles.finders.FileSystemFinder',
 #'django.contrib.staticfiles.finders.AppDirectoriesFinder',
 'django.contrib.staticfiles.finders.DefaultStorageFinder',
 )

 In urls.py I added at the end:
 urlpatterns += staticfiles_urlpatterns()

 In directory /someprj/static/ exists file test.txt
 When I try to access this file on http://localhost:8000/static/test.txt
 error page is returned.
 When a copy this file to /someprj/media/, Django shows it.
 }}}

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

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

Re: [Django] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---
Changes (by bberes):

 * cc: botondus@… (added)


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

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

Re: [Django] #13024: Signal sent on application startup

[Django]

#13024: Signal sent on application startup
-+-
   Reporter:  wojteks|  Owner:  nobody
   Type:  New| Status:  closed
  feature|  Component:  Core (Other)
  Milestone: |   Severity:  Normal
Version: |   Keywords:
 Resolution:  fixed  |  Has patch:  0
   Triage Stage:  Fixed on   |Needs tests:  0
  a branch   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * status:  new => closed
 * resolution:   => fixed
 * stage:  Accepted => Fixed on a branch


Comment:

 Closing as this is fixed in a branch which needs review. See #3591.

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

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

Re: [Django] #13024: Signal sent on application startup

[Django]

#13024: Signal sent on application startup
---+--
   Reporter:  wojteks  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Core (Other)
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|
---+--
Changes (by guettli):

 * cc: hv@… (added)


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

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

Re: [Django] #13024: Signal sent on application startup

[Django]

#13024: Signal sent on application startup
---+--
   Reporter:  wojteks  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Core (Other)
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|
---+--
Changes (by guettli):

 * version:  1.1 =>


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

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

Re: [Django] #13024: Signal sent on application startup

[Django]

#13024: Signal sent on application startup
---+--
   Reporter:  wojteks  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Core (Other)
Version:  1.1  |   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 guettli):

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


Comment:

 There is a workaround on stackoverflow:
 http://stackoverflow.com/questions/2781383/where-to-put-django-startup-
 code

 I think this workaround is ugly, a better solution is needed.

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

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

[Django] #16719: Support for symlinking to whole app directories for staticfiles

[Django]

#16719: Support for symlinking to whole app directories for staticfiles
-+-
 Reporter:  mitar|  Owner:  nobody
 Type:  New feature  | Status:  new
Milestone:   |  Component:  contrib.staticfiles
  Version:  1.3  |   Severity:  Normal
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+-
 It would be useful to support also symlinking whole (top) app static
 directories and not just every and each file, with collectstatic manage
 command. In this way it would not be necessary to rerun the manage command
 every time you add some files to the app.

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

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

[Django] #16718: check_for_language fails when django are imported from zip file

[Django]

#16718: check_for_language fails when django are imported from zip file
+--
 Reporter:  jsantana@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  Translations
  Version:  1.2 |   Severity:  Normal
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+--
 If you import django from a zip file and some i18n utils fail (i.e
 django.views.i18n.javascript_catalog)

 Steps:

 1. import django as zip file
 2. setup a javascript translation different from default with some
 strings, i.e locale/es/LC_MESSAGES/djangojs.{po,mo}
 3. setup javascript_catalog view
 4. make a request like http://server/i18n/?language=es

 - expected result:
 spanish catalog should be returned in javascript file

 - result:
 default language catalog is returned in javascript 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10895: Improvements in BRCPFField and BRCNPJField in localflavor.br.forms

[Django]

#10895: Improvements in BRCPFField and BRCNPJField in localflavor.br.forms
-+-
   Reporter:  luizvital  |  Owner:  waa
   Type:  Bug| Status:  assigned
  Milestone: |  Component:  contrib.localflavor
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  localflavor
   Triage Stage:  Accepted   |  brcpffield, brcpnjfield, br,
Needs documentation:  0  |  localflavor
Patch needs improvement:  1  |  Has patch:  1
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by semente):

 * cc: semente+django@… (added)
 * ui_ux:   => 0
 * easy:   => 0


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

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