pyp

This looks interesting! A tool in the same vein that I already use is pyp (`pypyp` on PyPI). This project, pypipe, has built-in record splitting and CSV support that pyp doesn't. CSV is lower-friction. pyp automatically determines what modules to import. It is very convenient and would be nice to have here. A version of `pypprint` (https://github.com/hauntsaninja/pyp/blob/9408446a41bfdc60e44...) may be useful, too. The most famous Python command-line tool like this is probably Mario (https://github.com/python-mario/mario), which isn't maintained. pyp's readme compares Mario and some other alternatives: https://github.com/hauntsaninja/pyp/blob/9408446a41bfdc60e44.... pypipe is different from most for also having a feature like `--explain` in pyp (code generation).

> I too can never remember jq syntax when I need to. I usually just end up writing a Python script Same here! That's why for small things I made pyxargs [1] to use python in the shell. In another thread I also just learned of pyp [2] which I haven't tried yet but looks like it's even better for this use case. [1] https://github.com/elesiuta/pyxargs [2] https://github.com/hauntsaninja/pyp

I have bookmarked/tried so many Python/Shell mashups over the years. IMHO the following is about the only one that's tasteful in terms of project scope and not going off the deep end: https://github.com/hauntsaninja/pyp

> The submission is about a non-standard dialect of Awk True, but the comment I responded to also has this: > You won't need to learn Awk Regardless, let's accept the claim that it's only about non-standard frawk. > If it's between that and Pyp, why not use Pyp? Because, as the instructions[0] point out > Run pip install pypyp (note the extra "yp"!) > pyp requires Python 3.6 or above. It's necessary to install pip and Python at least to do so, I expect that I can produce a binary for frawk and drop it in far more easily. I'm not even sure what advantage Pyp has over using a Python REPL (or Ruby or perl etc). > And also, in the technology business, you are supposed to make progress happen. I do that by writing good code and improving processes. As I've pointed out, I fail to see how needing to include the Python ecosystem is "progress" ove

I wrote a similar tool a while back. My solution for this was to statically analyse the input to discover unused names. The cool part of doing transformations statically is that you're able to see the exact Python code you'd run without running it, e.g. `pyp --explain x[:5]`. https://github.com/hauntsaninja/pyp

I wrote a similar tool a while back that lets you create your own "magic" variables. I use `f` all the time! https://github.com/hauntsaninja/pyp#pyp-lets-you-configure-y...

This looks like an unmaintained version of (the much more complete) pyp: https://github.com/hauntsaninja/pyp

Thank you for the extensive and thoughtful comment! This does help clarify your approach quite considerably. I wonder, since you are hoping to attract collaborators, whether there is some kind of formal spec for the language somewhere? For example, you mentioned parallel efforts: suppose I wanted to write a port to pure C; is there any way, short of reading every one of your posts and trying to contain the whole language in my head at once, for me to know exactly what I need to implement? Something I've been trying to figure out: what is the exact relationship at present between OSH and Oil? When you say "OSH" do you mean the language, or the shell itself "oil shell"? If Oil is not something I can download, why exactly does that `const v = max(1, 2)` statement work in osh? It's clearly not just a Bash implementation, it's got other featur

I've enjoyed using pyp[1] with fish to make some nice one-liners For example, custom history command to make early commands at the top, scroll to the bottom, and show the date and command on the same line function hist; history -t -R | pyp '["\t".join(pair) for pair in zip(lines[::2],lines[1::2])]' | less +G; end; funcsave hist [1] https://github.com/hauntsaninja/pyp

In a similar vein, pyp: https://github.com/hauntsaninja/pyp

I feel that most of the tools mentioned here are quite outdated already and in 2019 alternatives should be recommended. find -> fd grep -> ripgrep wget/curl -> httpie awk/sed are just horrible to learn for beginners, would advise to just pick up python instead via xonsh[1] or pyp[2] How about we don't teach new users these legacy tools and we can finally progress a little? 1 - http://xon.sh 2 - https://github.com/hauntsaninja/pyp

Thanks to everyone who checked pyp out! Not sure if this comment will ever get seen, but I just added the ability to configure pyp with statically analysed Python, so it's easy to define your own functions, import aliases, or use libraries like pipetools to make your life easier! More details at https://github.com/hauntsaninja/pyp#pyp-is-configurable

Thanks for sharing! I hadn't seen Mario before. The async support is super nifty! From a quick look, it looks like pyp might be a little quicker for some use cases since it doesn't need subcommands, but I'll definitely be updating https://github.com/hauntsaninja/pyp#related-projects

xonsh is great! I'm a fan of your cousin's work :-) I mentioned it in https://github.com/hauntsaninja/pyp#related-projects for if you want even more Python in your shell.

Yup, that was the inspiration for this project and its name. See https://github.com/hauntsaninja/pyp#related-projects for more discussion. By no means is this a new idea, but I think this iteration has some convenient twists :-)