You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In testing #13, I ran into a bug when I tried to import Imviz:
>>> from jdaviz import Imviz
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\jdaviz\__init__.py", line 11, in <module>
from jdaviz.configs.specviz import Specviz, SpecViz # noqa
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\jdaviz\configs\__init__.py", line 1, in <module>
from .cubeviz import * # noqa
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\jdaviz\configs\cubeviz\__init__.py", line 1, in <module>
from .plugins import * # noqa
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\jdaviz\configs\cubeviz\plugins\__init__.py", line 1, in <module>
from .viewers import * # noqa
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\jdaviz\configs\cubeviz\plugins\viewers.py", line 2, in <module>
from glue_jupyter.bqplot.image import BqplotImageView
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\glue_jupyter\bqplot\image\__init__.py", line 1, in <module>
from .layer_artist import * # noqa
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\glue_jupyter\bqplot\image\layer_artist.py", line 1, in <module>
import skimage.measure
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\skimage\measure\__init__.py", line 6, in <module>
from ._polygon import approximate_polygon, subdivide_polygon
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\skimage\measure\_polygon.py", line 2, in <module>
from scipy import signal
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\scipy\signal\__init__.py", line 310, in <module>
from ._peak_finding import *
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\scipy\signal\_peak_finding.py", line 8, in <module>
from scipy.stats import scoreatpercentile
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\scipy\stats\__init__.py", line 441, in <module> from .stats import *
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\scipy\stats\stats.py", line 43, in <module>
from . import distributions
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\scipy\stats\distributions.py", line 11, in <module>
from . import _discrete_distns
File "E:\STScI\gitRepos\aas239-jwebbinar\envvalidate\lib\site-packages\scipy\stats\_discrete_distns.py", line 19, in <module>
from .biasedurn import (_PyFishersNCHypergeometric,
File "biasedurn.pyx", line 1, in init scipy.stats.biasedurn
ModuleNotFoundError: No module named 'numpy.random.bit_generator'
Even though scipy 1.7.3 claims support for numpy>=1.16.5, this seems to be breaking... This was fixed when Pey Lian suggested I upgrade numpy. Is there a reason why we have numpy pinned to 1.18.5 @mustaric@eteq@orifox?
The text was updated successfully, but these errors were encountered:
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:
Specifications:
- numpy==1.18.5 -> python[version='>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.8,<3.9.0a0']
Your python: python=3.9
In testing #13, I ran into a bug when I tried to import Imviz:
Pey Lian was able to trace it down to our pre-requirement on numpy:
https://github.com/spacetelescope/aas239-jwebbinar/blob/main/00_Installation/pre-requirements.txt#L2
specifically:
https://numpy.org/doc/stable/release/1.19.0-notes.html#numpy-random-bit-generator-moved-to-numpy-random-bit-generator
This above pinning on numpy==1.18.5 seems incompatible with our scipy requirement:
https://github.com/spacetelescope/aas239-jwebbinar/blob/main/00_Installation/requirements.txt#L1
Even though scipy 1.7.3 claims support for numpy>=1.16.5, this seems to be breaking... This was fixed when Pey Lian suggested I upgrade numpy. Is there a reason why we have numpy pinned to 1.18.5 @mustaric @eteq @orifox?
The text was updated successfully, but these errors were encountered: