fpgmaas/deptry

The functional unit tests seem to be using the wrong wheel file

Closed this issue · 0 comments

Describe the bug

Change the commands in tests/utils.py to:

        for setup_command in [
            f"pip install --find-links {deptry_directory / DEPTRY_WHEEL_DIRECTORY} deptry",
            *setup_commands,
        ]:  
            result = self.run(setup_command, check=True, cwd=self.project_path / "project")
            print(f"\ncommand: {setup_command}")
            print(result.stdout)

the output looks as follows;

command: pip install --find-links /Users/florian/git/deptry/build/functional_tests/deptry deptry
Looking in links: /Users/florian/git/deptry/build/functional_tests/deptry
Collecting deptry
  Using cached deptry-0.14.0-cp38-abi3-macosx_11_0_arm64.whl.metadata (4.7 kB)
Collecting chardet>=4.0.0 (from deptry)
  Using cached chardet-5.2.0-py3-none-any.whl.metadata (3.4 kB)
Collecting click<9,>=8.0.0 (from deptry)
  Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB)
Collecting pathspec>=0.9.0 (from deptry)
  Using cached pathspec-0.12.1-py3-none-any.whl.metadata (21 kB)
Using cached deptry-0.14.0-cp38-abi3-macosx_11_0_arm64.whl (2.1 MB)
Using cached chardet-5.2.0-py3-none-any.whl (199 kB)
Using cached click-8.1.7-py3-none-any.whl (97 kB)
Using cached pathspec-0.12.1-py3-none-any.whl (31 kB)
Installing collected packages: pathspec, click, chardet, deptry
Successfully installed chardet-5.2.0 click-8.1.7 deptry-0.14.0 pathspec-0.12.1

So it is not using the local changes. An example of where this is going wrong can be found here, where the new parameter requirements-file is not being recognized in the functional unit tests.