Taurus custom settings

Taurus provides a module located at its root directory called tauruscustomsettings which stores global configuration options. It can be modified permanently so that it affects all applications (use with care), or accessed at run time for setting options for the current execution.

This module contains some Taurus-wide default configurations.

The idea is that the final user may edit the values here to customize certain aspects of Taurus.


Set preferred API (if one is not already loaded). Accepted values are pyqt5, pyqt, pyside2, pyside. Set to an empty string to let taurus choose the first that works from the accepted values.


Default scheme (if not defined, “tango” is assumed)


Extra Taurus schemes. You can add a list of modules to be loaded for providing support to new schemes (e.g. EXTRA_SCHEME_MODULES = [‘myownschememodule’]


Filter old tango events: Sometimes TangoAttribute can receive an event with an older timestamp than its current one. See https://gitlab.com/taurus-org/taurus/-/issues/216 True discards (Tango) events whose timestamp is older than the cached one. False (or commented out) for backwards (pre 4.1) compatibility


Implicit optparse legacy support: In taurus < 4.6.5 if TaurusApplication did not receive an explicit cmd_line_parser keyword argument, it implicitly used a optparse.OptionParser instance. This was inconvenient because it forced the user to explicitly pass cmd_line_parser=None when using other mechanisms such as click or argparse to parse CLI options. In taurus >=4.6.5 this is no longer the case by default, but the old behaviour can be restored by setting IMPLICIT_OPTPARSE=True


Lightweight imports: True enables delayed imports (may break older code). False (or commented out) for backwards compatibility

Custom organization logo. Set the absolute path to an image file to be used as your organization logo. Qt registered paths can also be used. If not set, it defaults to ‘logos:taurus.png” (note that “logos:” is a Qt a registered path for “<taurus>/qt/qtgui/icon/logos/”)

PLOT_ALT = '.*'

Widget alternatives. Some widgets may be have alternative implementations (e.g. the TaurusPlot is implemented both by the qwt5 submodule and by the taurus_pyqtgraph plugin). The different implementations are registered in entry point groups (taurus.plot.alt, taurus.trend.alt, …) and they are tried in alphabetical order of their registered entry point names (the first one that works is used). You can restrict the set of available implementation alternatives to be tried (or even just select a given alternative) by setting the corresponding _ALT variable with a name regexp pattern that must be matched by the entry point name in order to be tried. For example, to force the `taurus_pyqtgraph` implementation for the plots, set `PLOT_ALT = “tpg”`. Leaving the variable undefined is equivalent to setting it to `”.”`


PLY (lex/yacc) optimization: 1=Active (default) , 0=disabled. Set PLY_OPTIMIZE = 0 if you are getting yacc exceptions while loading synoptics


Auto initialize Qt logging to python logging


Remove input hook (only valid for PyQt4)


Full Qt designer path (including filename. Default is None, meaning: - linux: look for the system designer following Qt.QLibraryInfo.BinariesPath - windows: look for the system designer following Qt.QLibraryInfo.BinariesPath. If this fails, taurus tries to locate binary manually


Select the theme to be used: set the theme dir and the theme name. The path can be absolute or relative to the dir of taurus.qt.qtgui.icon If not set, the dir of taurus.qt.qtgui.icon will be used


In Linux the QT_THEME_NAME is not applied (to respect the system theme) setting QT_THEME_FORCE_ON_LINUX=True overrides this.


The name of the icon theme (e.g. ‘Tango’, ‘Oxygen’, etc). Default=’Tango’


Strict RFC3986 URI names in models. True makes Taurus only use the strict URI names False enables a backwards-compatibility mode for pre-sep3 model names


Whether TangoAttribute is subscribed to configuration events by default. Setting to True (or not setting it) makes the TangoAttribute auto-subscribe Setting to False avoids this subscription, which prevents issues such as https://gitlab.com/taurus-org/taurus/-/issues/1118 but it also prevents clients to be notified when configurations (e.g., units, format) change.


Default serialization mode for the tango scheme. Possible values are: ‘Serial’, ‘Concurrent’, or ‘TangoSerial’ (default)


Compact mode for widgets True sets the preferred mode of TaurusForms to use “compact” widgets


DEPRECATED. Use “taurus.form.item_factories” plugin group instead A map for using custom widgets for certain devices in TaurusForms. It is a dictionary with the following structure: device_class_name:(classname_with_full_module_path, args, kwargs) where the args and kwargs will be passed to the constructor of the class

T_FORM_ITEM_FACTORIES = {'exclude': (), 'include': ('.*',)}

Default include and exclude patterns for TaurusForm item factories See TaurusForm.setItemFactories docs. By default, all available factories are enabled (and tried alphabetically)