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

Build dependencies conflict fails in Poetry #62

Open
valhuber opened this issue Jun 7, 2024 · 1 comment
Open

Build dependencies conflict fails in Poetry #62

valhuber opened this issue Jun 7, 2024 · 1 comment
Assignees

Comments

@valhuber
Copy link
Contributor

valhuber commented Jun 7, 2024

I use poetry to manage my dependencies and go the following error which prevented me from installing ApiLogicServer. I could install ApiLogicServer with pip but using poetry is my preferred option.

poetry add apilogicserver
Using version ^10.4.32 for apilogicserver

Updating dependencies
Resolving dependencies... (4.0s)

Because safrs (3.1.3) depends on Werkzeug (>=2.3.8)
and no versions of safrs match >3.1.3, safrs (>=3.1.3) requires Werkzeug (>=2.3.8).
And because apilogicserver (10.4.32) depends on both Werkzeug (2.3.3) and safrs (>=3.1.3), apilogicserver is forbidden.
So, because no versions of apilogicserver match >10.4.32,<11.0.0
and api-logic-server-samples depends on apilogicserver (^10.4.32), version solving failed.

@valhuber
Copy link
Contributor Author

valhuber commented Jun 7, 2024

Werkzeug is a safrs dependency: (Werkzeug>=2.3.8)

In als pyproject.tom, using "Werkzeug==2.3.3" makes BLT (Build, Load and Test) work, but fails to install in Poetry, as reported by customer (above).

als using Werkzeug >= 2.3.8 fails BLT.

Here's the log of BLT:

build_failure-log.txt

Here is the built venv from the BLT. Note: the pip freeze shows Werkzeug==3.0.3, presumably from safrs Werkzeug>=2.3.8

build-failure-pip-freeze.txt

I tried removing safrs dependencies from als, expecting the build process would include safrs dependencies. That also fails (a big surprise), on CORS.

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

2 participants