Re: [Django] #27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() and tearDownClass()

[Django]

#27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() 
and
tearDownClass()
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  1.10
 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):

 * 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/067.03458ebfaf57eeb7e722a06494791389%40djangoproject.com.

Re: [Django] #30398: Check database connection's health before it is reused

[Django]

#30398: Check database connection's health before it is reused
-+-
 Reporter:  Przemysław Suliga|Owner:
 |  Przemysław Suliga
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 See
 [https://github.com/django/django/pull/14899#pullrequestreview-788437304
 Florian's review].

-- 
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.29c255861ed5ecd2fd5b215dfe4ae71d%40djangoproject.com.

Re: [Django] #33229: BaseDatabaseOperations.adapt_datetimefield_value and adapt_timefield_value() crash on expressions

[Django]

#33229: BaseDatabaseOperations.adapt_datetimefield_value and
adapt_timefield_value() crash on expressions
-+-
 Reporter:  Tim Graham   |Owner:  Vishal
 |  Pandey
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. We should probably add the same to the
 `BaseDatabaseOperations.adapt_datefield_value()`.

-- 
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.8c4137a4b305991d385614c851196411%40djangoproject.com.

Re: [Django] #33228: Change BaseDatabaseFeatures.has_case_insensitive_like to False

[Django]

#33228: Change BaseDatabaseFeatures.has_case_insensitive_like to False
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/067.d299ef7664f7b5710cb7b3f5c6f38c93%40djangoproject.com.

Re: [Django] #33229: BaseDatabaseOperations.adapt_datetimefield_value and adapt_timefield_value() crash on expressions

[Django]

#33229: BaseDatabaseOperations.adapt_datetimefield_value and
adapt_timefield_value() crash on expressions
-+-
 Reporter:  Tim Graham   |Owner:  Vishal
 |  Pandey
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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
-+-
Changes (by Vishal Pandey):

 * owner:  nobody => Vishal Pandey
 * 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/067.5338487f6b2f9de74005e4c066a5f666%40djangoproject.com.

[Django] #33229: BaseDatabaseOperations.adapt_datetimefield_value and adapt_timefield_value() crash on expressions

[Django]

#33229: BaseDatabaseOperations.adapt_datetimefield_value and
adapt_timefield_value() crash on expressions
-+-
   Reporter:  Tim|  Owner:  nobody
  Graham |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  dev
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 While building a backend for Snowflake, I saw these test failures:
 {{{
 ==
 ERROR: test_in_lookup_allows_F_expressions_and_expressions_for_datetimes
 (expressions.tests.IterableLookupInnerExpressionsTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/django/db/backends/utils.py", line 87, in
 _execute
 return self.cursor.execute(sql, params)
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/cursor.py", line 777, in execute
 Error.errorhandler_wrapper(
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/errors.py", line 255, in errorhandler_wrapper
 handed_over = Error.hand_to_other_handler(
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/errors.py", line 310, in
 hand_to_other_handler
 cursor.errorhandler(connection, cursor, error_class, error_value)
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/errors.py", line 189, in default_errorhandler
 raise error_class(
 snowflake.connector.errors.ProgrammingError: Timestamp
 'Col(expressions_ExPeRiMeNt, expressions.Experiment.start)' is not
 recognized

 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "/home/tim/code/django/tests/expressions/tests.py", line 959, in
 test_in_lookup_allows_F_expressions_and_expressions_for_datetimes
 self.assertSequenceEqual(queryset, [r1])
   File "/opt/python3.9.5/lib/python3.9/unittest/case.py", line 949, in
 assertSequenceEqual
 len1 = len(seq1)
   File "/home/tim/code/django/django/db/models/query.py", line 262, in
 __len__
 self._fetch_all()
   File "/home/tim/code/django/django/db/models/query.py", line 1324, in
 _fetch_all
 self._result_cache = list(self._iterable_class(self))
   File "/home/tim/code/django/django/db/models/query.py", line 51, in
 __iter__
 results = compiler.execute_sql(chunked_fetch=self.chunked_fetch,
 chunk_size=self.chunk_size)
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line
 1175, in execute_sql
 cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/utils.py", line 101, in
 execute
 return super().execute(sql, params)
   File "/home/tim/code/django/django/db/backends/utils.py", line 69, in
 execute
 return self._execute_with_wrappers(sql, params, many=False,
 executor=self._execute)
   File "/home/tim/code/django/django/db/backends/utils.py", line 78, in
 _execute_with_wrappers
 return executor(sql, params, many, context)
   File "/home/tim/code/django/django/db/backends/utils.py", line 87, in
 _execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/utils.py", line 90, in __exit__
 raise dj_exc_value.with_traceback(traceback) from exc_value
   File "/home/tim/code/django/django/db/backends/utils.py", line 87, in
 _execute
 return self.cursor.execute(sql, params)
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/cursor.py", line 777, in execute
 Error.errorhandler_wrapper(
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/errors.py", line 255, in errorhandler_wrapper
 handed_over = Error.hand_to_other_handler(
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/errors.py", line 310, in
 hand_to_other_handler
 cursor.errorhandler(connection, cursor, error_class, error_value)
   File "/home/tim/.virtualenvs/django39/lib/python3.9/site-
 packages/snowflake/connector/errors.py", line 189, in default_errorhandler
 raise error_class(
 django.db.utils.ProgrammingError: Timestamp 'Col(expressions_ExPeRiMeNt,
 expressions.Experiment.start)' is not recognized

 ==
 ERROR: test_expressions_in_lookups_join_choice
 

[Django] #33228: Change BaseDatabaseFeatures.has_case_insensitive_like to False

[Django]

#33228: Change BaseDatabaseFeatures.has_case_insensitive_like to False
-+-
   Reporter:  Tim|  Owner:  nobody
  Graham |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  dev
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 It seems that a better default for this feature would be `False`, as of
 the built-in backends, only SQLite uses `True`. In addition, all three of
 the databases I've built third-party backends for (Cloud Spanner,
 CockroachDB, Snowflake) all use `False`. Of course, a mention in the
 release notes that the default is changed is still appropriate.

-- 
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.4902bc672f8a7c22858d1f1ab47dfce8%40djangoproject.com.

Re: [Django] #33220: Test suite failures when using PYTHONOPTIMIZE or optimization CLI flags

[Django]

#33220: Test suite failures when using PYTHONOPTIMIZE or optimization CLI flags
-+-
 Reporter:  Keryn Knight |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam Johnson):

 I would drop PYTHONOPTIMIZE from your environment, basically no one knows
 about its existence so most code assumes `assert` always works.

-- 
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.92e6c47ede8d8a7e204528be30d99f7a%40djangoproject.com.

Re: [Django] #32672: Primary Key, type double and type unsigned integer ain't detected correctly for Sqlite3 Database

[Django]

#32672: Primary Key, type double and type unsigned integer ain't detected 
correctly
for Sqlite3 Database
-+-
 Reporter:  jgr88|Owner:  Anvesh
 Type:   |  Mishra
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  SQLite3 PrimaryKey   | Triage Stage:  Accepted
  Datatypes  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

 * 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 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/073.6226214761156dad72eaa283e2477099%40djangoproject.com.

Re: [Django] #31685: Support updating conflicts with QuerySet.bulk_create().

[Django]

#31685: Support updating conflicts with QuerySet.bulk_create().
-+-
 Reporter:  Vitor Pereira|Owner:  Chih Sean
 |  Hsu
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  bulk insert update   | Triage Stage:  Accepted
  upsert |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * 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 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/062.f5f723065675b819bbd455a118b951c4%40djangoproject.com.

Re: [Django] #31503: Moving a unique constraint from unique_together to Field.unique generate an invalid migration.

[Django]

#31503: Moving a unique constraint from unique_together to Field.unique 
generate an
invalid migration.
-+-
 Reporter:  Xiang Wang   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unique_together  | Triage Stage:  Ready for
  unique migrations  |  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:"0314593fe8e7dc685bbb6585eee40e755588864e" 0314593f]:
 {{{
 #!CommitTicketReference repository=""
 revision="0314593fe8e7dc685bbb6585eee40e755588864e"
 Fixed #31503 -- Made autodetector remove unique/index_together before
 altering fields.
 }}}

-- 
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.196776d5f38a0bf1f68a4b97fe0cd6aa%40djangoproject.com.

Re: [Django] #31503: Moving a unique constraint from unique_together to Field.unique generate an invalid migration.

[Django]

#31503: Moving a unique constraint from unique_together to Field.unique 
generate an
invalid migration.
-+-
 Reporter:  Xiang Wang   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unique_together  | Triage Stage:  Ready for
  unique migrations  |  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:"ea00a0843eb7a7bb074625a663ca4f5c86b8c5bd" ea00a084]:
 {{{
 #!CommitTicketReference repository=""
 revision="ea00a0843eb7a7bb074625a663ca4f5c86b8c5bd"
 [4.0.x] Fixed #31503 -- Made autodetector remove unique/index_together
 before altering fields.

 Backport of 0314593fe8e7dc685bbb6585eee40e755588864e 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.0f6b02aa10d2cd7635ccf347de96457b%40djangoproject.com.

Re: [Django] #31503: Moving a unique constraint from unique_together to Field.unique generate an invalid migration.

[Django]

#31503: Moving a unique constraint from unique_together to Field.unique 
generate an
invalid migration.
-+-
 Reporter:  Xiang Wang   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  unique_together  | Triage Stage:  Ready for
  unique migrations  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/064.aa67e02e210a3b23a454b54e581d8102%40djangoproject.com.

Re: [Django] #33205: call_command() fails when required mutually exclusive arguments use the same `dest`.

[Django]

#33205: call_command() fails when required mutually exclusive arguments use the
same `dest`.
-+-
 Reporter:  Peter Law|Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  3.2
  commands)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c9ebe4ca4e3f5d5d76bfbdae489e3f44e32416e5" c9ebe4ca]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9ebe4ca4e3f5d5d76bfbdae489e3f44e32416e5"
 [4.0.x] Fixed #33205 -- Made call_command() raise TypeError when dest with
 multiple arguments is passed.

 Backport of c1e4111c74ee9d9f48cbee5a5b7c40289203c93d 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/068.8a61e65acb4a527a9e66852f2f337142%40djangoproject.com.

Re: [Django] #33205: call_command() fails when required mutually exclusive arguments use the same `dest`.

[Django]

#33205: call_command() fails when required mutually exclusive arguments use the
same `dest`.
-+-
 Reporter:  Peter Law|Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  3.2
  commands)  |
 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:"c1e4111c74ee9d9f48cbee5a5b7c40289203c93d" c1e4111c]:
 {{{
 #!CommitTicketReference repository=""
 revision="c1e4111c74ee9d9f48cbee5a5b7c40289203c93d"
 Fixed #33205 -- Made call_command() raise TypeError when dest with
 multiple arguments is passed.
 }}}

-- 
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/068.e1544c221be3e8b5a7bff63675b3f511%40djangoproject.com.

Re: [Django] #33225: Missing FROM-clause when ordering by a relationship defined on the parent model in a Subquery inside a negated Q

[Django]

#33225: Missing FROM-clause when ordering by a relationship defined on the 
parent
model in a Subquery inside a negated Q
-+-
 Reporter:  InvalidInterrupt |Owner:  Geonsang
 |  Yoo
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 Geonsang Yoo):

 * owner:  nobody => Geonsang Yoo
 * status:  new => assigned


Comment:

 Thank you both (@InvalidInterrupt, @ Simon Charette) for your report and
 analysis!
 I will try to solve this issue!!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/074.7a6be517cd99d051e60db28525223b21%40djangoproject.com.