Implement_array_function method already has a docstring

[taiwotman]

After pip install bokeh, and using the import statement:

from bokeh.plotting import figure

I got the runtime error:

Implement_array_function method already has a docstring

Same error would occur if bokeh is downloaded while using the import statement:

from .bokeh.bokeh.plotting import figure

[bryevdv]

@taiwotman There is nothing called Implement_array_function anywhere at all in the Bokeh repo:

https://github.com/bokeh/bokeh/search?q=Implement_array_function&unscoped_q=Implement_array_function

I also can't reproduce any issue with a pip install into a clean conda env. There are ~800k pip installs of Bokeh each month with no other problems reported with basic usage. I think the most likely explanation is some problem on your local system. Do you have a "bokeh.py" module of your own any any chance?

[bryevdv]

@taiwotman actually it appears this is actually an issue with Numpy under some circumstances:

numpy/numpy#14384
numpy/numpy#14012

Accordingly, I am closing this here, and marking as upstream

It seems as though a potential workaround may be to downgrade Numpy to an 1.15.4 or earlier, but you will have to experiment.

[bryevdv]

@taiwotman I would suggest it would be helpful if you could comment on numpy/numpy#14384 with more details about how you ran in to this. Everything in that issue seems to indicate problems with numpy used in certain situations where the module is reloaded. If you can confirm or contradict that I am sure it would help the numpy devs

[taiwotman]

Thanks. Followed your guide by downgrading numpy to 1.15.4 and the error disappeared...but then got a new one: typing-extensions module not found. There after, pip install the module and voila all went well with the example Components

[bryevdv]

@taiwotman I'm not sure about the typing extensions message. We are adding typing_extensions as a new requirement starting with version 2.0 but you would only need it for 2.0 pre-releases, not any any previous full release. Perhaps some other package in your environment was trying to pull it in? In any case thanks for the update and I am glad it's now working!