sh

I love how this import trick shows how hackable Python is - and it’s this very hackability that has led to so many of the advances we see in AI. Arguably without operator overloads we’d be 5 or more years behind. https://github.com/amoffat/sh/blob/2a90b1f87a877e5e09da32fd4...

Another technique I've seen is to hide or overwrite the name of the class, such that client code only knows about the instance (and is expected to use it directly rather than doing any kind of access or instantiation). Of course, this doesn't give you lazy initialization unless you lazily import the module, at which point you would definitely be better off just using the module object directly. There's also code out there which replaces the cached module object with a class instance in top-level code! This is especially used to work around the prior lack of module-level `__getattr__` (and `__dir__`), added in 3.7 (https://peps.python.org/pep-0562/). But you might still need it if for some reason you want to hook into the lower-level `__getattribute__`. And Andrew Moffat's `sh` package still does this (https://github.com/amoffat/sh/blob/de

I've maintained a fairly popular open source project for over 13 years[1]. The software is basically "complete." How does funding work for someone like me? I have no initiatives with it that require funding. Occasionally, I need to fix a bizarre obscure bug, or support a new python version/feature (async/await being the last big one). But otherwise, I just field questions a few times a month. Truth be told, I'd rather be done with the project completely. It's like a little monkey on my back that I can never be rid of, that I must always tend to. But at the same time, since I can never realistically receive funding for it, the only value I get is the fact that my name is on it. I wish a big, legit company would just buy it off of me somehow, but there's no incentive for them either. I don't know how this ends. 1. https://github.com/amoffat

I think the linked page gives a better overview of what this Python lib can do, but if you want to know more: The repository is here: https://github.com/amoffat/sh And the full documentation is there: https://amoffat.github.io/sh/index.html In particular I was wondering if it supports piping, and it does: https://amoffat.github.io/sh/sections/piping.html But

I love the motivation for this tool. This looks very useful for when you just want to make something easier in an existing shell script, without fully migrating to Python. If you do want to migrate fully to Python, I encourage people to use sh[0] (disclaimer: author). One concern that I have is that it could be so useful that now your script is filled with `| pz`, and is launching Python processes at every line . Now you have a tangled hybrid of Bash and Python. 0. https://github.com/amoffat/sh

For start, https://github.com/amoffat/sh seems to not even mention this problem. No idea whether it would help but clearly staying exactly > I've maintained for over 10 years. I don't recall ever receiving a donation. I am still maintaining it, but I just don't have time to add the improvements that it needs to keep up with the ecosystem (asyncio, for example). If organizations who use it got together and chipped in some non-negligible amount, I would be much more serious about keeping up with it, but $0, or $5-20/month, is just not realistic incentive to compete with other priorities in my life. may be a good idea. Even if that would not help this project then making people aware about problem in general would help.

I'm an open source author and maintainer of a somewhat-popular python package[0] (~1M downloads/month) that I've maintained for over 10 years. I don't recall ever receiving a donation. I am still maintaining it, but I just don't have time to add the improvements that it needs to keep up with the ecosystem (asyncio, for example). If organizations who use it got together and chipped in some non-negligible amount, I would be much more serious about keeping up with it, but $0, or $5-20/month, is just not realistic incentive to compete with other priorities in my life. I don't know the answer, but that's my thought process. 0. https://github.com/amoffat/sh

Many people have responded to your comment saying that this is bad and that using other languages makes things more complicated when you are doing 'bash-like' things. I'm guessing they haven't actually tried it, because I have used python with the [sh](https://github.com/amoffat/sh) package many times to replace bash scripts, and I have never regretted it.

Author of a project with > 5k stars here[0]. I honestly haven't had any experience with mean people for the nearly 10 years since I started it. I've had maybe one or two pushy people, but it was mostly justified (I hadn't pushed a release in like 3 years). They were pushing me to find a maintainer if I wasn't going to answer some of the open requests. 0. https://github.com/amoffat/sh

I agree, but this lib does make it easier: https://github.com/amoffat/sh

Check out python sh: https://github.com/amoffat/sh

Shameless self promotion: if you want to automate subprocesses with python in an intuitive way, give sh a try: https://github.com/amoffat/sh

Try the python 'sh' module (https://github.com/amoffat/sh). For example: from sh import git print git('version')