-
Notifications
You must be signed in to change notification settings - Fork 0
Python Binding Packages #2
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
base: master
Are you sure you want to change the base?
Conversation
- NWX_MODULE_DIRECTORY is set correctly for all NWChemExBasePybindings-based packages - ParallelZone and PluginPlay bindings appear to be working - TensorWrapper and above are in-progress - The value of NWX_MODULE_DIRECTORY needs to be generalized to any Python version. It currently only works for Python 3.13.
|
@jwaldrop107 I think this is ready for another review. I need to check if I can build the whole thing, which will take time, but it all looks right from an surface-level check on my end. Questions/points of interest for this review:
|
jwaldrop107
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zachcran In general, LGTM. The actions should be sufficient for the time being. I would say go ahead and remove the two _package.py files.
Description
Python bindings are not currently working properly with Spack packaging. This PR works on solving that issue.
TODOs
+pythonflag correctly down the stack, sincenwchemex-tensorwrapper+pythonwas depending onnwchemex-parallelzone~pythonfor some reason.depends_on("nwchemex-parallelzone+python", when="+python").