Mojtaba Samimi

@fredricj FYI - I added this PR to our `v2.35.0` milestone. Let's try to make it to the finish line. Please fetch `upstream/master` and merge it into this branch to...

The traces in the codepens have transparency. @alexcjohnson do you this may be the expected behavior or a bug?

Great PR. Thanks @LiamConnors for all this. :medal_sports: :trophy: :star2: I suggest we set status of this PR to `on hold` as we did for https://github.com/plotly/plotly.js/pull/7015 and don't merge it....

Here is a list of doc files that has `mapbox` in their name: ``` ./doc/python/mapbox-county-choropleth.md ./doc/python/mapbox-layers.md ./doc/python/filled-area-on-mapbox.md ./doc/python/mapbox-density-heatmaps.md ./doc/python/lines-on-mapbox.md ./doc/python/scattermapbox.md ./doc/python/hexbin-mapbox.md ```

Yes we could keep mapbox names in this PR. But for the other one we want to merge those should be renamed as we need to keep doc for mapbox...

IMHO, for a while we need to keep mapbox examples until they could use the next plotly.py version in their systems. @ndrezn @emilykl @gvwilson

Also having two versions (mapbox and new map) on two doc files, could help everyone see the difference between the two.

There is also `hexbin_mapbox` in `figure_factory` at `packages/python/plotly/plotly/figure_factory/_hexbin_mapbox.py`. We should possibly add `hexbin_map`. No?

cc: [birkskyum](https://github.com/birkskyum)

> Is it possible to add a deprecation warning for Mapbox traces similar to [plotly/plotly.js#7087](https://github.com/plotly/plotly.js/pull/7087), but in this case have it appear in the Python console _in addition to_ in...