-
Notifications
You must be signed in to change notification settings - Fork 57
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
Support PEP 517 (and thus poetry) #167
Comments
I've been looking to at cvxpy as a model for the wheel builds (#163). It is interesting to note that the conda forge build has to remove the pyproject.toml file: https://github.com/conda-forge/cvxpy-feedstock/blob/main/recipe/meta.yaml#L12 I also noticed that pip has a |
poetry has no issues installing cyipopt if the build dependencies are installed first (which is currently the standard recommended procedure in the cyipopt docs for a pip or python setup.py install). This works on Ubuntu 22.04:
|
Some issues with the above work around noted here #201 (comment) |
We now include a pyproject.toml in the source tarball on pypi. |
poetry has a strict set of flags when invoking pip. One of those is
--use-pep517
. This means that poetry fails to install cyipopt using pip because PEP 517 expects pypi available build dependencies to be specified in apyproject.toml
file. PEP 517 causes difficulties in the conda build system and various hacks are needed to delete or ignore thepyproject.toml
file and thus PEP 517 compliance.See more info in:
If we include a pyproject.toml in our source distribution then we will have to accommodate that with work arounds in our conda forge builds. If we don't include the file, then users trying to install using poetry will need a work around. We need a solution that works for both.
Here is an example error message from a poetry install command:
The text was updated successfully, but these errors were encountered: