PlotPy 2.8.2__tar.gz → 2.8.4__tar.gz

{plotpy-2.8.2 → plotpy-2.8.4}/MANIFEST.in

@@ -3,5 +3,4 @@ graft qtdesigner
 graft src
 graft colormaps
 include *.desktop
-include CHANGELOG.md
 include requirements.txt

{plotpy-2.8.2/PlotPy.egg-info → plotpy-2.8.4}/PKG-INFO

@@ -1,9 +1,38 @@
 Metadata-Version: 2.4
 Name: PlotPy
-Version: 2.8.2
+Version: 2.8.4
 Summary: Curve and image plotting tools for Python/Qt applications
 Author-email: Codra <p.raybaut@codra.fr>
-License-Expression: BSD-3-Clause
+License: BSD 3-Clause License
+        
+        Copyright (c) 2023, CEA-Codra, Pierre Raybaut.
+        All rights reserved.
+        
+        Redistribution and use in source and binary forms, with or without
+        modification, are permitted provided that the following conditions are met:
+        
+        1. Redistributions of source code must retain the above copyright notice, this
+           list of conditions and the following disclaimer.
+        
+        2. Redistributions in binary form must reproduce the above copyright notice,
+           this list of conditions and the following disclaimer in the documentation
+           and/or other materials provided with the distribution.
+        
+        3. Neither the name of the copyright holder nor the names of its
+           contributors may be used to endorse or promote products derived from
+           this software without specific prior written permission.
+        
+        THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+        AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+        IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+        DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+        FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+        DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+        SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+        CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+        OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+        OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+        
 Project-URL: Homepage, https://github.com/PlotPyStack/plotpy/
 Project-URL: Documentation, https://plotpy.readthedocs.io/en/latest/
 Classifier: Development Status :: 5 - Production/Stable
@@ -21,6 +50,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Classifier: Topic :: Scientific/Engineering :: Image Processing
 Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
@@ -32,7 +62,7 @@ Classifier: Topic :: Utilities
 Requires-Python: <4,>=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: guidata>=3.13
+Requires-Dist: guidata>=3.14.1
 Requires-Dist: PythonQwt>=0.15
 Requires-Dist: numpy>=1.22
 Requires-Dist: SciPy>=1.7.3
@@ -49,6 +79,8 @@ Requires-Dist: Cython>=3.0; extra == "dev"
 Requires-Dist: pylint; extra == "dev"
 Requires-Dist: ruff; extra == "dev"
 Requires-Dist: pre-commit; extra == "dev"
+Requires-Dist: setuptools; extra == "dev"
+Requires-Dist: wheel; extra == "dev"
 Provides-Extra: doc
 Requires-Dist: sphinx; extra == "doc"
 Requires-Dist: myst_parser; extra == "doc"
@@ -85,7 +117,7 @@ It is part of the [PlotPyStack](https://github.com/PlotPyStack) project, aiming
 
 <img src="https://raw.githubusercontent.com/PlotPyStack/plotpy/master/doc/images/panorama.png">
 
-See [documentation](https://plotpy.readthedocs.io/en/latest/) for more details on the library and [changelog](https://github.com/PlotPyStack/PlotPy/blob/master/CHANGELOG.md) for recent history of changes.
+See [documentation](https://plotpy.readthedocs.io/en/latest/) for more details on the library.
 
 Copyrights and licensing:
 
@@ -129,8 +161,8 @@ Compatibility table:
 
 | PlotPy version | PyQt5 | PyQt6 | PySide2 | PySide6 |
 |----------------|-------|-------|---------|---------|
-| 2.0-2.5        | ✅    | ⚠️    | ❌     | ⚠️      |
-| Latest         | ✅    | ✅    | ❌     | ✅      |
+| 2.0-2.5        | ✅    | ⚠️    | ❌      | ⚠️      |
+| Latest         | ✅    | ✅    | ❌      | ✅      |
 
 ### Other dependencies and installation
 

{plotpy-2.8.2 → plotpy-2.8.4/PlotPy.egg-info}/PKG-INFO

@@ -1,9 +1,38 @@
 Metadata-Version: 2.4
 Name: PlotPy
-Version: 2.8.2
+Version: 2.8.4
 Summary: Curve and image plotting tools for Python/Qt applications
 Author-email: Codra <p.raybaut@codra.fr>
-License-Expression: BSD-3-Clause
+License: BSD 3-Clause License
+        
+        Copyright (c) 2023, CEA-Codra, Pierre Raybaut.
+        All rights reserved.
+        
+        Redistribution and use in source and binary forms, with or without
+        modification, are permitted provided that the following conditions are met:
+        
+        1. Redistributions of source code must retain the above copyright notice, this
+           list of conditions and the following disclaimer.
+        
+        2. Redistributions in binary form must reproduce the above copyright notice,
+           this list of conditions and the following disclaimer in the documentation
+           and/or other materials provided with the distribution.
+        
+        3. Neither the name of the copyright holder nor the names of its
+           contributors may be used to endorse or promote products derived from
+           this software without specific prior written permission.
+        
+        THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+        AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+        IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+        DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+        FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+        DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+        SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+        CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+        OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+        OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+        
 Project-URL: Homepage, https://github.com/PlotPyStack/plotpy/
 Project-URL: Documentation, https://plotpy.readthedocs.io/en/latest/
 Classifier: Development Status :: 5 - Production/Stable
@@ -21,6 +50,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Classifier: Topic :: Scientific/Engineering :: Image Processing
 Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
@@ -32,7 +62,7 @@ Classifier: Topic :: Utilities
 Requires-Python: <4,>=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: guidata>=3.13
+Requires-Dist: guidata>=3.14.1
 Requires-Dist: PythonQwt>=0.15
 Requires-Dist: numpy>=1.22
 Requires-Dist: SciPy>=1.7.3
@@ -49,6 +79,8 @@ Requires-Dist: Cython>=3.0; extra == "dev"
 Requires-Dist: pylint; extra == "dev"
 Requires-Dist: ruff; extra == "dev"
 Requires-Dist: pre-commit; extra == "dev"
+Requires-Dist: setuptools; extra == "dev"
+Requires-Dist: wheel; extra == "dev"
 Provides-Extra: doc
 Requires-Dist: sphinx; extra == "doc"
 Requires-Dist: myst_parser; extra == "doc"
@@ -85,7 +117,7 @@ It is part of the [PlotPyStack](https://github.com/PlotPyStack) project, aiming
 
 <img src="https://raw.githubusercontent.com/PlotPyStack/plotpy/master/doc/images/panorama.png">
 
-See [documentation](https://plotpy.readthedocs.io/en/latest/) for more details on the library and [changelog](https://github.com/PlotPyStack/PlotPy/blob/master/CHANGELOG.md) for recent history of changes.
+See [documentation](https://plotpy.readthedocs.io/en/latest/) for more details on the library.
 
 Copyrights and licensing:
 
@@ -129,8 +161,8 @@ Compatibility table:
 
 | PlotPy version | PyQt5 | PyQt6 | PySide2 | PySide6 |
 |----------------|-------|-------|---------|---------|
-| 2.0-2.5        | ✅    | ⚠️    | ❌     | ⚠️      |
-| Latest         | ✅    | ✅    | ❌     | ✅      |
+| 2.0-2.5        | ✅    | ⚠️    | ❌      | ⚠️      |
+| Latest         | ✅    | ✅    | ❌      | ✅      |
 
 ### Other dependencies and installation
 

{plotpy-2.8.2 → plotpy-2.8.4}/PlotPy.egg-info/SOURCES.txt

@@ -1,4 +1,3 @@
-CHANGELOG.md
 LICENSE
 MANIFEST.in
 README.md
@@ -20,13 +19,13 @@ colormaps/README.md
 colormaps/_cm.py
 colormaps/colormap.py
 colormaps/matplotlib_cmaps.py
-doc/changelog.rst
 doc/conf.py
 doc/index.rst
 doc/requirements.rst
 doc/_static/favicon.ico
 doc/dev/build.rst
 doc/dev/contribute.rst
+doc/dev/gitworkflow.rst
 doc/dev/guiqwt_to_plotpy.csv
 doc/dev/guiqwt_to_plotpy.rst
 doc/dev/index.rst
@@ -107,6 +106,16 @@ doc/intro/installation.rst
 doc/intro/licenses.rst
 doc/intro/motivation.rst
 doc/intro/overview.rst
+doc/release_notes/index.rst
+doc/release_notes/release_2.00.md
+doc/release_notes/release_2.01.md
+doc/release_notes/release_2.02.md
+doc/release_notes/release_2.03.md
+doc/release_notes/release_2.04.md
+doc/release_notes/release_2.05.md
+doc/release_notes/release_2.06.md
+doc/release_notes/release_2.07.md
+doc/release_notes/release_2.08.md
 plotpy/__init__.py
 plotpy/config.py
 plotpy/constants.py
@@ -372,6 +381,7 @@ plotpy/tests/data.py
 plotpy/tests/vistools.py
 plotpy/tests/benchmarks/__init__.py
 plotpy/tests/benchmarks/test_benchmarks.py
+plotpy/tests/benchmarks/test_bigcurves.py
 plotpy/tests/benchmarks/test_bigimages.py
 plotpy/tests/benchmarks/test_large_number_of_annotations.py
 plotpy/tests/benchmarks/test_loadtest.py
@@ -417,6 +427,7 @@ plotpy/tests/items/test_curves_highdpi.py
 plotpy/tests/items/test_hist2d.py
 plotpy/tests/items/test_histogram.py
 plotpy/tests/items/test_image.py
+plotpy/tests/items/test_image_aspect_ratio.py
 plotpy/tests/items/test_image_contour.py
 plotpy/tests/items/test_image_masked.py
 plotpy/tests/items/test_image_masked_xy.py
@@ -426,6 +437,7 @@ plotpy/tests/items/test_mandelbrot.py
 plotpy/tests/items/test_pcolor.py
 plotpy/tests/items/test_polygons.py
 plotpy/tests/items/test_svgshapes.py
+plotpy/tests/items/test_to_bins.py
 plotpy/tests/items/test_transform.py
 plotpy/tests/tools/__init__.py
 plotpy/tests/tools/test_actiontool.py

{plotpy-2.8.2 → plotpy-2.8.4}/PlotPy.egg-info/requires.txt

@@ -1,4 +1,4 @@
-guidata>=3.13
+guidata>=3.14.1
 PythonQwt>=0.15
 numpy>=1.22
 SciPy>=1.7.3
@@ -14,6 +14,8 @@ Cython>=3.0
 pylint
 ruff
 pre-commit
+setuptools
+wheel
 
 [doc]
 sphinx

{plotpy-2.8.2 → plotpy-2.8.4}/README.md

@@ -23,7 +23,7 @@ It is part of the [PlotPyStack](https://github.com/PlotPyStack) project, aiming
 
 <img src="https://raw.githubusercontent.com/PlotPyStack/plotpy/master/doc/images/panorama.png">
 
-See [documentation](https://plotpy.readthedocs.io/en/latest/) for more details on the library and [changelog](https://github.com/PlotPyStack/PlotPy/blob/master/CHANGELOG.md) for recent history of changes.
+See [documentation](https://plotpy.readthedocs.io/en/latest/) for more details on the library.
 
 Copyrights and licensing:
 
@@ -67,8 +67,8 @@ Compatibility table:
 
 | PlotPy version | PyQt5 | PyQt6 | PySide2 | PySide6 |
 |----------------|-------|-------|---------|---------|
-| 2.0-2.5        | ✅    | ⚠️    | ❌     | ⚠️      |
-| Latest         | ✅    | ✅    | ❌     | ✅      |
+| 2.0-2.5        | ✅    | ⚠️    | ❌      | ⚠️      |
+| Latest         | ✅    | ✅    | ❌      | ✅      |
 
 ### Other dependencies and installation
 

plotpy-2.8.4/doc/dev/gitworkflow.rst

@@ -0,0 +1,311 @@
+.. _gitworkflow:
+
+Git Workflow
+============
+
+This document describes the Git workflow used in the PlotPy project,
+based on a ``master`` branch, a ``develop`` branch, and feature-specific branches.
+It also defines how bug fixes are managed.
+
+.. note::
+
+      This workflow is a simplified version of the `Gitflow Workflow <https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow>`_.
+      It has been adapted to suit the needs of the PlotPy project at the current stage of development.
+
+Branching Model
+---------------
+
+Main Branches
+^^^^^^^^^^^^^
+
+- ``master``: Represents the stable, production-ready version of the project.
+- ``develop``: Used for ongoing development and integration of new features.
+
+Feature Branches
+^^^^^^^^^^^^^^^^
+
+- ``feature/feature_name``: Used for the development of new features.
+
+  - Created from ``develop``.
+  - Merged back into ``develop`` once completed.
+  - Deleted after merging.
+
+Release Branch
+^^^^^^^^^^^^^^
+
+- ``release``: Represents the current maintenance line for patch releases.
+
+  - Created from ``master`` after a stable release when the first patch is needed.
+  - Accepts ``fix/xxx`` and ``hotfix/xxx`` branch merges.
+  - Merged back into ``master`` for each patch release tag (e.g., 2.8.1, 2.8.2).
+  - Reset or recreated when starting a new minor/major release cycle.
+
+.. note::
+
+      The ``release`` branch is not versioned (no ``release/2.8.x``). It always
+      represents "the current maintenance line." When a new minor version is released
+      (e.g., 2.9.0), the old ``release`` branch is deleted and a new one is created
+      from the fresh tag when the first patch for 2.9.1 is needed.
+
+Bug Fix Branches
+^^^^^^^^^^^^^^^^
+
+- ``fix/xxx``: Used for general bug fixes that are not urgent.
+
+  - Created from ``develop`` (for next feature release) or ``release`` (for patch release).
+  - Merged back into the originating branch once completed.
+  - Deleted after merging.
+
+- ``hotfix/xxx``: Used for urgent production-critical fixes.
+
+  - Created from ``release`` (if exists) or ``master`` (if no ``release`` branch yet).
+  - Merged back into ``release`` or ``master``.
+  - The fix is then cherry-picked into ``develop``.
+  - Deleted after merging.
+
+.. note::
+
+      Hotfixes (high-priority fixes) will be integrated in the next maintenance
+      release (X.Y.Z -> Z+1), while fixes (low-priority fixes) will be integrated
+      in the next feature release (X.Y -> Y+1).
+
+
+Documentation Branches
+----------------------
+
+When working on documentation that is not related to source code
+(e.g. training materials, user guides), branches should be named
+using the ``doc/`` prefix.
+
+Examples:
+
+- ``doc/training-materials``
+- ``doc/user-guide``
+
+This naming convention improves clarity by clearly separating
+documentation efforts from code-related development (features, fixes, etc.).
+
+
+Workflow for New Features
+-------------------------
+
+1. Create a new feature branch from ``develop``:
+
+   .. code-block:: sh
+
+         git checkout develop
+         git checkout -b develop/feature_name
+
+2. Develop the feature and commit changes.
+
+3. Merge the feature branch back into ``develop``:
+
+   .. code-block:: sh
+
+         git checkout develop
+         git merge --no-ff develop/feature_name
+
+4. Delete the feature branch:
+
+   .. code-block:: sh
+
+         git branch -d develop/feature_name
+
+.. warning::
+
+      Do not leave feature branches unmerged for too long.
+      Regularly rebase them on ``develop`` to minimize conflicts.
+
+Workflow for Regular Bug Fixes
+------------------------------
+
+For next feature release (target: ``develop``):
+
+1. Create a bug fix branch from ``develop``:
+
+   .. code-block:: sh
+
+         git checkout develop
+         git checkout -b fix/bug_description
+
+2. Apply the fix and commit changes.
+
+3. Merge the fix branch back into ``develop``:
+
+   .. code-block:: sh
+
+         git checkout develop
+         git merge --no-ff fix/bug_description
+
+4. Delete the fix branch:
+
+   .. code-block:: sh
+
+         git branch -d fix/bug_description
+
+For current maintenance release (target: ``release``):
+
+1. Create a bug fix branch from ``release``:
+
+   .. code-block:: sh
+
+         git checkout release
+         git checkout -b fix/bug_description
+
+2. Apply the fix and commit changes.
+
+3. Merge the fix branch back into ``release``:
+
+   .. code-block:: sh
+
+         git checkout release
+         git merge --no-ff fix/bug_description
+
+4. Delete the fix branch:
+
+   .. code-block:: sh
+
+         git branch -d fix/bug_description
+
+.. warning::
+
+      Do not create a ``fix/xxx`` branch from a ``develop/feature_name`` branch.
+      Always branch from ``develop`` or ``release`` to ensure fixes are correctly propagated.
+
+      .. code-block:: sh
+
+            # Incorrect:
+            git checkout develop/feature_name
+            git checkout -b fix/wrong_branch
+
+      .. code-block:: sh
+
+            # Correct:
+            git checkout develop
+            git checkout -b fix/correct_branch
+
+Workflow for Critical Hotfixes
+------------------------------
+
+1. Create a hotfix branch from ``release`` (or ``master`` if no ``release`` branch exists):
+
+   .. code-block:: sh
+
+         git checkout release  # or: git checkout master
+         git checkout -b hotfix/critical_bug
+
+2. Apply the fix and commit changes.
+
+3. Merge the fix back into ``release`` (or ``master``):
+
+   .. code-block:: sh
+
+         git checkout release  # or: git checkout master
+         git merge --no-ff hotfix/critical_bug
+
+4. Cherry-pick the fix into ``develop``:
+
+   .. code-block:: sh
+
+         git checkout develop
+         git cherry-pick <commit_hash>
+
+5. Delete the hotfix branch:
+
+   .. code-block:: sh
+
+         git branch -d hotfix/critical_bug
+
+.. warning::
+
+      Do not merge ``fix/xxx`` or ``hotfix/xxx`` directly into ``master`` without following the workflow.
+      Ensure hotfixes are cherry-picked into ``develop`` to avoid losing fixes in future releases.
+
+Workflow for Patch Releases
+----------------------------
+
+When ready to release a patch version (e.g., 2.8.1, 2.8.2):
+
+1. Ensure the ``release`` branch contains all desired fixes.
+
+2. Merge ``release`` into ``master``:
+
+   .. code-block:: sh
+
+         git checkout master
+         git merge --no-ff release
+
+3. Tag the release on ``master``:
+
+   .. code-block:: sh
+
+         git tag -a v2.8.1 -m "Release version 2.8.1"
+         git push origin master --tags
+
+4. Keep the ``release`` branch for additional patches in the same minor version series.
+
+Workflow for Minor/Major Releases
+----------------------------------
+
+When ready to release a new minor or major version (e.g., 2.9.0, 3.0.0):
+
+1. Merge ``develop`` into ``master``:
+
+   .. code-block:: sh
+
+         git checkout master
+         git merge --no-ff develop
+
+2. Tag the release on ``master``:
+
+   .. code-block:: sh
+
+         git tag -a v2.9.0 -m "Release version 2.9.0"
+         git push origin master --tags
+
+3. Delete the old ``release`` branch (if exists):
+
+   .. code-block:: sh
+
+         git branch -d release
+         git push origin --delete release
+
+4. Create a new ``release`` branch from ``master`` when the first patch for 2.9.1 is needed:
+
+   .. code-block:: sh
+
+         git checkout master
+         git checkout -b release
+         git push -u origin release
+
+Best Practices
+--------------
+
+- Regularly **rebase feature branches** on ``develop`` to stay up to date:
+
+  .. code-block:: sh
+
+        git checkout develop/feature_name
+        git rebase develop
+
+- Avoid long-lived branches to minimize merge conflicts.
+
+- Ensure bug fixes in ``release`` or ``master`` are **always cherry-picked** to ``develop``.
+
+- Clearly differentiate between ``fix/xxx`` (non-urgent fixes) and ``hotfix/xxx`` (critical production fixes).
+
+- When creating the ``release`` branch, update release notes to indicate which version it targets (e.g., add a comment in the merge commit: "Create release branch for v2.8.x maintenance").
+
+- The ``release`` branch always represents the current maintenance line. To know which version it targets, check the most recent tag on ``master`` or the release notes.
+
+Takeaway
+--------
+
+This workflow ensures a structured yet flexible development process while keeping
+``master`` stable and ``develop`` always updated with the latest changes.
+
+The ``release`` branch provides a dedicated maintenance line for patch releases,
+allowing ``develop`` to proceed with new features without interference. This solves
+the problem of coordinating unreleased changes across the PlotPyStack ecosystem
+(DataLab, Sigima, PlotPy, guidata, PythonQwt) by providing a stable branch for
+CI testing during maintenance cycles.

{plotpy-2.8.2 → plotpy-2.8.4}/doc/dev/index.rst

@@ -6,6 +6,7 @@ Development
    :caption: Contents:
 
    contribute
+   gitworkflow
    build
    guiqwt_to_plotpy
    v1_to_v2

{plotpy-2.8.2 → plotpy-2.8.4}/doc/features/colormapmanager.rst

@@ -1 +1,2 @@
 .. automodule:: plotpy.widgets.colormap
+   :no-index:

plotpy-2.8.4/doc/features/mathutils/colormaps.rst

@@ -0,0 +1,2 @@
+.. automodule:: plotpy.mathutils.colormap
+   :no-index:

{plotpy-2.8.2 → plotpy-2.8.4}/doc/index.rst

@@ -50,6 +50,6 @@ Table of contents
    intro/index
    features/index
    dev/index
-   changelog
+   release_notes/index
 
 * :ref:`genindex`

{plotpy-2.8.2 → plotpy-2.8.4}/doc/intro/examples.rst

@@ -22,7 +22,7 @@ Curve plotting
 Basic curve plotting
 ~~~~~~~~~~~~~~~~~~~~
 
-.. literalinclude:: ../../plotpy/tests/items/test_curve.py
+.. literalinclude:: ../../plotpy/tests/items/test_curves.py
    :start-after: guitest:
 
 
@@ -86,7 +86,7 @@ Affine transforms example on 3000x3000 images (real-time transforms):
 Image rectangular filter
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. literalinclude:: ../../plotpy/tests/features/test_imagefilter.py
+.. literalinclude:: ../../plotpy/tests/features/test_image_filter.py
    :start-after: guitest:
 
 

plotpy-2.8.4/doc/release_notes/index.rst

@@ -0,0 +1,12 @@
+Release notes
+=============
+
+This section contains the release notes for all versions of :mod:`plotpy`, documenting
+new features, improvements, bug fixes, and breaking changes.
+
+.. toctree::
+    :maxdepth: 1
+    :glob:
+    :reversed:
+
+    release_*