Based on recommendations by @iLLiCiT I’ve re-installed the Ayon Dependencies Tool by starting off with pyenv
to manage the Python version to use. I installed: pyenv-win
.
Then did pyenv install 3.9.13
and pyenv local 3.9.13
in the Ayon Dependencies Tool folder and reinstalled through that version and running the bundle build:
.\start.ps1 install
.\start.ps1 create -b 2024.01.0-full-2024-01-17-02-roydev
But I hit the same error:
Could not parse version constraint: None
EDIT: Logging the .toml
file that ayon dependencies tool generates I can see:
[tool.poetry.dependencies]
acre = "None"
...
appdirs = "None"
By the way, I’d recommend adding -v
flag to the poetry runs of the tool + always print(toml.dumps(full_toml_data))
if an error occurred so that we can identify the culprit from the los better by default.
These seemed to come from the Launcher build that I did since it was found in its .json
file as well. Where the values were:
"acre": "file:///E:/dev/ayon-launcher/.venv/src/acre",
"appdirs": "file:///E:/dev/ayon-launcher/.venv/src/appdirs",
But should have been git+<url>
paths.
This issue seems to have to do with changes in pip
.
See: python - pip freeze creates some weird path instead of the package version - Stack Overflow
My pip version was 22.0.4
but after upgrading to 24.0
it behaved the same.
Replacing pip freeze
with pip list --format=freeze
does fix the issue - however @iLLiCiT told me he’d set up a PR with a fix.