taurus 5.4.0.dev0__tar.gz → 5.4.1__tar.gz

{taurus-5.4.0.dev0 → taurus-5.4.1}/CHANGELOG.md

@@ -11,7 +11,32 @@ Note: changes in the [support-3.x] branch (which was split from
 the master branch after [3.7.1] and maintained in parallel to the
 develop branch) won't be reflected in this file.
 
-## Unreleased
+## [5.4.1] - 2026-10-09
+
+### Fixed
+- Fixed Tango attribute event recovery when an error event sets the internal attribute value to None, preventing later valid events from updating it and propagating the event (!1413).
+- Restored the `TANGO_DEVICE_STATE_COLOR_POLICY` custom setting and its documentation after they were accidentally removed (!1419).
+- Update the link to the latest develop documentation
+
+
+## [5.4.0] - 2026-03-18
+[Jan26 milestone](https://gitlab.com/taurus-org/taurus/-/milestones/22)
+
+This release introduces support for Tango asynchronous event subscription
+modes as part of the Taurus Performance Optimization project. 
+It also migrates the `guiqwt` dependency to `plotpy`, affecting all 2D widgets
+that rely on it. This change requires Python >= 3.8.
+
+### Fixed
+- Corrected the device/attribute separator in EvaluatorDevice.getAttribute to use
+'/' instead of ';' (!1392, #1434)
+- Fixed Pythonw compatibility due to widgets bytes enconding(!1393, !1395, #1423)
+- Fixed Tango authority identity/equality by reusing cached default authorities in
+TangoFactory.getAuthority() and adding TangoAuthority.__eq__/__hash__ based on full
+name (!1394, #1431)
+- Prevent blocking waits when creating Tango attributes after application startup in
+Async subscription modes. It now forces a read instead of waiting for the cache to 
+be populated (!1400)
 
 ### Added
 - Support for Tango `EventSubMode` in attribute event subscriptions. This enables
@@ -25,10 +50,17 @@ develop branch) won't be reflected in this file.
   (`Sync`, `Async`) to ensure cached values are initialized.
 - Ability to change or disable Tango event subscriptions from Taurus custom settings,
   CLI, or programmatically through the `TangoFactory` API.
+- Command parser as starting point to implement taurus command fragments (!1389)
+- Added `AutoScaleZTool` to `TaurusImageDialog` to enable dynamic Z-axis autoscaling 
+  from the toolbar. An autoLutRange constructor parameter has also been added to 
+  allow enabling it at startup.
 
 ### Changed
 - Default subscription mode is now `AsyncRead` when `EventSubMode` is available (Tango >= 10.1).
   To retain the previous Taurus behavior, `SyncRead` can be selected via Taurus custom settings.
+- Migrated usage of `pkg_resources` to `importlib` to address deprecation warnings and ensure future compatibility with setuptools (#1422, !1391).
+- Migrated usage of `guiqwt` to `plotpy`. `guiqwt` project has been officially replaced by `plotpy` (!1373).
+- Updated minimum Python version to 3.8 for `plotpy` compatibility (!1398)
 
 ## [5.3.2] - 2025-11-28
 Patch release with bug fixes.
@@ -985,6 +1017,8 @@ and several other places](https://sf.net/p/tauruslib/tickets/milestone/Jul15/)
 [TEP19]: http://www.taurus-scada.org/tep/?TEP19.md
 [TEP20]: http://www.taurus-scada.org/tep/?TEP20.md
 [Unreleased]: https://gitlab.com/taurus-org/taurus/-/tree/develop
+[5.4.1]: https://gitlab.com/taurus-org/taurus/-/tree/5.4.0
+[5.4.0]: https://gitlab.com/taurus-org/taurus/-/tree/5.4.0
 [5.3.2]: https://gitlab.com/taurus-org/taurus/-/tree/5.3.2
 [5.3.1]: https://gitlab.com/taurus-org/taurus/-/tree/5.3.1
 [5.3.0]: https://gitlab.com/taurus-org/taurus/-/tree/5.3.0

{taurus-5.4.0.dev0/lib/taurus.egg-info → taurus-5.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taurus
-Version: 5.4.0.dev0
+Version: 5.4.1
 Summary: A framework for scientific/industrial CLIs and GUIs
 Home-page: http://www.taurus-scada.org
 Download-URL: http://pypi.python.org/packages/source/t/taurus
@@ -25,7 +25,6 @@ Classifier: Operating System :: POSIX :: Linux
 Classifier: Operating System :: Unix
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
-Classifier: Programming Language :: Python :: 3.7
 Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
@@ -37,7 +36,7 @@ Classifier: Topic :: Software Development :: Libraries
 Classifier: Topic :: Software Development :: User Interfaces
 Classifier: Topic :: Software Development :: Widget Sets
 Provides: taurus
-Requires-Python: >=3.7
+Requires-Python: >=3.8
 License-File: LICENSE.txt
 Requires-Dist: numpy>=1.16
 Requires-Dist: pint>=0.8
@@ -48,8 +47,7 @@ Provides-Extra: taurus-qt
 Requires-Dist: ply>=2.3; extra == "taurus-qt"
 Requires-Dist: lxml>=2.1; extra == "taurus-qt"
 Requires-Dist: PyQtWebEngine; extra == "taurus-qt"
-Requires-Dist: guiqwt>=3; extra == "taurus-qt"
-Requires-Dist: pythonqwt<=0.14.3; extra == "taurus-qt"
+Requires-Dist: plotpy>=2.6.2; extra == "taurus-qt"
 Provides-Extra: taurus-tango
 Requires-Dist: PyTango>=9.2; extra == "taurus-tango"
 Provides-Extra: taurus-epics

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/devel/core_tutorial.rst

@@ -122,7 +122,7 @@ our TO-DO list are:
 - A scheme to access data from mySQL databases as Taurus attributes
 - A scheme to access Tango-archived data as Taurus attributes
 
-model access
+Model access
 ------------
 
 Taurus users are encouraged to write code that is "scheme-agnostic",
@@ -254,3 +254,107 @@ the most important ones.
 .. _PyTango: http://packages.python.org/PyTango/
 .. _EPICS: http://www.aps.anl.gov/epics/
 .. _RFC3986: https://tools.ietf.org/html/rfc3986
+
+
+Fragments
+---------
+
+Taurus model names support an optional *fragment* component introduced by the
+``#`` separator:
+
+.. code-block:: text
+
+    <model-name>#<fragment>
+
+**Important!** The fragment is not part of the model identity. Taurus creates the model object
+(using :class:`TaurusModel` or one of its subclasses) exclusively from the
+portion of the name before the ``#``. The fragment string is stored by widgets
+through :attr:`TaurusBaseComponent.modelFragmentName` and is therefore part of
+the *view* layer, not the model layer.
+
+Fragments allow widgets to request additional information or behavior from a
+model. Internally, fragments are resolved via :meth:`TaurusModel.getFragmentObj`,
+whose default implementation maps:
+
+.. code-block:: python
+
+    model.getFragmentObj("foo")  ->  getattr(model, "foo")
+
+This enables models to expose additional attributes or callables without
+modifying the underlying model name structure.
+
+
+WIP: Command - Command Fragments
+--------------------------------
+
+**Important** This feature in not fully implemented yet, only the command parser
+is available.
+
+Fragments can also represent backend *commands*. A command can be encoded in the
+fragment as a function-like expression that includes the command name and
+(optional) arguments:
+
+.. code-block:: text
+
+    tango:sys/tg_test/1#Init
+    tango:sys/tg_test/1#Init(1)
+    tango:sys/tg_test/1#Init(1, x=2)
+
+In all such cases, the model name remains ``tango:sys/tg_test/1``. The fragment
+(e.g. ``"Init"`` or ``"Init(1, x=2)"``) is interpreted only by the widget and does
+not influence how the model is constructed.
+
+
+Using Command Fragments
+-----------------------
+
+A widget that supports command fragments typically performs the following steps:
+
+1. **Read the fragment**
+   The widget retrieves :attr:`modelFragmentName`, which contains the raw
+   fragment string (e.g. ``"Init(1, x=2)"``).
+
+2. **Parse the command expression**
+   The widget is responsible for extracting:
+   - the command name,
+   - positional arguments,
+   - keyword arguments.
+
+   Argument parsing is entirely a widget-side responsibility; the model receives
+   only the command name.
+
+3. **Resolve the backend callable**
+   The widget obtains the callable via:
+
+   .. code-block:: python
+
+       func = model.getFragmentObj(cmd_name)
+
+   This returns a Python callable exposed by the model implementation.
+
+4. **Execute the command**
+   The widget invokes:
+
+   .. code-block:: python
+
+       func(*args, **kwargs)
+
+   This triggers the appropriate backend operation (e.g. Tango command
+   invocation) through the model object, not through the widget.
+
+
+Scheme-Agnostic Command Widgets
+-------------------------------
+
+Taurus follows a strict separation of concerns: widgets must remain *scheme
+agnostic*. A widget must **not** contain backend-specific logic.
+Instead, the widget interacts solely with
+the model via:
+
+- :meth:`TaurusBaseComponent.getModelObj`,
+- :meth:`TaurusModel.getFragmentObj`,
+- :attr:`modelFragmentName`.
+
+Backend-specific behavior belongs in the model implementation (e.g. a Tango
+scheme plugin), which must expose backend commands as Python callables accessible
+via attribute lookup.

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/devel/designer_tutorial.rst

@@ -64,9 +64,7 @@ Designer in a Linux Conda installation:
 
 Option 1
   Use a dedicated Conda environment with PyQt5 version 5.12 specifically for
-  running the designer. Due to that ``guiqwt`` library version installed
-  will be 3.0.7 and to maintain API compatibility you have to downgrade
-  ``guidata`` library from 3.1.0 to 2.3.1.
+  running the designer.
 
 Option 2
   Copy the missing ``libpyqt5.so`` file to the appropriate folder in the Conda

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/devel/plotting_guide.rst

@@ -8,7 +8,7 @@ Taurus plotting guide
 
 In taurus, the following dependencies are used for its various plotting widgets:
 
-- guiqwt_: for `TaurusImageDialog` and `TaurusTrend2DDialog` implemented in :mod:`taurus.qt.qtgui.extra_guiqwt`.
+- plotpy_: for `TaurusImageDialog` and `TaurusTrend2DDialog` implemented in :mod:`taurus.qt.qtgui.extra_plotpy`.
   It does not depend at all of PyQwt5, and supports py3 and Qt5 so replacing it is not urgent
   (but still it should be eventually replaced by pyqtgraph-based widgets)
 - pyqtgraph_: for `TaurusPlot` and `TaurusTrend` implementions provided by the
@@ -33,7 +33,7 @@ Tips for Getting started with taurus_pyqtgraph_
 
 
 
-.. _guiqwt: https://pythonhosted.org/guiqwt/
+.. _plotpy: https://plotpy.readthedocs.io/en/latest/
 .. _pyqtgraph: http://www.pyqtgraph.org/
 .. _taurus_pyqtgraph: https://gitlab.com/taurus-org/taurus_pyqtgraph
 .. _taurus_tangoarchiving: https://gitlab.com/taurus-org/tangoarchiving-scheme

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/devel/plugins.rst

@@ -116,12 +116,12 @@ Image widget Alternatives
   widget creator needs to accept the ``wintitle`` keyword argument (it may
   change when the API is formalized)
 - Entry point name convention: a short descriptive identifier of the
-  implementation (e.g. ``"guiqwt"``, ``"tpg"``, ...). The name is used in the UI
+  implementation (e.g. ``"plotpy"``, ``"tpg"``, ...). The name is used in the UI
   for user selection of the implementation.
 - Loading pattern: Extension
 - Enabling pattern: explicit
 - Examples: :mod:`taurus` self-registers its
-  :class:`taurus.qt.qtgui.extra_guiqwt.TaurusImageDialog` as an image widget
+  :class:`taurus.qt.qtgui.extra_plotpy.TaurusImageDialog` as an image widget
   alternative (see ``setup.py``)
 
 Trend2D widget Alternatives
@@ -136,12 +136,12 @@ Trend2D widget Alternatives
   widget creator needs to accept the following keyword arguments: ``stackMode``,
   ``wintitle``, ``buffersize``. (it may change when the API is formalized)
 - Entry point name convention: a short descriptive identifier of the
-  implementation (e.g. ``"guiqwt"``, ``"tpg"``, ...). The name is used in the UI
+  implementation (e.g. ``"plotpy"``, ``"tpg"``, ...). The name is used in the UI
   for user selection of the implementation.
 - Loading pattern: Extension
 - Enabling pattern: explicit
 - Examples: :mod:`taurus` self-registers its
-  :class:`taurus.qt.qtgui.extra_guiqwt.TaurusTrend2DDialog` as trend2d widget
+  :class:`taurus.qt.qtgui.extra_plotpy.TaurusTrend2DDialog` as trend2d widget
   alternative (see ``setup.py``)
 
 Form Factories

taurus-5.4.1/doc/source/other_versions.rst

@@ -0,0 +1,14 @@
+
+==============================
+Docs for other Taurus versions
+==============================
+
+The `default taurus docs <http://taurus-scada.org>`_ reflect the latest tagged
+version in the repository.
+
+The documentation for the latest push to ``develop`` is available at:
+https://taurus.readthedocs.io/en/develop/
+
+Note that the docs are also automatically built by the pipelines triggered by
+Merge Requests. They can be viewed using the "View App" button in the given
+Merge Request page.

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/tep/TEP17.md

@@ -5,16 +5,16 @@
     Drivers: Carlos Pascual-Izarra cpascual@cells.es
     URL: http://www.taurus-scada.org/tep?TEP17.md
     License: http://www.jclark.com/xml/copying.txt
-    Abstract: 
+    Abstract:
      Replace TaurusPlot and TaurusTrend implementations from the deprecated
      taurus.qt.qtgui.qwt5 by taurus_pyqtgraph implementations
- 
+
 ## Introduction
 
-Taurus currently depends on [PyQwt5][] for its `taurus.qt.qtgui.plot` and 
+Taurus currently depends on [PyQwt5][] for its `taurus.qt.qtgui.plot` and
 `taurus.qt.qtgui.qwt5` modules.
 
-PyQwt5 has been unmaintained for a long time and is not supported in  
+PyQwt5 has been unmaintained for a long time and is not supported in
 most modern linux distros and is not compatible with PyQt5 and Python3.
 
 This TEP proposes using the [taurus_pyqtgraph][] plugin as a replacement for
@@ -22,13 +22,13 @@ This TEP proposes using the [taurus_pyqtgraph][] plugin as a replacement for
 
 ## Goals
 
-For the scope of this TEP, only a basic subset of the features that were 
+For the scope of this TEP, only a basic subset of the features that were
 supported by `taurus.qt.qtgui.qwt5` are implemented in the current version of
-the [taurus_pyqtgraph][] plugin. The rest would be treated as future 
-enhancements. 
+the [taurus_pyqtgraph][] plugin. The rest would be treated as future
+enhancements.
 
-The following is a list of features provided and planned by the 
-`taurus_pyqtgraph` plugin  (the checked features are already implemented 
+The following is a list of features provided and planned by the
+`taurus_pyqtgraph` plugin  (the checked features are already implemented
 in the latest release of the plugin, v0.4.9, at the moment of writing):
 
 ### For 1D plots
@@ -84,7 +84,7 @@ trends:
 - [x] Fixed-range scale (aka oscilloscope mode)
 - [x] UI to switch between fixed and free scale mode
 - [x] Stand-alone Widget (`TaurusTrend`)
-- [x] Support for forced-reading of attributes (aka "-r mode") 
+- [x] Support for forced-reading of attributes (aka "-r mode")
 - [x] UI for forced-reading mode
 - [x] configurable properties support (setting permanence)
 
@@ -187,14 +187,14 @@ Also see the Issues and Pull Requests from the [taurus_pyqtgraph][] project.
 
 ## Follow-on
 
-Originally the scope of TEP17 also included providing a replacement for the 
-following 2D widgets: 
+Originally the scope of TEP17 also included providing a replacement for the
+following 2D widgets:
 
 - `TaurusImageDialog`
 - `TaurusTrend2DDialog`
 
-This was later reconsidered and the scope was reduced to the 1D plots and 
-trends. Future work may include the 2D widgets and also some other features. 
+This was later reconsidered and the scope was reduced to the 1D plots and
+trends. Future work may include the 2D widgets and also some other features.
 See [taurus_pyqtgraph][] for more details and updated information iabout it.
 
 ## License
@@ -226,7 +226,7 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 - 2017-03-10 [Carlos Pascual][]. Initial version
 - 2017-05-17 [Carlos Pascual][]. TEP text updated and proof-of-concept
   implementation by [oscarprades][] added
-- 2020-12-09 [Carlos Pascual][]. TEP text updated to reflect the use of the 
+- 2020-12-09 [Carlos Pascual][]. TEP text updated to reflect the use of the
   taurus_pyqtgraph plugin. Changed state to CANDIDATE and proposed for APPROVAL
 - 2021-03-08 [Carlos Pascual][]. Changed state to ACCEPTED
 - 2021-03-17 [Carlos Pascual][]. Updated links

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/users/getting_started.rst

@@ -51,13 +51,13 @@ optionally, you may also want to install tango::
 
     conda install -c conda-forge pytango
 
-Note: for windows, until pytango is available on conda-forge, you may need to use 
+Note: for windows, until pytango is available on conda-forge, you may need to use
 `pip install pytango` for installing it.
 
 .. warning::
 
    There is a known issue with PyQt5 versions >= 5.15.4 where Taurus Designer is
-   not showing Taurus widgets. See :ref:`Designer known issues<designer_pyqt515_issue>` 
+   not showing Taurus widgets. See :ref:`Designer known issues<designer_pyqt515_issue>`
    for possible workarounds.
 
 
@@ -71,7 +71,7 @@ on each change::
 
     # optional: if using a conda environment, pre-install dependencies:
     # e.g, for basic dependencies:
-    conda install -c conda-forge python=3 click numpy pint pyqt ply lxml guiqwt pyqtgraph
+    conda install -c conda-forge python=3 click numpy pint pyqt ply lxml plotpy pyqtgraph
     # ... and some extra dependencies (pick the ones you need)
     conda install -c conda-forge pytango pyepics spyder pymca
     # ... and if you want to run the test suite:
@@ -108,7 +108,7 @@ expected of Taurus (which are considered "extras"). For example:
   is done with PyQt5, so many features may not be
   regularly tested with PySide2.
 
-- The image widgets require the guiqwt_ library.
+- The image widgets require the plotpy_ library.
 
 - The JDraw synoptics widgets require the PLY_ package.
 
@@ -151,7 +151,7 @@ installation method:
 .. _PySide: https://wiki.qt.io/Qt_for_Python
 .. _PyQwt: http://pyqwt.sourceforge.net/
 .. _taurus_pyqtgraph: https://gitlab.com/taurus-org/taurus_pyqtgraph
-.. _guiqwt: https://pypi.org/project/guiqwt/
+.. _plotpy: https://plotpy.readthedocs.io/en/latest/
 .. _IPython: http://ipython.org
 .. _PyMca5: http://pymca.sourceforge.net/
 .. _pyepics: https://pypi.org/project/pyepics/

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/users/ui/plot.rst

@@ -12,7 +12,7 @@ TaurusPlot User's Interface
 
 The standard way for Taurus applications to show one-dimensional data is by
 using a :class:`TaurusPlot` widget.
-    
+
 :class:`TaurusPlot` is shown as an area with X and Y axes where curves (data sets)
 are plotted. It may also show a legend.
 
@@ -22,7 +22,7 @@ are plotted. It may also show a legend.
 But the :class:`TaurusPlot` does a lot more than just showing a plot. It allows
 the user to interact with the plot in many ways as described below.
 
-.. note:: The features described here are available *by default* in all TaurusPlot 
+.. note:: The features described here are available *by default* in all TaurusPlot
           widgets, but certain GUIs may choose to disable some of these features.
 
 .. _standalonetaurusplot:
@@ -35,7 +35,7 @@ attributes from the control system or for plotting a function. You can launch th
 stand-alone :class:`TaurusPlot` with the following command::
 
     taurus plot [options] [<model_list>]
-	
+
 Run the following command for more details::
 
     taurus plot --help
@@ -88,13 +88,13 @@ There are several ways of changing the scales interactively:
 
 
 .. _plotconfiguration:
-  
+
 Plot Configuration dialog
 -------------------------
 
 .. figure:: /_static/taurusplot-config01.png
    :align: center
-   
+
 This dialog can be accessed from the `TaurusPlot context menu`_.
 
 On its top section you can customize the look of the displayed data (line type,
@@ -160,7 +160,7 @@ in several ways:
 - Through the `Change Curves Titles...` option in the `TaurusPlot context menu`_
 - Through the `Plot Configuration dialog`_ (either editing the name
   individually, or selecting several curves and clicking on the `Curve Title(s)...` button)
-    
+
 .. _taurusplottime:
 
 Date/time support
@@ -180,7 +180,7 @@ instead of the epoch number:
 
 .. references
 .. _numpy: http://numpy.scipy.org/
-.. _guiqwt: http://pypi.python.org/pypi/guiqwt
+.. _plotpy: https://plotpy.readthedocs.io/en/latest/
 
 
 .. |inspector_icon| image:: /_static/whatsthiscursor.png

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/users/ui/taurusimage.rst

@@ -1,4 +1,4 @@
-.. currentmodule:: taurus.qt.qtgui.extra_guiqwt
+.. currentmodule:: taurus.qt.qtgui.extra_plotpy
 
 .. _taurusimage:
 
@@ -10,25 +10,25 @@ Image's interface
 .. contents::
 
 The :class:`TaurusImageDialog` widget is a Taurus Widget for displaying
-**image** attributes from the control system. A contour plot 
+**image** attributes from the control system. A contour plot
 is created from the values of the image attribute.
 
 .. figure:: /_static/taurusimage01.png
   :align: center
-  
+
   A TaurusImage widget displaying the `sys/tg_test/1/long_image_ro` attribute
- 
+
 Many tools may be available, such as:
 
 - zooming and panning
 - X/Y cross sections
 - Annotation tools (for creating labels, shapes,...)
-- add/delete images 
+- add/delete images
 - ...
 
-.. note:: The :class:`TaurusImageDialog` widget is provided by  
-          the :mod:`taurus.qt.qtgui.extra_guiqwt` module which depends on 
-          the :mod:`guiqwt` module being installed. If guiqwt is not installed, 
+.. note:: The :class:`TaurusImageDialog` widget is provided by
+          the :mod:`taurus.qt.qtgui.extra_plotpy` module which depends on
+          the :mod:`plotpy` module being installed. If plotpy is not installed,
           the image widget will not be available.
 
 .. _standalonetaurusimage:
@@ -40,8 +40,8 @@ You may also use TaurusImageDialog as a stand-alone application for showing imag
 attributes from the control system. You can launch the stand-alone Taurus Image
 with the following command::
 
-    taurus guiqwt image [options] <model>
+    taurus image [options] <model>
 
 Run the following command for more details::
 
-    taurus guiqwt image --help
+    taurus image --help

{taurus-5.4.0.dev0 → taurus-5.4.1}/doc/source/users/ui/trend.rst

@@ -40,15 +40,15 @@ attributes from the control system. You can launch the stand-alone TaurusTrend
 with the following command::
 
     taurus trend [options] [<model_list>]
-	
+
 Run the following command for more details::
 
     taurus trend --help
 
-    
-The model list is optional and is a space-separated list of models for TaurusTrend. 
+
+The model list is optional and is a space-separated list of models for TaurusTrend.
 Valid models are: SCALAR or 1D attribute names (1D attributes will be treated
-as collections of scalars). See :class:`TaurusTrend` API for more information about valid models   
+as collections of scalars). See :class:`TaurusTrend` API for more information about valid models
 
 
 Timestamp VS "event number" mode
@@ -85,7 +85,7 @@ You can switch the `Fixed-range X scale` mode on and off from either:
 - The :ref:`Plot Configuration dialog <plotconfiguration>` (under the
   `X axis` sub-menu). Here you can choose from suggested values or simply
   type a range:
-  
+
     .. image:: /_static/taurustrend-fixedRange01.png
 
 
@@ -122,13 +122,13 @@ that do not change often, do not get new points in the trend and thus may seem
 to have been "lost". To avoid this issue, you can instruct the TaurusTrend to
 periodically force re-read the attributes being displayed. You can enable this
 feature (and set the re-read period) from the :ref:`Context Menu <taurusplotcontextmenu>`
- 
+
 If launching the TaurusTrend as a stand-alone application, you can also enable this
-at launch time by passing the `-r` option (see the `TaurusTrend as a stand-alone 
+at launch time by passing the `-r` option (see the `TaurusTrend as a stand-alone
 application`_ section).
 
 Keep in mind the following:
-  
+
 - Setting very frequent re-reads may impact your control system and GUI
   performance. Specially if you are plotting several attributes. **So, do not
   use this feature unless it is really needed**
@@ -142,7 +142,7 @@ Limited timing precision when comparing two attributes
 
 If two different attributes are plotted in the same trend, their times may appear
 slightly out-of-synch. For example, two parameters that are known to vary
-simultaneously may be apparently 0.5 seconds apart. 
+simultaneously may be apparently 0.5 seconds apart.
 
 This occurs because TaurusTrend relies on the control system timestamps for
 assigning the time values. Therefore, its precision is limited by that of the
@@ -152,7 +152,7 @@ Note that timestamps for an attribute may be assigned using the internal
 clock of the machine hosting the device server. Therefore, attributes managed
 by different machines may only be compared to the extent of the synchronization
 of the corresponding internal clocks. In such a case, keeping all machines
-synchronized is highly recommended (e.g., using NTP_, accuracy should not be 
+synchronized is highly recommended (e.g., using NTP_, accuracy should not be
 worse than 0.1s).
 
 Trend of Tango State attribute (or other non-numerical attributes)
@@ -166,14 +166,14 @@ However you can still achieve trends of the State attribute values using the
 :mod:`taurus.core.evaluation` scheme models. For example, to make a trend
 of the State attribute values::
 
-    taurus trend -r 500 'eval:state=int({tango:sys/tg_test/1/state});state' 
+    taurus trend -r 500 'eval:state=int({tango:sys/tg_test/1/state});state'
 
-Or to make a trend of the State attribute changes between a given state 
+Or to make a trend of the State attribute changes between a given state
 (in this case MOVING state has the enumeration value 6) and all other states::
 
     taurus trend -r 500 'eval:moving=(int({tango:sys/tg_test/1/state})==6);moving'
 
-This "trick" can of course be applied to any other attributes whose values are not 
+This "trick" can of course be applied to any other attributes whose values are not
 numerical.
 
 .. _trend2d_ui:
@@ -182,21 +182,21 @@ numerical.
 Spectrograms (2D trends)
 ========================
 
-The :class:`TaurusTrend2DDialog` widget is the standard way for Taurus 
-applications to graphically show the evolution of a one-dimensional 
-attribute. The representation is done as a *spectrogram*: the time (or 
-event number) is represented in the X axis while values of the array 
+The :class:`TaurusTrend2DDialog` widget is the standard way for Taurus
+applications to graphically show the evolution of a one-dimensional
+attribute. The representation is done as a *spectrogram*: the time (or
+event number) is represented in the X axis while values of the array
 are color-coded along the Y axis.
 
 
 .. figure:: /_static/taurustrend2d.png
   :align: center
 
-Several tools from the standard guiqwt_ toolkit for images are available,
-and zooming and panning are possible using the standard mechanisms of 
-guiqwt_.
+Several tools from the standard plotpy_ toolkit for images are available,
+and zooming and panning are possible using the standard mechanisms of
+plotpy_.
 
-The :class:`TaurusTrend2DDialog` widget can be launched as a 
+The :class:`TaurusTrend2DDialog` widget can be launched as a
 stand-alone application with the following command::
 
 	taurus trend2d <array_attribute_name>
@@ -206,6 +206,6 @@ Run the following command for more details::
     taurus trend2d --help
 
 
-.. _guiqwt: https://pypi.python.org/pypi/guiqwt
+.. _plotpy: https://plotpy.readthedocs.io/en/latest/
 .. _taurus-tangoarchiving: https://gitlab.com/taurus-org/taurus_tangoarchiving
 .. _NTP: http://en.wikipedia.org/wiki/Network_Time_Protocol

{taurus-5.4.0.dev0 → taurus-5.4.1}/lib/taurus/_release.py

@@ -52,7 +52,7 @@ __docformat__ = "restructuredtext"
 # (https://github.com/peritus/bumpversion), except when adding/removing
 # extra numbers in the release segment (e.g. for hotfixes), which is done
 # manually.
-version = "5.4.0.dev0"
+version = "5.4.1"
 
 name = "taurus"