Release Notes for version 2.3

This is the list of changes of taipy version 2.3.

Unsupported version

Version 2.3 of Taipy is no longer supported. We strongly recommend that you upgrade to the latest version of Taipy.

Published on 2023-06.

taipy 2.3 contains the latest taipy-config 2.3, taipy-gui 2.3, taipy-core 2.3 and taipy-rest 2.3 packages.

taipy

2.3.1

Improvements and changes

• The expanded and show_tags properties of the scenario control now have a default value of False.

2.3.0

New features

• Scenario and Data Management Controls
  Taipy comes, in the taipy package, with a set of ready-to-use GUI controls that connect to entities created by Taipy. Your application can then visualize the Taipy entities related to Scenario and Data Management and interact with them.
  Please check the list of Scenario and Data Management Scenario and Data Management controls.
• New Taipy command-line interface (CLI). Please refer to the Taipy command-line interface documentation page for more information.
• Users can now create a new Taipy application from a template by running $ taipy create from the CLI. Besides the default template, "multi-page-gui" template can be chosen with the optional --template option.

taipy-gui

2.3.1

Improvements and changes

• Multi-line input controls accept the Shift+Enter combination to create a new line.
  See issue #824.
• Table filters adapt to a change of the visible columns.
  See issue #822.

2.3.0

New features

• The table and
• chart controls have a new property called rebuild that allows for modifying the control configuration at runtime, using properties that are not dynamic.
  See the details in the specific documentation sections for tables and charts.
• The part block now accepts any URL as a value for the page property. You can then integrate any external web page as demonstrated in this example.
  To better control the layout of external pages, a new height property has been added to the part element.
• The navigate() function has an additional parameter called force that, when set to True, re-renders the page (set to the to parameter). This allows to force the evaluation of bound variables in complex dependencies situations.

Improvements and changes

• Page scopes (how Taipy GUI finds bound variables in different modules) have been improved so any given page can locate a variable in any module that defines a local page.
  See the section on page scopes for more information and examples.
• A new mechanism to start the web server when using Notebooks was put in place to prevent potential bottlenecks when allocating a port number. This behavior is controlled by the notebook_proxy configuration parameter.

Significant bug fixes

• The removal of all the table filters has no immediate effect.
  See issue #667.
• Styling of the pane block was not applied properly.
  See issue #766.
• Some notifications (see notify()) could be missed when there were too many in a small period of time.
  See issue #777.

taipy-core

2.3.1

New features

• New exposed functions:

  • is_submittable() checks if a scenario or a pipeline can be submitted;

  • is_promotable() checks if a scenario can be promoted to primary;

  • is_deletable() checks if an entity can be deleted.

Deprecations

• The Config.configure_default_data_node() method has been deprecated. The Config.set_default_data_node_configuration() method should be used instead.
• The Config.configure_task_node() method has been deprecated. The Config.set_task_node_configuration() method should be used instead.
• The Config.configure_pipeline_node() method has been deprecated. The Config.set_pipeline_node_configuration() method should be used instead.
• The Config.configure_scenario_node() method has been deprecated. The Config.set_scenario_node_configuration() method should be used instead.

2.3.0

New features

• All scenarios grouped by their cycle can now be retrieved by calling taipy.get_cycles_scenarios().
• All entities (cycles, scenarios, pipelines, tasks, data nodes, and jobs) expose two new methods: get_label() and get_simple_label(), that can be used to display the entity.
• taipy.get_entities_by_config_id() can be used to retrieve all entities that are based on the provided configuration identifier.
• Commands for managing Taipy application versions can now be accessed via the $ taipy manage-versions command. Run $ taipy manage-versions --help for more details.
• A version can now be renamed by running $ taipy manage-versions --rename <old_version> <new_version> from the CLI.
• The configuration of a version can now be compared with another one by running $ taipy manage-versions --compare-config <version_1> <version_2> from the CLI.

Improvements and changes

• A generic data node can now be created defining only the read_fct parameter for a read-only data node, or only the write_fct parameter for a write-only data node.
• The parameters read_fct_params and write_fct_params of the generic data nodes were renamed to read_fct_args and write_fct_args, and both must be populated with a List value to avoid the problem of passing Tuple of one string.
• The validity_period attribute of a data node is now exposed at the configuration level to set the up-to-date duration of a data node.
• Add support for SQLAlchemy 2.0

Deprecations

• PipelineConfig has been deprecated and will be combined with ScenarioConfig in future updates.
• taipy.create_pipeline() has been deprecated.