Version 2.0.0: Drop support for python 3.6 and 3.7

[frank113]

Summary

This PR responds to issue #39 concerning the removal of support for Python 3.6 and 3.7. As stated in the PR the stated versions of python entered "End of Life" during the following times:

• Python 3.6: 2021-12-23
• Python 3.7: 2023-06-27

Changes Made

1. Add @frank113 to list of contributors
2. Bump major version from 1.0.0 -> 2.0.0 as per Semantic Versioning point 9.
3. Standardize typing imports as conditional imports for python>=3.8 is no longer needed
4. Update tox.ini to include py311 to match tags within setup.py
5. Update setup.py to remove install_requires and now-irrelevant tags.
6. Remove 3.7 from CI workflow

Considerations

• The assumption that py311 was needed within tox.ini to match the given tags within setup.py is an assumption on my end
• I do not feel strongly about the typing import in argparse_dataclass.py but prefer to avoid repetition of typing.<TYPE>

References

• Python EOL Chart
• Semantic Versioning

Other

The package results in a very clean interface. Thanks for starting this!

[mivade]

I've never actually been sure if dropping support for a Python version actually counts as a breaking change. I think you meant to refer to Item 8 which talks about breaking changes to the public API, not to things like what versions are supported. However I've also had issues with other libraries that I've used before where they drop support for a version of Python I'm using and only change the minor version or even the patch version which is annoying so I don't feel particularly strongly one way or another.

[mivade]

Thanks! This looks good to me overall apart from some minor changelog comments.

[mivade]

Can you change this to Unreleased and remove the date? I'll finalize updates here when I'm ready to push a release to PyPI.

[frank113]

Changes made!

[mivade]

I believe there have been some more changes since the last release but if you don't feel like checking I can handle updating this when I make the release.

[frank113]

Using commit 11cf9ef468a9f5d54d83275b9317492bf98c68ce as the starting point the following changes were as follows:

• AddTypeError for non-Optional Union typing with prompt to use custom type
• Add support for metavar in metadata
• Literal types as an alternative for fixed-choice fields
• Prevent Literal and choices collision
• Unit tests for:
  • union typing

I added the above points in CHANGELOG.md, feel free to add any that I may have missed!

[frank113]

I've never actually been sure if dropping support for a Python version actually counts as a breaking change. I think you meant to refer to Item 8 which talks about breaking changes to the public API, not to things like what versions are supported. However I've also had issues with other libraries that I've used before where they drop support for a version of Python I'm using and only change the minor version or even the patch version which is annoying so I don't feel particularly strongly one way or another.

Agreed, my thinking was to err on the side of caution and us Item 9 and increment the major version. Luckily python3.8 has EOL October 14, 2024 so we won't encounter this problem in the near future.

[mivade]

Thanks!