Re: [Django] #32744: Template changes cause dev server to reload

[Django]

#32744: Template changes cause dev server to reload
-+--
 Reporter:  Ryan P Kilby |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Ryan P Kilby):

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


Comment:

 Hi Carlton,
 long time :)

 Figured out how to reproduce the issue:

 - Ensure `TEMPLATES["DIRS"]` contains a directory path that's a string
 instead of a `Path` object.
 - Add a template to that directory, point a view to that template.
 - Modify/save the template, observe reload

 Specifically, the failure is occurring in the
 [https://github.com/django/django/pull/12928/files#diff-
 85e705dc6a3e8563ae082481a870c003b31fc639accfa6133e47477c9e964c90R48
 template_changed] handler's `if template_dir in file_path.parents` check.
 As `template_dir` is a string, it fails the comparison to the parent
 `Path`s. While the failure occurs here, I'm guessing that
 `loader.get_dirs` should normalize its directories to `Path`s.

 Also, you'd only hit this issue when upgrading an older settings module.
 New projects are setup to use `Path`s, while old projects would be
 building paths with `os.path.join()`.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.28741f8aafde8737f6fe1bdb71cea253%40djangoproject.com.

Re: [Django] #32338: Accessibility issues with Django forms RadioSelect and CheckboxSelectMultiple

[Django]

#32338: Accessibility issues with Django forms RadioSelect and
CheckboxSelectMultiple
-+-
 Reporter:  Thibaud Colas|Owner:  David
 |  Smith
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  forms, wcag|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by David Smith):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.c294ba824131811563eec5f23aa77cdf%40djangoproject.com.

Re: [Django] #32721: Geometry Index with PostGIS using schema

[Django]

#32721: Geometry Index with PostGIS using schema
-+-
 Reporter:  Alan D. Snow |Owner:  Alan D.
 |  Snow
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"29345aecf6e8d53ccb3577a3762bb0c263f7558d" 29345aec]:
 {{{
 #!CommitTicketReference repository=""
 revision="29345aecf6e8d53ccb3577a3762bb0c263f7558d"
 Fixed #32721 -- Fixed migrations crash when adding namespaced spatial
 indexes on PostGIS.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.80750b699454747f33acb0a886850de8%40djangoproject.com.

Re: [Django] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+-
 Reporter:  Christian Karrié |Owner:  jbronn
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgis 2.0  | Triage Stage:  Design
 |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c6d88a18726118c694b6ac4c308642efbe84c151" c6d88a1]:
 {{{
 #!CommitTicketReference repository=""
 revision="c6d88a18726118c694b6ac4c308642efbe84c151"
 Refs #16455 -- Added test for using opclasses on indexes for
 multidimensional geometry fields on PostGIS.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9c99326ff5bbe5ea49c795197adea5c9%40djangoproject.com.

Re: [Django] #32721: Geometry Index with PostGIS using schema

[Django]

#32721: Geometry Index with PostGIS using schema
-+-
 Reporter:  Alan D. Snow |Owner:  Alan D.
 |  Snow
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"99bc67a9e79256d8a2fcd5742e33a5e79c056539" 99bc67a]:
 {{{
 #!CommitTicketReference repository=""
 revision="99bc67a9e79256d8a2fcd5742e33a5e79c056539"
 Refs #32721 -- Made PostGISSchemaEditor._create_index_sql() call
 super()._create_index_sql().
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a5d92eec0b6bbeaf243e764520db030a%40djangoproject.com.

Re: [Django] #32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.

[Django]

#32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.
-+-
 Reporter:  Jakub Kleň   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  3.2.1 file model | Triage Stage:  Accepted
  filefield fieldfile|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"63f0d7a0f6b6d762b8c15894c531b687ac843c66" 63f0d7a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="63f0d7a0f6b6d762b8c15894c531b687ac843c66"
 [2.2.x] Refs #32718 -- Fixed file_storage.test_generate_filename and
 model_fields.test_filefield tests on Python 3.5.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.f552202bc2a3990f5109f226dd90cd40%40djangoproject.com.

Re: [Django] #32747: CacheHandler initialize unused caches. (was: CacheHandler logic issue)

[Django]

#32747: CacheHandler initialize unused caches.
-+
 Reporter:  Alexander Ebral  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  3.2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * cc: Florian Apolloner (added)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. I agree this can cause a performance regression, we
 shouldn't initialize unused caches unnecessarily. As far as I'm aware we
 can restore the previous behavior with:
 {{{
 diff --git a/django/core/cache/__init__.py b/django/core/cache/__init__.py
 index 05ef3897d0..c008ed1125 100644
 --- a/django/core/cache/__init__.py
 +++ b/django/core/cache/__init__.py
 @@ -43,6 +43,8 @@ class CacheHandler(BaseConnectionHandler):
  ) from e
  return backend_cls(location, params)

 +def all(self):
 +return [self[alias] for alias in self if
 hasattr(self._connections, alias)]

  caches = CacheHandler()

 }}}

 Regression in 98e05ccde440cc9b768952cc10bc8285f4924e1f.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.53823ad781b29ebd9b421e814871f9be%40djangoproject.com.

Re: [Django] #32748: Django admin Filefield in Tabularinline does not work

[Django]

#32748: Django admin Filefield in Tabularinline does not work
---+--
 Reporter:  mypseudo   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  3.2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by mypseudo):

 * status:  new => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.60cfd65e4393b5c1c441b1682616108c%40djangoproject.com.

Re: [Django] #32748: Django admin Filefield in Tabularinline does not work

[Django]

#32748: Django admin Filefield in Tabularinline does not work
---+--
 Reporter:  mypseudo   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by mypseudo:

Old description:

> I've a Child model with ForeignKey to Parent, my Child has a FileField.
> When I register that in the admin with Tabularinline, there is no problem
> at first sight, but then when I click on "Save", there is no error but
> the file is not recorded, when I return to previous page (and reload the
> page), there is still the old file.

New description:

 I've a Child model with ForeignKey to Parent, my Child has a FileField.
 When I register that in the admin with Tabularinline, there is no problem
 at first sight, but then when I click on "Save", after having edited the
 filefield, there is no error but the file is not recorded, when I return
 to previous page (and reload the page), there is still the old file.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a995c02dc2f440575404f0f72f375be5%40djangoproject.com.

[Django] #32748: Django admin Filefield in Tabularinline does not work

[Django]

#32748: Django admin Filefield in Tabularinline does not work
-+
   Reporter:  mypseudo   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I've a Child model with ForeignKey to Parent, my Child has a FileField.
 When I register that in the admin with Tabularinline, there is no problem
 at first sight, but then when I click on "Save", there is no error but the
 file is not recorded, when I return to previous page (and reload the
 page), there is still the old file.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.9536021421cd682981c68e93db66f503%40djangoproject.com.

[Django] #32747: CacheHandler logic issue

[Django]

#32747: CacheHandler logic issue
---+
   Reporter:  Alexander Ebral  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (Cache system)  |Version:  3.2
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 After the commit:
 
https://github.com/django/django/commit/98e05ccde440cc9b768952cc10bc8285f4924e1f
 logic of the method "all" from CacheHandler class was changed.

 Before:

 {{{
 def all(self):
 return getattr(self._caches, 'caches', {}).values()
 }}}


 This method returned connections that were created in !__getitem!__



 Now:

 {{{
 def all(self):
 return [self[alias] for alias in self]
 }}}


 Connections return for all "CACHES" from settings.py  (in case of absence
 - they are forcibly created in self[alias])

 Which version of this method seems to be right?

 In my case this unnecessary mass initialization of custom diskcache-
 classes leads to io-lags.

 Snippet that helped me:


 {{{
 import django.core.cache


 def cache_getitem(self, alias, exists_only=False):
 try:
 return getattr(self._connections, alias)
 except AttributeError:
 if alias not in self.settings:
 raise self.exception_class(f"The connection '{alias}' doesn't
 exist.")
 if exists_only:
 return
 conn = self.create_connection(alias)
 setattr(self._connections, alias, conn)
 return conn


 def cache_all(self):
 connections = [self.__getitem__(alias, exists_only=True) for alias in
 self]
 return [conn for conn in connections if conn is not None]


 django.core.cache.CacheHandler.all = cache_all
 django.core.cache.CacheHandler.__getitem__ = cache_getitem
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.f00286d2bf6919229005ed8de4fb65ab%40djangoproject.com.

Re: [Django] #32746: Unexpected test failures in 3.3.2 when running the whole testsuite

[Django]

#32746: Unexpected test failures in 3.3.2 when running the whole testsuite
---+--
 Reporter:  Jakub Kulík|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  3.2
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Mariusz Felisiak):

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


Comment:

 I cannot reproduce these failures, all tests works for me when run in
 reverse, see also https://djangoci.com/job/main-reverse/. Can you provide
 a subset of these that causes failures for you? flags passed to
 `runtests.py`, Python version, database, 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0a459cd23c49baad627c7296422e0310%40djangoproject.com.

Re: [Django] #32744: Template changes cause dev server to reload

[Django]

#32744: Template changes cause dev server to reload
-+--
 Reporter:  Ryan P Kilby |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

 * Attachment "ticket32744.zip" added.

 Barest project NOT reproducing editing the hello.html file whilst running
 the dev server.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.69b3b16db58684a42595430b297058f4%40djangoproject.com.

Re: [Django] #32744: Template changes cause dev server to reload

[Django]

#32744: Template changes cause dev server to reload
-+--
 Reporter:  Ryan P Kilby |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

 * resolution:  worksforme => needsinfo


Comment:

 Having seen the duplicate #32745 in the timeline, I've tried again here
 (double checking). It's still not reproducing with a fresh project so,
 still more info... 樂

 I'll upload a sample project with just a single view and template.

 Observed: `startproject`, `startapp`, then app template and view.
 `runserver`, edit the template. Not reload.

 Clearly you're seeing something, but what?
 Thanks.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1eb210977f1b1b5f1e265ff21a5d0d54%40djangoproject.com.

Re: [Django] #32745: Django 3.2 is auto reloading when template files are changed

[Django]

#32745: Django 3.2 is auto reloading when template files are changed
-+-
 Reporter:  Riccardo Di  |Owner:  nobody
  Virgilio   |
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Hi Riccardo — can you follow-up on #32744 please? As I wrote there, this
 isn't currently reproducing for me. (Just tried again with a fresh
 project, without luck, so more details are needed.) Thanks.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.c147127164412d938ded7097b71fac73%40djangoproject.com.

Re: [Django] #32746: Unexpected test failures in 3.3.2 when running the whole testsuite

[Django]

#32746: Unexpected test failures in 3.3.2 when running the whole testsuite
---+--
 Reporter:  Jakub Kulík|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Jakub Kulík):

 * Attachment "reverse-failures.txt" added.

 Test failures when running with --reverse

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.e23636e8bb2215401ceb31eccf2937c3%40djangoproject.com.

[Django] #32746: Unexpected test failures in 3.3.2 when running the whole testsuite

[Django]

#32746: Unexpected test failures in 3.3.2 when running the whole testsuite
-+
   Reporter:  Jakub Kulík|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  3.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 We recently introduced Django 3.3.2 to Solaris (with Python 3.9) and we
 are hitting unexpected test failures when running the full test suite on
 SPARC. When I rerun those tests one by one however, they are successful.
 My guess is that parts of the test suite are not independent and affect
 each other.

 Errors we are seeing are (although I am not sure that they are always the
 same and they changed since 3.3.1):
 {{{
 ERROR: test_output_normal (test_runner.test_debug_sql.TestDebugSQL)
 ERROR: test_output_verbose (test_runner.test_debug_sql.TestDebugSQL)
 ERROR: test_setupclass_exception (test_runner.test_debug_sql.TestDebugSQL)
 ERROR: test_lazy_base_url_init (file_storage.tests.FileSystemStorageTests)
 FAIL: test_incorrect_timezone (settings_tests.tests.SettingsTests)
 FAILED (failures=1, errors=4, skipped=1146, expected failures=4)
 }}}

 Running the test suite with `--reverse` results in many more failures
 (attached).

 This happens on SPARC only, Intel test results are clean (both with and
 without `--reverse`). Our other Django 2.2.21 with Python 3.7 is clean as
 well on both platforms.

 I am not sure how to continue/investigate the issue further, but I am
 happy to do so if guided a little.

 I have yet to try Django 3.1 or Python 3.7 (but runtime is highly unlike
 the problem).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.415e36da2713ec2ff41662e57642cd45%40djangoproject.com.

Re: [Django] #32721: Geometry Index with PostGIS using schema

[Django]

#32721: Geometry Index with PostGIS using schema
-+-
 Reporter:  Alan D. Snow |Owner:  Alan D.
 |  Snow
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7a1f8d00442d146e74ecdff8655c194c%40djangoproject.com.

Re: [Django] #32744: Template changes cause dev server to reload

[Django]

#32744: Template changes cause dev server to reload
-+--
 Reporter:  Ryan P Kilby |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

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


Comment:

 Hey Ryan 

 Thanks for the report. I'm need more detail, as I'm struggling to
 reproduce.

 Testing running with Django 3.2.3, both with Django's built-in runserver
 and  Channels' ASGI based one too. I'm **not seeing** the auto-reload
 behaviour on template saves.

 My `TEMPLATES` looks almost identical to yours.

 Obviously something is going on, but there must be more to it…


 {{{
 Watching for file changes with StatReloader
 }}}

 What reloader are you using? 樂

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.24457f4bfb0f215815044ffe8be54521%40djangoproject.com.

Re: [Django] #32743: Migrations don't alter foreign key data types when referencing primary keys in MTI models.

[Django]

#32743: Migrations don't alter foreign key data types when referencing primary 
keys
in MTI models.
--+
 Reporter:  Mariusz Felisiak  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  3.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * stage:  Unreviewed => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.22fcb8258271df6e3a2b57e2f23553d0%40djangoproject.com.

Re: [Django] #32702: urlize() should not decode URL fragments

[Django]

#32702: urlize() should not decode URL fragments
-+--
 Reporter:  Victor Shih  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  3.2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

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


Comment:

 Hi Victor — I'm going to mark this as needsinfo following Florian's
 comment on the PR. I'm very happy to discuss this with you, and see if we
 can make sure we're 100% clear before proceeding (but I think we need that
 discussion before moving forwards) — I hope that makes sense. Thanks.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.37cfc3d9c67e9da91c79e14021f45856%40djangoproject.com.

Re: [Django] #32740: Running colorama.init() at import time causes deployment error

[Django]

#32740: Running colorama.init() at import time causes deployment error
-+
 Reporter:  Leon Matthews|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  3.2
 Severity:  Release blocker  |   Resolution:
 Keywords:  apache mod_wsgi  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Carlton Gibson):

 Hi Leon.

 [https://github.com/GrahamDumpleton/mod_wsgi/issues/675#issuecomment-840181867
 Graham replied on `mod_wsgi`]:

 > For now try setting:
 > WSGIRestrictedStdout Off

 He also points out there where `colorama` can catch the OSError
 ([https://github.com/tartley/colorama/issues/304 Matching colorama issue])

 Can you give the PR on https://github.com/django/django/pull/14386 a go.
 That should at least enable you to get past this with
 `WSGIRestrictedStdout` still on.

 We're looking into whether we can move the `colorama.init()` off the
 import-time path. (It's meant to be a no-op on other platforms, but is
 hitting this OSError issue from mod_wsgi...)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.c3b810357da89fec919aea406f0f3f44%40djangoproject.com.

Re: [Django] #32745: Django 3.2 is auto reloading when template files are changed

[Django]

#32745: Django 3.2 is auto reloading when template files are changed
-+-
 Reporter:  Riccardo Di  |Owner:  nobody
  Virgilio   |
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.623416eff76df35e364bf19aab627d43%40djangoproject.com.

Re: [Django] #32745: Django 3.2 is auto reloading when template files are changed

[Django]

#32745: Django 3.2 is auto reloading when template files are changed
-+-
 Reporter:  Riccardo Di  |Owner:  nobody
  Virgilio   |
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Duplicate of #32744.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.314c8c9e7d744495dcd21d5a87317227%40djangoproject.com.

[Django] #32745: Django 3.2 is auto reloading when template files are changed

[Django]

#32745: Django 3.2 is auto reloading when template files are changed
+
   Reporter:  Riccardo Di Virgilio  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Template system   |Version:  3.2
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 The new version of Django 3.2 is forcing the auto reloading of all
 templates files, and there is no way to switch this feature off.
 For development I don't used any cached reloader and the legacy strategy
 of not reloading the server on template changes worked quite well for
 several years.
 When upgrading to Django 3.2 people working with me started complaining
 that any tiny change in html is now forcing the project to auto reload,
 this might not seems a big deal on a small project, but on a project of
 the size I'm working on it takes several seconds to reload.

 Unfortunately the current implementation is automatically opting you in
 here if you use Django templates:

 https://github.com/django/django/blob/main/django/template/autoreload.py#L9

 And there is no way to turn this off, so I needed to switch back to Django
 3.1 because this slowdown while developing is a dealbreaker for us.

 I'm proposing 2 ways of fixing this:

 1. A setting under TEMPLATES
 2. Instead of checking if the class has a method named get_dirs, check if
 there is a property called "should_autoreload", this way I can at least
 subclass the loader and disable it.

 I can contribute if you need, I have already done some small contributions
 I would be happy to help here.

 Thanks.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.dd1c470d21341ec97d753afea31296c2%40djangoproject.com.

Re: [Django] #32744: Template changes cause dev server to reload

[Django]

#32744: Template changes cause dev server to reload
-+--
 Reporter:  Ryan P Kilby |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

 * cc: Tom Forbes (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2452c745019bfbbee40c635f21b69891%40djangoproject.com.

Re: [Django] #32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.

[Django]

#32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.
-+-
 Reporter:  Jakub Kleň   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  3.2.1 file model | Triage Stage:  Accepted
  filefield fieldfile|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"224b8e5a5a8b316c9aa497efc72ed3f23156717b" 224b8e5a]:
 {{{
 #!CommitTicketReference repository=""
 revision="224b8e5a5a8b316c9aa497efc72ed3f23156717b"
 [3.2.x] Fixed #32718 -- Relaxed file name validation in FileField.

 - Validate filename returned by FileField.upload_to() not a filename
   passed to the FileField.generate_filename() (upload_to() may
   completely ignored passed filename).
 - Allow relative paths (without dot segments) in the generated filename.

 Thanks to Jakub Kleň for the report and review.
 Thanks to all folks for checking this patch on existing projects.
 Thanks Florian Apolloner and Markus Holtermann for the discussion and
 implementation idea.

 Regression in 0b79eb36915d178aef5c6a7bbce71b1e76d376d3.
 Backport of b55699968fc9ee985384c64e37f6cc74a0a23683 from main
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.286e3a688e533517b1864452b89971e6%40djangoproject.com.

Re: [Django] #32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.

[Django]

#32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.
-+-
 Reporter:  Jakub Kleň   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  3.2.1 file model | Triage Stage:  Accepted
  filefield fieldfile|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b8ecb0643619a0650a4447b282478ce5257856e2" b8ecb064]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8ecb0643619a0650a4447b282478ce5257856e2"
 [2.2.x] Fixed #32718 -- Relaxed file name validation in FileField.

 - Validate filename returned by FileField.upload_to() not a filename
   passed to the FileField.generate_filename() (upload_to() may
   completely ignored passed filename).
 - Allow relative paths (without dot segments) in the generated filename.

 Thanks to Jakub Kleň for the report and review.
 Thanks to all folks for checking this patch on existing projects.
 Thanks Florian Apolloner and Markus Holtermann for the discussion and
 implementation idea.

 Regression in 0b79eb36915d178aef5c6a7bbce71b1e76d376d3.

 Backport of b55699968fc9ee985384c64e37f6cc74a0a23683 from main.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2c295cdc0d308750c8e2fe095570cfd3%40djangoproject.com.

Re: [Django] #32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.

[Django]

#32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.
-+-
 Reporter:  Jakub Kleň   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  3.2.1 file model | Triage Stage:  Accepted
  filefield fieldfile|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b7d4a6fa650f97982cf9ca246ddfa623d685487b" b7d4a6fa]:
 {{{
 #!CommitTicketReference repository=""
 revision="b7d4a6fa650f97982cf9ca246ddfa623d685487b"
 [3.1.x] Fixed #32718 -- Relaxed file name validation in FileField.

 - Validate filename returned by FileField.upload_to() not a filename
   passed to the FileField.generate_filename() (upload_to() may
   completely ignored passed filename).
 - Allow relative paths (without dot segments) in the generated filename.

 Thanks to Jakub Kleň for the report and review.
 Thanks to all folks for checking this patch on existing projects.
 Thanks Florian Apolloner and Markus Holtermann for the discussion and
 implementation idea.

 Regression in 0b79eb36915d178aef5c6a7bbce71b1e76d376d3.

 Backport of b55699968fc9ee985384c64e37f6cc74a0a23683 from main.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.40b4ca08199efb41fec9db78297b2b75%40djangoproject.com.

Re: [Django] #32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.

[Django]

#32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.
-+-
 Reporter:  Jakub Kleň   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  3.2.1 file model | Triage Stage:  Accepted
  filefield fieldfile|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"b55699968fc9ee985384c64e37f6cc74a0a23683" b5569996]:
 {{{
 #!CommitTicketReference repository=""
 revision="b55699968fc9ee985384c64e37f6cc74a0a23683"
 Fixed #32718 -- Relaxed file name validation in FileField.

 - Validate filename returned by FileField.upload_to() not a filename
   passed to the FileField.generate_filename() (upload_to() may
   completely ignored passed filename).
 - Allow relative paths (without dot segments) in the generated filename.

 Thanks to Jakub Kleň for the report and review.
 Thanks to all folks for checking this patch on existing projects.
 Thanks Florian Apolloner and Markus Holtermann for the discussion and
 implementation idea.

 Regression in 0b79eb36915d178aef5c6a7bbce71b1e76d376d3.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5cdbc0772323b92b3ea3b36d872a334a%40djangoproject.com.

Re: [Django] #32719: Re-allow path components in `name` for Storage backends which allow it.

[Django]

#32719: Re-allow path components in `name` for Storage backends which allow it.
-+-
 Reporter:  Carlton Gibson   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  File |  Version:  3.2
  uploads/storage|
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Closing as a duplicate of #32718 which allows for relative paths and
 Windows separators in the file names.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.d67b62ed2c822b8e1545791b2418b24f%40djangoproject.com.

Re: [Django] #32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.

[Django]

#32718: Saving a FileField raises SuspiciousFileOperation in some scenarios.
-+-
 Reporter:  Jakub Kleň   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  3.2.1 file model | Triage Stage:  Accepted
  filefield fieldfile|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Phillip Marshall):

 Replying to [comment:33 Mariusz Felisiak]:
 > I added [https://github.com/django/django/pull/14372 PR] with the
 proposed solution. Please give it a spin.

 This patch resolves the issue for my project's use case as well. Thanks a
 lot!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.687c1de67212fb7d41342245cb4bb42b%40djangoproject.com.

Re: [Django] #32338: Accessibility issues with Django forms RadioSelect and CheckboxSelectMultiple

[Django]

#32338: Accessibility issues with Django forms RadioSelect and
CheckboxSelectMultiple
-+-
 Reporter:  Thibaud Colas|Owner:  David
 |  Smith
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  forms, wcag|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by David Smith):

 * owner:  (none) => David Smith
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.fef9f534ac7b1d1305138192023efea7%40djangoproject.com.