-
Notifications
You must be signed in to change notification settings - Fork 8
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
Mac moves .dynlib to .dynlib.icloud #138
Comments
Thanks for letting us know about this, I found a temporary fix here for why the extension pops up, and how you can prevent it from happening. I'm working on a patch now, are you running an x86 (intel) or arm64 (M1, M2, etc.) chip on your mac? |
I'm running an x86 (intel) chip. |
Ok, I've pushed a patched wheel to testpypi now, if you could test it by running
and seeing if that fixes the issue, that would be great :) |
Thanks! I have followed the instructions provided and my script runs as expected with both 'libthermopack.dynlib' and its iCloud counterpart, 'libthermopack.dynlib.icloud'. |
Fantastic! Thank you for testing for us :) |
Hi! I have come across a small issue using SoaveRedlichKwong from thermopack. Occasionally, the file "libthermopack.dynlib" within the thermopack package is uploaded to iCloud. Furthermore, I have experienced difficulties when attempting to rename the file back to ".dynlib" without it being automatically moved back to ".dynlib.icloud". This issue has led to an error message stating:
AttributeError: 'SoaveRedlichKwong' object has no attribute 's_delete_eos’
.The script is running on macOS operating system, python version 3.11, using thermopack 2.2.1.
I managed to resolve the issue by accessing thermopack from the virtual environment in Finder on my Mac. From there, I could download libthermopack.dynlib from iCloud and remove the problem. It is possible to reproduce the issue by renaming the file from "libthermopack.dynlib" to "libthermopack.dynlib.icloud» in the virtual inviorment.
Let me know if you need any further information to address this issue.
The text was updated successfully, but these errors were encountered: