Re: [Django] #10342: login view should accept a form class

[Django]

#10342: login view should accept a form class
-+--
  Reporter:  steph   | Owner:  nobody   
   
Status:  closed  | Milestone:   
   
 Component:  Authentication  |   Version:  SVN  
   
Resolution:  duplicate   |  Keywords:  contrib auth login form 
override
 Stage:  Accepted| Has_patch:  1
   
Needs_docs:  1   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Changes (by julien):

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

Comment:

 Duplicate of #8274

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10596: There should be a better way to remove the actions provided by parent classes

[Django]

#10596: There should be a better way to remove the actions provided by parent
classes
---+
  Reporter:  ElliottM  | Owner:  nobody
Status:  reopened  | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:  admin bulk default
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * status:  closed => reopened
  * summary:  There should be a way to remove the "Delete selected items"
  bulk admin action. => There should be a better
  way to remove the actions provided by parent
  classes
  * version:  1.0-beta-1 => SVN
  * milestone:  => 1.1
  * resolution:  duplicate =>
  * stage:  Unreviewed => Accepted

Comment:

 Reopened with a better, more general title; I agree this needs to be fixed
 for the feature to be generally 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] #10641: manage.py runserver fails on windows

[Django]

#10641: manage.py runserver fails on windows
+---
  Reporter:  anonymous  | Owner:  nobody   
Status:  closed | Milestone:  1.0.3
 Component:  Documentation  |   Version:  1.0  
Resolution:  invalid|  Keywords:  runserver
 Stage:  Unreviewed | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by julien):

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

Comment:

 It would be more appropriate to ask the question on the user-list
 (http://groups.google.com/group/django-users/topics) since it's probably
 not a bug in Django. Likely, you'd need to add your project's parent
 folder in the PYTHONPATH.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10641: manage.py runserver fails on windows

[Django]

#10641: manage.py runserver fails on windows
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:  1.0.3 
Component:  Documentation  | Version:  1.0   
 Keywords:  runserver  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 following the setup and tutorial word for word under winxp fails when
 attempting to execute manage.py runserver to get the test webserver
 running. fails with the following

 "No such module MYSITE"

 PATH is set and installation was by the book. import django loads
 successfully.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10357: "manage.py dbshell" broken for MySQL on Windows

[Django]

#10357: "manage.py dbshell" broken for MySQL on Windows
--+-
  Reporter:  anonymous| Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  django-admin.py  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Comment (by jumpfroggy):

 Ahh, found the root of my redirection bug.  Found here
 (http://www.velocityreviews.com/forums/t318845-piping-data-into-python-on-
 the-command-line-windows-2000.html).  The bug is in cmd.exe.  So running
 this fails on windows: `manage.py dbshell < data.sql`, but running this on
 windows works `python manage.py dbshell < data.sql`.  Finally, an answer!
 Stupid windows.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10357: "manage.py dbshell" broken for MySQL on Windows

[Django]

#10357: "manage.py dbshell" broken for MySQL on Windows
--+-
  Reporter:  anonymous| Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  django-admin.py  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Changes (by jumpfroggy):

 * cc: vir...@rocketmonkeys.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] #10357: "manage.py dbshell" broken for MySQL on Windows

[Django]

#10357: "manage.py dbshell" broken for MySQL on Windows
--+-
  Reporter:  anonymous| Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  django-admin.py  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Comment (by jumpfroggy):

 I'm experiencing some problems related to this bug.  I filed a DUP bug
 here (http://code.djangoproject.com/ticket/10639) with the same symptoms
 (mysql.exe executing in the background).  I tried the db.patch from here,
 and it does allow me to execute `manage.py dbshell` and use the mysql
 client.  However, it does not work for `manage.py dbshell < data.sql`,
 which is what I really want to do.  In that case, the mysql client
 executes as if it had never seen the `< data.sql` redirection, and is in
 interactive mode.

 Seems like there's some issue with pipe redirection going on... any ideas
 why this doesn't work with the above fix?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10639: "manage.py dbshell" on windows causes strange command line / mysql switching bug

[Django]

#10639: "manage.py dbshell" on windows causes strange command line / mysql
switching bug
+---
  Reporter:  jumpfroggy | Owner:  nobody 
Status:  closed | Milestone: 
 Component:  Uncategorized  |   Version:  1.0
Resolution:  duplicate  |  Keywords:  dbshell windows
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by jumpfroggy):

 I'm trying the patch, looks like it's better but not fixed completely.
 I'll comment more in that thread.  Thx.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10640: Add `add_form_template` option to ModelAdmin

[Django]

#10640: Add `add_form_template` option to ModelAdmin
--+-
 Reporter:  dcramer   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In some use cases we've found that we need to slightly tweak our change
 templates. Typically this is because the change view isn't directly
 changing the object, but it's handling it in some other way.

 One small problem that came across was there's no way to specify the add
 page's template versus the change page's template.

 I propose simply modifying render_change_form, to check for add=True, and
 if it's present, check for add_form_template. If add_form_template is set
 in the ModelAdmin to a value it should look for that template first. If
 it's set to None, it should use the default templates (and not
 change_form_template).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #7052: auth fixture fails to import when running test server

[Django]

#7052: auth  fixture fails to import when running test server
+---
  Reporter:  jb0t   | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Serialization  |   Version:  SVN   
 
Resolution: |  Keywords:  auth_permission 
auth_content fixture import
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by russ):

 * cc: russ.a...@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] #10639: "manage.py dbshell" on windows causes strange command line / mysql switching bug

[Django]

#10639: "manage.py dbshell" on windows causes strange command line / mysql
switching bug
+---
  Reporter:  jumpfroggy | Owner:  nobody 
Status:  closed | Milestone: 
 Component:  Uncategorized  |   Version:  1.0
Resolution:  duplicate  |  Keywords:  dbshell windows
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 I suspect this is due to the same root cause as #10357.  You might try the
 latest patch there and see if it solves what you are seeing, it would be
 useful either way to get feedback on that patch in #10357.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10638: Inline forms do not render correctly for models with custom primary keys

[Django]

#10638: Inline forms do not render correctly for models with custom primary keys
+---
  Reporter:  dgouldin   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 #8903 already reports this, I believe.  I noted there the existence of a
 patch here for it.

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

Re: [Django] #8903: admin.TabularInline creates duplicate pk input boxes

[Django]

#8903: admin.TabularInline creates duplicate pk input boxes
---+
  Reporter:  Spads | Owner:  Spads  
Status:  assigned  | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords:  admin TabularInline
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 #10638 reports this again and has a patch.

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

Re: [Django] #10639: "manage.py dbshell" on windows causes strange command line / mysql switching bug

[Django]

#10639: "manage.py dbshell" on windows causes strange command line / mysql
switching bug
+---
  Reporter:  jumpfroggy | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Uncategorized  |   Version:  1.0
Resolution: |  Keywords:  dbshell windows
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jumpfroggy):

 * cc: vir...@rocketmonkeys.com (added)
  * 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-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] #10639: "manage.py dbshell" on windows causes strange command line / mysql switching bug

[Django]

#10639: "manage.py dbshell" on windows causes strange command line / mysql
switching bug
-+--
 Reporter:  jumpfroggy   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.0   
 Keywords:  dbshell windows  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 This is hard to explain.  I run this on a Windows XP machine:

 {{{
 C:\project>manage.py dbshell
 C:\project>Welcome to the MySQL monitor.  Commands end with ; or \
 g.
 Your MySQL connection id is 6902
 Server version: 5.0.51a-community-nt-log MySQL Community Edition (GPL)
 Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
 mysql>
 }}}

 Basically what happens is that every other command goes to either the
 mysql.exe client or the original command line shell (cmd.exe) in
 alternating order.  So if you keep pressing enter/return, you get this:

 {{{
 mysql>
 C:\project>
 mysql>
 C:\project>
 }}}

 And if you do type in "show tables;" three times, you get this:

 {{{
 mysql> show tables;
 'show' is not recognized as an internal or external command,
 operable program or batch file.

 C:\project>show tables;
 (shows tables here)
 26 rows in set (0.00 sec)

 mysql> show tables;
 'show' is not recognized as an internal or external command,
 operable program or batch file.
 }}}

 The first response (show is not recognized) is from cmd.exe.  The second
 result is from mysql.exe.  The third result is again from cmd.exe.

 I think that manage.py is executing the mysql.exe process concurrently
 with the opening command line, and the STDIN and STDOUT are being merged
 together.  Since they both block for input, when you enter a command in
 one and press enter, the "focus" switches to the other process.

 All of this works on unix, so it seems to be a Windows-only problem.  Can
 anyone else confirm?

  * Django SVN rev 9014 (Apologies for running an older version of
 Django... production server is running 1.0, so I can't upgrade my dev
 machine at the moment).
  * Windows XP SP3
  * Python 2.5.2

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10638: Inline forms do not render correctly for models with custom primary keys

[Django]

#10638: Inline forms do not render correctly for models with custom primary keys
+---
  Reporter:  dgouldin   | 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 dgouldin):

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

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

[Django] #10638: Inline forms do not render correctly for models with custom primary keys

[Django]

#10638: Inline forms do not render correctly for models with custom primary keys
---+
 Reporter:  dgouldin   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When using a model with a custom primary key as an inline in the admin,
 the primary key field is rendered twice and tabular's field count is off
 by one.

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

Re: [Django] #8746: Data entered in raw_id_fields needs better checking

[Django]

#8746: Data entered in raw_id_fields needs better checking
---+
  Reporter:  kmtracey  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by dgouldin):

 * cc: dgoul...@gmail.com (added)
  * 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-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] #9264: ModelAdmin: multipe items in prepopulated_fields breaks the auto-fillin

[Django]

#9264: ModelAdmin: multipe items in prepopulated_fields breaks the auto-fillin
---+
  Reporter:  pickel...@gmail.com   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by dgouldin):

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

Comment:

 I was not able to reproduce this.  Can anybody else?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9651: [9297] breaks save_as in inline admin forms

[Django]

#9651: [9297] breaks save_as in inline admin forms
---+
  Reporter:  yamad | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  django.contrib.admin  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by isometry):

 * cc: isometry (added)
  * milestone:  => 1.1

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

Re: [Django] #9696: FileField raises unhandled exception when filename contains non-ascii characters

[Django]

#9696: FileField raises unhandled exception when filename contains non-ascii
characters
---+
  Reporter:  magarac   | Owner:  kmtracey
Status:  new   | Milestone:  1.1 
 Component:  File uploads/storage  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by oyiptong):

 I fixed my problem. It was a server configuration issue. For some reason,
 the LANG environment variable wasn't being set.

 I could not reproduce the issue on my development machine, which had me
 look at my production server's environment.
 The unicode characters are not stripped, but its fine now that env vars
 are set properly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10636: Development server fails if settings module does not define ADMIN_MEDIA_PREFIX

[Django]

#10636: Development server fails if settings module does not define
ADMIN_MEDIA_PREFIX
--+-
  Reporter:  Lee Phillips   | 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 Lee Phillips ):

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

Comment:

 Replying to [comment:1 kmtracey]:
 OK, your explanation is good, so I've changed my ticket to "invalid" (I
 hope that's the right thing). My naive expectation was that, since I
 didn't have any admin media, that it was better to not define a place for
 the server to look for it, but, as you've explained, the side-effect was
 that all URLs were interpreted requests for admin media. Maybe a little
 extra documentation would be in order?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #3999: django-admin.py template dir argument

[Django]

#3999: django-admin.py template dir argument
-+--
  Reporter:  stuff4...@gmail.com | Owner:  adrian
Status:  closed  | Milestone:
 Component:  django-admin.py |   Version:  SVN   
Resolution:  wontfix |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by gsong):

 Or just write a custom command to plug into `manage.py`.

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

Re: [Django] #2612: Fix admin formatting when help_text used with multiple fields on the same line

[Django]

#2612: Fix admin formatting when help_text used with multiple fields on the same
line
-+--
  Reporter:  Andy Dustman   | Owner:  xian 
  
Status:  closed  | Milestone:  1.0  
  
 Component:  django.contrib.admin|   Version:  SVN  
  
Resolution:  fixed   |  Keywords:  
nfa-someday
 Stage:  Accepted| Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  1
  
Needs_better_patch:  1   |  
-+--
Changes (by anonymous):

 * cc: a...@andybak.net (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] #10635: list_editable: mention Meta class in ordering exception

[Django]

#10635: list_editable: mention Meta class in ordering exception
---+
  Reporter:  mkb...@gmail.com  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Documentation |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * status:  closed => reopened
  * resolution:  invalid =>
  * component:  django.contrib.admin => Documentation
  * summary:  list_editable: logic error when checking for ordering
  property => list_editable: mention Meta class
  in ordering exception

Comment:

 Reopening, and reassigning to docs with a changed summary.

 I had an ordering property on the model object, not the
 interior Meta class for the model object.  This was what
 caused that conditional to fail for me; then I moved the
 property to the admin object and somehow thought it was
 still failing eh voila, my "patch" worked.

 I suggest that the error message explicitly
 mention the Meta class; maybe something like this:

 Please define ordering on either %s or %s's Meta class.


 If I had seen Meta in the message, I would have wondered what
 it was, searched the docs, and figured out that on the model
 object (unlike the admin object), the ordering property should
 be an attribute of the interior Meta class, not the model class
 itself.

 I think it's worth documenting to draw attention to the
 different place this property lives on the admin and
 model object.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #7567: modpython.authenhandler does not work

[Django]

#7567: modpython.authenhandler does not work
-+--
  Reporter:  dannychen   | Owner:
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  0.96  
Resolution:  fixed   |  Keywords:  mod_python
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by sneakeralley):

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #2812: Simplified Chinese Translation updated

[Django]

#2812: Simplified Chinese Translation updated
+---
  Reporter:  limo...@gmail.com  | Owner:  hugo
Status:  closed | Milestone:  
 Component:  Translations   |   Version:  
Resolution:  fixed  |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by sneakeralley):

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #7054: help_text breaks formatting in Admin when using Admin option 'fields' to display several fields on the same line

[Django]

#7054: help_text breaks formatting in Admin when using Admin option 'fields' to
display several fields on the same line
+---
  Reporter:  Andy Baker   | Owner:  rmyers
   
Status:  closed | Milestone:  1.0   
   
 Component:  django.contrib.admin   |   Version:  SVN   
   
Resolution:  duplicate  |  Keywords:  admin css 
help_text fields newforms-admin
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Comment (by sneakeralley):

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #3825: crash on sorting on foreign key with default ordering desc

[Django]

#3825: crash on sorting on foreign key with default ordering desc
--+-
  Reporter:  David S.   | Owner:  
adrian 
Status:  closed   | Milestone:  
   
 Component:  Database layer (models, ORM) |   Version:  
SVN
Resolution:  duplicate|  Keywords:  
ordering foreignkey
 Stage:  Accepted | Has_patch:  
1  
Needs_docs:  0|   Needs_tests:  
0  
Needs_better_patch:  1|  
--+-
Comment (by sneakeralley):

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #2721: [patch] Allow block tags to be commented out

[Django]

#2721: [patch] Allow block tags to be commented out
--+-
  Reporter:  SmileyChris  | Owner:  adrian  
 
Status:  closed   | Milestone:  
 
 Component:  Template system  |   Version:  
 
Resolution:  wontfix  |  Keywords:  Nike Air Force One, Air 
Force 1, Air Force One, Air Force Shoes, Nike Air Force 1
 Stage:  Unreviewed   | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Changes (by sneakeralley):

  * keywords:  => Nike Air Force One, Air Force 1, Air Force One, Air Force
   Shoes, Nike Air Force 1

Comment:

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #4330: formtools.preview.FormPreview unused_name uses non-instance form

[Django]

#4330: formtools.preview.FormPreview unused_name uses non-instance form
+---
  Reporter:  Daniel Blasco   | Owner:  
adrian  
 
Status:  closed | Milestone:
   
 Component:  django.contrib.formtools   |   Version:  SVN   
   
Resolution:  fixed  |  Keywords:  Nike 
Air Force One, Air Force 1, Air Force One, Air Force Shoes, Nike Air Force 1
 Stage:  Ready for checkin  | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by sneakeralley):

  * keywords:  => Nike Air Force One, Air Force 1, Air Force One, Air Force
   Shoes, Nike Air Force 1

Comment:

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #4465: Invalid sql string formatting (TypeError) if sql contains '%' signs in /django/db/backends/util.py

[Django]

#4465: Invalid sql string formatting (TypeError) if sql contains '%' signs in
/django/db/backends/util.py
---+
  Reporter:  MockSoul  | Owner:  adrian 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  0.96   
  
Resolution:  duplicate |  Keywords:  Nike Air 
Force One, Air Force 1, Air Force One, Air Force Shoes, Nike Air Force 1
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by sneakeralley):

  * keywords:  => Nike Air Force One, Air Force 1, Air Force One, Air Force
   Shoes, Nike Air Force 1

Comment:

 [http://www.sneakeralley.com Nike Air Force One]

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

Re: [Django] #10636: Development server fails if settings module does not define ADMIN_MEDIA_PREFIX

[Django]

#10636: Development server fails if settings module does not define
ADMIN_MEDIA_PREFIX
--+-
  Reporter:  Lee Phillips   | Owner:  
nobody
Status:  new  | 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 kmtracey):

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

Comment:

 So don't do that?  The development server has a built-in admin media
 server that keys off of ADMIN_MEDIA_PREFIX -- any url that beings with
 ADMIN_MEDIA_PREFIX is routed to the built-in server that serves the files
 in the admin media directory.  So if you set ADMIN_MEDIA_PREFIX to "", I'd
 guess everything gets routed to the built-in media server, which of course
 isn't going to work.  It probably won't even be able to server the admin
 media files since the setting is expected (as noted in the comment for it
 in settings.py) to include a trailing slash, and you left even that out.
 It isn't clear what you expect to happen 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-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] #10637: Documentation of fixture loading misleading

[Django]

#10637: Documentation of fixture loading misleading
---+
 Reporter:  arkx   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Django documentation at
 http://docs.djangoproject.com/en/dev/topics/testing/#fixture-loading says
 this about fixture placement:

 ''Once you've created a fixture and placed it somewhere in your Django
 project, you can use it in your unit tests by specifying a fixtures class
 attribute on your django.test.TestCase subclass.''

 However, this is wrong: Django looks specifically at fixtures/
 subdirectory in each app. The word "somewhere" is too ambiguous -- the
 exact behaviour of Django should be documented 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] #9696: FileField raises unhandled exception when filename contains non-ascii characters

[Django]

#9696: FileField raises unhandled exception when filename contains non-ascii
characters
---+
  Reporter:  magarac   | Owner:  kmtracey
Status:  new   | Milestone:  1.1 
 Component:  File uploads/storage  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 For people who are experiencing this, have you (or the code you are using)
 done something to override the default django.core.files.Storage
 `get_valid_name` method?  That routine strips all "non-filename-safe"
 characters from the name, so I cannot easily recreate the exception you
 are seeing by simply, say, trying to upload a file using admin and a model
 that contains a simple !FileField.  (Which indicates the 2nd part of #6009
 had not been fixed, despite the testcases added, but that's a different
 issue.)  It would help if someone could provide a small reproducible
 testcase that demonstrates this exception, as it involves more than just
 uploading a file with unicode chars in the name using all normal defaults
 in admin...when doing that, the unicode chars are stripped and the
 exception does not happen.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10635: list_editable: logic error when checking for ordering property

[Django]

#10635: list_editable: logic error when checking for ordering property
---+
  Reporter:  mkb...@gmail.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.1-beta-1
Resolution:  invalid   |  Keywords:
 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:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This looks correct, we want it to evaluate that code only when there isn't
 an ordering:
 {{{
 [1] >>> not ([] or [])
   [1] : True

 [2] >>> not ([] or [''])
   [2] : False

 [3] >>> not ([''] or [])
   [3] : False
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9409: "OperationalError: database is locked" with Python 2.6 multiprocessing and SQLite backend

[Django]

#9409: "OperationalError: database is locked" with Python 2.6 multiprocessing 
and
SQLite backend
+---
  Reporter:  mrts   | Owner:  nobody
Status:  reopened   | Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bthomas):

  * 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-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] #10636: Development server fails if settings module does not define ADMIN_MEDIA_PREFIX

[Django]

#10636: Development server fails if settings module does not define
ADMIN_MEDIA_PREFIX
-+--
 Reporter:  Lee Phillips   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I defined ADMIN_MEDIA_PREFIX = "" in my settings module and found that
 this caused the development server to not work: all requests for URLs
 returned a "URL not found", and the server did not log the requests to
 stdout as it normally does. Setting ADMIN_MEDIA_PREFIX to any nonempty
 string fixes this.

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

[Django] #10635: list_editable: logic error when checking for ordering property

[Django]

#10635: list_editable: logic error when checking for ordering property
--+-
 Reporter:  mkb...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1-beta-1
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 {{{
 >>> l = (opts.ordering or cls.ordering)
 >>> l
 [ '-id' ]
 >>> not l
 False
 >>>
 }}}

 Following patch fixes this bug.

 {{{
 To apply:
 $ cd 
 $ patch -p0 < contrib.admin.validate.patch0

 For example,
 $ cd /usr/lib/python2.5/site-packages/django/
 $ sudo patch -p0 < $OLDPWD/contrib.admin.validate.patch0
 $ cd -


 --- /dev/null
 +++ ./contrib/admin/validation.py   2009-03-26 10:37:36.0
 -0400
 @@ -67,7 +67,7 @@
  # list_editable
  if hasattr(cls, 'list_editable') and cls.list_editable:
  check_isseq(cls, 'list_editable', cls.list_editable)
 -if not (opts.ordering or cls.ordering):
 +if not len(opts.ordering or cls.ordering):
  raise ImproperlyConfigured("'%s.list_editable' cannot be used
 "
  "without a default ordering. Please define ordering on
 either %s or %s."
  % (cls.__name__, cls.__name__, model.__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-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] #9696: FileField raises unhandled exception when filename contains non-ascii characters

[Django]

#9696: FileField raises unhandled exception when filename contains non-ascii
characters
---+
  Reporter:  magarac   | Owner:  kmtracey
Status:  new   | Milestone:  1.1 
 Component:  File uploads/storage  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * owner:  nobody => kmtracey
  * status:  reopened => new

Comment:

 This looks similar to #9579.  We can't necessarily pass unicode into
 Python's os.path routines.  In fact I see there is an
 os.path.supports_unicode_filenames that may be what we are supposed to
 consult to determine whether we can pass unicode in or if we must encode
 to a bytestring before calling the os.path routines.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10634: Confusing differential exceptions: get_or_create vs get with psycopg2

[Django]

#10634: Confusing differential exceptions: get_or_create vs get with psycopg2
---+
 Reporter:  fergusferrier  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Database layer (models, ORM)   | Version:  SVN   
 Keywords:  psycopg2 get_or_create get misleading  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I'm using Psycopg2. I hope the models here are somewhat self-explanatory
 in structure.

 I made the simple mistake of forgetting the boolean 'created' in a
 get_or_create...

 {{{
usr = EventsUser.objects.get_or_create(user = request.user)
 }}}

 Then running the following code [NB. usr is not an instance of EventsUser
 at this point]...

 {{{
 Reminder.objects.get_or_create(
 events_user = usr,
 event = event,
 assoctype = 'EML_HR'
 )
 }}}

 gives thus:

 {{{
 Traceback (most recent call last):
   File
 "/home/django/domains/staging.mypidge.com/project/Apps/Events/tests/views.py",
 line 418, in test_set_reminder_unset
 response = self.client.get(reverse('Events.views.SetReminders',
 args=[self.event.id]), {'day': '1', 'hour': '1'})
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/test/client.py", line 278, in get
 response = self.request(**r)
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/core/handlers/base.py", line 91, in get_response
 response = callback(request, *callback_args, **callback_kwargs)
   File
 "/home/django/domains/staging.mypidge.com/project/Apps/basic/funcs.py",
 line 35, in decorator
 return f(request, *args, **kwargs)
   File
 "/home/django/domains/staging.mypidge.com/project/Apps/Events/views.py",
 line 319, in SetReminders
 assoctype = 'EML_HR'
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/manager.py", line 120, in get_or_create
 return self.get_query_set().get_or_create(**kwargs)
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/query.py", line 365, in get_or_create
 return self.get(**kwargs), False
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/query.py", line 337, in get
 num = len(clone)
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/query.py", line 161, in __len__
 self._result_cache = list(self.iterator())
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/query.py", line 281, in iterator
 for row in self.query.results_iter():
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/sql/query.py", line 256, in results_iter
 for rows in self.execute_sql(MULTI):
   File "/home/django/domains/mypidge.com/env/lib/python2.5/site-
 packages/django/db/models/sql/query.py", line 2098, in execute_sql
 cursor.execute(sql, params)
   File "build/bdist.linux-x86_64/egg/psycopg2/extensions.py", line 96, in
 getquoted
 pobjs = [adapt(o) for o in self._seq]
 ProgrammingError: can't adapt
 }}}

 When one replaces the second get_or_create with a plain get, you are
 returned
 {{{
 ValueError: Cannot assign "(, False)":
 "Reminder.events_user" must be a "EventsUser" instance.
 }}}

 which is a much more useful exception. I would expect get_or_create to
 return a similar.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9696: FileField raises unhandled exception when filename contains non-ascii characters

[Django]

#9696: FileField raises unhandled exception when filename contains non-ascii
characters
---+
  Reporter:  magarac   | Owner:  nobody
Status:  reopened  | Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by oyiptong):

 I have this issue as well.

 I reproduced this by uploading a file with a filename containing unicode
 characters: "Peña.cbz"

 {{{
 Environment:

 Request Method: POST
 Request URL: http://staging.getcomicstrips.com/library/upload
 Django Version: 1.0.2 final
 Python Version: 2.5.2
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'django.contrib.admin',
  'getcomics.library',
  'getcomics.downloader',
  'getcomics.rest_ws',
  'getcomics.jobserver']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware')


 Traceback:
 File "/usr/lib/python2.5/site-packages/django/core/handlers/base.py" in
 get_response
   86. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/usr/lib/python2.5/site-packages/django/contrib/auth/decorators.py"
 in __call__
   67. return self.view_func(request, *args, **kwargs)
 File
 
"/u/apps/getcomics/releases/20090325215603/getcomics/../getcomics/library/views.py"
 in user_upload
   50. pub = new_form.save()
 File "/usr/lib/python2.5/site-packages/django/forms/models.py" in save
   319. return save_instance(self, self.instance,
 self._meta.fields, fail_message, commit)
 File "/usr/lib/python2.5/site-packages/django/forms/models.py" in
 save_instance
   61. f.save_form_data(instance, cleaned_data[f.name])
 File "/usr/lib/python2.5/site-packages/django/db/models/fields/files.py"
 in save_form_data
   192. getattr(instance, self.name).save(data.name, data,
 save=False)
 File "/usr/lib/python2.5/site-packages/django/db/models/fields/files.py"
 in save
   74. self._name = self.storage.save(name, content)
 File "/usr/lib/python2.5/site-packages/django/core/files/storage.py" in
 save
   44. name = self.get_available_name(name)
 File "/usr/lib/python2.5/site-packages/django/core/files/storage.py" in
 get_available_name
   66. while self.exists(name):
 File "/usr/lib/python2.5/site-packages/django/core/files/storage.py" in
 exists
   188. return os.path.exists(self.path(name))
 File "/usr/lib/python2.5/posixpath.py" in exists
   171. st = os.stat(path)

 Exception Type: UnicodeEncodeError at /library/upload
 Exception Value: 'ascii' codec can't encode character u'\xf1' in position
 49: ordinal not in range(128)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8408: add a new meta option: don't do count(*) in admin

[Django]

#8408: add a new meta option: don't do count(*) in admin
---+
  Reporter:  lidaobing | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  0.96  
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mrts):

  * milestone:  => 1.2

Comment:

 Having problems with large datasets in admin myself (not sure if `count()`
 is the only reason though), proposing this for 1.2.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10633: Missing msgids for comment application

[Django]

#10633: Missing msgids for comment application
-+--
 Reporter:  zgoda|   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.comments  | Version:  SVN   
 Keywords:  translations i18n|   Stage:  Unreviewed
Has_patch:  1|  
-+--
 The comment framework is missing many msgids (translation keys), rendering
 it partially in English in admin site. Attached patch adds translation
 markers for comment application models.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10631: Documentation: SQL for second exclude example is incorrect

[Django]

#10631: Documentation: SQL for second exclude example is incorrect
+---
 Reporter:  muffinresearch  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Documentation   | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 See http://docs.djangoproject.com/en/dev/ref/models/querysets/#exclude-
 kwargs

 The second example has AND instead of OR.

 {{{
 SELECT ...
 WHERE NOT pub_date > '2005-1-3'
 AND NOT headline = 'Hello'
 }}}

 Should be:

 {{{
 SELECT ...
 WHERE NOT pub_date > '2005-1-3'
 OR NOT headline = 'Hello'
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10630: [PATCH] GZipMiddleware does not handle all MSIE issues.

[Django]

#10630: [PATCH] GZipMiddleware does not handle all MSIE issues.
-+--
 Reporter:  sebastian_noack  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 There is a hook in the GZipMiddleware which bypass compression for
 javascript and pdfs, if user agent is MSIE. But I had to note that there
 are more situations where MSIE sucks. For example zip archives are not
 decompressed by Internet Explorer, instead MSIE saves a gzip compressed
 zip archive (which you can't open), even when using the latest version of
 Internet Explorer. So because of MSIE sucks so much and there might be
 another cases where compression leads to problems, I think the best
 aproach is to bypass compression for each non-text content type, when
 using MSIE. I have written a patch for that, see attachment.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9749: ModelAdmin should allow specifying Changelist class to further modify Changelist behavior

[Django]

#9749: ModelAdmin should allow specifying Changelist class to further modify
Changelist behavior
---+
  Reporter:  anonymous | Owner:  brosner
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:|  Keywords:  ModelAdmin 
Changelist subclass
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by zgoda):

 * cc: jarek.zg...@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
-~--~~~~--~~--~--~---

[Django] #10629: allow login redirects to traverse a secure connection

[Django]

#10629: allow login redirects to traverse a secure connection
+---
 Reporter:  rfk |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  SVN   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 To protect user's login details in-transit, I like to have my login page
 submit over a secure connection, redirecting the user back to an unsecured
 connection once the login has been established.  Something along the
 following lines:

1. Unauthenticated user requests http://site/private/
2. They're redirected to http://site/login/
3. They submit their details securely to https://site/login/
4. This establishes the login and redirects to http://site/private/

 The standard contrib.auth views and decorators almost get me there, but
 they don't like switching protocols during the redirect.  Attached is a
 simple patch that lets contrib.auth support the above workflow by doing
 two things:

   *  allowing the 'next' argument to auth.views.login to contain a full
 URL, as long as it points to the correct host and not a third-party site
   *  having the various auth decorators record the full URL when
 redirecting to the login page, rather than just the path information

 I imagine that having logins traverse a secure connection like this would
 be fairly common practice, so it'd be great to see support for it in the
 core distribution.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10628: RelatedManager and NULL

[Django]

#10628: RelatedManager and NULL
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Please ask support questions on the django-users mailing list. The SQL
 output you are getting for the filter you have given is not incorrect.
 There is no bug 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] #10623: scheme for filtering an object based on a ManyToManyField or a reverse ForeignKeyField

[Django]

#10623: scheme for filtering an object based on a ManyToManyField or a reverse
ForeignKeyField
+---
  Reporter:  while0pass | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 The suggested change isn't correct. All successive `filter()` calls are
 combined with "AND", no matter what fields care involved. You can see this
 from looking at the generated SQL.

 Perhaps you are being confused by the fact that successive filters against
 multi-valued tables use separate copies of the table each time? The very
 section you refer to in the documentation explains exactly that. The
 filters are all combined simultaneously to the object being filtered (that
 is, they are "AND"-ed together) and only objects that meet all filter()
 criteria are in the final result set.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10628: RelatedManager and NULL

[Django]

#10628: RelatedManager and NULL
---+
  Reporter:  anonymous | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * status:  closed => reopened
  * 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] #10628: RelatedManager and NULL

[Django]

#10628: RelatedManager and NULL
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 I need:
 AND `doska_active`.`type_id` = %s  AND '''`doska_active`.`rubrica_id` IS
 NULL'''

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10623: scheme for filtering an object based on a ManyToManyField or a reverse ForeignKeyField

[Django]

#10623: scheme for filtering an object based on a ManyToManyField or a reverse
ForeignKeyField
+---
  Reporter:  while0pass | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by while0pass):

  * status:  closed => reopened
  * 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] #10628: RelatedManager and NULL

[Django]

#10628: RelatedManager and NULL
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Your filter is asking for things where `rubrica__isnull=True`, which is
 why that comparison to NULL is in the query. That's the correct SQL for
 that filter.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10628: RelatedManager and NULL

[Django]

#10628: RelatedManager and NULL
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1-beta-1
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 My Model:

 {{{
 class Active(models.Model):
  post= models.ForeignKey(Post, related_name='activeposts')
  rubrica = models.ForeignKey(Rubrica, related_name='activeposts',
 null=True, blank=True)
  type= models.ForeignKey(Type, related_name='activeposts', null=True,
 blank=True)
 }}}

 Code:
 {{{
 >>> p = Post.objects.get(pk=1206535731)
 >>> p.activeposts.filter(type__pk=2, rubrica__isnull=True)
 }}}

 return empty result. but a have data in database.

 {{{
 >>> p.activeposts.filter(type__exact=2,
 rubrica__isnull=True).query.as_sql()
 ('SELECT `doska_active`.`id`, `doska_active`.`post_id`,
 `doska_active`.`rubrica_id`, `doska_active`.`type_id` FROM `doska_active`
 LEFT OUTER JOIN `doska_rubrica` ON (`doska_active`.`rubrica_id` =
 `doska_rubrica`.`id`) WHERE (`doska_active`.`post_id` = %s  AND
 `doska_active`.`type_id` = %s  AND `doska_rubrica`.`id` IS NULL)',
 (1206535731, 2))
 }}}

 Problem in '''AND `doska_rubrica`.`id` IS NULL'''

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10623: scheme for filtering an object based on a ManyToManyField or a reverse ForeignKeyField

[Django]

#10623: scheme for filtering an object based on a ManyToManyField or a reverse
ForeignKeyField
+---
  Reporter:  while0pass | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by while0pass):

 I wanted that in documentation section "filtering an object based on a
 ManyToManyField or a reverse ForeignKeyField" one would add some text with
 idea that, in general, conditions within a filter are composed through
 AND-operation, the same is true for composition of filters. But when
 conditions deal with an object based on a ManyToManyField or a reverse
 ForeignKeyField composition of filters goes through OR, not through AND-
 operation.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---