Re: [Django] #3233: manage.py reset fails to handle valid sql file

[Django]

#3233: manage.py reset fails to handle valid sql file
--+-
  Reporter:  chris_br...@redback.com  | Owner:  nobody  
Status:  closed   | Milestone:  
 Component:  django-admin.py  |   Version:  0.95
Resolution:  wontfix  |  Keywords:  
d...@simon.net.nz
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 As per #14268, we're deprecating sqlreset and family.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14268: reset and sqlreset management commands should raise PendingDeprecationWarning for 1.3

[Django]

#14268: reset and sqlreset management commands should raise
PendingDeprecationWarning for 1.3
+---
  Reporter:  carljm | Owner:  laurentluce
Status:  assigned   | Milestone:  1.3
 Component:  django-admin.py|   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * component:  Uncategorized => django-admin.py
  * stage:  Accepted => Ready for checkin

Old description:

> These commands break a lot and should be deprecated.

New description:

 These commands break a lot and should be deprecated.

 The underlying problem was reported as #2493; it's been duplicated a
 couple of times (#7731, #9348). Resetting individual tables is a hard
 problem; Django can't be a substitute for a good DBA in this case.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #2225: 'manage.py sql ...' gets confused when using tables from separate apps

[Django]

#2225: 'manage.py sql ...' gets confused when using tables from separate apps
---+
  Reporter:  Lucas Hazel   | Owner:  
glassresistor
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:  fixed |  Keywords: 
  
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 I'm pretty sure this problem doesn't exist anymore.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14391: update man django-admin.1 to include missing commands

[Django]

#14391: update man django-admin.1 to include missing commands
--+-
  Reporter:  laurentluce  | Owner:  laurentluce
Status:  assigned | Milestone:  1.3
 Component:  django-admin.py  |   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by laurentluce):

  * stage:  Unreviewed => Accepted

Comment:

 Accepted after feedback from Russell.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14268: reset and sqlreset management commands should raise PendingDeprecationWarning for 1.3

[Django]

#14268: reset and sqlreset management commands should raise
PendingDeprecationWarning for 1.3
+---
  Reporter:  carljm | Owner:  laurentluce
Status:  assigned   | Milestone:  1.3
 Component:  Uncategorized  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by laurentluce):

  * has_patch:  0 => 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14268: reset and sqlreset management commands should raise PendingDeprecationWarning for 1.3

[Django]

#14268: reset and sqlreset management commands should raise
PendingDeprecationWarning for 1.3
+---
  Reporter:  carljm | Owner:  laurentluce
Status:  assigned   | Milestone:  1.3
 Component:  Uncategorized  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by laurentluce):

  * status:  new => assigned

Comment:

 - added PendingDeprecationWarning to reset command in
 django/core/management/commands/reset.py
 - added PendingDeprecationWarning to sqlreset in
 django/core/management/sql.py
 - updated docs/releases/1.3.txt and docs/ref/django-admin.txt

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14268: reset and sqlreset management commands should raise PendingDeprecationWarning for 1.3

[Django]

#14268: reset and sqlreset management commands should raise
PendingDeprecationWarning for 1.3
+---
  Reporter:  carljm | Owner:  laurentluce
Status:  new| Milestone:  1.3
 Component:  Uncategorized  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by laurentluce):

  * owner:  nobody => laurentluce

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14391: update man django-admin.1 to include missing commands

[Django]

#14391: update man django-admin.1 to include missing commands
--+-
  Reporter:  laurentluce  | Owner:  laurentluce
Status:  assigned | Milestone:  1.3
 Component:  django-admin.py  |   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by laurentluce):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14391: update man django-admin.1 to include missing commands

[Django]

#14391: update man django-admin.1 to include missing commands
-+--
 Reporter:  laurentluce  |   Owner:  laurentluce
   Status:  new  |   Milestone:  1.3
Component:  django-admin.py  | Version:  1.2
 Keywords:   |   Stage:  Unreviewed 
Has_patch:  0|  
-+--


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13870: psycopg2 backend never terminates isolating transactions

[Django]

#13870: psycopg2 backend never terminates isolating transactions
---+
  Reporter:  patrys| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by davidr):

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

Comment:

 I ran into to this problem from Django 1.0 and ended up using the
 following workaround to explicitly close the connection after the model
 was used.
 {{{
 from django.db import connection
 connection.close()
 }}}
 In my case there was a shared table lock which ended up being held by the
 process using the model classes (because of the uncommited transaction)
 which in turn caused a deadlock as another process requiring an exclusive
 lock on the table would block forever.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] r13984 - django/trunk/docs/topics

[noreply]

Author: russellm
Date: 2010-10-04 20:44:12 -0500 (Mon, 04 Oct 2010)
New Revision: 13984

Modified:
   django/trunk/docs/topics/logging.txt
Log:
Refs #14388 -- ... and corrected the naming of a formatter in the sample 
logging config.

Modified: django/trunk/docs/topics/logging.txt
===
--- django/trunk/docs/topics/logging.txt2010-10-05 01:42:20 UTC (rev 
13983)
+++ django/trunk/docs/topics/logging.txt2010-10-05 01:44:12 UTC (rev 
13984)
@@ -241,7 +241,7 @@
 'version': 1,
 'disable_existing_loggers': True,
 'formatters': {
-'explicit': {
+'verbose': {
 'format': '%(levelname)s %(asctime)s %(module)s %(process)d 
%(thread)d %(message)s'
 },
 'simple': {

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] r13983 - django/trunk/docs/topics

[noreply]

Author: russellm
Date: 2010-10-04 20:42:20 -0500 (Mon, 04 Oct 2010)
New Revision: 13983

Modified:
   django/trunk/docs/topics/logging.txt
Log:
Refs #14388 -- Corrected another spelling erorr.

Modified: django/trunk/docs/topics/logging.txt
===
--- django/trunk/docs/topics/logging.txt2010-10-05 00:11:41 UTC (rev 
13982)
+++ django/trunk/docs/topics/logging.txt2010-10-05 01:42:20 UTC (rev 
13983)
@@ -193,7 +193,7 @@
 * ``logger.log()``: Manually emits a logging message with a
   specific log level.
 
-* ``logger.exception()``: Creates an ``ERORR`` level logging
+* ``logger.exception()``: Creates an ``ERROR`` level logging
   message wrapping the current exception stack frame.
 
 Configuring logging

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #2407: CGI Support for django

[Django]

#2407: CGI Support for django
--+-
  Reporter:  Martin Glueck   | Owner:  
nobody
Status:  closed   | Milestone:  
  
 Component:  Core framework   |   Version:  
1.1   
Resolution:  wontfix  |  Keywords:  
cgi   
 Stage:  Design decision needed   | Has_patch:  
1 
Needs_docs:  0|   Needs_tests:  
1 
Needs_better_patch:  1|  
--+-
Changes (by russellm):

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

Comment:

 Django doesn't support CGI for deployment, and Trac isn't a user support
 forum. If you have a howto question, please ask on Django-users, but be
 advised -- Django doesn't support CGI for a very good reason.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #2407: CGI Support for django

[Django]

#2407: CGI Support for django
--+-
  Reporter:  Martin Glueck   | Owner:  
nobody
Status:  reopened | Milestone:  
  
 Component:  Core framework   |   Version:  
1.1   
Resolution:   |  Keywords:  
cgi   
 Stage:  Design decision needed   | Has_patch:  
1 
Needs_docs:  0|   Needs_tests:  
1 
Needs_better_patch:  1|  
--+-
Changes (by DremLIN):

  * status:  closed => reopened
  * version:  SVN => 1.1
  * resolution:  wontfix =>
  * summary:  [patch] CGI Support for django => CGI Support for django

Comment:

 Hello,

 In my hosting, I have: Python 2.3 run with Apache 1.3 as CGI. I install
 Django 1.1.2, but can't run "mysite" application.

 I try dj_wsgiref_cgihandler.py by limon and I get error:
 Status: 500 Dude, this is whack! A server error occurred. Please contact
 the administrator.

 Please give me working example index.cgi for CGI.2.py (6.8 kB) by Martin
 or CGI_Server.py (1.2 kB) by Martin.

 My e-mail: dremlin.ru [at] gmail.com

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14023: Better example for the custom form template

[Django]

#14023: Better example for the custom form template
+---
  Reporter:  konryd | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14384: Installation documentation should avoid sys.path.append

[Django]

#14384: Installation documentation should avoid sys.path.append
+---
  Reporter:  monokrome  | Owner:  wogan 
   
Status:  assigned   | Milestone:  1.3   
   
 Component:  Documentation  |   Version:  1.2   
   
Resolution: |  Keywords:  documentation apache 
mod_wsgi
 Stage:  Ready for checkin  | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13914: Add natural keys to contrib.auth.User and Group models

[Django]

#13914: Add natural keys to contrib.auth.User and Group models
-+--
  Reporter:  jbochi  | Owner:  nobody   
   
Status:  new | Milestone:  1.3  
   
 Component:  Authentication  |   Version:  SVN  
   
Resolution:  |  Keywords:  Contrib, Auth, User, 
Group, natural keys
 Stage:  Accepted| Has_patch:  1
   
Needs_docs:  1   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Changes (by PaulM):

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

Comment:

 At the very least this patch still needs tests and documentation before
 it's RFC. I'm agnostic about the actual functionality.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] r13982 - in django/trunk/docs: ref topics

[noreply]

Author: russellm
Date: 2010-10-04 19:11:41 -0500 (Mon, 04 Oct 2010)
New Revision: 13982

Modified:
   django/trunk/docs/ref/settings.txt
   django/trunk/docs/topics/logging.txt
Log:
Fixed #14388 -- Corrected some typos in the logging docs. Thanks to varikin, 
gremmie, Ramiro Morales and Gabriel Hurley for the reviews.

Modified: django/trunk/docs/ref/settings.txt
===
--- django/trunk/docs/ref/settings.txt  2010-10-04 15:12:39 UTC (rev 13981)
+++ django/trunk/docs/ref/settings.txt  2010-10-05 00:11:41 UTC (rev 13982)
@@ -1006,11 +1006,13 @@
 A tuple of directories where Django looks for translation files.
 See :ref:`using-translations-in-your-own-projects`.
 
-.. setting:: LOGIN_REDIRECT_URL
+.. setting:: LOGGING
 
 LOGGING
 ---
 
+.. versionadded:: 1.3
+
 Default: A logging configuration dictionary.
 
 A data structure containing configuration information. The contents of
@@ -1020,11 +1022,13 @@
 The default logging configuration passes HTTP 500 server errors to an
 email log handler; all other log messages are given to a NullHandler.
 
-.. versionadded:: 1.3
+.. setting:: LOGGING_CONFIG
 
 LOGGING_CONFIG
 --
 
+.. versionadded:: 1.3
+
 Default: ``'django.utils.log.dictConfig'``
 
 A path to a callable that will be used to configure logging in the
@@ -1036,7 +1040,7 @@
 
 .. _dictConfig: http://docs.python.org/library/logging.html#logging.dictConfig
 
-.. versionadded:: 1.3
+.. setting:: LOGIN_REDIRECT_URL
 
 LOGIN_REDIRECT_URL
 --

Modified: django/trunk/docs/topics/logging.txt
===
--- django/trunk/docs/topics/logging.txt2010-10-04 15:12:39 UTC (rev 
13981)
+++ django/trunk/docs/topics/logging.txt2010-10-05 00:11:41 UTC (rev 
13982)
@@ -35,7 +35,7 @@
 A logger is the entry point into the logging system. Each logger is
 a named bucket to which messages can be written for processing.
 
-A logger is configured to have *log level*. This log level describes
+A logger is configured to have a *log level*. This log level describes
 the severity of the messages that the logger will handle. Python
 defines the following log levels:
 
@@ -59,7 +59,7 @@
 stack trace or an error code.
 
 When a message is given to the logger, the log level of the message is
-compare to the log level of the logger. If the log level of the
+compared to the log level of the logger. If the log level of the
 message meets or exceeds the log level of the logger itself, the
 message will undergo further processing. If it doesn't, the message
 will be ignored.
@@ -84,7 +84,7 @@
 different log level. In this way, it is possible to provide different
 forms of notification depending on the importance of a message. For
 example, you could install one handler that forwards ``ERROR`` and
-``CRITICIAL`` messages to a paging service, while a second handler
+``CRITICAL`` messages to a paging service, while a second handler
 logs all messages (including ``ERROR`` and ``CRITICAL`` messages) to a
 file for later analysis.
 
@@ -143,7 +143,7 @@
 error log record will be written.
 
 Naming loggers
-~~
+--
 
 The call to :meth:`logging.getLogger()` obtains (creating, if
 necessary) an instance of a logger. The logger instance is identified
@@ -177,7 +177,7 @@
 can turn off this behavior.
 
 Making logging calls
-
+
 
 The logger instance contains an entry method for each of the default
 log levels:
@@ -190,10 +190,10 @@
 
 There are two other logging calls available:
 
-* ``logger.log()``: manually a logging message with a specific
-  log level.
+* ``logger.log()``: Manually emits a logging message with a
+  specific log level.
 
-* ``logger.exception()``: create a ``ERRORR`` level logging
+* ``logger.exception()``: Creates an ``ERORR`` level logging
   message wrapping the current exception stack frame.
 
 Configuring logging
@@ -204,7 +204,7 @@
 formatters to ensure that logging output is output in a useful way.
 
 Python's logging library provides several techniques to configure
-logging, ranging from a programatic interface to configuration files.
+logging, ranging from a programmatic interface to configuration files.
 By default, Django uses the `dictConfig format`_.
 
 .. note::
@@ -320,15 +320,15 @@
 
 * Defines three handlers:
 
-* ``null``, a NullHandler, which will pass any `DEBUG` or
+* ``null``, a NullHandler, which will pass any ``DEBUG`` or
   higher message to ``/dev/null``.
 
-* ``console``, a StreamHandler, which will print any `DEBUG`
+* ``console``, a StreamHandler, which will print any ``DEBUG``
   message to stdout. This handler uses the `simple` output
   format.
 
 * ``mail_admins``, an AdminEmailHandler, which will email any
-  `ERROR` level message to the site admins. This handler uses
+

Re: [Django] #14390: set_password functionality outside of the User model

[Django]

#14390: set_password functionality outside of the User model
--+-
  Reporter:  k...@lysator.liu.se  | Owner:  nobody
Status:  reopened | Milestone:
 Component:  Authentication   |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by lrekucki):

 Actually, you can... in Python 3. Sorry for the confusion.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14390: set_password functionality outside of the User model

[Django]

#14390: set_password functionality outside of the User model
--+-
  Reporter:  k...@lysator.liu.se  | Owner:  nobody
Status:  reopened | Milestone:
 Component:  Authentication   |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Alex):

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

Comment:

 No, you really can't use that:

 {{{
 >>> class A(object):
 ... def m(self):
 ...return 3
 ...
 >>> class B(object):
 ... pass
 ...
 >>> A.m(B())
 Traceback (most recent call last):
   File "", line 1, in 
 TypeError: unbound method m() must be called with A instance as first
 argument (got B instance instead)
 >>>
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14390: set_password functionality outside of the User model

[Django]

#14390: set_password functionality outside of the User model
--+-
  Reporter:  k...@lysator.liu.se  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Authentication   |   Version:  1.2   
Resolution:  worksforme   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by lrekucki):

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

Comment:

 You don't have to create a User model. If your custom model also has a
 password field, you can just use:
 {{{
 x = MyModel()
 User.set_password(x, "foo")
 }}}

 Alternatively, you can user an anonymous object:
 {{{
 salt_and_hash = User.set_password(object(), "foo").password
 }}}

 If the later is too cumbersome for you, just copy those 2 lines from User
 model.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13795: Add CACHE_KEY_PREFIX setting that prefixes the low-level cache API

[Django]

#13795: Add CACHE_KEY_PREFIX setting that prefixes the low-level cache API
---+
  Reporter:  bruth | Owner:  bruth
Status:  assigned  | Milestone:  1.3  
 Component:  Cache system  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by agabel):

  * needs_better_patch:  1 => 0
  * milestone:  => 1.3

Comment:

 My last patch had a few problems with file based caching.  The latest is
 up to date with trunk and passes all tests.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14346: Url patterns double slash // problem

[Django]

#14346: Url patterns double slash // problem
+---
  Reporter:  mihneagiurgea  | Owner:  nobody
Status:  closed | Milestone:
 Component:  HTTP handling  |   Version:  1.2   
Resolution:  invalid|  Keywords:  url patterns, double slash
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by dan_head):

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

Comment:

 I've seen this before and it's usually an Apace/mod_rewrite issue.  Have a
 look at this [http://stackoverflow.com/q/831355 Stack Overflow
 Question/Answer]

 I'm going to close this ticket as invalid since The META variables should
 come directly from the server.  If you see some evidence that the web
 server is sending the right values and it is Django that is somehow
 modifying them then please reopen.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
  Reporter:  jdunck| Owner:  laurentluce
Status:  assigned  | Milestone:  1.3
 Component:  Contrib apps  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by laurentluce):

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

Comment:

 - add method get_url to Site model to return an absolute url based on a
 relative path passed as an argument.[[BR]]

 - add site_url template tag doing the same

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
  Reporter:  jdunck| Owner:  laurentluce
Status:  assigned  | Milestone:  1.3
 Component:  Contrib apps  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by laurentluce):

  * status:  new => assigned

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
  Reporter:  jdunck| Owner:  laurentluce
Status:  new   | Milestone:  1.3
 Component:  Contrib apps  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by laurentluce):

  * owner:  anonymous => laurentluce
  * status:  assigned => new

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
  Reporter:  jdunck| Owner:  anonymous
Status:  assigned  | Milestone:  1.3  
 Component:  Contrib apps  |   Version:  1.0  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * owner:  laurentluce => anonymous
  * status:  new => assigned

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
  Reporter:  jdunck| Owner:  laurentluce
Status:  new   | Milestone:  1.3
 Component:  Contrib apps  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * owner:  nobody => laurentluce

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14388: Logging documentation typos

[Django]

#14388: Logging documentation typos
+---
  Reporter:  varikin| Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * stage:  Unreviewed => Ready for checkin
  * milestone:  => 1.3

Comment:

 Added one tiny typo cleanup, otherwise patch looks good to me. Marking
 RFC.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14386: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14386: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
+---
  Reporter:  gabrielhurley  | Owner:  gabrielhurley
Status:  closed | Milestone:  1.3  
 Component:  Contrib apps   |   Version:  SVN  
Resolution:  fixed  |  Keywords:   
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by gabrielhurley):

 Thanks for the final cleanup (and commit) on the patch, Luke. The
 inconsistent whitespace on comments and the like are what I get when
 writing too much code too late at night. Good point on TearDown, too.

 As for rolling the other two tickets into it later, I did that simply
 because the solution to them relied on the same get_current_site method,
 and I wasn't sure if this would get committed soon or days/weeks from now.
 Didn't want to write a patch for those that wouldn't apply cleanly until
 this one was in and have it end up getting messy. I certainly see your
 point though.

 Thanks!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14388: Logging documentation typos

[Django]

#14388: Logging documentation typos
+---
  Reporter:  varikin| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * has_patch:  0 => 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14390: set_password functionality outside of the User model

[Django]

#14390: set_password functionality outside of the User model
-+--
 Reporter:  k...@lysator.liu.se  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Authentication   | Version:  1.2   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Today I wanted to use a hashed, salted password in a custom model. Instead
 of reinventing the wheel or looking for it in other places, I tried to use
 the Django implementation from contrib.auth. Checking a password was fine
 as django.contrib.auth.models.check_password is not tied to the User
 model, but creating it was harder as set_password is a method on the
 User model. I had to choose between copying the implementation from
 set_password or calling set_password on a throwaway User object.

 Perhaps the salt-and-hash action from set_password could be placed in a
 separate public, documented function (make_password? hash_password?) that
 set_password then uses?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13877: More documentation needed on exceptions in middlewares

[Django]

#13877: More documentation needed on exceptions in middlewares
---+
  Reporter:  pakal   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Uncategorized |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by pakal):

 I guess the whole middleware processing should be protected by lowest-
 level exception handlers.

 It seems that neither email sending, nor debug page processing, require
 the middlewares to function, anyway.
 So process_response should be handled like other middleware functions - if
 they raise smth, catch it and trigger the critical eror system.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14388: Logging documentation typos

[Django]

#14388: Logging documentation typos
+---
  Reporter:  varikin| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gremmie):

  * summary:  Logging documentation has a type => Logging documentation
  typos

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14388: Logging documentation has a type

[Django]

#14388: Logging documentation has a type
+---
  Reporter:  varikin| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gremmie):

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

Comment:

 Also:
  * "A logger is configured to have ''log level''" should probably read "A
 logger is configured to have '''a''' ''log level''"
  * CRITICIAL should be CRITICAL

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated strings

[Django]

#13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated 
strings
-+--
  Reporter:  mitar   | Owner:  nobody
Status:  new | Milestone:
 Component:  Internationalization|   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by mitar):

 Hm, but in this case this is not a silent data loss because it is stored
 for concrete user in his context. It is only fixation of his settings at
 the time of storage. Please read initial description. I have a custom
 model field with default value which should be populated based on context
 and that value should be fixed and stored in the database. It is the same
 thing as I would display to the user values in his language context and
 then store that value. Would we say that there was a loss of data?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14389: Future url replacement

[Django]

#14389: Future url replacement
-+--
 Reporter:  seanbrant|   Owner:  nobody
   Status:  new  |   Milestone:  1.3   
Component:  Template system  | Version:  1.2   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 As previously discussed in #7917 context variables inside {% url %} do not
 work. Ticket #7917 purposed fiddling with the current {% url %} trying to
 make it support quoted/un-quoted view names as well as view names defined
 in the context. This ticket was closed by core as invalid, however this
 feature is still needed imho. In this thread[1] Malcolm suggested creating
 a new tag that depreciated the use of unquoted "string based" view names.
 I raised the issue recently[2] on django-dev and Russ recommend creating a
 new tag living in a future_url module that once loaded {% load future_url
 %} it would replace the old url tag. This allows us the ability to switch
 over the tags in a couple of releases giving developers time to upgrade
 code.

 So the upgrade path would look something like this.

 1.3: adds the new behavior only if you {% load future_url %} also if you
 are using the old url we throw a PendingDeprecationWarning
 1.4: upgrades the warning to DeprecationWarning
 1.5: replaces the old style url with the new on in
 template_tags/future_url.py the url tag defined in
 emplate_tags/future_url.py would now throw a DeprecationWarning
 1.6: remove template_tags/future_url.py

 Since we are moving to a new tag in stages I also figured we can
 officially remove support for comma separated url arguments in favor of
 the new style.

 My patch does all of above with some docs and tests. This is my first time
 writing docs so I suspect those will need some tweaking.

 Thanks,
 Sean

 [1] http://groups.google.com/group/django-
 
developers/browse_thread/thread/ac2b1ea4555c0a62/21cf9b1aed6d11e0?lnk=gst&q=url+tag+viewname#21cf9b1aed6d11e0
 [2] http://groups.google.com/group/django-
 developers/browse_thread/thread/98a9c0d2a3e2d43d

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14388: Logging documentation has a type

[Django]

#14388: Logging documentation has a type
---+
 Reporter:  varikin|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The new logging documentation has a typo with the word ERRORR:

 logger.exception(): create a ERRORR level logging message wrapping the
 current exception stack frame.

 should be

 logger.exception(): create a ERROR level logging message wrapping the
 current exception stack frame.

 If I find the time to create a patch, I will when not at 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-upda...@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] #11358: Flatpage sitemap shows all pages, even private pages

[Django]

#11358: Flatpage sitemap shows all pages, even private pages
+---
  Reporter:  dburke | Owner:  kmtracey 
Status:  closed | Milestone:   
 Component:  Contrib apps   |   Version:  1.0  
Resolution:  fixed  |  Keywords:  sprintSep2010
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Replying to [comment:11 lukeplant]:
 > Is there a reason this wasn't backported?  I'm trying to backport
 another patch, and I've got a conflict because this hasn't been backported
 to 1.2.X.

 Hectic sprint day oversight, I think. On first read I think I thought this
 was more of a feature than a bugfix...on re-looking at it it seems to be
 more of a bugfix, so should probably be backported.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #11358: Flatpage sitemap shows all pages, even private pages

[Django]

#11358: Flatpage sitemap shows all pages, even private pages
+---
  Reporter:  dburke | Owner:  kmtracey 
Status:  closed | Milestone:   
 Component:  Contrib apps   |   Version:  1.0  
Resolution:  fixed  |  Keywords:  sprintSep2010
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by lukeplant):

 Is there a reason this wasn't backported?  I'm trying to backport another
 patch, and I've got a conflict because this hasn't been backported to
 1.2.X.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #5938: test.Client.login_user(user_instance)

[Django]

#5938: test.Client.login_user(user_instance)
---+
  Reporter:  Thomas Güttler   | Owner:  
nobody
Status:  closed| Milestone:
 Component:  Testing framework |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by guettli):

 New ticket #14350

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13877: More documentation needed on exceptions in middlewares

[Django]

#13877: More documentation needed on exceptions in middlewares
---+
  Reporter:  pakal   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Uncategorized |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

  * stage:  Unreviewed => Design decision needed

Comment:

 Looks like this could use a little DDN... is this a documentation issue or
 a code issue? What *is* the desired behavior 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-upda...@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] #7923: Add links when using raw_id_fields in admin

[Django]

#7923: Add links when using raw_id_fields in admin
---+
  Reporter:  julianb   | Owner:  julianb
Status:  closed| Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:  duplicate |  Keywords:  admin raw_id_fields
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by EmilStenstrom):

 Here's a snippet that adds links to ManyToManyField too:
 http://djangosnippets.org/snippets/2217/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  
raw-id-fields nfa-someday design_ux
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

Needs_better_patch:  1 |  
---+
Comment (by EmilStenstrom):

 While you wait for this ticket to be resolved, I've added a snippet that
 shows the values for both ForeignKeys and ManyToManyFields, and links each
 value to its change page in the admin. If this is something that can be
 used in this patch, feed free to pick whatever you want from it:
 http://djangosnippets.org/snippets/2217/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #12735: django shell is broken with IPython 0.11.x (bzr.r1219)

[Django]

#12735: django shell is broken with IPython 0.11.x (bzr.r1219)
--+-
  Reporter:  alperkanat   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Changes (by mk):

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

Comment:

 Most of the time we try the "new way" to do things first and fall back to
 the old way if it didn't work out.

 Plus, a comment explaining why we need this try...except clause is in
 order too.

 {{{
 try:
 shell = IPython.InteractiveShell()
 except AttributeError:
 # IPython < 0.11
 # Explicitly pass an empty list as arguments, because otherwise
 IPython
 # would use sys.argv from this script.
 shell = IPython.Shell.IPShell(argv=[])
 shell.mainloop()
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13839: select_related caches None for non-existent objects in reverse one-to-one relations

[Django]

#13839: select_related caches None for non-existent objects in reverse 
one-to-one
relations
--+-
  Reporter:  shauncutts   | Owner: 
Status:  new  | Milestone: 
 Component:  ORM aggregation  |   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by mk):

 Here's a patch for the testsuite which currently fails, but should not.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14373: annotate() will gladly delete your data

[Django]

#14373: annotate() will gladly delete your data
--+-
  Reporter:  patrys   | Owner:  carljm
Status:  new  | Milestone:  1.3   
 Component:  ORM aggregation  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by patrys):

 I only test with sqlite and pg and could reproduce with both in 1.2
 (although I used slightly more complex queries when I discovered 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-upda...@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] #13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated strings

[Django]

#13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated 
strings
---+
  Reporter:  mitar | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by mitar):

 Replying to [comment:7 mk]:
 > I'm not sure whether lazy strings should be automatically converted to
 unicode on save(). I'd say this constitutes silent loss of information.

 Ha? Lazy strings are just that - lazy. They should behave exactly the same
 as strict strings, only their evaluation is postponed. This behavior
 should be transparent, semantics should be the same. This should only have
 influence on performance. So you can change strict into lazy and vice
 versa without worrying that something will explode.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13918: [patch] Simplify implementation of `get_model_and_form_class`

[Django]

#13918: [patch] Simplify implementation of `get_model_and_form_class`
+---
  Reporter:  suzaku | Owner:  suzaku
Status:  new| Milestone:  1.3   
 Component:  Generic views  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 Even though there's an upcoming refactoring of generic views using class-
 based views I think this patch makes sense, if only to avoid repetition.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] r13980 - in django/trunk: django/contrib/auth django/contrib/auth/tests django/contrib/contenttypes django/contrib/gis/sitemaps django/contrib/sitemaps django/contrib/sitemaps/tests django

[noreply]

Author: lukeplant
Date: 2010-10-04 09:20:47 -0500 (Mon, 04 Oct 2010)
New Revision: 13980

Modified:
   django/trunk/django/contrib/auth/forms.py
   django/trunk/django/contrib/auth/tests/views.py
   django/trunk/django/contrib/auth/views.py
   django/trunk/django/contrib/contenttypes/tests.py
   django/trunk/django/contrib/contenttypes/views.py
   django/trunk/django/contrib/gis/sitemaps/views.py
   django/trunk/django/contrib/sitemaps/__init__.py
   django/trunk/django/contrib/sitemaps/tests/basic.py
   django/trunk/django/contrib/sitemaps/views.py
   django/trunk/django/contrib/sites/models.py
   django/trunk/django/contrib/sites/tests.py
   django/trunk/django/contrib/syndication/views.py
   django/trunk/docs/ref/contrib/sites.txt
Log:
Fixed #14386, #8960, #10235, #10909, #10608, #13845, #14377 - standardize 
Site/RequestSite usage in various places.

Many thanks to gabrielhurley for putting most of this together.  Also to
bmihelac, arthurk, qingfeng, hvendelbo, petr.p...@s-cape.cz, Hraban for
reports and some initial patches.

The patch also contains some whitespace/PEP8 fixes.

Modified: django/trunk/django/contrib/auth/forms.py
===
--- django/trunk/django/contrib/auth/forms.py   2010-10-02 13:56:58 UTC (rev 
13979)
+++ django/trunk/django/contrib/auth/forms.py   2010-10-04 14:20:47 UTC (rev 
13980)
@@ -1,7 +1,7 @@
 from django.contrib.auth.models import User
 from django.contrib.auth import authenticate
 from django.contrib.auth.tokens import default_token_generator
-from django.contrib.sites.models import Site
+from django.contrib.sites.models import get_current_site
 from django.template import Context, loader
 from django import forms
 from django.utils.translation import ugettext_lazy as _
@@ -117,14 +117,14 @@
 return email
 
 def save(self, domain_override=None, 
email_template_name='registration/password_reset_email.html',
- use_https=False, token_generator=default_token_generator, 
from_email=None):
+ use_https=False, token_generator=default_token_generator, 
from_email=None, request=None):
 """
 Generates a one-use only link for resetting password and sends to the 
user
 """
 from django.core.mail import send_mail
 for user in self.users_cache:
 if not domain_override:
-current_site = Site.objects.get_current()
+current_site = get_current_site(request)
 site_name = current_site.name
 domain = current_site.domain
 else:

Modified: django/trunk/django/contrib/auth/tests/views.py
===
--- django/trunk/django/contrib/auth/tests/views.py 2010-10-02 13:56:58 UTC 
(rev 13979)
+++ django/trunk/django/contrib/auth/tests/views.py 2010-10-04 14:20:47 UTC 
(rev 13980)
@@ -248,6 +248,12 @@
 self.assert_('Logged out' in response.content)
 self.confirm_logged_out()
 
+def test_14377(self):
+# Bug 14377
+self.login()
+response = self.client.get('/logout/')
+self.assertTrue('site' in response.context)
+
 def test_logout_with_next_page_specified(self): 
 "Logout with next_page option given redirects to specified resource"
 self.login()

Modified: django/trunk/django/contrib/auth/views.py
===
--- django/trunk/django/contrib/auth/views.py   2010-10-02 13:56:58 UTC (rev 
13979)
+++ django/trunk/django/contrib/auth/views.py   2010-10-04 14:20:47 UTC (rev 
13980)
@@ -10,7 +10,7 @@
 from django.views.decorators.csrf import csrf_protect
 from django.core.urlresolvers import reverse
 from django.shortcuts import render_to_response, get_object_or_404
-from django.contrib.sites.models import Site, RequestSite
+from django.contrib.sites.models import get_current_site
 from django.http import HttpResponseRedirect, Http404
 from django.template import RequestContext
 from django.utils.http import urlquote, base36_to_int
@@ -26,21 +26,21 @@
 """Displays the login form and handles the login action."""
 
 redirect_to = request.REQUEST.get(redirect_field_name, '')
-
+
 if request.method == "POST":
 form = authentication_form(data=request.POST)
 if form.is_valid():
 # Light security check -- make sure redirect_to isn't garbage.
 if not redirect_to or ' ' in redirect_to:
 redirect_to = settings.LOGIN_REDIRECT_URL
-
-# Heavier security check -- redirects to http://example.com should 
-# not be allowed, but things like /view/?param=http://example.com 
+
+# Heavier security check -- redirects to http://example.com should
+# not be allowed, but things like /view/?param=http://example.com
 # should be allowed. This regex checks if there is a '//' *before* 
a
  

Re: [Django] #14386: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14386: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
+---
  Reporter:  gabrielhurley  | Owner:  gabrielhurley
Status:  assigned   | Milestone:  1.3  
 Component:  Contrib apps   |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by lukeplant):

 I will commit this shortly. I've made some tweaks to the patch, which I'll
 document here for your benefit:

 1. In the tests, settings.DEBUG should be restored to it's original value
 in a tearDown method, rather than in the test and rather than to the value
 'False'.  This is to avoid relying on assumptions about settings files or
 other code - it might be safe now, but that could change.

 2. Similarly, in the tests, Site._meta.installed should also be restored
 in the tearDown method, and again to the original value, and the test
 should set it to True if it is assuming that it is installed.

 3. According to PEP8, comments should start with a `#` followed by a space
 - the space was missing in some of the comments. Also, according to PEP8
 there should be be two lines between top level definitions in modules - a
 convention we haven't followed properly so far, but are trying to do with
 new files.

 4. I moved a tearDown method to after the setup, since they belong
 together.

 5. There was an unneeded import in one test, and a remaining unneeded
 import of Site/RequestSite in auth.views, and one in FlatPageSitemap

 6. Technically I think #13845 and #14377 should have had separate patches
 with tests. I added a test for #14377 since it was easy to do.

 7. Whitespace - we like trailing spaces removed in the Django code base.
 It's admittedly hard to see in some editors, Emacs has an option for
 seeing it.


 BTW, Trac didn't show the patch because of a bug where it fails to parse
 "\ No newline at end of file" in the patch, which wasn't your fault.

 Notwithstanding those comments, thanks for putting all this together,
 great 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-upda...@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] #13938: django.test.Client response has wrong request type

[Django]

#13938: django.test.Client response has wrong request type
+---
  Reporter:  Ciantic| Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 As you wrote initializing the request object directly is probably better.

 This behavior (storing the data, not the object) is documented, I'm
 closing the ticket as invalid because of that:
 
http://docs.djangoproject.com/en/dev/topics/testing/#django.test.client.Response.request

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django-admin.py
  * 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-upda...@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] #13972: Field initial value callable should take a request object as an argument

[Django]

#13972: Field initial value callable should take a request object as an argument
-+--
  Reporter:  mitar   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mk):

  * stage:  Unreviewed => Design decision needed

Comment:

 The form classes do not know anything about requests currently, and the
 prevailing opinion is that this should not be changed in the future.

 The last time that coupling requests and forms came up was during the last
 refactoring of CSRF protection. It was rejected.

 This ticket is probably a candidate for "wontfix", this is to be decided
 by the core developers though.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13979: Django manage.py d oesn’t work with IPython

[Django]

#13979: Django manage.py doesn’t work with IPython
--+-
  Reporter:  ingo86   | Owner:  nobody 
Status:  closed   | Milestone: 
 Component:  django-admin.py  |   Version:  1.2
Resolution:  worksforme   |  Keywords:  manage.py shell ipython
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by adamnelson):

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

Comment:

 Two people saying worksforme seems sufficient to mark it as such.  Again,
 for future readers, the 'typical' Django installation on a Mac is:

  * Snow Leopard
  *  Everything installed via homebrew
  * Use virtualenv for the environment
  * Use pip to install packages (i.e. everywhere somebody says
 "easy_install package_name", do "pip install package_name"

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13770: form BooleanField should clean the string u'false' as False.

[Django]

#13770: form BooleanField should clean the string u'false' as False.
---+
  Reporter:  jordanb   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by mk):

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

Comment:

 I think this feature makes sense. However, we still need tests for this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14295: Saving an object with a custom manager results in IntegrityError

[Django]

#14295: Saving an object with a custom manager results in IntegrityError
+---
  Reporter:  loekje | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

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

Comment:

 I can't reproduce this failure on trunk or 1.2 with the code provided.

  1. Your example code works just fine when run on a clean project.
  2. Reading the source for Model.save, which in turn calls
 Model.save_base, the default manager is *not* used. Saving is done with
 `_base_manager` which should be an instance of models.Manager in all cases
 I'm aware of.

 If you can provide a failing test case (bonus points if it's in the form
 of a unit test for the Django test suite), please reopen the ticket.

 However, if you're really reporting this from a version 1.0 installation
 of Django, it's almost certainly been fixed subsequently, and 1.0 is no
 longer even an officially "supported" version according to the release
 process docs.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13916: DecimalField min_value does not enforce use of decimal.Decimal type

[Django]

#13916: DecimalField min_value does not enforce use of decimal.Decimal type
+---
  Reporter:  b...@trick.vanstaveren.us  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Forms  |   Version:  1.2   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 I think the developer can be expected to know the distinction between
 floats and decimals.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14387: pre_save problem with inherrited model

[Django]

#14387: pre_save problem with inherrited model
--+-
  Reporter:  iskren   | Owner:  iskren  
   
Status:  assigned | Milestone:  
   
 Component:  ORM aggregation  |   Version:  1.2 
   
Resolution:   |  Keywords:  pre_save inheritance 
inherited save
 Stage:  Unreviewed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by iskren):

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

Comment:

 The solution I used was to check if the primary key of the instance is
 None and if so skip the code that breaks.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13974: saving object with multi-table inheritance is not transactional by default

[Django]

#13974: saving object with multi-table inheritance is not transactional by 
default
---+
  Reporter:  ccurvey   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by emulbreh):

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

Comment:

 Django cannot know the scope of your transaction. At best, Model.save()
 could be wrapped with a savepoint.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #6735: Class-based generic views

[Django]

#6735: Class-based generic views
+---
  Reporter:  jkocherhans| Owner:  david
Status:  assigned   | Milestone:  1.3  
 Component:  Generic views  |   Version:   
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  1  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by mk):

 XViewMiddleware should be fixed if class-based views are added to Django:
 #13842

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13896: Change language to dynamic attribute in syndication feed generator

[Django]

#13896: Change language to dynamic attribute in syndication feed generator
+---
  Reporter:  jedie  | Owner:  nobody
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 I think this makes sense. The language of the feed might be encoded inside
 the URL too and isn't fixed to LANGUAGE_CODE from the site settings.

 This change has to be documented.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14132: Feedgenerator doesn't support dates before 1900

[Django]

#14132: Feedgenerator doesn't support dates before 1900
---+
  Reporter:  mlissner  | Owner:  mk 
Status:  assigned  | Milestone: 
 Component:  Contrib apps  |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by mk):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  Feedparser doesn't support dates before 1900 => Feedgenerator
  doesn't support dates before 1900
  * owner:  nobody => mk
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 This affects feedgenerator, not feedparser.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14377: Add site to the context of the logout view

[Django]

#14377: Add site to the context of the logout view
---+
  Reporter:  Hraban   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Authentication|   Version:  SVN
 
Resolution:|  Keywords:  logout site 
view
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

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

Comment:

 Valid issue, marking accepted. However, the fix for this issue is in the
 patch on #14386. When that patch is committed this issue can be closed.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14385: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14385: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
---+
 Reporter:  gabrielhurley  |   Owner:  gabrielhurley
   Status:  new|   Milestone:  1.3  
Component:  Contrib apps   | Version:  SVN  
 Keywords: |   Stage:  Unreviewed   
Has_patch:  1  |  
---+
 A few days ago I started [http://groups.google.com/group/django-
 developers/browse_frm/thread/0584c60ba9969052 this thread on the Django
 Developers list] in order to solve a number of tickets at the same time.
 The gist:

 All of these tickets relate to needing access to the current domain,
 whether that's through a Site instance, or through a RequestSite instance.
 To facilitate this, the provided patch adds a utility function,
 `django.contrib.sites.models.get_current_site` which takes a request as an
 argument and returns either a Site or RequestSite instance.

 Using that utility function, a lot of repetitious code could be removed
 and streamlined, and several tickets were trivial to resolve.

 Included in this patch:

  * Adds the `django.contrib.sites.models.get_current_site` function.
  * Provides a note in the contrib.sites docs regarding the function.
  * Converts to contrib.sites tests from doctests to unit tests and adds a
 test for `get_current_site`
  * Resolves #8960 by allowing `django.contrib.contenttypes.views.shortcut`
 to use either a Site or RequesSite object.
  * Converts contrib.contenttypes tests from doctests to unit tests and
 adds a test for #8960.
  * Resolves #10235 and #10909 by using `get_current_site` in the Sitemaps
 framework.
  * Adds test case for #10235/#10909.
  * Updates `django.contrib.syndication.views` to use `get_current_site.
  * Updates `django.contrib.gis.sitemaps.views` to use `get_current_site`
 as per #10608.
  * Updates `django.contrib.auth.views.login` to use `get_current_site`.

 The patch passes the full test suite under WinXP/Py2.6/SQLite.

 This patch would completely fix #8960, #10235, and #10909. The remainder
 of #10608 is actually invalid, because the remaining places where contrib
 apps rely on contrib.sites the model has a direct relation to Site, or
 there is no way to access a request object to use RequestSite. Any further
 decoupling in contrib would require backwards-incompatible rewrites.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14384: Installation documentation should avoid sys.path.append

[Django]

#14384: Installation documentation should avoid sys.path.append
+---
  Reporter:  monokrome  | Owner:  wogan 
   
Status:  assigned   | Milestone:  1.3   
   
 Component:  Documentation  |   Version:  1.2   
   
Resolution: |  Keywords:  documentation apache 
mod_wsgi
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by wogan):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * milestone:  => 1.3
  * owner:  nobody => wogan
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 Agreed, the documentation should follow mod_wsgi best practices here.

 The patch just contains the appropriate changes to the WSGI application
 without explanation. I'm not entirely sure whether a footnote is required
 or not.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13842: XViewMiddleware fails with class-based views

[Django]

#13842: XViewMiddleware fails with class-based views
-+--
  Reporter:  ch0wn   | Owner:  mk
Status:  assigned| Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:  middleware
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mk):

  * owner:  nobody => mk
  * status:  new => assigned
  * stage:  Unreviewed => Accepted

Comment:

 See #6735 too (adding class-based generic views to Django)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14279: typo in tests for private flatpage not showing sitemaps

[Django]

#14279: typo in tests for private flatpage not showing sitemaps
+---
  Reporter:  jamesodo   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Contrib apps   |   Version:  SVN   
Resolution: |  Keywords:  flatpages sitemaps
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

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

Comment:

 This typo didn't actually affect the test, but it's good to correct the
 typo.

 Patch applies cleanly, passes tests, issue is valid, marking RFC.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13494: Bad default for EMAIL_SUBJECT_PREFIX

[Django]

#13494: Bad default for EMAIL_SUBJECT_PREFIX
---+
  Reporter:  hcarvalhoalves| Owner:  andialbrecht
Status:  assigned  | Milestone:  
 Component:  django.core.mail  |   Version:  1.1 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by andialbrecht):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14387: pre_save problem with inherrited model

[Django]

#14387: pre_save problem with inherrited model
--+-
  Reporter:  iskren   | Owner:  
   
Status:  new  | Milestone:  
   
 Component:  ORM aggregation  |   Version:  1.2 
   
Resolution:   |  Keywords:  pre_save inheritance 
inherited save
 Stage:  Unreviewed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Comment (by iskren):

 After creating an empty instance of the Child Class and trying to save it,
 django DoesNotExist exception;
 when the inheritance is removed test works fine. Also if I remove the
 pre_save it works fine, but the wanted result is not achieved.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14283: AttributeError on admin detail page after r13708

[Django]

#14283: AttributeError on admin detail page after r13708
--+-
  Reporter:  rene.p...@repro-mayr.de  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Uncategorized|   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by mk):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 Need to curry formfield_for_dbfield in contenttypes/generic.py. Patch
 attached.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14135: Admin ignores to_field on ForeignKey

[Django]

#14135: Admin ignores to_field on ForeignKey
+---
  Reporter:  vbs| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by vbs):

 Replying to [comment:1 mk]:
 > You must define a __unicode__ method on course if you do not want the
 admin to show "". This has nothing to do with to_field on a
 ForeignKey.


 but if i just want a specified field rather than an object, how can i do?

 Thank you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14283: AttributeError on admin detail page after r13708

[Django]

#14283: AttributeError on admin detail page after r13708
--+-
  Reporter:  rene.p...@repro-mayr.de  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Contrib apps |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by gabrielhurley):

  * component:  Uncategorized => Contrib apps

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14385: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14385: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
+---
  Reporter:  gabrielhurley  | Owner:  gabrielhurley
Status:  closed | Milestone:  1.3  
 Component:  Contrib apps   |   Version:  SVN  
Resolution:  duplicate  |  Keywords:   
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

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

Comment:

 Duplicate of #14386... Trac is being buggy at the moment :-/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13839: select_related caches None for non-existent objects in reverse one-to-one relations

[Django]

#13839: select_related caches None for non-existent objects in reverse 
one-to-one
relations
--+-
  Reporter:  shauncutts   | Owner: 
Status:  new  | Milestone:  1.3
 Component:  ORM aggregation  |   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by mk):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * milestone:  => 1.3

Comment:

 Proposed fix attached. This isn't my area of expertise though but the full
 test suite passed on Python 2.6 / sqlite3.

 Assigning milestone 1.3 because this bug is a possible cause of crashes
 and should be looked into before another release is made.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14387: pre_save problem with inherrited model

[Django]

#14387: pre_save problem with inherrited model
---+
   Reporter:  iskren   |Owner:  
  
 Status:  new  |Milestone:  
  
  Component:  ORM aggregation  |  Version:  1.2 
  
   Keywords:  pre_save inheritance inherited save  |Stage:  
Unreviewed
  Has_patch:  0|   Needs_docs:  0   
  
Needs_tests:  0|   Needs_better_patch:  0   
  
---+
 Hello.

 I have a base-class and a child-class. The child-class has a pre_save
 signal and it has a list of related items to it.
 when testing for save action django raises DoesNotExist exception.
 Traceback follows:

 Thank you for the time spent on the Django project

  File "../children_pre_save_problem/test_b/tests.py", line 9, in
 test1_inc_num
 invo.save()
   File "/usr/lib/pymodules/python2.6/django/db/models/base.py", line 410,
 in save
 self.save_base(force_insert=force_insert, force_update=force_update)
   File "/usr/lib/pymodules/python2.6/django/db/models/base.py", line 432,
 in save_base
 signals.pre_save.send(sender=origin, instance=self, raw=raw)
   File "/usr/lib/pymodules/python2.6/django/dispatch/dispatcher.py", line
 166, in send
 response = receiver(signal=self, sender=sender, **named)
   File
 "/home/iskren/tc/python/children_pre_save_problem/test_b/models.py", line
 30, in invoicedoc_pre_save
 instance.recalc_total()
   File
 "/home/iskren/tc/python/children_pre_save_problem/test_b/models.py", line
 19, in recalc_total
 for item in self.item_set.all():
   File "/usr/lib/pymodules/python2.6/django/db/models/fields/related.py",
 line 324, in __get__
 self.related.model._default_manager.__class__)
   File "/usr/lib/pymodules/python2.6/django/db/models/fields/related.py",
 line 399, in create_manager
 getattr(instance, attname)}
   File "/usr/lib/pymodules/python2.6/django/db/models/fields/related.py",
 line 244, in __get__
 raise self.field.rel.to.DoesNotExist

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14386: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14386: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
+---
  Reporter:  gabrielhurley  | Owner:  gabrielhurley
Status:  assigned   | Milestone:  1.3  
 Component:  Contrib apps   |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by gabrielhurley):

 Since apparently overwriting an old patch file in Trac overwrites messages
 added with it, I'll add a permanent note that this patch now solves #13845
 (using get_current_site in contrib.auth.forms.PasswordResetForm.save), and
 #14377 (using get_current_site in contrib.auth.views.logout to make the
 current site accessible in the logout template as it is in the login
 view/template).

 Complete list of tickets affected currently: #8960, #10235, #10909,
 #10608, #13845, #14377.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #5365: sqlite3+DateField: field__year doesn't work.

[Django]

#5365: sqlite3+DateField: field__year doesn't work.
+---
  Reporter:  Jakub Wilk   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution:  worksforme |  Keywords:  qs-rf 
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by mk):

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

Comment:

 Cannot reproduce, please provide a testcase if this is still a problem.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14135: Admin ignores to_field on ForeignKey

[Django]

#14135: Admin ignores to_field on ForeignKey
+---
  Reporter:  vbs| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 You must define a __unicode__ method on course if you do not want the
 admin to show "". This has nothing to do with to_field on a
 ForeignKey.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13494: Bad default for EMAIL_SUBJECT_PREFIX

[Django]

#13494: Bad default for EMAIL_SUBJECT_PREFIX
---+
  Reporter:  hcarvalhoalves| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.core.mail  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by andialbrecht):

  * has_patch:  0 => 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14350: Please add a login method to the test Client that doesn't depend on passwords

[Django]

#14350: Please add a login method to the test Client that doesn't depend on
passwords
---+
  Reporter:  James Westby   | Owner: 
 nobody
Status:  new   | Milestone: 
   
 Component:  Testing framework |   Version: 
 1.2   
Resolution:|  Keywords: 
   
 Stage:  Unreviewed| Has_patch: 
 0 
Needs_docs:  0 |   Needs_tests: 
 0 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

  * 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-upda...@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] #14295: Saving an object with a custom manager results in IntegrityError

[Django]

#14295: Saving an object with a custom manager results in IntegrityError
+---
  Reporter:  loekje | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by mk):

 I think this has been fixed in [10056]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13804: URLField validation fails with "://" on the path and no scheme

[Django]

#13804: URLField validation fails with "://" on the path and no scheme
---+
  Reporter:  Samus_| Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by emulbreh):

  * 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-upda...@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] #14167: Using Instances in Generic Create/Update/Delete

[Django]

#14167: Using Instances in Generic Create/Update/Delete
+---
  Reporter:  monokrome  | Owner:  nobody
Status:  new| Milestone:
 Component:  Generic views  |   Version:  1.2   
Resolution: |  Keywords:  generic views DRY instance
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by monokrome):

  * needs_tests:  0 => 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #6735: Class-based generic views

[Django]

#6735: Class-based generic views
+---
  Reporter:  jkocherhans| Owner:  david
Status:  assigned   | Milestone:  1.3  
 Component:  Generic views  |   Version:   
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  1  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: benjixx (removed)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14200: new RegexURLResolver is contructed for every request

[Django]

#14200: new RegexURLResolver is contructed for every request
-+--
  Reporter:  Suor| Owner:  Suor 
Status:  new | Milestone:   
 Component:  Core framework  |   Version:  1.2  
Resolution:  |  Keywords:  performance, urlresolvers
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  1   |  
-+--
Changes (by mk):

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

Comment:

 Did you do some performance testing? I'm not sure whether this really
 impacts performance in a noticeable negative way.

 Anyway, applying this patch breaks the testsuite (FAIL:
 test_urlconf_overridden_with_null
 (regressiontests.urlpatterns_reverse.tests.RequestURLconfTests)) and
 breaks assigning request.urlconf:

 http://docs.djangoproject.com/en/dev/topics/http/urls/#how-django-
 processes-a-request

 The patch at least needs improvement and probably additional justification
 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-upda...@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] #13845: Contrib auth password-reset email depends on is_admin_site

[Django]

#13845: Contrib auth password-reset email depends on is_admin_site
--+-
  Reporter:  petr.p...@s-cape.cz  | Owner:  nobody
Status:  new  | Milestone:  1.3   
 Component:  Authentication   |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by gabrielhurley):

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

Comment:

 For the record, the reason behind that email template control has to do
 with the way the template name and the site domain name were being passed
 around between the view and the save method of PasswordResetForm. It
 wasn't pretty.

 This issue is definitely valid, so I'll accept it. However, this issue has
 a fix in the patch for #14386, which broadly decouples the sites framework
 from the various contrib apps. Provided that patch gets committed, this
 issue will be 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-upda...@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] #13979: Django manage.py d oesn’t work with IPython

[Django]

#13979: Django manage.py doesn’t work with IPython
--+-
  Reporter:  ingo86   | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  django-admin.py  |   Version:  1.2
Resolution:   |  Keywords:  manage.py shell ipython
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by mk):

  * component:  Core framework => django-admin.py

Comment:

 I'm using IPython on Snow Leopard all the time. I think this ticket should
 be resolved as "worksforme".

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14135: Admin ignores to_field on ForeignKey

[Django]

#14135: Admin ignores to_field on ForeignKey
+---
  Reporter:  vbs| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by mk):

 This is an usage question -- please submit it to the django-users mailing
 list instead.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated strings

[Django]

#13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated 
strings
-+--
  Reporter:  mitar   | Owner:  nobody
Status:  new | Milestone:
 Component:  Internationalization|   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mk):

  * stage:  Unreviewed => Design decision needed

Comment:

 No, semantics aren't the same. A lazy i18n string depends on the context
 and this is lost when the string is stored in a DB. I'll rather be warned
 (with an explosion, if it has to be) when I try doing something stupid.
 "Silent data loss" is a strong description for what's happening if a lazy
 string is translated upon entering storage, but I'd still argue that's
 what is happening here. And silent data loss is bad(tm).

 I'll mark this design decision needed, hopefully someone from core will
 weigh in on this issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13979: Django manage.py d oesn’t work with IPython

[Django]

#13979: Django manage.py doesn’t work with IPython
--+-
  Reporter:  ingo86   | Owner:  nobody 
Status:  closed   | Milestone: 
 Component:  django-admin.py  |   Version:  1.2
Resolution:  worksforme   |  Keywords:  manage.py shell ipython
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by russellm):

 @adamnelson: That's a common setup, but it's not universal. I, for one,
 don't use homebrew at all; all my databases and support libraries are
 native installs.

 That said, I'm not seeing this problem either.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #12325: Allow value of zero for moderate_after and close_after

[Django]

#12325: Allow value of zero for moderate_after and close_after
--+-
  Reporter:  zhigang  | Owner:  gabrielhurley
Status:  assigned | Milestone:  1.3  
 Component:  django.contrib.comments  |   Version:  1.1  
Resolution:   |  Keywords:  moderation   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by gabrielhurley):

  * needs_docs:  1 => 0
  * summary:  Allow zero moderate_after time => Allow value of zero for
  moderate_after and close_after
  * needs_tests:  1 => 0
  * milestone:  => 1.3

Comment:

 Added a new patch which allows 0 as a valid value for both `close_after`
 and `moderate_after`. Includes docs and tests. Passes test suite.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14041: Templates in function calls for sitemap

[Django]

#14041: Templates in function calls for sitemap
---+
  Reporter:  owcarnia  | Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Contrib apps  |   Version:  1.2 
Resolution:|  Keywords:  sitemaps
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Contrib apps
  * 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-upda...@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] #14135: Admin ignores to_field on ForeignKey

[Django]

#14135: Admin ignores to_field on ForeignKey
+---
  Reporter:  vbs| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by vbs):

 but if i just want a specified field rather than an object, how can i do?

 Thank you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14023: Better example for the custom form template

[Django]

#14023: Better example for the custom form template
+---
  Reporter:  konryd | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.3

Comment:

 People forget about form.non_field_errors all the time.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14386: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14386: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
+---
  Reporter:  gabrielhurley  | Owner:  gabrielhurley
Status:  assigned   | Milestone:  1.3  
 Component:  Contrib apps   |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Unreviewed | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I'm not sure why Trac isn't displaying the diff for this patch, but the
 code *is* in there... ::sigh::

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14386: Standardize Site/RequestSite access; looser coupling of sites framework in contrib

[Django]

#14386: Standardize Site/RequestSite access; looser coupling of sites framework 
in
contrib
---+
 Reporter:  gabrielhurley  |   Owner:  gabrielhurley
   Status:  new|   Milestone:  1.3  
Component:  Contrib apps   | Version:  SVN  
 Keywords: |   Stage:  Unreviewed   
Has_patch:  1  |  
---+
 A few days ago I started [http://groups.google.com/group/django-
 developers/browse_frm/thread/0584c60ba9969052 this thread on the Django
 Developers list] in order to solve a number of tickets at the same time.
 The gist:

 All of these tickets relate to needing access to the current domain,
 whether that's through a Site instance, or through a RequestSite instance.
 To facilitate this, the provided patch adds a utility function,
 `django.contrib.sites.models.get_current_site` which takes a request as an
 argument and returns either a Site or RequestSite instance.

 Using that utility function, a lot of repetitious code could be removed
 and streamlined, and several tickets were trivial to resolve.

 Included in this patch:

  * Adds the `django.contrib.sites.models.get_current_site` function.
  * Provides a note in the contrib.sites docs regarding the function.
  * Converts to contrib.sites tests from doctests to unit tests and adds a
 test for `get_current_site`
  * Resolves #8960 by allowing `django.contrib.contenttypes.views.shortcut`
 to use either a Site or RequesSite object.
  * Converts contrib.contenttypes tests from doctests to unit tests and
 adds a test for #8960.
  * Resolves #10235 and #10909 by using `get_current_site` in the Sitemaps
 framework.
  * Adds test case for #10235/#10909.
  * Updates `django.contrib.syndication.views` to use `get_current_site.
  * Updates `django.contrib.gis.sitemaps.views` to use `get_current_site`
 as per #10608.
  * Updates `django.contrib.auth.views.login` to use `get_current_site`.

 The patch passes the full test suite under WinXP/Py2.6/SQLite.

 This patch would completely fix #8960, #10235, and #10909. The remainder
 of #10608 is actually invalid, because the remaining places where contrib
 apps rely on contrib.sites the model has a direct relation to Site, or
 there is no way to access a request object to use RequestSite. Any further
 decoupling in contrib would require backwards-incompatible rewrites.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14175: Comment object's user_name field too short for User.get_full_name

[Django]

#14175: Comment object's user_name field too short for User.get_full_name
--+-
  Reporter:  gravm| Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.comments  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by mk):

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

Comment:

 Either that or the return value of get_full_name() would have to be
 truncated.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14384: Installation documentation should avoid sys.path.append

[Django]

#14384: Installation documentation should avoid sys.path.append
---+
 Reporter:  monokrome  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords:  documentation apache mod_wsgi  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Using Apache's mod_wsgi implementation (and I'm sure some others), there
 are cases where sys.path.append will add redundant items to the system
 path. The mod_wsgi documentation requests that, instead, developers use
 the following in order to avoid these redundancies:

 {{{
 import sys
 path = '/usr/local/wsgi/modules'
 if path not in sys.path:
 sys.path.append(path)
 }}}

 More information is available here:
 
[http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIReloadMechanism
 WSGIReloadMechanism]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated strings

[Django]

#13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated 
strings
---+
  Reporter:  mitar | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by mk):

 I'm not sure whether lazy strings should be automatically converted to
 unicode on save(). I'd say this constitutes silent loss of information.

 Btw, this does not work on sqlite either: It fails with an InterfaceError:
 InterfaceError: Error binding parameter 5 - probably unsupported type.

 I'd close this ticket as "wontfix".

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

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