4 ms·
The PEP was/is accepted. The problem is all the resources with the knowledge to merge it have since been reassigned. It's still pending merge into py3k.
by jnoller 16y ago
The PEP was/is accepted. The problem is all the resources with the knowledge to merge it have since been reassigned. It's still pending merge into py3k.
- ot 16y agoThat's not entirely accurate, the PEP is about merging it in a new branch called py3k-jit. AFAIK there are no plans of merging it in the main, vanilla, py3k.
- jnoller 16y agoLook at the header - 3.3 the intention was to accept the PEP, do the merge, and then ask for final approval for merge into Py3k. The intention on both sides was to always merge it into vanilla Py3k.
- ot 16y agoYes you are right, what I meant is that it will still need a "final approval", which I think will imply a more thorough discussion and a round of voting. The "merge plan" section states that, before that, all the jit-related patches will be confined in the py3k-jit branch
- jnoller 16y agoAnd you're right; final approval won't come because well, it ain't done.