[Django] #12813: Invalid documentation link.

[Django]

#12813: Invalid documentation link.
---+
 Reporter:  subhranath |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The link http://www.djangoproject.com/documentation/models/validation/
 from the page
 http://www.djangoproject.com/documentation/0.95/models/validation/ is
 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-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] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
--+-
  Reporter:  trigeek38| Owner:  anonymous   
Status:  assigned | Milestone:  1.2 
 Component:  Template system  |   Version:  SVN 
Resolution:   |  Keywords:  TemplateDoesNotExist
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  1|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by jkatzer):

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

Comment:

 scrapped the old patch

 the new patch(es) overload the previous TemplateDoesNotExist execption, to
 add wether or not that error should be thrown out. it is worded as to
 wether or not a super function calling it "should_keep_trying"

 in regards to this, any place that previously raised an
 TemplateDoesNotExist error needs to be rewritten to have an extra arg...
 this also is the case in the testing file, which has been modified
 accordingly...

 please excuse my code as i am not fully familiar with python and the
 coding conventions used by the django community.

-- 
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] #12812: Inheriting from comments breaks comment moderation

[Django]

#12812: Inheriting from comments breaks comment moderation
--+-
  Reporter:  Beetle_B | Owner:  nobody  
   
Status:  closed   | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  1.1 
   
Resolution:  invalid  |  Keywords:  comments 
inheritance moderation
 Stage:  Unreviewed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by kmtracey):

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

Comment:

 This page:
 http://docs.djangoproject.com/en/dev/ref/contrib/comments/custom/

 appears to document the correct way to get your own model returned by that
 `comments.get_model()` call.

-- 
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] #11875: ForeignKey field with blank=True and null=True in list_display breaks admin

[Django]

#11875: ForeignKey field with blank=True and null=True in list_display breaks 
admin
---+
  Reporter:  skorpan   | Owner:  djansoft   
   
Status:  closed| Milestone:  1.2
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:  worksforme|  Keywords:  foreignkey admin 
list_editable
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Possibly contributing to the recreation difficulty is that there is no
 description of what to do in the admin interface to trigger the error. It
 may seem obvious, but making it explicit (for example: Bring up the change
 list page for Bicycles after adding a Bicycle with no specified Brand)
 really helps. Also, the full traceback of the error would be helpful, not
 just the error message.

-- 
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] #11675: [patch] Support new memcached wrapper pylibmc

[Django]

#11675: [patch] Support new memcached wrapper pylibmc
--+-
  Reporter:  pipp...@yahoo.co.jp  | Owner:  otherjacob  
  
Status:  assigned | Milestone:  1.2 
  
 Component:  Cache system |   Version:  SVN 
  
Resolution:   |  Keywords:  cache pylibmc 
memcached.py
 Stage:  Accepted | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Comment (by jammons):

 So rather than add other fallback we were thinking that one could specify
 the preferred memcached backend as follows:
 CACHE_BACKEND = memcached://server:port?lib=memcache

 Where memcache could be cmemcache, memcache, or some other python module.
 If an engine is not specified, it will default to the current behavior of
 cmemcache then memcache fallback.

-- 
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] #12808: errorCSRF() got an unexpected keyword argument 'reason'.

[Django]

#12808: errorCSRF() got an unexpected keyword argument 'reason'.
+---
  Reporter:  coryjacobsen   | Owner:  nobody  
Status:  closed | Milestone:  1.2 
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  invalid|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by coryjacobsen):

 Replying to [comment:1 lukeplant]:
 > There is no `errorCSRF` function in Django.  This sounds like an error
 with your own CSRF_FAILURE_VIEW.
 You are absolutely correct.  Sorry to jump the gun like that, and thanks
 for checking it 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] #12239: Float is rounded to integer on queries on integer field

[Django]

#12239: Float is rounded to integer on queries on integer field
-+--
  Reporter:  waverider   | Owner:  nobody   
   
Status:  new | Milestone:  1.2  
   
 Component:  Core framework  |   Version:  1.1  
   
Resolution:  |  Keywords:  __gte, __lte, query 
rounding
 Stage:  Accepted| Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by aroy):

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

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

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

Re: [Django] #12812: Inheriting from comments breaks comment moderation

[Django]

#12812: Inheriting from comments breaks comment moderation
--+-
  Reporter:  Beetle_B | Owner:  nobody  
   
Status:  new  | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  1.1 
   
Resolution:   |  Keywords:  comments 
inheritance moderation
 Stage:  Unreviewed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by Beetle_B):

 * cc: mu...@nawaz.org (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] #12771: Humanize with natural time

[Django]

#12771: Humanize with natural time
--+-
  Reporter:  phinpho  | Owner:  anonymous
Status:  assigned | Milestone:  1.2  
 Component:  Template system  |   Version:  1.1  
Resolution:   |  Keywords:   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  1|   Needs_tests:  1
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

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

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

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

[Django] #12812: Inheriting from comments breaks comment moderation

[Django]

#12812: Inheriting from comments breaks comment moderation
-+--
 Reporter:  Beetle_B |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.comments  | Version:  1.1   
 Keywords:  comments inheritance moderation  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I created a new kind of comment called TreeComment which (ultimately)
 subclasses Comment (in contrib.comments)

 Essentially, I have a TreeCommentBase which subclasses Comment and is an
 abstract class. Then TreeComment subclasses TreeCommentBase. This is all
 in a custom app called treecomments.

 Now in the moderation code, we have:

 {{{
 signals.comment_will_be_posted.connect(self.pre_save_moderation,
 sender=comments.get_model())
 signals.comment_was_posted.connect(self.post_save_moderation,
 sender=comments.get_model())
 }}}

 which relies on get_model() which is defined in the __init__.py file in
 comments. This causes a wrong model to be sent (my model is TreeComment,
 not Comment).

 If I replace it with treecomments.get_model() (and create that function
 under __init__.py - I needed it for something else anyway), then it all
 works.

 Am I doing something wrong? Is there a more proper way of subclassing? For
 now I'll just subclass Moderator and customize to fix 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] #12239: Float is rounded to integer on queries on integer field

[Django]

#12239: Float is rounded to integer on queries on integer field
-+--
  Reporter:  waverider   | Owner:  aroy 
   
Status:  assigned| Milestone:  1.2  
   
 Component:  Core framework  |   Version:  1.1  
   
Resolution:  |  Keywords:  __gte, __lte, query 
rounding
 Stage:  Accepted| Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by aroy):

  * has_patch:  0 => 1

Comment:

 The bug is only for gte queries; lte already worked as expected.  I've
 attached a patch that fixes 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] #11875: ForeignKey field with blank=True and null=True in list_display breaks admin

[Django]

#11875: ForeignKey field with blank=True and null=True in list_display breaks 
admin
---+
  Reporter:  skorpan   | Owner:  djansoft   
   
Status:  closed| Milestone:  1.2
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:  worksforme|  Keywords:  foreignkey admin 
list_editable
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by djansoft):

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

Comment:

 I can't reproduce this error and I tried in sqlite and in PostgreSQL.  It
 just works as expected.  To reopen the bug please give information about
 the DBMS used.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12811: Tutorial suggestion at the end of lesson 2 is inappropriate

[Django]

#12811: Tutorial suggestion at the end of lesson 2 is inappropriate
---+
 Reporter:  bac|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 At the very end of lesson two there is this suggestion:

 "Edit the file, and you'll see it uses a template variable called
 app_list. That variable contains every installed Django app. Instead of
 using that, you can hard-code links to object-specific admin pages in
 whatever way you think is best."

 At this point in the tutorial there has been no discussion of the template
 formatting language and it is unclear how one would go about completing
 the suggested task if he or she wanted to limit the apps to non-admin
 apps, for example.  The means of 'hard coding' the links has not yet been
 addressed.  Given that I think it is silly to even have this section in
 the tutorial.

-- 
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] #12072: Literal strings containing [, =] break {% url %}.

[Django]

#12072: Literal strings containing [,=] break {% url %}.
--+-
  Reporter:  emulbreh | Owner:  eculver
Status:  assigned | Milestone:  1.2
 Component:  Template system  |   Version:  1.1
Resolution:   |  Keywords:  url tag
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by eculver):

  * owner:  nobody => eculver
  * 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] #12712: syncdb doesn't create tables for m2m through-less fields that are added on the model after the class_prepared signal

[Django]

#12712: syncdb doesn't create tables for m2m through-less fields that are added 
on
the model after the class_prepared signal
---+
  Reporter:  IonelMaries   | Owner:  nobody   
Status:  new   | Milestone:  1.2  
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Unreviewed| Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by IonelMaries):

 Forgot to note this:

 The fact that the m2m field is added in the model after the class_prepared
 signal changes the order in the tables list (tables =
 connection.introspection.table_names()). So in my scenario the m2m table
 appears after the table of the model containing the m2m filed.

 In a normal scenario the m2m table appears before the table of the model
 containing the m2m field.

-- 
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] #12808: errorCSRF() got an unexpected keyword argument 'reason'.

[Django]

#12808: errorCSRF() got an unexpected keyword argument 'reason'.
+---
  Reporter:  coryjacobsen   | Owner:  nobody  
Status:  closed | Milestone:  1.2 
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  invalid|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by lukeplant):

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

Comment:

 There is no `errorCSRF` function in Django.  This sounds like an error
 with your own CSRF_FAILURE_VIEW.

-- 
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] #12810: ManyToManyField.db_table

[Django]

#12810: ManyToManyField.db_table
+---
  Reporter:  strelnikovdmitrij  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords:  ManyToManyField
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Old description:

> Originally from documentation.
> ManyToManyField.db_table
> The name of the table to create for storing the many-to-many data. If
> this is not provided, Django will assume a default name based upon the
> names of the two tables being joined.
>
> It is a little bit unclear, cause if db_table is not provided, Django
> will create table with name based on the name of the model (table that
> has the ManyToManyField), and field name that contain this
> ManyToManyField.
>
> class Product(models.Model):
>  color = models.ManyToManyField('ProductColor', null=True, blank=True)
>  class Meta:
>   db_table = 'eshop_product'
>
> class ProductColor(models.Model):
>  name = ...
>  class Meta:
>   db_table = 'eshop_product_color'
>
> running syncdb
> after the creation of 'eshop_product' table Django will create
> 'eshop_product_color' table that holds relation between Product and
> ProductColor. The table for ProductColor will never create.

New description:

 Originally from documentation.
 ManyToManyField.db_table
 The name of the table to create for storing the many-to-many data. If this
 is not provided, Django will assume a default name based upon the names of
 the two tables being joined.

 It is a little bit unclear, cause if db_table is not provided, Django will
 create table with name based on the name of the model (table that has the
 ManyToManyField), and field name that contain this ManyToManyField.
 {{{
 class Product(models.Model):
  color = models.ManyToManyField('ProductColor', null=True, blank=True)
  class Meta:
   db_table = 'eshop_product'

 class ProductColor(models.Model):
  name = ...
  class Meta:
   db_table = 'eshop_product_color'
 }}}
 running syncdb
 after the creation of 'eshop_product' table Django will create
 'eshop_product_color' table that holds relation between Product and
 ProductColor. The table for ProductColor will never create.

Comment:

 Reformatted, please use preview.

-- 
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] #12810: ManyToManyField.db_table

[Django]

#12810: ManyToManyField.db_table
---+
 Reporter:  strelnikovdmitrij  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords:  ManyToManyField|   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Originally from documentation.
 ManyToManyField.db_table
 The name of the table to create for storing the many-to-many data. If this
 is not provided, Django will assume a default name based upon the names of
 the two tables being joined.

 It is a little bit unclear, cause if db_table is not provided, Django will
 create table with name based on the name of the model (table that has the
 ManyToManyField), and field name that contain this ManyToManyField.

 class Product(models.Model):
  color = models.ManyToManyField('ProductColor', null=True, blank=True)
  class Meta:
   db_table = 'eshop_product'

 class ProductColor(models.Model):
  name = ...
  class Meta:
   db_table = 'eshop_product_color'

 running syncdb
 after the creation of 'eshop_product' table Django will create
 'eshop_product_color' table that holds relation between Product and
 ProductColor. The table for ProductColor will never create.

-- 
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] #11875: ForeignKey field with blank=True and null=True in list_display breaks admin

[Django]

#11875: ForeignKey field with blank=True and null=True in list_display breaks 
admin
---+
  Reporter:  skorpan   | Owner:  djansoft   
   
Status:  new   | Milestone:  1.2
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  foreignkey admin 
list_editable
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by djansoft):

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

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

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

Re: [Django] #11875: ForeignKey field with blank=True and null=True in list_display breaks admin

[Django]

#11875: ForeignKey field with blank=True and null=True in list_display breaks 
admin
---+
  Reporter:  skorpan   | Owner:  anonymous  
   
Status:  assigned  | Milestone:  1.2
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  foreignkey admin 
list_editable
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

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

Re: [Django] #12791: Setting encoding on EmailMessage does not produce intended result

[Django]

#12791: Setting encoding on EmailMessage does not produce intended result
---+
  Reporter:  oyvind| Owner:  oyvind 
   
Status:  closed| Milestone:  1.2
   
 Component:  django.core.mail  |   Version:  SVN
   
Resolution:  duplicate |  Keywords:  iso-8859-1 utf-8 
smart_str mail header
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by oyvind):

  * 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] #12749: "Please correct the error below." when saving add model form with inline formset and no auto primary key.

[Django]

#12749: "Please correct the error below." when saving add model form with inline
formset and no auto primary key.
-+--
  Reporter:  chris.wessel...@cwi.nl  | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jezdez):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 0
  * 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.

[Changeset] r12398 - django/trunk/django/contrib/admin/templates/admin

[noreply]

Author: jezdez
Date: 2010-02-07 09:55:40 -0600 (Sun, 07 Feb 2010)
New Revision: 12398

Modified:
   django/trunk/django/contrib/admin/templates/admin/change_list.html
Log:
Fixed #12716 - Typo in the admin change list template. Thanks, kbrownlees.

Modified: django/trunk/django/contrib/admin/templates/admin/change_list.html
===
--- django/trunk/django/contrib/admin/templates/admin/change_list.html  
2010-02-07 14:42:16 UTC (rev 12397)
+++ django/trunk/django/contrib/admin/templates/admin/change_list.html  
2010-02-07 15:55:40 UTC (rev 12398)
@@ -67,7 +67,7 @@
 
 {% blocktrans count cl.formset.errors|length as counter %}Please 
correct the error below.{% plural %}Please correct the errors below.{% 
endblocktrans %}
 
-{% for error in cl.formset.non_field_errors 
%}{{ error }}{% endfor %}
+{% for error in cl.formset.non_form_errors 
%}{{ error }}{% endfor %}
 {% endif %}
 
   {% block search %}{% search_form cl %}{% endblock %}

-- 
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] r12397 - django/trunk/django/contrib/admin/media/js

[noreply]

Author: jezdez
Date: 2010-02-07 08:42:16 -0600 (Sun, 07 Feb 2010)
New Revision: 12397

Modified:
   django/trunk/django/contrib/admin/media/js/core.js
Log:
Fixed #12748 - Use charAt instead of array-like access to format string to 
please IE. Thanks, yedpodtrzitko.

Modified: django/trunk/django/contrib/admin/media/js/core.js
===
--- django/trunk/django/contrib/admin/media/js/core.js  2010-02-07 14:41:43 UTC 
(rev 12396)
+++ django/trunk/django/contrib/admin/media/js/core.js  2010-02-07 14:42:16 UTC 
(rev 12397)
@@ -174,12 +174,12 @@
 };
 var result = '', i = 0;
 while (i < format.length) {
-if (format[i] === '%') {
-result = result + fields[format[i + 1]];
+if (format.charAt(i) === '%') {
+result = result + fields[format.charAt(i + 1)];
 ++i;
 }
 else {
-result = result + format[i];
+result = result + format.charAt(i);
 }
 ++i;
 }

-- 
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] r12396 - django/trunk/django/contrib/admin/templates/admin

[noreply]

Author: jezdez
Date: 2010-02-07 08:41:43 -0600 (Sun, 07 Feb 2010)
New Revision: 12396

Modified:
   django/trunk/django/contrib/admin/templates/admin/change_list.html
Log:
Fixed #12793 - Only use the admin actions JavaScript if not explicitly 
deactivated with 'actions = None' in the ModelAdmin. Thanks, Florian Apolloner.

Modified: django/trunk/django/contrib/admin/templates/admin/change_list.html
===
--- django/trunk/django/contrib/admin/templates/admin/change_list.html  
2010-02-06 20:48:55 UTC (rev 12395)
+++ django/trunk/django/contrib/admin/templates/admin/change_list.html  
2010-02-07 14:41:43 UTC (rev 12396)
@@ -19,6 +19,7 @@
 
 {% block extrahead %}
 {{ block.super }}
+{% if action_form %}{% if actions_on_top or actions_on_bottom %}
 
 (function($) {
 $(document).ready(function($) {
@@ -26,6 +27,7 @@
 });
 })(jQuery.noConflict());
 
+{% endif %}{% endif %}
 {% endblock %}
 
 {% block bodyclass %}change-list{% endblock %}

-- 
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] #12809: Add returning of parameters for get_from_clause()

[Django]

#12809: Add returning of parameters for get_from_clause()
--+-
 Reporter:  Kronuz|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:
 Keywords:  dynamic queries, from |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Could it be possible to make the get_from_clause() in
 django.db.models.sql.compiler return params? It'd be useful in some cases
 to be able to "insert" parameters to the FROM (such as when you need to
 add an ON clause or other "extended" things)
 For an example of this, you can check the "Simple Backend" for the django-
 fts (at google code), in where I need to "patch" the structures directly
 to achieve what I wanted (or perhaps there's a better way?)... it's right
 there in fts.backends.simple, in the _search() method... where I add extra
 joined tables to do the search (just after the tables already in the
 queryset). I'd appreciate any comments. :)

-- 
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] #12515: confusing wording - formset Extra parameter

[Django]

#12515: confusing wording - formset Extra parameter
+---
  Reporter:  smalldocerror  | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Documentation  |   Version:  1.1 
Resolution:  duplicate  |  Keywords:  formset extra= param
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

Comment:

 #12505 describes the confusion in a slightly different way.

-- 
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] #12505: Formsets: Misleading documentation

[Django]

#12505: Formsets: Misleading documentation
+---
  Reporter:  Andreas| Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.1
Resolution: |  Keywords:  formset
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

Comment:

 I believe the extra parameter describes how many blank forms to show.
 #12515 describes the confusion in a slightly different way.

-- 
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] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
+---
  Reporter:  petrilli   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by timo):

 The attached diagram is out of date, since MessageMiddleware is now
 included by startproject (#12795). We may want to consider an approach
 that doesn't require the image to be updated each time this list is
 changed.

-- 
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] #12795: MessageMiddleware missing from default MIDDLEWARE_CLASSES value described in middlewared overview

[Django]

#12795: MessageMiddleware missing from default MIDDLEWARE_CLASSES value 
described
in middlewared overview
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * 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.

Re: [Django] #12526: middleware application order image missing

[Django]

#12526: middleware application order image missing
-+--
  Reporter:  j...@pocketvillage.com  | Owner:  nobody 
Status:  closed  | Milestone: 
 Component:  Documentation   |   Version:  1.1
Resolution:  invalid |  Keywords:  resolve
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by timo):

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

Comment:

 The url in the description has a double // between dev and topics which
 looks to be the cause of this (since the image src uses a relative path).
 If you fix this in the url the image works fine.

-- 
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] #12805: Raw method docs are misleading

[Django]

#12805: Raw method docs are misleading
+---
  Reporter:  vbabiy | Owner:  nobody  
Status:  closed | Milestone:  1.2 
 Component:  Documentation  |   Version:  1.2-beta
Resolution:  duplicate  |  Keywords:  
 Stage:  Unreviewed | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

Comment:

 duplicate of #12519

-- 
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] #12804: decorating admin views doesn't work

[Django]

#12804: decorating admin views doesn't work
+---
  Reporter:  apollo13   | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Uncategorized  |   Version:  SVN   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by apollo13):

 Yes, I am aware that super works and what the problem is, but it's imo
 still a bug or at least should get documented as it's nothing you'd
 expect. Aside from that it's a backwards incompatible change since CSRF
 protection got merged!

-- 
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.