Vyas Ramasubramani
Vyas Ramasubramani
Sure! A simple import on the CLI shows this: ``` ❯ time python -c "import cupy" python -c "import cupy" 0.58s user 0.09s system 75% cpu 0.888 total ❯ time...
I put together and experimental branch to investigate how much cupy is currently using cupyx by trying to move all imports to be functional-local in https://github.com/cupy/cupy/pull/9338. I also went ahead...
Once #9338 is merged we can revisit this issue. Here were a couple of ideas @leofang proposed to me offline for how we could actually remove cupyx imports from cupy...
I think it would be nice to remove the optional dependency as well, but I don't know how feasible that is. I'll defer to the cupy devs on that.
cf. https://github.com/cython/cython/issues/5855 Similar issues, although whether the specific limitation is sys.meta_path or sys.path_hooks related depends on your build backend and how it implements editable installs.
The failure I see here looks like https://github.com/pytest-dev/pytest-cov/issues/693 (cf. https://github.com/pytest-dev/pytest-xdist/issues/1211).
I resolved the above issue by ignoring one error. The other failure looks to be due to our testing of the streaming executor for cudf-polars using dask in some way...
One of the remaining issues is that it seems like more recent versions of pytest are making it harder to guarantee that the current path is not added to sys.path....
After some offline discussion I added a few extra tests to the list of expected failures for pandas. It seems likely that the pandas version we are currently using has...
This PR needs some conflict resolution.