Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pyproject.toml: dependency conflicts #1546

Open
dgmcdona opened this issue Jan 13, 2025 · 0 comments · May be fixed by #1548 or #1558
Open

pyproject.toml: dependency conflicts #1546

dgmcdona opened this issue Jan 13, 2025 · 0 comments · May be fixed by #1548 or #1558

Comments

@dgmcdona
Copy link
Contributor

dgmcdona commented Jan 13, 2025

I've been playing with using uv to automatically create virtual environments, install dependencies, and run the vol.py script in a single command with uv run --python 3.8.10 vol.py and it has produced some errors when attempting to resolve volatility3's dependencies.

The first issue seems to be a clear bug, which is that the sphinx doc dependency is impossible to resolve - the < and > need to be flipped since I'm assuming that we want the version to be within that range.

The second one that I know of so far is that pyinstaller 6.11.0 (our minimum pyinstaller required version) pinned pefile != 2024.8.26 due to regressions introduced in pefile: https://github.com/pyinstaller/pyinstaller/blob/ee05de897aa82abad2efe7ce2e8d45555930d5a4/doc/CHANGES.rst#pyinstaller-core

However, we have pefile as a required dependency pinned to pefile >= 2024.8.26, and 2024.8.26 is the highest available version on PyPi, which produces an unresolvable conflict.

I'll see if any others come up while attempting to resolve these.

@dgmcdona dgmcdona linked a pull request Jan 14, 2025 that will close this issue
@ikelos ikelos linked a pull request Jan 17, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants