Ed Morley

@potiuk What you are saying makes sense for wider-reaching changes like the historic switch from the legacy resolver, however, I don't think it's as applicable here. Since: 1. This deprecation...

The performance impact of the man-db auto-update trigger appears to be getting worse - it's come up again in: - https://github.com/actions/runner/issues/4030 - https://github.com/actions/runner-images/issues/5770#issuecomment-3409530353

I suggest everyone affected by this (which seems to be quite a few projects, judging by the ping-backs in the issue history) open a GitHub support ticket asking for this...

@jkalpeshgithub Hi! Is this issue still occurring? If so, could you provide more details? (For example, Python version, other information about the environment etc)

I suppose one option would be to make `pyproject.toml` TOML parse errors fatal during settings discovery instead? (Rather than trying to defer the warning until later to avoid a warning+error)

Hi! Thank you for looking into this - however I don't think the solution in #3260 helps in the majority of cases? The CSS spec says ([source](https://w3c.github.io/webappsec-csp/2/#script-src-nonce-usage)): > For each...

Hi! My concerns were: 1. That unless the messaging was clear, it would be easy for users to think #3260 was the correct solution even when using static hard coded...

I'm slightly concerned this will lead to more fragmentation of where third party ecosystems (such as Heroku, GHA setup-python, Dependabot, ...) will need to check for Python versions when bootstrapping...

@dependabot rebase

> How do you decide which version to pick; does the latest win? The `--flatten` feature doesn't change the buildpacks selected or the paths on disk. It only affects whether...