Use a PEP621 license definition.

[freakboy3742]

beeware/briefcase#1812 adds parsing for PEP 621 LICENSE file definitions. This updates the base template to generate PEP 621 format output, rather than bare license text.

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[rmartin16]

I was actually just about to make this change myself 🙂

Perhaps instead of hardcoding the name of the license file in the pyproject.toml, a license_file property could be introduced that defaults to LICENSE? Not immediately useful for current purposes....but the cost is pretty low for the configurability...

[freakboy3742]

Perhaps instead of hardcoding the name of the license file in the pyproject.toml, a license_file property could be introduced that defaults to LICENSE? Not immediately useful for current purposes....but the cost is pretty low for the configurability...

I guess... but I'm not sure how/where it would be used. We have a template that generates LICENSE; so we generate a pyproject.toml that references that file. LICENSE is a "known name"; yes, there are other variants on that naming, but at this point, Github conventions are so rusted on that almost any other name is anachronistic. Sure, we could template the name and make it configurable... but who is going to use that point of configuration?

[rmartin16]

but who is going to use that point of configuration?

Yeah....I can only come up with particularly contrived situations where this could be used right now; other changes would be necessary to be of any real world use.