Cody Piersall added the comment: Yeah, having "embeddable" in the name is a good hint, I think. It was almost enough for me to not even try downloading it.
Is it possible / even worth the time to give a more helpful error message? I'm not sure that it's possible, based on when the dll is laoded, or if it were possible whether it's worth doing. It might require more code than it's worth to maintain. You'd have to... 1. In the main function in C, check whether you're running the embedded Python (probably with an #ifdef) 2. If so, check that the required CRT is found (which probably requires _another_ #ifdef for 32/64 bit, and maybe Python version) 3. If it isn't found, create a message box using the Windows API explaining the problem. Which may require including the GUI libraries into the Python executable, and I don't think those are small things. I'm not sure if that is either possible or desirable, though. Or if what I explained would even work; I'm not sure if the DLLs are loaded right when the executable starts, or only as needed whenever functions from the DLLs are called. And I have _no_ idea how to check for the presence of the CRT. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24679> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
