-
Notifications
You must be signed in to change notification settings - Fork 45
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
xpa module conflicts with pyds9 #122
Comments
@olebole can you comment further on how the xpa module conflicts with imexam? The xpa C code is a submodule of imexam, imexam uses a cython wrapper to access it's functions and interface with DS9. pyds9 (last time I looked) used ctypes for it's interface. While the two packages do have overlap, imexam provides a library of methods that help examine and plot images, not just provide access into the xpa ds9 functions. I haven't seen an issue with installing both packages on the same machine, could you give me an example of where or how this is failing for you? thanks! |
I did take a quick look at the bug report you listed, but I don't see anything there that would lead me to believe that having imexam installed in the environment would conflict with importing pyds9. Maybe there's a script install somewhere that's clobbering between the two packages ... I haven't investigated it on my machine yet, but I'll give it a go this afternoon. |
I can confirm the bug; when I installed imexam and pyds9, then I get the following when running:
I think this is because |
yah, lemme check that out.. |
In pyds9 version <= 1.8.1, pyds9.py and xpa.py got installed at the |
We also ran into this, but it appears to be fixed with |
PS. Putting a module named |
true. |
Original bug (Ubuntu): https://bugs.launchpad.net/bugs/1733352
Imexam does not play together with pyds9. While both have overlapping use cases, it may be good that a user has the opportunity to install and use them in parallel. One way could be to make the package a subpackage of imexam, another to agree on a common xpa package.
See also ericmandel/pyds9#58 for the pyds9 issue.
The text was updated successfully, but these errors were encountered: