Re: [Django] #31703: Name all initial migrations "NNNN_initial".

[Django]

#31703: Name all initial migrations "_initial".
-+-
 Reporter:  Jon Dufresne |Owner:  Jon
 Type:   |  Dufresne
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 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 felixxm):

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

Re: [Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

[Django]

#31737: Strange admin behaviour on Django 3.1b1 with Firefox
-+--
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 Severity:  Release blocker  |   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
 * resolution:   => needsinfo


Comment:

 Unfortunately I cannot reproduce this issue on Firefox 77 or Chrome, can
 you provide more details or a sample project?

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

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

Re: [Django] #31738: invalid exception thrown "django.core.exceptions.ImproperlyConfigured: settings.FIXTURE_DIRS contains duplicates."

[Django]

#31738: invalid exception thrown "django.core.exceptions.ImproperlyConfigured:
settings.FIXTURE_DIRS contains duplicates."
-+-
 Reporter:  timharsch|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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
-+-
Description changed by felixxm:

Old description:

> loaddata.py incorrectly throws an ImproperlyConfigured exception when
> FIXTURE_DIRS is a list of one.  See:
> https://github.com/django/django/blame/798835112d81b852efaae0e067af389c733cd1b3/django/core/management/commands/loaddata.py#L296
>
> I changed this code to:
> {{{
> 286 print(fixture_dirs)
> 287 print(len(fixture_dirs))
> 288 print(len(set(fixture_dirs)))
> 289 if len(fixture_dirs) != len(set(fixture_dirs)):
> 290 raise ImproperlyConfigured("settings.FIXTURE_DIRS
> contains duplicates.")
> }}}
> and set my FIXTURE_DIRS like so:
> `FIXTURE_DIRS=('piece/core/fixtures','piece/core/fixtures2')`
>
> when I run loaddata I see:
> {{{
> ('piece/core/fixtures', 'piece/core/fixtures2')
> 2
> 2
> Installed 6 object(s) from 2 fixture(s)
> }}}
> so far so good.  Now set it like so:
> `FIXTURE_DIRS=('piece/core/fixtures'')`
>
> I run it and get:
> 
> piece/core/fixtures
> 19
> 12
> Traceback (most recent call last):
>   File "manage.py", line 16, in 
> execute_from_command_line(sys.argv)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/__init__.py", line 401, in
> execute_from_command_line
> utility.execute()
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/__init__.py", line 395, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/base.py", line 328, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/base.py", line 369, in execute
> output = self.handle(*args, **options)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 72, in handle
> self.loaddata(fixture_labels)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 106, in
> loaddata
> if self.find_fixtures(fixture_label):
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 235, in
> find_fixtures
> fixture_dirs = self.fixture_dirs
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/utils/functional.py", line 48, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 290, in
> fixture_dirs
> raise ImproperlyConfigured("settings.FIXTURE_DIRS contains
> duplicates.")
> django.core.exceptions.ImproperlyConfigured: settings.FIXTURE_DIRS
> contains duplicates.
> 

New description:

 loaddata.py incorrectly throws an ImproperlyConfigured exception when
 FIXTURE_DIRS is a list of one.  See:
 
https://github.com/django/django/blame/798835112d81b852efaae0e067af389c733cd1b3/django/core/management/commands/loaddata.py#L296

 I changed this code to:
 {{{
 286 print(fixture_dirs)
 287 print(len(fixture_dirs))
 288 print(len(set(fixture_dirs)))
 289 if len(fixture_dirs) != len(set(fixture_dirs)):
 290 raise ImproperlyConfigured("settings.FIXTURE_DIRS contains
 duplicates.")
 }}}
 and set my FIXTURE_DIRS like so:
 `FIXTURE_DIRS=('piece/core/fixtures','piece/core/fixtures2')`

 when I run loaddata I see:
 {{{
 ('piece/core/fixtures', 'piece/core/fixtures2')
 2
 2
 Installed 6 object(s) from 2 fixture(s)
 }}}
 so far so good.  Now set it like so:
 `FIXTURE_DIRS=('piece/core/fixtures'')`

 I run it and get:
 {{{
 piece/core/fixtures
 19
 12
 Traceback (most recent call last):
   File "manage.py", line 16, in 
 execute_from_command_line(sys.argv)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/__init__.py", line 401, in
 

Re: [Django] #31738: invalid exception thrown "django.core.exceptions.ImproperlyConfigured: settings.FIXTURE_DIRS contains duplicates."

[Django]

#31738: invalid exception thrown "django.core.exceptions.ImproperlyConfigured:
settings.FIXTURE_DIRS contains duplicates."
-+-
 Reporter:  timharsch|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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
 * component:  Uncategorized => Core (Management commands)
 * easy:  1 => 0


Old description:

> loaddata.py incorrectly throws an ImproperlyConfigured exception when
> FIXTURE_DIRS is a list of one.  See:
> https://github.com/django/django/blame/798835112d81b852efaae0e067af389c733cd1b3/django/core/management/commands/loaddata.py#L296
>
> I changed this code to:
> 286 print(fixture_dirs)
> 287 print(len(fixture_dirs))
> 288 print(len(set(fixture_dirs)))
> 289 if len(fixture_dirs) != len(set(fixture_dirs)):
> 290 raise ImproperlyConfigured("settings.FIXTURE_DIRS
> contains duplicates.")
>
> and set my FIXTURE_DIRS like so:
> FIXTURE_DIRS=('piece/core/fixtures','piece/core/fixtures2')
>
> when I run loaddata I see:
> ('piece/core/fixtures', 'piece/core/fixtures2')
> 2
> 2
> Installed 6 object(s) from 2 fixture(s)
>
> so far so good.  Now set it like so:
> FIXTURE_DIRS=('piece/core/fixtures'')
>
> I run it and get:
>
> piece/core/fixtures
> 19
> 12
> Traceback (most recent call last):
>   File "manage.py", line 16, in 
> execute_from_command_line(sys.argv)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/__init__.py", line 401, in
> execute_from_command_line
> utility.execute()
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/__init__.py", line 395, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/base.py", line 328, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/base.py", line 369, in execute
> output = self.handle(*args, **options)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 72, in handle
> self.loaddata(fixture_labels)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 106, in
> loaddata
> if self.find_fixtures(fixture_label):
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 235, in
> find_fixtures
> fixture_dirs = self.fixture_dirs
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/utils/functional.py", line 48, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
> packages/django/core/management/commands/loaddata.py", line 290, in
> fixture_dirs
> raise ImproperlyConfigured("settings.FIXTURE_DIRS contains
> duplicates.")
> django.core.exceptions.ImproperlyConfigured: settings.FIXTURE_DIRS
> contains duplicates.

New description:

 loaddata.py incorrectly throws an ImproperlyConfigured exception when
 FIXTURE_DIRS is a list of one.  See:
 
https://github.com/django/django/blame/798835112d81b852efaae0e067af389c733cd1b3/django/core/management/commands/loaddata.py#L296

 I changed this code to:
 {{{
 286 print(fixture_dirs)
 287 print(len(fixture_dirs))
 288 print(len(set(fixture_dirs)))
 289 if len(fixture_dirs) != len(set(fixture_dirs)):
 290 raise ImproperlyConfigured("settings.FIXTURE_DIRS contains
 duplicates.")
 }}}
 and set my FIXTURE_DIRS like so:
 `FIXTURE_DIRS=('piece/core/fixtures','piece/core/fixtures2')`

 when I run loaddata I see:
 {{{
 ('piece/core/fixtures', 'piece/core/fixtures2')
 2
 2
 Installed 6 object(s) from 2 fixture(s)
 }}}
 so far so good.  Now set it like so:
 `FIXTURE_DIRS=('piece/core/fixtures'')`

 I run it and get:
 
 piece/core/fixtures
 19
 12
 Traceback (most recent call last):
   File "manage.py", line 16, in 
 execute_from_command_line(sys.argv)
   File 

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Accepted
  many;relationship;intermediate;table;through|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * 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/072.6feae3300d51870e82cc6fe4075cd2a6%40djangoproject.com.

[Django] #31738: invalid exception thrown "django.core.exceptions.ImproperlyConfigured: settings.FIXTURE_DIRS contains duplicates."

[Django]

#31738: invalid exception thrown "django.core.exceptions.ImproperlyConfigured:
settings.FIXTURE_DIRS contains duplicates."
-+
   Reporter:  timharsch  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  master
   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  |
-+
 loaddata.py incorrectly throws an ImproperlyConfigured exception when
 FIXTURE_DIRS is a list of one.  See:
 
https://github.com/django/django/blame/798835112d81b852efaae0e067af389c733cd1b3/django/core/management/commands/loaddata.py#L296

 I changed this code to:
 286 print(fixture_dirs)
 287 print(len(fixture_dirs))
 288 print(len(set(fixture_dirs)))
 289 if len(fixture_dirs) != len(set(fixture_dirs)):
 290 raise ImproperlyConfigured("settings.FIXTURE_DIRS contains
 duplicates.")

 and set my FIXTURE_DIRS like so:
 FIXTURE_DIRS=('piece/core/fixtures','piece/core/fixtures2')

 when I run loaddata I see:
 ('piece/core/fixtures', 'piece/core/fixtures2')
 2
 2
 Installed 6 object(s) from 2 fixture(s)

 so far so good.  Now set it like so:
 FIXTURE_DIRS=('piece/core/fixtures'')

 I run it and get:

 piece/core/fixtures
 19
 12
 Traceback (most recent call last):
   File "manage.py", line 16, in 
 execute_from_command_line(sys.argv)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/__init__.py", line 401, in
 execute_from_command_line
 utility.execute()
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/__init__.py", line 395, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/base.py", line 328, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/base.py", line 369, in execute
 output = self.handle(*args, **options)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/commands/loaddata.py", line 72, in handle
 self.loaddata(fixture_labels)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/commands/loaddata.py", line 106, in
 loaddata
 if self.find_fixtures(fixture_label):
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/commands/loaddata.py", line 235, in
 find_fixtures
 fixture_dirs = self.fixture_dirs
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/utils/functional.py", line 48, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
   File "/Users/harsch/.pyenv/versions/p38/lib/python3.8/site-
 packages/django/core/management/commands/loaddata.py", line 290, in
 fixture_dirs
 raise ImproperlyConfigured("settings.FIXTURE_DIRS contains
 duplicates.")
 django.core.exceptions.ImproperlyConfigured: settings.FIXTURE_DIRS
 contains duplicates.

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

Re: [Django] #31730: manage.py sqlsequencereset not implemented for sqlite3

[Django]

#31730: manage.py sqlsequencereset not implemented for sqlite3
-+-
 Reporter:  axil |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sql sequence reset   | Triage Stage:  Accepted
  sqlite3|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by axil):

 Replying to [comment:4 Simon Charette]:
 > In a following commit the logic that identifies the sequences that need
 to be reset should be moved to the command itself to avoid the huge amount
 of boilerplate repeated in the current PostgreSQL and Oracle
 `DatabaseOperations` implementations. That will also avoid leaking
 `db.models` abstraction to the `db.backends` ones. We should probably use
 `connection.introspection.sequence_list()` to ''JOIN'' its return value to
 the specified model subset tables. In the end I think the signature of the
 of the `sequence_reset_sql` method should be something like `(style,
 sequences)`.
 I've done this part in a separate PR:
 https://github.com/django/django/pull/13103
 So far for postgres only. Please have a look.

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

Re: [Django] #31736: PostgreSQL InspectDB test fails on Windows.

[Django]

#31736: PostgreSQL InspectDB test fails on Windows.
-+-
 Reporter:  Ahmad A. Hussein |Owner:  Ahmad A.
 |  Hussein
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgresql,  | Triage Stage:  Accepted
  inspectdb  |
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:"ac0ff7d7001bdf2c6669857ea184656d097bd603" ac0ff7d]:
 {{{
 #!CommitTicketReference repository=""
 revision="ac0ff7d7001bdf2c6669857ea184656d097bd603"
 [3.1.x] Fixed #31736 -- Fixed
 InspectDBTransactionalTests.test_foreign_data_wrapper crash on Windows.

 Backport of 798835112d81b852efaae0e067af389c733cd1b3 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.2a97cfc1efaa02f1ae322ec7a9c00050%40djangoproject.com.

Re: [Django] #31736: PostgreSQL InspectDB test fails on Windows.

[Django]

#31736: PostgreSQL InspectDB test fails on Windows.
-+-
 Reporter:  Ahmad A. Hussein |Owner:  Ahmad A.
 |  Hussein
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgresql,  | Triage Stage:  Accepted
  inspectdb  |
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:"798835112d81b852efaae0e067af389c733cd1b3" 79883511]:
 {{{
 #!CommitTicketReference repository=""
 revision="798835112d81b852efaae0e067af389c733cd1b3"
 Fixed #31736 -- Fixed
 InspectDBTransactionalTests.test_foreign_data_wrapper crash on Windows.
 }}}

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

Re: [Django] #31541: Improve documentation of django.contrib.redirects.

[Django]

#31541: Improve documentation of django.contrib.redirects.
-+-
 Reporter:  Adam (Chainz)|Owner:  Yash
  Johnson|  Saini
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.redirects|  Version:  master
 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:  1|UI/UX:  0
-+-
Changes (by felixxm):

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


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

Re: [Django] #31541: Improve documentation of django.contrib.redirects.

[Django]

#31541: Improve documentation of django.contrib.redirects.
-+-
 Reporter:  Adam (Chainz)|Owner:  Yash
  Johnson|  Saini
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"648f6ffcd700de4990957c84000484f066b9edb2" 648f6ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="648f6ffcd700de4990957c84000484f066b9edb2"
 [3.1.x] Refs #31541 -- Added example of creating Redirect objects to
 redirects app docs.

 Backport of a8c0246ece0716cea2ea6c1b313d4d93a10ee333 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/068.6f64067d0443286eccfac4bc077c937b%40djangoproject.com.

Re: [Django] #31541: Improve documentation of django.contrib.redirects.

[Django]

#31541: Improve documentation of django.contrib.redirects.
-+-
 Reporter:  Adam (Chainz)|Owner:  Yash
  Johnson|  Saini
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"d5118d2abc62eecbbce14b398ed7203e102444ae" d5118d2a]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5118d2abc62eecbbce14b398ed7203e102444ae"
 Refs #31541 -- Updated Redirect.new_path.help_text.
 }}}

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

Re: [Django] #31541: Improve documentation of django.contrib.redirects.

[Django]

#31541: Improve documentation of django.contrib.redirects.
-+-
 Reporter:  Adam (Chainz)|Owner:  Yash
  Johnson|  Saini
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"a8c0246ece0716cea2ea6c1b313d4d93a10ee333" a8c0246]:
 {{{
 #!CommitTicketReference repository=""
 revision="a8c0246ece0716cea2ea6c1b313d4d93a10ee333"
 Refs #31541 -- Added example of creating Redirect objects to redirects app
 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/068.8328f7d5aa841fddef90afdcdf9d99e2%40djangoproject.com.

Re: [Django] #31736: PostgreSQL InspectDB test fails on Windows. (was: PostgreSQL InspectDB test fails due to assuming it only runs on Linux)

[Django]

#31736: PostgreSQL InspectDB test fails on Windows.
-+-
 Reporter:  Ahmad A. Hussein |Owner:  Ahmad A.
 |  Hussein
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:  Accepted
  inspectdb  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/13102 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/066.6ff3c955591fb0a1c29e14ddd888c2e1%40djangoproject.com.

[Django] #31737: Strange admin behaviour on Django 3.1b1 with Firefox

[Django]

#31737: Strange admin behaviour on Django 3.1b1 with Firefox
---+
   Reporter:  Claude Paroz |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  contrib.admin|Version:  3.1
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 On Firefox (68 ESR), when trying to display any model changelist page, I
 find myself with the `nav-sidebar` taking the whole page widths
 (changelist itself is completely hidden).

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

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Accepted
  many;relationship;intermediate;table;through|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 This should be solveable by making sure the schema name is included in the
 `SET CONSTRAINT` as well.

 That would result in `SET CONSTRAINTS
 "loader"."data_load_valuation_id_9af1ae91_fk_valuation_id" IMMEDIATE`.

-- 
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/072.3d20cdaedcc08f1f92e439a20e44b73c%40djangoproject.com.

Re: [Django] #31736: PostgreSQL InspectDB test fails due to assuming it only runs on Linux

[Django]

#31736: PostgreSQL InspectDB test fails due to assuming it only runs on Linux
-+-
 Reporter:  Ahmad A. Hussein |Owner:  Ahmad A.
 |  Hussein
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  inspectdb  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ahmad A. Hussein):

 * owner:  nobody => Ahmad A. Hussein


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

Re: [Django] #31736: PostgreSQL InspectDB test fails due to assuming it only runs on Linux (was: PostgreSQL InspectDB tests due to assuming it only runs on Linux)

[Django]

#31736: PostgreSQL InspectDB test fails due to assuming it only runs on Linux
-+-
 Reporter:  Ahmad A. Hussein |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  inspectdb  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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/066.9c9c2cf5b23a56502bbf2a5dcc372626%40djangoproject.com.

Re: [Django] #31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux

[Django]

#31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux
-+-
 Reporter:  Ahmad A. Hussein |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  inspectdb  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Ahmad A. Hussein:

Old description:

> On Windows,
> {{{inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper}}}
> fails with the following error:
>
> {{{
> The error was: could not open file "/dev/null" for reading: No such file
> or directory
> HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
> You may want a client-side facility such as psql's \copy.
>
> AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not
> found in [...]
> }}}
> This is because of the way the test is written as
> [https://github.com/django/django/pull/12646#issuecomment-647944821/
> pointed out by]. Patch fixes this by generalizing the test to use
> os.devnull to be OS-agnostic instead of /dev/null always.

New description:

 On Windows,
 {{{inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper}}}
 fails with the following error:

 {{{
 The error was: could not open file "/dev/null" for reading: No such file
 or directory
 HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
 You may want a client-side facility such as psql's \copy.

 AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not found
 in [...]
 }}}
 This is because of the way the test is written as
 [https://github.com/django/django/pull/12646#issuecomment-647944821/
 pointed out by Nick Pope]. Patch fixes this by generalizing the test to
 use os.devnull to be OS-agnostic instead of /dev/null always.

--

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

Re: [Django] #31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux

[Django]

#31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux
-+-
 Reporter:  Ahmad A. Hussein |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  inspectdb  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Ahmad A. Hussein:

Old description:

> On Windows,
> ```inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper```
> fails with the following error:
>
> ```
> The error was: could not open file "/dev/null" for reading: No such file
> or directory
> HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
> You may want a client-side facility such as psql's \copy.
>
> AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not
> found in [...]
> ```
> This is because of the way the test is written as
> [https://github.com/django/django/pull/12646#issuecomment-647944821/
> pointed out by]. Patch fixes this by generalizing the test to use
> os.devnull to be OS-agnostic instead of /dev/null always.

New description:

 On Windows,
 {{{inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper}}}
 fails with the following error:

 {{{
 The error was: could not open file "/dev/null" for reading: No such file
 or directory
 HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
 You may want a client-side facility such as psql's \copy.

 AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not found
 in [...]
 }}}
 This is because of the way the test is written as
 [https://github.com/django/django/pull/12646#issuecomment-647944821/
 pointed out by]. Patch fixes this by generalizing the test to use
 os.devnull to be OS-agnostic instead of /dev/null always.

--

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

Re: [Django] #31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux

[Django]

#31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux
-+-
 Reporter:  Ahmad A. Hussein |Owner:  nobody
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql,  | Triage Stage:
  inspectdb  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Ahmad A. Hussein:

Old description:

> On Windows,
> ```inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper```
> fails with the following error:
>
> ```
> The error was: could not open file "/dev/null" for reading: No such file
> or directory
> HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
> You may want a client-side facility such as psql's \copy.
>
> AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not
> found in [...]
> ```
> This is because of the way the test is written as [pointed out
> by](https://github.com/django/django/pull/12646#issuecomment-647944821).
> Patch fixes this by generalizing the test to use os.devnull to be OS-
> agnostic instead of /dev/null always.

New description:

 On Windows,
 ```inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper```
 fails with the following error:

 ```
 The error was: could not open file "/dev/null" for reading: No such file
 or directory
 HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
 You may want a client-side facility such as psql's \copy.

 AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not found
 in [...]
 ```
 This is because of the way the test is written as
 [https://github.com/django/django/pull/12646#issuecomment-647944821/
 pointed out by]. Patch fixes this by generalizing the test to use
 os.devnull to be OS-agnostic instead of /dev/null always.

--

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

[Django] #31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux

[Django]

#31736: PostgreSQL InspectDB tests due to assuming it only runs on Linux
-+-
   Reporter:  Ahmad A.   |  Owner:  nobody
  Hussein|
   Type:  Bug| Status:  assigned
  Component:  Testing|Version:  master
  framework  |   Keywords:  postgresql,
   Severity:  Normal |  inspectdb
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 On Windows,
 ```inspectdb..tests.InspectDBTransactionalTests.test_foreign_data_wrapper```
 fails with the following error:

 ```
 The error was: could not open file "/dev/null" for reading: No such file
 or directory
 HINT:  COPY FROM instructs the PostgreSQL server process to read a file.
 You may want a client-side facility such as psql's \copy.

 AssertionError: 'class InspectdbIrisForeignTable(models.Model):' not found
 in [...]
 ```
 This is because of the way the test is written as [pointed out
 by](https://github.com/django/django/pull/12646#issuecomment-647944821).
 Patch fixes this by generalizing the test to use os.devnull to be OS-
 agnostic instead of /dev/null always.

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

Re: [Django] #31541: Improve documentation of django.contrib.redirects.

[Django]

#31541: Improve documentation of django.contrib.redirects.
-+-
 Reporter:  Adam (Chainz)|Owner:  Yash
  Johnson|  Saini
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * 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/068.68e3f6145800cfc4ba42a7c8153c01c0%40djangoproject.com.

Re: [Django] #9061: formsets with can_delete=True shouldn't add delete field to extra forms

[Django]

#9061: formsets with can_delete=True shouldn't add delete field to extra forms
-+-
 Reporter:  Gabriel Farrell  |Owner:  David
 |  Smith
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 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 Carlton Gibson):

 * 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/061.c01273eda1fdceb43c17d625bacdd859%40djangoproject.com.

Re: [Django] #31692: compilemessages needlessly runs msgfmt on unchanged .po files

[Django]

#31692: compilemessages needlessly runs msgfmt on unchanged .po files
-+-
 Reporter:  Per Cederqvist   |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 GitHub ):

 In [changeset:"02ea98bc2ff972f7705bfffb24843494086d011f" 02ea98bc]:
 {{{
 #!CommitTicketReference repository=""
 revision="02ea98bc2ff972f7705bfffb24843494086d011f"
 Refs #31692 -- Fixed compilemessages crash on Windows with Python < 3.8.

 Regression in ed0a040773f5bad187170ab4e3b094fe3108d702.
 See https://bugs.python.org/issue31961
 }}}

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

Re: [Django] #31443: LoginRequiredMixin/AccessMixin bug with off-site LOGIN_URL

[Django]

#31443: LoginRequiredMixin/AccessMixin bug with off-site LOGIN_URL
-+-
 Reporter:  minusf   |Owner:  minusf
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  login required   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"cc7c16af98e4c9a7146c248c8567aac7a50e0fbb" cc7c16af]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc7c16af98e4c9a7146c248c8567aac7a50e0fbb"
 Fixed #31443 -- Fixed login redirection in auth mixins when LOGIN_URL is
 off-site URL.
 }}}

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

Re: [Django] #29177: Unmanaged models with ForeignKeys do not get those fields serialized into their migration state when CreateModel happens.

[Django]

#29177: Unmanaged models with ForeignKeys do not get those fields serialized 
into
their migration state when CreateModel happens.
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Ponytech):

 Replying to [comment:7 Daniel Naab]:
 > I hit this bug also, and worked around by:
 >
 > 1) Making the models `managed = True`
 > 2) Running `manage.py makemigrations` for those models
 > 3) Manually switched all `'managed': True` models in the migration to
 `'managed': False`
 > 4) Switch models back to `managed = False`

 Same bug here and this workaround saved my day.
 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/067.0f67108cf1eb709f241175691a3f57e2%40djangoproject.com.

Re: [Django] #31443: LoginRequiredMixin/AccessMixin bug with off-site LOGIN_URL

[Django]

#31443: LoginRequiredMixin/AccessMixin bug with off-site LOGIN_URL
-+-
 Reporter:  minusf   |Owner:  minusf
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  login required   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * version:  3.0 => master
 * 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.e9dfdb320b6611791210b7a18cd6970a%40djangoproject.com.

Re: [Django] #31358: Increase default password salt size in BasePasswordHasher.

[Django]

#31358: Increase default password salt size in BasePasswordHasher.
--+
 Reporter:  Jon Moroney   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"136ec9b62bd0b105f281218d7cad54b7db7a4bab" 136ec9b6]:
 {{{
 #!CommitTicketReference repository=""
 revision="136ec9b62bd0b105f281218d7cad54b7db7a4bab"
 Refs #31358 -- Added decode() to password hashers.

 By convention a hasher which does not use a salt should populate the
 decode dict with `None` rather than omit the dict key.

 Co-Authored-By: Florian Apolloner 
 }}}

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

Re: [Django] #25281: Permission strings don't uniquely identify permissions

[Django]

#25281: Permission strings don't uniquely identify permissions
-+-
 Reporter:  Przemysław   |Owner:  tsyplakou
  Pietrzkiewicz  |
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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

Re: [Django] #31717: WSGI calling close causes premature close_if_unusable_or_obsolete calls during transaction?

[Django]

#31717: WSGI calling close causes premature close_if_unusable_or_obsolete calls
during transaction?
---+--
 Reporter:  Yu Li  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  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 Carlton Gibson):

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


Comment:

 There's not enough to go on here. If you could upload a minimal reproduce
 project so we can investigate that would be awesome. 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/066.379195f418513e2f6f134001fa544e07%40djangoproject.com.

Re: [Django] #31703: Name all initial migrations "NNNN_initial".

[Django]

#31703: Name all initial migrations "_initial".
-+-
 Reporter:  Jon Dufresne |Owner:  Jon
 Type:   |  Dufresne
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 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 felixxm):

 * owner:  nobody => Jon Dufresne
 * needs_better_patch:  0 => 1
 * 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.33b4b4e3b651b920f68177d51c1e6eb5%40djangoproject.com.

Re: [Django] #31722: RangeWidget produces 1 subwidget, itself

[Django]

#31722: RangeWidget produces 1 subwidget, itself
-+-
 Reporter:  Ryan Heard   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  3.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  MultiWidget  | Triage Stage:
  RangeWidget Widget |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 You need to drill down further to access the child widgets.

 `form.date_range` is a BoundField. `subwidgets` returns the single item
 list of the BoundWidget wrapping your RangeWidget, which is a MultiWidget
 subclass. The RangeWidget has a `widgets` property containing the child
 widgets you're after.

 As
 
[https://docs.djangoproject.com/en/3.0/ref/forms/widgets/#django.forms.MultiWidget.get_context
 per the multi widget docs] RangeWidget will add `subwidgets` to the
 context to be used by the **widget template**:

 {{{
 >>>f["a_range"].subwidgets[0].parent_widget.get_context('a_range', '',
 {})["widget"]["subwidgets"]
 [{'name': 'a_range_0', 'is_hidden': False, 'required': False, 'value':
 None, 'attrs': {}, 'template_name': 'django/forms/widgets/number.html',
 'type': 'number'}, {'name': 'a_range_1', 'is_hidden': False, 'required':
 False, 'value': None, 'attrs': {}, 'template_name':
 'django/forms/widgets/number.html', 'type': 'number'}]
 }}}

 It's that that can be iterated as you're intending. Please see
 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/064.3e3036dbfd55a859af9285ad04c3df07%40djangoproject.com.

Re: [Django] #31725: Setting ImageField and FileField default to a static file

[Django]

#31725: Setting ImageField and FileField default to a static file
-+-
 Reporter:  Daniel González  |Owner:  nobody
  Fernández  |
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  static image | Triage Stage:
  default|  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:   => wontfix


Comment:

 Yes, I think if there's no image then setting `null=True` is correct. You
 **could** use a custom field to encapsulate the placeholder handling but
 it strikes me doing it at the presentation layer is fine.

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