2.0.0 Wishlist

@chriddyp @Kully @cldougl

I haven’t had many cycles to play around with the python api library lately, but recently got in a little deep for https://github.com/plotly/plotly.py/pull/640, where we’ve now got fully-unified api modules.

I think enough shifted (mostly additions, but the error handling is definitely not backwards compat) that we should open up a discussion on non-minor changes that we’ve been looking to add to the plotly module. Here’s a list of topics:

• API request/response unification (https://github.com/plotly/plotly.py/pull/651)
• Fix or drop support for matplotlib
• Add numpy as an official dep. and use it to speed up the library. (#667)
• Related to above, clean up how we handle optional imports (https://github.com/plotly/plotly.py/pull/317)
• Stop auto-loading graph reference and just use packaged graph reference (https://github.com/plotly/plotly.py/pull/614)**
• Add transforms to graph objects (https://github.com/plotly/plotly.py/issues/587) holding off on this until the transforms spec settles in plotly.js.
• Add frames for graph objects (https://github.com/plotly/plotly.py/issues/604)
• Add a sign_in validation #525 (#668)
• Fix up streaming? (this might be more work than it’s worth at this point https://github.com/plotly/plotly.py/pull/253) No time for this atm.
• Some module re-organizing. Most importantly, we should move FigureFactory into it’s own sub-package and each Figure-generator should be it’s own file. The tools.py module is enormous and is a constant point of pain for circular imports (https://github.com/plotly/plotly.py/pull/652).

**In fact, if we do do this, we can just add some meta programming to auto-create a module full of all the objects from graph-reference. This way we don’t have those dump “Scatter is not defined” errors, etc.

Anything else?

[chriddyp]

Add numpy as an official dep. and use it to speed up the library.

I’m OK with using this in all of our FigureFactory methods but I’d still like to keep this as a protected import. I think there will still be new users who might have trouble installing it on their machine with their default python distribution.

[chriddyp]

yeah, I think we should keep it, albeit in a fragile state. we still have a lot of docs about it (/plot.ly/matplotlib) that are neat for people to see