Re: [Django] #2131: HttpResponseSendFile for serving static files handler-specific sendfile mechanism

[Django]

#2131: HttpResponseSendFile for serving static files handler-specific sendfile
mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  ccahoon
Status:  new   | Milestone:  1.2
 Component:  Core framework|   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Fixed on a branch | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by springmeyer):

 * cc: dane.springme...@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] #12309: New format character to represent alternative locale-specifc month names

[Django]

#12309: New format character to represent alternative locale-specifc month names
---+
  Reporter:  shell_dweller | Owner:  shell_dweller  
 
Status:  assigned  | Milestone:  1.2
 
 Component:  Internationalization  |   Version: 
 
Resolution:|  Keywords:  date, template, 
i18n
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by shell_dweller):

  * owner:  nobody => shell_dweller
  * needs_better_patch:  => 0
  * status:  new => assigned
  * 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] #12309: New format character to represent alternative locale-specifc month names

[Django]

#12309: New format character to represent alternative locale-specifc month names
--+-
 Reporter:  shell_dweller |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Internationalization  | Version:
 Keywords:  date, template, i18n  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I would like to suggest (and claim responsibility for) an extension for
 date format to handle alternative (locale specific) months names.

 == Why is this needed? ==

 Alternative months names would have no universal meaning but would allow
 an additional flexibility with date display in certain languages.

 For example, in some Slavic languages (Polish, Ukrainian, Russian and
 likely few others) phrases “January 2010” and “January 1 2010” would
 require two distinct grammatical forms: nominative in the first case and
 genitive in the second. To represent phrases with month names in the
 genitive case one would use the alternative month names.

 == How to represent it ==

 I have no particular preference. “E” seems to be a reasonable choice
 because it stands next to “F” in the alphabet and “F” in used in Django to
 represent long month names.

 == Implementation ==

 Coding for this feature is trivial. But I will need to cooperate with
 language translators to add translations to certain locales.

-- 
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] r11794 - django/branches/soc2009/multidb/docs/releases

[noreply]

Author: Alex
Date: 2009-12-03 18:55:38 -0600 (Thu, 03 Dec 2009)
New Revision: 11794

Modified:
   django/branches/soc2009/multidb/docs/releases/1.2.txt
Log:
[soc2009/multidb] Corrected a typo in the get_db_prep_* migration notes. Thanks 
to Waldemar Kornewald for the report.

Modified: django/branches/soc2009/multidb/docs/releases/1.2.txt
===
--- django/branches/soc2009/multidb/docs/releases/1.2.txt   2009-12-03 
20:57:53 UTC (rev 11793)
+++ django/branches/soc2009/multidb/docs/releases/1.2.txt   2009-12-04 
00:55:38 UTC (rev 11794)
@@ -178,7 +178,7 @@
 def get_db_prep_value(self, value, connection, prepared=False):
 # ...
 
-def get_prep_lookup(self, lookup_type, value, connection, 
prepared=False):
+def get_db_prep_lookup(self, lookup_type, value, connection, 
prepared=False):
 # ...
 
 These changes are required to support multiple databases -

--

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

[Django]

#8528: Admin list_filter doesn't respect null=True
---+
  Reporter:  StevenPotter  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by marcob):

 Patch for Django 1.1.1 and that uses:
 {{{
  "(%s)" % _("None")
 }}}

-- 
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] #10989: Typos in formset and widget media docs

[Django]

#10989: Typos in formset and widget media docs
-+--
  Reporter:  fal...@mixworx.net  | Owner:  nobody   
Status:  new | Milestone:  1.2  
 Component:  Documentation   |   Version:  1.1-beta-1   
Resolution:  |  Keywords:  formset media
 Stage:  Ready for checkin   | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #11882: Documentation missing for django.contrib.admin.ModelAdmin.formfield_for_manytomany

[Django]

#11882: Documentation missing for
django.contrib.admin.ModelAdmin.formfield_for_manytomany
+---
  Reporter:  Nils L | Owner:  anonymous 
 
Status:  assigned   | Milestone:
 
 Component:  Documentation  |   Version:  1.1   
 
Resolution: |  Keywords:  
formfield_for_manytomany, admin
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * stage:  Accepted => Ready for checkin

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

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12308: Adding tablespace support to postgres backends

[Django]

#12308: Adding tablespace support to postgres backends
--+-
 Reporter:  tclineks  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The postgres backend(s) should support tablespaces.

-- 
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] r11793 - django/branches/soc2009/multidb/docs/topics/db

[noreply]

Author: Alex
Date: 2009-12-03 14:57:53 -0600 (Thu, 03 Dec 2009)
New Revision: 11793

Modified:
   django/branches/soc2009/multidb/docs/topics/db/multi-db.txt
Log:
[soc2009/multidb] Removed a documentation reference to Meta.using.  Patch from 
Russell Keith-Magee.

Modified: django/branches/soc2009/multidb/docs/topics/db/multi-db.txt
===
--- django/branches/soc2009/multidb/docs/topics/db/multi-db.txt 2009-12-03 
20:57:33 UTC (rev 11792)
+++ django/branches/soc2009/multidb/docs/topics/db/multi-db.txt 2009-12-03 
20:57:53 UTC (rev 11793)
@@ -27,15 +27,6 @@
 in your :setting:`DATABASES` setting then Django will raise a
 ``django.db.utils.ConnectionDoesNotExist`` exception.
 
-Selecting a Database for a ``Model``
-
-
-In addition to the global default database for all models, it is possible to
-select a default database on a per-model level.  This is done using the
-``using`` option in a model's inner ``Meta`` class.  When provided this
-database becomes the default database for all lookups, saves, and deletes for
-this model.  It can be overiden on a per-query basis as described below.
-
 Selecting a Database for a ``QuerySet``
 ===
 

--

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] r11792 - django/branches/soc2009/multidb/django/db

[noreply]

Author: Alex
Date: 2009-12-03 14:57:33 -0600 (Thu, 03 Dec 2009)
New Revision: 11792

Modified:
   django/branches/soc2009/multidb/django/db/utils.py
Log:
[soc2009/multidb] Corrected error handling when the database backend is 
incorrectly specified.  Patch from Russell Keith-Magee.

Modified: django/branches/soc2009/multidb/django/db/utils.py
===
--- django/branches/soc2009/multidb/django/db/utils.py  2009-12-03 15:11:14 UTC 
(rev 11791)
+++ django/branches/soc2009/multidb/django/db/utils.py  2009-12-03 20:57:33 UTC 
(rev 11792)
@@ -2,6 +2,7 @@
 import os
 
 from django.conf import settings
+from django.core.exceptions import ImproperlyConfigured
 from django.utils.importlib import import_module
 
 def load_backend(backend_name):
@@ -29,7 +30,9 @@
 available_backends = []
 available_backends.sort()
 if backend_name not in available_backends:
-error_msg = "%r isn't an available database backend. Available 
options are: %s\nError was: %s" % \
+error_msg = ("%r isn't an available database backend. \n" +
+"Try using django.db.backends.XXX, where XXX is one of:\n  
  %s\n" +
+"Error was: %s") % \
 (backend_name, ", ".join(map(repr, available_backends)), 
e_user)
 raise ImproperlyConfigured(error_msg)
 else:

--

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] #6587: remove django.templates __path__ hacking

[Django]

#6587: remove django.templates __path__ hacking
--+-
  Reporter:  oyvind   | Owner:  andrewbadr 
Status:  new  | Milestone:  1.2
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords:  path hacking remove
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  1|  
--+-
Changes (by andrewbadr):

  * owner:  => andrewbadr

Comment:

 can take a look for 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.

Re: [Django] #12234: db_index=True creates indexes which PostgreSQL may not be able to use

[Django]

#12234: db_index=True creates indexes which PostgreSQL may not be able to use
---+
  Reporter:  ubernostrum   | Owner:  jbronn
Status:  assigned  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by jbronn):

  * owner:  nobody => jbronn
  * needs_docs:  0 => 1
  * has_patch:  0 => 1
  * status:  new => assigned
  * needs_tests:  0 => 1

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

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #11981: Add custom Q-object (add_to_query) support to QuerySet.filter() and QuerySet.exclude()

[Django]

#11981: Add custom Q-object (add_to_query) support to QuerySet.filter() and
QuerySet.exclude()
---+
  Reporter:  emulbreh  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
complex_filter, add_to_query
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by emulbreh):

  * has_patch:  0 => 1

Comment:

 ...

-- 
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] #11946: ManyToOneRel.lookup_overrides is unused

[Django]

#11946: ManyToOneRel.lookup_overrides is unused
---+
  Reporter:  emulbreh  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by emulbreh):

  * has_patch:  0 => 1

Comment:

 ...

-- 
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] #9475: add(), create(), etc. should be supported by intermedite ManyToMany model with extra attributes if extra fields can be calculated

[Django]

#9475: add(), create(), etc. should be supported by intermedite ManyToMany model
with extra attributes if extra fields can be calculated
---+
  Reporter:  o...@gezgin.com   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by emulbreh):

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

Comment:

 ...

-- 
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] #11981: Add custom Q-object (add_to_query) support to QuerySet.filter() and QuerySet.exclude()

[Django]

#11981: Add custom Q-object (add_to_query) support to QuerySet.filter() and
QuerySet.exclude()
---+
  Reporter:  emulbreh  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
complex_filter, add_to_query
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * has_patch:  1 => 0
  * version:  1.1 => 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-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] #9475: add(), create(), etc. should be supported by intermedite ManyToMany model with extra attributes if extra fields can be calculated

[Django]

#9475: add(), create(), etc. should be supported by intermedite ManyToMany model
with extra attributes if extra fields can be calculated
---+
  Reporter:  o...@gezgin.com   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * needs_better_patch:  1 => 0
  * 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-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] #11946: ManyToOneRel.lookup_overrides is unused

[Django]

#11946: ManyToOneRel.lookup_overrides is unused
---+
  Reporter:  emulbreh  | 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 anonymous):

  * has_patch:  1 => 0
  * version:  1.1 => 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-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] #11892: Model __eq__ is not symmetric.

[Django]

#11892: Model __eq__ is not symmetric.
+---
  Reporter:  pmcnerth...@clearpointmetrics.com  | Owner:  nobody
Status:  new| Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by anonymous):

  * needs_better_patch:  0 => 1
  * version:  1.1 => 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-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] #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:  0  

Needs_better_patch:  0 |  
---+
Changes (by Harm Geerts ):

 * cc: hgee...@osso.nl (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.

[Changeset] r11791 - django/trunk/django/contrib/admin

[noreply]

Author: lukeplant
Date: 2009-12-03 09:11:14 -0600 (Thu, 03 Dec 2009)
New Revision: 11791

Modified:
   django/trunk/django/contrib/admin/sites.py
Log:
Updated all PendingDeprecationWarning from 1.1 to DeprecationWarning ready for 
1.2



Modified: django/trunk/django/contrib/admin/sites.py
===
--- django/trunk/django/contrib/admin/sites.py  2009-12-03 14:58:58 UTC (rev 
11790)
+++ django/trunk/django/contrib/admin/sites.py  2009-12-03 15:11:14 UTC (rev 
11791)
@@ -452,7 +452,7 @@
 import warnings
 warnings.warn(
 "AdminSite.root() is deprecated; use include(admin.site.urls) 
instead.",
-PendingDeprecationWarning
+DeprecationWarning
 )
 
 #

--

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] r11790 - in django/trunk: django/core/mail docs/releases

[noreply]

Author: russellm
Date: 2009-12-03 08:58:58 -0600 (Thu, 03 Dec 2009)
New Revision: 11790

Modified:
   django/trunk/django/core/mail/__init__.py
   django/trunk/docs/releases/1.2.txt
Log:
Expanded on the SMTPConnection deprecation notes, and made the deprecation a 
PendingDeprecationWarning as per the deprecation guidelines.

Modified: django/trunk/django/core/mail/__init__.py
===
--- django/trunk/django/core/mail/__init__.py   2009-12-03 14:55:28 UTC (rev 
11789)
+++ django/trunk/django/core/mail/__init__.py   2009-12-03 14:58:58 UTC (rev 
11790)
@@ -105,6 +105,6 @@
 import warnings
 warnings.warn(
 'mail.SMTPConnection is deprecated; use mail.get_connection() 
instead.',
-DeprecationWarning
+PendingDeprecationWarning
 )
 super(SMTPConnection, self).__init__(*args, **kwds)

Modified: django/trunk/docs/releases/1.2.txt
===
--- django/trunk/docs/releases/1.2.txt  2009-12-03 14:55:28 UTC (rev 11789)
+++ django/trunk/docs/releases/1.2.txt  2009-12-03 14:58:58 UTC (rev 11790)
@@ -42,8 +42,8 @@
  * All of the CSRF has moved from contrib to core (with backwards compatible
imports in the old locations, which are deprecated).
 
-LazyObject
---
+``LazyObject``
+--
 
 ``LazyObject`` is an undocumented utility class used for lazily wrapping other
 objects of unknown type.  In Django 1.1 and earlier, it handled introspection 
in
@@ -67,6 +67,7 @@
 
__members__ = property(lambda self: self.__dir__())
 
+
 .. _deprecated-features-1.2:
 
 Features deprecated in 1.2
@@ -88,8 +89,39 @@
 ``SMTPConnection``
 --
 
-This class has been deprecated in favor of the new generic e-mail backends.
+The ``SMTPConnection`` class has been deprecated in favor of a generic
+E-mail backend API. Old code that explicitly instantiated an instance
+of an SMTPConnection::
 
+from django.core.mail import SMTPConnection
+connection = SMTPConnection()
+messages = get_notification_email()
+connection.send_messages(messages)
+
+should now call :meth:`~django.core.mail.get_connection()` to
+instantiate a generic e-mail connection::
+
+from django.core.mail import get_connection
+connection = get_connection()
+messages = get_notification_email()
+connection.send_messages(messages)
+
+Depending on the value of the :setting:`EMAIL_BACKEND` setting, this
+may not return an SMTP connection. If you explicitly require an SMTP
+connection with which to send e-mail, you can explicitly request an
+SMTP connection::
+
+from django.core.mail import get_connection
+connection = get_connection('django.core.mail.backends.smtp')
+messages = get_notification_email()
+connection.send_messages(messages)
+
+If your call to construct an instance of ``SMTPConnection`` required
+additional arguments, those arguments can be passed to the
+:meth:`~django.core.mail.get_connection()` call::
+
+connection = get_connection('django.core.mail.backends.smtp', 
hostname='localhost', port=1234)
+
 What's new in Django 1.2
 
 

--

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] r11789 - in django/trunk/docs: releases topics

[noreply]

Author: lukeplant
Date: 2009-12-03 08:55:28 -0600 (Thu, 03 Dec 2009)
New Revision: 11789

Modified:
   django/trunk/docs/releases/1.2.txt
   django/trunk/docs/topics/email.txt
Log:
Corrected spelling of e-mail (according to our standard).

Also fixed an incorrect link in release notes.



Modified: django/trunk/docs/releases/1.2.txt
===
--- django/trunk/docs/releases/1.2.txt  2009-12-03 14:48:47 UTC (rev 11788)
+++ django/trunk/docs/releases/1.2.txt  2009-12-03 14:55:28 UTC (rev 11789)
@@ -105,21 +105,21 @@
 CSRF', where an attacking site tricks a user's browser into logging
 into a site with someone else's credentials, is also covered.
 
-Email Backends
---
+E-mail Backends
+---
 
-You can now :ref:`configure the way that Django sends email
-`. Instead of using SMTP to send all email, you
-can now choose a configurable email backend to send messages. If your
+You can now :ref:`configure the way that Django sends e-mail
+`. Instead of using SMTP to send all e-mail, you
+can now choose a configurable e-mail backend to send messages. If your
 hosting provider uses a sandbox or some other non-SMTP technique for
-sending mail, you can now construct an email backend that will allow
+sending mail, you can now construct an e-mail backend that will allow
 Django's standard :ref:`mail sending methods` to use
 those facilities.
 
 This also makes it easier to debug mail sending - Django ships with
-backend implementations that allow you to send email to a
+backend implementations that allow you to send e-mail to a
 :ref:`file`, to the
 :ref:`console`, or to
 :ref:`memory` - you can even configure all
-email to be :ref:`thrown away`.
+e-mail to be :ref:`thrown away`.
 

Modified: django/trunk/docs/topics/email.txt
===
--- django/trunk/docs/topics/email.txt  2009-12-03 14:48:47 UTC (rev 11788)
+++ django/trunk/docs/topics/email.txt  2009-12-03 14:55:28 UTC (rev 11789)
@@ -10,7 +10,7 @@
 Although Python makes sending e-mail relatively easy via the `smtplib
 library`_, Django provides a couple of light wrappers over it. These wrappers
 are provided to make sending e-mail extra quick, to make it easy to test
-email sending during development, and to provide support for platforms that
+e-mail sending during development, and to provide support for platforms that
 can't use SMTP.
 
 The code lives in the ``django.core.mail`` module.
@@ -64,7 +64,7 @@
 * ``auth_password``: The optional password to use to authenticate to the
   SMTP server. If this isn't provided, Django will use the value of the
   ``EMAIL_HOST_PASSWORD`` setting.
-* ``connection``: The optional email backend to use to send the mail.
+* ``connection``: The optional e-mail backend to use to send the mail.
   If unspecified, an instance of the default backend will be used.
   See the documentation on :ref:`E-mail backends `
   for more details.
@@ -215,8 +215,8 @@
 responsible for sending the e-mail.
 
 For convenience, :class:`~django.core.mail.EmailMessage` provides a simple
-``send()`` method for sending a single email. If you need to send multiple
-messages, the email backend API :ref:`provides an alternative
+``send()`` method for sending a single e-mail. If you need to send multiple
+messages, the e-mail backend API :ref:`provides an alternative
 `.
 
 EmailMessage Objects
@@ -264,7 +264,7 @@
 The class has the following methods:
 
 * ``send(fail_silently=False)`` sends the message. If a connection was
-  specified when the email was constructed, that connection will be used.
+  specified when the e-mail was constructed, that connection will be used.
   Otherwise, an instance of the default backend will be instantiated and
   used. If the keyword argument ``fail_silently`` is ``True``, exceptions
   raised while sending the message will be quashed.
@@ -358,9 +358,9 @@
 
 The e-mail backend class has the following methods:
 
-* ``open()`` instantiates an long-lived email-sending connection.
+* ``open()`` instantiates an long-lived e-mail-sending connection.
 
-* ``close()`` closes the current email-sending connection.
+* ``close()`` closes the current e-mail-sending connection.
 
 * ``send_messages(email_messages)`` sends a list of
   :class:`~django.core.mail.EmailMessage` objects. If the connection is
@@ -379,11 +379,11 @@
 .. function:: get_connection(backend=None, fail_silently=False, *args, 
**kwargs)
 
 By default, a call to ``get_connection()`` will return an instance of the
-email backend specified in :setting:`EMAIL_BACKEND`. If you specify the
+e-mail backend specified in :setting:`EMAIL_BACKEND`. If you specify the
 ``backend`` argument, an instance of that backend will be instantiated.
 
 The ``fail_silently`` argument controls how the backend should handle errors.
-If ``fail_silently`` is True, exceptions during th

[Django] #12307: GeoDjango test suite fails for SpatialRefSys model objects

[Django]

#12307: GeoDjango test suite fails for SpatialRefSys model objects
---+
 Reporter:  tylere |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  SVN   
 Keywords:  SpatialRefSys TOWGS84  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When running the GeoDjango test suite, two tests fail because srs.wkt
 includes the term '''TOWGS84[0,0,0,0,0,0,0],
 '''

 Environment:[[BR]]
 django:  '1.2 pre-alpha SVN-11787'[[BR]]
 postgis: 1.4.0[[BR]]
 proj:4.6.0[[BR]]
 GEOS:3.1.1[[BR]]
 GDAL:1.6.2[[BR]]
 OS:  Ubuntu 9.04[[BR]]


 
 {{{
 ==
 FAIL: Testing retrieval of SpatialRefSys model objects.
 --
 Traceback (most recent call last):
   File "/usr/local/django/django-svn-
 trunk/django/contrib/gis/tests/test_spatialrefsys.py", line 59, in
 test01_retrieve
 self.assertEqual(srtext, srs.wkt)
 AssertionError: 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'
 != u'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'

 ==
 FAIL: Testing getting OSR objects from SpatialRefSys model objects.
 --
 Traceback (most recent call last):
   File "/usr/local/django/django-svn-
 trunk/django/contrib/gis/tests/test_spatialrefsys.py", line 86, in
 test02_osr
 self.assertEqual(srtext, srs.wkt)
 AssertionError: 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'
 != 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
 
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]'
 }}}


 


 $ sudo -u postgres psql postgis-template -c "select
 postgis_full_version();"
  POSTGIS="1.4.0" GEOS="3.1.1-CAPI-1.6.0" PROJ="Rel. 4.6.0, 21 Dec 2007"
 USE_STATS (procs from 1.4.0SVN need upgrade)

-- 
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] r11788 - in django/trunk/docs: ref/contrib releases

[noreply]

Author: lukeplant
Date: 2009-12-03 08:48:47 -0600 (Thu, 03 Dec 2009)
New Revision: 11788

Modified:
   django/trunk/docs/ref/contrib/csrf.txt
   django/trunk/docs/releases/1.2.txt
Log:
Added notes to "Features deprecated in 1.2" about CSRF and SMTPConnection



Modified: django/trunk/docs/ref/contrib/csrf.txt
===
--- django/trunk/docs/ref/contrib/csrf.txt  2009-12-03 06:28:26 UTC (rev 
11787)
+++ django/trunk/docs/ref/contrib/csrf.txt  2009-12-03 14:48:47 UTC (rev 
11788)
@@ -153,6 +153,8 @@
 `...@csrf_response_exempt`` decorator can be used to fix this, but only if the
 page doesn't also contain internal forms that require the token.
 
+.. _ref-csrf-upgrading-notes:
+
 Upgrading notes
 ---
 

Modified: django/trunk/docs/releases/1.2.txt
===
--- django/trunk/docs/releases/1.2.txt  2009-12-03 06:28:26 UTC (rev 11787)
+++ django/trunk/docs/releases/1.2.txt  2009-12-03 14:48:47 UTC (rev 11788)
@@ -26,13 +26,13 @@
 changes that developers must be aware of:
 
  * ``CsrfResponseMiddleware`` and ``CsrfMiddleware`` have been deprecated, and
-   will be removed completely in Django 1.4, in favour of a template tag that
+   will be removed completely in Django 1.4, in favor of a template tag that
should be inserted into forms.
 
  * All contrib apps use a ``csrf_protect`` decorator to protect the view.  This
requires the use of the csrf_token template tag in the template, so if you
-   have used custom templates for contrib views, you MUST READ THE UPGRADE
-   INSTRUCTIONS to fix those templates.
+   have used custom templates for contrib views, you MUST READ THE 
:ref:`UPGRADE
+   INSTRUCTIONS ` to fix those templates.
 
  * ``CsrfViewMiddleware`` is included in :setting:`MIDDLEWARE_CLASSES` by
default. This turns on CSRF protection by default, so that views that accept
@@ -72,8 +72,24 @@
 Features deprecated in 1.2
 ==
 
-None.
+CSRF response rewriting middleware
+--
 
+``CsrfResponseMiddleware``, the middleware that automatically inserted CSRF
+tokens into POST forms in outgoing pages, has been deprecated in favor of a
+template tag method (see above), and will be removed completely in Django
+1.4. ``CsrfMiddleware``, which includes the functionality of
+``CsrfResponseMiddleware`` and ``CsrfViewMiddleware`` has likewise been
+deprecated.
+
+Also, the CSRF module has moved from contrib to core, and the old imports are
+deprecated, as described in the :ref:`upgrading notes 
`.
+
+``SMTPConnection``
+--
+
+This class has been deprecated in favor of the new generic e-mail backends.
+
 What's new in Django 1.2
 
 

--

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] #12306: Checkbox (label, field) ordering

[Django]

#12306: Checkbox (label, field) ordering
-+--
 Reporter:  EoghanM  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Forms| Version:  1.1   
 Keywords:  label checkbox BooleanField  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 It is currently very difficult to reorder the default layout of fields:
 {{{
 My Label: 
 }}}

 For checkboxes, this should be either:
 {{{
  My Label
 }}}
  or
 {{{
  My Label
 }}}

 At the moment, in a template there's no way of knowing if a field is a
 !BooleanField (in order to special case the html), and I don't know how
 I'd edit widgets etc. to override the current layout.

 This has been touched on as a sore point elsewhere:

 http://www.mail-archive.com/django-
 develop...@googlegroups.com/msg21887.html

 http://stackoverflow.com/questions/572263/

 

 Where would be the best place to apply a patch for this?

  - At the form level: as a new argument to forms/forms.py:_html_output,
 called 'checkbox_row' which for e.g. table rows would look like:
 {{{
 u'%(field)s%(label)s%(help_text)s%(errors)s'
 }}}
  - At the field level: as a new boolean function 'is_checkbox'?
  - Both of the 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.

Re: [Django] #12302: Exception with utf8 message leads to DjangoUnicodeDecodeError

[Django]

#12302: Exception with utf8 message leads to DjangoUnicodeDecodeError
+---
  Reporter:  bjourne| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by wdoekes):

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

Comment:

 Hmyes.. I've tested this on my debian/lenny install and can confirm this.

 psycopg2 uses the client_encoding (as set through
 self.connection.set_client_encoding('UTF8') in
 django/db/backends/postgresql_psycopg2/base.py) for its error messages.

 Thus, to get this fixed, all DatabaseErrors raised by psycopg2 should have
 their .message.decode('utf-8')'d before they're exposed to the world.

-- 
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] #10768: Allow for Admin Actions to be applied to an empty QuerySet

[Django]

#10768: Allow for Admin Actions to be applied to an empty QuerySet
--+-
  Reporter:  andreplebl...@gmail.com  | Owner:  nobody 
Status:  reopened | Milestone: 
 Component:  django.contrib.admin |   Version:  SVN
Resolution:   |  Keywords:  actions
 Stage:  Design decision needed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Uh, sorry. See also: #12281

-- 
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] #10768: Allow for Admin Actions to be applied to an empty QuerySet

[Django]

#10768: Allow for Admin Actions to be applied to an empty QuerySet
--+-
  Reporter:  andreplebl...@gmail.com  | Owner:  nobody 
Status:  reopened | Milestone: 
 Component:  django.contrib.admin |   Version:  SVN
Resolution:   |  Keywords:  actions
 Stage:  Design decision needed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 See also: #10768

-- 
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] #12281: Admin Actions: Display Message on Empty Queryset

[Django]

#12281: Admin Actions: Display Message on Empty Queryset
-+--
  Reporter:  blinkylights| Owner:  nobody   

Status:  new | Milestone:   

 Component:  django.contrib.admin|   Version:  SVN  

Resolution:  |  Keywords:  admin actions 
change-list
 Stage:  Design decision needed  | Has_patch:  0

Needs_docs:  0   |   Needs_tests:  0

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

  * stage:  Accepted => Design decision needed

Comment:

 Actually, this is in conflict with #10768

-- 
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] #12281: Admin Actions: Display Message on Empty Queryset

[Django]

#12281: Admin Actions: Display Message on Empty Queryset
---+
  Reporter:  blinkylights  | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  admin actions 
change-list
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

  * component:  Contrib apps => django.contrib.admin

-- 
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] #12281: Admin Actions: Display Message on Empty Queryset

[Django]

#12281: Admin Actions: Display Message on Empty Queryset
---+
  Reporter:  blinkylights  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Contrib apps  |   Version:  SVN  
Resolution:|  Keywords:  admin actions change-list
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

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

Comment:

 Sounds fair enough

-- 
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] #12276: Adding a UnixDateTimeField to Models

[Django]

#12276: Adding a UnixDateTimeField to Models
---+
  Reporter:  nemesys   | Owner:  nobody 

Status:  closed| Milestone: 

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

Resolution:  wontfix   |  Keywords:  unix 
timestamp datetime
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 You're speaking to a brick wall here, nemesys. Bring it up in the django-
 dev google group if you're really passionate about it.

-- 
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] #12301: Template adds extra characters when using utf8 file encoding

[Django]

#12301: Template adds extra characters when using utf8 file encoding
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

-- 
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] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by simon):

 Looking great so far. Just one comment - the default __repr__ of a
 RawQuerySet is a little jarring, I thought for a moment something was
 broken or there was a logging message left in the code. I'd suggest
 something like  instead.

-- 
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] #1480: Don't Set TIME_ZONE unless it is explictly needed (or put it back to how you found it)

[Django]

#1480: Don't Set TIME_ZONE unless it is explictly needed (or put it back to how
you found it)
--+-
  Reporter:  i...@holsman.net  | Owner:  jedie
Status:  assigned | Milestone:  1.2  
 Component:  Core framework   |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  1|   Needs_tests:  1
Needs_better_patch:  1|  
--+-
Changes (by russellm):

  * version:  soc2009/multidb => SVN

Comment:

 Not sure why this was assigned to multidb.

-- 
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] #11828: Testing w/ contenttypes with syncdb causes an error django_content_types table does not exist

[Django]

#11828: Testing w/ contenttypes with syncdb causes an error django_content_types
table does not exist
--+-
  Reporter:  craig.kime...@gmail.com  | Owner:  robmadole   
   
Status:  closed   | Milestone:  
   
 Component:  Testing framework|   Version:  soc2009/multidb 
   
Resolution:  fixed|  Keywords:  multidb syncdb 
content_type
 Stage:  Design decision needed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 There may have been a problem at the time of the original report due to
 errors being raised; however, there have since been some major changes to
 the way the management commands interact with multiple database
 situations, so this doesn't appear to be a problem any more - I certainly
 can't reproduce the problem using the technique described.

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

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #11955: resetting an app appears to touch all configured dbs not just those that app uses

[Django]

#11955: resetting an app appears to touch all configured dbs not just those that
app uses
--+-
  Reporter:  kthhrv   | Owner:  nobody 
Status:  closed   | Milestone: 
 Component:  django-admin.py  |   Version:  soc2009/multidb
Resolution:  fixed|  Keywords: 
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 I'm fairly sure that this problem has been resolved by the change to the
 way the management commands interact with multidb setups.

-- 
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] #12058: resetting an app (manage.py reset) with a --database option results in an AttributeError: 'str' object has no attribute 'introspection'

[Django]

#12058: resetting an app (manage.py reset) with a --database option results in 
an
AttributeError: 'str' object has no attribute 'introspection'
--+-
  Reporter:  lemuelf  | Owner:  nobody 
Status:  closed   | Milestone: 
 Component:  django-admin.py  |   Version:  soc2009/multidb
Resolution:  fixed|  Keywords:  multidb
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Fixed inadvertently by a change to the way reset interacts with multiple
 databases.

-- 
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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+--
  Reporter:  etianen | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * version:  soc2009/multidb => SVN

Comment:

 This really isn't a multidb 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.

Re: [Django] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+--
  Reporter:  etianen | Owner:  nobody 
Status:  new | Milestone:  1.2
 Component:  Authentication  |   Version:  soc2009/multidb
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * version:  SVN => soc2009/multidb

-- 
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] #12295: A formset with no forms does not call self.clean() when self.is_valid() is called.

[Django]

#12295: A formset with no forms does not call self.clean() when self.is_valid() 
is
called.
--+-
  Reporter:  tomevans222  | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Forms|   Version:  1.1
Resolution:   |  Keywords:  formset
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by tomevans222):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * 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.