[issue25042] Create an "embedding SDK" distribution?

[Steve Dower]

Steve Dower added the comment:

This was done! Just never closed

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25042] Create an "embedding SDK" distribution?

[Paul Moore]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25042] Create an "embedding SDK" distribution?

[Steve Dower]

Steve Dower added the comment:

It may be worth it. What I'd rather have people do is to install using the 
regular installer and include both debug symbols and debug binaries. This will 
put it in a registered location that can be auto detected (I have written a 
template for Visual Studio that does just that for extensions - will be 
released soon), and also gives a pretty solid debugging experience.

Probably we just need to get word out that it's a valuable scenario and do some 
walkthroughs/tutorials (good PyCon topic?). In my paid-work life doing 
developer tools for Python developers, it's certainly something that we as 
Microsoft are willing to offer (with VS tie-ins, obviously - when you're paid 
you are also owned :) ), but I've got no opposition to supporting this.

To do an extra package, I'd need to hear that:
* people aren't able to install a full Python distro in these contexts
* people *are* able/willing to extract and configure a ZIP distro of the same 
things
* people aren't confident building against a full distro and releasing with the 
embedded distro

>From a Visual Studio POV, making a NuGet package containing the embedded 
>Python distro and the build headers would be pretty cool, simply for the IDE 
>integration. Doesn't really help other IDEs, but since they're all different I 
>think they'll all need specific solutions anyway.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com