@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 #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 ([2.0.0] Unify API #651)
• Fix or drop support for matplotlib
• Add numpy as an official dep. and use it to speed up the library. (FF requires numpy #667)
• Related to above, clean up how we handle optional imports (Cleaner import checking #317)
• Stop auto-loading graph reference and just use packaged graph reference (Load graph reference from pkg copy of plot schema #614)**
• Add transforms to graph objects (Add support for transform graph objects #587) holding off on this until the transforms spec settles in plotly.js.
• Add frames for graph objects (Better Integrate frames into Figure #604)
• Add a sign_in validation plotly.sign_in should check authentication settings #525 (Validate signin #668)
• Fix up streaming? (this might be more work than it's worth at this point Revamp streaming #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 ([2.0.0] Relocate figure factory #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?