Marc Mueller

@corneliusroemer This issue should be fixed with #468. 

Personally, I'd love this option. However, just from working the the cache API myself I noticed permission issues with deleting cache entries. For example the normal `pull_request` trigger doesn't grant...

> > Use the SPDX license identifier for GPL-2.0-or-later > > We use Apache 2.0. Sorry, copy-paste error in the PR description. The file change is correct though.

> How compatible is this with our current license validation in Home Assistant core? It's fully compatible. The current implementation just looks for "Apache License" and similar (which is obviously...

> License SPDX identifiers sounds good. But until the PEP is accepted I don't think we should try to change libraries in one way or the other. The current status...

[PEP 639](https://peps.python.org/pep-0639/) has been provisionally accepted. It'll still take some time before the build backends fully support it though. However, changing the license text to the SPDX identifier should be...

> That project is using poetry which documents that the SPDX identifiers should be used for the license field. BTW: Both (poetry and setuptools) output to the same project metadata...

I mentioned it in the issue already. I think we should not move forward with it, at this time. Maybe at some point we can pick it up again. https://github.com/PyCQA/pylint/issues/4814#issuecomment-980727214...

> > Do you want to lead the communication and specification effort @matusvalo ? > > Yes, I can take this activity on my shoulders. But unfortunately, I was playing...

> ftfy is the first libray to use this one right? The first to use `Library-Expression` although I'd expect more now that `hatchling uses it by default. The PR doesn't...