-
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
Interop with casatasks/casatools #251
Comments
On linux, using that last script, I get these errors:
and
|
Hey all - just wondering if anyone has had a chance to look at this? Tagging @gijzelaerr @tammojan for some visibility. |
Hi, thanks for the ping. I think trying to have both the CASA python bindings and the python-casacore python bindings to casacore is near impossible. That is due to the underlying casacore. If you load two python bindings, two casacores will be loaded, but the symbols of these two will shadow each other. If the versions are binary incompatible (which is probably the case) this will in the best case lead to segfaults, in a good case you get the error on importing. In theory this should be solvable, but on the short term we have no plans to work on this. So if you use casatools, you'd have to access the table also through casatools - or use a trick with multiple venvs or so. |
Thanks so much @tammojan. Really appreciate the feedback on this. I'll give the |
Hi there,
Apologies if this is wrong stream to report this issue. Myself and @tjgalvin have had adventures trying to install both
python-casacore
andcasatasks
/casatools
on Python 3.10. I've been testing on MacOS Apple Silicon, but @tjgalvin has had similar results on linux.First, installation with
pip
alone does not seem to work. I needed to resort to using a conda install. There are also issues withcasatasks
/casatools
and how it handlesmatplotlib
- it seems to be have been built againstmatplotlib<=3.5.1
and newer versions break.Here is summary of my first stages of installation trials with minimal conda installs:
Next I resorted to the
conda-forge
build. This can seemingly work, but the order of imports matters withcasatasks
/casatools
:The text was updated successfully, but these errors were encountered: