RE: https://phpc.social/@supergarv/116291496556589191
What fuck GitHub. I have never enabled any of this. Fastest way of losing my trust is sneakily violating consent. Not that I had any trust left.
RE: https://phpc.social/@supergarv/116291496556589191
What fuck GitHub. I have never enabled any of this. Fastest way of losing my trust is sneakily violating consent. Not that I had any trust left.
@astraluma @janl that is an incredibly annoying error but the poetry maintainer is great to collaborate with (i only mention this because uv refuses to do so while they directly take credit for my work). i attempted to propose a standard API for telemetry but was rebuffed and forgejo/codeberg did not respond when i tagged them on here. if you have any packaging workflows that are unclear or features that are nontrivial i would love to be a resource here, i have a pip fork that is much faster and writes metadata that can be queried.
i'm not sure this will be immediately useful or necessary to either of you but do just want to register that i've spent years on this subject and would be delighted for an excuse to solve problems

(This is my first attempt to propose a packaging standard in this forum. I am basing this off the instructions at PyPA Specifications — PyPA documentation. Those instructions seem to indicate that a PR against GitHub - pypa/packaging.python.org: Python Packaging User Guide should be provided at the same time, but I’m not seeing many examples of that being done for in-progress PEPs, so I am assuming this is the appropriate first stop for potential new PEPs. I also could not find a standard format...
@hipsterelectron @janl oh the problem was that https://github.com/actions/setup-python expected poetry but ghcr.io/catthehacker/ubuntu:act-latest (https://github.com/catthehacker/docker_images) doesn't include it.
Maybe the answer is use ghcr.io/catthehacker/ubuntu:full-latest instead