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
Currently not working when DASPK is not available #2070
Comments
This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days. |
I've been automatically notified that this is a stale issue now. As far as I can see, the bug is still present in the code. |
Hi @mark-pfeifle thanks for the followup! I am going to add the bug label to this so that it won't be bothered by the bot, and we will try and get toward resolving this. |
I changed the respective code line. Please pull the changes into the upstream. |
changed typo from pydas.daspk to pydas.dassl #2070
There is currently a bug in rmgpy/solver/base.pyx:
" from pydas.daspk import DASSLError as DASxError"
in one of the first code lines. This should read
" from pydas.dassl import DASSLError as DASxError"
Otherwise, if daspk is not available, the program will still try to access pydas.daspk.
This applies to the latest commit on master as of Feb 11 2021.
Best regards,
Mark
The text was updated successfully, but these errors were encountered: