Re: [Django] #12386: Automatic ManyToMany Fields in models defined in packages use invalid column names

[Django]

#12386: Automatic ManyToMany Fields in models defined in packages use invalid
column names
---+
  Reporter:  ldevesine | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by simonb):

 It seems that 1.2 produces a different column name for the m2m field when
 there are more than one m2m field in a model. I will attach a sample
 project that demonstrates this.

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

Re: [Django] #12607: django.test.client.Client changes the HTTP method to "GET" when doing a redirect.

[Django]

#12607: django.test.client.Client changes the HTTP method to "GET" when doing a
redirect.
+---
  Reporter:  pbiggar| Owner:  nobody
   
Status:  closed | Milestone:  1.2   
   
 Component:  Testing framework  |   Version:  1.2-alpha 
   
Resolution:  invalid|  Keywords:  get redirect 
_handle_redirect
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Comment (by Alex):

 I just read through RFC2616 and you are correct that the spec says that
 you are supposed to redirect using the same request method, however the
 spec specifically notes that most clients transform any redirects into a
 GET, this is the behavior of most web browsers, AFAIK.  I think the
 solution here might be for you to just use follow=False and do the
 redirect tracking manually, as I think the django test client wants to
 stay similar to browsers.

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

Re: [Django] #12607: django.test.client.Client changes the HTTP method to "GET" when doing a redirect.

[Django]

#12607: django.test.client.Client changes the HTTP method to "GET" when doing a
redirect.
+---
  Reporter:  pbiggar| Owner:  nobody
   
Status:  closed | Milestone:  1.2   
   
 Component:  Testing framework  |   Version:  1.2-alpha 
   
Resolution:  invalid|  Keywords:  get redirect 
_handle_redirect
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This is the intended behavior - the test client is doing exactly what a
 browser does. If you POST to a URL, and the POST returns a redirect, the
 browser doesn't POST the request to the redirected URL - it *always* uses
 GET for the redirected URL.

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

[Django] #12607: django.test.client.Client changes the HTTP method to "GET" when doing a redirect.

[Django]

#12607: django.test.client.Client changes the HTTP method to "GET" when doing a
redirect.
---+
 Reporter:  pbiggar|   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Testing framework  | Version:  1.2-alpha 
 Keywords:  get redirect _handle_redirect  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 With the code:

 Client().post(path, {}, follow=True)

 where path causes a redirect, the HTTP verb will be changed to a GET. This
 is probably due to line 949 of
 http://code.djangoproject.com/svn/django/trunk/django/test/client.py.
 _handle_redirect is called from post(), put(), delete() etc, even though
 it redirects by calling get().

 (My knowledge of HTTP is hazy, but it seems wrong to change this.)

 Workaround: make sure tests dont redirect (which probably means avoid the
 automatic redirection of leaving a '/' off the end of paths).

 I'm experiencing this with Django 1.1, but it looks like its still present
 in svn.

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

Re: [Django] #11263: Bug in lookup with generic relation in model inheritance

[Django]

#11263: Bug in lookup with generic relation in model inheritance
---+
  Reporter:  veena | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  generic 
relations, model inheritance
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 @jawn: Offers of assistance are welcome. Abuse and foul language is not.

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

Re: [Django] #11263: Bug in lookup with generic relation in model inheritance

[Django]

#11263: Bug in lookup with generic relation in model inheritance
---+
  Reporter:  veena | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  generic 
relations, model inheritance
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by jawn):

 Uhh...this is a pretty big fucking bug in the ORM...  Any chance of you
 gusy looking at this??

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

Re: [Django] #12606: Stray print statement in django.contrib.auth.admin

[Django]

#12606: Stray print statement in django.contrib.auth.admin
---+
  Reporter:  seanbrant | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

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

[Django] #12606: Stray print statement in django.contrib.auth.admin

[Django]

#12606: Stray print statement in django.contrib.auth.admin
--+-
 Reporter:  seanbrant |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 I came across a stray print statement inside django.contrib.auth.admin at
 line 119 inside the user_change_password method. I attached a patch that
 removes it.

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

Re: [Django] #11761: DB error on TestCase execution

[Django]

#11761: DB error on TestCase execution
+---
  Reporter:  dmishe | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  fixed  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I suspect this is a dupe of #11936, which has been fixed in [11938].
 Please reopen if the problem still exists for you.

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

Re: [Django] #12605: ImproperlyConfigured improperly imported in Spatialite base wrapper

[Django]

#12605: ImproperlyConfigured improperly imported in Spatialite base wrapper
-+--
  Reporter:  tmcw| Owner:  jbronn
Status:  new | Milestone:
 Component:  GIS |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jbronn):

  * owner:  nobody => jbronn
  * needs_better_patch:  => 0
  * component:  Contrib apps => GIS
  * needs_tests:  => 0
  * needs_docs:  => 0

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

[Changeset] r12224 - django/trunk/docs/ref

[noreply]

Author: russellm
Date: 2010-01-13 17:54:07 -0600 (Wed, 13 Jan 2010)
New Revision: 12224

Modified:
   django/trunk/docs/ref/signals.txt
Log:
Fixed #12603 -- Corrected typo in m2m signals docs. Thanks to hvdklauw for the 
report.

Modified: django/trunk/docs/ref/signals.txt
===
--- django/trunk/docs/ref/signals.txt   2010-01-13 11:07:16 UTC (rev 12223)
+++ django/trunk/docs/ref/signals.txt   2010-01-13 23:54:07 UTC (rev 12224)
@@ -187,7 +187,7 @@
 ``sender``
 The intermediate model class describing the :class:`ManyToManyField`.
 This class is automatically created when a many-to-many field is
-defined; it you can access it using the ``through`` attribute on the
+defined; you can access it using the ``through`` attribute on the
 many-to-many field.
 
 ``instance``

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

Re: [Django] #12602: Timezone issue with Asia/Calcutta

[Django]

#12602: Timezone issue with Asia/Calcutta
+---
  Reporter:  rohitj | Owner:  nobody
 
Status:  closed | Milestone:
 
 Component:  Uncategorized  |   Version:  1.1   
 
Resolution:  invalid|  Keywords:  timezone, kolkata, 
calcutta
 Stage:  Unreviewed | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This actually isn't anything to do with Django itself. Django doesn't
 include a list of timezone names or process the naming of timezones - it
 only uses the TIME_ZONE setting to force the system environment to a
 particular time zone. The support for Asia/Kolkata (or any other timezone)
 is entirely dependent upon the support provided by your operating system.
 OS/X, for example, supports Asia/Kolkata. Other operating systems (or
 operating systems that haven't been updated since Calcutta changed it's
 name) may not support the new name.

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Changes (by mrts):

  * needs_better_patch:  0 => 1

Comment:

 Note that I haven't even thought about !ManyToManyFields, but the patch
 has to handle them as well eventually. Will deal with it later, left a
 failing test as a remainder.

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 I've added selection clearing via javascript with the red x button. The ID
 input field (and the confusing numeric ID) can be entirely hidden from
 end-users with CSS `display: none` now with no loss of functionality.

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

[Django] #12605: ImproperlyConfigured improperly imported in Spatialite base wrapper

[Django]

#12605: ImproperlyConfigured improperly imported in Spatialite base wrapper
--+-
 Reporter:  tmcw  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Contrib apps  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The Spatialite-specific code in spatialite/base.py necessitated the use of
 this exception, so imported it for the entire module, but the existing
 code had a local import, so in many cases, ImproperlyConfigured is treated
 as an undefined local variable, this producing the error message

 {{{
 django.core.exceptions.ImproperlyConfigured: Cannot determine the
 SpatiaLite version for the "mapdemo.db" database (error was "local
 variable 'ImproperlyConfigured' referenced before assignment").  Was the
 SpatiaLite initialization SQL loaded on this database?
 }}}

 This patch removes the redundant import, allowing the correct exception to
 be reported. Also the code in operations.py might want to be tighter in
 catching all exceptions as problems identifying the Spatialite version.

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

Re: [Django] #12024: error with limit_choices_to with complex queries (Q object) and raw_id_fields

[Django]

#12024: error with limit_choices_to with complex queries (Q object) and
raw_id_fields
---+
  Reporter:  anonymous | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by tubaman):

 * cc: tubaman (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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12420: "OneToOneField doesn't allow assignment of None"

[Django]

#12420: "OneToOneField doesn't allow assignment of None"
---+
  Reporter:  kbrownlees| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by tubaman):

 * cc: tubaman (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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10743: Support lookup separators in ModelAdmin.list_display

[Django]

#10743: Support lookup separators in ModelAdmin.list_display
---+
  Reporter:  mrts  | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  efficient-admin, 
list_display
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by Rilt):

  * keywords:  efficient-admin => efficient-admin, list_display
  * has_patch:  0 => 1

Comment:

 Added a patch, but would definitely like someone to look at it and
 comment. The basic jist of what I did was add an additional check for any
 strings with "__" in them, indicating a field spanning a relationship, and
 then looping through each relationship until the proper attribute was
 grabbed. Then in the admin validation, there is a recursive function which
 accurately checks that the field exists and is not a ManyToMany.

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

[Django] #12604: Typo on /en/dev/releases/1.1

[Django]

#12604: Typo on /en/dev/releases/1.1
-+--
 Reporter:  mortense |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Django Web site  | Version:  1.1   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 On page :

 "begin to remove use of this features" should be changed.

 E.g. to "begin to remove use of these features" or maybe
 "begin to remove use of this feature".

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

Re: [Django] #23: Add support for ValidationWarning

[Django]

#23: Add support for ValidationWarning
---+
  Reporter:  adrian| Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Forms |   Version:  soc2009/admin-ui
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  1   
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

  * version:  1.0-alpha-2 => soc2009/admin-ui

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

Re: [Django] #11722: Query lookups that reference an F() expression produce invalid sql

[Django]

#11722: Query lookups that reference an F() expression produce invalid sql
---+
  Reporter:  plan...@provplan.org  | Owner:  Ubercore   
 
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  F() 
expression query sql
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Comment (by Ubercore):

 Closed #12545 as a duplicate.

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

Re: [Django] #12545: contains and F() don't work well together

[Django]

#12545: contains and F() don't work well together
+---
  Reporter:  Matthew| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Ubercore):

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

Comment:

 Closing this as a duplicate of #11722.

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

Re: [Django] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
---+
  Reporter:  Ubercore  | Owner:  Ubercore   
 
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  postgresql 
cast case-insensitive
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Ubercore):

  * stage:  Ready for checkin => Accepted

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

Re: [Django] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
---+
  Reporter:  Ubercore  | Owner:  Ubercore   
 
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  postgresql 
cast case-insensitive
 Stage:  Ready for checkin | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Ubercore):

  * stage:  Unreviewed => Ready for checkin

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

Re: [Django] #11722: Query lookups that reference an F() expression produce invalid sql

[Django]

#11722: Query lookups that reference an F() expression produce invalid sql
---+
  Reporter:  plan...@provplan.org  | Owner:  Ubercore   
 
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  F() 
expression query sql
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by Ubercore):

  * stage:  Unreviewed => Accepted

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

Re: [Django] #11722: Query lookups that reference an F() expression produce invalid sql

[Django]

#11722: Query lookups that reference an F() expression produce invalid sql
---+
  Reporter:  plan...@provplan.org  | Owner:  Ubercore   
 
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  F() 
expression query sql
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by Ubercore):

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

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

Re: [Django] #12583: Postgresql backend uses implicit text casts for case insensitive operators

[Django]

#12583: Postgresql backend uses implicit text casts for case insensitive 
operators
---+
  Reporter:  Ubercore  | Owner:  Ubercore   
 
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  postgresql 
cast case-insensitive
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Ubercore):

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

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

Re: [Django] #12557: AnonymousUser has_perm should check backends has_perm

[Django]

#12557: AnonymousUser has_perm should check backends has_perm
-+--
  Reporter:  hvdklauw| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  has_perm AnonymousUser
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by hvdklauw):

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

Comment:

 Finally got the diff correct (stupid bug in svn :S)

 Anyway.. I think this will make the whole permission system even more
 powerful, it will allow backends to implement anonymous permissions.

 The documentation should reflect this change too, because custom backends
 shouldn't assume the user is a valid logged in user.

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

Re: [Django] #2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql)

[Django]

#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
---+
  Reporter:  scan...@nominum.com   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by ruckc):

 * cc: ru...@yahoo.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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12599: MultiValueDictKeyError with inline admin, when inline model's ID not displayed

[Django]

#12599: MultiValueDictKeyError with inline admin, when inline model's ID not
displayed
---+
  Reporter:  handelaar | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 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:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 If you don't what the primary key field to be displayed and editable then
 it needs to be made an `AutoField`, not an `IntegerField`.  Otherwise how
 else can it be assigned?  I think the problem here is you have models
 asking for the impossible: non-displayed, non-editable, and non-auto-
 assigned primary keys in the inlines.  I'm pretty sure simply making the
 primary key field an `AutoField` will fix the problem.  Do not manually
 exclude the field, the admin will correctly handle hiding the field from
 the user if it is defined 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Changes (by mrts):

  * needs_better_patch:  1 => 0

Comment:

 The linked label should properly update now both when objects are added
 and changed via the popup, so all the required functionality should be
 there.

 Marco and others who are interested in this, please test and report any
 problems you notice (e.g. I haven't tried in IE).

 I'll leave it into "more tests needed" state as of now -- the
 `options.py:response_change():elif request.POST.has_key("_popup")` path
 needs testing as do quirky PKs and other corner cases.


 > Another minor glitch is that I have a table with a FK on a table of
 hierarchical codes that has a "self" FK. When I open the first popup
 window and I click on the inside label for
 > the "self" FK I don't get another popup but it opens in the same window.
 I'm not sure if it's better in this way or to open a new window but to
 obtain this behaviour it's enough
 > to name the window with the id of the object.


 I'd say handling this is not worth the effort. But you are most welcome to
 tinker with the case.

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

[Django] #12603: new m2m signal documentation typo

[Django]

#12603: new m2m signal documentation typo
---+
 Reporter:  hvdklauw   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 There's a double "it", see patch for a correction

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

[Django] #12602: Timezone issue with Asia/Calcutta

[Django]

#12602: Timezone issue with Asia/Calcutta
-+--
 Reporter:  rohitj   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.1   
 Keywords:  timezone, kolkata, calcutta  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I am using Asia/Calcutta timezone. Though its been quite sometime when it
 was renamed to Asia/Kolkata . And it seems django doesn't know about
 Asia/Kolkata. Please support the new name. Thank you.

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

Re: [Django] #12282: Admin Actions: No Way to Select All

[Django]

#12282: Admin Actions: No Way to Select All
---+
  Reporter:  blinkylights  | Owner:  jezdez 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  admin actions 
change-list
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * status:  assigned => new
  * version:  1.1 => SVN
  * milestone:  => 1.2
  * owner:  blinkylights => jezdez
  * needs_docs:  0 => 1
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12601: ModelForm documentation refers to a forms field SlugField which is not documented

[Django]

#12601: ModelForm documentation refers to a forms field SlugField which is not
documented
---+
 Reporter:  gvangool   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In the documentation of !ModelForm's which
 [http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#field-types
 talks about which Model field is represented by a which Form field], it
 refers to a !SlugField ({{{ django.forms.fields.SlugField }}})

 The {{{ django.forms.fields.SlugField }}} exists, but is not listed on
 http://docs.djangoproject.com/en/dev/ref/forms/fields/.

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

Re: [Django] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
--+-
  Reporter:  Manfred Wassmann   | 
Owner:  nobody
Status:  new  | 
Milestone:
 Component:  Database layer (models, ORM) |   
Version:  SVN   
Resolution:   |  
Keywords:
 Stage:  Accepted | 
Has_patch:  1 
Needs_docs:  1|   
Needs_tests:  1 
Needs_better_patch:  1|  
--+-
Changes (by hejsan):

 * cc: hr.bjarni+dja...@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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7876: Improve template error messages to include expected end tag

[Django]

#7876: Improve template error messages to include expected end tag
+---
  Reporter:  jo...@bec.de   | Owner:  mk 
Status:  assigned   | Milestone:  1.2
 Component:  Template system|   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by mk):

  * milestone:  => 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11907: EmailField should run strip()

[Django]

#11907: EmailField should run strip()
-+--
  Reporter:  whatcould   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mk):

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

Comment:

 Duplicate of #6362

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

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by mrts):

 Marco, good point, but here come some of my notes:

  1. the added block should be within the `} else if (elem.nodeName ==
 'INPUT') {` branch,
  1. as `win.location.href` already is a string, there is no need to cast
 it,
  1. we should not `split()` as theoretically it's not impossible that the
 path already contains an add, e.g. a contrived but not illegal
 '/add/admin/add/add/` (admin is mounted under `/add/`, there's an app
 labeled `add`), so I propose the following instead: `var chosenIdHref =
 win.location.href.replace(/\/add\/[^\/]*$/, '/' + newId + '/');` (that
 gets rid of the redundant `?_popup=1` as well),
  1. it makes sense to store the escaped copy of newRepr in the beginning
 and not escape it again.

 Thanks! I've updated the patch accordingly, re-merged master and will
 upload the resulting patch shortly.

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

[Changeset] r12223 - in django/trunk: django/db/models django/db/models/fields docs/ref docs/topics tests/modeltests tests/modeltests/m2m_signals

[noreply]

Author: russellm
Date: 2010-01-13 05:07:16 -0600 (Wed, 13 Jan 2010)
New Revision: 12223

Added:
   django/trunk/tests/modeltests/m2m_signals/
   django/trunk/tests/modeltests/m2m_signals/__init__.py
   django/trunk/tests/modeltests/m2m_signals/models.py
Modified:
   django/trunk/django/db/models/fields/related.py
   django/trunk/django/db/models/signals.py
   django/trunk/docs/ref/signals.txt
   django/trunk/docs/topics/signals.txt
Log:
Fixed #5390 -- Added signals for m2m operations. Thanks to the many people 
(including, most recently, rvdrijst and frans) that have contributed to this 
patch.

Modified: django/trunk/django/db/models/fields/related.py
===
--- django/trunk/django/db/models/fields/related.py 2010-01-12 23:37:07 UTC 
(rev 1)
+++ django/trunk/django/db/models/fields/related.py 2010-01-13 11:07:16 UTC 
(rev 12223)
@@ -427,7 +427,8 @@
 through = rel.through
 class ManyRelatedManager(superclass):
 def __init__(self, model=None, core_filters=None, instance=None, 
symmetrical=None,
-join_table=None, source_field_name=None, 
target_field_name=None):
+join_table=None, source_field_name=None, 
target_field_name=None,
+reverse=False):
 super(ManyRelatedManager, self).__init__()
 self.core_filters = core_filters
 self.model = model
@@ -437,6 +438,7 @@
 self.target_field_name = target_field_name
 self.through = through
 self._pk_val = self.instance.pk
+self.reverse = reverse
 if self._pk_val is None:
 raise ValueError("%r instance needs to have a primary key 
value before a many-to-many relationship can be used." % 
instance.__class__.__name__)
 
@@ -516,14 +518,19 @@
 source_field_name: self._pk_val,
 '%s__in' % target_field_name: new_ids,
 })
-vals = set(vals)
-
+new_ids = new_ids - set(vals)
 # Add the ones that aren't there already
-for obj_id in (new_ids - vals):
+for obj_id in new_ids:
 
self.through._default_manager.using(self.instance._state.db).create(**{
 '%s_id' % source_field_name: self._pk_val,
 '%s_id' % target_field_name: obj_id,
 })
+if self.reverse or source_field_name == self.source_field_name:
+# Don't send the signal when we are inserting the
+# duplicate data row for symmetrical reverse entries.
+signals.m2m_changed.send(sender=rel.through, action='add',
+instance=self.instance, reverse=self.reverse,
+model=self.model, pk_set=new_ids)
 
 def _remove_items(self, source_field_name, target_field_name, *objs):
 # source_col_name: the PK colname in join_table for the source 
object
@@ -544,9 +551,21 @@
 source_field_name: self._pk_val,
 '%s__in' % target_field_name: old_ids
 }).delete()
+if self.reverse or source_field_name == self.source_field_name:
+# Don't send the signal when we are deleting the
+# duplicate data row for symmetrical reverse entries.
+signals.m2m_changed.send(sender=rel.through, 
action="remove",
+instance=self.instance, reverse=self.reverse,
+model=self.model, pk_set=old_ids)
 
 def _clear_items(self, source_field_name):
 # source_col_name: the PK colname in join_table for the source 
object
+if self.reverse or source_field_name == self.source_field_name:
+# Don't send the signal when we are clearing the
+# duplicate data rows for symmetrical reverse entries.
+signals.m2m_changed.send(sender=rel.through, action="clear",
+instance=self.instance, reverse=self.reverse,
+model=self.model, pk_set=None)
 
self.through._default_manager.using(self.instance._state.db).filter(**{
 source_field_name: self._pk_val
 }).delete()
@@ -579,7 +598,8 @@
 instance=instance,
 symmetrical=False,
 source_field_name=self.related.field.m2m_reverse_field_name(),
-target_field_name=self.related.field.m2m_field_name()
+target_field_name=self.related.field.m2m_field_name(),
+reverse=True
 )
 
 return manager
@@ -596,6 +616,7 @@
 manager.clear()
 manager.add(*value)
 
+
 class ReverseManyRelatedObjectsDescriptor(object):
 # This class provides the functionality that makes the related-object
 # managers available as attributes on a model class, 

Re: [Django] #12600: Comments app template_search_list inconsistency

[Django]

#12600: Comments app template_search_list inconsistency
---+
  Reporter:  hvdklauw  | Owner:  nobody  
Status:  new   | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  comments
 Stage:  Unreviewed| Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by hvdklauw):

  * has_patch:  0 => 1

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

Re: [Django] #12177: Error in part 4 of the tutorial?

[Django]

#12177: Error in part 4 of the tutorial?
+---
  Reporter:  simon_k| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by lukeplant):

 In case you didn't find your problem yet, I notice that the directory that
 contains your SVN checkout (~/source/django-trunk) does not appear in your
 tracebacks (which contain /usr/lib/pymodules/python2.6/django/...).  This
 indicates that your SVN checkout is not being used i.e. it's not at an
 appropriate place on your PYTHONPATH.  I recommend virtualenv for sorting
 this kind of thing out.

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

Re: [Django] #12600: Comments app template_search_list inconsistency

[Django]

#12600: Comments app template_search_list inconsistency
---+
  Reporter:  hvdklauw  | Owner:  nobody  
Status:  new   | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  comments
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by hvdklauw):

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

Comment:

 Seems my svn diff doesn't generate valid patches.. I'll see if I can fix
 it.

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

[Django] #12600: Comments app template_search_list inconsistency

[Django]

#12600: Comments app template_search_list inconsistency
--+-
 Reporter:  hvdklauw  |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Contrib apps  | Version:  SVN   
 Keywords:  comments  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The way templates are searched is inconsistent.
 For the templatetags the comments/%s/%s/.html style is used
 while in the views the comments/%s_%s_.html is used.

 This should be consistently comments/%s/%s/http://code.djangoproject.com/ticket/12600>
Django 
The Web framework for perfectionists with deadlines.-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #12599: MultiValueDictKeyError with inline admin, when inline model's ID not displayed

[Django]

#12599: MultiValueDictKeyError with inline admin, when inline model's ID not
displayed
--+-
 Reporter:  handelaar |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 An odd issue, which I don't have the Python-fu to debug fully.

 I have a meta-model called 'Person' (they're parliamentarians, not that
 this matters especially) to which expenses and past Ministerial Offices
 are attached through an AdminInline interface.  If I do not remove line 6
 from the admin.py file attached ("exclude = ('moffice_id',)") then I can't
 save anything on the page because a traceback like the one attached here
 results.  Yay, workaround available, but boo - exposing nasty IDs in
 editable fields where I don't want them.

 I don't know whether the fact that the model Moffice does not use the
 default ID fieldname is a factor here or not.

 Attaching a minimal admin.py and models.py and the traceback generated
 when the admin barfs.

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