rich VS hy

4oe DEPRECATION: A future pip version will change local packages to be built in-place without first copying to a temporary directory. We recommend you use --use-feature=in-tree-build to test your packages with this new behavior before it becomes the default. pip 21.3 will remove support for this functionality. You can find discussion regarding this at https://github.com/pypa/pip/issues/7555. Added file:///tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/source to build tracker '/tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-req-tracker-pg0s4jcy' Created temporary directory: /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-modern-metadata-r4la6pf4 Running command /nix/store/cgxc3jz7idrb1wnb2lard9rvcx6aw2si-python3-3.9.6/bin/python3.9 /nix/store/3xcbipxg7dacja7arkqsdp31wv48a59b-python3.9-pip-21.1.3/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py prepare_metadata_for_build_wheel /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/tmpmpim2fje Preparing wheel metadata ... done Source in /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-req-build-rzzt_4oe has version 1.0.0.0, which satisfies requirement oreo==1.0.0.0 from file:///tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/source Removed oreo==1.0.0.0 from file:///tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/source from build tracker '/tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-req-tracker-pg0s4jcy' Created temporary directory: /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-unpack-1nnn3w07 Building wheels for collected packages: oreo Created temporary directory: /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-wheel-jyheihmt Destination directory: /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-wheel-jyheihmt Running command /nix/store/cgxc3jz7idrb1wnb2lard9rvcx6aw2si-python3-3.9.6/bin/python3.9 /nix/store/3xcbipxg7dacja7arkqsdp31wv48a59b-python3.9-pip-21.1.3/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py build_wheel /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/tmp8ljzwh4w Building wheel for oreo (PEP 517) ... done Created wheel for oreo: filename=oreo-1.0.0.0-py3-none-any.whl size=10319 sha256=fb4efcf870de4c110a634e3c533e9bf01b7688bf2a5afaccabcfaa6970ce7885 Stored in directory: /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-ephem-wheel-cache-w03nuxin/wheels/39/40/4f/f0b9937669794874506485e96ceaa27a49834a1f4b7406fb86 Successfully built oreo Removed build tracker: '/tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-req-tracker-pg0s4jcy' Finished creating a wheel... Finished executing pipBuildPhase installing Executing pipInstallPhase /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/source/dist /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/source Processing ./oreo-1.0.0.0-py3-none-any.whl Collecting rich@ git+https://github.com/syvlorg/rich.git@master Cloning https://github.com/syvlorg/rich.git (to revision master) to /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-install-qnk_ga2u/rich_0259bc6873ce438bbee709d94f271c2d Running command git clone -q https://github.com/syvlorg/rich.git /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-install-qnk_ga2u/rich_0259bc6873ce438bbee709d94f271c2d Installing build dependencies ... error ERROR: Command errored out with exit status 1: command: /nix/store/cgxc3jz7idrb1wnb2lard9rvcx6aw2si-python3-3.9.6/bin/python3.9 /tmp/nix-build-python3.9-oreo-1.0.0.0.drv-0/pip-standalone-pip-1673qp7k/

Not exactly the same (doesn't embed into the source like this did), but I believe Hylang[0] is the best Lisp package available for modern Python.

[0] https://github.com/hylang/hy

Isn't that a bit what hy (https://hylang.org/) tries to do ? AIUI it is a lisp interacting directly with the AST of Python, allowing seamless interop: Python modules can be used from hy and vice versa, everything is transparent.

I’ve been keeping loose tabs on this and Hy[1] for a while, but I’ve had some trouble figuring out the major differences between them and the use-cases for either. Would love to see an in-depth comparison in the form of a blog post sometime (though maybe the answer here is to do the research and write one up myself).

1: https://hylang.org

“Python is for scientists. Lisp is for engineers.”

Then what does that make Hy language?

https://hylang.org/

Re Languages with lots of example code and LLM’s

With translators or things like Hy lang, one could get the LLM’s to solve your problem in Python before converting it to another form. Then, you just need a translator. If lacking one, it’s easy to translate by hand.

The practicality of this concept will probably vary by use case. My experiments had GPT doing sketching, implementations, boilerplate, and even porting Python to Rust. A legally-clear LLM trained on multiple languages could probably be fine-tuned to do Python to LISP conversions. If not, Hy might be a stepping stone, too.

You could say so: I've been maintaining the compiler since 2016 ;). Infinitesimal Quest 2 + ε (SQ) exists more to advance Hy than for its own sake.

If you are using Python - you might find Hylang (https://hylang.org) interesting.