Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15761
| Path | csiph.com!weretis.net!feeder6.news.weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | Martin <debacle@debian.org> |
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Status of sqlalchemy |
| Date | Sun, 14 Apr 2024 23:30:01 +0200 |
| Message-ID | <ItfAd-6iQb-3@gated-at.bofh.it> (permalink) |
| References | <Iadfz-bPa4-1@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Sun Apr 14 21:28:05 2024 |
| Old-Return-Path | <debacle@debian.org> |
| X-Amavis-Spam-Status | No, score=-110.264 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-2.355, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no |
| User-Agent | mu4e 1.10.8; emacs 29.2 |
| Jabber-ID | debacle@debian.org |
| Accept-Language | de, en, es |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| X-Debian-User | debacle |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/21783 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/871q77fxdd.fsf@fama.lan |
| Approved | robomod@news.nic.it |
| Lines | 7 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Sun, 14 Apr 2024 21:23:58 +0000 |
| X-Original-Message-ID | <871q77fxdd.fsf@fama.lan> |
| X-Original-References | <ZdcNAJOHG1_LQBai@an3as.eu> |
| Xref | csiph.com linux.debian.maint.python:15761 |
Show key headers only | View raw
Hi, are there any news regarding the status of sqlalchemy? I'm curious, because the next version of gajim will depend on sqlalchemy >= 2, which is only in experimental right now. Cheers
Back to linux.debian.maint.python | Previous | Next — Previous in thread | 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