Repository navigation
releases to pypi for this project ? #2
Description
I thought the discussion on:
ParallelSSH/parallel-ssh#386
was going somewhere, but seems like it got deleted.
is there any release going out to pypi from this repository ?
I thought the discussion on:
ParallelSSH/parallel-ssh#386
was going somewhere, but seems like it got deleted.
is there any release going out to pypi from this repository ?
Activity
JacobCallahan commentedon Dec 1, 2024
Hi @fruch, I put out a release from my fork for Python versions up to 3.12. it's (horribly) called ssh2-python312 on pypi.
I'm also trying to see if I can put out builds for up to 3.13, but as you can see I'm running into issues.
JacobCallahan#5
If anyone wants to help, that would be awesome. Otherwise, my rust-based alternative "Hussh" has builds for Python 3.8-3.13 across most major OS's and architectures.
fruch commentedon Dec 1, 2024
@JacobCallahan
Wasn't the whole point of this fork to be a joint effort? How it ended up working mostly on your personal fork :(
Your PR regarding 3.13 looks in the right direction, but seems like a big change for one single PR...
JacobCallahan commentedon Dec 1, 2024
It is currently easier for me to work out of my fork and iterate quickly. I'm hoping that if I (or others) can get builds working on my fork, then I can move everything over here for longer term maintenance.
However, this is all a volunteer effort and ssh2-python is very low on my personal priority list. I'd love to see more volunteers come out to help, but that hasn't happened yet.
It looks large since I'm removing the copy vendoring of libssh2 in favor of using a fit submodule.
The other changes are almost entirely in the GitHub actions.
fruch commentedon Dec 1, 2024
I might be able to volunteer some time (or push someone else :))
We were considering forking it for quite some time, I was tracking the upstream project discussion, and then it vaporized.
Saw the comment about the fork just today (looking at my email history)
I'll give ssh2-python12 a ride, see it works for our project
I took a quick peak, and it seems like Cmake cache is in an unexpected location