Re: [pylons-discuss] Re: SQLAlchemy 2.0 support

2022-11-29 Thread Jonathan Vanasco
That should be fine. If you see any warnings, that's unfortunately more than most developers see! On Monday, November 28, 2022 at 4:14:16 PM UTC-5 zsol...@gmail.com wrote: > I just use "PYTHONWARNINGS=default", afaik that's all I need to do right? > It shows me all the Pyramid and waitress

Re: [pylons-discuss] Re: SQLAlchemy 2.0 support

2022-11-28 Thread Zsolt Ero
I just use "PYTHONWARNINGS=default", afaik that's all I need to do right? It shows me all the Pyramid and waitress warnings. On 28. Nov 2022 at 19:53:27, Jonathan Vanasco wrote: > On Sunday, November 27, 2022 at 1:23:21 PM UTC-5 zsol...@gmail.com wrote: > >> Great to know! About the warnings,

Re: [pylons-discuss] Re: SQLAlchemy 2.0 support

2022-11-28 Thread Jonathan Vanasco
On Sunday, November 27, 2022 at 1:23:21 PM UTC-5 zsol...@gmail.com wrote: > Great to know! About the warnings, I'm on 2.0 and it works, so either some > of those RemovedIn20Warning are not removed or none of them are left. > The warnings are still there, you most likely have fully compatible

Re: [pylons-discuss] Re: SQLAlchemy 2.0 support

2022-11-27 Thread Zsolt Ero
Great to know! About the warnings, I'm on 2.0 and it works, so either some of those RemovedIn20Warning are not removed or none of them are left. I mean I rewrote my queries to 2.0 style, but I've read that 1.x style queries will continue to work, they are just removed from the documentation now.

[pylons-discuss] Re: SQLAlchemy 2.0 support

2022-11-27 Thread Jonathan Vanasco
There was one potential incompatibility with transaction, but the zope.sqlalchemy team addressed it already ( see https://github.com/zopefoundation/zope.sqlalchemy/issues/60 ). There are deprecation warnings that are still unhandled ( see