Re: [Django] #27888: Add a button to clear all admin filters

2020-01-24 Thread Django 
#27888: Add a button to clear all admin filters
-+-
 Reporter:  David Herring|Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
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:"5d654e1e7104d2ce86ec1b9fe52865a7dca4b4be" 5d654e1e]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d654e1e7104d2ce86ec1b9fe52865a7dca4b4be"
 Refs #27888 -- Removed redundant {% if %} in admin changelist filters.
 }}}

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

Re: [Django] #31179: Using the "forgot password" mechanism doesn't invalidate other sessions

2020-01-24 Thread Django 
#31179: Using the "forgot password" mechanism doesn't invalidate other sessions
-+-
 Reporter:  Mike Lissner |Owner:  Rishabh
 |  Verma
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  forgot password, | Triage Stage:  Accepted
  reset password, sessions logs out  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mike Lissner):

 Curious. I thought I reproduced it too, but perhaps I didn't do my test
 properly. I'm checking with the vulnerability reporter if he can reproduce
 it and will reopen if there's some subtlety we've missed (I suspect not!).

 Thanks for the response and sorry for taking your 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/066.a7ace800f167bfa1e04ee8d0d2a9adf8%40djangoproject.com.

[Django] #31206: Migration fails when a fields has db_returning = True set

2020-01-24 Thread Django 
#31206: Migration fails when a fields has db_returning = True set
-+-
   Reporter:  Tom|  Owner:  nobody
  Kazimiers  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I was happy to see PR 9983 merged before Django 3 was released, because it
 adds the `db_returning` attribute to the `Field` classes. This makes it
 possible to return multiple fields from an INSERT or UPDATE, which is
 especially useful to use database transaction timestamps (see issue
 #29444).

 It seems to work very well, except for migrations: if I have a field like
 `CreatedField()` as shown in `tests/queries/models.py` (part of the
 original PR), and create a new migration that sets the new default value
 on the field (e.g. `django.contrib.postgres.functions.TransactionNow`),
 `manage.py migrate` fails with this error:


 {{{
   File "./manage.py", line 11, in 
 execute_from_command_line(sys.argv)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 401, in
 execute_from_command_line
 utility.execute()
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 395, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/core/management/base.py", line 328, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/core/management/base.py", line 369, in execute
 output = self.handle(*args, **options)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/core/management/base.py", line 83, in wrapped
 res = handle_func(*args, **kwargs)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/core/management/commands/migrate.py", line 233, in handle
 fake_initial=fake_initial,
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/migrations/executor.py", line 117, in migrate
 state = self._migrate_all_forwards(state, plan, full_plan, fake=fake,
 fake_initial=fake_initial)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/migrations/executor.py", line 147, in
 _migrate_all_forwards
 state = self.apply_migration(state, migration, fake=fake,
 fake_initial=fake_initial)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/migrations/executor.py", line 245, in apply_migration
 state = migration.apply(state, schema_editor)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/migrations/migration.py", line 124, in apply
 operation.database_forwards(self.app_label, schema_editor, old_state,
 project_state)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/migrations/operations/fields.py", line 249, in
 database_forwards
 schema_editor.alter_field(from_model, from_field, to_field)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/backends/base/schema.py", line 565, in alter_field
 old_db_params, new_db_params, strict)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/backends/postgresql/schema.py", line 154, in
 _alter_field
 new_db_params, strict,
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/backends/base/schema.py", line 679, in _alter_field
 new_default = self.effective_default(new_field)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/backends/base/schema.py", line 303, in
 effective_default
 return field.get_db_prep_save(self._effective_default(field),
 self.connection)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/models/fields/__init__.py", line 817, in
 get_db_prep_save
 return self.get_db_prep_value(value, connection=connection,
 prepared=False)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/models/fields/__init__.py", line 1372, in
 get_db_prep_value
 value = self.get_prep_value(value)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 packages/django/db/models/fields/__init__.py", line 1351, in
 get_prep_value
 value = super().get_prep_value(value)
   File "/home/tom/.virtualenvs/catmaid/lib/python3.6/site-
 p

Re: [Django] #27734: Add a helpful error message when a parallel test worker is assigned an unexpected index

2020-01-24 Thread Django 
#27734: Add a helpful error message when a parallel test worker is assigned an
unexpected index
--+
 Reporter:  Adam Wróbel   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:  parallel  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Hameed Gifford):

 To anyone else who's still having this problem, it seems to be specific to
 OSX. Or at least this reason and fix is.

 https://stackoverflow.com/questions/50168647/multiprocessing-causes-
 python-to-crash-and-gives-an-error-may-have-been-in-progr

 Putting this somewhere in your code before the test runner is initialized
 (settings worked good for me) fixes the issue:
 {{{
 import os
 import platform
 import sys

 if 'test' in sys.argv and platform.system().lower() == 'darwin':
 os.environ.setdefault('OBJC_DISABLE_INITIALIZE_FORK_SAFETY', 'YES')
 }}}

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

Re: [Django] #31185: fields.E310-E311 should take into account UniqueConstraints without conditions.

2020-01-24 Thread Django 
#31185: fields.E310-E311 should take into account UniqueConstraints without
conditions.
-+-
 Reporter:  Pavel Garkin |Owner:  Ahmad
 |  Abdallah
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  UniqueConstraint | Triage Stage:  Accepted
  unique_together E310 E311  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ahmad Abdallah):

 * owner:  nobody => Ahmad Abdallah
 * 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/064.3c258205ad3a44b38405651cae4e9bf6%40djangoproject.com.

Re: [Django] #30846: postgis backend doesn't respect custom index names.

2020-01-24 Thread Django 
#30846: postgis backend doesn't respect custom index names.
-+-
 Reporter:  Thomas Steen |Owner:
  Rasmussen  |  Pratik1999
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 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 Ahmad Abdallah):

 * cc: Ahmad Abdallah (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.1432467b9102550cae5a447723e9b2eb%40djangoproject.com.

Re: [Django] #30997: Deprecate HttpRequest.is_ajax.

2020-01-24 Thread Django 
#30997: Deprecate HttpRequest.is_ajax.
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"d66d72f95655312c413d916add61a62928639514" d66d72f]:
 {{{
 #!CommitTicketReference repository=""
 revision="d66d72f95655312c413d916add61a62928639514"
 Refs #30997 -- Added HttpRequest.accepts().
 }}}

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

Re: [Django] #31204: Paginator with count = 0 always produce non-limited QuerySet. (was: Paginator with count = 0 always produce non-limited QuerySet)

2020-01-24 Thread Django 
#31204: Paginator with count = 0 always produce non-limited QuerySet.
+--
 Reporter:  Alexander Pervakov  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Core (Other)|  Version:  3.0
 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 felixxm):

 * status:  new => closed
 * type:  Uncategorized => Bug
 * component:  contrib.admin => Core (Other)
 * has_patch:  1 => 0
 * resolution:   => needsinfo


Comment:

 Thanks for this report, however I'm sure how the fact that a custom
 paginator returned `0` in `count()` ended with a queryset without any
 limit. As far as I'm concerned builtin paginators return and empty
 queryset in such cases, so it looks like an issue in custom paginator
 implementation .

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

Re: [Django] #30846: postgis backend doesn't respect custom index names.

2020-01-24 Thread Django 
#30846: postgis backend doesn't respect custom index names.
-+-
 Reporter:  Thomas Steen |Owner:
  Rasmussen  |  Pratik1999
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 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
-+-

Comment (by felixxm):

 Pratik1999, PR is the proper place to discuss patches. At first glance,
 tests are missing.

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

Re: [Django] #30846: postgis backend doesn't respect custom index names.

2020-01-24 Thread Django 
#30846: postgis backend doesn't respect custom index names.
-+-
 Reporter:  Thomas Steen |Owner:
  Rasmussen  |  Pratik1999
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 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
-+-

Comment (by Pratik1999):

 https://github.com/Pratik1999/django-1/tree/ticket_30846

 These are the changes I have made, shall I submit the pull request?  Or
 more changes are needed?

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

Re: [Django] #31205: Setting headers in JsonResponse

2020-01-24 Thread Django 
#31205: Setting headers in JsonResponse
---+--
 Reporter:  Saurav Goyal   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  3.0
 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 felixxm):

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


Comment:

 Please don't use Trac as a support channel.

 TicketClosingReasons/UseSupportChannels

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

[Django] #31205: Setting headers in JsonResponse

2020-01-24 Thread Django 
#31205: Setting headers in JsonResponse
-+
   Reporter:  goyalsaurav|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  HTTP handling  |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  |
-+
 How can i set headers in JsonResponse object.

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

Re: [Django] #31184: URL dispatcher docs should mention path_info

2020-01-24 Thread Django 
#31184: URL dispatcher docs should mention path_info
-+-
 Reporter:  Roy Smith|Owner:  Roy Smith
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
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:"27739ad3f2b2f00b1af573b6dfb5ef9935562a58" 27739ad]:
 {{{
 #!CommitTicketReference repository=""
 revision="27739ad3f2b2f00b1af573b6dfb5ef9935562a58"
 [3.0.x] Fixed #31184 -- Clarified URL matching behavior in URL dispatcher
 docs.

 Backport of cf493e5c819f5ee49b96954f026bec722e19d9c3 from master
 }}}

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

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

Re: [Django] #31184: URL dispatcher docs should mention path_info

2020-01-24 Thread Django 
#31184: URL dispatcher docs should mention path_info
-+-
 Reporter:  Roy Smith|Owner:  Roy Smith
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"cf493e5c819f5ee49b96954f026bec722e19d9c3" cf493e5c]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf493e5c819f5ee49b96954f026bec722e19d9c3"
 Fixed #31184 -- Clarified URL matching behavior in URL dispatcher docs.
 }}}

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

[Django] #31204: Paginator with count = 0 always produce non-limited QuerySet

2020-01-24 Thread Django 
#31204: Paginator with count = 0 always produce non-limited QuerySet
--+
   Reporter:  Alexander Pervakov  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  contrib.admin   |Version:  3.0
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Problem:

 Custom paginator, i.e. approximate PostgreSQL paginator based on
 pg_class.reltuples, could return count = 0 when vacuum haven't run yet.
 QuerySet doesn't set limit on following select query, and in my case I've
 got max memory exceeded error because Django Admin have tried to visualise
 all 3M rows from my DB.

 Solution:

 As a workaround for that case one should always use limit for one's custom
 ``count``, a good candidate for this is a Paginator.per_page attribute.
 Django itself could limits count as well, but when I've tried to implement
 it myself a 3 tests was failed (because in these tests Django Admin trust
 to ChangeList.result_count), and I've no time for deeper investigation.
 So my github PR isn't going beyond and only point to this case in a docs
 and in a count method comment to help curious ones in their custom
 Paginator implementation.

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