New submission from Paul Moore: At the moment, building an application that embeds Python requires the user to have a full install of Python on the build machine, to get access to the include and library files.
Now that we provide an embeddable build of Python on Windows, would it be worth also having an "embedding SDK" which consisted of a zipfile distribution of the include and lib files? This may be pointless, as it's not that hard to install Python onto a development system, and even if it is, you'd just need to grab the "include" and "libs" directories from an existing installation, so creating your own SDK is pretty trivial. It's also extra work in the release process to provide the extra distribution file. So I'm OK if this is viewed as not worth it. The main advantage of having such an "SDK" would be strengthening the message that embedding is a well-supported scenario. ---------- assignee: steve.dower components: Windows messages: 250310 nosy: paul.moore, steve.dower, tim.golden, zach.ware priority: low severity: normal status: open title: Create an "embedding SDK" distribution? type: enhancement versions: Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25042> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
