Release Notes for version 4.1

This is the list of changes to Taipy version 4.1.

Upgrading to Taipy 4.1

Please refer to the Migration page for potential migration paths for your applications implemented on legacy Taipy versions.

Published on 2026-02.

taipy-enterprise 4.1 depends on the latest taipy 4.1 package which depends on the latest taipy-common 4.1, taipy-gui 4.1, taipy-core 4.1, taipy-templates 4.1, and taipy-rest 4.1 packages.

taipy

4.1.1

Improvements and changes

• Pandas version dependency has been updated for the latest Python versions. The supported versions are:

  • for Python 3.9: From 1.3.5 to 2.2.3 included.
  • for Python versions >= 3.10: Pandas versions >= 2.2.0 and < 3.0.0.

4.1.0

New features

• Event management simplification: A new EventProcessor class has been introduced to simplify the management of events in Taipy.
  See issue #2306.

taipy-gui

4.1.2

Significant bug fixes

• Fix for two decimator classes:
  • MinMaxDecimator may lose some trailing data points
  • ScatterDecimator does not always properly handle missing input data points.

4.1.1

Significant bug fixes

• Fix for hover text not working with the number element.
  See issue #2791.

Improvements and changes

• The chart element performance was improved when using the figure property.
  See issue #2716.

4.1.0

New features

• A mock implementation of State, called MockState, is available for testing purposes. You can learn about how tu use this class on the Mocking State in unit tests page.
  See issue #2098.
• The text element supports LaTeχ rendering, setting the mode property to "latex".
  See issue #1401.

Improvements and changes

• The syntax for creating long running callbacks can be simplified by using the async keyword of Python 3.
  TODO: Point to the code sample that demonstrates the usage of that feature.
  See issue #2288.
• The input and number elements now trigger the on_change callback if the new action_on_blur property is set to True.
  See issue #2023.
• The selector element supports multiple selection when configured as a dropdown selector.
  See issue #1834.
• The chat element supports images in text areas.
  See issue #1314.

taipy-core

4.1.0

Significant bug fixes

• Global data nodes depending on the order of task configs in the scenario config constructor are missing some task IDs in the parent_ids attribute.
  See issue #2597.

Deprecations

• Class CoreEventConsumerBase has been deprecated in favor of the new API EventProcessor.

taipy-enterprise

4.1.0

New features

• A new migration function has been added to help upgrading to a new production version. This function is designed to automatically migrate entities based on changes in the scenario configuration graph topology. This includes adding, moving or removing task configurations and/or data node configurations from a scenario configuration graph.
  See Config.auto_migrate_scenario_graph() for more details.
  Note that renaming task or data node configurations is considered as a deletion and an addition. Resulting entities won't keep their IDs or previous attributes.
  Note that changes in the various configurations' attributes are not automatically migrated. Please refer to the Config.add_migration_function() method and the migration page for more details.