added links to px.data and px.colors in API doc

[emmanuelle]

This PR add links to px.data and px.colors at the end of the API doc page on plotly.express.

For px.data

For px.colors, the objects which we want to list are not functions but lists, and they are not listed in an __all__ somewhere already so I figured out it would be easier to link to the corresponding doc tutorials.

In the main px page:

[nicolaskruchten]

In your screenshot it's listed as plotly.data but it's actually plotly.express.data.

[nicolaskruchten]

Re colors, can we list the submodules of plotly.express.colors like qualitative and sequential so at least people know that those are namespaces?

Maybe we could list the px.colors.named_colorscales() function?

[nicolaskruchten]

If I had a function that outputted the color scales and sequences by namespace, could we execute that function and inline the output here?

[emmanuelle]

In your screenshot it's listed as plotly.data but it's actually plotly.express.data.

So if you want it to appear as plotly.express.data, data should be a sub-package of plotly.express which it is not at the moment (ie there should be a data directory with an __init__.py). This is what I did with colors but then I had to change some imports which apparently cause problem for py 3.6. Should I create the plotly.express.data package? This would be a cleaner organization of the code.

[emmanuelle]

So this CI failure is very frustrating. I created subpackages data and colors in plotly.express in order to be able to document them in the API (and it's also a cleaner way to organize code). Everything works fine locally but on the CI build-doc build all notebooks where px is imported fail at the line 58 of the __init__.py: from . import data, colors. Everything works well on my laptop. I thought it could come from the version of python so I tried py 3.6 and 3.7 locally and both work. Any idea?

[emmanuelle]

I removed the re-direction for failed builds of notebooks because the output is full of unicode characters which are hard to read but I'll put this back.

[emmanuelle]

ok I can reproduce the error if I try to install the package with python setup.py install instead of python setup.py develop, I'll investigate from here.

[emmanuelle]

ok, silly me, it was just a question of adding the new subpackages to the packages list in setup.py. All green now!

[emmanuelle]

These changes:

• remove titles such as "List of modules" which I deemed to be verbose and not helpful.
• put the module content before the list of submodules

[emmanuelle]

I updated the screenshots above.

[emmanuelle]

ok, I hacked the Makefile to get the architecture of colors right but this make me cringe a bit. Since we have generated code in graph_objects maybe we could also generate code in colors subpackages in the future? Anyway here is the screenshot for now

[nicolaskruchten]

@jonmmease could you give these package manipulations a once-over plz? They seem fine to me but I’m always wary of breaking something :)

[jonmmease]

It all looks reasonable to me!

[nicolaskruchten]

Should be good to merge tomorrow right before the release... thanks @emmanuelle !

[emmanuelle]

I made the small requested changes, please tell me if I can merge!

[nicolaskruchten]

💃