Initial commit of pyproject-toml branch #201
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch moves much of the configuration of the cyipopt package to pyproject.toml. My motivation for this is that as currently configured, cyipopt is incompatible with poetry. Trying to do
results in an error from poetry
To fix this, I moved the dependencies (and much of the other setup information) into
pyproject.toml
. In the process, that allows deletion of theAUTHORS
,MANIFEST.in
,pytest.ini
, andrequirements.txt
files, without losing any information.In addition, it greatly simplifies the
setup.py
script, which now only has to generate the extension modules.BTW, I don't think this is just a poetry problem. In the past, I've had trouble installing cyipopt because of incompatible dependencies.
You can test that the new fork works as intended in poetry by executing
in a Python environment, or
using poetry, and then in either case running the cyipopt test suite. I've also used the new fork in a Github workflow successfully.