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
Is your feature request related to a problem? Please describe.
When import cudf is called, we import a few modules/functions for setup but leave a lot of these objects in the namespace afterwards. Since we advertise cudf as a public namespace, we should only have objects that are designed to be use publicly
e.g. today you can do
In [5]: importcudfIn [6]: cudf.cupy.zeros(1)
Out[6]: array([0.])
Is your feature request related to a problem? Please describe.
When
import cudf
is called, we import a few modules/functions for setup but leave a lot of these objects in the namespace afterwards. Since we advertisecudf
as a public namespace, we should only have objects that are designed to be use publiclye.g. today you can do
pandas had a similar discussion in pandas-dev/pandas#30296
Describe the solution you'd like
Remove objects in the
cudf
namespace that are scoped to justcudf
Python and are designed to be publicI suggest
del
-ing_setup_numba
validate_setup
numba_config
cuda
cupy
rmm
rmm_cupy_allocator
RMMNumbaManager
core
clear_cache
And these objects which probably should not have public API use
dtype
BaseIndex
isclose
Describe alternatives you've considered
Status quo.
Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.
The text was updated successfully, but these errors were encountered: