date:20220803

Re: [Django] #33891: TypeError when trying to run tests in parallel with spawn.

2022-08-03 Thread Django

#33891: TypeError when trying to run tests in parallel with spawn.
-+-
 Reporter:  Kevin Renskers   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  4.1
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15911 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/0107018267a3c1bf-960553ac-f513-43c2-b360-bdb7a754d580-00%40eu-central-1.amazonses.com.

[Django] #33892: Management commands with flags using action="store_false" create possible inverted boolean flags in call_command

2022-08-03 Thread Django

#33892: Management commands with flags using action="store_false" create 
possible
inverted boolean flags in call_command
-+-
   Reporter:  lukewiwa   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Core   |Version:  4.0
  (Management commands)  |
   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  |
-+-
 In any management command which parses a flag using the action
 `store_false` it has an unexpected side effect when calling the management
 command from the `call_command` function. When `call_command` parses the
 arg it won't be taken into account the action and can create weird
 inversions of the intent of the boolean.

 **example:**

 from the command line this will work fine:

 {{{
 ./manage.py flush --no-input
 }}}

 However if called from the `call_command` with one of the recommended ways
 we might expect `no_input=True` to work the same but it doesn't.

 {{{
 from django.core.management import call_command

 call_command("flush", no_input=True)

 You have requested a flush of the database.
 This will IRREVERSIBLY DESTROY all data currently in the ":memory:"
 database,
 and return each table to an empty state.
 Are you sure you want to do this?

 Type 'yes' to continue, or 'no' to cancel:

 call_command("flush", no_input=False)  # This will continue with no input
 required
 }}}

 I'm not sure how widespread this is but `flush` is definitely affected

-- 
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/0107018267a1da67-349cad37-7e4a-42eb-8f10-f6f32c20e21d-00%40eu-central-1.amazonses.com.

Re: [Django] #33891: TypeError when trying to run tests in parallel with spawn. (was: TypeError when trying to run tests in parallel)

2022-08-03 Thread Django

#33891: TypeError when trying to run tests in parallel with spawn.
-+-
 Reporter:  Kevin Renskers   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  4.1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => assigned
 * severity:  Normal => Release blocker
 * cc: Carlton Gibson (added)
 * owner:  nobody => Mariusz Felisiak
 * stage:  Unreviewed => Accepted


Comment:

 It looks that I overcomplicated 41c4cb253c137edf5a96b7408ea55d57d6e0602a,
 sorry. Does the following patch work for you?
 {{{#!diff
 diff --git a/django/test/runner.py b/django/test/runner.py
 index 270ddf5b59..24ce766ce1 100644
 --- a/django/test/runner.py
 +++ b/django/test/runner.py
 @@ -443,6 +443,11 @@ def _run_subsuite(args):
  return subsuite_index, result.events


 +def _process_setup_stub(*args):
 +"""Stub method to simplify run() implementation."""
 +pass
 +
 +
  class ParallelTestSuite(unittest.TestSuite):
  """
  Run a series of tests in parallel in several processes.
 @@ -461,6 +466,7 @@ class ParallelTestSuite(unittest.TestSuite):

  # In case someone wants to modify these in a subclass.
  init_worker = _init_worker
 +process_setup = _process_setup_stub
  process_setup_args = ()
  run_subsuite = _run_subsuite
  runner_class = RemoteTestRunner
 @@ -474,14 +480,6 @@ class ParallelTestSuite(unittest.TestSuite):
  self.serialized_contents = None
  super().__init__()

 -def process_setup(self, *args):
 -"""
 -Stub method to simplify run() implementation. "self" is never
 actually
 -passed because a function implementing this method (__func__) is
 -always used, not the method itself.
 -"""
 -pass
 -
  def run(self, result):
  """
  Distribute test cases across workers.

 }}}

-- 
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/01070182677e02bb-29644bb3-e79f-4c15-be0e-42a9e0a2ae12-00%40eu-central-1.amazonses.com.

Re: [Django] #33890: call_command('startproject', 'project_name', '.') raises CommandError 'project_name'

2022-08-03 Thread Django

#33890: call_command('startproject', 'project_name', '.') raises CommandError
'project_name'
-+-
 Reporter:  piscvau  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  4.0
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  call_command raises  | Triage Stage:
  exception  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 > SO I do believe this is a bug!.

 There is no need to shout, and no, it's not the same, `django-admin
 startproject project-name .` tries to create a project called `project-
 name`, on the other hand, in your Python shell example you tried to create
 a project called `Path.cwd().stem` which conflicts with the name of an
 existing Python module. Again, please try to use support channels.

-- 
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/010701826759da27-a0a6edb9-6636-467a-ac55-9af2e4608f0a-00%40eu-central-1.amazonses.com.

Re: [Django] #28333: Filter and subquery for window expressions

2022-08-03 Thread Django

#28333: Filter and subquery for window expressions
-+-
 Reporter:  Mads Jensen  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  window orm filter| Triage Stage:  Accepted
  subquery GSoC  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Had a first stab at the above and it seems to be working relatively well,
 [https://github.com/django/django/compare/main...charettes:django:ticket-28333
 -filter-by-window not too intrusive of a change]. I'll give a shot at
 implementing #26780 on to of it now to confirm it could work.

 As a side note it seems that the Snowflake database has an SQL extension
 to filter against window functions, the [https://docs.snowflake.com/en
 /sql-reference/constructs/qualify.html QUALIFY clause].

-- 
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/01070182671431a4-3d78206a-3b30-41ce-9306-c268ebbdc057-00%40eu-central-1.amazonses.com.

Re: [Django] #5815: Adds per-view cache refreshing (clearing)

2022-08-03 Thread Django

Comment (by Mike Lissner):

Just to add a data points here, I spent a bunch of time today trying to
figure out which key to delete to nuke a cached page and eventually gave
up and just nuked a larger part of the cache in hopes of getting lucky (I
did).

Having a helper util just to figure out what the cache key value is would
be really nice.

Here's a summary of my failed research:

- "Expire a view-cache in Django?"
(https://stackoverflow.com/q/2268417/64911) — Says it works with < django
1.7. I didn't try it, but I don't think it'd work.
- "How to invalidate cache_page in Django?"
(https://stackoverflow.com/q/33749369/64911) — Accepted answer just says
to cache the queryset instead of using cache_page.
- "How to manually clear/update a cached view in django"
(https://stackoverflow.com/q/47040438/64911) — Has a solution, but it's
quite old and doesn't work. This is when I gave up.

The reason I need this (and couldn't wait for the cache to just expire) is
because I use the db cache to cache really big sitemaps that don't change
very often. The cache is usually on the order of a couple of weeks.

--
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/0107018265d1cd2a-f9263e1b-6927-4ddf-96b9-4703c9179571-00%40eu-central-1.amazonses.com.

Re: [Django] #31721: Allow ModelForm meta to specify formfield_callback.

2022-08-03 Thread Django

#31721: Allow ModelForm meta to specify formfield_callback.
---+---
 Reporter:  Klaas-Jan Gorter   |Owner:  Kamil Turek
 Type:  New feature|   Status:  assigned
Component:  Forms  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords:  modelform_factory  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by Kamil Turek):

 * owner:  nobody => Kamil Turek
 * 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/01070182659d744c-c9e80f8a-4ede-4ed0-9bdb-b5cc61807922-00%40eu-central-1.amazonses.com.

Re: [Django] #33890: call_command('startproject', 'project_name', '.') raises CommandError 'project_name'

2022-08-03 Thread Django

#33890: call_command('startproject', 'project_name', '.') raises CommandError
'project_name'
-+-
 Reporter:  piscvau  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  4.0
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  call_command raises  | Triage Stage:
  exception  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by piscvau:

Old description:

> call_command ('startproject', 'project_name', '.') shoud create a project
> named 'project_name' in the current directory.
>
> to reproduce the bug :
> from django.core import management
> from pathlib import Path
> project_name = Path.cwd().stem
> management.call_command('startproject', project_name, '.')
>
> This raises the exception
>
> django.core.management.base.CommandError:   conflicts with
> the name of an existing Python module and cannot be used as a project
> name. Please try another name.
>
> This is because the initial directory of the python script is in
> sys.module.

New description:

 call_command ('startproject', 'project_name', '.') shoud create a project
 named 'project_name' in the current directory.

 to reproduce the bug :
 from django.core import management
 from pathlib import Path
 project_name = Path.cwd().stem
 management.call_command('startproject', project_name, '.')

 This raises the exception

 django.core.management.base.CommandError:   conflicts with
 the name of an existing Python module and cannot be used as a project
 name. Please try another name.

 This is because the initial directory of the python script is in
 sys.module.

 When called from the command line, in the exact same condition, the
 command passes :
  in directory project_name :
 django-admin startproject project-name .

 in django docs it is described as the right usage to create a project
 project_name in the current directory!

 SO I do believe this is a bug!.

--

-- 
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/01070182653e440d-fbbcd2aa-dc72-4432-8b01-c69046118620-00%40eu-central-1.amazonses.com.

Re: [Django] #33353: Can't collect static files if don't have vendor's JavaScript source map files

2022-08-03 Thread Django

#33353: Can't collect static files if don't have vendor's JavaScript source map
files
-+-
 Reporter:  Michael  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  4.0
 Severity:  Release blocker  |   Resolution:  invalid
 Keywords:  manifeststatic   | Triage Stage:
  storage|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aodin):

 Django Rest Framework does not include its source map files despite
 linking to them: https://github.com/encode/django-rest-
 
framework/blob/fd8adb32cec9c7545039f03cc3aa6cda95d4d692/rest_framework/static/rest_framework/css/bootstrap.min.css#L6

 The `collectstatic` command is currently broken for any builds on Django
 4.1 that include DRF and use `ManifestStaticFilesStorage`.

 Developers will need to either:

 1. Downgrade to 4.0 until DRF adds its source maps (or removes the link to
 them)
 2. Sub-class `ManifestStaticFilesStorage` with their own fix, such as
 disabling `manifest_strict` or reverting the matched patterns (both of
 which are mentioned above)

-- 
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/01070182653329e8-0fbeb832-8ce6-4951-b735-5a5517b46386-00%40eu-central-1.amazonses.com.

[Django] #33891: TypeError when trying to run tests in parallel

2022-08-03 Thread Django

#33891: TypeError when trying to run tests in parallel
-+
Reporter: kevinrenskers | Owner: nobody
Type: Bug| Status: new
Component: Testing framework |Version: 4.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+
After updating to Django 4.1 I can no longer run my tests in parallel. I
get seemingly endless errors in my terminal.

{{{
(env) $ ./manage.py test --parallel
Found 124 test(s).
Creating test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
System check identified no issues (0 silenced).
Process SpawnPoolWorker-7:
Process SpawnPoolWorker-2:
Process SpawnPoolWorker-6:
Process SpawnPoolWorker-3:
Process SpawnPoolWorker-1:
Process SpawnPoolWorker-8:
Process SpawnPoolWorker-5:
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/process.py",
line 315, in _bootstrap
self.run()
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/process.py",
line 108, in run
self._target(*self._args, **self._kwargs)
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/pool.py",
line 109, in worker
initializer(*initargs)
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/process.py",
line 315, in _bootstrap
self.run()
File "/Users/kevin/Workspace/cn-django/env/lib/python3.10/site-
packages/django/test/runner.py", line 420, in _init_worker
process_setup(*process_setup_args)
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/process.py",
line 108, in run
self._target(*self._args, **self._kwargs)
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/pool.py",
line 109, in worker
initializer(*initargs)
File

"/opt/homebrew/Cellar/python@3.10/3.10.5/Frameworks/Python.framework/Versions/3.10/lib/python3.10/multiprocessing/process.py",
line 315, in _bootstrap
self.run()
File

That traceback and error then keeps repeating.

If I run the tests just with `./manage.py test`, everything works 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/0107018265055c68-fbd3d469-4cd3-42dd-957e-67f78c8183f9-00%40eu-central-1.amazonses.com.

Re: [Django] #33865: Optimize django.core.handlers.wsgi.LimitedStream

2022-08-03 Thread Django

#33865: Optimize django.core.handlers.wsgi.LimitedStream
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi,| Triage Stage:  Accepted
  limitedstream, performance |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 Per Florian's and Nick's comments.

-- 
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/0107018265043f6d-a7ff8d26-c77d-4126-97a4-482fe7708659-00%40eu-central-1.amazonses.com.

Re: [Django] #33889: Error in admin.site.register on pypy3.8 and Django 4.1+.

2022-08-03 Thread Django

#33889: Error in admin.site.register on pypy3.8 and Django 4.1+.
+--
 Reporter:  Hasan Ramezani  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  4.1
 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 Mariusz Felisiak):

 * resolution:  needsinfo => invalid


Comment:

 I missed my own comments 🤦

-- 
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/0107018264fddc4d-6ff1686e-e78f-4be8-8a03-e84507976600-00%40eu-central-1.amazonses.com.

Re: [Django] #33890: call_command('startproject', 'project_name', '.') raises CommandError 'project_name'

2022-08-03 Thread Django

#33890: call_command('startproject', 'project_name', '.') raises CommandError
'project_name'
-+-
 Reporter:  piscvau  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  4.0
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  call_command raises  | Triage Stage:
  exception  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 This is not a bug in Django but in your code. You cannot create project
 with the name of an existing Python module (as is explained in the error
 message). If you're having trouble understanding how Django works, see
 TicketClosingReasons/UseSupportChannels for ways to get help.

-- 
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/0107018264fbc038-282705c2-ae28-4bfe-9627-5f6aeb47be20-00%40eu-central-1.amazonses.com.

Re: [Django] #33889: Error in admin.site.register on pypy3.8 and Django 4.1+.

2022-08-03 Thread Django

#33889: Error in admin.site.register on pypy3.8 and Django 4.1+.
+--
 Reporter:  Hasan Ramezani  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  4.1
 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
+--

Comment (by Hasan Ramezani):

 Ah sorry for the duplication.
 Seems there is a related issue in
 [https://foss.heptapod.net/pypy/pypy/-/issues/3751 PyPy] and also you
 discussed about it in
 https://code.djangoproject.com/ticket/28358#comment:13

-- 
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/0107018264fa7eb9-1344dd5a-01b5-4ab3-9114-d0cc2af8f94d-00%40eu-central-1.amazonses.com.

Re: [Django] #33888: get_select2_language crashes when translations are deactivated

2022-08-03 Thread Django

#33888: get_select2_language crashes when translations are deactivated
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"0638b4e23dbabdcf7d7a6f2a2d5b95b980dece78" 0638b4e2]:
 {{{
 #!CommitTicketReference repository=""
 revision="0638b4e23dbabdcf7d7a6f2a2d5b95b980dece78"
 Fixed #33888 -- Fixed get_select2_language() crash with no language
 activated.

 Regression in 3079133c73f3b8b0e929673b06b62dce1f54be71.
 }}}

-- 
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/0107018264f4841d-6efc5b5d-33f4-45e9-b8a4-e4b2e96b8d44-00%40eu-central-1.amazonses.com.

Re: [Django] #33888: get_select2_language crashes when translations are deactivated

2022-08-03 Thread Django

#33888: get_select2_language crashes when translations are deactivated
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"2ae024c7447c5dd4172741f0f2cefad654bc1555" 2ae024c7]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ae024c7447c5dd4172741f0f2cefad654bc1555"
 [4.1.x] Fixed #33888 -- Fixed get_select2_language() crash with no
 language activated.

 Regression in 3079133c73f3b8b0e929673b06b62dce1f54be71.

 Backport of 0638b4e23dbabdcf7d7a6f2a2d5b95b980dece78 from main
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018264f4acdd-2600860d-7be6-4066-b119-e89c7e058693-00%40eu-central-1.amazonses.com.

Re: [Django] #33889: Error in admin.site.register on pypy3.8 and Django 4.1+. (was: Error in admin.site.register on pypy3.8 Django 4.1 and main)

2022-08-03 Thread Django

#33889: Error in admin.site.register on pypy3.8 and Django 4.1+.
+--
 Reporter:  Hasan Ramezani  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  4.1
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * version:  dev => 4.1
 * resolution:   => needsinfo


Comment:

 Thanks for this ticket, however this can be an issue in PyPy, not in
 Django itself. Can you debug this issue and provide details about why and
 where Django is at fault? I'd start from creating a bug report in PyPy and
 reopen this ticket if they indicate that Django is at fault.

-- 
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/0107018264f3025a-bc497696-1414-40e8-9b6b-2cc4cab46884-00%40eu-central-1.amazonses.com.

[Django] #33890: call_command('startproject', 'project_name', '.') raises CommandError 'project_name'

2022-08-03 Thread Django

#33890: call_command('startproject', 'project_name', '.') raises CommandError
'project_name'
-+-
   Reporter:  piscvau|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Core   |Version:  4.0
  (Management commands)  |   Keywords:  call_command raises
   Severity:  Normal |  exception
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 call_command ('startproject', 'project_name', '.') shoud create a project
 named 'project_name' in the current directory.

 to reproduce the bug :
 from django.core import management
 from pathlib import Path
 project_name = Path.cwd().stem
 management.call_command('startproject', project_name, '.')

 This raises the exception

 django.core.management.base.CommandError:   conflicts with
 the name of an existing Python module and cannot be used as a project
 name. Please try another name.

 This is because the initial directory of the python script is in
 sys.module.

-- 
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/0107018264defe6f-2e63c5cb-28d4-4013-ac42-03f3a59970b4-00%40eu-central-1.amazonses.com.

Re: [Django] #33888: get_select2_language crashes when translations are deactivated

2022-08-03 Thread Django

#33888: get_select2_language crashes when translations are deactivated
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018264d68460-bfd9ee9c-05c9-423d-a502-2127b047bd7a-00%40eu-central-1.amazonses.com.

Re: [Django] #33886: GeoIP module unnecessarily requires GDAL

2022-08-03 Thread Django

#33886: GeoIP module unnecessarily requires GDAL
-+-
 Reporter:  Aarni Koskela|Owner:  Aarni
 |  Koskela
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  4.1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"a3ce58ac4c9fee7c769d48ad1c4df45fa4c1775b" a3ce58ac]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3ce58ac4c9fee7c769d48ad1c4df45fa4c1775b"
 [4.1.x] Fixed #33886 -- Reallowed using GeoIP2() when GEOS is not
 installed.

 Regression in 31bef51d8ea5e3bf650de1495ae1f0566670b8f3.

 Backport of e7afb8a18061f664a5d20d409d423b77195e6060 from main
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070182648c7326-9531dedf-1109-47dc-9440-49e2bb74bf3e-00%40eu-central-1.amazonses.com.

Re: [Django] #33886: GeoIP module unnecessarily requires GDAL

2022-08-03 Thread Django

#33886: GeoIP module unnecessarily requires GDAL
-+-
 Reporter:  Aarni Koskela|Owner:  Aarni
 |  Koskela
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  4.1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"e7afb8a18061f664a5d20d409d423b77195e6060" e7afb8a1]:
 {{{
 #!CommitTicketReference repository=""
 revision="e7afb8a18061f664a5d20d409d423b77195e6060"
 Fixed #33886 -- Reallowed using GeoIP2() when GEOS is not installed.

 Regression in 31bef51d8ea5e3bf650de1495ae1f0566670b8f3.
 }}}

-- 
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/01070182648c52c3-64ffbe07-ae08-44db-a0f0-77ab8d377a0f-00%40eu-central-1.amazonses.com.

[Django] #33889: Error in admin.site.register on pypy3.8 Django 4.1 and main

2022-08-03 Thread Django

#33889: Error in admin.site.register on pypy3.8 Django 4.1 and main
--+
   Reporter:  Hasan Ramezani  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  contrib.admin   |Version:  dev
   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 tried to [https://github.com/jazzband/django-axes/pull/910 include
 Django 4.1 in django-axes]. then I noticed the CI fails on
 [https://github.com/jazzband/django-
 axes/runs/7653550763?check_suite_focus=true Django 4.1] and
 [https://github.com/jazzband/django-
 axes/runs/7653551446?check_suite_focus=true Django main] with the
 following error:


 {{{
File "/home/runner/work/django-axes/django-
 axes/.tox/pypy38-djmain/lib/pypy3.8/site-
 packages/django/contrib/auth/admin.py", line 29, in 
   class GroupAdmin(admin.ModelAdmin):
 File "/home/runner/work/django-axes/django-
 axes/.tox/pypy38-djmain/lib/pypy3.8/site-
 packages/django/contrib/admin/decorators.py", line 102, in
 _model_admin_wrapper
   raise ValueError("site must subclass AdminSite")
   ValueError: site must subclass AdminSite
 }}}

 It seems the error comes from
 
[https://github.com/django/django/blob/0dd29209091280ccf34e07c9468746c396b7778e/django/contrib/admin/decorators.py#L101
 register decorator]

 I've checked it and found this introduced after
 
https://github.com/django/django/commit/97d7990abde3fe4b525ae83958fd0b52d6a1d13f

 It seems the  `if not isinstance(admin_site, AdminSite):` returns `False`
 after this change.

-- 
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/01070182645fd772-61549fe3-a563-4e2b-a546-14e57c915e7e-00%40eu-central-1.amazonses.com.

Re: [Django] #33886: GeoIP module unnecessarily requires GDAL

2022-08-03 Thread Django

#33886: GeoIP module unnecessarily requires GDAL
-+-
 Reporter:  Aarni Koskela|Owner:  Aarni
 |  Koskela
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  4.1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018264369205-f0f9c4f3-2aaa-4f10-bb57-7a05f4eb30af-00%40eu-central-1.amazonses.com.

Re: [Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

#33887: test_fails_squash_migration_manual_porting fails in the assert
-+-
 Reporter:  Alberto Planas   |Owner:  Alberto
 |  Planas
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  4.1
 Severity:  Release blocker  |   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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"9e9bdf8dbd6e2354a2e23aa7e37d5b491338085e" 9e9bdf8]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e9bdf8dbd6e2354a2e23aa7e37d5b491338085e"
 [4.1.x] Fixed #33887 -- Fixed test_fails_squash_migration_manual_porting()
 on final tags.

 Regression in 7c318a8bdd66f8c5241864c9970dddb525d0ca4c.
 Backport of 4e13b40a764cfdae50416338c5d077e9d9a6d0f1 from main
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701826423b3f1-df65a6b4-092f-4184-a5dc-3ec004f50c82-00%40eu-central-1.amazonses.com.

Re: [Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

#33887: test_fails_squash_migration_manual_porting fails in the assert
-+-
 Reporter:  Alberto Planas   |Owner:  Alberto
 |  Planas
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  4.1
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"4e13b40a764cfdae50416338c5d077e9d9a6d0f1" 4e13b40a]:
 {{{
 #!CommitTicketReference repository=""
 revision="4e13b40a764cfdae50416338c5d077e9d9a6d0f1"
 Fixed #33887 -- Fixed test_fails_squash_migration_manual_porting() on
 final tags.

 Regression in 7c318a8bdd66f8c5241864c9970dddb525d0ca4c.
 }}}

-- 
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/010701826422df23-c201c87f-0b72-4e7c-aeb1-564f28bc1df5-00%40eu-central-1.amazonses.com.

Re: [Django] #33888: get_select2_language crashes when translations are deactivated

2022-08-03 Thread Django

#33888: get_select2_language crashes when translations are deactivated
-+
 Reporter:  Claude Paroz |Owner:  Claude Paroz
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.1
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * owner:  nobody => Claude Paroz
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report!

-- 
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/01070182641fed68-084ed812-bd01-4f02-992a-54cc3702a066-00%40eu-central-1.amazonses.com.

Re: [Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

#33887: test_fails_squash_migration_manual_porting fails in the assert
-+-
 Reporter:  Alberto Planas   |Owner:  Alberto
 |  Planas
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  4.1
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * owner:  nobody => Alberto Planas
 * status:  new => assigned
 * 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/0107018264130366-050d6d5b-82df-42c5-b68b-812e82512195-00%40eu-central-1.amazonses.com.

Re: [Django] #33886: GeoIP module unnecessarily requires GDAL

2022-08-03 Thread Django

#33886: GeoIP module unnecessarily requires GDAL
-+-
 Reporter:  Aarni Koskela|Owner:  Aarni Koskela
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  4.1
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * severity:  Normal => Release blocker


Comment:

 Regression in 31bef51d8ea5e3bf650de1495ae1f0566670b8f3.

-- 
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/010701826404cd58-94a681df-32b7-4c22-af01-8173b1feb4ce-00%40eu-central-1.amazonses.com.

Re: [Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

#33887: test_fails_squash_migration_manual_porting fails in the assert
-+
 Reporter:  Alberto Planas   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Alberto Planas):

 * 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/0107018263fdb18a-e6b278ae-1870-44b9-a5ea-f76b519ccc2e-00%40eu-central-1.amazonses.com.

Re: [Django] #33886: GeoIP module unnecessarily requires GDAL

2022-08-03 Thread Django

#33886: GeoIP module unnecessarily requires GDAL
---+-
 Reporter:  Aarni Koskela  |Owner:  Aarni Koskela
 Type:  Bug|   Status:  assigned
Component:  GIS|  Version:  4.1
 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 Claude Paroz):

 * 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/0107018263fcce08-d0f1fa70-f7ac-4299-b1d2-ddf47ef7985a-00%40eu-central-1.amazonses.com.

Re: [Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

#33887: test_fails_squash_migration_manual_porting fails in the assert
-+
 Reporter:  Alberto Planas   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.1
 Severity:  Release blocker  |   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 Alberto Planas):

 For dev: https://github.com/django/django/pull/15907
 For 4.1: https://github.com/django/django/pull/15908

-- 
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/0107018263fa705d-c1bcde7a-381a-4ff3-b6b9-1119e7cdadea-00%40eu-central-1.amazonses.com.

Re: [Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

* severity: Normal => Release blocker
* stage: Unreviewed => Accepted

Comment:

Yes... Running against the release version hit's this.

{{{
% git checkout 4.1
% ./runtests.py migrations
...
AssertionError: 'Migration will require manual porting but is already a
squashed migration.\nTransition to a normal migration first:
https://docs.djangoproject.com/en/dev/topics/migrations/#squashing-
migrations' not found in 'Migration will require manual porting but is
already a squashed migration.\nTransition to a normal migration first:
https://docs.djangoproject.com/en/4.1/topics/migrations/#squashing-
migrations'
}}}

Good spot. Thanks Alberto

--
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/0107018263f80003-dee1f5b0-ec23-4abd-b86c-2cd43aaf17ce-00%40eu-central-1.amazonses.com.

Re: [Django] #33888: get_select2_language crashes when translations are deactivated

2022-08-03 Thread Django

#33888: get_select2_language crashes when translations are deactivated
-+--
 Reporter:  Claude Paroz |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  4.1
 Severity:  Release blocker  |   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 Claude Paroz):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15909 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/0107018263f6c3cd-792095ef-32ed-48a6-a882-43910f659b68-00%40eu-central-1.amazonses.com.

[Django] #33888: get_select2_language crashes when translations are deactivated

2022-08-03 Thread Django

#33888: get_select2_language crashes when translations are deactivated
---+
   Reporter:  Claude Paroz |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  contrib.admin|Version:  4.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|
---+
 Regression in [3079133c73f3b8b0e929673b06b62dce1f54be71], #33514, patch
 follows.

-- 
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/0107018263f37ed4-de4e6c7b-b943-4d4c-a071-ddd66a27851a-00%40eu-central-1.amazonses.com.

[Django] #33887: test_fails_squash_migration_manual_porting fails in the assert

2022-08-03 Thread Django

#33887: test_fails_squash_migration_manual_porting fails in the assert
--+
   Reporter:  Alberto Planas  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |Version:  4.1
   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   |
--+
 Seems that the URL in the test is checking for the dev version.

 [  380s]
 ==
 [  380s] FAIL: test_fails_squash_migration_manual_porting
 (migrations.test_commands.OptimizeMigrationTests)
 [  380s]
 --
 [  380s] Traceback (most recent call last):
 [  380s]   File "/usr/lib/python3.8/unittest/case.py", line 60, in
 testPartExecutor
 [  380s] yield
 [  380s]   File "/usr/lib/python3.8/unittest/case.py", line 676, in run
 [  380s] self._callTestMethod(testMethod)
 [  380s]   File "/usr/lib/python3.8/unittest/case.py", line 633, in
 _callTestMethod
 [  380s] method()
 [  380s]   File
 "/home/abuild/rpmbuild/BUILD/Django-4.1/tests/migrations/test_commands.py",
 line 3015, in test_fails_squash_migration_manual_porting
 [  380s] call_command("optimizemigration", "migrations", "0004",
 stdout=out)
 [  380s]   File "/usr/lib/python3.8/contextlib.py", line 131, in __exit__
 [  380s] self.gen.throw(type, value, traceback)
 [  380s]   File
 "/home/abuild/rpmbuild/BUILD/Django-4.1/django/test/testcases.py", line
 879, in _assert_raises_or_warns_cm
 [  380s] self.assertIn(expected_message, str(getattr(cm, cm_attr)))
 [  380s]   File "/usr/lib/python3.8/unittest/case.py", line 1179, in
 assertIn
 [  380s] self.fail(self._formatMessage(msg, standardMsg))
 [  380s]   File "/usr/lib/python3.8/unittest/case.py", line 753, in fail
 [  380s] raise self.failureException(msg)
 [  380s] AssertionError: 'Migration will require manual porting but is
 already a squashed migration.\nTransition to a normal migration first:
 https://docs.djangoproject.com/en/dev/topics/migrations/#squashing-
 migrations' not found in 'Migration will require manual porting but is
 already a squashed migration.\nTransition to a normal migration first:
 https://docs.djangoproject.com/en/4.1/topics/migrations/#squashing-
 migrations'
 [  380s]

-- 
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/0107018263f06308-4798a7ec-6091-41c2-bff5-b9085845aae0-00%40eu-central-1.amazonses.com.

[Django] #33886: GeoIP module unnecessarily requires GDAL

2022-08-03 Thread Django

#33886: GeoIP module unnecessarily requires GDAL
-+---
   Reporter:  Aarni Koskela  |  Owner:  Aarni Koskela
   Type:  Bug| Status:  assigned
  Component:  GIS|Version:  4.1
   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  |
-+---
 The commit
 
https://github.com/django/django/commit/31bef51d8ea5e3bf650de1495ae1f0566670b8f3
 (in versions 4.1a1 forward) moved the import of
 `django.contrib.gis.geos.Point` from the `def geos()` function to top-
 level, with the unfortunate side-effect that importing the `GeoIP` module
 now requires working GDAL libraries.

 The GeoIP module should be usable without GDAL; naturally, returning a
 GDAL geometry would require GDAL.

 My suggested fix would be to revert the above commit; a late import should
 be fine here.

-- 
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/0107018263ed013a-0b7156c7-b4b9-4d0d-8e53-e8e6a3631409-00%40eu-central-1.amazonses.com.

Re: [Django] #29186: "django.request" logging breaks "logging.handlers.SocketHandler"

2022-08-03 Thread Django

#29186: "django.request" logging breaks "logging.handlers.SocketHandler"
--+-
 Reporter:  direx |Owner:  Anvesh Mishra
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  2.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 Anvesh Mishra):

 * owner:  (none) => Anvesh Mishra
 * status:  new => assigned


Comment:

 Replying to [comment:11 Mariusz Felisiak]:
 > Stripping non-picklable attributes may be an acceptable solution, see
 similar change for `HttpResponse`
 d7f5bfd241666c0a76e90208da1e9ef81aec44db.

 Yeah seems like a valid solution gonna work on it.

-- 
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/010701826343284f-51c1a730-9caf-4174-9b7c-a28cee61621d-00%40eu-central-1.amazonses.com.

Re: [Django] #33872: Deprecate CICharField, CIEmailField, CITextField.

2022-08-03 Thread Django

#33872: Deprecate CICharField, CIEmailField, CITextField.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  contrib.postgres |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"cb791a2540c289390b68a3ea9c6a79476890bab2" cb791a25]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb791a2540c289390b68a3ea9c6a79476890bab2"
 Fixed #33872 -- Deprecated
 django.contrib.postgres.fields.CIText/CICharField/CIEmailField/CITextField.
 }}}

-- 
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/010701826316da6b-8ff44c99-2fab-4985-8d9c-5ae97d1e138d-00%40eu-central-1.amazonses.com.

Re: [Django] #28975: Skip automatic creation of postgis extension if it already exists

2022-08-03 Thread Django

#28975: Skip automatic creation of postgis extension if it already exists
-+-
 Reporter:  sphrak   |Owner:  amureki
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  GIS  |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  create extension,| Triage Stage:  Accepted
  postgis, psycopg2, postgresql  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  sphrak => amureki
 * status:  new => assigned


Comment:

 Replying to [comment:12 amureki]:
 > As I am also affected by this, I would be happy to introduce a fix for
 that, which would be following Mariusz's suggestion.

 Thanks, feel-free to submit a patch.

-- 
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/0107018262a0c311-0912e405-8d23-48bd-8f32-c1808da9706d-00%40eu-central-1.amazonses.com.

39 matches

Mail list logo