x42005e1f commented on issue #50185: URL: https://github.com/apache/airflow/issues/50185#issuecomment-2913968644
> Looks like this package is not maintained or not sure, no activity since last Feb 2024. It is not always possible to tell from the commit activity of such packages whether they are maintained or not. Sometimes they are not updated just because there are no serious issues, in which case the author can focus on other projects. Even more ambiguous is the situation when tests are regularly run for new versions of dependencies and a lockfile is updated - in this case the repository may look alive with a huge number of commits, but in fact it has not been updated for a very long time, having very few commits in the source code for the whole history. There are also alternatives such as [greenletio](https://github.com/miguelgrinberg/greenletio) or [awaitlet](https://github.com/sqlalchemy/awaitlet). But if you want, you can implement something similar on your side - for example, SQLAlchemy has long used [its own module](https://github.com/sqlalchemy/sqlalchemy/blob/05b2442132d5ae31cfcc7a1fe95e0f6b739aa995/lib/sqlalchemy/util/concurrency.py) as part of asynchronous API implementation. These solutions have some disadvantages associated with stack growth, but they are usually insignificant. A more comprehensive solution is to implement (generators and) coroutines via greenlets - what I called (genlets and) corolets 3 years ago (for a non-public tutorial on asynchronous library design). But it is redundant for this task. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
