Re: [Django] #34204: Django cannot load when Python is compiled with --without-doc-strings enabled

[Django]

#34204: Django cannot load when Python is compiled with --without-doc-strings
enabled
---+--
 Reporter:  Jon Janzen |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  4.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by Jon Janzen:

Old description:

> I'm not sure that this is even a supported configuration for Django, but
> CPython's `./configure` script offers an option called
> [https://docs.python.org/3/using/configure.html#cmdoption-without-doc-
> strings --without-doc-strings] which improves memory utilization
> slightly.
>
> Quoting the relevant portion from CPython docs:
>
> > --without-doc-strings
> > Disable static documentation strings to reduce the memory footprint
> (enabled by default). Documentation strings defined in Python are not
> affected.
>
> I have an use-case where I need to deploy a Django service on a device
> with low available memory. I'd like to disable built-in doc strings as
> part of an overall strategy to reduce memory but compiling CPython with
> that option and running the django service crashes:
>

> {{{
>   File ".../asgi.py", line 3, in 
> from django.core.asgi import get_asgi_application
>   File ".../lib/python3.11/site-packages/django/core/asgi.py", line 2, in
> 
> from django.core.handlers.asgi import ASGIHandler
>   File ".../lib/python3.11/site-packages/django/core/handlers/asgi.py",
> line 11, in 
> from django.core.handlers import base
>   File ".../lib/python3.11/site-packages/django/core/handlers/base.py",
> line 11, in 
> from django.urls import get_resolver, set_urlconf
>   File ".../lib/python3.11/site-packages/django/urls/__init__.py", line
> 1, in 
> from .base import (
>   File ".../lib/python3.11/site-packages/django/urls/base.py", line 8, in
> 
> from .exceptions import NoReverseMatch, Resolver404
>   File ".../lib/python3.11/site-packages/django/urls/exceptions.py", line
> 1, in 
> from django.http import Http404
>   File ".../lib/python3.11/site-packages/django/http/__init__.py", line
> 2, in 
> from django.http.request import (
>   File ".../lib/python3.11/site-packages/django/http/request.py", line 8,
> in 
> from django.core import signing
>   File ".../lib/python3.11/site-packages/django/core/signing.py", line
> 43, in 
> from django.utils.crypto import constant_time_compare, salted_hmac
>   File ".../lib/python3.11/site-packages/django/utils/crypto.py", line
> 85, in 
> if func_supports_parameter(hashlib.md5, 'usedforsecurity'):
>^^^
>   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
> 74, in func_supports_parameter
> return any(param.name == name for param in
> _get_callable_parameters(func))
> ^^
>   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
> 16, in _get_callable_parameters
> return _get_func_parameters(func, remove_first=is_method)
>^^
>   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
> 7, in _get_func_parameters
> parameters = tuple(inspect.signature(func).parameters.values())
>^^^
>   File ".../cpython/Lib/inspect.py", line 3270, in signature
> return Signature.from_callable(obj, follow_wrapped=follow_wrapped,
>^^^
>   File ".../cpython/Lib/inspect.py", line 3018, in from_callable
> return _signature_from_callable(obj, sigcls=cls,
>^
>   File ".../cpython/Lib/inspect.py", line 2510, in
> _signature_from_callable
> return _signature_from_builtin(sigcls, obj,
>
>   File ".../cpython/Lib/inspect.py", line 2317, in
> _signature_from_builtin
> raise ValueError("no signature found for builtin {!r}".format(func))
> ValueError: no signature found for builtin  openssl_md5>
> }}}
>
> (irrelevant information lightly censored)
>
> An easy way to repro is to follow this script:
> {{{
> git clone https://github.com/python/cpython.git
> cd cpython
> git checkout 3.11 # or whatever version you have that already has django
> installed
> ./configure --without-doc-strings
> make -j
> ./python
> >>> import django.utils.crypto
> *crash*
> }}}
>
> Looking through this stack trace the problem looks to be
> [https://github.com/django

Re: [Django] #34204: Django cannot load when Python is compiled with --without-doc-strings enabled

[Django]

#34204: Django cannot load when Python is compiled with --without-doc-strings
enabled
---+--
 Reporter:  Jon Janzen |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  4.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by Jon Janzen:

Old description:

> I'm not sure that this is even a supported configuration for Django, but
> CPython's `./configure` script offers an option called
> [https://docs.python.org/3/using/configure.html#cmdoption-without-doc-
> strings --without-doc-strings] which improves memory utilization
> slightly.
>
> Quoting the relevant portion from CPython docs:
>
> > --without-doc-strings
> > Disable static documentation strings to reduce the memory footprint
> (enabled by default). Documentation strings defined in Python are not
> affected.
>
> I have an use-case where I need to deploy a Django service on a device
> with low available memory. I'd like to disable built-in doc strings as
> part of an overall strategy to reduce memory but compiling CPython with
> that option and running the django service crashes:
>

> {{{
>   File ".../asgi.py", line 3, in 
> from django.core.asgi import get_asgi_application
>   File ".../lib/python3.11/site-packages/django/core/asgi.py", line 2, in
> 
> from django.core.handlers.asgi import ASGIHandler
>   File ".../lib/python3.11/site-packages/django/core/handlers/asgi.py",
> line 11, in 
> from django.core.handlers import base
>   File ".../lib/python3.11/site-packages/django/core/handlers/base.py",
> line 11, in 
> from django.urls import get_resolver, set_urlconf
>   File ".../lib/python3.11/site-packages/django/urls/__init__.py", line
> 1, in 
> from .base import (
>   File ".../lib/python3.11/site-packages/django/urls/base.py", line 8, in
> 
> from .exceptions import NoReverseMatch, Resolver404
>   File ".../lib/python3.11/site-packages/django/urls/exceptions.py", line
> 1, in 
> from django.http import Http404
>   File ".../lib/python3.11/site-packages/django/http/__init__.py", line
> 2, in 
> from django.http.request import (
>   File ".../lib/python3.11/site-packages/django/http/request.py", line 8,
> in 
> from django.core import signing
>   File ".../lib/python3.11/site-packages/django/core/signing.py", line
> 43, in 
> from django.utils.crypto import constant_time_compare, salted_hmac
>   File ".../lib/python3.11/site-packages/django/utils/crypto.py", line
> 85, in 
> if func_supports_parameter(hashlib.md5, 'usedforsecurity'):
>^^^
>   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
> 74, in func_supports_parameter
> return any(param.name == name for param in
> _get_callable_parameters(func))
> ^^
>   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
> 16, in _get_callable_parameters
> return _get_func_parameters(func, remove_first=is_method)
>^^
>   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
> 7, in _get_func_parameters
> parameters = tuple(inspect.signature(func).parameters.values())
>^^^
>   File ".../cpython/Lib/inspect.py", line 3270, in signature
> return Signature.from_callable(obj, follow_wrapped=follow_wrapped,
>^^^
>   File ".../cpython/Lib/inspect.py", line 3018, in from_callable
> return _signature_from_callable(obj, sigcls=cls,
>^
>   File ".../cpython/Lib/inspect.py", line 2510, in
> _signature_from_callable
> return _signature_from_builtin(sigcls, obj,
>
>   File ".../cpython/Lib/inspect.py", line 2317, in
> _signature_from_builtin
> raise ValueError("no signature found for builtin {!r}".format(func))
> ValueError: no signature found for builtin  openssl_md5>
> }}}
>
> (irrelevant information lightly censored)
>
> Looking through this stack trace the problem looks to be
> [https://github.com/django/django/blob/d10c7bfe56f025ccc690721c9f13e7029b777b9c/django/utils/crypto.py#L80-L92
> some code] that executes at module import to determine whether or not md5
> supports the `usedforsecurity` parameter.
>
> If this ticket is accepted I'm happy to put up a PR to fix this, I've
> included my proposed solution on

[Django] #34204: Django cannot load when Python is compiled with --without-doc-strings enabled

[Django]

#34204: Django cannot load when Python is compiled with --without-doc-strings
enabled
-+
   Reporter:  Jon Janzen |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |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  |
-+
 I'm not sure that this is even a supported configuration for Django, but
 CPython's `./configure` script offers an option called
 [https://docs.python.org/3/using/configure.html#cmdoption-without-doc-
 strings --without-doc-strings] which improves memory utilization slightly.

 Quoting the relevant portion from CPython docs:

 > --without-doc-strings
 > Disable static documentation strings to reduce the memory footprint
 (enabled by default). Documentation strings defined in Python are not
 affected.

 I have an use-case where I need to deploy a Django service on a device
 with low available memory. I'd like to disable built-in doc strings as
 part of an overall strategy to reduce memory but compiling CPython with
 that option and running the django service crashes:


 {{{
   File ".../asgi.py", line 3, in 
 from django.core.asgi import get_asgi_application
   File ".../lib/python3.11/site-packages/django/core/asgi.py", line 2, in
 
 from django.core.handlers.asgi import ASGIHandler
   File ".../lib/python3.11/site-packages/django/core/handlers/asgi.py",
 line 11, in 
 from django.core.handlers import base
   File ".../lib/python3.11/site-packages/django/core/handlers/base.py",
 line 11, in 
 from django.urls import get_resolver, set_urlconf
   File ".../lib/python3.11/site-packages/django/urls/__init__.py", line 1,
 in 
 from .base import (
   File ".../lib/python3.11/site-packages/django/urls/base.py", line 8, in
 
 from .exceptions import NoReverseMatch, Resolver404
   File ".../lib/python3.11/site-packages/django/urls/exceptions.py", line
 1, in 
 from django.http import Http404
   File ".../lib/python3.11/site-packages/django/http/__init__.py", line 2,
 in 
 from django.http.request import (
   File ".../lib/python3.11/site-packages/django/http/request.py", line 8,
 in 
 from django.core import signing
   File ".../lib/python3.11/site-packages/django/core/signing.py", line 43,
 in 
 from django.utils.crypto import constant_time_compare, salted_hmac
   File ".../lib/python3.11/site-packages/django/utils/crypto.py", line 85,
 in 
 if func_supports_parameter(hashlib.md5, 'usedforsecurity'):
^^^
   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
 74, in func_supports_parameter
 return any(param.name == name for param in
 _get_callable_parameters(func))
 ^^
   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line
 16, in _get_callable_parameters
 return _get_func_parameters(func, remove_first=is_method)
^^
   File ".../lib/python3.11/site-packages/django/utils/inspect.py", line 7,
 in _get_func_parameters
 parameters = tuple(inspect.signature(func).parameters.values())
^^^
   File ".../cpython/Lib/inspect.py", line 3270, in signature
 return Signature.from_callable(obj, follow_wrapped=follow_wrapped,
^^^
   File ".../cpython/Lib/inspect.py", line 3018, in from_callable
 return _signature_from_callable(obj, sigcls=cls,
^
   File ".../cpython/Lib/inspect.py", line 2510, in
 _signature_from_callable
 return _signature_from_builtin(sigcls, obj,

   File ".../cpython/Lib/inspect.py", line 2317, in _signature_from_builtin
 raise ValueError("no signature found for builtin {!r}".format(func))
 ValueError: no signature found for builtin 
 }}}

 (irrelevant information lightly censored)

 Looking through this stack trace the problem looks to be
 
[https://github.com/django/django/blob/d10c7bfe56f025ccc690721c9f13e7029b777b9c/django/utils/crypto.py#L80-L92
 some code] that executes at module import to determine whether or not md5
 supports the `usedforsecurity` parameter.

 If this ticket is accepted I'm happy to put up a PR to fix this, I've
 included my proposed solution on this ticket to save a roundtrip in
 discussion:

 {{{
 diff --git a/django/utils/inspect.py b/django/utils/inspect.py
 index 28418f7312..d8622a22df 100644
 --- a/django/utils/inspect.py
 +++ b/

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

[Django]

#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
-+
 Reporter:  Chris Woytowitz  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  dev
 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
-+

Comment (by Mikko Ahonen):

 Run into this as well, using django 3.1 and Postgres. Similar case as for
 scholtalbers.

 I wanted to switch to using a library that wanted to add field to model
 which was conflicting with the existing name, used for similar purpose
 (parent).

 I renamed the field (to old_parent), ran migration, created migration,
 added the library (which added the parent field), created migration, run
 migration.

 Locally migrations worked because I was using SQLite, but when installing
 on staging it failed because of conflicting index name.

-- 
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/01070184f4447718-6f4b218c-873f-41b2-81c5-fe962b5dd944-00%40eu-central-1.amazonses.com.

Re: [Django] #33199: Deprecate passing positional arguments to Signer.

[Django]

#33199: Deprecate passing positional arguments to Signer.
+-
 Reporter:  Daniel Samuels  |Owner:  Abhinav Yadav
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  dev
 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 Abhinav Yadav):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * needs_docs:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184f3b11e03-52475865-b72d-426e-936e-2a8453db9349-00%40eu-central-1.amazonses.com.

Re: [Django] #33945: get_previous_in_order and get_next_in_order return incorrect data when objects is stored in non-default database

[Django]

#33945: get_previous_in_order and get_next_in_order return incorrect data when
objects is stored in non-default database
-+-
 Reporter:  François Granade |Owner:  Aryan
 |  Amish
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aryan Amish):

 * owner:  Wael Ramadan => Aryan Amish
 * 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/01070184f359cd82-55bed343-e0ea-4bef-a53e-f94ae15c8beb-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 > I still don't see any drawbacks for Django to drop support for Psycopg2
 2.8

 Maybe not for Django itself, but for our users that would be forced to
 bump a `psycopg2` version. Closing as "wontfix". Please feel-free, to
 start a discussion on DevelopersMailingList if you don't agree, 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/01070184f33c7d09-644783ad-0e41-419f-8c53-ade2247202e3-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Debian stable still has `2.8.6` currently, and works fine with Python 3.9.
 Dropping it for 4.2 looks too quick in my opinion.

-- 
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/01070184f2c46765-9981232b-cf84-4f14-b614-be8de2e9fbbb-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paolo Melchiorre):

 Replying to [comment:6 Mariusz Felisiak]:
 >> What do you think are the cons of removing `Psycopg2 2.8` support from
 `Django 4.2` ?
 > Normally we don't bump minimum supported versions of 3rd party packages
 when it's not necessary...
 > I'd ask what are the pros for Django itself?

 The advantage of removing support for Psycopg2 2.8 for Django is to avoid
 opening issues related to a version of Psycopg2 that hasn't received new
 updates for more than 2 years and still supports very old versions of
 Python.

 > > Since `Psycopg2 2.8` is **EOL**
 > What is the source of this information?
 > There are commits in the
 [https://github.com/psycopg/psycopg2/commits/maint_2_8 maint_2_8] branch
 after the 2.8.6 release, so as far as I'm aware, we cannot assume that
 `2.8.7` will not be released in the future.

 In the [https://pypi.org/project/psycopg2/#history history of Psycopg2] I
 have never seen a bugfix release after the release of a subsequent major
 release. Psycopg2 has no official EOL statement, but after more than 2
 years since the last release and 3 major versions released I find a new
 version highly unlikely.

 I still don't see any drawbacks for Django to remove support for Psycopg2
 2.8 , and I think it could be a gradual way to deprecate Psycopg2 2.9
 before Django 5.0, but if you think otherwise, please close this issue,
 because I understand that the priority right now is to complete support
 for Psycop 3.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/01070184f280e0fc-944a7dd4-dc91-4c28-b0a4-dab9b68185bf-00%40eu-central-1.amazonses.com.

Re: [Django] #32798: StreamingHttpResponse raises SynchronousOnlyOperation in ASGI server

[Django]

#32798: StreamingHttpResponse raises SynchronousOnlyOperation in ASGI server
+-
 Reporter:  Ralph Broenink  |Owner:  Michael Brown
 Type:  Bug |   Status:  closed
Component:  HTTP handling   |  Version:  3.2
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  ASGI, async | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Carles Pina Estany):

 * cc: Carles Pina Estany (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184f2594c2a-8844c6c6-d342-4df6-8157-718ba3b899d6-00%40eu-central-1.amazonses.com.

Re: [Django] #33735: Add asynchronous responses for use with an ASGI server

[Django]

#33735: Add asynchronous responses for use with an ASGI server
+
 Reporter:  florianvazelle  |Owner:  (none)
 Type:  New feature |   Status:  new
Component:  HTTP handling   |  Version:  4.0
 Severity:  Normal  |   Resolution:
 Keywords:  ASGI async  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Carles Pina Estany):

 * cc: Carles Pina Estany (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184f257cbde-25c2ae89-38d4-4240-ba4a-80f47dcf92a1-00%40eu-central-1.amazonses.com.

Re: [Django] #16180: IGNORED_PARAMS customization

[Django]

#16180: IGNORED_PARAMS customization
-+
 Reporter:  Manuel Saelices  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  dev
 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
-+

Comment (by Vaskevich Aleksander):

 Is there any movement on this ticket? May I offer my 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/01070184f257aee0-ddb8568c-18c1-4665-a87a-6d17e09c05bb-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 > What do you think are the cons of removing `Psycopg2 2.8` support from
 `Django 4.2` ?

 Normally we don't bump minimum supported versions of 3rd party packages
 when it's not necessary (e.g. they're not compatible with the current
 Django version, or they require some workarounds in Django). I'd ask what
 are the pros for Django itself?

 > Since `Psycopg2 2.8` is **EOL**

 What is the source of this information? There are commits in the
 [https://github.com/psycopg/psycopg2/commits/maint_2_8 maint_2_8] branch
 after the 2.8.6 release, so as far as I'm aware, we cannot assume that
 `2.8.7` will not be released in the future.

-- 
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/01070184f222580e-b91eba1d-b334-40bf-8db5-c21aff5b800b-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Tushar
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ux,   | Triage Stage:  Accepted
  ui, admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Carlton Gibson):

 Thanks Tushar, this looks interesting. Let's see what folks say.

 I adjusted the PR title to start `Fixed #33620 -- ...` which allows Trac
 to pickup that it links to this issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184f200d4b7-7563e774-9bcd-4984-b4d0-83b8231c6051-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Tushar
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ux,   | Triage Stage:  Accepted
  ui, admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tushar):

 I have made a draft PR to get some comments and better clarity on what
 could be done. https://github.com/django/django/pull/16372. Linking it
 here manually as issue tracker is not picking it up (I did something wrong
 probably)

-- 
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/01070184f1fd2035-653473b1-8251-4134-9737-ae9f911e1ccd-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paolo Melchiorre):

 I agree to deprecate `Psycopg2` in `Django 5.0`, but `Django 4.2 LTS` will
 be supported until **April 2026** and I think there will be many `Django
 4.2` users who will continue to use `Psycopg2`.

 Since `Psycopg2 2.8` is **EOL** , hasn't been updated for **over 2 years**
 and barely supports `Python 3.8`, I only see benefits in removing its
 support from `Django 4.2` and forcing `Psycopg2` users to at least use the
 latest 2.9 series which dropped support for `Python 2.7` / `Python 3` <
 3.6 and added support for `Python 3` from 3.6 to 3.11.

 What do you think are the cons of removing `Psycopg2 2.8` support from
 `Django 4.2` ?

-- 
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/01070184f1f2f52b-88b80fe4-8a04-4151-b22b-4723eecdcb98-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Carlton Gibson, Florian Apolloner (added)


Comment:

 I don't see much value in bumping the minimum supported version of
 `psycopg2` to `2.9.5`. I'd rather completely deprecate support for
 `psycopg2` in Django 5.0 (and remove in Django 6.0) if we fix #33308 in
 Django 4.2.

-- 
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/01070184f198692d-cfcfc75e-2659-49fe-adcb-d5104c82628a-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 TBH, I don't see a reason to drop support for `psycopg2` `2.8.4` as it
 supports Python 3.8 and brings us no difference in maintenance.

-- 
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/01070184f18bce01-06caa825-1e5c-4d89-b345-020b6a4a63ea-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paolo Melchiorre):

 I submitted the [https://github.com/django/django/pull/16370 PR 16370]
 with Psycopg2 2.9.5 as minimum version.

-- 
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/01070184f18a5d53-0cf1846b-c4e4-4ecd-9521-7af541771023-00%40eu-central-1.amazonses.com.

Re: [Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql, psycopg  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Paolo Melchiorre:

Old description:

> ''Psycopg2'' **2.8.6** was released ''over 2 years ago'' and is the
> latest release of the **2.8** series which is now **EOL**.
> The 2.8 series supports very old versions of Python 3 and still has
> support for **Python 2.7**.
>
> ''Django'' **4.2** (which supports ''Python'' from **3.8** to **3.11**)
> may set ''Psycopg2'' **2.9.5** (with Python 3.11 support) as the minimum
> version it supports, or at least ''Psycopg2'' **2.9.2** (with preliminary
> Python 3.11 support).

New description:

 ''Psycopg2'' **2.8.6** was released ''over 2 years ago'' and is the latest
 release of the **2.8** series which is now **EOL**.
 The 2.8 series supports very old versions of Python 3 and still has
 support for **Python 2.7**.

 ''Django'' **4.2** (which supports ''Python'' from **3.8** to **3.11**)
 may set ''Psycopg2'' **2.9.5** (with Python 3.11 support) as the minimum
 version it supports, or at least ''Psycopg2'' **2.9.2** (with preliminary
 Python 3.11 support).

 In any case, the important thing would be to switch to using the 2.9
 series of Psycopg2 which drops support for Python 2.7 and older versions
 of Python 3.

--

-- 
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/01070184f1893191-2434cde0-7d57-4ea3-bf04-4fe774a7aa8e-00%40eu-central-1.amazonses.com.

[Django] #34203: Drop support for psycopg2 2.8

[Django]

#34203: Drop support for psycopg2 2.8
-+-
   Reporter:  Paolo  |  Owner:  nobody
  Melchiorre |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  dev
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  postgresql, psycopg
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 ''Psycopg2'' **2.8.6** was released ''over 2 years ago'' and is the latest
 release of the **2.8** series which is now **EOL**.
 The 2.8 series supports very old versions of Python 3 and still has
 support for **Python 2.7**.

 ''Django'' **4.2** (which supports ''Python'' from **3.8** to **3.11**)
 may set ''Psycopg2'' **2.9.5** (with Python 3.11 support) as the minimum
 version it supports, or at least ''Psycopg2'' **2.9.2** (with preliminary
 Python 3.11 support).

-- 
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/01070184f180fa28-8af09cfd-658b-4fef-a976-67db0d2904fd-00%40eu-central-1.amazonses.com.