In one week (2023-03-02), or slightly later, I plan to update the python-shapely package from 1.8.5.post1 to 2.0.1 in Rawhide/F39 by merging the linked PR[1].

There are incompatible changes[2], but after some patching and some waiting for upstream releases, all dependent packages now build successfully in COPR[3], and I believe all upper-bounds on the Shapely version have been removed or loosened. No action by dependent package maintainers should be required; however, I am happy to help if you do encounter any problems.

The License field changes from BSD-3-Clause to (BSD-3-Clause AND Unlicense AND MIT). The Unlicense term comes from more careful consideration of the versioneer-generated file shapely/_version.py, and the MIT term comes from a new bundled source file that is a “copylib” from https://github.com/attractivechaos/klib.

I have no plans to build Shapely 2 for Fedora 38/Branched.

[1] https://src.fedoraproject.org/rpms/python-shapely/pull-request/9

[2] https://shapely.readthedocs.io/en/stable/migration.html

[3] https://copr.fedorainfracloud.org/coprs/music/shapely/packages/
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to