pyviewarr 0.3.1__tar.gz → 0.3.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/PKG-INFO +23 -2
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/README.md +22 -1
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/pyproject.toml +1 -1
- pyviewarr-0.3.2/src/pyviewarr/static/widget.js +48 -0
- pyviewarr-0.3.1/src/pyviewarr/static/widget.js +0 -48
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/.gitignore +0 -0
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/LICENSE +0 -0
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/src/pyviewarr/__init__.py +0 -0
- {pyviewarr-0.3.1 → pyviewarr-0.3.2}/src/pyviewarr/static/widget.css +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: pyviewarr
|
|
3
|
-
Version: 0.3.
|
|
3
|
+
Version: 0.3.2
|
|
4
4
|
License-File: LICENSE
|
|
5
5
|
Requires-Python: >=3.10
|
|
6
6
|
Requires-Dist: anywidget<0.10,>=0.9
|
|
@@ -240,11 +240,32 @@ The test server uses `tests/e2e/jupyter_server_config.py`, which enables Galata'
|
|
|
240
240
|
|
|
241
241
|
Note that `viewarr/` submodule changes will need to be committed and pushed first, then the submodule reference in this repository can be updated.
|
|
242
242
|
|
|
243
|
+
Release checklist:
|
|
244
|
+
|
|
245
|
+
1. Update changelog entries and set `[project].version` in `pyproject.toml` to the release version (e.g. `0.3.2`), then commit.
|
|
246
|
+
2. Create the Git tag/release for that version (e.g. `v0.3.2`).
|
|
247
|
+
3. Immediately after release, bump `pyproject.toml` to the next development version (e.g. `0.3.3dev`) and commit.
|
|
248
|
+
|
|
243
249
|
GitHub releases are automatically pushed to PyPI by the workflow in [`.github/workflows/ci.yml`](./.github/workflows/ci.yml).
|
|
244
250
|
|
|
245
251
|
## Changelog
|
|
246
252
|
|
|
247
|
-
### Unreleased (since `v0.3.
|
|
253
|
+
### Unreleased (since `v0.3.2`)
|
|
254
|
+
|
|
255
|
+
- No unreleased changes yet.
|
|
256
|
+
|
|
257
|
+
### `v0.3.2`
|
|
258
|
+
|
|
259
|
+
#### pyviewarr changes
|
|
260
|
+
|
|
261
|
+
- Updated bundled `viewarr` submodule from `3797ee7` to `cc78498`.
|
|
262
|
+
|
|
263
|
+
#### Included `viewarr` changes
|
|
264
|
+
|
|
265
|
+
- Fixed diverging/symmetric colorbar limit behavior so `vmax` is the only editable limit, coerced positive, and `vmin` is displayed as `-vmax` in that mode.
|
|
266
|
+
- Fixed state callback / `getValueRange()` limit reporting in diverging/symmetric mode to reflect the effective displayed range.
|
|
267
|
+
|
|
268
|
+
### `v0.3.1`
|
|
248
269
|
|
|
249
270
|
#### pyviewarr changes
|
|
250
271
|
|
|
@@ -226,11 +226,32 @@ The test server uses `tests/e2e/jupyter_server_config.py`, which enables Galata'
|
|
|
226
226
|
|
|
227
227
|
Note that `viewarr/` submodule changes will need to be committed and pushed first, then the submodule reference in this repository can be updated.
|
|
228
228
|
|
|
229
|
+
Release checklist:
|
|
230
|
+
|
|
231
|
+
1. Update changelog entries and set `[project].version` in `pyproject.toml` to the release version (e.g. `0.3.2`), then commit.
|
|
232
|
+
2. Create the Git tag/release for that version (e.g. `v0.3.2`).
|
|
233
|
+
3. Immediately after release, bump `pyproject.toml` to the next development version (e.g. `0.3.3dev`) and commit.
|
|
234
|
+
|
|
229
235
|
GitHub releases are automatically pushed to PyPI by the workflow in [`.github/workflows/ci.yml`](./.github/workflows/ci.yml).
|
|
230
236
|
|
|
231
237
|
## Changelog
|
|
232
238
|
|
|
233
|
-
### Unreleased (since `v0.3.
|
|
239
|
+
### Unreleased (since `v0.3.2`)
|
|
240
|
+
|
|
241
|
+
- No unreleased changes yet.
|
|
242
|
+
|
|
243
|
+
### `v0.3.2`
|
|
244
|
+
|
|
245
|
+
#### pyviewarr changes
|
|
246
|
+
|
|
247
|
+
- Updated bundled `viewarr` submodule from `3797ee7` to `cc78498`.
|
|
248
|
+
|
|
249
|
+
#### Included `viewarr` changes
|
|
250
|
+
|
|
251
|
+
- Fixed diverging/symmetric colorbar limit behavior so `vmax` is the only editable limit, coerced positive, and `vmin` is displayed as `-vmax` in that mode.
|
|
252
|
+
- Fixed state callback / `getValueRange()` limit reporting in diverging/symmetric mode to reflect the effective displayed range.
|
|
253
|
+
|
|
254
|
+
### `v0.3.1`
|
|
234
255
|
|
|
235
256
|
#### pyviewarr changes
|
|
236
257
|
|