Steve Dower <steve.do...@python.org> added the comment:
The embeddable distro is meant to be a "redistributable" for end-user machines, rather than a development kit. "Build" and "distribution" are two clearly separated tasks (at least on Windows), and so they have different dependencies. We won't be adding headers to the embeddable distro. To get the headers, you'll either want the regular installer or the package from https://www.nuget.org/packages/python (or pythonx86). Or you can grab the Include folder from git, provided you use PC/pyconfig.h and the correct tag, as none of the files are "cooked" on Windows. To directly address your two examples: - the linked SCons script is a build script, which should be run on a build machine against a development kit. But when you copy the built result to another machine, they'll only require the embeddable distro at runtime - the "frozen" distribution will need the new .exe binary to be built against a development kit. But when you copy the built result to another machine, they'll only require the embeddable distro at runtime. ---------- resolution: -> rejected stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38224> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
