Distutils-SIG

Download

distutils-sig@python.org

July 2018

55 participants
32 discussions

[Distutils]Provisional PEPs can now actually be marked as Provisional
by Nick Coghlan July 8, 2018

July 8, 2018

Hi folks, Some time ago, we adjusted the distutils-sig PEP approval process to include a "Provisional" status, where we approved changes for inclusion in the reference implementations (typically pip and setuptools), but still reserved the right to make adjustments if practical experience showed that we'd missed something critical. Earlier today, I merged the amendment to PEP 1 that makes that part of the Python Enhancement Proposal process in general, and explicitly marked the affected PEPs as Provisional. For distutils-sig, that update affects both of the pyproject.toml PEPs (although I expect PEP 518 isn't too far off being marked as Final - the question of the precise meaning of a missing build-system table when pyproject.toml is present seems to be the only underspecified point that anyone has found during the Provisional period). Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

3 2

[Distutils]Handing over default BDFL-Delegate responsibilities for packaging interoperability PEPs to Paul Moore
by Nick Coghlan July 8, 2018

July 8, 2018

Hi folks, Since 2013, I've been the default BDFL-Delegate for packaging interoperability PEPs. In that time, the Python packaging ecosystem has moved forward in a lot of different areas, with pip being shipped by default with CPython, the wheel binary packaging format reaching ever-increasing heights of popularity, the cross-distro manylinux ABI compatibility specification being developed, the new pyproject.toml based sdist format being defined, the PSF's Packaging Working Group being formed, the Python Packaging User Guide being developed, and various aspects of the packaging metadata being enhanced to improve the general user experience of the Python packaging ecosystem. The role of the BDFL-Delegate in that process is partly about making arbitrary decisions when arbitrary decisions need to be made ("The bikeshed shall be green!"), but also about helping to guide discussions in productive directions, as well as determining when more complex PEP level proposals have reached a sufficient level of consensus that it makes sense to provisionally accept them and move on to publishing reference implementations. While it's been a fascinating ~5 years, I've decided that it's time for me to hand over those responsibilities to another PyPA contributor. With Guido's approval, I've asked Paul Moore if he'd be willing to take on the role, and Paul has graciously accepted the additional responsibility. Paul's a long term pip contributor, and also a CPython core developer, with a lot of practical experience in getting Python (and Python packaging) to work well in Windows environments. He's also a familiar, calm, and constructive presence in design discussions within distutils-sig, pip and other PyPA projects, which is an important characteristic when taking on BDFL-Delegate responsibilities. I'd like to personally thank Paul for being willing to take on this task, and I look forward to many more productive design discussions! Cheers, Nick. P.S. I'm not stepping down from Python packaging related activities entirely, as I'll still be involved in Python Packaging User Guide and pipenv maintenance, and will continue as a member of the PSF's Packaging Working Group. However, the final sign-off for packaging interoperability PEPs will now rest with Paul or someone else that he appoints, rather than with me :) -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

4 3