[Django] #11785: Invalid error reporting when importing MapInfo layer with Unknown type

[Django]

#11785: Invalid error reporting when importing MapInfo layer with Unknown type
--+-
 Reporter:  esizikov  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  GIS   | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 When going to import a spatial data from an !MapInfo file I've stacked
 with an error message like following:

 {{{
 #!python
 ...
   File "../django/contrib/gis/utils/layermapping.py", line 293, in
 check_layer
 raise LayerMapError('Invalid mapping geometry; model has %s, feature
 has %s.' % (fld_name, ltype))
 django.contrib.gis.utils.layermapping.LayerMapError: Invalid mapping
 geometry; model has PolygonField, feature has Polygon.
 }}}

 It took about 2 hours to figure out what could be wrong here, as the error
 message looks like a nonsense (Polygon != Polygon)

 Looking through the code I've found a possible reason of such a
 misunderstanding:
 {{{
 #!diff
 --- layermapping.py.orig2009-08-26 09:36:12.438952459 +0700
 +++ layermapping.py 2009-08-26 09:36:21.979827357 +0700
 @@ -290,7 +290,7 @@
  # Making sure that the OGR Layer's Geometry is
 compatible.
  ltype = self.layer.geom_type
  if not (gtype == ltype or self.make_multi(ltype,
 model_field)):
 -raise LayerMapError('Invalid mapping geometry; model
 has %s, feature has %s.' % (fld_name, gtype))
 +raise LayerMapError('Invalid mapping geometry; model
 has %s, feature has %s.' % (fld_name, ltype))

  # Setting the `geom_field` attribute w/the name of the
 model field
  # that is a Geometry.

 }}}

 After that been done I've got a meaningful error like this one:
 {{{
 #!python
   File "../django/contrib/gis/utils/layermapping.py", line 293, in
 check_layer
 raise LayerMapError('Invalid mapping geometry; model has %s, feature
 has %s.' % (fld_name, ltype))
 django.contrib.gis.utils.layermapping.LayerMapError: Invalid mapping
 geometry; model has PolygonField, feature has Unknown.
 }}}

 It became clear to me that LayerMapping complains to import from a
 !MapInfo layer with Unknown geometry type. That's what I was looking for 2
 hours!

 However, that "... ''model has PolygonField, feature has Unknown''."
 doesn't looks polished too. Could someone provide a better fix?

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

Re: [Django] #10976: missing template files for correctly executing test cases on django.contrib.auth

[Django]

#10976: missing template files for correctly executing test cases on
django.contrib.auth
+---
  Reporter:  aarond10   | Owner:  SmileyChris
Status:  assigned   | Milestone:  1.2
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * owner:  arthurk => SmileyChris
  * status:  new => assigned

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

Re: [Django] #10976: missing template files for correctly executing test cases on django.contrib.auth

[Django]

#10976: missing template files for correctly executing test cases on
django.contrib.auth
+---
  Reporter:  aarond10   | Owner:  arthurk
Status:  new| Milestone:  1.2
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * has_patch:  0 => 1
  * stage:  Accepted => Ready for checkin
  * milestone:  => 1.2

Comment:

 Here's a patch which adds the missing template files (and I verify that
 this fixes the auth test errors related to overridden template files for
 me).

 #11009 covered fixing just the incomplete duplicate `setUp` and `tearDown`
 methods, so I marked that as a duplicate of this one

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

Re: [Django] #11009: Auth PasswordResestTest fails since changeset 10599 - Ticket #8752

[Django]

#11009: Auth PasswordResestTest fails since changeset 10599 - Ticket #8752
-+--
  Reporter:  laureline.gue...@makina-corpus.org  | Owner:  
nobody
Status:  closed  | Milestone:   
 
 Component:  Contrib apps|   Version:  SVN  
 
Resolution:  duplicate   |  Keywords:   
 
 Stage:  Ready for checkin   | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

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

Comment:

 Closing as a duplicate of #10976

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

Re: [Django] #9674: app_label missing from documentation

[Django]

#9674: app_label missing from documentation
+---
  Reporter:  andymckay  | 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 jpaulett):

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

Re: [Django] #9674: app_label missing from documentation

[Django]

#9674: app_label missing from documentation
+---
  Reporter:  andymckay  | 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 John Paulett):

  * has_patch:  0 => 1
  * version:  1.0 => SVN

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

Re: [Django] #5833: Custom FilterSpecs

[Django]

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

 Another place where it would be likeable to keep the filters are with
 admin actions

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

Re: [Django] #11609: Allow for long pointer format in django.contrib.gis.gdal.base

[Django]

#11609: Allow for long pointer format in django.contrib.gis.gdal.base
---+
  Reporter:  rmkemker  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Contrib apps  |   Version:  1.1-beta-1
Resolution:|  Keywords:  gdal.base 
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by starsareblueandfaraway):

 Replying to [ticket:11609 rmkemker]:
 > My apache webserver is outputting long pointer types for the ESRI
 Driver. Adding a check for the long format and then converting it to int
 allows for the webserver to work correctly.

 I am having the same problem.  Can someone please address this issue?

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

Re: [Django] #11784: exceptions should sublcass StandardError, not Exception

[Django]

#11784: exceptions should sublcass StandardError, not Exception
-+--
  Reporter:  anonymous   | Owner:  nobody   
Status:  closed  | Milestone:   
 Component:  Core framework  |   Version:  1.1  
Resolution:  wontfix |  Keywords:  exception
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by dc):

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

Comment:

 exception Exception

 All built-in, non-system-exiting exceptions are derived from this
 class. All user-defined exceptions should also be derived from this class.

 http://docs.python.org/library/exceptions.html#exceptions.Exception

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

Re: [Django] #10136: django should not insert newlines in generated html at places where the template has comments

[Django]

#10136: django should not insert newlines in generated html at places where the
template has  comments
---+
  Reporter:  sar...@media.mit.edu  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Template system   |   Version:  SVN   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by SmileyChris):

 (#2594)

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

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  new   | Milestone:  1.2

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

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 It's not ready for checkin, because it's missing the test (you marked it
 as such). After the test is added, feel free to bring it up in the dev
 google group.

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

Re: [Django] #11783: django.contrib.humanize.templatetags.ordinal throws TypeError for NoneType

[Django]

#11783: django.contrib.humanize.templatetags.ordinal throws TypeError for 
NoneType
---+
  Reporter:  realpolitik   | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Contrib apps  |   Version:  1.1
   
Resolution:|  Keywords:  contrib, humanize, 
ordinal, ValueError
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Changes (by SmileyChris):

  * needs_better_patch:  0 => 1

Comment:

 That should be:
 {{{
 #!python
 except (TypeError, ValueError):
 }}}

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

[Django] #11784: exceptions should sublcass StandardError, not Exception

[Django]

#11784: exceptions should sublcass StandardError, not Exception
+---
 Reporter:  anonymous   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.1   
 Keywords:  exception   |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 a quick look at the standard python library's exception hierarchy (
 http://docs.python.org/library/exceptions.html#exception-hierarchy ) will
 show that in all but a few special cases, exceptions should subclass
 StandardError.  all of django's exceptions subclass the parent class of
 StandardError, Exception.  In addition to being good practice to keep a
 clean class hierarchy, coders accustomed to catching StandardError may
 have unexpected results when using django.

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

Re: [Django] #11687: The 'add' template filter only works for integers, and can fail noisily

[Django]

#11687: The 'add' template filter only works for integers, and can fail noisily
+---
  Reporter:  thepointer | Owner:  gruszczy
Status:  new| Milestone:  1.2 
 Component:  Template system|   Version:  1.1 
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * stage:  Design decision needed => Ready for checkin

Comment:

 Looking good.

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

Re: [Django] #10355: add support for email backends

[Django]

#10355: add support for email backends
---+
  Reporter:  wkornewald| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.core.mail  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by andialbrecht):

 Replying to [comment:5 wkornewald]:
 > It's good that you can override send_messages (plural), but most
 backends will probably only need a send_message (singular) function which
 gets called repeatedly. How about making the
 BaseEmailBackend.send_messages() function simply call send_message()?
 Maybe it could even try to call open() and close() if those functions are
 defined?

 I think that this would complicate things. The connection handling needs
 to be implemented in both methods then as both methods need to know the
 current connection state (if any) for doing their job right.

 >
 > Regarding fail_silently, couldn't this be moved out? If an exception is
 raised by send_messages it simply gets ignored.

 This would change the current behavior and available keyword arguments to
 a lot of functions and there are cases where it's good to know when mail
 delivery has failed.

 >
 > Regarding the log backend: This can be useful on App Engine and other
 systems which don't allow for writing to the console.

 I don't see a real need for App Engine. The SDK already logs messages to
 the console and if someone still wants to log in production environment
 it'd be a single additional line in a custom App Engine backend. For other
 systems I'm not sure. However, writing such a custom backend would be
 trivial.

 >
 > Andi, thanks a lot for working on this!

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

Re: [Django] #5390: Add signals to ManyRelatedManager

[Django]

#5390: Add signals to ManyRelatedManager
--+-
  Reporter:  Ludovico Magnocavallo   | Owner:  
rvdrijst   
Status:  assigned | Milestone:  
   
 Component:  Database layer (models, ORM) |   Version:  SVN 
   
Resolution:   |  Keywords:  
manytomanyfield feature signals
 Stage:  Design decision needed   | Has_patch:  1   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by natrius):

 * cc: ni...@niran.org (added)

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

Re: [Django] #11783: django.contrib.humanize.templatetags.ordinal throws TypeError for NoneType

[Django]

#11783: django.contrib.humanize.templatetags.ordinal throws TypeError for 
NoneType
---+
  Reporter:  realpolitik   | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Contrib apps  |   Version:  1.1
   
Resolution:|  Keywords:  contrib, humanize, 
ordinal, ValueError
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

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

[Django] #11783: django.contrib.humanize.templatetags.ordinal throws TypeError for NoneType

[Django]

#11783: django.contrib.humanize.templatetags.ordinal throws TypeError for 
NoneType
+---
 Reporter:  realpolitik |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Contrib apps| Version:  1.1   
 Keywords:  contrib, humanize, ordinal, ValueError  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 The short summary probably covered everything. ordinal(value) catches
 ValueError but not TypeError.

 Error Message: "Exception Value: int() argument must be a string or a
 number, not 'NoneType'"

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

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  new   | Milestone:  1.2

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

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 I'm honestly not sure why the attached patch hasn't made it in -- I've
 been using it in my production environments and haven't had any problems.
 I was waiting on some feedback from mtredinnick, as to what the "if not
 allow_many and (m2m or not direct)" was for,   but I'm not sure if he's
 following this ...

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

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  new   | Milestone:  1.2

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

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 Why not make this (following reverse relationships as well as forward
 ones) the default behavior if select_related() is given no arguments?

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

Re: [Django] #10972: Use Expressions with Annotations

[Django]

#10972: Use Expressions with Annotations
--+-
  Reporter:  m...@donaldrichardson.net  | Owner:
  
Status:  new  | Milestone:  

 Component:  ORM aggregation  |   Version:  SVN 

Resolution:   |  Keywords:  expression 
aggregation aggregates annotation
 Stage:  Accepted | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

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

 * cc: alexkoshelev (added)

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

Re: [Django] #7198: manage.py sql/sqlall/etc. errors on apps without models.py files

[Django]

#7198: manage.py sql/sqlall/etc. errors on apps without models.py files
-+--
  Reporter:  gav | Owner:  nobody   

Status:  new | Milestone:   

 Component:  Core framework  |   Version:  SVN  

Resolution:  |  Keywords:  management 
command sql sqlall
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Comment (by imbac...@gmail.com):

 ok disregard that.

 this problem also happens if you have an import error in your models.py. i
 changed too much on a single go and incorrectly blamed the other apps -
 they do have their own models.py.

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

Re: [Django] #7198: manage.py sql/sqlall/etc. errors on apps without models.py files

[Django]

#7198: manage.py sql/sqlall/etc. errors on apps without models.py files
-+--
  Reporter:  gav | Owner:  nobody   

Status:  new | Milestone:   

 Component:  Core framework  |   Version:  SVN  

Resolution:  |  Keywords:  management 
command sql sqlall
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Comment (by imbac...@gmail.com):

 this is a serious problem - afaik tinymce and filebrowser apps will
 trigger this.

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

Re: [Django] #10355: add support for email backends

[Django]

#10355: add support for email backends
---+
  Reporter:  wkornewald| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.core.mail  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by wkornewald):

 It's good that you can override send_messages (plural), but most backends
 will probably only need a send_message (singular) function which gets
 called repeatedly. How about making the BaseEmailBackend.send_messages()
 function simply call send_message()? Maybe it could even try to call
 open() and close() if those functions are defined?

 Regarding fail_silently, couldn't this be moved out? If an exception is
 raised by send_messages it simply gets ignored.

 Regarding the log backend: This can be useful on App Engine and other
 systems which don't allow for writing to the console.

 Andi, thanks a lot for working on this!

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