Please be vendor neutral and don't launch something that is GitHub only and centralized and faun over GitHub's security. <a href="https://github.com/python-poetry/poetry/issues/7940#issuecomment-1551713573">https://github.com/python-poetry/poetry/issues/7940#issuecom...</a> <a href="https://news.ycombinator.com/item?id=35646436">https://news.ycombinator.com/item?id=35646436</a>
I wrote a few scripts years ago to automate the creation of packages, name them something similar to a popular project (typo squatting), and then verify them by creating a new pypi user with a new email address. The payload was just an http request to a server I ran.<p>Submitted this to pycon, and I let the PSF know. Neither were interested. Haven’t trusted a single Python package since.
My wishlist: a mirror metadata service like Yarn to force pypi to innovate more. Pip is slow because it doesn't store the dependency metadata and has to download all upstream dependencies during the resolution phase. They were too busy wasting time on minor issues like domain squatting than core dependency resolution concerns. I also want to see Python support simultaneously conflicting diamond dependencies like Npm and Cargo. Python doesn't even support shading. One old dependency and your whole build breaks, with no recourse aside from forking upstream.
Role mentions security. Candidate shows no experience with security.<p>It would've been weird... but then you remember it's Python. It's by amateurs for amateurs. Well, god speed and god bless. Who knows, maybe despite the counter-indications something good will come out of it.
in the name of supply chain security, i just want verified package signatures (cosign, not the extant unused gpg), the new passwordless publication is good step towards (get humans and static credentials out of pushing assets). actually one more minor, support for poetry in pip-audit.. <a href="https://github.com/pypa/pip-audit/issues/84">https://github.com/pypa/pip-audit/issues/84</a>