Re: [Django] #13328: Cannot pickle a queryset with filter on field with callable default datetime.datetime.now

[Django]

#13328: Cannot pickle a queryset with filter on field with callable default
datetime.datetime.now
---+
  Reporter:  bkonkle   | Owner:  nobody 

Status:  new   | Milestone:  1.2

 Component:  Database layer (models, ORM)  |   Version:  1.2-beta   

Resolution:|  Keywords:  pickle, 
queryset, datetime__lte
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by vbabiy):

  * has_patch:  0 => 1

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

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

Re: [Django] #13328: Cannot pickle a queryset with filter on field with callable default datetime.datetime.now

[Django]

#13328: Cannot pickle a queryset with filter on field with callable default
datetime.datetime.now
---+
  Reporter:  bkonkle   | Owner:  nobody 

Status:  new   | Milestone:  1.2

 Component:  Database layer (models, ORM)  |   Version:  1.2-beta   

Resolution:|  Keywords:  pickle, 
queryset, datetime__lte
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by vbabiy):

 Here is my first go at a patch for Django.

 My thinking was that if you are serializing the queryset we can just
 remove the default off the datetime field to allow pickling the queryset.

-- 
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] #13334: Importing template tags from an egg fails

[Django]

#13334: Importing template tags from an egg fails
--+-
  Reporter:  joerg86  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ramiro):

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

Comment:

 See #9427 the third attachment there proposes even another idiom to
 differentiate between `ImportError`'s generated because a module doesn't
 exist and `ImportError`'s generated by the module itself but that unlike
 `imp.find_module()` is compatible with eggs.

-- 
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] #3349: If an ImportError occurs within some loaders a rather confusing exception is raised.

[Django]

#3349: If an ImportError occurs within some loaders a rather confusing exception
is raised.
+---
  Reporter:  Chris Wagner   | Owner:  nobody
Status:  closed | Milestone:  1.3   
 Component:  Template system|   Version:  SVN   
Resolution:  fixed  |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 This has been fixed in r12944. I now get:

 {{{
 ImportError at /view/

 No module named notthere

 Request Method: GET
 Request URL:http://localhost:8000/view/
 Django Version: 1.2 beta 1
 Exception Type: ImportError
 Exception Value:

 No module named notthere

 Exception Location: /home/r/r/dtest07/t3349/templatetags/tag_lib.py in
 , line 1
 }}}


 This ticket is three years old so IMHO it is safe to declare that the
 first release containing a fix for this is 1.2 without further backporting
 work needed.

-- 
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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by haras):

 After applying your patch to r12950
 to my unmodified revision (this without correcting ..admin problem)

 produces much less traceback, but still
 and no DEBUG = False, does not correct it for me

 {{{
 Validating models...
 Unhandled exception in thread started by 
 Traceback (most recent call last):
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/commands/runserver.py", line 48, in
 inner_run
 self.validate(display_num_errors=True)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/base.py", line 250, in validate
 num_errors = get_validation_errors(s, app)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/validation.py", line 28, in
 get_validation_errors
 for (app_name, error) in get_app_errors().items():
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 142, in get_app_errors
 self._populate()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 63, in _populate
 self.load_app(app_name)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 83, in load_app
 models = import_module('.models', app_name)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/utils/importlib.py", line 35, in import_module
 __import__(name)
   File
 
"/Users/haras/Source/WebApps/current/crm/srcOld/crm/payment/models/__init__.py",
 line 7, in 
 from crm.payment.models.payment import Payment
   File
 "/Users/haras/Source/WebApps/current/crm/srcOld/crm/payment/models/payment.py",
 line 12, in 
 from crm.contract.models.contract import Contract
   File
 
"/Users/haras/Source/WebApps/current/crm/srcOld/crm/contract/models/__init__.py",
 line 7, in 
 from crm.contract.models.contract import Contract
   File
 
"/Users/haras/Source/WebApps/current/crm/srcOld/crm/contract/models/contract.py",
 line 14, in 
 from crm.group.models.group import Group
   File
 "/Users/haras/Source/WebApps/current/crm/srcOld/crm/group/models/__init__.py",
 line 7, in 
 from crm.group.models.group import Group
   File
 "/Users/haras/Source/WebApps/current/crm/srcOld/crm/group/models/group.py",
 line 91, in 
 from ..admin import group
   File
 "/Users/haras/Source/WebApps/current/crm/srcOld/crm/group/admin/group.py",
 line 8, in 
 from crm.contract.models.contract import Contract
 ImportError: cannot import name Contract
 }}}

-- 
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] #13340: patch for updating postgis template script for ubuntu 10.04

[Django]

#13340: patch for updating postgis template script for ubuntu 10.04
+---
  Reporter:  nesk...@gmail.com  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by ramiro):

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

Comment:

 The current Debian stable release ships postgres 8.3 and postgis 1.3.3 and
 so the `/usr/share/postgresql-8.3-postgis` is the correct one to be used
 in the `create_template_postgis-debian.sh` script.

 Making things work in a straightforward way for Ubuntu users is a good
 thing but it shouldn't break thing for people that use the script on
 stabler distributions/releases,m for that you could contribute another
 separate script.

 Also, ideally it would me more robust than simply changing the path to the
 one used in the latest Ubuntu release. One possible approach would be to
 test for existence a sequence of paths corresponding to the postgis
 version as shipped wit all the officially supported Ubuntu releases, test
 them for existence one by one and setting the value of the
 `POSTGIS_SQL_PATH` variable to the one first found to be there. IMHO
 people using alpha/beta releases of a distribution are expected to cope
 with manually editing a shell 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-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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by haras):

 Replying to [comment:8 kmtracey]:
 > Not that it really matters, but why are your models modules importing
 admin modules? That's (part of) the crux of the problem that is leading to
 a circular import, and is generally not necessary. Admin modules are
 certainly dependent on the models, but the reverse dependence seems a bit
 unusual.

 in other case admin models are not visible in admin panel
 I partially solved circular import problem with importing admin model at
 the end of file with models, not at the beginning, it seems odd, but it
 works :}

 I have to admit that I forgot about method I use in models case, adding
 admin models imports to admin/__init__.py and then relaying on admin
 autodiscover,

 Yes this solves problem
 I removed all
 {{{ from ..admin import module }}}

 and it does not breaks at this revision anymore,
 moreover I updated to HEAD - most recent one, from svn and there is no
 longer any problem

 I have to apologize for posting this problem, but this revision breaks (or
 fixes) inappropriate method used by me

-- 
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] #13339: Date(Time)Field.to_python() fails to parse localized month names

[Django]

#13339: Date(Time)Field.to_python() fails to parse localized month names
---+
 Reporter:  UloPe  |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Forms  | Version:  1.1   
 Keywords:  i18n l10n  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Date(Time)Field.to_python() uses time.strptime to try and parse the input
 values.

 If the input string contains a localized month name (e.g. "Dezember" for
 December in German) validation fails. This probably is due to strptime
 relying on the current locale to parse month names.

 Test showing this behaviour is attached.

 (N.B.: I'm not really clear on why the reverse operation in
 formats.localize_input() works correctly)

-- 
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] #13315: Backwards-incompatible changes for GeoDjango not documented (e.g., PostGISAdaptor -> PostGISAdapter)

[Django]

#13315: Backwards-incompatible changes for GeoDjango not documented (e.g.,
PostGISAdaptor -> PostGISAdapter)
-+--
  Reporter:  bkonkle | Owner:  jbronn   
  
Status:  assigned| Milestone:  1.2  
  
 Component:  GIS |   Version:  1.2-beta 
  
Resolution:  |  Keywords:  geodjango, gis, 
postgis, PostGISAdaptor
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  1   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Comment (by Alex):

 Justin, can you add a note to the backwards compatibility timeline doc, so
 we can (amongst other things) remember when to remove these aliases.

-- 
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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by haras):

 sample case I use my models
 I hope this would help to solve problem


 module crm.customer.models.country
 {{{
 """
   Mateusz Harasymczuk
   mate...@harasymczuk.pl
   www.mateusz.harasymczuk.pl
 """


 from django.db import models
 from django.utils.translation import ugettext as _
 from ..helpers import address_unify
 from ..helpers import string_unify
 from country import Country

 DEFAULT_COUNTRY = 1

 class Document ( models.Model ):
   name = models.CharField( unique=True, max_length=20, verbose_name=_(
 'Name' ) )
   country = models.ForeignKey( Country, verbose_name=_( 'Country' ),
 default=DEFAULT_COUNTRY )
   comment = models.TextField( verbose_name=_( 'Comment' ), unique=False,
 null=True, blank=True )
   def __unicode__( self ): return '%s (%s)' % ( _( self.name ), _(
 self.country.name ) )
   class Meta ():
 ordering = ( 'name', )
 verbose_name = _( 'Document' )
 verbose_name_plural = _( 'Documents' )
 app_label = 'customer'

 from ..admin import document
 }}}


 module crm.customer.admin.document
 {{{
 from django.contrib import admin
 from ..models.country import Country


 class CountryAdmin ( admin.ModelAdmin ):
   list_select_related = True
   search_fields = ['name', 'iso_alpha_2', 'iso_alpha_3']
   list_display = ( 'continent', 'name', 'iso_alpha_2', 'iso_alpha_3' )
   list_display_links = ( 'name', )
   list_filter = ( 'continent', )

 admin.site.register( Country, CountryAdmin )
 }}}

-- 
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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:5 haras]:
 > sample case I use my models
 > I hope this would help to solve problem

 I don't need partial sample code, I've already recreated the basic problem
 evident in the traceback from the description. What I did not recreate was
 a project containing at least six different apps, interdependent in ways I
 cannot necessarily see from the traceback. The easiest way to see if the
 attached fix corrects the problem in your specific case is for you to try
 it out. I believe it will fix the problem, but it's clear your project is
 pretty extensive, and it's hard to be 100% sure that there is not
 something else in how you have things set up that is going to cause an
 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-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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:6 haras]:
 > I pasted wrong code, this is ok
 > but you can see, all my models are importing its own admin module from
 file which is located in ../admin/ directory
 > (models are in model dir, admin files in admin dir, views in views dir,
 and so on...)
 >

 Not that it really matters, but why are your models modules importing
 admin modules? That's (part of) the crux of the problem that is leading to
 a circular import, and is generally not necessary. Admin modules are
 certainly dependent on the models, but the reverse dependence seems a bit
 unusual.

-- 
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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by haras):

 I pasted wrong code, this is ok
 but you can see, all my models are importing its own admin module from
 file which is located in ../admin/ directory
 (models are in model dir, admin files in admin dir, views in views dir,
 and so on...)

 crm.contract.admin.document
 {{{
 from django.contrib import admin
 from ..models.document import Document
 import settings



 class DocumentAdmin ( admin.ModelAdmin ):
   class Media():
 #js = ( settings.MEDIA_URL + '/js/crm/contract.js', )
 css = { 'all': ( settings.MEDIA_URL + '/css/crm/contract/admin.css', )
 }

   list_select_related = True
   search_fields = ['name', 'type']
   list_display = ( 'name', 'type', 'sample_view' )
   list_display_links = ( 'name', )

 admin.site.register( Document, DocumentAdmin )
 }}}

-- 
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] #13340: patch for updating postgis template script for ubuntu 10.04

[Django]

#13340: patch for updating postgis template script for ubuntu 10.04
---+
 Reporter:  nesk...@gmail.com  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://geodjango.org/docs/create_template_postgis-debian.sh
 it probably works on debian too...

-- 
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] #13227: Query cloning fails with models having Lock as instance member

[Django]

#13227: Query cloning fails with models having Lock as instance member
---+
  Reporter:  claudep   | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by claudep):

 Thanks Russell, it's fine now!

-- 
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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  0 => 1
  * milestone:  => 1.2

Comment:

 Possible fix attached. It fixes the problem for the scenario I came up
 with; I'd like to confirm it fixes the problem for the more complicated
 original scenario. Does not yet integrate 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-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] #13315: Backwards-incompatible changes for GeoDjango not documented (e.g., PostGISAdaptor -> PostGISAdapter)

[Django]

#13315: Backwards-incompatible changes for GeoDjango not documented (e.g.,
PostGISAdaptor -> PostGISAdapter)
-+--
  Reporter:  bkonkle | Owner:  jbronn   
  
Status:  assigned| Milestone:  1.2  
  
 Component:  GIS |   Version:  1.2-beta 
  
Resolution:  |  Keywords:  geodjango, gis, 
postgis, PostGISAdaptor
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  1   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by jbronn):

  * needs_docs:  0 => 1

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

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

Re: [Django] #13338: adding custom template context processor(s) to settings.py screws up admin

[Django]

#13338: adding custom template context processor(s) to settings.py screws up 
admin
-+--
  Reporter:  marshall@gmail.com  | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  Template system |   Version:  1.1  
 
Resolution:  invalid |  Keywords:  template context 
processor
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Comment:

 Trac is not for asking support questions, please use #django or the
 django-users mailing list.  For the record this isn't a bug, when you set
 TEMPLATE_CONTEXT_PROCESSORS you aren't adding to the defaults, you're
 overiding them, so you need to add the defaults in.

-- 
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] #13338: adding custom template context processor(s) to settings.py screws up admin

[Django]

#13338: adding custom template context processor(s) to settings.py screws up 
admin
+---
 Reporter:  marshall@gmail.com  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Template system | Version:  1.1   
 Keywords:  template context processor  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I added my own template context processor:

 {{{
 TEMPLATE_CONTEXT_PROCESSORS = (
 'www.context_processor.static_url',
 )
 }}}

 and the admin system stopped receiving its context and I got
 TemplateSyntaxErrors. It worked again when I added:


 {{{
 TEMPLATE_CONTEXT_PROCESSORS = (
 'www.context_processor.static_url',
 'django.core.context_processors.auth',
 )
 }}}

 is there a reason I have to manually add the context processor for auth
 after creating a custom processor? A user in #django told me to add the
 following:


 {{{
 from django.conf.global_settings import TEMPLATE_CONTEXT_PROCESSORS
 }}}

 to the top of my settings.py, I did that and added my template context
 processor using:


 {{{
 TEMPLATE_CONTEXT_PROCESSORS += (
 'www.context_processor.static_url',
 )
 }}}

 which seems to have worked. What's going on? Is this the way it's supposed
 to be or have I done something I'm not supposed to?

-- 
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] #12691: ModelForms documentation missing versionadded tag for 'widgets'

[Django]

#12691: ModelForms documentation missing versionadded tag for 'widgets'
+---
  Reporter:  danielr| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * milestone:  => 1.2

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

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

[Django] #13337: multiple installations in wsgi_embedded mode

[Django]

#13337: multiple installations in wsgi_embedded mode
---+
 Reporter:  canburak   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 deployment/modwsgi documentation may include a pointer to
 
"http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Timezone_and_Locale_Settings";
 by suggesting to use the daemon mode if same server is to serve different
 applications in multiple timezones

-- 
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] #12903: Missing plural forms in admin

[Django]

#12903: Missing plural forms in admin
---+
  Reporter:  stephaner | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Fixed in [12968].

-- 
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] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
---+
  Reporter:  jacob | Owner:  dcramer 
Status:  assigned  | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  database
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by chouquette):

 * cc: chouquette (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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 OK, I figured out a simpler scenario to trigger the problem. Given one
 app, `blah`, with a models directory containing `__init__.py`:

 {{{
 #!python
 from blah.models.bar import Bar
 from blah.models.foo import Foo

 __all__ = ['Foo', 'Bar']
 }}}

 `blah/models/bar.py`:
 {{{
 #!python
 from django.db import models

 from ..admin import foo
 class Bar(models.Model):
 name = models.CharField(max_length=5)
 class Meta:
 app_label = 'blah'

 }}}

 `blah/models/foo.py`:
 {{{
 #!python
 from django.db import models

 class Foo(models.Model):
 name = models.CharField(max_length=5)
 class Meta:
 app_label = 'blah'

 }}}

 The `blah` app also has an admin directory containing `foo.py`:

 {{{
 #!python
 from django.contrib import admin
 from blah.models.foo import Foo
 admin.site.register(Foo)
 }}}

 Plus another app listed in `INSTALLED_APPS`, `blahblah`, with a simple
 `models.py`:

 {{{
 #!python
 from blah.models.bar import Bar
 }}}

 Loading the blah app starts with an import of Bar from the
 `blah/models/__init__.py` file. Before Bar is defined, the admin module
 for Foo is imported, triggering registration of Foo. With debug on, this
 results in a call to the admin validation code, which first attempts to
 ensure that all apps and models are fully loaded. This leads to an attempt
 to load the `blahblah` models file, which since it attempts to import Bar
 (where we started), results in an !ImportError.

 Setting DEBUG to False makes the problem go away, since then we don't have
 an attempt to ensure all all models are fully loaded while we are in-
 process of importing a model. Also, moving the admin import in `bar.py`
 __after__ the definition of Bar fixes the problem. Finally this scenario
 does also fail on Django 1.0.4:

 {{{
 k...@lbox:~/software/web/foo$ python manage.py shell
 Traceback (most recent call last):
   File "manage.py", line 11, in 
 execute_manager(settings)
   File "/home/kmt/django/Django-1.0.4/django/core/management/__init__.py",
 line 361, in execute_manager
 utility.execute()
   File "/home/kmt/django/Django-1.0.4/django/core/management/__init__.py",
 line 306, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/kmt/django/Django-1.0.4/django/core/management/base.py",
 line 192, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/kmt/django/Django-1.0.4/django/core/management/base.py",
 line 219, in execute
 output = self.handle(*args, **options)
   File "/home/kmt/django/Django-1.0.4/django/core/management/base.py",
 line 348, in handle
 return self.handle_noargs(**options)
   File
 "/home/kmt/django/Django-1.0.4/django/core/management/commands/shell.py",
 line 18, in handle_noargs
 loaded_models = get_models()
   File "/home/kmt/django/Django-1.0.4/django/db/models/loading.py", line
 136, in get_models
 self._populate()
   File "/home/kmt/django/Django-1.0.4/django/db/models/loading.py", line
 57, in _populate
 self.load_app(app_name, True)
   File "/home/kmt/django/Django-1.0.4/django/db/models/loading.py", line
 72, in load_app
 mod = __import__(app_name, {}, {}, ['models'])
   File "/home/kmt/software/web/foo/blah/models/__init__.py", line 1, in
 
 from blah.models.bar import Bar
   File "/home/kmt/software/web/foo/blah/models/bar.py", line 3, in
 
 from ..admin import foo
   File "/home/kmt/software/web/foo/blah/admin/foo.py", line 5, in 
 admin.site.register(Foo)
   File "/home/kmt/django/Django-1.0.4/django/contrib/admin/sites.py", line
 77, in register
 validate(admin_class, model)
   File "/home/kmt/django/Django-1.0.4/django/contrib/admin/validation.py",
 line 22, in validate
 models.get_apps()
   File "/home/kmt/django/Django-1.0.4/django/db/models/loading.py", line
 97, in get_apps
 self._populate()
   File "/home/kmt/django/Django-1.0.4/django/db/models/loading.py", line
 57, in _populate
 self.load_app(app_name, True)
   File "/home/kmt/django/Django-1.0.4/django/db/models/loading.py", line
 72, in load_app
 mod = __import__(app_name, {}, {}, ['models'])
   File "/home/kmt/software/web/foo/blahblah/models.py", line 1, in
 
 from blah.models.bar import Bar
 Import

[Changeset] r12970 - in django/trunk: django/db/models tests/regressiontests/queries

[noreply]

Author: russellm
Date: 2010-04-13 10:18:10 -0500 (Tue, 13 Apr 2010)
New Revision: 12970

Modified:
   django/trunk/django/db/models/query.py
   django/trunk/tests/regressiontests/queries/tests.py
Log:
Fixed #13227 -- Ensure that the query cache is flushed when a QuerySet is 
deepcopied, avoiding problems when an evaluated queryset is used as a subquery. 
Thanks to claudep for the report.

Modified: django/trunk/django/db/models/query.py
===
--- django/trunk/django/db/models/query.py  2010-04-13 10:29:44 UTC (rev 
12969)
+++ django/trunk/django/db/models/query.py  2010-04-13 15:18:10 UTC (rev 
12970)
@@ -45,11 +45,12 @@
 """
 Deep copy of a QuerySet doesn't populate the cache
 """
-obj_dict = deepcopy(self.__dict__, memo)
-obj_dict['_iter'] = None
-
 obj = self.__class__()
-obj.__dict__.update(obj_dict)
+for k,v in self.__dict__.items():
+if k in ('_iter','_result_cache'):
+obj.__dict__[k] = None
+else:
+obj.__dict__[k] = deepcopy(v, memo)
 return obj
 
 def __getstate__(self):

Modified: django/trunk/tests/regressiontests/queries/tests.py
===
--- django/trunk/tests/regressiontests/queries/tests.py 2010-04-13 10:29:44 UTC 
(rev 12969)
+++ django/trunk/tests/regressiontests/queries/tests.py 2010-04-13 15:18:10 UTC 
(rev 12970)
@@ -4,7 +4,7 @@
 from django.db.models import Count
 from django.test import TestCase
 
-from models import Tag, Annotation, DumbCategory
+from models import Tag, Annotation, DumbCategory, Note, ExtraInfo
 
 class QuerysetOrderedTests(unittest.TestCase):
 """
@@ -63,3 +63,21 @@
 # This prevents us from even evaluating this test case at all.
 # Refs #10099
 
self.assertFalse(connections[DEFAULT_DB_ALIAS].features.allow_sliced_subqueries)
+
+class CloneTests(TestCase):
+def test_evaluated_queryset_as_argument(self):
+"#13227 -- If a queryset is already evaluated, it can still be used as 
a query arg"
+n = Note(note='Test1', misc='misc')
+n.save()
+e = ExtraInfo(info='good', note=n)
+e.save()
+
+n_list = Note.objects.all()
+# Evaluate the Note queryset, populating the query cache
+list(n_list)
+# Use the note queryset in a query, and evalute
+# that query in a way that involves cloning.
+try:
+
self.assertEquals(ExtraInfo.objects.filter(note__in=n_list)[0].info, 'good')
+except:
+self.fail('Query should be clonable')

-- 
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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 I'd also be interested to know if turning off DEBUG makes the problem go
 away. Is it just the admin validation triggering the issue or is there a
 problem even without that? If the latter, the traceback from the DEBUG off
 case might help with recreating a simpler scenario to demonstrate the
 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] #13336: Document example for setting HttpResponse headers is misleading because it users wrong cache header

[Django]

#13336: Document example for setting HttpResponse headers is misleading because 
it
users wrong cache header
---+
 Reporter:  dnjuls |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords:  cache reponse headers  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In the HttpReponse documentation (http://docs.djangoproject.com/en/dev/ref
 /request-response/#django.http.HttpResponse) exists and example for
 setting headers in for the HttpResponse object.

 The header used in the example response['Pragma'] = 'no-cache'

 This header is intended for use in requests, not responses. See
 http://en.wikipedia.org/wiki/List_of_HTTP_headers#Avoiding_caching
 Better use Cache-Control: no-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-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] #13335: Revision 12950 crashes complex interdependent models in directory

[Django]

#13335: Revision 12950 crashes complex interdependent models in directory
---+
  Reporter:  haras | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * needs_better_patch:  => 0
  * summary:  Revision 12950 crashes models in directory => Revision 12950
  crashes complex interdependent models in
  directory
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This is a bit more complicated than "models in a directory" not working
 after r12950. Models in a directory do still work, what isn't working is
 this particular case, which from the traceback involves the models modules
 importing admin modules, triggering admin registration, which is
 triggering admin validation, which in turn triggers more app loading, more
 model imports, more admin imports and registrations, more validation,
 until a point is reached where we try to import something that we're still
 in the process of importing. Netting down the trace, what we've got is:

 {{{
 self.load_app(app_name, True)
 from crm.contract.models.contract import Contract
 from crm.date.models.season import Season
 from crm.date.models.month import Month
 from ..admin import month
 admin.site.register( Month )
 validate(admin_class, model)
 self.load_app(app_name, True)
 from crm.customer.models.country import Country
 from ..admin import country
 admin.site.register( Country, CountryAdmin )
 validate(admin_class, model)
 self.load_app(app_name, True)
 from crm.group.models.group import Group
 from crm.date.helpers.default_season import default_season
 from ..models.season import Season
 from ..admin import season
 admin.site.register( Season, SeasonAdmin )
 validate(admin_class, model)
 self.load_app(app_name, True)
 from crm.feedback.models.feedback import Feedback
 from category import Category
 from ..admin import category
 admin.site.register( Category, CategoryAdmin )
 validate(admin_class, model)
 self.load_app(app_name, True)
 from crm.payment.models.payment import Payment
 from crm.contract.models.contract import Contract
 }}}

 That last one is triggering an !ImportError because we are already in the
 process of importing Contract way up top. Prior to r12950 that import
 error would be suppressed. Now it's not.

 Trying to come up with a somewhat simpler scenario to recreate the issue,
 but haven't managed to do that yet. I'd be interested to know if this case
 worked on Django 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-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] #13335: Revision 12950 crashes models in directory

[Django]

#13335: Revision 12950 crashes models in directory
--+-
 Reporter:  haras |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 my project is to big to hold models in one file
 I am using models in directory structure

 apps/
  - myapp/
  -- admin/
  -- models/
  -- views/
 ...etc
 I did this from this post
 http://www.acooke.org/cute/UsingaDire0.html
 and it worked for very long time

 Revision 12950 breaks it!
 http://code.djangoproject.com/changeset/12950
 exactly loading.py throw unhanded exception

 If I downgrade to 12949 it is ok




 traceback after upgrade to 12950

 {{{
 > python manage.py shell
 Traceback (most recent call last):
   File "manage.py", line 11, in 
 execute_manager( settings )
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/__init__.py", line 438, in
 execute_manager
 utility.execute()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/__init__.py", line 379, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/base.py", line 196, in run_from_argv
 self.execute(*args, **options.__dict__)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/base.py", line 223, in execute
 output = self.handle(*args, **options)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/base.py", line 352, in handle
 return self.handle_noargs(**options)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/core/management/commands/shell.py", line 18, in
 handle_noargs
 loaded_models = get_models()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 156, in get_models
 self._populate()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 60, in _populate
 self.load_app(app_name, True)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 87, in load_app
 models = import_module('.models', app_name)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/utils/importlib.py", line 35, in import_module
 __import__(name)
   File
 "/Users/haras/Source/WebApps/current/crm/src/crm/contract/models/__init__.py",
 line 7, in 
 from crm.contract.models.contract import Contract
   File
 "/Users/haras/Source/WebApps/current/crm/src/crm/contract/models/contract.py",
 line 12, in 
 from crm.date.models.season import Season
   File
 "/Users/haras/Source/WebApps/current/crm/src/crm/date/models/__init__.py",
 line 7, in 
 from crm.date.models.month import Month
   File
 "/Users/haras/Source/WebApps/current/crm/src/crm/date/models/month.py",
 line 26, in 
 from ..admin import month
   File
 "/Users/haras/Source/WebApps/current/crm/src/crm/date/admin/month.py",
 line 10, in 
 admin.site.register( Month )
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/contrib/admin/sites.py", line 94, in register
 validate(admin_class, model)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/contrib/admin/validation.py", line 20, in validate
 models.get_apps()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 104, in get_apps
 self._populate()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 60, in _populate
 self.load_app(app_name, True)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/db/models/loading.py", line 87, in load_app
 models = import_module('.models', app_name)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/django/utils/importlib.py", line 35, in import_module
 __import__(name)
   File
 "/Users/haras/Source/WebApps/current/crm/src/crm/customer/models/__init__.py",
 line 7, in 
 from crm.customer.mod

[Django] #13334: Importing template tags from an egg fails

[Django]

#13334: Importing template tags from an egg fails
-+--
 Reporter:  joerg86  |   Owner:  nobody
   Status:  new  |   Milestone:  1.2   
Component:  Template system  | Version:  SVN   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Hi,

 it seems that from r12944, django cannot deal with template tags and
 filters imported from egg files. I ran into this as I tried to use sorl-
 thumbnail 3.2.5 - django gives me a template syntax error saying the
 "thumbnail" template tag couldn't be found in
 sorl.thumbnail.templatetags.thumbnail and others.
 If I put the same module uncompressed in my pythonpath, everything works.

 Thanks for fixing it,

 Jörg

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

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

[Changeset] r12969 - in django/trunk: django/contrib/admin/media/js docs/internals

[noreply]

Author: jezdez
Date: 2010-04-13 05:29:44 -0500 (Tue, 13 Apr 2010)
New Revision: 12969

Modified:
   django/trunk/django/contrib/admin/media/js/compress.py
   django/trunk/docs/internals/contributing.txt
Log:
Fixed #13290 - Added a section about minification of admin JavaScript files to 
the contributing docs. Thanks to Gabriel Hurley for the report and patch.

Modified: django/trunk/django/contrib/admin/media/js/compress.py
===
--- django/trunk/django/contrib/admin/media/js/compress.py  2010-04-13 
10:29:19 UTC (rev 12968)
+++ django/trunk/django/contrib/admin/media/js/compress.py  2010-04-13 
10:29:44 UTC (rev 12969)
@@ -9,10 +9,11 @@
 def main():
 usage = "usage: %prog [file1..fileN]"
 description = """With no file paths given this script will automatically
-compress all jQuery based files of the admin app."""
+compress all jQuery-based files of the admin app. Requires the Google Closure
+Compiler library and Java version 6 or later."""
 parser = optparse.OptionParser(usage, description=description)
 parser.add_option("-c", dest="compiler", default="~/bin/compiler.jar",
-  help="path to closure compiler jar file")
+  help="path to Closure Compiler jar file")
 parser.add_option("-v", "--verbose",
   action="store_true", dest="verbose")
 parser.add_option("-q", "--quiet",
@@ -21,7 +22,7 @@
 
 compiler = os.path.expanduser(options.compiler)
 if not os.path.exists(compiler):
-sys.exit("Closure compiler jar file %s not found. Please use the -c 
option to specify the path." % compiler)
+sys.exit("Google Closure compiler jar file %s not found. Please use 
the -c option to specify the path." % compiler)
 
 if not args:
 if options.verbose:

Modified: django/trunk/docs/internals/contributing.txt
===
--- django/trunk/docs/internals/contributing.txt2010-04-13 10:29:19 UTC 
(rev 12968)
+++ django/trunk/docs/internals/contributing.txt2010-04-13 10:29:44 UTC 
(rev 12969)
@@ -433,6 +433,44 @@
 
 .. _Django i18n mailing list: http://groups.google.com/group/django-i18n/
 
+Submitting javascript patches
+=
+
+.. versionadded:: 1.2
+
+Django's admin system leverages the jQuery framework to increase the
+capabilities of the admin interface. In conjunction, there is an emphasis on
+admin javascript performance and minimizing overall admin media file size.
+Serving compressed or "minified" versions of javascript files is considered
+best practice in this regard.
+
+To that end, patches for javascript files should include both the original
+code for future development (e.g. "foo.js"), and a compressed version for
+production use (e.g. "foo.min.js"). Any links to the file in the codebase
+should point to the compressed version.
+
+To simplify the process of providing optimized javascript code, Django
+includes a handy script which should be used to create a "minified" version.
+This script is located at ``/contrib/admin/media/js/compress.py``.
+
+Behind the scenes, ``compress.py`` is a front-end for Google's
+`Closure Compiler`_ which is written in Java. However, the Closure Compiler
+library is not bundled with Django directly, so those wishing to contribute
+complete javascript patches will need to download and install the library
+independently.
+
+The Closure Compiler library requires Java version 6 or higher (Java 1.6 or
+higher on Mac OS X). Note that Mac OS X 10.5 and earlier did not ship with Java
+1.6 by default, so it may be necessary to upgrade your Java installation before
+the tool will be functional. Also note that even after upgrading Java, the
+default `/usr/bin/java` command may remain linked to the previous Java
+binary, so relinking that command may be necessary as well.
+
+Please don't forget to run ``compress.py`` and include the ``diff`` of the
+minified scripts when submitting patches for Django's javascript.
+
+.. _Closure Compiler: http://code.google.com/closure/compiler/
+
 Django conventions
 ==
 

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

[Changeset] r12968 - in django/trunk: django/contrib/admin django/contrib/admin/media/js django/contrib/admin/templates/admin tests/regressiontests/admin_views

[noreply]

Author: jezdez
Date: 2010-04-13 05:29:19 -0500 (Tue, 13 Apr 2010)
New Revision: 12968

Modified:
   django/trunk/django/contrib/admin/media/js/actions.js
   django/trunk/django/contrib/admin/media/js/actions.min.js
   django/trunk/django/contrib/admin/options.py
   django/trunk/django/contrib/admin/templates/admin/actions.html
   django/trunk/django/contrib/admin/templates/admin/change_list.html
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #12903 - Made translating the admin action selection text easier. Thanks 
to Ramiro Morales for the patch.

Modified: django/trunk/django/contrib/admin/media/js/actions.js
===
--- django/trunk/django/contrib/admin/media/js/actions.js   2010-04-13 
10:28:44 UTC (rev 12967)
+++ django/trunk/django/contrib/admin/media/js/actions.js   2010-04-13 
10:29:19 UTC (rev 12968)
@@ -12,17 +12,21 @@

.parent().parent().toggleClass(options.selectedClass, checked);
}
updateCounter = function() {
-   var count = 
$(actionCheckboxes).filter(":checked").length;
-   $("span._acnt").html(count);
+   var sel = $(actionCheckboxes).filter(":checked").length;
+   $(options.counterContainer).html(interpolate(
+   ngettext('%(sel)s of %(cnt)s selected', '%(sel)s of 
%(cnt)s selected', sel), {
+   sel: sel,
+   cnt: _actions_icnt
+   }, true));
$(options.allToggle).attr("checked", function() {
-   if (count == actionCheckboxes.length) {
+   if (sel == actionCheckboxes.length) {
value = true;
showQuestion();
} else {
value = false;
clearAcross();
}
-   return value
+   return value;
});
}
showQuestion = function() {

Modified: django/trunk/django/contrib/admin/media/js/actions.min.js
===
--- django/trunk/django/contrib/admin/media/js/actions.min.js   2010-04-13 
10:28:44 UTC (rev 12967)
+++ django/trunk/django/contrib/admin/media/js/actions.min.js   2010-04-13 
10:29:19 UTC (rev 12968)
@@ -1,5 +1,5 @@
-(function(a){a.fn.actions=function(g){var 
b=a.extend({},a.fn.actions.defaults,g),e=a(this);checker=function(c){c?showQuestion():reset();a(e).attr("checked",c).parent().parent().toggleClass(b.selectedClass,c)};updateCounter=function(){var
 
c=a(e).filter(":checked").length;a("span._acnt").html(c);a(b.allToggle).attr("checked",function(){if(c==e.length){value=true;showQuestion()}else{value=false;clearAcross()}return
 
value})};showQuestion=function(){a(b.acrossClears).hide();a(b.acrossQuestions).show();
-a(b.allContainer).hide()};showClear=function(){a(b.acrossClears).show();a(b.acrossQuestions).hide();a(b.actionContainer).toggleClass(b.selectedClass);a(b.allContainer).show();a(b.counterContainer).hide()};reset=function(){a(b.acrossClears).hide();a(b.acrossQuestions).hide();a(b.allContainer).hide();a(b.counterContainer).show()};clearAcross=function(){reset();a(b.acrossInput).val(0);a(b.actionContainer).removeClass(b.selectedClass)};a(b.counterContainer).show();a(this).filter(":checked").each(function(){a(this).parent().parent().toggleClass(b.selectedClass);
-updateCounter();a(b.acrossInput).val()==1&&showClear()});a(b.allToggle).show().click(function(){checker(a(this).attr("checked"));updateCounter()});a("div.actions
 span.question 
a").click(function(c){c.preventDefault();a(b.acrossInput).val(1);showClear()});a("div.actions
 span.clear 
a").click(function(c){c.preventDefault();a(b.allToggle).attr("checked",false);clearAcross();checker(0);updateCounter()});lastChecked=null;a(e).click(function(c){if(!c)c=window.event;var
 d=c.target?c.target:c.srcElement;if(lastChecked&&
-a.data(lastChecked)!=a.data(d)&&c.shiftKey==true){var 
f=false;a(lastChecked).attr("checked",d.checked).parent().parent().toggleClass(b.selectedClass,d.checked);a(e).each(function(){if(a.data(this)==a.data(lastChecked)||a.data(this)==a.data(d))f=f?false:true;f&&a(this).attr("checked",d.checked).parent().parent().toggleClass(b.selectedClass,d.checked)})}a(d).parent().parent().toggleClass(b.selectedClass,d.checked);lastChecked=d;updateCounter()})};a.fn.actions.defaults={actionContainer:"div.actions",
-counterContainer:"span.action-counter",allContainer:"div.actions 
span.all",acrossInput:"div.actions 
input.select-across",acrossQuestions:"div.actions 
span.question",acrossClears:"div.actions 
span.clear",allToggle:"#action-toggle",sele

[Changeset] r12967 - in django/trunk/django/contrib/admin: . media/js

[noreply]

Author: jezdez
Date: 2010-04-13 05:28:44 -0500 (Tue, 13 Apr 2010)
New Revision: 12967

Added:
   django/trunk/django/contrib/admin/media/js/prepopulate.min.js
Modified:
   django/trunk/django/contrib/admin/media/js/compress.py
   django/trunk/django/contrib/admin/options.py
Log:
Also minify the JavaScript file for pre-populated form fields in the admin.

Modified: django/trunk/django/contrib/admin/media/js/compress.py
===
--- django/trunk/django/contrib/admin/media/js/compress.py  2010-04-13 
10:28:24 UTC (rev 12966)
+++ django/trunk/django/contrib/admin/media/js/compress.py  2010-04-13 
10:28:44 UTC (rev 12967)
@@ -21,12 +21,13 @@
 
 compiler = os.path.expanduser(options.compiler)
 if not os.path.exists(compiler):
-sys.exit("Compiler jar file %s not found. Please use the -c option to 
specify the path." % compiler)
+sys.exit("Closure compiler jar file %s not found. Please use the -c 
option to specify the path." % compiler)
 
 if not args:
 if options.verbose:
 sys.stdout.write("No filenames given; defaulting to admin 
scripts\n")
-args = [os.path.join(here, f) for f in ["actions.js", "collapse.js", 
"inlines.js"]]
+args = [os.path.join(here, f) for f in [
+"actions.js", "collapse.js", "inlines.js", "prepopulate.js"]]
 
 for arg in args:
 if not arg.endswith(".js"):

Added: django/trunk/django/contrib/admin/media/js/prepopulate.min.js
===
--- django/trunk/django/contrib/admin/media/js/prepopulate.min.js   
(rev 0)
+++ django/trunk/django/contrib/admin/media/js/prepopulate.min.js   
2010-04-13 10:28:44 UTC (rev 12967)
@@ -0,0 +1 @@
+(function(b){b.fn.prepopulate=function(d,f){return this.each(function(){var 
a=b(this);a.data("_changed",false);a.change(function(){a.data("_changed",true)});var
 c=function(){if(a.data("_changed")!=true){var 
e=[];d.each(function(){b(this).val().length>0&&e.push(b(this).val())});a.val(URLify(e.join("
 "),f))}};d.keyup(c).change(c).focus(c)})}})(django.jQuery);

Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2010-04-13 10:28:24 UTC 
(rev 12966)
+++ django/trunk/django/contrib/admin/options.py2010-04-13 10:28:44 UTC 
(rev 12967)
@@ -274,7 +274,7 @@
 js.extend(['js/jquery.min.js', 'js/jquery.init.js', 
'js/actions.min.js'])
 if self.prepopulated_fields:
 js.append('js/urlify.js')
-js.append('js/prepopulate.js')
+js.append('js/prepopulate.min.js')
 if self.opts.get_ordered_objects():
 js.extend(['js/getElementsBySelector.js', 'js/dom-drag.js' , 
'js/admin/ordering.js'])
 
@@ -1202,7 +1202,7 @@
 js = ['js/jquery.min.js', 'js/jquery.init.js', 'js/inlines.min.js']
 if self.prepopulated_fields:
 js.append('js/urlify.js')
-js.append('js/prepopulate.js')
+js.append('js/prepopulate.min.js')
 if self.filter_vertical or self.filter_horizontal:
 js.extend(['js/SelectBox.js' , 'js/SelectFilter2.js'])
 return forms.Media(js=['%s%s' % (settings.ADMIN_MEDIA_PREFIX, url) for 
url in js])

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

[Changeset] r12966 - in django/trunk/django/contrib/admin: . media/js templates/admin templates/admin/edit_inline

[noreply]

Author: jezdez
Date: 2010-04-13 05:28:24 -0500 (Tue, 13 Apr 2010)
New Revision: 12966

Added:
   django/trunk/django/contrib/admin/media/js/jquery.init.js
Modified:
   django/trunk/django/contrib/admin/helpers.py
   django/trunk/django/contrib/admin/media/js/actions.js
   django/trunk/django/contrib/admin/media/js/actions.min.js
   django/trunk/django/contrib/admin/media/js/collapse.js
   django/trunk/django/contrib/admin/media/js/collapse.min.js
   django/trunk/django/contrib/admin/media/js/inlines.js
   django/trunk/django/contrib/admin/media/js/inlines.min.js
   django/trunk/django/contrib/admin/media/js/prepopulate.js
   django/trunk/django/contrib/admin/options.py
   django/trunk/django/contrib/admin/templates/admin/change_list.html
   django/trunk/django/contrib/admin/templates/admin/edit_inline/stacked.html
   django/trunk/django/contrib/admin/templates/admin/edit_inline/tabular.html
   django/trunk/django/contrib/admin/templates/admin/prepopulated_fields_js.html
Log:
Fixed #12882 - Moved the admin's jQuery into our own namespace to lower the 
risk of a clash with third party apps that use jQuery.

Modified: django/trunk/django/contrib/admin/helpers.py
===
--- django/trunk/django/contrib/admin/helpers.py2010-04-13 02:43:03 UTC 
(rev 12965)
+++ django/trunk/django/contrib/admin/helpers.py2010-04-13 10:28:24 UTC 
(rev 12966)
@@ -76,7 +76,8 @@
 
 def _media(self):
 if 'collapse' in self.classes:
-return forms.Media(js=['%sjs/collapse.min.js' % 
settings.ADMIN_MEDIA_PREFIX])
+js = ['js/jquery.min.js', 'js/jquery.init.js', 
'js/collapse.min.js']
+return forms.Media(js=['%s%s' % (settings.ADMIN_MEDIA_PREFIX, url) 
for url in js])
 return forms.Media()
 media = property(_media)
 

Modified: django/trunk/django/contrib/admin/media/js/actions.js
===
--- django/trunk/django/contrib/admin/media/js/actions.js   2010-04-13 
02:43:03 UTC (rev 12965)
+++ django/trunk/django/contrib/admin/media/js/actions.js   2010-04-13 
10:28:24 UTC (rev 12966)
@@ -108,4 +108,4 @@
allToggle: "#action-toggle",
selectedClass: "selected"
}
-})(jQuery);
+})(django.jQuery);

Modified: django/trunk/django/contrib/admin/media/js/actions.min.js
===
--- django/trunk/django/contrib/admin/media/js/actions.min.js   2010-04-13 
02:43:03 UTC (rev 12965)
+++ django/trunk/django/contrib/admin/media/js/actions.min.js   2010-04-13 
10:28:24 UTC (rev 12966)
@@ -2,4 +2,4 @@
 
a(b.allContainer).hide()};showClear=function(){a(b.acrossClears).show();a(b.acrossQuestions).hide();a(b.actionContainer).toggleClass(b.selectedClass);a(b.allContainer).show();a(b.counterContainer).hide()};reset=function(){a(b.acrossClears).hide();a(b.acrossQuestions).hide();a(b.allContainer).hide();a(b.counterContainer).show()};clearAcross=function(){reset();a(b.acrossInput).val(0);a(b.actionContainer).removeClass(b.selectedClass)};a(b.counterContainer).show();a(this).filter(":checked").each(function(){a(this).parent().parent().toggleClass(b.selectedClass);
 
updateCounter();a(b.acrossInput).val()==1&&showClear()});a(b.allToggle).show().click(function(){checker(a(this).attr("checked"));updateCounter()});a("div.actions
 span.question 
a").click(function(c){c.preventDefault();a(b.acrossInput).val(1);showClear()});a("div.actions
 span.clear 
a").click(function(c){c.preventDefault();a(b.allToggle).attr("checked",false);clearAcross();checker(0);updateCounter()});lastChecked=null;a(e).click(function(c){if(!c)c=window.event;var
 d=c.target?c.target:c.srcElement;if(lastChecked&&
 a.data(lastChecked)!=a.data(d)&&c.shiftKey==true){var 
f=false;a(lastChecked).attr("checked",d.checked).parent().parent().toggleClass(b.selectedClass,d.checked);a(e).each(function(){if(a.data(this)==a.data(lastChecked)||a.data(this)==a.data(d))f=f?false:true;f&&a(this).attr("checked",d.checked).parent().parent().toggleClass(b.selectedClass,d.checked)})}a(d).parent().parent().toggleClass(b.selectedClass,d.checked);lastChecked=d;updateCounter()})};a.fn.actions.defaults={actionContainer:"div.actions",
-counterContainer:"span.action-counter",allContainer:"div.actions 
span.all",acrossInput:"div.actions 
input.select-across",acrossQuestions:"div.actions 
span.question",acrossClears:"div.actions 
span.clear",allToggle:"#action-toggle",selectedClass:"selected"}})(jQuery);
+counterContainer:"span.action-counter",allContainer:"div.actions 
span.all",acrossInput:"div.actions 
input.select-across",acrossQuestions:"div.actions 
span.question",acrossClears:"div.actions 
span.clear",allToggle:"#action-toggle",selectedClass:"selected"}})(django.jQuery);

Modified: django/trunk/django/contrib/admin/media/js/collapse.js
===
--- django/trunk/django/contri

Re: [Django] #13333: typo in http://docs.djangoproject.com/en/dev/intro/whatsnext/

[Django]

#1: typo in http://docs.djangoproject.com/en/dev/intro/whatsnext/
+---
  Reporter:  cicatrix1  | Owner:  gabrielhurley
Status:  assigned   | Milestone:   
 Component:  Documentation  |   Version:  1.1  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => gabrielhurley
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Ready for checkin

Comment:

 I too believe strongly in spelling and grammar, and love the Django docs.
 Patch 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] #13331: Strange behavior of lists of objects with overriden changelist_view in admin after re-login.

[Django]

#13331: Strange behavior of lists of objects with overriden changelist_view in
admin after re-login.
---+
  Reporter:  minder| Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

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

Comment:

 I'm gonna third the "please don't do this." The bug you're seeing is the
 inevitable consequence of doing something that's not thread-safe. It's not
 meant to be done.

 Re-closing as invalid as per kmtracey 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-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] #13333: typo in http://docs.djangoproject.com/en/dev/intro/whatsnext/

[Django]

#1: typo in http://docs.djangoproject.com/en/dev/intro/whatsnext/
---+
 Reporter:  cicatrix1  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I found a typo in
 {{{ "http://docs.djangoproject.com/en/dev/intro/whatsnext/"; }}}

 The (con)text is

 {{{ "This is probably where you’ll want to spent most of your time" }}}

 {{{ s/spent/spend/ }}}

 P.S. Love django and the docs.

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