Windows assistance for PEP 432 (CPython startup sequence)
I've started work on the PEP 432 implementation at https://bitbucket.org/ncoghlan/cpython_sandbox/compare/pep432_modular_bootst... As part of that work, I'm also cleaning up some of the crazier things in the source tree layout, like "pythonrun" being this gigantic monolith covering interpreter initialisation, code execution and interpreter shutdown all in one file, as well as the source files for the application binaries being mixed in with the source files for standard library builtin and extension modules. This means I know I'm breaking the Windows builds. Rather than leaving that until the end, I'm looking for someone that's willing to take the changes from the "pep432_modular_bootstrap" in my sandbox repo, check what is needed to get them building on Windows, and then send me pull requests on BitBucket to fix them. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Sun, Jan 13, 2013 at 11:59 AM, Brian Curtin <brian@python.org> wrote:
Richard Oudkerk has given me a patch at least for the VS 2010 files. (We discovered in the process that bitbucket only allows pull requests for forked repos back to their parent - no pull requests between sibling repos). Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Sun, Jan 13, 2013 at 8:31 PM, Georg Brandl <g.brandl@gmx.net> wrote:
I hadn't, but I have now: https://bitbucket.org/site/master/issue/5968/allow-creation-of-pull-requests... Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 13 January 2013 02:15, Nick Coghlan <ncoghlan@gmail.com> wrote:
Looks like it's OK now - I just pulled your latest version and it built and ran all the tests fine. I didn't build the various extension modules that need external libraries, I assume they won't have changed. I can do if it would help, though. Couple of crashes in test_capi and test_faulthandler. I suspect those are expected, though. And one in test_urllib2 which I haven't investigated yet but I doubt is related to these changes. Paul
On Sun, Jan 13, 2013 at 12:53 PM, Paul Moore <p.f.moore@gmail.com> wrote:
The test_capi and test_faulthandler ones are expected but kind of a hassle on the desktop. There's an issue somewhere and I have a patch to make those work nicer, but there's a few ways we can go about it. On the buildbots those aren't a problem because we already remove and/or have a script that closes the crash dialogs.
On Sun, Jan 13, 2013 at 11:59 AM, Brian Curtin <brian@python.org> wrote:
Richard Oudkerk has given me a patch at least for the VS 2010 files. (We discovered in the process that bitbucket only allows pull requests for forked repos back to their parent - no pull requests between sibling repos). Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Sun, Jan 13, 2013 at 8:31 PM, Georg Brandl <g.brandl@gmx.net> wrote:
I hadn't, but I have now: https://bitbucket.org/site/master/issue/5968/allow-creation-of-pull-requests... Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 13 January 2013 02:15, Nick Coghlan <ncoghlan@gmail.com> wrote:
Looks like it's OK now - I just pulled your latest version and it built and ran all the tests fine. I didn't build the various extension modules that need external libraries, I assume they won't have changed. I can do if it would help, though. Couple of crashes in test_capi and test_faulthandler. I suspect those are expected, though. And one in test_urllib2 which I haven't investigated yet but I doubt is related to these changes. Paul
On Sun, Jan 13, 2013 at 12:53 PM, Paul Moore <p.f.moore@gmail.com> wrote:
The test_capi and test_faulthandler ones are expected but kind of a hassle on the desktop. There's an issue somewhere and I have a patch to make those work nicer, but there's a few ways we can go about it. On the buildbots those aren't a problem because we already remove and/or have a script that closes the crash dialogs.
participants (4)
-
Brian Curtin -
Georg Brandl -
Nick Coghlan -
Paul Moore