Re: [Django] #11700: actions and list_editables in popups problematic

2010-09-02 Thread Django 
#11700: actions and list_editables in popups problematic
+---
  Reporter:  sehmasch...@gmail.com  | Owner:  DrMeers  
Status:  new| Milestone:  1.3  
 Component:  django.contrib.admin   |   Version:  SVN  
Resolution: |  Keywords:  design_ux
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by DrMeers):

  * status:  reopened => new
  * version:  => SVN
  * milestone:  => 1.3
  * owner:  nobody => DrMeers
  * has_patch:  0 => 1
  * stage:  Design decision needed => Accepted

Comment:

 http://groups.google.com/group/django-
 developers/browse_thread/thread/c8da7710647dc979

-- 
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] #12106: FileFields ignore initial data when required=False

2010-09-02 Thread Django 
#12106: FileFields ignore initial data when required=False
---+
  Reporter:  etianen   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Forms |   Version:  1.1   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 If you believe an issue has been resolved, then mark it closed. Trac is
 completely open for all to modify for exactly this reason. If it turns out
 you are mistaken, the original reporter can always reopen. In this case,
 you *are* the original reporter, so that's not likely to happen :-)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #13205: Fix empty value detection in DateTimeField with SplitDateTimeWidget rendering

2010-09-02 Thread Django 
#13205: Fix empty value detection in DateTimeField with SplitDateTimeWidget
rendering
-+--
  Reporter:  Bastian Kleineidam   | Owner:  
nobody
Status:  new | Milestone:   
 
 Component:  Forms   |   Version:  
1.1   
Resolution:  |  Keywords:   
 
 Stage:  Accepted| Has_patch:  
1 
Needs_docs:  0   |   Needs_tests:  
0 
Needs_better_patch:  0   |  
-+--
Comment (by kmtracey):

 Is this different from #8898?

-- 
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] #14219: Incorrect empty field validation for DateTimeField with SplitDateTimeWidget

2010-09-02 Thread Django 
#14219: Incorrect empty field validation for DateTimeField with 
SplitDateTimeWidget
-+--
  Reporter:  pma_| Owner:  nobody  
Status:  closed  | Milestone:  1.3 
 Component:  Forms   |   Version:  1.1 
Resolution:  duplicate   |  Keywords:  validation DateTimeField
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 I think this is the same as #13205

-- 
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] #5833: Custom FilterSpecs

2010-09-02 Thread Django 
#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by fas):

 Can you please give a concrete example where multiple filter spec are used
 in such a way that it causes a problem?

-- 
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] #14219: Incorrect empty field validation for DateTimeField with SplitDateTimeWidget

2010-09-02 Thread Django 
#14219: Incorrect empty field validation for DateTimeField with 
SplitDateTimeWidget
+---
   Reporter:  pma_  |Owner:  nobody
 Status:  new   |Milestone:  1.3   
  Component:  Forms |  Version:  1.1   
   Keywords:  validation DateTimeField  |Stage:  Unreviewed
  Has_patch:  0 |   Needs_docs:  0 
Needs_tests:  0 |   Needs_better_patch:  0 
+---
 Create simple form with field like dt =
 DateTimeField(widget=SplitDateTimeWidget)
 clean will report error, source is in first line of
 DateTimeField.to_python
 in case of SplitDateTimeWidget value is ['', ''] and this one is missing
 from validators.EMPTY_VALUES.

 I'm not sure if it's safe to simply path validators.EMPTY_VALUES by adding
 ['',''] to 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-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] #5833: Custom FilterSpecs

2010-09-02 Thread Django 
#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by subsume):

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

Comment:

 One problem I have with this--and this may be completely irrelevant, is
 the get_query_set method.

 The problem I see is that it accepts and returns a filtered queryset and
 these FilterSpecs chain like so:

 Model.objects.filter(x=y).filter(z=y).filter(a=y)

 When it comes to related objects, this is a problem because:

 Model.objects.filter(x__z=y).filter(x__y=z).filter(y__x=a)

 ...is not the same as:

 Model.objects.filter(Q(x__z=y)(x__y=z)(y__x=a))

 One solution may be to allow get_query_set to return a Q() object and then
 string them together as above. Sure, you're still locked into a chain of
 &-joined Q objects but you already are and it could be the stuff of future
 tickets.

 If there's a better place to have this discussion please forward me along.
 =). Thanks.

-- 
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] #14218: Paginator just implement the __iter__ function

2010-09-02 Thread Django 
#14218: Paginator just implement the __iter__ function
+---
  Reporter:  mlhamel| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution: |  Keywords:
 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:

> Right now, when you want to iter into all the pages of a Paginator object
> you to use the page_range function. It would be more logical and naturel
> to use the normal python of doing that by implementing the __iter__
> function like that:
>
> def __iter__(self):
> for page_num in self.page_range:
> yield self.page(page_num)

New description:

 Right now, when you want to iter into all the pages of a Paginator object
 you to use the page_range function. It would be more logical and naturel
 to use the normal python of doing that by implementing the __iter__
 function like that:
 {{{
 def __iter__(self):
 for page_num in self.page_range:
 yield self.page(page_num)
 }}}

Comment:

 Reformatted, please use the preview button in the future.

-- 
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] #14218: Paginator just implement the __iter__ function

2010-09-02 Thread Django 
#14218: Paginator just implement the __iter__ function
---+
 Reporter:  mlhamel|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Right now, when you want to iter into all the pages of a Paginator object
 you to use the page_range function. It would be more logical and naturel
 to use the normal python of doing that by implementing the __iter__
 function like that:

 def __iter__(self):
 for page_num in self.page_range:
 yield self.page(page_num)

-- 
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] #12106: FileFields ignore initial data when required=False

2010-09-02 Thread Django 
#12106: FileFields ignore initial data when required=False
---+
  Reporter:  etianen   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by etianen):

 Looking over the Django source code, it would appear that this issue has
 been fixed. Many thanks!

 Would it be okay to mark this as 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-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] #12012: Integration with the Python standard library logging module

2010-09-02 Thread Django 
#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by remibroemeling):

 Sorry for the double post, but possibly the .setLevel() call should be
 moved to take place under "if len(logger.handlers) == 0:" as well.

-- 
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] #12012: Integration with the Python standard library logging module

2010-09-02 Thread Django 
#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by remibroemeling):

 A comment on http://bazaar.launchpad.net/~vinay-
 sajip/django/logging/revision/56 , specifically the code:

 {{{
 if len(logger.handlers) == 0:
 logger.addHandler(NullHandler())
 logger.propagate = False
 }}}

 This will set the 'django' logger not to propagate, even if the user
 (previous to the inclusion of django) has it configured TO propagate.
 Changing it to:

 {{{
 if len(logger.handlers) == 0:
 logger.addHandler(NullHandler())
 logger.propagate = False
 }}}

 ... would have the same effect in the case of Django starting up when
 logging hasn't been configured, but wouldn't alter an existing logging
 setup in a way that the user wouldn't expect.

-- 
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] #10733: Invalid results when deferring fields in more than one related model with only()

2010-09-02 Thread Django 
#10733: Invalid results when deferring fields in more than one related model 
with
only()
---+
  Reporter:  mrts  | Owner:  nobody 

Status:  reopened  | Milestone:  1.3

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

Resolution:|  Keywords:  
efficient-admin
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Changes (by wdoekes):

 * cc: walter+dja...@wjd.nu (added)

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

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

Re: [Django] #12012: Integration with the Python standard library logging module

2010-09-02 Thread Django 
#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by remibroemeling):

 * cc: remibroemeling (added)

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

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

Re: [Django] #13095: modelform_factory, modelformset_factory, inlineformset_factory formfield_callback lamba function missing **kwargs

2010-09-02 Thread Django 
#13095: modelform_factory, modelformset_factory, inlineformset_factory
formfield_callback lamba function missing **kwargs
---+
  Reporter:  hvdklauw  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Forms |   Version:  SVN  
Resolution:|  Keywords:  inlineformset_factory
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by frans):

 * cc: franc...@verbeek.name (added)

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

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

Re: [Django] #9625: ForeignKey data type for certain derived model fields not calculated correctly

2010-09-02 Thread Django 
#9625: ForeignKey data type for certain derived model fields not calculated
correctly
---+
  Reporter:  robbyd| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by hartror):

 The other problem with the above example is if you don't derive from
 AutoField (which I didn't) then the ForeignKey will get the the
 rel_field.db_type() as it's own which in this case will be 'bigint
 UNSIGNED AUTO_INCREMENT'. This of course is invalid being that the
 ForeignKey can't auto increment. My solution has been to write the CREATE
 TABLE SQL myself.

 This of course is the easy MySQL example, it gets even more fun when we
 start to deal with the other 3 databases that Django supports.

-- 
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] #14217: Fieldname cannot be the same as the Modelname when using model inheritance

2010-09-02 Thread Django 
#14217: Fieldname cannot be the same as the Modelname when using model 
inheritance
---+
 Reporter:  willian|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 {{{
 class Place(models.Model):
 pass

 class Restaurant(Place):
 restaurant = models.CharField(max_length=100)

 }}}

 When accessing Restaurant in the admin, a ValueError is Raised:

 
 ValueError at /admin/questionnaire/restaurant/add/
 Cannot assign "''": "Restaurant.restaurant" must be a "Restaurant"
 instance.
 ---

-- 
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] #14216: Tutorial 2 - Decoupling the URLconfs

2010-09-02 Thread Django 
#14216: Tutorial 2 - Decoupling the URLconfs
+---
  Reporter:  Youdaman   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Duplicate of #13865, #13507, #12126, #11464, #11424, #11172, #10081,
 #9860, #9767, #7709, #7660, #7650, #7443, #5283, #4087 and #3941.

 We know about this issue, but it's not as simple as just removing a
 prefix. We need to do a tutorial rewrite to introduce the idea of reusable
 apps.

-- 
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] #14216: Tutorial 2 - Decoupling the URLconfs

2010-09-02 Thread Django 
#14216: Tutorial 2 - Decoupling the URLconfs
+---
  Reporter:  Youdaman   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Youdaman):

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

[Django] #14216: Tutorial 2 - Decoupling the URLconfs

2010-09-02 Thread Django 
#14216: Tutorial 2 - Decoupling the URLconfs
---+
 Reporter:  Youdaman   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://docs.djangoproject.com/en/1.2/intro/tutorial03/#decoupling-the-
 urlconfs

 The first line of final code snippet should read:

 urlpatterns = patterns('polls.views',

 i.e. remove the 'mysite' bit if you want to really decouple the urlconf as
 per the intention of this section of 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.