Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15488
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.maint.python |
| Subject | Bug#1058265: Status of sqlalchemy |
| Date | 2024-02-22 10:10 +0100 |
| Message-ID | <Iadfz-bPa4-1@gated-at.bofh.it> (permalink) |
| References | <HK6te-d1mn-67@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi,
we have quite some Python3.12 related bugs caused by sqlalchemy which
seem to be fixed in experimental (which is lagging behind upstream
2.0.27 as well as version 1.4 in unstable where upstream just released
1.4.51).
It seems the issue that leads to bug #1058265
> File "/usr/lib/python3/dist-packages/sqlalchemy/sql/sqltypes.py", line 2061, in Interval
> epoch = dt.datetime.utcfromtimestamp(0)
is not fixed in 1.4.51 so sticking to 1.4 maintenance releases will not
simply solve our Python3.12 issues if we do not fix these ourselves with
patches. So the question remains for Thomas wo wrote in bug #1058895:
> It'd be nice if we could have the patch in Unstable with this series 1.4.x
> before uploading 2.x, so that I have a chance to fix all Python 3.12 bugs and
> not mix SQLA 2.x and Py 3.12 problems.
Do yuo really want to fix 1.4.x (maybe x=51) first or do we want to
switch to 2.0.27 and fix remaining problems with this latest version? I
have no resources to run all the tests but I stumbled upon this question
when trying to do some general Python3.12 bug hunting.
Kind regards
Andreas.
--
http://fam-tille.de
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1058265: Status of sqlalchemy Andreas Tille <andreas@an3as.eu> - 2024-02-22 10:10 +0100
Re: Status of sqlalchemy Martin <debacle@debian.org> - 2024-04-14 23:30 +0200
Re: Status of sqlalchemy Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-04-15 11:40 +0200
Status of pymodbus (was: Status of sqlalchemy) Martin <debacle@debian.org> - 2024-04-22 08:10 +0200
Re: Status of pymodbus (was: Status of sqlalchemy) Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-04-22 09:50 +0200
Re: Status of pymodbus (was: Status of sqlalchemy) Martin <debacle@debian.org> - 2024-04-22 10:00 +0200
Re: Status of pymodbus (was: Status of sqlalchemy) Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-04-22 10:10 +0200
Re: Status of pymodbus (was: Status of sqlalchemy) Martin <debacle@debian.org> - 2024-04-23 00:10 +0200
Re: Status of pymodbus (was: Status of sqlalchemy) Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-05-13 08:30 +0200
Re: Status of pymodbus (was: Status of sqlalchemy) Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-05-27 22:50 +0200
Re: Status of sqlalchemy Martin <debacle@debian.org> - 2024-04-15 12:10 +0200
Re: Status of sqlalchemy Piotr Ożarowski <piotr@debian.org> - 2024-04-15 15:20 +0200
Re: Status of sqlalchemy Martin <debacle@debian.org> - 2024-04-15 17:20 +0200
Re: Status of sqlalchemy Martin <debacle@debian.org> - 2024-05-21 22:10 +0200
Re: Status of sqlalchemy Carsten Schoenert <c.schoenert@t-online.de> - 2024-04-15 18:10 +0200
csiph-web