-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
MMGBSA.py can not find 'alamdcrd' module #84
Comments
From my humble investigation, 'from alamdcrd import' is a Python 2 style code for importing from same package, which may not work with an egg distribution. Therefore:
from alamdcrd import MutantMdcrd, GlyMutantMdcrd to from MMPBSA_mods.alamdcrd import MutantMdcrd, GlyMutantMdcrd
pip install .
|
@dacase, in case you are tracking this in the ambertools repo! |
I will pass this on to Jason Swails, and it looks like we may be able to push an update to AmberTools22. Not sure why this doesn't always fail, however. Our source code builds don't see this problem -- it may have something to do with how egg files are used (if at all) -- this is way beyond my understanding, however. In my view, this should not prevent a conda release for AmberTools22. If the above patch works, we can release an update to AmberTools22.1 to fix things. But few people will use the particular option being tested here. So: explicitly: is it possible to create a package with the current codes? Or even with the above fix? Our web site, https://ambermd.org/GetAmber.php asks people to ...thanks...dac |
2to3 was supposed to fix this. The source code in AmberTools 23 has made 2to3 replacement permanent (rather than a build-time activity). |
Solution to issue cannot be found in the documentation.
Issue
$ conda create -n test -c conda-forge ambertools
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: