date:20110227

Re: [Django] #14496: Conflict between ModelForm.Meta.exclude and ModelAdmin.readonly attributes

2011-02-27 Thread Django

#14496: Conflict between ModelForm.Meta.exclude and ModelAdmin.readonly 
attributes
+---
   Reporter:  msgre_valise  | Owner:  nobody
   
 Status:  new   | Milestone:
   
  Component:  django.contrib.admin  |   Version:  1.2   
   
 Resolution:|  Keywords:  ModelForm 
ModelAdmin readonly_fields exclude conflict
   Triage Stage:  Accepted  | Has patch:  0 
   
Needs documentation:  0 |   Needs tests:  0 
   
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Contrib apps => django.contrib.admin


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

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

Re: [Django] #11195: add fieldname to admin changelist tags -- eases CSS customization

2011-02-27 Thread Django

#11195: add fieldname to admin changelist  tags -- eases CSS customization
--+-
   Reporter:  akaihola| Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.admin|   Version:  SVN   
 Resolution:  |  Keywords:  css   
   Triage Stage:  Design decision needed  | Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-

Comment (by julien):

 #14291 is a dupe.

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

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

Re: [Django] #14291: In django admin results list, provide the field name as a css class on the table cell

2011-02-27 Thread Django

#14291: In django admin results list, provide the field name as a css class on 
the
table cell
+---
   Reporter:  vjimw | Owner:  nobody   
 Status:  closed| Milestone:   
  Component:  Contrib apps  |   Version:  1.2  
 Resolution:  duplicate |  Keywords:  admin css class field
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 Dupe of #11195.

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

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

Re: [Django] #14639: admin.site.register() does not check if the model is abstract (gives weird error)

2011-02-27 Thread Django

#14639: admin.site.register() does not check if the model is abstract (gives 
weird
error)
+---
   Reporter:  vdboor| Owner:  nobody
 Status:  closed| Milestone:
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:  fixed |  Keywords:  error-messages
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 This was fixed in [15636].

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

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

Re: [Django] #14131: The pagination module should have some limit, or a warning should be given in the documentation

2011-02-27 Thread Django

#14131: The pagination module should have some limit, or a warning should be 
given
in the documentation
--+-
   Reporter:  mlissner| Owner:  nobody
 Status:  new | Milestone:
  Component:  Core framework  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by julien):

  * component:  Contrib apps => Core framework


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

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

Re: [Django] #13729: UK localflavor mis-named/documentation bug.

2011-02-27 Thread Django

#13729: UK localflavor mis-named/documentation bug.
--+-
   Reporter:  schinckel   | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.localflavor  |   Version:  1.2   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by julien):

  * component:  Contrib apps => django.contrib.localflavor


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

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

Re: [Django] #13344: Name collision for "next" template variable between contrib.comments and views.generic.list_detail

2011-02-27 Thread Django

#13344: Name collision for "next" template variable between contrib.comments and
views.generic.list_detail
---+
   Reporter:  erik | Owner:  nobody  
 Status:  new  | Milestone:  
  Component:  django.contrib.comments  |   Version:  1.2-beta
 Resolution:   |  Keywords:  
   Triage Stage:  Design decision needed   | Has patch:  0   
Needs documentation:  0|   Needs tests:  0   
Patch needs improvement:  0|  
---+
Changes (by julien):

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

Re: [Django] #14105: django.contrib.auth tests failing with cache middleware

2011-02-27 Thread Django

#14105: django.contrib.auth tests failing with cache middleware
+---
   Reporter:  baumer1122| Owner:  PaulM
 Status:  assigned  | Milestone:   
  Component:  Cache system  |   Version:  1.2  
 Resolution:|  Keywords:   
   Triage Stage:  Accepted  | Has patch:  0
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Contrib apps => Cache system


Comment:

 This is primarily a cache-related issue.

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

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

Re: [Django] #14408: Admin Error when subclassing ContentType for generic Relations

2011-02-27 Thread Django

#14408: Admin Error when subclassing ContentType for generic Relations
+---
   Reporter:  MS| Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Contrib apps => django.contrib.admin


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

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

Re: [Django] #14434: AdminSite should check self.has_permission in self.login

2011-02-27 Thread Django

#14434: AdminSite should check self.has_permission in self.login
+---
   Reporter:  bkonkle   | Owner:  nobody 
 Status:  new   | Milestone: 
  Component:  django.contrib.admin  |   Version:  1.2
 Resolution:|  Keywords:  admin views
   Triage Stage:  Accepted  | Has patch:  1  
Needs documentation:  0 |   Needs tests:  0  
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Contrib apps => django.contrib.admin


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

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

Re: [Django] #12982: Add get_or_set method to cache API

2011-02-27 Thread Django

#12982: Add get_or_set method to cache API
+---
   Reporter:  Alex  | Owner:  jmeed
 Status:  assigned  | Milestone:  1.4  
  Component:  Cache system  |   Version:  SVN  
 Resolution:|  Keywords:  cache
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Core framework => Cache system


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

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

Re: [Django] #11788: cache_page decorator doesn't work with HttpResponses whose content is an iterator

2011-02-27 Thread Django

#11788: cache_page decorator doesn't work with HttpResponses whose content is an
iterator
-+--
   Reporter:  RaceCondition  | Owner:  nobody
 Status:  reopened   | Milestone:
  Component:  Cache system   |   Version:  1.1   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by julien):

  * component:  Core framework => Cache system


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

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

Re: [Django] #14334: Queries don't ensure that comparison objects are the correct type

2011-02-27 Thread Django

#14334: Queries don't ensure that comparison objects are the correct type
+---
   Reporter:  rpbarlow  | Owner: 
 Status:  new   | Milestone: 
  Component:  Database layer (models, ORM)  |   Version:  1.2
 Resolution:|  Keywords: 
   Triage Stage:  Accepted  | Has patch:  1  
Needs documentation:  1 |   Needs tests:  0  
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #14675: Update docs and project template to avoid "import *" for url patterns

2011-02-27 Thread Django

#14675: Update docs and project template to avoid "import *" for url patterns
--+-
   Reporter:  robhudson   | Owner:  nobody
 Status:  new | Milestone:  1.4   
  Component:  Core framework  |   Version:  1.2   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by julien):

  * milestone:  1.3 => 1.4


Comment:

 Changing the milestone as per Carl's comment above.

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

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

Re: [Django] #1891: 'distinct':True no longer usable in limit_choices_to

2011-02-27 Thread Django

#1891: 'distinct':True no longer usable in limit_choices_to
+---
   Reporter:  mattimustang@…| Owner:  nobody
 Status:  reopened  | Milestone:
  Component:  Database layer (models, ORM)  |   Version:
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  1 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #5619: FileField and ImageField return the wrong path/url before calling save_FOO_file()

2011-02-27 Thread Django

#5619: FileField and ImageField return the wrong path/url before calling
save_FOO_file()
+---
   Reporter:  wreese@…  | Owner:  
leahculver
 Status:  reopened  | Milestone:

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

 Resolution:|  Keywords:

   Triage Stage:  Someday/Maybe | Has patch:  1 

Needs documentation:  0 |   Needs tests:  1 

Patch needs improvement:  1 |  
+---
Changes (by julien):

  * needs_better_patch:  0 => 1
  * component:  Core framework => Database layer (models, ORM)


Comment:

 3 years later, I'm not sure how relevant this is still. At the very least
 the patch needs to be updated to use unittests.

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

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

Re: [Django] #6282: Clarify comment for MEDIA_URL in settings.py

2011-02-27 Thread Django

#6282: Clarify comment for MEDIA_URL in settings.py
--+-
   Reporter:  apollo13| Owner:  nobody  
  
 Status:  closed  | Milestone:  
  
  Component:  Core framework  |   Version:  SVN 
  
 Resolution:  fixed   |  Keywords:  settings 
MEDIA_URL
   Triage Stage:  Design decision needed  | Has patch:  0   
  
Needs documentation:  0   |   Needs tests:  0   
  
Patch needs improvement:  0   |  
--+-
Changes (by julien):

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


Comment:

 Well, it seems like this has been fixed at some stage. The comment is now
 pretty clear:
 
http://code.djangoproject.com/browser/django/trunk/django/conf/project_template/settings.py?rev=15501#L50

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

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

Re: [Django] #6860: Improvements for the new paginator

2011-02-27 Thread Django

#6860: Improvements for the new paginator
--+-
   Reporter:  Alberto García Hierro   | 
Owner:  nobody   
 Status:  new | 
Milestone:   
  Component:  Core framework  |   
Version:  SVN  
 Resolution:  |  
Keywords:  paginator
   Triage Stage:  Design decision needed  | Has 
patch:  1
Needs documentation:  1   |   Needs 
tests:  1
Patch needs improvement:  1   |  
--+-
Changes (by julien):

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


Comment:

 This seems useful but the patch is old and needs to be updated. Also needs
 tests.

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

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

Re: [Django] #6870: pre_delete should be sent before collecting ForeignKey relationships

2011-02-27 Thread Django

#6870: pre_delete should be sent before collecting ForeignKey relationships
+---
   Reporter:  wkornewald| Owner:  
nobody
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  
pre_delete signals related
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  1 |   Needs tests:  0 

Patch needs improvement:  1 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


Comment:

 See a possibly related feature request in #13251.

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

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

Re: [Django] #13251: Add ability to know where an object was deleted from to pre/post delete signals

2011-02-27 Thread Django

#13251: Add ability to know where an object was deleted from to pre/post delete
signals
+---
   Reporter:  skoom | Owner:  
nobody 
 Status:  new   | Milestone:
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:  
signals
   Triage Stage:  Accepted  | Has patch:  1 
 
Needs documentation:  1 |   Needs tests:  1 
 
Patch needs improvement:  0 |  
+---

Comment (by julien):

 See a possibly related issue in #6870.

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

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

Re: [Django] #7623: Multi-table inheritance does not allow linking new instance of child model to existing parent model instance.

2011-02-27 Thread Django

#7623: Multi-table inheritance does not allow linking new instance of child 
model
to existing parent model instance.
+---
   Reporter:  brooks.travis@…   | Owner:  
nobody
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  
model-inheritance, multi-table-inheritance
   Triage Stage:  Design decision needed| Has patch:  1 

Needs documentation:  1 |   Needs tests:  1 

Patch needs improvement:  1 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #7689: add 'symmetrical' argument to OneToOneField('self')

2011-02-27 Thread Django

#7689: add 'symmetrical' argument to OneToOneField('self')
+---
   Reporter:  aldo.deluca@… | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Design decision needed| Has patch:  0 
Needs documentation:  1 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #8291: "pk" alias doesn't work for Meta option "ordering"

2011-02-27 Thread Django

#8291: "pk" alias doesn't work for Meta option "ordering"
+---
   Reporter:  peterd12  | Owner:  
nobody
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  Meta 
ordering pk alias
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #8618: Many-to-many intermediary tables can't have multiple foreign keys to source/target models

2011-02-27 Thread Django

#8618: Many-to-many intermediary tables can't have multiple foreign keys to
source/target models
+---
   Reporter:  coda  | Owner:  
nobody 
 Status:  new   | Milestone:
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:  m2m 
intermediary validation
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #9195: Paginator.page() should raise PageNotAnInteger when given a NoneType value

2011-02-27 Thread Django

#9195: Paginator.page() should raise PageNotAnInteger when given a NoneType 
value
--+-
   Reporter:  thomas@…| Owner:  nobody
 Status:  new | Milestone:
  Component:  Documentation   |   Version:  1.0   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by julien):

  * component:  Core framework => Documentation


Comment:

 I agree with Karen and therefore change the component of this ticket to
 address this case in the documentation.

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

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

Re: [Django] #15516: Update the ticket life cycle diagram (was: Update the ticket life cyvle diagram)

2011-02-27 Thread Django

#15516: Update the ticket life cycle diagram
-+--
   Reporter:  ramiro | Owner:  nobody
 Status:  new| Milestone:
  Component:  Documentation  |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

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

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

Re: [Django] #15516: Update the ticket life cyvle diagram

2011-02-27 Thread Django

#15516: Update the ticket life cyvle diagram
-+--
   Reporter:  ramiro | Owner:  nobody
 Status:  new| Milestone:
  Component:  Documentation  |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by gabrielhurley):

  * stage:  Unreviewed => Accepted


Comment:

 As far as I can tell Jacob added that image in [4346]... quite a long time
 ago. At this point if the original isn't available we may need to just re-
 create it.

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

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

Re: [Django] #10657: Meta option 'ordering' causes problems with nullable fields

2011-02-27 Thread Django

#10657: Meta option 'ordering' causes problems with nullable fields
+---
   Reporter:  andrewl   | Owner:  
nobody
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  
ordering, order_by
   Triage Stage:  Design decision needed| Has patch:  0 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by julien):

  * component:  Core framework => Database layer (models, ORM)


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

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

Re: [Django] #13840: 404 error reported via e-mail even when DEBUG is True

2011-02-27 Thread Django

#13840: 404 error reported via e-mail even when DEBUG is True
--+-
   Reporter:  master  | Owner:  nobody  
 Status:  closed  | Milestone:  
  Component:  Core framework  |   Version:  SVN 
 Resolution:  fixed   |  Keywords:  404, broken link
   Triage Stage:  Accepted| Has patch:  1   
Needs documentation:  0   |   Needs tests:  0   
Patch needs improvement:  0   |  
--+-
Changes (by julien):

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


Comment:

 This has been reported again in #15187 and has been fixed.

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

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

Re: [Django] #11212: Don't encode emails with base64/qp

2011-02-27 Thread Django

#11212: Don't encode emails with base64/qp
+---
   Reporter:  phr   | Owner:  nobody   
 Status:  new   | Milestone:  1.3  
  Component:  django.core.mail  |   Version:  SVN  
 Resolution:|  Keywords:  send_mail
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by ramiro):

  * needs_better_patch:  1 => 0


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

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

[Django] #15516: Update the ticket life cyvle diagram

2011-02-27 Thread Django

#15516: Update the ticket life cyvle diagram
-+--
   Reporter:  ramiro | Owner:  nobody
 Status:  new| Milestone:
  Component:  Documentation  |   Version:  SVN   
   Keywords: |  Triage Stage:  Unreviewed
  Has patch:  0  |   Needs documentation:  0 
Needs tests:  0  |   Patch needs improvement:  0 
-+--
 Now that r15665 has happened, we will also want to update the workflow
 [http://docs.djangoproject.com/en/dev/_images/djangotickets.png diagram]
 in the [http://docs.djangoproject.com/en/dev/internals/contributing
 /#ticket-triage Ticket triage section]. We would need help from someone
 with accesss to the right platform/tool (OS X/Omni Graffle?) and the
 source file.

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

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

Re: [Django] #15512: Admin imports cleanup

2011-02-27 Thread Django

#15512: Admin imports cleanup
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


Comment:

 Personal preference is to use braces, rather than backslash line
 continuations; however, that's easy to pick up on commit, so marking RFC

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

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

Re: [Django] #15511: MultiValueField should allow subfield requirement

2011-02-27 Thread Django

#15511: MultiValueField should allow subfield requirement
+---
   Reporter:  jdunck| Owner:  nobody
 Status:  new   | Milestone:
  Component:  Forms |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted


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

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

Re: [Django] #15515: Django should support customizable project/app templates

2011-02-27 Thread Django

#15515: Django should support customizable project/app templates
--+-
   Reporter:  Joshua "jag" Ginsberg| 
Owner:  nobody
 Status:  closed  | 
Milestone:
  Component:  Core framework  |   
Version:  1.2   
 Resolution:  duplicate   |  
Keywords:
   Triage Stage:  Unreviewed  | Has 
patch:  1 
Needs documentation:  0   |   Needs 
tests:  0 
Patch needs improvement:  0   |  
--+-

Comment (by russellm):

 #15095 is also worth mentioning as a prior ticket -- especially since it
 isn't closed.

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

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

Re: [Django] #15514: Django 1.2 tutorial03 error template clarification

2011-02-27 Thread Django

#15514: Django 1.2 tutorial03 error template clarification
-+--
   Reporter:  cubex  | Owner:  nobody   
   
 Status:  closed | Milestone:   
   
  Component:  Documentation  |   Version:  1.2  
   
 Resolution:  wontfix|  Keywords:  404 template error 
debug
   Triage Stage:  Unreviewed | Has patch:  0
   
Needs documentation:  0  |   Needs tests:  0
   
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


Comment:

 This text is already there: "If you don't define your own 404 view -- and
 simply use the default, which is recommended -- you still have one
 obligation: To create a 404.html template in the root of your template
 directory"

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

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

Re: [Django] #15515: Django should support customizable project/app templates

2011-02-27 Thread Django

#15515: Django should support customizable project/app templates
--+-
   Reporter:  Joshua "jag" Ginsberg| 
Owner:  nobody
 Status:  closed  | 
Milestone:
  Component:  Core framework  |   
Version:  1.2   
 Resolution:  duplicate   |  
Keywords:
   Triage Stage:  Unreviewed  | Has 
patch:  1 
Needs documentation:  0   |   Needs 
tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

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


Comment:

 Duplicate of #3999.

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

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

Re: [Django] #15515: Django should support customizable project/app templates

2011-02-27 Thread Django

#15515: Django should support customizable project/app templates
--+-
   Reporter:  Joshua "jag" Ginsberg| 
Owner:  nobody
 Status:  new | 
Milestone:
  Component:  Core framework  |   
Version:  1.2   
 Resolution:  |  
Keywords:
   Triage Stage:  Unreviewed  | Has 
patch:  1 
Needs documentation:  0   |   Needs 
tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by Joshua "jag" Ginsberg ):

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


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

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

[Django] #15515: Django should support customizable project/app templates

2011-02-27 Thread Django

#15515: Django should support customizable project/app templates
+---
 Reporter:  Joshua "jag" Ginsberg|  Owner:  
nobody
   Status:  new |  Milestone:   
 
Component:  Core framework  |Version:  1.2  
 
 Keywords:  |   Triage Stage:  
Unreviewed
Has patch:  0   |  
+---
 The django management startproject and startapp commands use the templates
 in /django/conf/(project|app)_template without any option to use anything
 else. That's silly. The attached patch allows the user to specify the path
 to an alternate template, processed in the same manner.

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

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

Re: [Django] #717: If-Modified-Since checked for exact match

2011-02-27 Thread Django

#717: If-Modified-Since checked for exact match
---+
   Reporter:  Maniac | Owner: 
 adrian   
 Status:  reopened | Milestone: 
  
  Component:  HTTP handling|   Version: 
  
 Resolution:   |  Keywords: 
 http middleware conditional get if-modified-since
   Triage Stage:  Accepted | Has patch: 
 1
Needs documentation:  0|   Needs tests: 
 0
Patch needs improvement:  0|  
---+
Changes (by aaugustin):

  * needs_better_patch:  1 => 0


Comment:

 Existing tests in `tests/regressiontests/conditional_processing/models.py`
 are for the view decorators `condition`, `last_modified` and `etag`. The
 tests I added are for `ConditionnalGetMiddleware`. These are two different
 mechanisms to achieve the same goal, the former per-view, the latter
 globally. Obviously tests are similar, but they test different modules.

 Currently there are no tests for `ConditionnalGetMiddleware`. It seems to
 me that `tests/regressiontests/middleware/tests.py` is the proper place to
 test middleware, so I put the tests there.

 I have updated the patch to cope with the refactoring of
 `django.views.static` and `django.contrib.staticfiles`.
 I'm now using `django.utils.unittest.TestCase` when `django.test.TestCase`
 is not needed.

 New patch attached. Thanks for your review, lukeplant!

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

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

Re: [Django] #13411: Some improvement for query string built by utils.next_redirect if next parameter contains '#' anchor

2011-02-27 Thread Django

#13411: Some improvement for query string built by utils.next_redirect if next
parameter contains '#' anchor
---+
   Reporter:  timesong | Owner:  nobody
 Status:  new  | Milestone:  1.3   
  Component:  django.contrib.comments  |   Version:  1.1   
 Resolution:   |  Keywords:
   Triage Stage:  Ready for checkin| Has patch:  1 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by julien):

  * stage:  Accepted => Ready for checkin
  * needs_tests:  1 => 0
  * milestone:  => 1.3


Comment:

 I've actually gotten bitten by this in one of my current projects. The
 patch looks good. I've just updated the test to make sure it works both
 with and without a query string.

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

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

Re: [Django] #13411: Some improvement for query string built by utils.next_redirect if next parameter contains '#' anchor

2011-02-27 Thread Django

#13411: Some improvement for query string built by utils.next_redirect if next
parameter contains '#' anchor
---+
   Reporter:  timesong | Owner:  nobody
 Status:  new  | Milestone:
  Component:  django.contrib.comments  |   Version:  1.1   
 Resolution:   |  Keywords:
   Triage Stage:  Accepted | Has patch:  1 
Needs documentation:  0|   Needs tests:  1 
Patch needs improvement:  0|  
---+

Comment (by jonasnockert):

 Should/could this be marked as milestone 1.4?

 For what it's worth, there's a little more information on
 [http://stackoverflow.com/questions/1735357/remove-the-comment-variable-
 from-url-after-posting-django Stack Overflow].

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

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

Re: [Django] #15513: CharField ForeignKey forced to int during lookup in get_prep_value in django.db.models.fields

2011-02-27 Thread Django

#15513: CharField ForeignKey forced to int during lookup in get_prep_value in
django.db.models.fields
+---
Reporter: harijay | Owner: nobody
Status: closed| Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: invalid | Keywords:
Triage Stage: Unreviewed| Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
+---
Changes (by kmtracey):

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

Comment:

The cause of the exception you are seeing is that per your Django models,
the target column of the !ForeignKey field in your Child model is the
primary key field of Parent, not the ssn field. Primary key field of
parent is an integer, so attempting to lookup a non-integer value raises
an exception.

In order to tell Django that the target column for the !ForeignKey field
in child is the parent's ssn field, you need to specify to_field='ssn' on
that !ForeignKey definition. See:

http://docs.djangoproject.com/en/1.2/ref/models/fields/#django.db.models.ForeignKey.to_field

Note though that your existing table definitions don't meet the
requirements for a !ForeignKey field here, because the Parent ssn field is
not unique. Django's !ForeignKey is a many-to-one relation, so the target
column must be unique. See #11702. If you are not actually creating the
tables via syncdb you may not initially see any error related to this
failure to meet the requirements for a !ForeignKey -- but if in fact you
have duplicated values in that target field, you may see errors later on.

Your Django models also show evidence of bug #5725. The max_length values
for all your !CharFields are 3x higher than they should be. Easiest fix is
to manually correct them to be the right value.

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

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

[Django] #15514: Django 1.2 tutorial03 error template clarification

2011-02-27 Thread Django

#15514: Django 1.2 tutorial03 error template clarification
--+-
 Reporter:  cubex |  Owner:  nobody
   Status:  new   |  Milestone:
Component:  Documentation |Version:  1.2   
 Keywords:  404 template error debug  |   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 On [http://docs.djangoproject.com/en/1.2/intro/tutorial03/ page 3 of the
 Django tutorial], it's worth confirming that custom 404.html and 500.html
 templates need to be in the in the top level of the template tree, i.e.
 loose in the templates folder (as stated under
 [http://docs.djangoproject.com/en/dev/topics/http/views/#the-
 http404-exception Writing Views]).

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

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

Re: [Django] #15507: Savepoint support for MySQL backend

2011-02-27 Thread Django

#15507: Savepoint support for MySQL backend
+---
   Reporter:  lamby | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by TomaszZielinski):

 * cc: tomasz.zielinski@… (added)


Comment:

 Have you verified that MySQLdb supports savepoints? I'm pretty sure that
 once I checked that and it didn't.

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

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

[Django] #15513: CharField ForeignKey forced to int during lookup in get_prep_value in django.db.models.fields

2011-02-27 Thread Django

#15513: CharField ForeignKey forced to int during lookup  in get_prep_value in
django.db.models.fields
--+-
 Reporter:  harijay   |  Owner:  nobody
   Status:  new   |  Milestone:
Component:  Database layer (models, ORM)  |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 I created a small test case to illustrate the problem.

 {{{
 >>> c = Child.objects.filter(parents_ssn="2354234234")

 Suceeds!

 >>> print c[0].name
 werwer sdfgsdg

 The following lookup fails

 >>> cfails = Child.objects.filter(parents_ssn="g354234234c")
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/hari/djtrunk/django/db/models/manager.py", line 141, in
 filter
 return self.get_query_set().filter(*args, **kwargs)
   File "/home/hari/djtrunk/django/db/models/query.py", line 550, in filter
 return self._filter_or_exclude(False, *args, **kwargs)
   File "/home/hari/djtrunk/django/db/models/query.py", line 568, in
 _filter_or_exclude
 clone.query.add_q(Q(*args, **kwargs))
   File "/home/hari/djtrunk/django/db/models/sql/query.py", line 1170, in
 add_q
 can_reuse=used_aliases, force_having=force_having)
   File "/home/hari/djtrunk/django/db/models/sql/query.py", line 1105, in
 add_filter
 connector)
   File "/home/hari/djtrunk/django/db/models/sql/where.py", line 67, in add
 value = obj.prepare(lookup_type, value)
   File "/home/hari/djtrunk/django/db/models/sql/where.py", line 316, in
 prepare
 return self.field.get_prep_lookup(lookup_type, value)
   File "/home/hari/djtrunk/django/db/models/fields/related.py", line 136,
 in get_prep_lookup
 return self._pk_trace(value, 'get_prep_lookup', lookup_type)
   File "/home/hari/djtrunk/django/db/models/fields/related.py", line 209,
 in _pk_trace
 v = getattr(field, prep_func)(lookup_type, v, **kwargs)
   File "/home/hari/djtrunk/django/db/models/fields/__init__.py", line 882,
 in get_prep_lookup
 return super(IntegerField, self).get_prep_lookup(lookup_type, value)
   File "/home/hari/djtrunk/django/db/models/fields/__init__.py", line 292,
 in get_prep_lookup
 return self.get_prep_value(value)
   File "/home/hari/djtrunk/django/db/models/fields/__init__.py", line 876,
 in get_prep_value
 return int(value)
 ValueError: invalid literal for int() with base 10: 'g354234234c'


 
 models.py has:
 

 from django.db import models

 class Parent(models.Model):
 id = models.IntegerField(primary_key=True)
 name = models.CharField(max_length=384, blank=True)
 ssn = models.CharField(max_length=768, blank=True)
 class Meta:
 db_table = u'Parent'
 app_label = u'mydjapp'

 class Child(models.Model):
 id = models.IntegerField(primary_key=True)
 name = models.CharField(max_length=384, blank=True)
 parents_ssn = models.ForeignKey(Parent, null=True,
 db_column='parents_ssn', blank=True)
 class Meta:
 db_table = u'child'
 app_label= u'mydjapp'

 ~
 #
 The database columns are:
 ##

 mysql> select * from Parent;
 ++--+--+
 | id | name | ssn  |
 ++--+--+
 |  1 | Aefwesk baob | 42s354234234 |
 |  2 | Ask bob  | 2354234234   |
 |  3 | Seelan Cyata | 2354234234c  |
 |  4 | Hdel Abnot   | g354234234c  |
 ++--+--+
 4 rows in set (0.00 sec)


 mysql> select * from child;
 +++-+
 | id | name   | parents_ssn |
 +++-+
 |  1 | werwer sdfgsdg | 2354234234  |
 |  2 | Hyadr Abnot| g354234234c |
 +++-+
 2 rows in set (0.00 sec)



 ##
 The raw SQL test was setup :
 ###
 CREATE TABLE `Parent` (

   `id` int(11) NOT NULL,
   `name` varchar(128) DEFAULT NULL,
   `ssn` varchar(256) DEFAULT NULL,
   PRIMARY KEY (`id`),

   KEY `parents_ssn_fk` (`ssn`)
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |


 CREATE TABLE `child` (

   `id` int(11) NOT NULL,
   `name` varchar(128) DEFAULT NULL,
   `parents_ssn` varchar(256) DEFAULT NULL,
   PRIMARY KEY (`id`),

   KEY `parents_ssn` (`parents_ssn`),
   CONSTRAINT `child_ibfk_1` FOREIGN KEY (`parents_ssn`) REFERENCES
 `Parent` (`ssn`)
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this g

Re: [Django] #2550: [patch] Allow a Backend to Globally Fail Authentication

2011-02-27 Thread Django

#2550: [patch] Allow a Backend to Globally Fail Authentication
+---
   Reporter:  umbrae@…  | Owner:  aashu_dwivedi 
   
 Status:  new   | Milestone:
   
  Component:  Contrib apps  |   Version:  SVN   
   
 Resolution:|  Keywords:  authentication 
backends easy-pickings
   Triage Stage:  Accepted  | Has patch:  1 
   
Needs documentation:  1 |   Needs tests:  0 
   
Patch needs improvement:  1 |  
+---
Changes (by lrekucki):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted
  * needs_docs:  0 => 1


Comment:

 Yes, otherwise people won't even know the feature is available.

 Some comments to the patch:

 * Your tests fail (did you runned them?):
 {{{
 Traceback (most recent call last):
   File "/home/lrekucki/django/django-
 gh/django/contrib/auth/tests/auth_backends.py", line 388, in
 test_authenticates
 self.assertEqual(authenticate(username='test',password='test'),self.user1)
 NameError: global name 'authenticate' is not defined
 }}}

 * Some of your code (like "except PermissionDenied" in
 {{{django/contrib/__init__.py}}}) is indented with tabs. Mixin spaces and
 tabs is bad. Django prefers 4 spaces as indentation.
 * You should also format your code according to PEP8 (i.e. whitespace
 around operators, whitespace after comma in argument list).

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

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

Re: [Django] #15255: DB Cache table creation (createcachetable) ignores the DB Router

2011-02-27 Thread Django

#15255: DB Cache table creation (createcachetable) ignores the DB Router
+---
   Reporter:  zvikico   | Owner:  nobody  
 Status:  new   | Milestone:  
  Component:  Cache system  |   Version:  1.3-beta
 Resolution:|  Keywords:  
   Triage Stage:  Accepted  | Has patch:  1   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by aaugustin):

 * cc: aaugustin (added)
  * has_patch:  0 => 1


Comment:

 Attached patch resolves the problem described above.

 While writing it, I noticed that `createcachetable` could be much more
 automatic. Currently the docs at
 http://docs.djangoproject.com/en/dev/topics/cache/#database-caching
 suggest first creating the table, then adding the cache backend settings.
 Couldn't we do the opposite: first add the cache backend settings, then
 create the table? `createcachetable` would go through the cache backends,
 find all instances of !BaseDatabaseCache, and create the tables with the
 appropriate name, like this:
 {{{
 from django.conf import settings
 from django.core.cache import get_cache

 for cache_alias in settings.CACHES:
 cache = get_cache(cache_alias)
 if isinstance(cache, BaseDatabaseCache):
 tablename = cache._table
... create the table ...
 }}}
 What do you think? Should I create a different ticket for this?

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

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

Re: [Django] #2550: [patch] Allow a Backend to Globally Fail Authentication

2011-02-27 Thread Django

#2550: [patch] Allow a Backend to Globally Fail Authentication
-+--
   Reporter:  umbrae@…   | Owner:  aashu_dwivedi

 Status:  new| Milestone:   

  Component:  Contrib apps   |   Version:  SVN  

 Resolution: |  Keywords:  authentication 
backends easy-pickings
   Triage Stage:  Ready for checkin  | Has patch:  1

Needs documentation:  0  |   Needs tests:  0

Patch needs improvement:  0  |  
-+--
Changes (by aashu_dwivedi):

  * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #2550: [patch] Allow a Backend to Globally Fail Authentication

2011-02-27 Thread Django

#2550: [patch] Allow a Backend to Globally Fail Authentication
+---
   Reporter:  umbrae@…  | Owner:  aashu_dwivedi 
   
 Status:  new   | Milestone:
   
  Component:  Contrib apps  |   Version:  SVN   
   
 Resolution:|  Keywords:  authentication 
backends easy-pickings
   Triage Stage:  Accepted  | Has patch:  1 
   
Needs documentation:  0 |   Needs tests:  0 
   
Patch needs improvement:  0 |  
+---

Comment (by aashu_dwivedi):

 I am not sure but do i need to update the documentation also ?

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

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

49 matches

Mail list logo