Repository navigation
PlotPy 2.12.0 - #79
Merged
Merged
Conversation
Cross-section panels kept one curve for every image ever shown, so plots with hundreds of hidden images became progressively slower to refresh. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…item list Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Every new image item recomputed its 1024-entry lookup table (and the 256-color table) in Python, twice, even for the colormap used by all the other images. Tables are now cached by colormap content, inversion and alpha settings, so that an edited colormap still gets a new table. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… builds Read the Docs installs dependencies from PyPI only, so documentation builds of development branches and pull requests fail as soon as PlotPy requires a guidata or PythonQwt version that is not released yet. Add a pre_install step mirroring the GitHub Actions test workflows: for branch and pull request builds, guidata is installed from its develop branch and PythonQwt from master. Tag builds and the master branch keep using PyPI releases. The script is shared with Sigima and SigimaX; only its project-specific settings differ. Assisted-by: Claude Opus 5.5
Install development dependencies for Read the Docs dev builds
Refs #74 Assisted-by: GPT-6.1 Sol
chore: require Python 3.10 or newer
… range The slider position was computed without clipping, so a fitted value far outside the [min, max] range of its parameter (unconstrained optimization methods) exceeded the 32-bit range of QSlider.setValue: OverflowError, slider signals left blocked and following parameters not updated. Non-finite values, empty ranges and log scale values below min - 1 raised similar errors. - Clip the slider position to the slider range, using the inverse mapping of slider_value_changed, and skip undefined positions - Restore the slider signal-blocking state in a finally clause - Show a warning icon with a tooltip when the value is outside the range - Reject non-finite values typed in the parameter field - Require at least 2 slider steps in the parameter properties dialog Fixes #76 (cherry picked from commit b38c0a4) Assisted-by: Claude Opus 5.5
(cherry picked from commit fbf22fd) Assisted-by: Claude Opus 5.5
The entry was flagged as fuzzy, so it was left out of the compiled catalog and "Polygon" was shown untranslated in the French interface. Assisted-by: Claude Opus 5.5
PlotPy 2.11.2 is not released: its changes, together with the Python 3.10 requirement, are now part of PlotPy 2.12.0. Assisted-by: Claude Opus 5.5
Prepare PlotPy 2.12.0 release
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release PlotPy 2.12.0:
developbecomesmaster.master(v2.11.1) andreleasehave no content that is not already indevelop: the hotfix merged inrelease(#77) has already been ported todevelop, and the only otherreleasecommit (CI for Python 3.9) is obsolete since Python 3.10 is now required. The result of this merge is therefore exactly thedeveloptree.See release notes.