RFC: Proposing incompatible upgrade of python-asgiref from 3.4.1 to 3.7.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

Django 4.2 (the only currently supported LTS series) requires asgiref >=
3.6, so I would like to propose updating python-asgiref in EPEL 9 at
least to 3.6.0, but ideally to 3.8.1 for future proofing.

The affected packages (maintainers bcc:ed) are python-django3 (which I
maintain, and has just reached EOL) and python-opentelemetry

❯ fedrq whatrequires 'python3dist(asgiref)' -b epel9
python-django3-3.2.20-3.el9.src                                       
python-opentelemetry-1.12.0-8.el9.src

❯ fedrq pkgs --src -P python-django3 -F requires -b epel9 | grep asgi
python3dist(asgiref) >= 3.3.2
(python3dist(asgiref) < 4~~ with python3dist(asgiref) >= 3.3.2)

❯ fedrq pkgs --src -P python-opentelemetry -F requires -b epel9 | grep asgi
(python3dist(asgiref) >= 3 with python3dist(asgiref) < 4)

The relevant breaking changes seem to be (starting from the safest
option of upgrading only to 3.6.0)

https://github.com/django/asgiref/blob/main/CHANGELOG.txt

* 3.6.0
  Support for the ``ASGI_THREADS`` environment variable, used by
  ``SyncToAsync``, is removed. In general, a running event-loop is not
  available to `asgiref` at import time, and so the default thread pool
  executor cannot be configured. Protocol servers, or applications, should set
  the default executor as required when configuring the event loop at
  application startup.

I don't see anything that could be breaking in 3.7.x and 3.8.x, but PTAL

Note that Fedora's opentelemetry 1.24 has not bumped its asgiref
requirement, so we are probably OK leaving it as is

❯ fedrq pkgs --src -P python-opentelemetry -F requires | grep asgi
python3dist(asgiref)
(python3dist(asgiref) >= 3 with python3dist(asgiref) < 4)

❯ fedrq pkgs --src python-opentelemetry 
python-opentelemetry-1.24.0-3.fc41.src

Best regards,

-- 
 _o) Michel Lind (né Salim)
_( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2

Attachment: signature.asc
Description: PGP signature

--
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux