pip-run VS peps

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.

If you have suggestions that could improve the Python experience, consider proposing these through the Python Enhancement Proposal (PEP) process. The Mojo team actively encourages this, as it views Mojo as a new member of the Python family.

after 1-6, should have a good idea of what type of documentation / coding standards / tools / levels of abstraction want to have/see for a projects source code/deliverable. :-)

[1] : http://github.com/Blackgu/ebooks/blob/master/ebooks/2012-2-1...

[2] : http://peps.python.org

[3] http://medium.com/codex/say-goodbye-to-loops-in-python-and-w...

Yet development is carried via consensus between developers and users, there are places where users come to discuss thinks and ask questsion, there are place where resolutions are described in a POSITA-understandable terms and so on.

Oh, I have a pretty fresh news for you.

https://github.com/python/peps/pull/2955

You mean like PEPs? https://peps.python.org