PyPA-Committers

Download

pypa-committers@python.org

January 2022

7 participants
2 discussions

Brett Cannon as PEP Delegate for PEP 639
by Paul Moore Jan. 27, 2022

Jan. 27, 2022

Brett has volunteered as PEP delegate for PEP 639 (Improving license clarity with better package metadata). The process says: """ If their self-nomination is accepted by the other PyPA core reviewers, the lead PyPI maintainer and the default PEP-Delegate for package distribution metadata PEPs, then they will have the authority to approve (or reject) that PEP. """ It's not 100% clear to me how we get that acceptance, so I'm posting here to give anyone who wants to, a chance to object. In the absence of any specific comment in the process, I'll give it a week and then if there's no objections, assume that Brett will be PEP delegate. If anyone thinks approving PEP delegate volunteers should be handled differently, please say so. I'm just guessing as to what's reasonable here :-) Paul

6 9

Vote: +1 to Mark PEP-660 final or -1 to keep it provisional
by Bernat Gabor Jan. 6, 2022

Jan. 6, 2022

https://discuss.python.org/t/pep-660-editable-installs-for-pep-517-style-bu… Stéphane Bidoul raised the question of whether we should mark PEP-660 (editable installs) final now or not. Me and Paul Moore have differing opinions on this so we're calling a vote of the members. - Reasons to mark it final as Stéphane said: *PEP 660 has now been implemented in pip, flit, enscons, hatchling, pdm, poetry (merged by not released).* - Reasons why I think we should not mark it final: *You’ll only find out what gaps the standard has once it’s widely used. IMHO enough is not a few backends that are overall not that often used adopts it. But enough should be when the majority of the projects using it adopt it (e.g. 80% of projects). Now I can see this by either setuptools implementing it or people moving away from using setuptools in time. Most projects that currently implement the standard don’t provide a generic build framework, as setuptools does, but instead only a subset so they don’t necessarily expose the current standards potential issues (think e.g. flit is restricting itself currently to purely toml configuration driven and avoids having a build step).* I'll start the voting, from my side it's -1, aka keep it provisional for now. All the best, Bernat

14 26