You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 docdependency is impossible to resolve - the < and > need to be flipped since I'm assuming that we want the version to be within that range.
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.
The text was updated successfully, but these errors were encountered:
I've been playing with using uv to automatically create virtual environments, install dependencies, and run the
vol.py
script in a single command withuv 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 inpefile
: https://github.com/pyinstaller/pyinstaller/blob/ee05de897aa82abad2efe7ce2e8d45555930d5a4/doc/CHANGES.rst#pyinstaller-coreHowever, we have
pefile
as a required dependency pinned topefile >= 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.
The text was updated successfully, but these errors were encountered: