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

Version conflicts #179

Open
typiconman opened this issue Jul 16, 2024 · 3 comments
Open

Version conflicts #179

typiconman opened this issue Jul 16, 2024 · 3 comments

Comments

@typiconman
Copy link

typiconman commented Jul 16, 2024

Running make customize leads to the following error message:

ERROR: Cannot install -r requirements.txt (line 25), -r requirements.txt (line 30), fontbakery==0.12.8 and freetype-py==2.4.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested freetype-py==2.4.0
    diffenator2 0.4.3 depends on freetype-py
    fontbakery 0.12.8 depends on freetype-py<2.4.0
    The user requested freetype-py==2.4.0
    diffenator2 0.4.3 depends on freetype-py
    fontbakery 0.12.8 depends on freetype-py<2.4.0
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Please advise.

@guidoferreyra
Copy link

Something similar is happening to me:

The conflict is caused by:
drawbot-skia 0.5.1 depends on skia-python
drawbot-skia 0.5.0 depends on skia-python

If I remove drawbot-skia from my requirements I’m getting the following:

ERROR: Could not find a version that satisfies the requirement skia-python; extra == "skia" (from blackrenderer[skia]) (from versions: none)

@simoncozens
Copy link
Contributor

If you're on Python 3.13, we are waiting on new skia-python wheels to become available. That's why it can't install skia-python.

@guidoferreyra
Copy link

That's what I thought and I tried to use 3.11 but forgot to remove the already created venv 🤦. Thanks @simoncozens

@typiconman, you might be able to solve your problem by first removing the venv and then modifying the "venv" job in the makefile specifying an old Python version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants