Thomas Güttler writes:
I see no agreement on the name for the concrete installation holding all those nice python libraries.
I don't see how you could get it.
The "concrete installation" you mention is apparently is defined by "holding all those nice python libraries" -- you make no mention of requirements.txt or any of the other "marker" files you've talked about. It's also unclear whether "concrete installation" includes things like the Python distribution itself (even the operating system), or perhaps things in site-packages but not the stdlib.
And that is the problem. The variety of "collections of libraries" (some of which are singletons, others of which may be instantiated as empty!) and accompanying configuration (if any) that a developer might want denoted by the name you're looking for is pretty well infinite. It's not going to be the same as the distribution, since those often don't include configuration files (and does the "example.cfg" count?) In any case it's large enough that we're going to get substantial disagreement on the definition even before we try to choose a name.