bpo-32604: Expose the subinterpreters C-API in a "private" stdlib module.#1748
Conversation
e0611a8 to
bee1baa
Compare
May 23, 2017 04:38
bee1baa to
060a720
Compare
May 23, 2017 23:42
060a720 to
2fd0e64
Compare
August 22, 2017 20:01
114bda4 to
52ca360
Compare
September 7, 2017 17:58
52ca360 to
9991d75
Compare
November 27, 2017 23:24
9991d75 to
e9d9b04
Compare
December 5, 2017 01:29
81de3c8 to
bfc025f
Compare
December 12, 2017 05:12
e05d02e to
396e294
Compare
December 23, 2017 00:30
5266080 to
c86647a
Compare
January 13, 2018 00:49
ff4ae72 to
0981dbf
Compare
January 20, 2018 01:44
0981dbf to
0be6314
Compare
January 20, 2018 02:13
8ae8507 to
2ebc68c
Compare
January 27, 2018 19:15
|
FYI, I've temporarily removed the Windows support to see if anything else breaks. I'll add it back in soon. I do not plan on merging this without it. |
Sorry, something went wrong.
ebbf591 to
9718b91
Compare
January 27, 2018 21:07
edec009 to
092fccc
Compare
January 27, 2018 22:50
092fccc to
b07e928
Compare
January 27, 2018 23:19
|
@zooba I suspect my problem is with Py_BUILD_CORE. When I don't set it I don't get the symbols out of Include/internal. When I do set it I end up missing stuff from python37.lib at link time. I tried adding a "Link" directive right below where I set Py_BUILD_CORE, but that did not help. :/ Any ideas on what I need to do? |
Sorry, something went wrong.
|
@python/windows-team Any of you have ideas on how I can get this PR to link on Windows? |
Sorry, something went wrong.
|
In the interest of the feature freeze I'm going to land the PR without Windows support. :/ The risk for beta1 is low since the PR does not have any OS-specific code and the new module is only for use in the test suite. I'll work on getting Windows support done ASAP. |
Sorry, something went wrong.
https://bugs.python.org/issue32604