Steve Dower added the comment:
> I'd been expecting this was commonly used as the way to give access to
> python3X.dll.
Yeah, both. The idea is to delete the files you don't want - so if you don't
need python.exe, just don't include it. Same goes for some of the native
modules (e.g.
Tom Kent added the comment:
A couple things...
>> One possible use-case is to package it along with another program to use the
>> interpreter.
> This is the primary use case. If you're doing something else with it, you're
> probably misusing it :)
Interesting, I'd been expecting this was
Steve Dower added the comment:
Updating the documentation link on the download page is being discussed as we
speak.
> One possible use-case is to package it along with another program to use the
> interpreter.
This is the primary use case. If you're doing something else with it, you're
Tom Kent added the comment:
I'm not sure I agree with that. One possible use-case is to package it along
with another program to use the interpreter. In this case they could use the
other program's native language features (e.g. .Net's Process.Start(), Win32
API's CreateProcess(), Even
Eryk Sun added the comment:
The embeddable distribution isn't intended for end users to run Python scripts
from the command line, so I don't think the CLI help needs to be special cased.
The documentation you quoted should be clarified as something like "isolated
from user and system Python
New submission from Tom Kent :
According to the documentation
https://docs.python.org/3/using/windows.html#windows-embeddable
> When extracted, the embedded distribution is (almost) fully isolated
> from the user’s system, including environment variables, system registry
> settings, and
