instld VS pip-run

This library is also a wrapper around virtual environments.

This library is also a wrapper around virtual environments.

This is also a dependency management library.

This is also a dependency management library.

This is also a dependency management library.

The instld library is also a way to quickly run scripts where dependencies can be installed in a temporary directory.

The instld library is also a way to quickly run scripts where dependencies can be installed in a temporary directory.

The instld library is also a way to quickly run scripts where dependencies can be installed in a temporary directory.

The instld library is also a way to quickly run scripts where dependencies can be installed in a temporary directory.

pip-run – dynamic dependency loader for Python

where only '[build-system.requires]' is supported. I think this could be extracted statically, through the AST, so no eval needed.

One of the links lead me to alternative proposals at https://github.com/jaraco/pip-run/issues/44 but none of them fit this form. (It's "Variant 1: single variable" with '__pyproject_toml__' as the variable name, "Option 2: Requirements.txt in comments" but in a string, and as TOML.)

The main objection seems to be 'Users may be tempted to dynamically construct the list (through runtime execution), but only static values are supported.' replacing 'list' with 'string'.

I have such a poor grasp one what "users" want that I can't judge.

If you insist on writing scripts, at least use something like pip-run to annotate which dependency versions it needs and verify them before running.

pip-run serves the same purpose as pipx. The only difference is that pip-run doesn't provide a persistent package installation but rather deletes all environments after the tool has been executed.