You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,21 @@
2
2
All notable changes to this project will be documented in this file.
3
3
This project adheres to [Semantic Versioning](http://semver.org/).
4
4
5
+
## [5.18.0] - 2023-10-25
6
+
7
+
### Updated
8
+
- Updated Plotly.js from version 2.26.0 to version 2.27.0. See the [plotly.js CHANGELOG](https://github.com/plotly/plotly.js/blob/master/CHANGELOG.md#2270----2023-10-20) for more information. These changes are reflected in the auto-generated `plotly.graph_objects` module. Notable changes include:
9
+
- Add `insiderange` to cartesian axes to help avoid overlap between visible grid lines and tick labels of the counter axis when they are positioned inside [[#6735](https://github.com/plotly/plotly.js/pull/6735)], this feature was anonymously sponsored: thank you to our sponsor!
10
+
- Fix column order changes on hover [[#6718](https://github.com/plotly/plotly.js/pull/6718)],
11
+
with thanks to @bhavinpatel1109 for the contribution!
12
+
- Fix hover at timestamp '1970-01-01 00:00:00' [[#6752](https://github.com/plotly/plotly.js/pull/6752)],
13
+
with thanks to @adamjhawley for the contribution!
14
+
- Fix clearing empty `candlestick` using react [[#6757](https://github.com/plotly/plotly.js/pull/6757)]
15
+
16
+
### Fixed
17
+
- Repair crash on Matplotlib 3.8 related to get_offset_position [[#4372](https://github.com/plotly/plotly.py/pull/4372)],
18
+
- Handle deprecation of `pandas.Series.dt.to_pydatetime()` calls and suppress the `FutureWarning` they currently emit. [[#4379](https://github.com/plotly/plotly.py/pull/4379)]
Running tests with tox is much more powerful, but requires a bit more setup.
273
273
274
-
You'll need to export an environment variable for *each* tox environment you wish to test with. For example, if you want to test with `Python 2.7` and
274
+
You'll need to export an environment variable for *each* tox environment you wish to test with. For example, if you want to test with `Python 3.9` and
275
275
`Python 3.6`, but only care to check the `core` specs, you would need to ensure that the following variables are exported:
276
276
277
277
```
278
-
export PLOTLY_TOX_PYTHON_27=<python binary>
278
+
export PLOTLY_TOX_PYTHON_39=<python binary>
279
279
export PLOTLY_TOX_PYTHON_36=<python binary>
280
280
```
281
281
@@ -286,15 +286,15 @@ Where the `<python binary` is going to be specific to your development setup. As
286
286
# tox envs #
287
287
############
288
288
289
-
exportPLOTLY_TOX_PYTHON_27=python2.7
290
-
exportPLOTLY_TOX_PYTHON_34=python3.4
291
-
export TOXENV=py27-core,py34-core
289
+
exportPLOTLY_TOX_PYTHON_39=python3.9
290
+
exportPLOTLY_TOX_PYTHON_36=python3.6
291
+
export TOXENV=py39-core,py36-core
292
292
```
293
293
294
294
Where `TOXENV` is the environment list you want to use when invoking `tox` from the command line. Note that the `PLOTLY_TOX_*` pattern is used to pass in variables for use in the `tox.ini` file. Though this is a little setup, intensive, you'll get the following benefits:
295
295
296
296
*`tox` will automatically manage a virtual env for each environment you want to test in.
297
-
* You only have to run `tox` and know that the module is working in both `Python 2` and `Python 3`.
297
+
* You only have to run `tox` and know that the module is working in all included Python versions.
298
298
299
299
Finally, `tox` allows you to pass in additional command line arguments that are formatted in (by us) in the `tox.ini` file, see `{posargs}`. This is setup to help with our configuration of [pytest markers](http://doc.pytest.org/en/latest/example/markers.html), which are set up in `packages/python/plotly/pytest.ini`. To run only tests that are *not* tagged with `nodev`, you could use the following command:
You can use `insiderange` instead of `range` on an axis if you have tick labels positioned on the inside of another axis and you don't want the range to overlap with those labels.
567
+
568
+
In this example, we have a y axis with `ticklabelposition="inside"` and by setting `insiderange=['2018-10-01', '2019-01-01']` on the x axis, the data point of `2018-10-01` is displayed after the y axis labels.
Copy file name to clipboardExpand all lines: doc/unconverted/python/amazon-redshift.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,8 +45,6 @@ This notebook will go over one of the easiest ways to graph data from your [Amaz
45
45
In this notebook we'll be using [Amazon's Sample Redshift Data](http://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-create-sample-db.html) for this notebook. Although we won't be connecting through a JDBC/ODBC connection we'll be using the [psycopg2 package](http://initd.org/psycopg/docs/index.html) with [SQLAlchemy](http://www.sqlalchemy.org/) and [pandas](http://pandas.pydata.org/) to make it simple to query and analyze our data.
46
46
47
47
```python
48
-
from__future__import print_function #python 3 support
0 commit comments