Re: [Django] #13984: template.loader.select_template should return template_name as well.

[Django]

#13984: template.loader.select_template should return template_name as well.
--+-
  Reporter:  DaNmarner| Owner:  JoshStegmaier
Status:  assigned | Milestone:   
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Unreviewed   | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by JoshStegmaier):

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

Comment:

 In order to maintain backwards compatibility, it would probably be better
 if returning the template name was optional. I've attached a patch that
 would accomplish this.

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

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

[Django] #14011: QuerySet.none().values('x').query causes "DatabaseError: subquery has too many columns" when used in filters.

[Django]

#14011: QuerySet.none().values('x').query causes "DatabaseError: subquery has 
too
many columns" when used in filters.
-+--
 Reporter:  skatei   |  Status:  new
 
Milestone:   |   Component:  ORM aggregation
 
  Version:  1.2  |Keywords:  none query 
DatabaseError
Stage:  Unreviewed   |   Has_patch:  0  
 
-+--
 Just came across this error.

 {{{
 class Test(models.Model):
   name = models.CharField(max_length=20)

 test = Test(name='bob')
 test.save()
 pks = Test.objects.none().values('pk').query
 print Test.objects.exclude(pk__in=pks)

 DatabaseError: subquery has too many columns
 }}}

 The query:

 {{{
 SELECT
   "error_test"."id",
   "error_test"."name",
 FROM
   "error_test"
 WHERE
   NOT (
 "error_test"."id"
   IN (
 SELECT
   "error_test"."id",
   "error_test"."name",
 FROM
   "error_test"
   )
   )
 }}}

 Fixes?:

 * Substitute with {{{.filter(pk__in=[])}}} (possibly overriding none).

 * Catch and deal with the exception.

 * Don't let this happen in the code.

 This should at least raise a more meaningful exception if deemed
 incorrect.

 Reason i'd like it to work is because I apply filters dynamically, using
 some complex logic that sometimes applies a none filter.

-- 
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] #13621: Regression in 1.2.1. date/time widgets are printing their values with an invalid format

[Django]

#13621: Regression in 1.2.1. date/time widgets are printing their values with an
invalid format
+---
  Reporter:  bufke  | Owner:  jacmkno
Status:  assigned   | Milestone: 
 Component:  Forms  |   Version:  1.2
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacmkno):

  * owner:  zerok => jacmkno
  * status:  new => assigned

Comment:

 ticket13621-alternative2.diff had a problem. Django's client side I18N
 architecture is build in the expectation that all I/O from date time
 fields is localized, so the client side part of the admin was still
 placing localized data in the fields.

 The new patch ticket13621-alternative3.diff, simply makes the date or time
 fields default their localize attribute to True which seems to work fine
 in EN, ES and ZH. Haven't tested the AM/PM problem yet.

-- 
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] #13621: Regression in 1.2.1. date/time widgets are printing their values with an invalid format

[Django]

#13621: Regression in 1.2.1. date/time widgets are printing their values with an
invalid format
+---
  Reporter:  bufke  | Owner:  zerok
Status:  new| Milestone:   
 Component:  Forms  |   Version:  1.2  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by jacmkno):

  * stage:  Accepted => Ready for checkin

Comment:

 ticket13621-alternative2.diff - Details:
 Django is currently using localization formatting only for the validations
 and the client-side widget behavior but not when filling the initial data
 of the field. So at first I thought the problem was about filling the
 localized data in the field, but it turns out that both the widget and the
 form field use the localized format if the localize attribute is set to
 True. Finally I found that for validations, Django was not checking the
 localize attribute but only the USE_L10N setting. Fixing this took
 changing only 5 lines of code, hopefully it solves the AM/PM problem too,
 but i'm not sure (haven't tested that yet).

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

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

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

[Django]

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

 Replying to [comment:10 jk]:
 > I get an error when I try to apply the patch
 >
 >
 > {{{
 > patch --dry-run -p1 < ~/Downloads/ticket13095_r12761.diff
 > patching file forms/models.py
 > Hunk #1 FAILED at 797.
 > 1 out of 1 hunk FAILED -- saving rejects to file forms/models.py.rej
 > }}}
 >
 > Any ideas?
 >

 My apologies.
 I tried applying the patch "ticket13095_r13307.diff" and it worked. It did
 complain about the missing test files, which I skipped.

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

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

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

[Django]

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

 I get an error when I try to apply the patch


 {{{
 patch --dry-run -p1 < ~/Downloads/ticket13095_r12761.diff
 patching file forms/models.py
 Hunk #1 FAILED at 797.
 1 out of 1 hunk FAILED -- saving rejects to file forms/models.py.rej
 }}}

 Any ideas?

-- 
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] #13621: Regression in 1.2.1. date/time widgets are printing their values with an invalid format

[Django]

#13621: Regression in 1.2.1. date/time widgets are printing their values with an
invalid format
---+
  Reporter:  bufke | Owner:  zerok
Status:  new   | Milestone:   
 Component:  Forms |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by jacmkno):

  * owner:  jacmkno => zerok
  * status:  assigned => new

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

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

Re: [Django] #13621: Regression in 1.2.1. date/time widgets are printing their values with an invalid format

[Django]

#13621: Regression in 1.2.1. date/time widgets are printing their values with an
invalid format
---+
  Reporter:  bufke | Owner:  jacmkno
Status:  assigned  | Milestone: 
 Component:  Forms |   Version:  1.2
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jacmkno):

  * owner:  zerok => jacmkno
  * status:  new => assigned
  * summary:  regression in 1.2.1 from 1.2 AM PM time input no longer works
  correctly => Regression in 1.2.1. date/time
  widgets are printing their values with an
  invalid format

Comment:

 This problem causes the django admin to become unusable in forms with date
 or datetime fields. This needs to fixed soon in the trunk. I changed the
 title to make it sound a bit more precise.

-- 
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] #10909: Allow use of the Sitemaps Framework without requiring the sites contrib application

[Django]

#10909: Allow use of the Sitemaps Framework without requiring the sites contrib
application
---+
  Reporter:  qingfeng  | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 Is this a dupe of #10235?

-- 
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] #9655: urlize should not quote already quoted urls.

[Django]

#9655: urlize should not quote already quoted urls.
-+--
  Reporter:  flytwokites | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Template system |   Version:  1.0   
Resolution:  |  Keywords:  urlize
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by myneur):

 Please, think in the way of most common usecase instead of "theoretical
 correctness" or what's your point(?).

 Most common usecase is that user copy-paste address from his browser and
 these links needs to be translated. [[BR]]
 - in urlize, this case doesn't work at all
 [[BR]]
 - there is absolutely no way how the current urlize can work with a space
 in link (common in linked google documents) (plain text space breaks
 detection, and encoded space %20 is replaced into %2520).
 [[BR]]
 - there is no way why to use this function if it doesn't work:(

 What is usecase you have built urlize for?
 Does anybody do anything else than copypasting links?

 Thank you for rethinking this.

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

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

Re: [Django] #2445: [patch] allow callable values for limit_choices_to

[Django]

#2445: [patch] allow callable values for limit_choices_to
+---
  Reporter:  mich...@actrix.gen.nz  | Owner:  nobody
Status:  new| Milestone:
 Component:  Core framework |   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  1 
Needs_better_patch:  1  |  
+---
Changes (by banyanleo):

 * cc: l...@banyanbranch.com (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] #13621: regression in 1.2.1 from 1.2 AM PM time input no longer works correctly

[Django]

#13621: regression in 1.2.1 from 1.2 AM PM time input no longer works correctly
---+
  Reporter:  bufke | Owner:  zerok
Status:  new   | Milestone:   
 Component:  Forms |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by zerok):

 Another update to the patch. The previous version was a bit too aggressive
 and more or less disabled localize=False in order to get the format to
 work in the admin. I'v now moved that behaviour into the admin's form
 field generator to make fields by default localize=True if USE_L10N=True
 and no previous setting was specified for that flag.

-- 
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] #14002: filesizeformat filter only supports up to GB

[Django]

#14002: filesizeformat filter only supports up to GB
--+-
  Reporter:  atm  | Owner:  atm
Status:  new  | Milestone: 
 Component:  Template system  |   Version: 
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  1  
Needs_better_patch:  1|  
--+-
Comment (by atm):

 Thanks for the review. New patch forthcoming.

-- 
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] #14010: mention DYLD_LIBRARY_PATH in macosx installation instructions

[Django]

#14010: mention DYLD_LIBRARY_PATH in macosx installation instructions
---+
 Reporter:  rburhum|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords:  mac, installation  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I've never had problems setting up a django environment on Linux or even
 Windows. However, I have always wrestled with getting it to work on a Mac
 and always ended up giving up and moving on. Turns out that all I needed
 was to setup the DYLD_LIBRARY_PATH in my .profile to get it to pick up the
 right libraries


 export
 
DYLD_LIBRARY_PATH=/Library/Frameworks/GEOS.framework/unix/lib:/Library/PostgreSQL/8.3/lib:/Library/Frameworks/GDAL.framework/Versions/Current/Libraries:/Library/Frameworks/GDAL.framework/Versions/Current/unix/lib:/Library/Frameworks/PROJ.framework/Versions/Current/unix/lib

 Maybe someone should add it to 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.

Re: [Django] #14001: Can't use testing w/out having db creation privileges

[Django]

#14001: Can't use testing w/out having db creation privileges
+---
  Reporter:  mnbayazit  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  1.2   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 This is an assumption we need to make to make testing predictable and
 stable. If it's an assumption that breaks for you, you should look into
 writing [http://docs.djangoproject.com/en/1.2/topics/testing/#defining-a
 -test-runner a custom test runner].

-- 
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] #13546: Easier handling of localize field options in ModelForm

[Django]

#13546: Easier handling of localize field options in ModelForm
---+
  Reporter:  hsk   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by camilonova):

 I like the solution from russellm seems pretty clean, and there is many
 cases for a developer would need this.

 When it will be possible include this solution at trunk?

-- 
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] #6646: included template blocks are not being overrided by parent template.

[Django]

#6646: included template blocks are not being overrided by parent template.
--+-
  Reporter:  anonymous| Owner: 
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords:  include, extends, block
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  1|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by mitar):

 * cc: mmi...@gmail.com (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] #4824: Enforce a check for duplicate named url patterns

[Django]

#4824: Enforce a check for duplicate named url patterns
-+--
  Reporter:  Favo   | Owner:  nobody  
Status:  new | Milestone:  1.3 
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  sprintsept14
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by heracek):

  * owner:  heracek => nobody

-- 
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] #13961: i18n documentation should specify how to include a reverse url lookup in a {% blocktrans %} tag

[Django]

#13961: i18n documentation should specify how to include a reverse url lookup 
in a
{% blocktrans %} tag
+---
  Reporter:  garrison   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by richardb):

 * cc: richardbar...@yahoo.co.uk (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] #4824: Enforce a check for duplicate named url patterns

[Django]

#4824: Enforce a check for duplicate named url patterns
-+--
  Reporter:  Favo   | Owner:  heracek 
Status:  new | Milestone:  1.3 
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  sprintsept14
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by drdee):

 * cc: dvanli...@gmail.com (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] #4824: Enforce a check for duplicate named url patterns

[Django]

#4824: Enforce a check for duplicate named url patterns
-+--
  Reporter:  Favo   | Owner:  heracek 
Status:  new | Milestone:  1.3 
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  sprintsept14
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by drdee):

  * needs_better_patch:  1 => 0
  * milestone:  => 1.3

Comment:

 Hi,

 I have taken the liberty to come up with a new patch to check for
 duplicate urlnames across different apps (but in the same project). This
 function loads the different urls.py file, constructs a list of urlnames
 and raises an ImproperlyConfigured error when it finds a duplicate name.
 The call to this function is missing because I do not think it should be
 part of patterns() like the previous patch: that would create too many
 unnecessary calls to the function. IMHO, it's better to put a call to this
 function around model initialization, but I do not know what would be an
 appropriate place to do that, so I leave that decision to the senior
 django developers. I can also imagine that this function needs to move to
 a different location then the current /django/conf/urls/defaults.py but
 for the sake of the ticket I have left it in the same place as the
 previous patch.

 Best,

 Diederik

-- 
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] #14000: Removal of obsolete "versionadded" tags

[Django]

#14000: Removal of obsolete "versionadded" tags
+---
  Reporter:  richardb   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  versionadded
 Stage:  Unreviewed | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by richardb):

 Hi Ramiro,

 I would be interested in seeing your script once it's cleaned up!

 I had thought of automating the removal of these tags, but got worried
 about it cutting out too much. For example, if you look at
 http://docs.djangoproject.com/en/1.2/ref/models/querysets/#order-by-fields
 there are several "comments" added on with a versionadded tag, if you just
 remove the tag then the document would no longer flow naturally and would
 be difficult to read.

 After spending a couple of hours manually stripping out tags (and posting
 the patch here) I realised that the majority of the tags are in fact
 attached to new attributes, methods, or settings, and so it should be
 possible to automatically detect these tags and remove only these, leaving
 the rest for manual review. Does your script do this?

 By the way, I notice that your script says it's removing 2 tags from
 ref/contrib/flatpages.txt and also from ref/contrib/formtools/form-
 wizard.txt - but I can only find one tag in the source for each of those
 pages?

-- 
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] #14008: GeoDjango subquery fails with bad quoting

[Django]

#14008: GeoDjango subquery fails with bad quoting
-+--
  Reporter:  Matthew | Owner:  nobody
Status:  new | Milestone:
 Component:  GIS |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jbronn):

  * needs_better_patch:  => 0
  * component:  Uncategorized => GIS
  * needs_tests:  => 0
  * needs_docs:  => 0

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

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

[Django] #14008: GeoDjango subquery fails with bad quoting

[Django]

#14008: GeoDjango subquery fails with bad quoting
---+
 Reporter:  Matthew|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 This code (adapted from source code of http://github.com/mysociety/mapit
 ):

 {{{
 areas = Area.objects.filter(
   polygons__polygon__contains = location,
   generation_low__lte = 13,
   generation_high__gte = 13
 )
 Code.objects.filter( area__in = areas )
 }}}

 generates the following SQL (on a PostGIS database):

 {{{
 SELECT "areas_code"."id", "areas_code"."area_id", "areas_code"."type",
 "areas_code"."code"
 FROM "areas_code"
 WHERE "areas_code"."area_id" IN (
   SELECT U0."id" FROM "areas_area" U0
   INNER JOIN "areas_geometry" U1 ON (U0."id" = U1."area_id")
   WHERE (ST_Contains("U1"."polygon",
 
ST_GeomFromWKB('\\001\\001\\000\\000\\000\\000\\000\\000\\000\\000j\\030A\\000\\000\\000\\000\\200O\\022A',
 27700))
   AND U0."generation_high_id" >= 13 AND U0."generation_low_id" <= 13 )
 );
 }}}

 which gives this error:

 {{{
 ERROR:  missing FROM-clause entry in subquery for table "U1"
 LINE 1: ...U1 ON (U0."id" = U1."area_id") WHERE (ST_Contains("U1"."poly...
 }}}

 It appears that the "U1" must '''not''' be quoted in the first argument to
 ST_Contains, as then it works fine:

 {{{
 SELECT "areas_code"."id", "areas_code"."area_id", "areas_code"."type",
 "areas_code"."code"
 FROM "areas_code"
 WHERE "areas_code"."area_id" IN (
   SELECT U0."id" FROM "areas_area" U0
   INNER JOIN "areas_geometry" U1 ON (U0."id" = U1."area_id")
   WHERE (ST_Contains(U1."polygon",
 
ST_GeomFromWKB('\\001\\001\\000\\000\\000\\000\\000\\000\\000\\000j\\030A\\000\\000\\000\\000\\200O\\022A',
 27700))
   AND U0."generation_high_id" >= 13 AND U0."generation_low_id" <= 13 )
 );
   id   | area_id |  type   |  code
 ---+-+-+
  14532 |9498 | unit_id | 148
  14531 |9498 | ons | 00CUGA
  44890 |   65890 | unit_id | 24640
  17586 |   11809 | unit_id | 41426
   2324 |2546 | unit_id | 72
   2323 |2546 | ons | 00CU
 (6 rows)
 }}}

 I did look at the code to try and see what does the quoting or inner
 joining, but I'm afraid I couldn't work it out, sorry.

-- 
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] #14007: Automatically discover models within a package without using the app_label Meta attribute

[Django]

#14007: Automatically discover models within a package without using the 
app_label
Meta attribute
--+-
 Reporter:  m...@deliciouslynerdy.com |   Owner:  nobody
   Status:  new   |   Milestone:  1.3   
Component:  Database layer (models, ORM)  | Version:  1.2   
 Keywords:  package models model  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Automatically figure out the app_label for a model by looking one level up
 from the package or module named 'models'.
 If no such package or module exists, fall back to the behavior of looking
 one level up from
 the module the model is defined in.

 For 'django.contrib.sites.models', this would be 'sites'.[[BR]]
 For 'geo.models.places' this would be 'geo'.[[BR]]
 For 'polymorphic.polymorhpic_model' this would be 'polymorphic'.[[BR]]

 This allows organization of models within a package named 'models' without
 having to specify the app_label Meta attribute for each model.

-- 
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] #14006: Documentation on Field's 'description' class attribute does not mention that it will be interpolated with field.__dict__

[Django]

#14006: Documentation on Field's 'description' class attribute does not mention
that it will be interpolated with field.__dict__
---+
 Reporter:  abeld  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The "Documenting your Custom Field" section in the "Writing custom
 model fields" page
 (http://docs.djangoproject.com/en/1.2/howto/custom-model-fields/) does
 not mention that this string will be string-interpolated with
 fields.__dict__ (in the get_readable_field_data_type() function in
 django.contrib.admindocs.views ) and thus can (and should, if
 appropriate, since it really increases the usability of the admin
 docs) contain stuff like %(some_attribute)s, and the example presented
 doesn't show this feature, either.

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