Add Python 3.11 support

[br3ndonland]

Description

This PR will add Python 3.11 support to fastenv.

Changes

Code changes

• Add Python 3.11 classifier to pyproject.toml
• Add Python 3.11 to GitHub Actions workflows

Results

• fastenv will now include a Python 3.11 classifier in its PyPI package
• fastenv will now build and publish its PyPI package using Python 3.11
• fastenv will now run tests with Python 3.11, in addition to 3.8-3.10

Related

• I have reviewed the Guidelines for Contributing and the Code of Conduct.

Related projects that have released support for Python 3.11:

• HTTPX (0.23.1 - 2022-11-18)

Related projects that have not released support for Python 3.11:

• AnyIO (has not released Python 3.11 support, but is testing with Python 3.11 in development - agronholm/anyio@bd59a21)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
fastenv	✅ Ready (Inspect)	Visit Preview	Jan 6, 2023 at 1:59AM (UTC)

[sourcery-ai]

Sourcery Code Quality Report

✅  Merging this PR will increase code quality in the affected files by 0.08%.

Quality metrics	Before	After	Change
Complexity	0.49 ⭐	0.50 ⭐	0.01 👎
Method Length	75.04 🙂	74.00 🙂	-1.04 👍
Working memory	6.39 🙂	6.40 🙂	0.01 👎
Quality	79.66% ⭐	79.74% ⭐	0.08% 👍

Other metrics	Before	After	Change
Lines	786	778	-8

Changed files	Quality Before	Quality After	Quality Change
tests/test_dotenv.py	79.66% ⭐	79.74% ⭐	0.08% 👍

Here are some functions in these files that still need a tune-up:

File	Function	Complexity	Length	Working Memory	Quality	Recommendation
tests/test_dotenv.py	TestDotEnvMethods.test_load_dotenv_file_in_sub_dir	1 ⭐	124 😞	8 🙂	69.16% 🙂	Try splitting into smaller methods
tests/test_dotenv.py	TestDotEnvMethods.test_load_dotenv_files_in_sub_dirs	1 ⭐	120 😞	8 🙂	69.65% 🙂	Try splitting into smaller methods
tests/test_dotenv.py	TestDotEnvMethods.test_load_dotenv_files_in_other_dirs_no_find	1 ⭐	123 😞	7 🙂	71.63% 🙂	Try splitting into smaller methods

Legend and Explanation

The emojis denote the absolute quality of the code:

• ⭐ excellent
• 🙂 good
• 😞 poor
• ⛔ very poor

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.

---

Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Help us improve this quality report!