[Django] #14269: It is impossible to run full Django test suite on Oracle because there is 100m maxsize limit for test tablespace

[Django]

#14269: It is impossible to run full Django test suite on Oracle because there 
is
100m maxsize limit  for test tablespace
--+-
 Reporter:  andrewsk  |   Owner:  andrewsk  
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 If you are trying to run full django test suite on Oracle 10g or 11g,
 database throws an error that it is unable to allocate enough space.
 Bumping up limits up to 1000m fixes 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] #11633: Stop requiring DJANGO_SETTINGS_MODULE when using settings.configure

[Django]

#11633: Stop requiring DJANGO_SETTINGS_MODULE when using settings.configure
-+--
  Reporter:  masklinn| Owner:  nobody  
Status:  closed  | Milestone:  
 Component:  Core framework  |   Version:  SVN 
Resolution:  worksforme  |  Keywords:  settings
 Stage:  Accepted| Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by niall):

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

-- 
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] r13759 - in django/branches/soc2010/app-loading: django/conf django/core django/db/models tests/appcachetests

[noreply]

Author: arthurk
Date: 2010-09-12 00:34:58 -0500 (Sun, 12 Sep 2010)
New Revision: 13759

Modified:
   django/branches/soc2010/app-loading/django/conf/global_settings.py
   django/branches/soc2010/app-loading/django/core/apps.py
   django/branches/soc2010/app-loading/django/db/models/options.py
   django/branches/soc2010/app-loading/tests/appcachetests/runtests.py
Log:
[soc2010/app-loading] implement APP_CLASSES setting

Modified: django/branches/soc2010/app-loading/django/conf/global_settings.py
===
--- django/branches/soc2010/app-loading/django/conf/global_settings.py  
2010-09-12 02:09:17 UTC (rev 13758)
+++ django/branches/soc2010/app-loading/django/conf/global_settings.py  
2010-09-12 05:34:58 UTC (rev 13759)
@@ -170,6 +170,9 @@
 EMAIL_HOST_PASSWORD = ''
 EMAIL_USE_TLS = False
 
+# List of strings representing installed app classes.
+APP_CLASSES = ()
+
 # List of strings representing installed apps.
 INSTALLED_APPS = ()
 

Modified: django/branches/soc2010/app-loading/django/core/apps.py
===
--- django/branches/soc2010/app-loading/django/core/apps.py 2010-09-12 
02:09:17 UTC (rev 13758)
+++ django/branches/soc2010/app-loading/django/core/apps.py 2010-09-12 
05:34:58 UTC (rev 13759)
@@ -33,7 +33,7 @@
 return self.name
 
 def __repr__(self):
-return '' % self.name
+return '<%s: %s>' % (self.__class__.__name__, self.name)
 
 class AppCache(object):
 """
@@ -78,10 +78,19 @@
 try:
 if self.loaded:
 return
+for app_name in settings.APP_CLASSES:
+if app_name in self.handled:
+continue
+app_module, app_classname = app_name.rsplit('.', 1)
+app_module = import_module(app_module)
+app_class = getattr(app_module, app_classname)
+app_name = app_name.rsplit('.', 2)[0]
+self.load_app(app_name, True, app_class)
 for app_name in settings.INSTALLED_APPS:
 if app_name in self.handled:
 continue
 self.load_app(app_name, True)
+
 if not self.nesting_level:
 for app_name in self.postponed:
 self.load_app(app_name)
@@ -111,7 +120,7 @@
 finally:
 self.write_lock.release()
 
-def load_app(self, app_name, can_postpone=False):
+def load_app(self, app_name, can_postpone=False, app_class=App):
 """
 Loads the app with the provided fully qualified name, and returns the
 model module.
@@ -119,20 +128,7 @@
 self.handled[app_name] = None
 self.nesting_level += 1
 
-try:
-app_module = import_module(app_name)
-except ImportError:
-# If the import fails, we assume it was because an path to a
-# class was passed (e.g. "foo.bar.MyApp")
-# We split the app_name by the rightmost dot to get the path
-# and classname, and then try importing it again
-if not '.' in app_name:
-raise
-app_name, app_classname = app_name.rsplit('.', 1)
-app_module = import_module(app_name)
-app_class = getattr(app_module, app_classname)
-else:
-app_class = App
+app_module = import_module(app_name)
 
 # check if an app instance with that name already exists
 app_instance = self.find_app(app_name)
@@ -144,10 +140,11 @@
 app_instance_name = app_name
 app_instance = app_class(app_instance_name)
 app_instance.module = app_module
+app_instance.path = app_name
 self.app_instances.append(app_instance)
 self.installed_apps.append(app_name)
 
-# check if the app instance specifies a path to models
+# Check if the app instance specifies a path to models
 # if not, we use the models.py file from the package dir
 try:
 models_path = app_instance.models_path
@@ -179,7 +176,7 @@
 self.nesting_level -= 1
 app_instance.models_module = models
 return models
-
+
 def find_app(self, name):
 "Returns the App instance that matches name"
 if '.' in name:
@@ -211,9 +208,9 @@
 self._populate()
 self.write_lock.acquire()
 try:
-for app_name in self.installed_apps:
-if app_label == app_name.split('.')[-1]:
-mod = self.load_app(app_name, False)
+for app in self.app_instances:
+if app_label == app.name:
+mod = self.load_app(app.path, False)
 if mod is None:
 if emptyOK:
 return None

Modified: django/branches/soc2010/app-loading/django/db/models/options.py

Re: [Django] #4027: ability to make a copies of model instances

[Django]

#4027: ability to make a copies of model instances
+---
  Reporter:  Marek Kubica   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  db, copy
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  1  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by mitar):

 I also think it would be useful to have a best-practice method on object
 which covers this (or few of them for different kinds of cloning, all
 nicely documented) so that programmer does not need to care about
 internals of the objects (for example, what if objects will represent non-
 relational data someday, will m2m field be there, will there be something
 else to also copy?).

-- 
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] #14268: reset and sqlreset management commands should raise PendingDeprecationWarning for 1.3

[Django]

#14268: reset and sqlreset management commands should raise
PendingDeprecationWarning for 1.3
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Uncategorized  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   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] #14226: Bug in dumpdata dependency calculation involving ManyToManyFields

[Django]

#14226: Bug in dumpdata dependency calculation involving ManyToManyFields
+---
  Reporter:  aneil  | Owner:  outofculture 
Status:  assigned   | Milestone:   
 Component:  Serialization  |   Version:  1.2  
Resolution: |  Keywords:  easy-pickings
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  1
Needs_better_patch:  1  |  
+---
Comment (by outofculture):

 The proposed code patch appeared to break
 fixtures_regress:test_dependency_sorting_dangling, but on closer
 inspection, should not be considered to be the case.  That test explicitly
 expected the dangling, un-related model to have a position in the
 resultant dependencies, but such an expectation is 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] #2225: 'manage.py sql ...' gets confused when using tables from separate apps

[Django]

#2225: 'manage.py sql ...' gets confused when using tables from separate apps
---+
  Reporter:  Lucas Hazel   | Owner:  
glassresistor
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords: 
  
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Changes (by glassresistor):

  * needs_docs:  1 => 0

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

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

Re: [Django] #2225: 'manage.py sql ...' gets confused when using tables from separate apps

[Django]

#2225: 'manage.py sql ...' gets confused when using tables from separate apps
---+
  Reporter:  Lucas Hazel   | Owner:  
glassresistor
Status:  new   | 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 glassresistor):

  * owner:  nobody => glassresistor
  * needs_better_patch:  1 => 0

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

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

Re: [Django] #5714: Date/Time fields' clean methods need strip()

[Django]

#5714: Date/Time fields' clean methods need strip()
--+-
  Reporter:  Simon Litchfield   | Owner:  
nobody
Status:  reopened | Milestone:  
  
 Component:  Forms|   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  1   
  
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * 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] #14060: PostGISAdapter needs to properly cast input for comparisons on geography columns.

[Django]

#14060: PostGISAdapter needs to properly cast input for comparisons on geography
columns.
-+--
  Reporter:  jbronn  | Owner:  jbronn
Status:  closed  | Milestone:  1.3   
 Component:  GIS |   Version:  1.2   
Resolution:  fixed   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by jbronn):

 PostGIS will properly cast internally geography types (hence why `&&`
 operator works).  The root cause of the issue is that despite the
 documentation, the `~=` operator was never implemented for geography
 types.  I had a [http://logs.qgis.org/postgis/%23postgis.2010-08-09.log
 discussion with Paul Ramsey] in `#postgis` about this issue, and he
 confirmed it was a "doc mistake" and "only && was implemented for
 geography."

-- 
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] r13758 - in django/branches/releases/1.2.X/django/contrib/gis: db/backends/postgis tests/geogapp

[noreply]

Author: jbronn
Date: 2010-09-11 21:09:17 -0500 (Sat, 11 Sep 2010)
New Revision: 13758

Modified:
   
django/branches/releases/1.2.X/django/contrib/gis/db/backends/postgis/operations.py
   django/branches/releases/1.2.X/django/contrib/gis/tests/geogapp/tests.py
Log:
[1.2.X] Fixed #14060 -- PostGIS never implemented the `~=` operator for 
geography types, so removed support for it.

Backport of r13757 from trunk.


Modified: 
django/branches/releases/1.2.X/django/contrib/gis/db/backends/postgis/operations.py
===
--- 
django/branches/releases/1.2.X/django/contrib/gis/db/backends/postgis/operations.py
 2010-09-12 02:07:04 UTC (rev 13757)
+++ 
django/branches/releases/1.2.X/django/contrib/gis/db/backends/postgis/operations.py
 2010-09-12 02:09:17 UTC (rev 13758)
@@ -233,8 +233,6 @@
 })
 self.geography_operators = {
 'bboverlaps' : PostGISOperator('&&'),
-'exact' : PostGISOperator('~='),
-'same_as' : PostGISOperator('~='),
 }
 
 # Creating a dictionary lookup of all GIS terms for PostGIS.

Modified: 
django/branches/releases/1.2.X/django/contrib/gis/tests/geogapp/tests.py
===
--- django/branches/releases/1.2.X/django/contrib/gis/tests/geogapp/tests.py
2010-09-12 02:07:04 UTC (rev 13757)
+++ django/branches/releases/1.2.X/django/contrib/gis/tests/geogapp/tests.py
2010-09-12 02:09:17 UTC (rev 13758)
@@ -44,6 +44,10 @@
 # `...@` operator not available.
 self.assertRaises(ValueError, 
City.objects.filter(point__contained=z.poly).count)
 
+# Regression test for #14060, `~=` was never really implemented for 
PostGIS.
+htown = City.objects.get(name='Houston')
+self.assertRaises(ValueError, City.objects.get, 
point__exact=htown.point)
+
 def test05_geography_layermapping(self):
 "Testing LayerMapping support on models with geography fields."
 # There is a similar test in `layermap` that uses the same data set,

-- 
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] #14221: Mashed Sentences in Doc

[Django]

#14221: Mashed Sentences in Doc
--+-
  Reporter:  Grant   | Owner:  dwillis
Status:  assigned | Milestone:  1.3
 Component:  Documentation|   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Ready for checkin| Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by dwillis):

  * 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-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] #14221: Mashed Sentences in Doc

[Django]

#14221: Mashed Sentences in Doc
--+-
  Reporter:  Grant   | Owner:  dwillis
Status:  new  | Milestone:  1.3
 Component:  Documentation|   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Ready for checkin| Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by dwillis):

  * has_patch:  0 => 1
  * stage:  Accepted => Ready for checkin
  * component:  Uncategorized => Documentation
  * milestone:  => 1.3

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14221: Mashed Sentences in Doc

[Django]

#14221: Mashed Sentences in Doc
--+-
  Reporter:  Grant   | Owner:  dwillis
Status:  new  | Milestone: 
 Component:  Uncategorized|   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by dwillis):

  * owner:  anonymous => dwillis
  * 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] #7048: Support clearing FileFields with ModelForms

[Django]

#7048: Support clearing FileFields with ModelForms
---+
  Reporter:  jarrow| Owner:  carljm
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Comment (by carljm):

 Added a new patch with these design choices:

  * No file deleting.
  * Clearability should be the default behavior of a
 forms.FileField(required=False) - and thus also
 models.FileField(blank=True).formfield(). It's a bug that FileFields are
 currently not clearable. Thus, no Meta options or extra field arguments
 are needed.
  * This involves a minor backwards incompatibility in form rendering (a
 possible checkbox where there was not one previously), which is documented
 in the 1.3 release notes.
  * It doesn't make sense to have a clearable file input that doesn't
 display the current value of the field, so that behavior is moved from
 AdminFileWidget to ClearableFileInput (which AdminFileWidget inherits).
  * The HTML rendering of the ClearableFileInput is customizable by
 subclassing and overriding some class attributes.
  * Contradictory input (checking the clear checkbox and simultaneously
 uploading a new file) results in a form validation error.

 All of these design choices were checked in person with at least one core
 committer at the sprint, mostly with Malcolm.

 For reviewers more comfortable with git, here is the github compare URL
 for my working branch for this patch:
 http://github.com/carljm/django/compare/master...ticket_7048

-- 
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] #5877: Force manage.py to output UTF-8 to avoid UnicodeEncodeErrors

[Django]

#5877: Force manage.py to output UTF-8 to avoid UnicodeEncodeErrors
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  django-admin.py |   Version:  SVN   
Resolution:  worksforme  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 This is a very old report, with a diff that no longer applies, without a
 test case that actually describes how the problem can actually be
 replicated (I have no idea what workstyle-py is, and the report doesn't
 tell me where I can get it from).

 I'm also reasonably certain that this has been resolved as a side effect
 of other changes (i.e., I've fixed other bugs about unicode in management
 output, like #12849). Closing worksforme; please reopen if you have a
 concrete example that fails.

-- 
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] #11041: Document all QuerySet methods in QuerySet API

[Django]

#11041: Document all QuerySet methods in QuerySet API
+---
  Reporter:  idangazit  | Owner:  dwillis
Status:  assigned   | Milestone:  1.3
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by dwillis):

 #14004 documents the update method, so I'll focus on documenting the
 delete method here.

-- 
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] #1820: Autogenerated ManyToMany fields can generate too long identifiers for mysql to handle

[Django]

#1820: Autogenerated ManyToMany fields can generate too long identifiers for 
mysql
to handle
---+
  Reporter:  re...@diji.biz| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  fixed |  Keywords:  mysql 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by glassresistor):

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

Comment:

 Have tried this in the current trunk it is no longer a problem
 `accomodationunit_id_refs_id_6c62fa96`
 This is now what is being generated.

-- 
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] #14226: Bug in dumpdata dependency calculation involving ManyToManyFields

[Django]

#14226: Bug in dumpdata dependency calculation involving ManyToManyFields
+---
  Reporter:  aneil  | Owner:  outofculture 
Status:  assigned   | Milestone:   
 Component:  Serialization  |   Version:  1.2  
Resolution: |  Keywords:  easy-pickings
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  1
Needs_better_patch:  1  |  
+---
Comment (by outofculture):

 also, this test does not account for russelm's concerns.

-- 
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] r13756 - django/branches/releases/1.2.X/django/contrib/gis/tests

[noreply]

Author: jbronn
Date: 2010-09-11 20:44:51 -0500 (Sat, 11 Sep 2010)
New Revision: 13756

Modified:
   django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py
Log:
[1.2.X] Fixed regression in running the GeoDjango test suite after r13670 with 
addition of `GeoDjangoTestSuiteRunner` (replaces `run_gis_tests`, which is now 
a stub).

Backport of r13755 from trunk.


Modified: django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py
===
--- django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py 
2010-09-12 01:40:42 UTC (rev 13755)
+++ django/branches/releases/1.2.X/django/contrib/gis/tests/__init__.py 
2010-09-12 01:44:51 UTC (rev 13756)
@@ -1,115 +1,108 @@
 import sys
+import unittest
 
+from django.conf import settings
+from django.db.models import get_app
+from django.test.simple import build_suite, DjangoTestSuiteRunner
+
 def run_tests(*args, **kwargs):
 from django.test.simple import run_tests as base_run_tests
 return base_run_tests(*args, **kwargs)
 
-def geo_suite():
-"""
-Builds a test suite for the GIS package.  This is not named
-`suite` so it will not interfere with the Django test suite (since
-spatial database tables are required to execute these tests on
-some backends).
-"""
-from django.conf import settings
-from django.contrib.gis.geos import GEOS_PREPARE
-from django.contrib.gis.gdal import HAS_GDAL
-from django.contrib.gis.utils import HAS_GEOIP
-from django.contrib.gis.tests.utils import postgis, mysql
-from django.db import connection
-from django.utils.importlib import import_module
+def run_gis_tests(test_labels, verbosity=1, interactive=True, failfast=False, 
extra_tests=None):
+import warnings
+warnings.warn(
+'The run_gis_tests() test runner has been deprecated in favor of 
GeoDjangoTestSuiteRunner.',
+PendingDeprecationWarning
+)
+test_runner = GeoDjangoTestSuiteRunner(verbosity=verbosity, 
interactive=interactive, failfast=failfast)
+return test_runner.run_tests(test_labels, extra_tests=extra_tests)
 
-gis_tests = []
+class GeoDjangoTestSuiteRunner(DjangoTestSuiteRunner):
 
-# Adding the GEOS tests.
-from django.contrib.gis.geos import tests as geos_tests
-gis_tests.append(geos_tests.suite())
+def setup_test_environment(self, **kwargs):
+super(GeoDjangoTestSuiteRunner, self).setup_test_environment(**kwargs)
 
-# Tests that require use of a spatial database (e.g., creation of models)
-test_apps = ['geoapp', 'relatedapp']
-if postgis and connection.ops.geography:
-# Test geography support with PostGIS 1.5+.
-test_apps.append('geogapp')
+from django.db import connection
+from django.contrib.gis.geos import GEOS_PREPARE
+from django.contrib.gis.gdal import HAS_GDAL
 
-# Tests that do not require setting up and tearing down a spatial database.
-test_suite_names = [
-'test_measure',
-]
+# Getting and storing the original values of INSTALLED_APPS and
+# the ROOT_URLCONF.
+self.old_installed = settings.INSTALLED_APPS
+self.old_root_urlconf = settings.ROOT_URLCONF
 
-if HAS_GDAL:
-# These tests require GDAL.
-if not mysql:
-test_apps.append('distapp')
+# Tests that require use of a spatial database (e.g., creation of 
models)
+self.geo_apps = ['geoapp', 'relatedapp']
+if connection.ops.postgis and connection.ops.geography:
+# Test geography support with PostGIS 1.5+.
+self.geo_apps.append('geogapp')
 
-# Only PostGIS using GEOS 3.1+ can support 3D so far.
-if postgis and GEOS_PREPARE:
-test_apps.append('geo3d')
+if HAS_GDAL:
+# The following GeoDjango test apps depend on GDAL support.
+if not connection.ops.mysql:
+self.geo_apps.append('distapp')
 
-test_suite_names.extend(['test_spatialrefsys', 'test_geoforms'])
-test_apps.append('layermap')
-
-# Adding the GDAL tests.
-from django.contrib.gis.gdal import tests as gdal_tests
-gis_tests.append(gdal_tests.suite())
-else:
-print >>sys.stderr, "GDAL not available - no tests requiring GDAL will 
be run."
+# 3D apps use LayerMapping, which uses GDAL.
+if connection.ops.postgis and GEOS_PREPARE:
+self.geo_apps.append('geo3d')
 
-if HAS_GEOIP and hasattr(settings, 'GEOIP_PATH'):
-test_suite_names.append('test_geoip')
+self.geo_apps.append('layermap')
 
-# Adding the rest of the suites from the modules specified
-# in the `test_suite_names`.
-for suite_name in test_suite_names:
-tsuite = import_module('django.contrib.gis.tests.' + suite_name)
-gis_tests.append(tsuite.suite())
+# Constructing the new 

[Changeset] r13755 - django/trunk/django/contrib/gis/tests

[noreply]

Author: jbronn
Date: 2010-09-11 20:40:42 -0500 (Sat, 11 Sep 2010)
New Revision: 13755

Modified:
   django/trunk/django/contrib/gis/tests/__init__.py
Log:
Fixed regression in running the GeoDjango test suite after r13670 with addition 
of `GeoDjangoTestSuiteRunner` (replaces `run_gis_tests`, which is now a stub).


Modified: django/trunk/django/contrib/gis/tests/__init__.py
===
--- django/trunk/django/contrib/gis/tests/__init__.py   2010-09-11 21:28:00 UTC 
(rev 13754)
+++ django/trunk/django/contrib/gis/tests/__init__.py   2010-09-12 01:40:42 UTC 
(rev 13755)
@@ -1,115 +1,108 @@
 import sys
+import unittest
 
+from django.conf import settings
+from django.db.models import get_app
+from django.test.simple import build_suite, DjangoTestSuiteRunner
+
 def run_tests(*args, **kwargs):
 from django.test.simple import run_tests as base_run_tests
 return base_run_tests(*args, **kwargs)
 
-def geo_suite():
-"""
-Builds a test suite for the GIS package.  This is not named
-`suite` so it will not interfere with the Django test suite (since
-spatial database tables are required to execute these tests on
-some backends).
-"""
-from django.conf import settings
-from django.contrib.gis.geos import GEOS_PREPARE
-from django.contrib.gis.gdal import HAS_GDAL
-from django.contrib.gis.utils import HAS_GEOIP
-from django.contrib.gis.tests.utils import postgis, mysql
-from django.db import connection
-from django.utils.importlib import import_module
+def run_gis_tests(test_labels, verbosity=1, interactive=True, failfast=False, 
extra_tests=None):
+import warnings
+warnings.warn(
+'The run_gis_tests() test runner has been deprecated in favor of 
GeoDjangoTestSuiteRunner.',
+PendingDeprecationWarning
+)
+test_runner = GeoDjangoTestSuiteRunner(verbosity=verbosity, 
interactive=interactive, failfast=failfast)
+return test_runner.run_tests(test_labels, extra_tests=extra_tests)
 
-gis_tests = []
+class GeoDjangoTestSuiteRunner(DjangoTestSuiteRunner):
 
-# Adding the GEOS tests.
-from django.contrib.gis.geos import tests as geos_tests
-gis_tests.append(geos_tests.suite())
+def setup_test_environment(self, **kwargs):
+super(GeoDjangoTestSuiteRunner, self).setup_test_environment(**kwargs)
+
+from django.db import connection
+from django.contrib.gis.geos import GEOS_PREPARE
+from django.contrib.gis.gdal import HAS_GDAL
 
-# Tests that require use of a spatial database (e.g., creation of models)
-test_apps = ['geoapp', 'relatedapp']
-if postgis and connection.ops.geography:
-# Test geography support with PostGIS 1.5+.
-test_apps.append('geogapp')
+# Getting and storing the original values of INSTALLED_APPS and
+# the ROOT_URLCONF.
+self.old_installed = settings.INSTALLED_APPS
+self.old_root_urlconf = settings.ROOT_URLCONF
 
-# Tests that do not require setting up and tearing down a spatial database.
-test_suite_names = [
-'test_measure',
-]
+# Tests that require use of a spatial database (e.g., creation of 
models)
+self.geo_apps = ['geoapp', 'relatedapp']
+if connection.ops.postgis and connection.ops.geography:
+# Test geography support with PostGIS 1.5+.
+self.geo_apps.append('geogapp')
 
-if HAS_GDAL:
-# These tests require GDAL.
-if not mysql:
-test_apps.append('distapp')
+if HAS_GDAL:
+# The following GeoDjango test apps depend on GDAL support.
+if not connection.ops.mysql:
+self.geo_apps.append('distapp')
 
-# Only PostGIS using GEOS 3.1+ can support 3D so far.
-if postgis and GEOS_PREPARE:
-test_apps.append('geo3d')
+# 3D apps use LayerMapping, which uses GDAL.
+if connection.ops.postgis and GEOS_PREPARE:
+self.geo_apps.append('geo3d')
 
-test_suite_names.extend(['test_spatialrefsys', 'test_geoforms'])
-test_apps.append('layermap')
-
-# Adding the GDAL tests.
-from django.contrib.gis.gdal import tests as gdal_tests
-gis_tests.append(gdal_tests.suite())
-else:
-print >>sys.stderr, "GDAL not available - no tests requiring GDAL will 
be run."
+self.geo_apps.append('layermap')
 
-if HAS_GEOIP and hasattr(settings, 'GEOIP_PATH'):
-test_suite_names.append('test_geoip')
+# Constructing the new INSTALLED_APPS, and including applications 
+# within the GeoDjango test namespace (`self.geo_apps`).
+new_installed =  ['django.contrib.sites',
+  'django.contrib.sitemaps',
+  'django.contrib.gis',
+  ]
+new_installed.extend(['django.contrib.gis.tests.%s' % app
+ 

Re: [Django] #13640: add_filter in django/db/models/ sql/query.py causes exception when model have 'evaluate' attribute

[Django]

#13640: add_filter in django/db/models/ sql/query.py causes exception when model
have 'evaluate' attribute
---+
  Reporter:  LukaszKorzybski   | Owner:  tobias
Status:  assigned  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by tobias):

 I don't know enough about the ORM to know which of these makes the most
 sense.  All tests pass with each patch.

-- 
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] #14226: Bug in dumpdata dependency calculation involving ManyToManyFields

[Django]

#14226: Bug in dumpdata dependency calculation involving ManyToManyFields
+---
  Reporter:  aneil  | Owner:  outofculture 
Status:  assigned   | Milestone:   
 Component:  Serialization  |   Version:  1.2  
Resolution: |  Keywords:  easy-pickings
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  1
Needs_better_patch:  1  |  
+---
Comment (by outofculture):

 the patch to add tests will only be usefully applied after the genocide of
 doc tests has been merged into master.

-- 
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] #13706: dbrouter uses wrong database on many2many addition

[Django]

#13706: dbrouter uses wrong database on many2many addition
---+
  Reporter:  cheerios  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by tobias):

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

Comment:

 Please provide a more complete example.

-- 
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] #12196: EmailField reject this email address tosha.....@gmail.com

[Django]

#12196: EmailField reject this email address tosha.@gmail.com
+---
  Reporter:  mtsyganov  | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   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:  Accepted => Ready for checkin

Comment:

 I've updated the patch to use the new `EmailValidator`.

-- 
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] #5848: post_syncdb signal callbacks: argument 'created_models' is sometimes a list, sometimes a set

[Django]

#5848: post_syncdb signal callbacks: argument 'created_models' is sometimes a
list, sometimes a set
+---
  Reporter:  s...@robots.org.uk  | Owner:  nobody   

Status:  new| Milestone:
   
 Component:  Core framework |   Version:  SVN   
   
Resolution: |  Keywords:  post_syncdb signal 
created_models
 Stage:  Ready for checkin  | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Accepted => Ready for checkin

Comment:

 Actually -- looking at the patch, it's pretty much RFC, although the patch
 needs to be updated (since the Python 2.3 protection is no longer
 required).

-- 
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] #5848: post_syncdb signal callbacks: argument 'created_models' is sometimes a list, sometimes a set

[Django]

#5848: post_syncdb signal callbacks: argument 'created_models' is sometimes a
list, sometimes a set
+---
  Reporter:  s...@robots.org.uk  | Owner:  nobody   

Status:  new| Milestone:
   
 Component:  Core framework |   Version:  SVN   
   
Resolution: |  Keywords:  post_syncdb signal 
created_models
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Design decision needed => Accepted

Comment:

 This should be a set. It's not ordered, you can't have duplicates, and
 membership of collection is an important operation.

-- 
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] #13710: raw() sql bug when using a model with many fields with long names

[Django]

#13710: raw() sql bug when using a model with many fields with long names
---+
  Reporter:  Renskers  | Owner:  tobias 
 
Status:  closed| Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.2
 
Resolution:  invalid   |  Keywords:  raw sql 
joins deffered class
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by tobias):

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

Comment:

 As far as I can tell, add_to_class is an undocumented method and hence
 unsupported.  Probably just best if you ensure that you pass in non-
 unicode strings.

-- 
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] #5767: EmailField should render as a mailto anchor in admin list page

[Django]

#5767: EmailField should render as a mailto anchor in admin list page
-+--
  Reporter:  hax | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  django.contrib.admin|   Version:  newforms-admin   
 
Resolution:  wontfix |  Keywords:  nfa-someday 
EmailField
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  1   |  
-+--
Changes (by mtredinnick):

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

Comment:

 We don't do this kind of thing for URL fields, so it would be
 inconsistent. We also have one column int he changelist page that is a
 link that goes to add form and that would cause confusion about what the
 links do.

 Creating a clickable column in the admin list page is easy enough: write a
 function and use that in the "fields" attribute (enabling linking for that
 function, etc), so creating this effect can be done in admin classes
 without requiring Django source changes.

-- 
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] #5745: MySQL Collations/Charsets and Engines

[Django]

#5745: MySQL Collations/Charsets and Engines
---+
  Reporter:  Armin Ronacher| 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 |  
---+
Comment (by mitsuhiko):

 Damn. That was not a very friendly written ticket. :)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5745: MySQL Collations/Charsets and Engines

[Django]

#5745: MySQL Collations/Charsets and Engines
---+
  Reporter:  Armin Ronacher| 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 mtredinnick):

  * stage:  Design decision needed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5749: Add field_name as a key on the _html_output dict

[Django]

#5749: Add field_name as a key on the _html_output dict
--+-
  Reporter:  SmileyChris  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Forms|   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * stage:  Design decision needed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5742: `static_pattern` shortcut for serving static files

[Django]

#5742: `static_pattern` shortcut for serving static files
-+--
  Reporter:  SmileyChris | Owner:  SmileyChris
Status:  closed  | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  wontfix |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

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

Comment:

 Not going to take this. We might add a commented out pattern for using the
 static server to the default project.

-- 
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] #5652: Straightforward use of startproject command results in broken "Show on Site" link in admin

[Django]

#5652: Straightforward use of startproject command results in broken "Show on
Site" link in admin
+---
  Reporter:  Leo Hourvitz   | Owner:  
nobody 
Status:  new| Milestone:
 
 Component:  django-admin.py|   Version:  SVN   
 
Resolution: |  Keywords:  
SITE_ID
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Sites is still needed by admin, at least for "view on site", unless #8960
 has been quietly fixed by some change that did not reference that
 ticket...

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5714: Date/Time fields' clean methods need strip()

[Django]

#5714: Date/Time fields' clean methods need strip()
--+-
  Reporter:  Simon Litchfield   | Owner:  
nobody
Status:  reopened | Milestone:  
  
 Component:  Forms|   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Comment (by mtredinnick):

 The other ticket isn't a real-dupe. This particular data type is a no-
 brainer. We should strip the spaces before strptime'ing. Accepted.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5349: Shouldn't the item_enclosure_url automatically prefixed with the current site?

[Django]

#5349: Shouldn't the item_enclosure_url automatically prefixed with the current
site?
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Design decision needed => Accepted

Comment:

 Accepted, although the implementation needs to be aware of base paths in
 Atom, etc.

-- 
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] #4031: Translate to a specified language (not necessarily the current session language)

[Django]

#4031: Translate to a specified language (not necessarily the current session
language)
-+--
  Reporter:  t...@barnettweb.net | Owner:  nobody   
  
Status:  closed  | Milestone:   
  
 Component:  Internationalization|   Version:  SVN  
  
Resolution:  wontfix |  Keywords:  translatation 
translate i18n i18n-nofix
 Stage:  Design decision needed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

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

Comment:

 My comment from 2007 still kind of holds. Given the relative scarcity of
 this, it's not up for inclusion in Django at the moment.

-- 
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] #14263: Allow fields to support custom double-underscore lookup methods

[Django]

#14263: Allow fields to support custom double-underscore lookup methods
---+
  Reporter:  carljm| 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 carljm):

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

Comment:

 Marking accepted per design discussion with core devs (Russell, Malcolm,
 Jannis) at sprint.

-- 
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] #14262: Helper for "get_something as varname" template tag pattern

[Django]

#14262: Helper for "get_something as varname" template tag pattern
-+--
 Reporter:  carljm   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  SVN   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 It's a common pattern to write a template tag that fetches some data and
 sticks it in a context variable. Currently writing these tags requires
 writing a full-blown parsing function and Node class, which is mostly
 boilerplate except for the render() method. It would be good to have a
 template tag helper for writing tags that follow this pattern. (Similar to
 simple_tag, except allowing for updating the context).

-- 
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.3   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

  * stage:  Design decision needed => Accepted

Comment:

 Proxy models should also proxy the permissions of the model they are
 shadowing. So any `app_label` check should first check if the instance is
 a proxy and look in the parent's `app_label` 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] #13894: Disable upstream caching with messages framework

[Django]

#13894: Disable upstream caching with messages framework
-+--
  Reporter:  bronger | Owner:  nobody
Status:  new | Milestone:
 Component:  Contrib apps|   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by bronger):

 First of all: As we had to find out, "{{{add_never_cache_headers}}}"
 doesn't work.  It only sets "Expires" and "Cache-control/max-age" but it
 also sets "ETag" and "Last-Modified" so that the next request may be taken
 from the browser's cache.  (It's strange that such a function is called
 "{{{add_never_cache_headers}}}".  It should be called
 "{{{add_expire_immediately_headers}}}".  Anyway.)

 Instead, we use

 {{{
 if request._messages.used:
 del response["ETag"]
 del response["Last-Modified"]
 response["Expires"] = "Fri, 01 Jan 1990 00:00:00 GMT"
 # FixMe: One should check whether the following settings are
 # sensible.
 response["Pragma"] = "no-cache"
 response["Cache-Control"] = "no-cache, no-store, max-age=0, must-
 revalidate, private"
 }}}

 Now to your question.  You're absolutely right.  We don't run into this
 problem because messages are shown on pages which have recently changed
 anyway (the message reads "You have successfully changed ...").  If we had
 a message saying "Editing aborted. Nothing was changed.", it would not get
 displayed.

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