As I mentioned on the github issue, aiopg's approach is one that has always
alarmed me, which is that they have taken large tracts of SQLAlchemy's
internals, copied them into their own source base, and simply altered them to
fit their needs. I would never recommend this approach as it has
n
Sqlalchemy 1.4 has asyncio support for postgresql using asyncpg. Not sure
how feasible it is to replace that library for you.
On Wed, 14 Jul 2021, 17:10 Marat Sharafutdinov, wrote:
> The problem is the part of my code base depends on third party library
> (aiopg) which should be compatible with
The problem is the part of my code base depends on third party library
(aiopg) which should be compatible with SQLAlchemy 1.4 too but there some
problems with it (
https://github.com/aio-libs/aiopg/issues/798#issuecomment-879815102 ) which
make migration from 1.3 to 1.4 impossible for now =/
O
On Wed, Jun 9, 2021, at 7:21 PM, Marat Sharafutdinov wrote:
> The problem is that currently only the entire codebase can be migrated from
> 1.3 to 1.4, even though it can be extremely difficult or too long to do.
>
> I suggest the following way of pinning dependencies:
> sqlalchemy==1.3
> sqlal
Hi,
> The problem is that currently only the entire codebase can be migrated
from 1.3 to 1.4, even though it can be extremely difficult or too long to
do.
I don't agree with this assessment. From my experience the main
incompatibility is the url that has become immutable. Other than this most
The problem is that currently only the entire codebase can be migrated from
1.3 to 1.4, even though it can be extremely difficult or too long to do.
I suggest the following way of pinning dependencies:
sqlalchemy==1.3
sqlalchemy2==1.4 or sqlalchemy2==2.0
Then current codebase will continue to wo
hi there -
having a separate project name on pypi doesn't solve any issue that isn't
already solved by using version pinning - the "sqlalchemy" name on pypi is
already at 1.4. the only way to install 1.3 is by requesting "pip install
sqlalchemy < 1.4".
As you've probably seen, SQLAlchemy 1.4
Currently I'm on SQLAlchemy 1.3 and there is a lot of work I have to do to
migrate to 1.4 / 2.0. I think it's good idea to distribute 1.4 / 2.0
versions not only as "SQLAlchemy" project but as additional separate
"SQLAlchemy2" project too with initial 1.4 version and then 2.0. This will
give op
