Hi,
I dislike having to do that, but I had to make a last minute change in
my PEP 587 "Python Initialization Configuration" to allow to modify
the structure in the future without breaking the backward
compatibility. I added a "struct_size" field to PyPreConfig and
PyConfig:
* https://bugs.python.
Hi,
Le lun. 20 mai 2019 à 21:36, Antoine Pitrou a écrit :
> - Since PyInitError can be "ok", I'd rather call it "PyInitStatus".
Oh, I like this name :-)
By the way, I'm not comfortable with "PyInitError_Failed()" name since
it's true if it's an error (failure) ... or "an exit". What do you
thin
Hi,
- Since PyInitError can be "ok", I'd rather call it "PyInitStatus".
- The PyConfig example sets "module_search_paths" but not
"module_search_paths_set". Is it an error?
- "PyConfig_InitPythonConfig" vs "PyConfig_InitIsolatedConfig": why not
"PyConfig_InitConfig" and "PyConfig_InitIsol
Hi,
I expected the version 3 of my PEP to be complete, but Gregory Szorc
and Steve Dower spotted a few more issues ;-)
The main change of the version 4 is the introduction of "Python
Configuration" and "Isolated Configuration" default configuration
which are well better defined.
The new "Isolate
Hi,
Since Steve Dower asked me to write a formal PEP for my proposal of a
new C API to initialize Python, here you have!
This new PEP will be shortly rendered as HTML at:
https://www.python.org/dev/peps/pep-0587/
The Rationale might be a little bit weak at this point and there are
still 3 small
