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 <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
