Support Python 3.12

[rad-pat]

With Python 3.12 the following error is encountered:

  Traceback (most recent call last):
    File "/opt/hostedtoolcache/Python/3.12.2/x64/bin/liccheck", line 5, in <module>
      from liccheck.command_line import main
    File "/opt/hostedtoolcache/Python/3.12.2/x64/lib/python3.12/site-packages/liccheck/command_line.py", line 5, in <module>
      from liccheck.requirements import parse_requirements, resolve, resolve_without_deps
    File "/opt/hostedtoolcache/Python/3.12.2/x64/lib/python3.12/site-packages/liccheck/requirements.py", line 1, in <module>
      import pkg_resources
  ModuleNotFoundError: No module named 'pkg_resources'

#114 covers the same error as a deprecation warning, but full support should be given to Python 3.12

[albertodiazdorado]

This is quite the necessary upgrade if we want to keep using liccheck.

@rad-pat do you know what changes must be done, maybe you can point me to them? Then I can try to open a PR myself.

[rad-pat]

@albertodiazdorado , according to https://docs.python.org/3/whatsnew/3.12.html, pkg_resources should be available if setuptools is installed as requirement, which is essentially what #113 is doing. I'm not sure why tests failed for that PR.

[Stigjb]

This warning suggests that relying on pkg_resources via setuptools may not be a lasting workaround. I get the warning when running liccheck in a project with Python 3.11.9 and an explicit dependency on setuptools

UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

[JanEricNitschke]

pkg_resources has been removed now from Setuptools 82: https://setuptools.pypa.io/en/stable/history.html#v82-0-0

[ml-evs]

+1 for this and the solution in #132 -- we still find liccheck really useful and would happily volunteer some time to help with maintenance, if that is the issue!

[ml-evs]

Any movement on this @dhatim? Think there's quite a few of us that would be happy to help out? Otherwise perhaps we can move to forking the repo and releasing under a different name on PyPI

[rad-pat]

FYI, I gave up on this and just used different license check approach.