setup.py -> pyproject.toml #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
the current setup.py approach to creating fortran extensions is not compatible with some recent PEP standards, meaning poetry will not install it from pypi. I struggled for a few hours to find a simple way to package the fortran code into a python module for execution, and I have not yet been successful. turns out it is difficult to build fortran modules using poetry.
so i settled here on just building
.sofiles withf2pyusing themake fortraintarget, and i'll just do this manually for the current versions of python (3.9-3.11) for the two OS I have access to (linux x86, osx 64-arm). this limits use to those systems, but hopefully the linux builds are stable enough 馃し馃徎