Did anything change in dependencies with 2.19.0 release for tox-pdm?

[mantomas]

Our tox starts to fail after 2.19.0 release and I'm wondering if there isn't some change needed also on tox-pdm side?
Here is the traceback as a result of pdm sync within the tox call:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/pdm/models/in_process/env_spec.py", line 24, in <module>
    print(json.dumps(get_current_env_spec(sys.argv[1]), indent=2))
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pdm/models/in_process/env_spec.py", line 12, in get_current_env_spec
    from dep_logic.tags import Platform
  File "/usr/local/lib/python3.11/site-packages/dep_logic/tags/__init__.py", line 2, in <module>
    from .tags import (
  File "/usr/local/lib/python3.11/site-packages/dep_logic/tags/tags.py", line 9, in <module>
    from dep_logic.specifiers.range import RangeSpecifier
  File "/usr/local/lib/python3.11/site-packages/dep_logic/specifiers/__init__.py", line 7, in <module>
    from packaging.specifiers import InvalidSpecifier as PkgInvalidSpecifier
ModuleNotFoundError: No module named 'packaging'

[frostming]

Can't reproduce, you may need to investigate why it can import dep_logic successfully but not packaging, because they are supposed to be under the same path (/usr/local/lib/python3.11/site-packages/).

[mantomas]

Ok, thanks - it might be specific to our Python image used in GitLab pipelines - I also cannot reproduce locally.

[frostming]

I fixed a path issue and released 2.19.1, try and see if the issue is gone after upgrade

[mantomas]

Nice, that was fast - tested in our pipeline and it fixes the issue 👍🏻