Skip to content

Release Notes for version 2.0

This is the list of changes of taipy version 2.0.

Unsupported version

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

Published on 2022-10.

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

taipy-gui

2.0.2

Significant bug fixes

  • image control may not render properly.
    See issue #436.
  • Clarify and improve the editable (and editable[]) property in the table control.
    See issue #464.
  • [gui] section in configuration files breaks the application.
    See issue #469.

2.0.1

Significant bug fixes

  • Bar charts' "barmode" set to "stack" is broken.
    See issue #445.

2.0.0

New features

  • Extension API: custom visual elements can be integrated into Taipy GUI applications.
    Third party HTML components can be integrated into Taipy GUI pages to address specific use cases.
    See Extension API for details.
  • New callbacks (on_init, on_navigate, on_exception and on_status) can be used to initialize a new session, detect navigation events, trigger code when exceptions are raised in user code, and invoke code when a status page is requested.
    See Callbacks for details.
  • New functions allow applications to invoke long-running callbacks without blocking.
    See Long Running Callbacks for details.
  • The Taipy GUI application configuration uses the generic Taipy configuration mechanism exposed in the new taipy-config package.
  • An application can request the status of the server application using the "status" predefined page.
  • The new 'base' property of the chart control makes it possible to create Gantt chart-like displays.
    See Gantt Charts for details.

Improvements and changes

  • Stopping then re-running the Gui instance is no longer required in Notebook contexts.
  • A discrete graphical indicator is displayed at the bottom of pages when the server is processing.

taipy-core

2.0.4

Significant bug fixes

  • Do not update last_edit_date when a job fails or is abandoned. See issue #366.

2.0.0

New features

  • New data node named SQLTableDataNode. It represents a table in a SQL database.
  • New data node named JSONDataNode. It represents the data from a JSON file.
  • SQLDataNode behavior is changed due to the release of SQLTableDataNode. Now it represents the data using custom read and write queries.
  • In standalone mode, a job whose status is SUBMITTED, PENDING, or BLOCKED can be canceled. When canceling the job, its subsequent jobs will be abandoned, and their statuses will be set to ABANDONED. When the cancel method is called on a job whose status is either RUNNING, COMPLETED, or SKIPPED, its subsequent jobs will be abandoned while its status remains unchanged. A job whose status is FAILED, CANCELED or ABANDONED cannot be canceled.
  • Taipy Orchestrator can now be run as a service by using Orchestrator().run() or tp.run(Orchestrator()). By running Orchestrator as a service, Taipy initializes the scheduler and the job dispatcher based on the provided configuration. The Taipy Orchestrator service can be run along with Taipy GUI or Taipy Rest services.

Improvements and changes

  • The data node of a scenario or a pipeline can now be accessed directly at the scenario or pipeline levels.
  • When submitting a scenario, a pipeline, or a task, the job(s) created will be returned.
  • When submitting a scenario, pipeline, or task in standalone mode, the user can use the parameters wait and timeout to wait until the submitted jobs are finished or up to timeout seconds.
  • When in standalone mode, the job dispatcher runs in a sub-thread that periodically checks for new jobs submitted by Taipy to execute.
  • When a running job fails, its subsequent jobs will be automatically abandoned.
  • A primary scenario can be deleted along with its cycle if it is the only scenario in the cycle.
  • The messages of the various Exceptions that can be raised have been improved to help the users debug their applications.

Deprecations

  • The field nb_of_workers within the Config has been deprecated in favor of max_nb_of_workers.

taipy-config

2.0.0

New features

  • The new taipy-config package was exposed to be used by any other Taipy package for configuration and logging.