plotly v3.2.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date. Notes and instructions for merging this PR:

1. Please check that the dependencies have not changed.
2. Please merge the PR only after the tests have passed.
3. Feel free to push to the bot's branch to update this PR if needed.
4. The bot will almost always only open one PR per version.

_{This PR was created by the cf-regro-autotick-bot. The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues!}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[moorepants]

FYI, the changelog seems to indicate that there are new dependencies (orca and psutil). They may be optional, not quite sure.

[ocefpaf]

Argh... I will check those.

PS: that is still the bot kryptonite, we need to use conda-skeleton parsing to extract new deps and add them there.

[ocefpaf]

setup.py still lists:

      install_requires=['decorator>=4.0.6',
                        'nbformat>=4.2',
                        'pytz',
                        'requests',
                        'retrying>=1.3.3',
                        'six'],

so we are good here. Thanks for the heads up!

[moorepants]

that is still the bot kryptonite, we need to use conda-skeleton parsing to extract new deps and add them there.

Yes, would be very useful. I'm also confused on when packages include optional dependencies in the meta.yml file. Seems like some do and some don't.

[ocefpaf]

I'm also confused on when packages include optional dependencies in the meta.yml file. Seems like some do and some don't.

Up to this moment it is up to the recipe maintainers, conda-forge does not have a policy on that. It is a trade-off between a lighter package vs shipping more functionalities.

Ideally support for optional deps should live in conda so we can do things like conda install package_x[extras]. Not sure how the development is on that front but I do know there are plans to do something along those lines.