Bug 2203139

Summary:	New release of sqlalchemy with many fixes and new orm
Product:	[Fedora] Fedora	Reporter:	justin.lamp96
Component:	python-sqlalchemy	Assignee:	Nils Philippsen <nphilipp>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	38	CC:	brian, infra-sig, mbayer, nphilipp, orion
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-16 14:45:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description justin.lamp96 2023-05-11 10:05:25 UTC

Description of problem:

I need the new sqlalchemy version 2 package that brings many bug fixes and a new style ORM.

Version-Release number of selected component (if applicable):


Actual results:

Version      : 1.4.46

Expected results:

Version      : 2.0.13

Additional info:

Please consider upgrading to it! Thank you!

Comment 1 Orion Poplawski 2023-05-11 23:23:38 UTC

Fixing component (python3-sqlalchemy is EPEL-only)

Comment 2 Brian J. Murrell 2023-11-12 20:46:14 UTC

Any word or update on this issue?

Comment 3 Nils Philippsen 2023-11-16 14:45:21 UTC

(In reply to Brian J. Murrell from comment #2)
> Any word or update on this issue?

Yes: SQLAlchemy version 2 is incompatible with other software using the 1.x APIs. Version 1.4 introduced the new API so it’s possible to write software that works with both. This unfortunately makes it impossible to introduce this new version in stable Fedora releases, too much would break.

For Fedora 40, I intend to upgrade python-sqlalchemy to version 2.x and have a python-sqlalchemy1.4 compatibility package for software that needs the old stack. Among the dependents, we need to find out which is which, so the affected packages depend on the right package. This Fedora Change is tracked here: https://fedoraproject.org/wiki/Changes/SQLAlchemy_2

*** This bug has been marked as a duplicate of bug 2134559 ***

Comment 4 Michael Bayer 2023-11-16 15:08:38 UTC

> For Fedora 40, I intend to upgrade python-sqlalchemy to version 2.x and have a python-sqlalchemy1.4 compatibility package for software that needs the old stack.

I think that's a great idea.  I would assume the two packages would be mutually exclusive since they use the same import space (this was an intentional, non-trivial decision on our part).