STINNER Victor added the comment:
> I'm building a dll add-in (on Windows) in which I want to use the installed
> version of Python, not provide my own installation. When py_initialize fails
> it appears to call exit(). (...)
This issue has been fixed by the PEP 587 in bpo-36763:
Yukihiro Nakadaira added the comment:
This problem easily happen when there is no python installation and there is
standalone python application compiled with py2exe or cx_Freeze (e.g.
Mercurial). Such application have pythonXX.dll in its directory. But its
python library can not be loaded
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13533
___
___
Python-bugs-list mailing
Nick Coghlan added the comment:
Changing this isn't really feasible with the current design of the
initialisation code - we call Py_FatalError in various places because we don't
have the infrastructure set up to do anything else.
PEP 432 should help (and the basic design there still seems
Changes by Martin Morrison m...@ensoft.co.uk:
--
nosy: +isoschiz, pconnell
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13533
___
___
New submission from dangermouseb da...@bigredmedia.tv:
I'm building a dll add-in (on Windows) in which I want to use the installed
version of Python, not provide my own installation. When py_initialize fails it
appears to call exit(). This doesn't seem very friendly behaviour for an
Antoine Pitrou pit...@free.fr added the comment:
If we add a (yet another) variant of Py_Initialize, I would suggest we make it
extensible by passing it a struct of arguments (so that the struct can be
augmented without breaking compatibility).
--
components: +Interpreter Core -None
Changes by Eric Snow ericsnowcurren...@gmail.com:
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13533
___
___
Python-bugs-list
