We can use pwk in an awk-like way. Here, we list all subfolders in the root directory, and ignore exceptions on files not being directories:

This one gives a dump to the console that, as an example of use, doesn't map to things people might want to do regularly:

[]
[]
['prepared', 'data8']
['vagrant', 'X11']
['etc', 'var', 'tmp', 'tftpboot']

I don't think people need a list of the contents of the (language improvement) subfolders of the root directory, in that style.

Could this be replaced with a better example? Something more fitting if a pipe-using sequence of unix commands?

pwk is a single-file app. Just download and chmod it, and you should be good to go.

Is insufficient. People want Homebrew style installs so they can keep up with your big fixes and enhancements.

Hello, I've been playing around with your package and I've loved I'm loving it so far!

I would, however, like to have an option in the cli to include a config file that would be expand the code's namespace.

Example:

# Config file ensures my path file exists and I can easily do something with it
# My aliases are also conveniently saved
pathlib import Path
P = print
if not (some_file := Path('./some_file')).exists():
    raise Exception("some_file doesn't exist!")

$ pwk '[P(line) for line in some_file.open().readlines())]' --config ./path/to/pwk_cfg.py

I'm currently working on this feature on my own fork; and would like to know if you'd be interested in a PR.

Why not edit pwk directly

This would allow me to have multiple config files for different projects, making it more convenient than hopping over to /usr/bin/pwk and editing the file directly or copy-pasting it everywhere.

What about name conflicts, won't this make it trickier to develop pwk itself?

We can pass the environment over to exec directly like so:

exec(python_cmd, {**globals, **vars_from_config})