Re: [Django] #3566: Proposal: ORM aggregation support

[Django]

#3566: Proposal: ORM aggregation support
+---
  Reporter:  Honza Král   | Owner:  
russellm
Status:  assigned   | Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:  orm 
aggregation group by
 Stage:  Someday/Maybe  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by underbluewaters):

 I would be great if this feature supported Standard Deviation to do some
 simple statistics. I'm currently doing this with plain sql and it is a
 hassle.

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

[Django] #9980: Nice-have correction for Authentication

[Django]

#9980: Nice-have correction for Authentication
--+-
 Reporter:  shelldweller  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Uncategorized | Version:  1.0   
 Keywords:  templates authentication  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In http://docs.djangoproject.com/en/dev/topics/auth/#id5 the wording is a
 bit misleading. It would be nice to replace this:

 ''The currently logged-in user, either a User instance or an AnonymousUser
 instance, is stored in the template variable {{ user }}''

 with this:

 '' '''If rendering template django.template.RequestContext (link),''' the
 currently logged-in user, either a User instance or an AnonymousUser
 instance, is stored in the template variable {{ user }}''

 to make clear that this feature is only available with RequestContext (and
 not with Context)

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

[Django] #9979: localizing input_formats on DateField

[Django]

#9979: localizing input_formats on DateField
-+--
 Reporter:  matehat  |   Owner:  matehat   
   Status:  new  |   Milestone:
Component:  Forms| Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 I needed a DateField to be able to receive lazy ugettext objects and
 resolve them at validating time, but when I tried I got an error from the
 internal python date parser, so I just applied `force_unicode` on each
 passed format in the field's clean method and everything works fine. I
 attached the patch so you can check it out and merge it ASAP!

 Currently, my modifications allows the input_formats parameter to be in
 the form of:

 input_formats = ( _l('some_format'), _('some_other_format') ) # where _l
 is `ugettext_lazy`

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

[Django] #9978: logout() method in test.client.Client raising KeyError

[Django]

#9978: logout() method in test.client.Client raising KeyError
---+
 Reporter:  igors  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I've noticed this logout() method raises !KeyError when I'm not
 authenticated.

 I'm not sure it's a bug, but in my opinion it should fail silently. Catch
 the exception would solve it.

 [1]
 http://code.djangoproject.com/browser/django/trunk/django/test/client.py#L413

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

Re: [Django] #9972: dbshell can't connect to Oracle database

[Django]

#9972: dbshell can't connect to Oracle database
---+
  Reporter:  lijin...@cn-acg.com   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  oracle, 
dbshell
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by lijin...@cn-acg.com):

 Oracle version:Oracle Database 10g Express Edition Release 10.2.0.1.0 -
 Production

 SQL*Plus version: SQL*Plus: Release 10.2.0.4.0 - Production

 cx_Oracle version: 4.4.1

 about database settings:

 DATABASE_ENGINE = 'oracle'
 DATABASE_NAME = 'xe'
 DATABASE_USER = 'dba'
 DATABASE_PASSWORD = 'password'
 DATABASE_HOST = '192.168.1.111'
 DATABASE_PORT = '1521'

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

Re: [Django] #8764: Mixing args and **kwargs in reverse() function

[Django]

#8764: Mixing args and **kwargs in reverse() function
-+--
  Reporter:  tolano  | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  wontfix |  Keywords:  reverse function 
exception
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by mtredinnick):

 For anybody else thinking of reopening this, please understand what
 comment:1 is saying. It's not merely difficult. It's '''impossible''' to
 do correctly for all cases and differentiating the cases where it's
 possible and the ones where it isn't is a computationally inefficient
 process.

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

Re: [Django] #9969: Admin change list view shows (None) instead of the real field value when it has been chosen from a choices named group

[Django]

#9969: Admin change list view shows (None) instead of the real field value when 
it
has been chosen from a choices named group
---+
  Reporter:  ramiro| Owner:  ramiro 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  change list 
choices columns (None) named groups select dropdown
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * owner:  nobody => ramiro
  * needs_tests:  1 => 0

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

Re: [Django] #8764: Mixing args and **kwargs in reverse() function

[Django]

#8764: Mixing args and **kwargs in reverse() function
-+--
  Reporter:  tolano  | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  wontfix |  Keywords:  reverse function 
exception
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

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

Comment:

 If you'd like to start a discussion on this, take it to the dev list. In
 the meantime, ticket stays 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-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8764: Mixing args and **kwargs in reverse() function

[Django]

#8764: Mixing args and **kwargs in reverse() function
-+--
  Reporter:  tolano  | Owner:  nobody   
 
Status:  reopened| Milestone:   
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  |  Keywords:  reverse function 
exception
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by Killarny):

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

Comment:

 I don't understand the rational here for not fixing this issue. The
 decision not to allow mixing args and kwargs seems like a lazy way to
 avoid coming up with a real solution. Forcing the use of one or the other
 but not both is simply not pythonic, and without some sort of discussion,
 seems silly. When a python framework does not allow valid python syntax to
 function properly, that sounds like a fundamental flaw in design to me.

 There are many instances where, in a complicated implementation of views,
 one might want to have a combination of required args and optional kwargs,
 and the inability to mix them introduces all sorts of complexities to the
 logic of the views that shouldn't have to be dealt with. Could anyone
 either fix this, or provide some sort of insight as to what the real
 rational here is?

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

Re: [Django] #7153: Not all callables are run by the template system

[Django]

#7153: Not all callables are run by the template system
--+-
  Reporter:  Ionut Ciocirlan   | 
Owner:  nobody   
Status:  new  | 
Milestone:   
 Component:  Template system  |   
Version:  SVN  
Resolution:   |  
Keywords:  template callable
 Stage:  Accepted | 
Has_patch:  1
Needs_docs:  0|   
Needs_tests:  1
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

 * cc: daeva...@gmail.com (added)

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

Re: [Django] #9977: CSRFMiddleware needs template tag

[Django]

#9977: CSRFMiddleware needs template tag
+---
  Reporter:  bthomas| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bthomas):

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

Comment:

 Usage:

  * Add 'django.contrib.csrf' to INSTALLED_APPS
  * Add 'django.contrib.csrf.context_processors.csrf' to
 TEMPLATE_CONTEXT_PROCESSORS
  * Add 'django.contrib.csrf.middleware.CsrfViewMiddleware' to
 MIDDLEWARE_CLASSES after SesssionMiddleware

 In a template:

 {{{
 {% load csrf %}
 
   {% csrf_token %}
   {{ form }}
   
 
 }}}

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

[Django] #9977: CSRFMiddleware needs template tag

[Django]

#9977: CSRFMiddleware needs template tag
---+
 Reporter:  bthomas|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 CSRFMiddleware needs a template tag so that a view-only middleware can be
 used. See discussion at http://groups.google.com/group/django-
 developers/browse_thread/thread/ae525f270ed46933

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

Re: [Django] #8127: CSRF + AJAX

[Django]

#8127: CSRF + AJAX
-+--
  Reporter:  xlax| Owner:  nobody   
Status:  closed  | Milestone:   
 Component:  Contrib apps|   Version:  SVN  
Resolution:  fixed   |  Keywords:  CSRF AJAX
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  1
Needs_better_patch:  0   |  
-+--
Changes (by bthomas):

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

Comment:

 This was fixed in [9554]

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

Re: [Django] #9972: dbshell can't connect to Oracle database

[Django]

#9972: dbshell can't connect to Oracle database
---+
  Reporter:  lijin...@cn-acg.com   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  oracle, 
dbshell
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by ikelly):

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

Comment:

 On my install, SQL*Plus rejects the connect string produced by this patch.
 What version of SQL*Plus are you using?  What settings.py database
 settings are you using?

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

[Changeset] r9710 - in django/branches/releases/1.0.X: . docs/ref docs/topics

[noreply]

Author: ikelly
Date: 2009-01-06 12:25:52 -0600 (Tue, 06 Jan 2009)
New Revision: 9710

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/ref/databases.txt
   django/branches/releases/1.0.X/docs/topics/install.txt
Log:
[1.0.X] Refs #9935: Added a note in the documentation to the effect that Django 
currently requires a 4.X release of cx_Oracle. Backport of [9709] from trunk.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691,9695-9696,9698
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691,9695-9696,9698,9709

Modified: django/branches/releases/1.0.X/docs/ref/databases.txt
===
--- django/branches/releases/1.0.X/docs/ref/databases.txt   2009-01-06 
18:22:07 UTC (rev 9709)
+++ django/branches/releases/1.0.X/docs/ref/databases.txt   2009-01-06 
18:25:52 UTC (rev 9710)
@@ -335,7 +335,8 @@
 
 Django supports `Oracle Database Server`_ versions 9i and higher. Oracle
 version 10g or later is required to use Django's ``regex`` and ``iregex`` query
-operators. You will also need the `cx_Oracle`_ driver, version 4.3.1 or newer.
+operators. You will also need a 4.X release of the `cx_Oracle`_ driver,
+version 4.3.1 or newer.
 
 .. _`Oracle Database Server`: http://www.oracle.com/
 .. _`cx_Oracle`: http://cx-oracle.sourceforge.net/

Modified: django/branches/releases/1.0.X/docs/topics/install.txt
===
--- django/branches/releases/1.0.X/docs/topics/install.txt  2009-01-06 
18:22:07 UTC (rev 9709)
+++ django/branches/releases/1.0.X/docs/topics/install.txt  2009-01-06 
18:25:52 UTC (rev 9710)
@@ -82,9 +82,9 @@
   wrapper in the standard library, so you don't need to install anything extra
   in that case.
 
-* If you're using Oracle, you'll need cx_Oracle_, version 4.3.1 or higher. You
-  will also want to read the database-specific notes for the :ref:`Oracle
-  backend `.
+* If you're using Oracle, you'll need a 4.X release of cx_Oracle_, version
+  4.3.1 or higher. You will also want to read the database-specific notes for
+  the :ref:`Oracle backend `.
 
 If you plan to use Django's ``manage.py syncdb`` command to
 automatically create database tables for your models, you'll need to


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

[Changeset] r9709 - in django/trunk/docs: ref topics

[noreply]

Author: ikelly
Date: 2009-01-06 12:22:07 -0600 (Tue, 06 Jan 2009)
New Revision: 9709

Modified:
   django/trunk/docs/ref/databases.txt
   django/trunk/docs/topics/install.txt
Log:
Refs #9935: Added a note in the documentation to the effect that Django 
currently requires a 4.X release of cx_Oracle.

Modified: django/trunk/docs/ref/databases.txt
===
--- django/trunk/docs/ref/databases.txt 2009-01-06 05:27:39 UTC (rev 9708)
+++ django/trunk/docs/ref/databases.txt 2009-01-06 18:22:07 UTC (rev 9709)
@@ -335,7 +335,8 @@
 
 Django supports `Oracle Database Server`_ versions 9i and higher. Oracle
 version 10g or later is required to use Django's ``regex`` and ``iregex`` query
-operators. You will also need the `cx_Oracle`_ driver, version 4.3.1 or newer.
+operators. You will also need a 4.X release of the `cx_Oracle`_ driver,
+version 4.3.1 or newer.
 
 .. _`Oracle Database Server`: http://www.oracle.com/
 .. _`cx_Oracle`: http://cx-oracle.sourceforge.net/

Modified: django/trunk/docs/topics/install.txt
===
--- django/trunk/docs/topics/install.txt2009-01-06 05:27:39 UTC (rev 
9708)
+++ django/trunk/docs/topics/install.txt2009-01-06 18:22:07 UTC (rev 
9709)
@@ -82,9 +82,9 @@
   wrapper in the standard library, so you don't need to install anything extra
   in that case.
 
-* If you're using Oracle, you'll need cx_Oracle_, version 4.3.1 or higher. You
-  will also want to read the database-specific notes for the :ref:`Oracle
-  backend `.
+* If you're using Oracle, you'll need a 4.X release of cx_Oracle_, version
+  4.3.1 or higher. You will also want to read the database-specific notes for
+  the :ref:`Oracle backend `.
 
 If you plan to use Django's ``manage.py syncdb`` command to
 automatically create database tables for your models, you'll need to


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

Re: [Django] #9935: The session db backend throws UnicodeEncodeError when used with Oracle

[Django]

#9935: The session db backend throws UnicodeEncodeError when used with Oracle
--+-
  Reporter:  jamesli  | Owner:  nobody  
 
Status:  new  | Milestone:  post-1.0
 
 Component:  django.contrib.sessions  |   Version:  1.0 
 
Resolution:   |  Keywords:  oracle session 
unicode UnicodeEncodeError
 Stage:  Unreviewed   | Has_patch:  0   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Comment (by ikelly):

 What version of cx_Oracle is being used in these setups?  My hope is that
 this is occurring with cx_Oracle 5.0, in which case the solution is easy:
 don't use that.  cx_Oracle 5.0 has a known NCLOB decoding bug that makes
 it unusable for Django (I suppose we should document this).  cx_Oracle
 trunk and the upcoming 5.0.1 release should be okay, as is the 4.4.1
 release.

 If you're not using cx_Oracle 5.0, let me know so we can investigate
 further.

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

Re: [Django] #9935: The session db backend throws UnicodeEncodeError when used with Oracle

[Django]

#9935: The session db backend throws UnicodeEncodeError when used with Oracle
--+-
  Reporter:  jamesli  | Owner:  nobody  
 
Status:  new  | Milestone:  post-1.0
 
 Component:  django.contrib.sessions  |   Version:  1.0 
 
Resolution:   |  Keywords:  oracle session 
unicode UnicodeEncodeError
 Stage:  Unreviewed   | Has_patch:  0   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Comment (by kmtracey):

 Egads, I'm guessing you did not preview what that looked like before
 submitting it?  The debug page has a "switch-to-cut-and-paste" link that
 is useful for extracting just the traceback instead of the 90K/2,000 lines
 of the html that makes up the debug page.  Using it to get just the
 traceback from that html:

 {{{

 Environment:

 Request Method: GET
 Request URL: http://lablnx04/accounts/login/
 Django Version: 1.0.2 final
 Python Version: 2.4.2
 Installed Applications:
 ['django.contrib.admin',
  'django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'discovery.edisco']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.middleware.doc.XViewMiddleware')


 Traceback:
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/core/handlers/base.py" in get_response
   86. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/views/decorators/cache.py" in _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/contrib/auth/views.py" in login
   33. request.session.set_test_cookie()
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/contrib/sessions/backends/base.py" in set_test_cookie
   78. self[self.TEST_COOKIE_NAME] = self.TEST_COOKIE_VALUE
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/contrib/sessions/backends/base.py" in __setitem__
   49. self._session[key] = value
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/contrib/sessions/backends/base.py" in _get_session
   172. self._session_cache = self.load()
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/contrib/sessions/backends/db.py" in load
   16. expire_date__gt=datetime.datetime.now()
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/models/manager.py" in get
   93. return self.get_query_set().get(*args, **kwargs)
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/models/query.py" in get
   304. num = len(clone)
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/models/query.py" in __len__
   160. self._result_cache = list(self.iterator())
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/models/query.py" in iterator
   275. for row in self.query.results_iter():
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/models/sql/query.py" in results_iter
   217. row = self.resolve_columns(row, fields)
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/backends/oracle/query.py" in resolve_columns
   52. values.append(self.convert_values(value, field))
 File "/usr/local/lib64/python2.4/site-packages/Django-1.0.2_final-
 py2.4.egg/django/db/backends/oracle/query.py" in convert_values
   59. value = value.read()

 Exception Type: UnicodeDecodeError at /accounts/login/
 Exception Value: 'utf16' codec can't decode bytes in position 120-121:
 illegal UTF-16 surrogate

 }}}

 It's similar but not quite the same.  Still have no clue what is going on
 in these error situations because I cannot recreate any problem on my own
 Oracle setup, and my knowedge of Oracle is just above zero (I was able to
 set it up for testing purposes, but I have not used it beyond that).

-- 
Ticket URL: 
Django 

Re: [Django] #9969: Admin change list view shows (None) instead of the real field value when it has been chosen from a choices named group

[Django]

#9969: Admin change list view shows (None) instead of the real field value when 
it
has been chosen from a choices named group
---+
  Reporter:  ramiro| Owner:  nobody 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  change list 
choices columns (None) named groups select dropdown
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

Needs_better_patch:  0 |  
---+
Comment (by SantiagoZarate):

 I've just patched my sistem... works perfectly!

 Thanks ramiro!

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

Re: [Django] #9976: Generic Foreign Keys should have a nice widget(ala raw_id)

[Django]

#9976: Generic Foreign Keys should have a nice widget(ala raw_id)
---+
  Reporter:  Alex  | Owner:  Alex
Status:  assigned  | Milestone:  
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Work on this can be found here:

 http://github.com/alex/django/commits/generic-foreign-key-widget

 (sorry not at a machine where I can produce a proper diff right now).

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

[Django] #9976: Generic Foreign Keys should have a nice widget(ala raw_id)

[Django]

#9976: Generic Foreign Keys should have a nice widget(ala raw_id)
--+-
 Reporter:  Alex  |   Owner:  Alex  
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 It would be nice if generic foreign keys could have a nice widget for the
 admin, right now they aren't very usable.

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

Re: [Django] #9681: Unable to load initial data with strings contained two dashes ('--')

[Django]

#9681: Unable to load initial data with strings contained two dashes ('--')
-+--
  Reporter:  Alexey Blinov   | Owner:  
nobody  
Status:  closed  | Milestone:   
   
 Component:  Database layer (models, ORM)|   Version:  1.0  
   
Resolution:  duplicate   |  Keywords:  sql, 
initial data, model
 Stage:  Unreviewed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 Dupe of #4680.

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

Re: [Django] #9975: initial data parsing error?

[Django]

#9975: initial data parsing error?
-+--
  Reporter:  antje.ga...@taconicartemis.com  | Owner:  nobody   
   
Status:  closed  | Milestone:   
   
 Component:  Database layer (models, ORM)|   Version:  
1.0-beta-1  
Resolution:  duplicate   |  Keywords:  syncdb, 
initial data
 Stage:  Unreviewed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Comment:

 This is a dupe of #4680 .

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

[Django] #9975: initial data parsing error?

[Django]

#9975: initial data parsing error?
+---
 Reporter:  antje.ga...@taconicartemis.com  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Database layer (models, ORM)| Version:  1.0-beta-1
 Keywords:  syncdb, initial data|   Stage:  Unreviewed
Has_patch:  0   |  
+---
 When I run syncdb with an SQL statement like this in e.g. foo/sql/bar.sql:

 INSERT INTO foo_bar (id, sequence)
 VALUES (1, 'ATTG--TTC');

 it quits with the message:
 Failed to install custom SQL for foo.Bar model: unterminated quoted string
 at or near "'ATTG;" at character ***
 (*** is the character number... I replaced and shortened my example here,
 so the original character # will not suit)

 Importing the bar.sql from postgres client itself works... that's why I
 think, the parser is interpreting everthing after '--' as comment... even
 within strings

 Has anybody already a bugfix yet? I couldn't find it here, but maybe I
 just didn't search for the right words.

 Thanks,
 Antje

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

Re: [Django] #9496: reverse() function doesn't seem to take account of the includer urlconf

[Django]

#9496: reverse() function doesn't seem to take account of the includer urlconf
+---
  Reporter:  seemant| Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kratorius):

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

Comment:

 Replying to [comment:7 kmtracey]: woops, sorry for closing this, I just
 made confusion with names.

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

Re: [Django] #9496: reverse() function doesn't seem to take account of the includer urlconf

[Django]

#9496: reverse() function doesn't seem to take account of the includer urlconf
+---
  Reporter:  seemant| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Replying to [comment:6 kratorius]:
 What's the reason for closing this as invalid?  The person (gogna) who
 said "sorry, I just found the error was mine. I apologize for the noise"
 is not the same as person who originally opened the ticket (seemant).  I
 do wish gonga had said what, exactly, the error was, perhaps it is the
 same problem as the original poster, but I'm not sure that's 100% obvious
 from what we have here.

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

Re: [Django] #5034: request.urlconf does not get used in URL template tag

[Django]

#5034: request.urlconf does not get used in URL template tag
-+--
  Reporter:  Trey| Owner:  SmileyChris  
 
Status:  new | Milestone:   
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  |  Keywords:  url, urlconf, 
override
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by apollo13):

 * cc: apollo13 (added)

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

Re: [Django] #9591: MemoryFileUploadHandler doesn't rewind InMemoryUploadedFile to the beginning

[Django]

#9591: MemoryFileUploadHandler doesn't rewind InMemoryUploadedFile to the
beginning
---+
  Reporter:  isagalaev | Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kratorius):

  * needs_better_patch:  => 0
  * component:  Uncategorized => File uploads/storage
  * needs_tests:  => 0
  * needs_docs:  => 0

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

Re: [Django] #9496: reverse() function doesn't seem to take account of the includer urlconf

[Django]

#9496: reverse() function doesn't seem to take account of the includer urlconf
+---
  Reporter:  seemant| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kratorius):

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

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

Re: [Django] #9939: Grammar error on doc page

[Django]

#9939: Grammar error on doc page
+---
  Reporter:  seemant| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kratorius):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Documentation
  * needs_tests:  => 0
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

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

[Django] #9974: Allow pluralize filter to consider zero as a singular form

[Django]

#9974: Allow pluralize filter to consider zero as a singular form
-+--
 Reporter:  david|   Owner:  david 
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 That's the case in French and probably with other languages, I can provide
 the fix but a design decision is needed on how to do this.

 It can be an argument on the pluralize filter or a new filter in
 localflavor but it seems overkill to me.

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

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  gav

Status:  new   | Milestone:  post-1.0   

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by gregoire):

 * cc: grego...@audacy.fr (added)

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