0.20.0 gratuitously breaks backwards compatibility

[dhirschfeld]

PR #15998 removed the pandas.types module which AFAICT wasn't deprecated.

This breaks 3rd party libraries such as dask without giving them any warning or time to adjust to the new api.

IMHO a shim should be put in place with a deprecation warning to give 3rd party libraries a chance to adjust to the new api

[jreback]

pandas.types was never public
dask is already compat (i fixed the latest)

[dhirschfeld]

In python private modules are denoted by a leading underscore so by that definition it wasn't private and if it was supposed to be was there ever any way for anyone to be able to tell that?

[dhirschfeld]

dask is only one such library which will break without warning

[jreback]

dask has already been fixed
they explicitly relied on some unstable apis and were willing to accept the risk
anything else is not going to be deprecated
the whatsnew is very clear

[jreback]

closed by 075eca1

@dhirschfeld if you find anything pls comment / open new issue.