Allow for different filename extensions in LICENSE

[freakboy3742]

What is the problem or limitation you are having?

In #2229, we added the ability for the auto-discovered CHANGELOG file to have other extensions.

It would be desirable to use a similar approach for LICENSE files.

Describe the solution you'd like

The license discovery mechanisms (in convert, and in the config parser), should look for .md, .rst. and .txt extensions on a license file, not just a bare LICENSE file. It would also be good to catch LICENSE, LICENCE, and COPYING

Describe alternatives you've considered

Status quo, requiring the user to manually specify a license file (or rename an existing license file)

Additional context

No response

[BaanCraft]

I'd like to address this issue. Thanks.

[freakboy3742]

@BaanCraft Go right ahead! As noted in our contribution guide, we don't have a formal process for claiming issues - a comment like yours is all you need to do. Next step is a PR!

[freakboy3742]

Update: @BaanCraft has indicated they're still working on this.

[BaanCraft]

Hey, is there any way I can save the settings of my venv? I keep having to install all the dev dependencies every time I work on the issue. Thanks in advance.

[freakboy3742]

@BaanCraft I'm not sure I understand the question. You create a virtual environment; you install dependencies into that virtual environment; then whenever you want to do additional development, you re-activate that virtual environment. The "settings" of the virtual environment... is the virtual environment. If the environment is active, all of the "settings" are applied. I'm not sure I understand what workflow would result in needing to re-install dev dependencies, other than a change in development dependencies.

[BaanCraft]

@freakboy3742 Ill elaborate. Whenever I work on beeware I find myself having to constantly rerun the set-up script and hence have to install all the dependencies again. Does the venv save somewhere that I can access at later times?

[freakboy3742]

@BaanCraft Again - I don't understand the question you're asking. What "setup script" are you referring to?

If you're following the Briefcase contribution guide, your setup is:

python3 -m venv .venv
. ./venv/bin/activate
python -m pip install -Ue ".[dev]"

That creates a virtual environment in the .venv directory. If you need to start a new shell session, running . ./venv/bin/activate re-activates that virtual environment. All the dependencies are installed in that environment.