-
Notifications
You must be signed in to change notification settings - Fork 22
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
Possibly numpy2.0 issue? #334
Comments
I should say that the error is not when i run python code, just when I load.
|
Good to see you here @sgosline ! We actually have a fix for this issue in the upcoming release which should be coming out very soon Hopefully next 2 weeks. Sorry about that! |
Thanks @thomasyu888 I'm glad I'm not hallucinating. I tried loading packages in all sorts of orders. Thanks for letting me know. |
Thanks for flagging @sgosline . To resolve the issue, please pin Numpy to version 1.24.4. As Tom said, we already had a fix that would be included in the upcoming release. |
Sorry I wasn’t clear in my original post. The above problem exists when i fixed my numpy version, which is why the issue is so confounding.
On Jul 15, 2024, at 11:30 AM, Dan Lu ***@***.***> wrote:
Check twice before you click! This email originated from outside PNNL.
Thanks for flagging @sgosline<https://github.com/sgosline> . To resolve the issue, please pin Numpy to version 1.24.4. As Tom said, we already had a fix that would be included in the upcoming release.
—
Reply to this email directly, view it on GitHub<#334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAODEORU6F3VLHBDEOYHUM3ZMQIKRAVCNFSM6AAAAABKXZDPHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRZGEZTAMRWGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The newer release should available soon, but it is in staging if you wanted to take a look.
|
OK, i'll wait until it's stable, then update my docker images. I dont want the images to point to staging.... |
Thanks for the wait @sgosline . The new version of synapser should be available for you to install and should also work with the newer versions of R (4.4.1), let us know if you run into any issues. |
Operating system
Docker container running - r-base:4.3.2 (so, ubuntu, but docker is running on Mac)
Description of the problem
When I load
synapser
and thenreticulate
, I get an error trying to use reticulate that looks a lot like the numpy2.0 compatibility issue that just came out:However, when I run the same command without loading
synapser
, I get no such error.Expected behavior
My docker container build explicitly calls out numpy==1.26.4, so I should get no error. My only suspicion is that
synapser
causes another numpy to be loaded.Actual behavior
However, when I load synapser I get an error, suggesting that numpy2.0 is being installed somewhere.
Output of
sessionInfo()
The text was updated successfully, but these errors were encountered: