Re: [Django] #31601: postgres_tests.test_search.SearchHeadlineTests fails on latest PostgreSQL versions. (was: Test suite fails on latest PostgreSQL versions)

[Django]

#31601: postgres_tests.test_search.SearchHeadlineTests fails on latest 
PostgreSQL
versions.
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 Type:   |  Ljungberg
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.postgres |  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  tests| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * type:  Bug => Cleanup/optimization
 * 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.023e2e5dc8e1f967cd349b7601d80c01%40djangoproject.com.

Re: [Django] #31601: Test suite fails on latest PostgreSQL versions (was: Test suite fails on PostgreSQL 10.13)

[Django]

#31601: Test suite fails on latest PostgreSQL versions
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  tests| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Hannes Ljungberg:

Old description:

> A couple of full text search related to headlines tests break on
> PostgresSQL 10.13. The reason appears to be that a trailing `!` is now
> present in the results which breaks the equality checks. Looking at the
> 10.13 release notes ([https://www.postgresql.org/docs/release/10.13/])
> it's probable that the patch "Fix ts_headline() to make better headline
> selections when working with phrase queries" introduced this behaviour.
>
> Output of failures:
>
> {{{
> ==
> FAIL [0.015s]: test_headline
> (postgres_tests.test_search.SearchHeadlineTests)
> --
> Traceback (most recent call last):
>   File "/tests/django/tests/postgres_tests/test_search.py", line 569, in
> test_headline
> 'Robin. He was not at all afraid to be killed in nasty '
> AssertionError: 'R[80 chars]brave, brave, brave
> Sir Robin!' != 'R[80 chars]brave, brave,
> brave Sir Robin'
> - Robin. He was not at all afraid to be killed in nasty ways.
> Brave, brave, brave, brave Sir
> Robin!
> ?
> -
> + Robin. He was not at all afraid to be killed in nasty ways.
> Brave, brave, brave, brave Sir
> Robin
>

> ==
> FAIL [0.019s]: test_headline_separator_options
> (postgres_tests.test_search.SearchHeadlineTests)
> --
> Traceback (most recent call last):
>   File "/tests/django/tests/postgres_tests/test_search.py", line 621, in
> test_headline_separator_options
> 'Robin. He was not at all afraid to be killed in '
> AssertionError: ', brave
> Sir Robin!' != ',
> brave Sir Robin'
> - Robin. He was not at all afraid to be killed in nasty
> ways. Brave, brave, brave,
> brave Sir Robin!
> ?
> -
> + Robin. He was not at all afraid to be killed in nasty
> ways. Brave, brave, brave,
> brave Sir Robin
>

> ==
> FAIL [0.016s]: test_headline_short_word_option
> (postgres_tests.test_search.SearchHeadlineTests)
> --
> Traceback (most recent call last):
>   File "/tests/django/tests/postgres_tests/test_search.py", line 650, in
> test_headline_short_word_option
> ), True)
> AssertionError: False is not True
> }}}

New description:

 A couple of full text search related to headlines tests break on the
 latest PostgresSQL versions (9.6.18, 10.13 11.8, 12.3). The reason appears
 to be that a trailing `!` is now present in the results which breaks the
 equality checks. Looking at the 10.13 release notes
 ([https://www.postgresql.org/docs/release/10.13/]) it's probable that the
 patch "Fix ts_headline() to make better headline selections when working
 with phrase queries" introduced this behaviour.

 Output of failures:

 {{{
 ==
 FAIL [0.015s]: test_headline
 (postgres_tests.test_search.SearchHeadlineTests)
 --
 Traceback (most recent call last):
   File "/tests/django/tests/postgres_tests/test_search.py", line 569, in
 test_headline
 'Robin. He was not at all afraid to be killed in nasty '
 AssertionError: 'R[80 chars]brave, brave, brave
 Sir Robin!' != 'R[80 chars]brave, brave,
 brave Sir Robin'
 - Robin. He was not at all afraid to be killed in nasty ways.
 Brave, brave, brave, brave Sir
 Robin!
 ?
 -
 + Robin. He was not at all afraid to be killed in nasty ways.
 Brave, brave, brave, brave Sir
 Robin


 ==
 FAIL [0.019s]: test_headline_separator_options
 (postgres_tests.test_search.SearchHeadlineTests)
 --
 Traceback (most recent call last):
   File "/tests/django/tests/postgres_tests/test_search.py", line 621, in
 test_headline_separator_options
 'Robin. He was not at all 

Re: [Django] #31599: Improve the performance of the autoreloader by ignoring third party packages. (was: Improve the performance of the autoreloader by ignoring third party packages)

[Django]

#31599: Improve the performance of the autoreloader by ignoring third party
packages.
-+-
 Reporter:  Tom Forbes   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 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
-+-
Changes (by felixxm):

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


Comment:

 IMO we should still trace changes in 3rd-party packages. It's not only
 about making local changes for debugging (I do the same) but also about
 changing versions of 3rd-party packages. In such cases, forcing users to
 manually restart the server can be annoying.

 This kind of changes should be preceded by discussion and a strong
 consensus on DevelopersMailingList. 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.b060b50531a21efc1b09042f2d6f1b75%40djangoproject.com.

Re: [Django] #31600: Calling .delete() on a queryset doesn't delete related objects

[Django]

#31600: Calling .delete() on a queryset doesn't delete related objects
---+--
 Reporter:  אורי   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  3.0
 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
---+--

Comment (by אורי):

 Hi,

 Since it's open source you can see the code. I created a branch with the
 failing test. You can see the test on  https://github.com/speedy-net
 /speedy-
 
net/blob/uri_temp_temp_branch_2020-05-18_a/speedy/match/likes/tests/test_views.py#L366-L411
 and the commit who causes it to fail on https://github.com/speedy-net
 /speedy-net/commit/d91bd29d465149ede7ff906e0982b21d6c4a712f . You can
 check the failing tests on Travis CI https://travis-ci.org/github/speedy-
 net/speedy-net/builds/688212117 and the passing tests without this commit
 on https://travis-ci.org/github/speedy-net/speedy-net/builds/688210140 .

-- 
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/069.c01aa162db4b50ecc188c4bf97e76a77%40djangoproject.com.

Re: [Django] #31601: Test suite fails on PostgreSQL 10.13

[Django]

#31601: Test suite fails on PostgreSQL 10.13
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  tests| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Hannes Ljungberg):

 PR: https://code.djangoproject.com/ticket/31601#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 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.5937b13d26f103b8bdeb574d70914ae4%40djangoproject.com.

[Django] #31601: Test suite fails on PostgreSQL 10.13

[Django]

#31601: Test suite fails on PostgreSQL 10.13
-+-
   Reporter:  Hannes |  Owner:  Hannes Ljungberg
  Ljungberg  |
   Type:  Bug| Status:  assigned
  Component: |Version:  3.1
  contrib.postgres   |
   Severity:  Normal |   Keywords:  tests
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 A couple of full text search related to headlines tests break on
 PostgresSQL 10.13. The reason appears to be that a trailing `!` is now
 present in the results which breaks the equality checks. Looking at the
 10.13 release notes ([https://www.postgresql.org/docs/release/10.13/])
 it's probable that the patch "Fix ts_headline() to make better headline
 selections when working with phrase queries" introduced this behaviour.

 Output of failures:

 {{{
 ==
 FAIL [0.015s]: test_headline
 (postgres_tests.test_search.SearchHeadlineTests)
 --
 Traceback (most recent call last):
   File "/tests/django/tests/postgres_tests/test_search.py", line 569, in
 test_headline
 'Robin. He was not at all afraid to be killed in nasty '
 AssertionError: 'R[80 chars]brave, brave, brave
 Sir Robin!' != 'R[80 chars]brave, brave,
 brave Sir Robin'
 - Robin. He was not at all afraid to be killed in nasty ways.
 Brave, brave, brave, brave Sir
 Robin!
 ?
 -
 + Robin. He was not at all afraid to be killed in nasty ways.
 Brave, brave, brave, brave Sir
 Robin


 ==
 FAIL [0.019s]: test_headline_separator_options
 (postgres_tests.test_search.SearchHeadlineTests)
 --
 Traceback (most recent call last):
   File "/tests/django/tests/postgres_tests/test_search.py", line 621, in
 test_headline_separator_options
 'Robin. He was not at all afraid to be killed in '
 AssertionError: ', brave Sir
 Robin!' != ', brave
 Sir Robin'
 - Robin. He was not at all afraid to be killed in nasty ways.
 Brave, brave, brave,
 brave Sir Robin!
 ?
 -
 + Robin. He was not at all afraid to be killed in nasty ways.
 Brave, brave, brave,
 brave Sir Robin


 ==
 FAIL [0.016s]: test_headline_short_word_option
 (postgres_tests.test_search.SearchHeadlineTests)
 --
 Traceback (most recent call last):
   File "/tests/django/tests/postgres_tests/test_search.py", line 650, in
 test_headline_short_word_option
 ), True)
 AssertionError: False is not True
 }}}

-- 
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.56067533e3b78f9e6b307820bd570e48%40djangoproject.com.

Re: [Django] #30913: Add support for adding non-key columns to indexes

[Django]

#30913: Add support for adding non-key columns to indexes
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql covering  | Triage Stage:  Accepted
  index include  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hannes Ljungberg):

 * 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/067.7fd50d606f27d1aa565be00d2079d0e0%40djangoproject.com.

Re: [Django] #31600: Calling .delete() on a queryset doesn't delete related objects

[Django]

#31600: Calling .delete() on a queryset doesn't delete related objects
---+--
 Reporter:  אורי   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  3.0
 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 אורי:

Old description:

> I created a new test and it had users and I deleted them:
>
> `User.objects.all().exclude(pk=self.user_1.pk).delete()`
>
> The User model has related models with `on_delete=models.CASCADE` which
> should be deleted as well.
>
> But in my test, I got this exception:
>
> {{{
> ==
> ERROR: test_like_list_views_titles_with_empty_lists
> (speedy.match.likes.tests.test_views.LikeListViewsEnglishTestCase)
> --
> Traceback (most recent call last):
>   File "env\lib\site-packages\django\db\backends\utils.py", line 84, in
> _execute
> return self.cursor.execute(sql)
> psycopg2.errors.ForeignKeyViolation: insert or update on table
> "net_accounts_siteprofile" violates foreign key constraint
> "net_accounts_sitepro_user_id_c96775a1_fk_accounts_"
> DETAIL:  Key (user_id)=(403828609159078) is not present in table
> "accounts_user".
>

> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
>   File "env\lib\site-packages\django\test\testcases.py", line 274, in
> __call__
> self._post_teardown()
>   File "env\lib\site-packages\django\test\testcases.py", line 1009, in
> _post_teardown
> self._fixture_teardown()
>   File "env\lib\site-packages\django\test\testcases.py", line 1177, in
> _fixture_teardown
> connections[db_name].check_constraints()
>   File "env\lib\site-packages\django\db\backends\postgresql\base.py",
> line 276, in check_constraints
> self.cursor().execute('SET CONSTRAINTS ALL IMMEDIATE')
>   File "env\lib\site-packages\django\db\backends\utils.py", line 68, in
> execute
> return self._execute_with_wrappers(sql, params, many=False,
> executor=self._execute)
>   File "env\lib\site-packages\django\db\backends\utils.py", line 77, in
> _execute_with_wrappers
> return executor(sql, params, many, context)
>   File "env\lib\site-packages\django\db\backends\utils.py", line 86, in
> _execute
> return self.cursor.execute(sql, params)
>   File "env\lib\site-packages\django\db\utils.py", line 90, in __exit__
> raise dj_exc_value.with_traceback(traceback) from exc_value
>   File "env\lib\site-packages\django\db\backends\utils.py", line 84, in
> _execute
> return self.cursor.execute(sql)
> django.db.utils.IntegrityError: insert or update on table
> "net_accounts_siteprofile" violates foreign key constraint
> "net_accounts_sitepro_user_id_c96775a1_fk_accounts_"
> DETAIL:  Key (user_id)=(403828609159078) is not present in table
> "accounts_user".
>

> --
> Ran 1 test in 7.425s
> }}}
>
> I think this exception is because the users I deleted.
> `net_accounts_siteprofile` refers to the `SiteProfile` model which should
> be deleted when deleting a user by on_delete=models.CASCADE .
>
> I checked and eventually I found out that changing:
>
> `User.objects.all().exclude(pk=self.user_1.pk).delete()`
>
> To:
>
> {{{
> for user in User.objects.all().exclude(pk=self.user_1.pk):
> user.delete()
> }}}
>
> Fixes the problem. But I expected related objects to be deleted by the
> first query too. Does it mean I can't safely delete users in bulk by
> `.delete()`? And if it does, how do I disable it so trying to delete
> users in bulk will raise an exception?
>
> I would like either to fix the queryset bulk `.delete()` method to delete
> related objects too, or to completely disable bulk deletions in Django.
> Is there a simple way to define a manager which doesn't have this bulk
> delete feature?

New description:

 I created a new test and it had users and I deleted them:

 `User.objects.all().exclude(pk=self.user_1.pk).delete()`

 The `User` model has related models with `on_delete=models.CASCADE` which
 should be deleted as well.

 But in my test, I got this exception:

 {{{
 ==
 ERROR: test_like_list_views_titles_with_empty_lists
 (speedy.match.likes.tests.test_views.LikeListViewsEnglishTestCase)
 --
 Traceback (most recent call last):
   File 

[Django] #31600: Calling .delete() on a queryset doesn't delete related objects

[Django]

#31600: Calling .delete() on a queryset doesn't delete related objects
-+
   Reporter:  אורי   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  3.0
   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 created a new test and it had users and I deleted them:

 `User.objects.all().exclude(pk=self.user_1.pk).delete()`

 The User model has related models with `on_delete=models.CASCADE` which
 should be deleted as well.

 But in my test, I got this exception:

 {{{
 ==
 ERROR: test_like_list_views_titles_with_empty_lists
 (speedy.match.likes.tests.test_views.LikeListViewsEnglishTestCase)
 --
 Traceback (most recent call last):
   File "env\lib\site-packages\django\db\backends\utils.py", line 84, in
 _execute
 return self.cursor.execute(sql)
 psycopg2.errors.ForeignKeyViolation: insert or update on table
 "net_accounts_siteprofile" violates foreign key constraint
 "net_accounts_sitepro_user_id_c96775a1_fk_accounts_"
 DETAIL:  Key (user_id)=(403828609159078) is not present in table
 "accounts_user".


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

 Traceback (most recent call last):
   File "env\lib\site-packages\django\test\testcases.py", line 274, in
 __call__
 self._post_teardown()
   File "env\lib\site-packages\django\test\testcases.py", line 1009, in
 _post_teardown
 self._fixture_teardown()
   File "env\lib\site-packages\django\test\testcases.py", line 1177, in
 _fixture_teardown
 connections[db_name].check_constraints()
   File "env\lib\site-packages\django\db\backends\postgresql\base.py", line
 276, in check_constraints
 self.cursor().execute('SET CONSTRAINTS ALL IMMEDIATE')
   File "env\lib\site-packages\django\db\backends\utils.py", line 68, in
 execute
 return self._execute_with_wrappers(sql, params, many=False,
 executor=self._execute)
   File "env\lib\site-packages\django\db\backends\utils.py", line 77, in
 _execute_with_wrappers
 return executor(sql, params, many, context)
   File "env\lib\site-packages\django\db\backends\utils.py", line 86, in
 _execute
 return self.cursor.execute(sql, params)
   File "env\lib\site-packages\django\db\utils.py", line 90, in __exit__
 raise dj_exc_value.with_traceback(traceback) from exc_value
   File "env\lib\site-packages\django\db\backends\utils.py", line 84, in
 _execute
 return self.cursor.execute(sql)
 django.db.utils.IntegrityError: insert or update on table
 "net_accounts_siteprofile" violates foreign key constraint
 "net_accounts_sitepro_user_id_c96775a1_fk_accounts_"
 DETAIL:  Key (user_id)=(403828609159078) is not present in table
 "accounts_user".


 --
 Ran 1 test in 7.425s
 }}}

 I think this exception is because the users I deleted.
 `net_accounts_siteprofile` refers to the `SiteProfile` model which should
 be deleted when deleting a user by on_delete=models.CASCADE .

 I checked and eventually I found out that changing:

 `User.objects.all().exclude(pk=self.user_1.pk).delete()`

 To:

 {{{
 for user in User.objects.all().exclude(pk=self.user_1.pk):
 user.delete()
 }}}

 Fixes the problem. But I expected related objects to be deleted by the
 first query too. Does it mean I can't safely delete users in bulk by
 `.delete()`? And if it does, how do I disable it so trying to delete users
 in bulk will raise an exception?

 I would like either to fix the queryset bulk `.delete()` method to delete
 related objects too, or to completely disable bulk deletions in Django. Is
 there a simple way to define a manager which doesn't have this bulk delete
 feature?

-- 
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/054.48232023dc77968c4bfad4786f784370%40djangoproject.com.

Re: [Django] #25791: Implement autoreload behaviour for cached template loader

[Django]

#25791: Implement autoreload behaviour for cached template loader
-+-
 Reporter:  Jaap Roes|Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autoreload   | Triage Stage:  Accepted
  templates cached loader|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Forbes):

 * needs_better_patch:  1 => 0


Comment:

 Second attempt at a patch: https://github.com/django/django/pull/12928

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

[Django] #31599: Improve the performance of the autoreloader by ignoring third party packages

[Django]

#31599: Improve the performance of the autoreloader by ignoring third party
packages
+
   Reporter:  Tom Forbes|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |Version:  master
   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 |
+
 In https://github.com/django/django/pull/12750 and
 https://code.djangoproject.com/ticket/30372 we stopped watching the
 translation files that Django ships, to improve the performance of the
 autoreloader.

 I believe we can go a step further and stop monitoring all third-party
 packages for changes by using the sysconfig module:
 https://docs.python.org/3/library/sysconfig.html. With this we can get a
 list of different Python system directories, for example:

 {{{
 data = "/Users/tom/PycharmProjects/github/orf/django/venv"
 include =
 
"/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/include/python3.7m"
 platinclude =
 
"/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/include/python3.7m"
 platlib =
 "/Users/tom/PycharmProjects/github/orf/django/venv/lib/python3.7/site-
 packages"
 platstdlib =
 "/Users/tom/PycharmProjects/github/orf/django/venv/lib/python3.7"
 purelib =
 "/Users/tom/PycharmProjects/github/orf/django/venv/lib/python3.7/site-
 packages"
 scripts = "/Users/tom/PycharmProjects/github/orf/django/venv/bin"
 stdlib =
 
"/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7/lib/python3.7"
 }}}

 We could simply not watch any path under the `purelib` directory to start.
 This would exclude a huge number of files from being watched - Django
 alone has 824 individual files that would be excluded, and it's safe to
 assume that a large project with many third party dependencies would have
 several thousand.

 This would be a breaking change - personally I sometimes find myself
 navigating into third party code and making small changes while debugging,
 and I'm sure others do this from time to time. However I don't think it's
 a common occurance for most developers and I'm not sure everyone paying a
 cost is worth the benefit to a small number of people.

-- 
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/046.8548a142cd495d11a6332a172401e048%40djangoproject.com.

Re: [Django] #31598: Broken link in Django 1.4 docs. (was: Broken link in https://docs.gunicorn.org/en/0.17.4/run.html)

[Django]

#31598: Broken link in Django 1.4 docs.
---+--
 Reporter:  Aaron Rono |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  3.0
 Severity:  Normal |   Resolution:  invalid
 Keywords:  broken link| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by felixxm):

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


Comment:

 Django 1.4 is not supported for a long time.

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

Re: [Django] #31577: The explanation ended in the middle.

[Django]

#31577: The explanation ended in the middle.
-+-
 Reporter:  Joon Hwan 김준환 |Owner:  Joon Hwan
 Type:   |  김준환
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Joon Hwan 김준환):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12927 PR]

-- 
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.903784aba139964f4b8c79e4db44b2d5%40djangoproject.com.

Re: [Django] #31577: The explanation ended in the middle.

[Django]

#31577: The explanation ended in the middle.
-+-
 Reporter:  Joon Hwan 김준환 |Owner:  Joon Hwan
 Type:   |  김준환
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.0
 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


Comment:

 OK, super. I shall Accept on that basis.

 Thanks for the input! 

-- 
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.4cc40dc5e101c23aa93784169caf7bb2%40djangoproject.com.

Re: [Django] #31596: ForeignKey.validate() should validate using the base manager.

[Django]

#31596: ForeignKey.validate() should validate using the base manager.
--+--
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 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):

 * cc: Carlton Gibson (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/067.29769c30728064d27355bf979d4fee9b%40djangoproject.com.

[Django] #31598: Broken link in https://docs.gunicorn.org/en/0.17.4/run.html

[Django]

#31598: Broken link in https://docs.gunicorn.org/en/0.17.4/run.html
-+-
   Reporter:  Aroniez|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  3.0
   Severity:  Normal |   Keywords:  broken link
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 I found the broken link to this page
 **https://docs.djangoproject.com/en/1.4/howto/deployment/wsgi/** in the
 following subtext

 ''Note
 If you run Django 1.4 or newer, it’s highly recommended to simply run your
 application with the  **WSGI interface** using the gunicorn command.''

-- 
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/050.5c2983a007e806196e29f54ca59e4c35%40djangoproject.com.