[Python-ideas] Windows assistance for PEP 432 (CPython startup sequence) (original) (raw)
Georg Brandl g.brandl at gmx.net
Sun Jan 13 11:31:54 CET 2013
- Previous message: [Python-ideas] Windows assistance for PEP 432 (CPython startup sequence)
- Next message: [Python-ideas] Windows assistance for PEP 432 (CPython startup sequence)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 13.01.2013 03:15, schrieb Nick Coghlan:
On Sun, Jan 13, 2013 at 11:59 AM, Brian Curtin <brian at python.org> wrote:
On Sat, Jan 12, 2013 at 8:55 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
I've started work on the PEP 432 implementation at https://bitbucket.org/ncoghlan/cpythonsandbox/compare/pep432modularbootstrap..default#commits
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 "pep432modularbootstrap" 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. I'll try to take a look within the next few days. 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).
That sounds unfortunate -- did you open a report/feature request in their tracker?
Georg
- Previous message: [Python-ideas] Windows assistance for PEP 432 (CPython startup sequence)
- Next message: [Python-ideas] Windows assistance for PEP 432 (CPython startup sequence)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]