CLN: __all__ for core/index.py
- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] passes `black pandas`
- [ ] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

this file is not used __anywhere__ in the code base (AT ALL).
It was deprecated in #30193 (About a month ago).

Is it OK to removed it completely?

I don't know if a month is a lot of time or not when it comes to API changes, if it's not a lot of time, then what is a good time span to give users a warn about API change before actually changing it? The CI is red, I guess the objects you removed were being imported somewhere. Looks like it failed before it began the tests, closing and reopening Sorry, assumed there were genuine test fails. The failure is a correct error now, you need to either remove `_new_Index` if it's not used, or add it to the `__all__` (with a comment if possible). This is a deprecated module that is being changed, that should not be used in pandas. So what is the rationale for this change? > This is a deprecated module that is being changed, that should not be used in pandas. So what is the rationale for this change?

@jorisvandenbossche I just saw the ```# noqa:F401``` comments, and decided to cleaned it up, regardless if the module is deprecated or not. OK, I wouldn't put effort in a deprecated / unused file, but too late I guess :-)

Is there a general issue about such changes? > but too late I guess :-)

That's exactly what I said, when I saw the deprecation message... only after I have made the changes :)

> Is there a general issue about such changes?

There isn't a "master issue" for it, it's something I started to do here and there since https://github.com/pandas-dev/pandas/pull/30828#discussion_r364500688 was pointed out.
 Yea I think since deprecated maybe not even worth touching this module so just closing this one out. But thanks as always @MomIsBestFriend  Understandable :) 