Add pylibefp python bindings to upstream libefp #18
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.
Hi @slipchenko, this PR is in reasonable shape now. Sorry for the delay -- our VPN went down, so I diverted to another project for a while. I'm glad to answer any questions about the changes. Please "merge" rather than "squash and merge" this one so that the commit that copies over all the code from my repo is preserved for easier diff in case we ever need it.
I do have some other edits locally for some new capabilities, but I'm guessing Suranjan's set is more complete.
_L
means only from the library but w/o suffix means search along paths, including library. this gets rid of those psi4 specializations of flattening the library and turning off _L, so it can use an ordinary compile. also, use python pathlib module rather than the extra fns copied in from psi4-D LIBEFP_ENABLE_PYTHON=ON
when configuring the libefp build. or, build thepython/
directory later and pass-D libefp_DIR=/path/to/libefpConfig
.todo