Development continuation

[adrianlasota]

@pahaz I would like to know if there are any upcoming releases or updates planned for the sshtunnel library. Additionally, if the development is no longer active, could you recommend any alternative libraries that offer similar functionality and are actively maintained?

We have upcoming changes in our project that require an official release of the sshtunnel library to ensure compatibility and stability.

Thank you.

[rewgs]

No idea if you're still interested, but I'm working on modernizing the library via my fork.

[lymperis-e]

@rewgs what stage are you in? Is your fork yet suitable for production use?

[rewgs]

Not suitable for production use yet, no. It's still definitely in progress. I got a decent start on it but got very busy with some other projects and had to divert my attention for a while. I'll get back to it as soon as I can, though. In the meantime, PRs are encouraged!

[ddxv]

could you recommend any alternative libraries that offer similar functionality and are actively maintained?

I've loved using sshtunnel. So much of my workflow is built around it! So the recent breaking changes and general lack of development has been concerning. I'll be sad to let it go, but I've started looking around a bit.

The closest replacement seems to be this, which is actively maintained. I haven't tried it yet, but it has built in functions for the basic port forwarding I am doing.
https://github.com/ronf/asyncssh

Second, is Paramiko itself. For my usecase, connecting to a remote DB via port forwarding, Paramiko has a demo showing how to do this here that is quit short:
https://github.com/paramiko/paramiko/blob/main/demos/forward.py

The difference, based on a bit of research just now, is that asyncssh is newer and async based. For my usecase which is that I create a tunnel per app which lives the lifetime of the app, I don't think that aysnc is specifically a benefit for me, but it could be beneficial in the future. On the Paramiko side, since SSHTunnel was based on it, the APIs are really similar and the flow might be similar enough that it has the least disruption if I switch.

Edit:
I went ahead and tried asyncssh and it was very easy to get going. In the end though, I'm not sure it would have been anything different than Paramiko for my usecase, as I ended up needing to work around it's async so I could get the port back out. Here's my implementation:
https://github.com/ddxv/adscrawler/blob/7d76a8d27aa1bd1cffdcf9729d9ebafe3f186d1b/adscrawler/dbcon/connection.py#L72