date:20110203

Re: [Django] #15221: Show field's verbose name instead of related model name for M2M filterspecs

2011-02-03 Thread Django

#15221: Show field's verbose name instead of related model name for M2M 
filterspecs
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  0 |  
+---
Changes (by anonymous):

  * needs_tests:  0 => 1


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

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

Re: [Django] #15221: Show field's verbose name instead of related model name for M2M filterspecs

2011-02-03 Thread Django

#15221: Show field's verbose name instead of related model name for M2M 
filterspecs
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by anonymous):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => Accepted


Comment:

 Yes, this problem exists, but no, it isn't related (directly) #3400
 specific -- the same problem exists in 1.2.X.

-- 
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] #15220: replace SelectFilter2.js with a jQuery plugin

2011-02-03 Thread Django

#15220: replace SelectFilter2.js with a jQuery plugin
+---
   Reporter:  slurms| Owner:  slurms
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by anonymous):

  * needs_better_patch:  => 1
  * needs_docs:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => Accepted


Comment:

 This needs to be reviewed by someone with better JS-foo than I have, but
 two initial impressions:

  1. The instantiation code (widgets.py) looks a lot more complex -- is
 there any way to clean up that interface?
  2. The widget.py code also contains a TODO. If we're refactoring in this
 area, it's a prime opportunity to do that cleanup.

-- 
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] #15222: Documentation example contains an incorrect class name

2011-02-03 Thread Django

#15222: Documentation example contains an incorrect class name
-+--
   Reporter:  Serp   | Owner:  nobody   
   
 Status:  new| Milestone:   
   
  Component:  Documentation  |   Version:   
   
 Resolution: |  Keywords:  cache, 
documentation
   Triage Stage:  Ready for checkin  | Has patch:  0
   
Needs documentation:  0  |   Needs tests:  0
   
Patch needs improvement:  0  |  
-+--
Changes (by anonymous):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15203: admin search_fields splitting query

2011-02-03 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  1 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---
Changes (by anonymous):

  * 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] #15200: ManyToManyField combined with "|" leads to trouble

2011-02-03 Thread Django

#15200: ManyToManyField combined with "|" leads to trouble
-+--
   Reporter:  vanschelven| Owner:  nobody
 Status:  closed | Milestone:
  Component:  Uncategorized  |   Version:  1.2   
 Resolution:  invalid|  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by anonymous):

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


Comment:

 Are you referring to the fact that there is a duplicate in the results? If
 this is the case, then this is a case of abstraction leakage, overcome
 with the use of
 
[http://docs.djangoproject.com/en/1.2/ref/models/querysets/#django.db.models.QuerySet.distinct
 distinct()]

-- 
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] #15222: Documentation example contains an incorrect class name

2011-02-03 Thread Django

#15222: Documentation example contains an incorrect class name
--+-
 Reporter:  Serp  |  Owner:  nobody
   Status:  new   |  Milestone:
Component:  Documentation |Version:
 Keywords:  cache, documentation  |   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 The example under cache arguments
 [http://docs.djangoproject.com/en/dev/topics/cache/#cache-arguments see
 here]

 django.core.cache.backends.filebased.FileCache

 should be:

 django.core.cache.backends.filebased.File'''Based'''Cache

-- 
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] #14230: Documentation for Auth's Logout view suggests wrong redirect takes precedence.

2011-02-03 Thread Django

#14230: Documentation for Auth's Logout view suggests wrong redirect takes
precedence.
+---
   Reporter:  Keryn Knight | 
Owner:  justinlilly
 Status:  assigned  | 
Milestone: 
  Component:  Authentication|   
Version:  1.2
 Resolution:|  
Keywords:  auth logout
   Triage Stage:  Accepted  | Has 
patch:  0  
Needs documentation:  0 |   Needs 
tests:  0  
Patch needs improvement:  0 |  
+---
Changes (by justinlilly):

  * status:  new => assigned
  * owner:  nobody => justinlilly
  * component:  Documentation => Authentication


Comment:

 I agree with andretavares that the documentation makes sense and the
 implementation does not.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12743: Add a style guide for javascript in the admin

2011-02-03 Thread Django

#12743: Add a style guide for javascript in the admin
-+--
   Reporter:  Alex   | Owner:  nobody
 Status:  new| Milestone:
  Component:  Documentation  |   Version:  1.1   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by justinlilly):

 * cc: justinlilly@… (added)


Comment:

 The paste you've setup does not exist any longer. Do you have it? Can you
 attach it to this ticket?

-- 
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] #11930: Django docs styles confuse H3 & H4

2011-02-03 Thread Django

#11930: Django docs styles confuse H3 & H4
---+
   Reporter:  david@…  | Owner:  cogat
 Status:  assigned | Milestone:  1.3  
  Component:  Django Web site  |   Version:  1.1  
 Resolution:   |  Keywords:  sprintdec2010
   Triage Stage:  Accepted | Has patch:  1
Needs documentation:  0|   Needs tests:  0
Patch needs improvement:  0|  
---+
Changes (by justinlilly):

 * cc: justinlilly@… (added)
  * has_patch:  0 => 1
  * component:  Documentation => Django Web site


Comment:

 https://github.com/jacobian/djangoproject.com/pull/11

-- 
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] #15221: Show field's verbose name instead of related model name for M2M filterspecs

2011-02-03 Thread Django

#15221: Show field's verbose name instead of related model name for M2M 
filterspecs
--+-
 Reporter:  julien|  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  django.contrib.admin  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 Consider the following example:

 Model:
 {{{
 #!python
 from django.db import models
 from django.contrib.auth.models import User

 class Book(models.Model):
 title = models.CharField(max_length=25)
 year = models.PositiveIntegerField(null=True, blank=True)
 author = models.ForeignKey(User, related_name='books_authored',
 blank=True, null=True)
 contributors = models.ManyToManyField(User,
 related_name='books_contributed', blank=True, null=True)
 }}}

 Admin:
 {{{
 #!python
 from django.contrib import admin

 from .models import Book

 class BookAdmin(admin.ModelAdmin):
 list_display = ('title', 'year', 'author')
 list_filter = ('year', 'author', 'contributors')

 admin.site.register(Book, BookAdmin)
 }}}

 Presumably since #3400 was fixed, M2M filterspecs are using the related
 model's name as title. This leads the example above to display "By user"
 instead of "By contributors". This is a bit silly in itself but it could
 be even more problematic if multiple M2M filters to User were specified at
 the same time.

 I've discussed this with DrMeers (who wrote the patch for #3400). The
 patch I'm attaching seems to fix the issue but we might have to
 investigate a bit more to see if there are cases where it wouldn't make
 sense to show the field's verbose name for a M2M.

 The patch doesn't contain tests yet. I'm waiting to get feedback on the
 latest patch I've posted in #8528 which introduces a new module for
 filterspecs' tests. If #8529 gets checked in then writing tests for this
 patch will be trivial.

-- 
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] #8528: Admin list_filter doesn't respect null=True

2011-02-03 Thread Django

#8528: Admin list_filter doesn't respect null=True
+---
   Reporter:  StevenPotter  | Owner:  julien   
 Status:  new   | Milestone:  1.3  
  Component:  django.contrib.admin  |   Version:  1.3-alpha
 Resolution:|  Keywords:   
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---

Comment (by julien):

 OK, I've written a patch based on marcob's, with some small tweaks. In
 particular I'm using EMPTY_CHANGELIST_VALUE (instead of _('None')) for
 consistency with the way NULL values are displayed in readonly fields and
 in the changelist, and also to dissociate it from the 'All' filter which
 has a different purpose.

 The tests are based on oyvind's patch and I've also added tests for the FK
 and M2M filters.

 Let me know what you think. I'm particularly wondering about the condition
 "if hasattr(self.field, 'rel')" which I had to add to avoid breaking the
 existing admin views 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] #14543: ContentTypes tests fails if auth app is not installed

2011-02-03 Thread Django

#14543: ContentTypes tests fails if auth app is not installed
+---
   Reporter:  sayane| Owner:  dmoisset
 Status:  new   | Milestone:  1.3 
  Component:  Contrib apps  |   Version:  SVN 
 Resolution:|  Keywords:  
   Triage Stage:  Accepted  | Has patch:  1   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  1 |  
+---
Changes (by russellm):

  * needs_better_patch:  0 => 1


Comment:

 I'm not convinced the approach taken by the patch is correct. auth is
 being used here because we need a model on which to invoke shortcut(), and
 auth is a generally reliable option.

 However, auth isn't always available, so we just need to find a
 substitute. Turns out you can actually define a model in tests.py, and
 that model will be available during testing, but not in production. This
 avoids the need to create a second test module for contenttype tests. It
 also provides an opportunity to test aspects of shortcut() that aren't
 currently tested -- testing models that *don't* have get_absolute_url
 defined.

-- 
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] #12103: Setting in contrib.auth AuthenticationForm to let inactive users log in

2011-02-03 Thread Django

#12103: Setting in contrib.auth AuthenticationForm to let inactive users log in
--+-
   Reporter:  ejucovy | Owner:  nobody
 Status:  new | Milestone:
  Component:  Authentication  |   Version:  1.1   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by lrekucki):

  * needs_better_patch:  0 => 1


Comment:

 Did you actually run the tests? By the look of the patch they aren't even
 syntacticly correct.

-- 
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] #15220: replace SelectFilter2.js with a jQuery plugin

2011-02-03 Thread Django

#15220: replace SelectFilter2.js with a jQuery plugin
--+-
 Reporter:  slurms|  Owner:  slurms
   Status:  new   |  Milestone:
Component:  django.contrib.admin  |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 I needed to extend the functionality of the select filter, so I rewrote it
 in jQuery. I noticed a discussion about replacing some of the admin
 javascript with jQuery, so this is a first attempt at replacing
 {{{SelectFilter2.js}}} with {{{jquery.selectfilter.js}}}.

 Discussion is here: http://groups.google.com/group/django-
 
developers/browse_thread/thread/ff460085a3bfb12e/2c4e6f5a9807c19b?lnk=gst=jquery#2c4e6f5a9807c19b

-- 
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] #12103: Setting in contrib.auth AuthenticationForm to let inactive users log in

2011-02-03 Thread Django

#12103: Setting in contrib.auth AuthenticationForm to let inactive users log in
--+-
   Reporter:  ejucovy | Owner:  nobody
 Status:  new | Milestone:
  Component:  Authentication  |   Version:  1.1   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by ejucovy):

  * needs_better_patch:  1 => 0


Comment:

 I've added a new version of the patch
 [http://code.djangoproject.com/attachment/ticket/12103/12103_with_tests.diff
 12103_with_tests.diff] -- which includes lasko's 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] #14824: django.utils.get_format_modules doesn't respect USE_L10N

2011-02-03 Thread Django

#14824: django.utils.get_format_modules doesn't respect USE_L10N
+---
   Reporter:  nullie| Owner:  nobody 
 Status:  new   | Milestone:  1.3
  Component:  Internationalization  |   Version:  1.2
 Resolution:|  Keywords:  blocker
   Triage Stage:  Accepted  | Has patch:  1  
Needs documentation:  0 |   Needs tests:  1  
Patch needs improvement:  0 |  
+---
Changes (by ramiro):

  * keywords:  => blocker


-- 
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] #14824: django.utils.get_format_modules doesn't respect USE_L10N

2011-02-03 Thread Django

#14824: django.utils.get_format_modules doesn't respect USE_L10N
+---
   Reporter:  nullie| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  Internationalization  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  0 |  
+---

Comment (by ramiro):

 #15218 describes a series of steps to reproduce a use case in the admin
 app that is broken because of this issue, was closed as a duplicate of
 this ticket.

-- 
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] #15218: USE_L10N, USE_I18N and DateTime Validation

2011-02-03 Thread Django

#15218: USE_L10N, USE_I18N and DateTime Validation
+---
   Reporter:  idle  | Owner:  nobody
 
 Status:  closed| Milestone:  1.3   
 
  Component:  django.contrib.admin  |   Version:  1.3-beta  
 
 Resolution:  duplicate |  Keywords:  blocker, 
regression
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by ramiro):

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


Comment:

 Bisection shows this change of behavior occurred in r13898 (r13903 for
 1.2.X between 1.2.3 and 1.2.4). Thus, I'm going to close this as a
 duplicate of #14824 adding a pointer to it there because I think they
 describe the same 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] #15213: Add support for compressors/minimizers to django.contrib.staticfiles (was: [PATCH] Add support for compressors/minimizers to django.contrib.staticfiles)

2011-02-03 Thread Django

#15213: Add support for compressors/minimizers to django.contrib.staticfiles
--+-
   Reporter:  sebastian_noack | Owner:  
 
 Status:  closed  | Milestone:  
 
  Component:  django.contrib.staticfiles  |   Version:  
1.3-alpha
 Resolution:  wontfix |  Keywords:  
 
   Triage Stage:  Accepted| Has patch:  1   
 
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] #14518: Field.to_python not called on foreign key IDs

2011-02-03 Thread Django

#14518: Field.to_python not called on foreign key IDs
+---
   Reporter:  wolever   | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by wolever):

 * cc: wolever (added)


Comment:

 It may also be worth noting: I have a StackOverflow question asking the
 same thing here: http://stackoverflow.com/questions/3983510

-- 
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] #15217: Cache setting deprecation warning is too aggressive

2011-02-03 Thread Django

#15217: Cache setting deprecation warning is too aggressive
+---
   Reporter:  adamv | Owner:  nobody 
 Status:  new   | Milestone:  1.3
  Component:  Cache system  |   Version:  SVN
 Resolution:|  Keywords:  blocker
   Triage Stage:  Accepted  | Has patch:  0  
Needs documentation:  0 |   Needs tests:  0  
Patch needs improvement:  0 |  
+---

Comment (by adamv):

 For completeness, I run my app tests like "python -Wall manage.py
 "; I believe the -Wall is what makes this warning visible.

-- 
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] #15213: [PATCH] Add support for compressors/minimizers to django.contrib.staticfiles

2011-02-03 Thread Django

#15213: [PATCH] Add support for compressors/minimizers to
django.contrib.staticfiles
--+-
   Reporter:  sebastian_noack | Owner:  
 
 Status:  closed  | Milestone:  
 
  Component:  django.contrib.staticfiles  |   Version:  
1.3-alpha
 Resolution:  wontfix |  Keywords:  
 
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

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


Comment:

 I'm strongly opposed to adding more than the collectstatic command to
 staticfiles due to the fact that there are various post processing
 workflows that could be applied to the collected files, not all of which
 are enough to be called in the serial manner ``collectstatic`` works. In
 other words, there is nothing that prevents you right now to do this
 during the rest of your deployment (see Fabric examples in our docs).

 And even then, there already *is* a hook to enable post processing: the
 STATICFILES_STORAGE setting
 (http://docs.djangoproject.com/en/dev/ref/contrib/staticfiles
 /#staticfiles-storage)

 Marking as wontfix, please reopen in case there is a usecase that can't be
 implemented in a custom storage backend or an external script.

-- 
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] #15202: Changeset 15376 breaks implementation

2011-02-03 Thread Django

#15202: Changeset 15376 breaks implementation
--+-
   Reporter:  liorsion| Owner: 
 Status:  closed  | Milestone: 
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  invalid |  Keywords: 
   Triage Stage:  Unreviewed  | Has patch:  0  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  0   |  
--+-
Changes (by carljm):

  * needs_docs:  1 => 0


Comment:

 No, you're misunderstanding. STATICFILES_DIRS allows you to add sources
 for static files: this is where you keep your static files. In
 development, staticfiles will automatically serve things from your
 staticfiles sources (app static/ subdirs, and STATICFILES_DIRS).
 STATIC_ROOT is completely unnecessary in local development. STATIC_ROOT
 (and the collectstatic command) are only needed for deployment with a real
 webserver. The collectstatic command copies (or symlinks) static files
 from all sources into STATIC_ROOT, where you can configure your front-end
 webserver to serve them.

 Trac isn't a support resource, so if this still isn't clear to you, please
 don't follow up here. Review the staticfiles docs (they've been
 significantly updated in the last few days for clarity on these exact
 points) and if it still isn't making sense ask in #django on IRC (I'm
 usually there and would be glad to help) or on the django-users mailing
 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] #11577: PLNIPField validation error when empty

2011-02-03 Thread Django

#11577: PLNIPField validation error when empty
--+-
   Reporter:  amz | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.localflavor  |   Version:  1.0   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  1 
Patch needs improvement:  1   |  
--+-
Changes (by lrekucki):

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


Comment:

 Replying to [comment:4 anonymous]:
 > Ding dong, someone is really (try to) using it. Can you accept this
 ticket?

 It is accepted, but not ready for inclusion. First, it needs tests.
 Second, it doesn't fix the problem entirely. A string like "---" will pass
 the length check, then get stripped and an empty string will be passed to
 has_checksum_valid.

-- 
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] #15129: Invalid order of applying formats

2011-02-03 Thread Django

#15129: Invalid order of applying formats
+---
   Reporter:  tonnzor   | Owner:  nobody
 Status:  closed| Milestone:  1.3   
  Component:  Internationalization  |   Version:  1.2   
 Resolution:  fixed |  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by ramiro):

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


Comment:

 In [15402]:

 Fixed stability of data input/output L10N format modules priority order.
 Thanks tonnzor for the report and fix.

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

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

Re: [Django] #11577: PLNIPField validation error when empty

2011-02-03 Thread Django

#11577: PLNIPField validation error when empty
--+-
   Reporter:  amz | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.localflavor  |   Version:  1.0   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-

Comment (by anonymous):

 Ding dong, someone is really (try to) using it. Can you accept this
 ticket?

-- 
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] #14543: ContentTypes tests fails if auth app is not installed

2011-02-03 Thread Django

#14543: ContentTypes tests fails if auth app is not installed
+---
   Reporter:  sayane| Owner:  dmoisset
 Status:  new   | Milestone:  1.3 
  Component:  Contrib apps  |   Version:  SVN 
 Resolution:|  Keywords:  
   Triage Stage:  Accepted  | Has patch:  1   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by paulegan):

 * cc: paulegan@… (added)


Comment:

 Looks like this issue made it into 1.2.4 as well.  It's real easy to
 recreate:
 {{{#!sh
 django-admin.py startproject djangotest
 cd djangotest
 sed -e '/ENGINE/s/backends.//' -e '/contrib.auth/d' -i settings.py
 python manage.py test
 }}}
 The attached patch - or any other which removes test_shortcut_view - 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-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-03 Thread Django

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

Comment (by ramiro):

 This has been partially fixed in [15401].

-- 
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] #14101: Localized DecimalField doesn't accept localized input

2011-02-03 Thread Django

#14101: Localized DecimalField doesn't accept localized input
+---
   Reporter:  dfoerster | Owner:  nobody  
 Status:  closed| Milestone:  
  Component:  Internationalization  |   Version:  1.2 
 Resolution:  worksforme|  Keywords:  localize
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


Comment:

 This *still* isn't a reproducible test case. A reproducible test case
 requires code samples, or a full set of instructions. These instructions
 or code samples tells someone else *exactly* how to reproduce a problem.
 i.e., here are my models, here are my admin registrations, etc. Three
 screenshots is *not* a reproducible test case.

 However, based on what I can glean from your screenshots, this appears to
 be working as expected. Django's admin doesn't localize widgets by
 default. If you want localized widgets in the admin, you need to override
 forms. This is something that could be made easier, but doesn't change the
 fact that it isn't a bug as described.

-- 
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] #15202: Changeset 15376 breaks implementation

2011-02-03 Thread Django

#15202: Changeset 15376 breaks implementation
--+-
   Reporter:  liorsion| Owner: 
 Status:  closed  | Milestone: 
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  invalid |  Keywords: 
   Triage Stage:  Unreviewed  | Has patch:  0  
Needs documentation:  1   |   Needs tests:  0  
Patch needs improvement:  0   |  
--+-
Changes (by liorsion):

  * needs_docs:  0 => 1


Comment:

 I understand what you mean on destination vs. source, however, I would
 think most of the time the destination of staticfile collection would be
 the source for my STATICFILES_DIRS -> this is why I used staticfiles
 collection.

 This is what I see in my mind:

 src->templates->html files
 static->css,js, img files

 static directory is outside the src directory.

 STATIC_ROOT is used as destination to which static files are collected (in
 my example it would be the static dir)
 however, since I want my static files to be provided from there, that's
 directory is inside my STATICFILES_DIRS as well, no?

 If not - I would appreciate some more information on how you think the
 setup would be implemented.

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

2011-02-03 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
   Triage Stage:  Accepted  | Has patch:  1 
  
Needs documentation:  1 |   Needs tests:  1 
  
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * milestone:  1.3 =>


Comment:

 1.3 feature deadline has passed.

-- 
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] #8528: Admin list_filter doesn't respect null=True

2011-02-03 Thread Django

#8528: Admin list_filter doesn't respect null=True
+---
   Reporter:  StevenPotter  | Owner:  julien   
 Status:  new   | Milestone:  1.3  
  Component:  django.contrib.admin  |   Version:  1.3-alpha
 Resolution:|  Keywords:   
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * status:  assigned => new
  * owner:  oyvind => julien


Comment:

 I'm working on a patch. Hopefully we can ship this one in 1.3.

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

2011-02-03 Thread Django

#5833: Custom FilterSpecs
+---
   Reporter:  Honza_Kral| Owner:  jkocherhans   
  
 Status:  assigned  | Milestone:  1.3   
  
  Component:  django.contrib.admin  |   Version:  SVN   
  
 Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
   Triage Stage:  Accepted  | Has patch:  1 
  
Needs documentation:  1 |   Needs tests:  1 
  
Patch needs improvement:  0 |  
+---
Changes (by anonymous):

  * milestone:  => 1.3


-- 
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] #10743: Support lookup separators in ModelAdmin.list_display

2011-02-03 Thread Django

#10743: Support lookup separators in ModelAdmin.list_display
+---
   Reporter:  mrts  | Owner:  nobody
   
 Status:  new   | Milestone:  1.4   
   
  Component:  django.contrib.admin  |   Version:  SVN   
   
 Resolution:|  Keywords:  
efficient-admin, list_display
   Triage Stage:  Accepted  | Has patch:  1 
   
Needs documentation:  0 |   Needs tests:  0 
   
Patch needs improvement:  0 |  
+---
Changes (by anonymous):

  * milestone:  => 1.4


-- 
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] #13007: Django fails to log in when a cookie is set on the same domain containing a colon

2011-02-03 Thread Django

#13007: Django fails to log in when a cookie is set on the same domain 
containing a
colon
-+--
   Reporter:  Warlax | Owner:  nobody   
 
 Status:  reopened   | Milestone:  1.3  
 
  Component:  HTTP handling  |   Version:  SVN  
 
 Resolution: |  Keywords:  cookies, 
sprintdec2010
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--
Changes (by ramiro):

  * needs_better_patch:  1 => 0


Comment:

 I've attached the patch to apply after r15298. Please review,
 particularly:

  * Replaced a explicit `SimpleCookie.load(self, rawdata)` in the added
 load() method with a `super(SimpleCookie, self).load(rawdata)` call
  * Added a runtime `_cookie_allows_colon_in_names` flag in the same spirit
 of the `_morsel_supports_httponly` and `_cookie_encodes_correctly` already
 there.

-- 
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] #15218: USE_L10N, USE_I18N and DateTime Validation

2011-02-03 Thread Django

#15218: USE_L10N, USE_I18N and DateTime Validation
+---
   Reporter:  idle  | Owner:  nobody
 
 Status:  reopened  | Milestone:  1.3   
 
  Component:  django.contrib.admin  |   Version:  1.3-beta  
 
 Resolution:|  Keywords:  blocker, 
regression
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * keywords:  => blocker, regression
  * component:  Internationalization => django.contrib.admin
  * stage:  Unreviewed => Accepted


Comment:

 Now I see it. It's not a problem with validation or display of
 DateTimeFields themselves -- the problem is the widget itself generating a
 localized widget regardless of the USE_L10N value.

 Since this is in 1.2.X, but not in 1.2.3, it's a regression.

-- 
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] #14101: Localized DecimalField doesn't accept localized input

2011-02-03 Thread Django

#14101: Localized DecimalField doesn't accept localized input
+---
   Reporter:  dfoerster | Owner:  nobody  
 Status:  reopened  | Milestone:  
  Component:  Internationalization  |   Version:  1.2 
 Resolution:|  Keywords:  localize
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by aledr):

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


Comment:

 settings.py has LANGUAGE_CODE = 'pt-br'
 You can check at 'django/conf/locale/pt_BR/formats.py' that
 DECIMAL_SEPARATOR is set to ','.

 Please note fields 'Pressão' e 'Vazão', both are DecimalFields, check how
 it displays the list, the change form and the error when I try to input a
 comma separated number in the change form.

-- 
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] #15218: USE_L10N, USE_I18N and DateTime Validation

2011-02-03 Thread Django

#15218: USE_L10N, USE_I18N and DateTime Validation
+---
   Reporter:  idle  | Owner:  nobody  
 Status:  reopened  | Milestone:  1.3 
  Component:  Internationalization  |   Version:  1.3-beta
 Resolution:|  Keywords:  
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by idle):

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


Comment:

 > USE_I18N only affects translations - i.e., does the admin show "Добавить
 object" or "Add new object"
 Not since 1.2.4 or just not for me %)
 [[BR]]
 [[BR]]
 What you described is exactly how it was till 1.2.4.

 Let's try to reproduce this behaviour:
 1. Set LANGUAGE_CODE to 'ru';
 2. Set USE_I18N to True;
 2. Do not define USE_L10N;
 3. Go to admin anywhere where widget for DateTime is used;
 4. Generate current date. It whould be '03.02.2011';
 5. Now save;
 6. Here I've got Validation error since 1.2.4.

 Again, only if you put USE_L10N = True date validates fine.

 *Before 1.2.4 using the same settings there was ISO '2011-02-03' at step
 4.

-- 
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] #15213: [PATCH] Add support for compressors/minimizers to django.contrib.staticfiles

2011-02-03 Thread Django

#15213: [PATCH] Add support for compressors/minimizers to
django.contrib.staticfiles
--+-
   Reporter:  sebastian_noack | Owner:  
 
 Status:  new | Milestone:  
 
  Component:  django.contrib.staticfiles  |   Version:  
1.3-alpha
 Resolution:  |  Keywords:  
 
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-

Comment (by sebastian_noack):

 Every compression tool I have seen so far is able to read a file from
 stdin and to write the output to stdout. So I think that my patch is
 flexible enough for most programs. That way you can use the most common
 tools without the need to write a function that calls the external
 program. Also note that if you still want use a compressor that does not
 work that way you can wrap it with a simple script.

-- 
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] #15156: Ordinal numbers in English and in other locales

2011-02-03 Thread Django

#15156: Ordinal numbers in English and in other locales
-+--
   Reporter:  Besnik   | Owner:  
nobody
 Status:  new| Milestone:   
 
  Component:  Translations   |   Version:  
1.2   
 Resolution: |  Keywords:   
 
   Triage Stage:  Design decision needed | Has patch:  
0 
Needs documentation:  0  |   Needs tests:  
0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Design decision needed


Comment:

 Marking this DDN. Like claudep, I'm not convinced this is even possible,
 but i18n isn't my specialty.

-- 
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] #14101: Localized DecimalField doesn't accept localized input

2011-02-03 Thread Django

#14101: Localized DecimalField doesn't accept localized input
+---
   Reporter:  dfoerster | Owner:  nobody  
 Status:  closed| Milestone:  
  Component:  Internationalization  |   Version:  1.2 
 Resolution:  worksforme|  Keywords:  localize
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


Comment:

 ... and again, what is needed is a *clear test case*. Ideally, this would
 be a programatic test case, but I'll settle for a clear set of
 instructions. I have a set of test cases that test this feature, and they
 are currently passing. If you are convinced there is a problem, you need
 to show me *exactly* what is going wrong, and where.

-- 
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] #15213: [PATCH] Add support for compressors/minimizers to django.contrib.staticfiles

2011-02-03 Thread Django

#15213: [PATCH] Add support for compressors/minimizers to
django.contrib.staticfiles
--+-
   Reporter:  sebastian_noack | Owner:  
 
 Status:  new | Milestone:  
 
  Component:  django.contrib.staticfiles  |   Version:  
1.3-alpha
 Resolution:  |  Keywords:  
 
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_docs:  => 0
  * needs_tests:  => 0
  * milestone:  1.3 =>


Comment:

 Accepting the broad concept. However, this will require a lot of thought,
 because there are lots of compression tools, and they have different
 requirements. I'm fully in favor of adding a hook to make it easy to use
 these compressors, but we need to make sure the hook will actually do
 everything it needs to do.

 It's certainly not on the 1.3 milestone, though. It's a new feature for
 staticfiles, not a defect in the existing feature.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15218: USE_L10N, USE_I18N and DateTime Validation

2011-02-03 Thread Django

#15218: USE_L10N, USE_I18N and DateTime Validation
+---
   Reporter:  idle  | Owner:  nobody  
 Status:  closed| Milestone:  1.3 
  Component:  Internationalization  |   Version:  1.3-beta
 Resolution:  worksforme|  Keywords:  
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


Comment:

 Either I'm not understanding this report, or you are misunderstanding what
 is going on.

 USE_I18N only affects translations - i.e., does the admin show "Добавить
 object" or "Add new object"

 USE_L10N affects the formatting of data -- do you use commas or periods to
 separate decimals, date/time formats etc.

 If you have USE_L10N=False, date/times will always be presented in ISO
 format (i.e.,  2011-02-03 16:17:23). I've tested with 1.2.3, 1.2.X and
 trunk, and this displays and validates as expected.

 If you have USE_L10N=True, date/times will be displayed in locale-specific
 format. For the "ru" locale, this means 03.02.2011. Again, I've tested
 this with 1.2.3, 1.2.X and trunk, and dates display and validate as
 expected.

 If you don't have USE_L10N defined at all, it defaults to False, which
 means you don't get localizations.

 I can't see anything "weird" the behavior I'm seeing.

 If I've misunderstood this report, please reopen with describing what you
 are seeing, what you would expect to see, and why.

-- 
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] #15217: Cache setting deprecation warning is too aggressive

2011-02-03 Thread Django

#15217: Cache setting deprecation warning is too aggressive
+---
   Reporter:  adamv | Owner:  nobody 
 Status:  new   | Milestone:  1.3
  Component:  Cache system  |   Version:  SVN
 Resolution:|  Keywords:  blocker
   Triage Stage:  Accepted  | Has patch:  0  
Needs documentation:  0 |   Needs tests:  0  
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * milestone:  => 1.3
  * keywords:  => blocker
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted


Comment:

 Agreed that we shouldn't be raising an warning if the user hasn't done
 something that requires attention. This is a problem with a new feature,
 so it's a blocker.

-- 
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] #15216: list/set inconsistency breaks syncdb

2011-02-03 Thread Django

#15216: list/set inconsistency breaks syncdb
+---
   Reporter:  arthur@…  | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 1
  * stage:  Unreviewed => Accepted


Comment:

 The regressiontests/introspection tests contains tests for
 django_table_names(); tests for this case should be added.

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

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

Re: [Django] #15215: API for simpler (permission or any) checks for generic view classes

2011-02-03 Thread Django

#15215: API for simpler (permission or any) checks for generic view classes
--+-
   Reporter:  Ciantic | Owner:  nobody
 Status:  new | Milestone:
  Component:  Generic views   |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

  * stage:  Unreviewed => Design decision needed


Comment:

 I'm not convinced that this is exactly the right approach, but after using
 CBVs in action for a bit, I will grant the premise that it's unnecessarily
 difficult to add a login_required decorator to a CBV on the class itself.

 #14512 was an original swing at this with a specific solution aimed at
 making decorators work for class based views -- it turns out to be
 inherently complex to do so. The discussions related to that thread
 provide more detail ([http://groups.google.com/group/django-
 developers/browse_thread/thread/f4bad32127776177 thread 1]
 [http://groups.google.com/group/django-
 developers/browse_thread/thread/f36447f96277fe8c thread 2]).

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

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

47 matches

Mail list logo