Legacy
This is the list of changes to legacy major Taipy releases as they were published.
The Release Notes for the latest major version of Taipy can be found in this page.
Unsupported released versions
Only the current and previous major versions of Taipy are supported.
Therefore, since Taipy 4.0 was shipped, we no longer provide support for Taipy 1.x and 2.x. We accordingly removed the documentation for the legacy Taipy versions from public access.
Community edition: 3.1¶
Published on 2024-03.
taipy
3.1 contains the latest
taipy-config
3.1,
taipy-gui
3.1,
taipy-core
3.1,
taipy-templates
3.1, and
taipy-rest
3.1 packages.
New Features¶
taipy
3.1.0
- Taipy and all its dependencies now support Python 3.12.
See Python documentation for details.
taipy-gui
3.1.0
- The
chart
control has a new property called figure that expects an instance ofplotly.graph_objects.Figure
. This class is provided by the Plotly Open Source Graphing Library for Python so you can create all sorts of graphs in Python.
See thefigure
property of thechart
control and the section on the figure property for more information. - The
part
block has a new property called content that lets developers integrate any third-party library that can generate HTML.
See the documentation for thepart
block and the examples using content providers for more information. - A new control called
date_range
is available if you need to represent and edit date ranges in your application pages. - A new control called
login
is available if you need users to authenticate in your application.
taipy-core
3.1.0
- The
DataNode.filter()
method and the indexing/filtering style now also support filtering a Numpy array, a list of objects, and a list of dictionaries.
For more information, please refer to Filter a data node. - You can now append new data to a data node using the
DataNode.append()
method. The method is available forCSVDataNode
,ExcelDataNode
,JSONDataNode
,ParquetDataNode
,SQLDataNode
,SQLTableDataNode
, andMongoCollectionDataNode
.
For more information, please refer to Append a data node. - A new class called
Submission
holds meta-data (such as its status or submission date) related to a submitted entity:Scenario
,Sequence
, and/orTask
.
The functiontaipy.get_latest_submission()
returns the last submission of a given entity.
For more information, please refer to Submission. taipy.submit()
,Scenario.submit()
,Sequence.submit()
, andTask.submit()
now return aSubmission
entity.- A new predefined data node named
S3ObjectDataNode
has been implemented.
For more information, please refer to S3ObjectDataNode.
Improvements and changes¶
taipy
3.1.0
- Task nodes in the
scenario_dag
control dynamically reflect the status of related jobs for the user that submitted scenarios or sequences. - The
scenario
control lets you add, modify, and edit sequences. - The
data_node
control can now represent collections.
taipy-gui
3.1.0
- The
table
control supports enumerated values. That allows for a better user experience when users edit cell values.
See the section on enumerated values in tables for the details. - The
toggle
control appears as a switch button if its value property holds a Boolean value.
taipy-core
3.1.0
- The
modin
exposed type as been deprecated. When used, a fallback on Pandas is applied.
See issue #631 for details. - Running twice the Orchestrator service raises an exception to prevent running multiple instances at the same time.
- Running the Orchestrator service or creating an entity by
taipy.create_scenario()
ortaipy.create_global_data_node()
blocks the Configuration from being modified.
Significant bug fixes¶
taipy
3.1.1
- Data is not shown or not automatically refreshed in
Data Node viewer.
See issue #908 and issue #950. - Data Nodes holding dates may not show in
Data Node viewers.
See issue #1043.
taipy-gui
3.1.0
- Selectors with dropdown menus cannot be deactivated.
See issue #894. - Problems scoping non-global variables used in Partials.
See issue #561. - Important error messages are mangled.
See issue #560.
taipy-core
3.1.1
- The signatures for
Config.configure_sql_data_node()
,Config.configure_s3_object_data_node()
, andconfigure_core()
methods are out-of-date.
See issue #1014.
Enterprise edition: 3.1¶
Published on 2024-03.
This release contains all of taipy
3.1 as well as
additional features.
New Features¶
- A new job execution mode named cluster mode is available. It enables to run the jobs on a cluster of dedicated machines in a remote, distributed and scalable environment.
Community edition: 3.0¶
Published on 2023-10.
!!! warning Error(#1180) when downgrading from Taipy 3.1 to Taipy 3.0
If you are experiencing an error downgrading to Taipy 3.0, please
reinstall Taipy with options `--no-cache-dir -I` like so:
`pip install --no-cache-dir -I taipy==3.0.0`
New Features¶
taipy
3.0.0
- Taipy application can now be run with the Taipy command-line interface (CLI) using the
taipy run
command. For more information, refer to Run application in Taipy CLI.
taipy-gui
3.0.0
- A new package holds the Page Builder API: a set of classes that let you define the pages for your application entirely with Python.
- You can now update variables on all clients using the shared variables concept. See
the
Gui.add_shared_variable()
andState.dispatch()
methods for details. - You can now invoke a callback for all clients using the
broadcast_callback()
function. - The
slider
control can now handle several knobs, allowing for range selection.
Please check the example for more information. - The
file_download
control now lets developers generate the file content dynamically, at download time.
Please check the example for more information. - A new CSS class called toggle-navbar was added to the
Stylekit to give a
toggle
control the aspect of anavbar
. - The
chart
control now supports the treemap and waterfall chart types.
taipy-core
3.0.0
- A production version of a Taipy application can now be provided with migration functions to
automatically migrate entities and keep them compatible with previous versions.
For more information, refer to Production mode. - A
GLOBAL
scope data node can be created from a data node configuration calling the newtaipy.create_global_data_node()
method.
For more information, refer to Create a data node. - A data node configuration can be built from an existing data node configuration. For more information, refer to the documentation page on data node configuration.
- A new class
Submittable
models entities that can be submitted for execution. It is an Abstract class instantiated byScenario
andSequence
. It can be handy to use the new followingSubmittable
methods:Submittable.get_inputs()
retrieves input data nodes of aSubmittable
entity;Submittable.get_outputs()
retrieves output data nodes of aSubmittable
entity;Submittable.get_intermediate()
retrieves intermediate data nodes of aSubmittable
entity;Submittable.is_ready_to_run()
checks if an entity is ready to be run;Submittable.data_nodes_being_edited()
retrieves data nodes that are being edited of aSubmittable
entity.
- New functions exposed by the
taipy
module:taipy.is_deletable()
checks if an entity can be deleted;taipy.exists()
checks if an entity exists.
- The encoding type of CSVDataNode and JSONDataNode can now be configured using the encoding parameter. For more information, please refer to Configure a CSVDataNode and Configure a JSONDataNode sections.
taipy-template
3.0.0
- A new template named "scenario-management" is available. For more information on creating a new Taipy application with the new "scenario-management" template, refer to the documentation page on templates.
Improvements and changes¶
taipy-gui
3.0.0
The action parameter of the
on_action
callback was removed for every control.
The signature of all on_action() callback functions are now unified to the following:- state (
State
): the state of the client invoking that callback; - id (str): the identifier of the visual element that triggers that callback;
- payload (dict): a dictionary that provides additional information to the callback.
This dictionary now has the additional action key that is set to the action name. This change not only impact the on_action callback of all controls that support it, but in an exactly similar manner the following callback signatures:
- state (
- The
navigate()
function has an additional parameter params that is used to add query parameters to the requested URL. The query parameters can be retrieved in theon_navigate
callback. - The on_action parameter of the
download()
function can be a function and not just a function name. - Setting the debug parameter of
Gui.run()
to True provides stack traces to be shown in the console when exceptions occur in user code.
taipy-core
3.0.0
A
ScenarioConfig
graph is now created directly fromTaskConfig
andDataNodeConfig
. Consequently,PipelineConfig
has been removed. For more information, refer to Configure a scenario.The
Pipeline
object has been removed and replaced bySequence
. A sequence is held by aScenario
and represents a subset of its tasks than can be submitted together independently of the other tasks of the scenario. For more information, refer toScenario.add_sequence()
andScenario.remove_sequence()
.Scope.PIPELINE
has been removed from possibleScope
values.- The
root_folder
,storage_folder
,read_entity_retry
,repository_type
, andrepository_properties
attributes of theGlobalAppConfig
have been moved to theCoreSection
.
Please refer to the Core configuration page for details. - The
clean_entities
attribute has been removed from theCoreSection
. Correspondingly, the--clean-entities
option has been removed from the version management CLI.
To clean entities of a version, please run your application in development mode, or delete your version with the--delete
CLI option. For more information, refer to Taipy command-line interface - The deprecated
nb_of_workers
attribute of the JobConfig has been removed. - The deprecated
parent_id
attribute of a DataNode, Task, Pipeline, or Scenario entity, has been removed. - The deprecated
last_edition_date
andedition_in_progress
attributes of a DataNode entity have been removed. - The deprecated
DataNode.lock_edition()
andDataNode.unlock_edition()
methods have been removed. - The deprecated
taipy.create_pipeline()
method has been removed. - Function
DataNode.track_edit
has been made public.
taipy-template
3.0.0
- The default template also supports creating a multi-pages application with Orchestrator and Rest services. These options are available when creating a new application from the template.
- The "multi-page-gui" template has been removed. Please use the default instead to create a Taipy multi-pages application.
Significant bug fixes¶
taipy-gui
3.0.0
- The callback function set to the on_action parameter of the function
download()
may be called too early. It is now ensured to be invoked after the download operation is performed.
See issue #916. - Setting the properties property of a visual element as the returned value from a function may not succeed. See issue #897.
- Variables imported by an
import *
directive are not handled properly in the state of a callback defined in the importing module. See issue #908. - The
date
control does not use the format property if with_time is not set.
See issue #909. - The
date
control uses thedatetime.date
type and does not apply time zones if time is not involved.
See issue #895 and issue #923. - Updating a
chart
control data may cause data congestion or display flickering.
See issue #864 and issue #932. - Selection in a
chart
with type pie type is not properly handled.
See issue #919. - Hover text doesn't show properly in a
selector
that is crowded.
See issue #927. - Options with a long text in a
selector
cannot cbe deselected.
See issue #917. - The
table
control does not support undefined date values from Pandas data frames.
See issue #886.
taipy-core
3.0.0
- When running the Orchestrator service in development mode, changing the name of the function used by a
task then running the application again would raise an error.
See issue #743.
Enterprise edition: 3.0¶
Published on 2023-10.
This release contains all of taipy
3.0 as well as
additional features.
New Features¶
- Python functions including scenario management methods can be scheduled to run at a specific
time using the new
taipy.Scheduler
API. For more information, refer to Schedule a method.
Improvements and changes¶
- The job recovery mechanism is now only available when the Orchestrator service is run.
Community edition: 2.3¶
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.
New Features¶
taipy
2.3.0
- Scenario and Data Management Controls
Taipy comes, in thetaipy
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 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.0
- 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 thepart
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.
taipy-core
2.3.1
-
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.
-
2.3.0
- 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()
andget_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¶
taipy
2.3.2
taipy-gui
2.3.2
- 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
- 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.
taipy-core
2.3.0
- 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
Significant bug fixes¶
taipy-gui
2.3.0
- 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.
Deprecations¶
taipy-core
2.3.2
- The
Config.configure_default_data_node()
method has been deprecated. TheConfig.set_default_data_node_configuration()
method should be used instead. - The
Config.configure_task_node()
method has been deprecated. TheConfig.set_task_node_configuration()
method should be used instead. - The
Config.configure_pipeline_node()
method has been deprecated. TheConfig.set_pipeline_node_configuration()
method should be used instead. - The
Config.configure_scenario_node()
method has been deprecated. TheConfig.set_scenario_node_configuration()
method should be used instead.
2.3.0
PipelineConfig
has been deprecated and will be combined withScenarioConfig
in future updates.taipy.create_pipeline()
has been deprecated.
Community edition: 2.2¶
Published on 2023-04.
taipy
2.2 contains the latest
taipy-config
2.2,
taipy-gui
2.2,
taipy-core
2.2 and
taipy-rest
2.2 packages.
New Features¶
taipy-gui
2.2.0
- A default set of stylesheets are installed with Taipy GUI so that, by
default, applications benefit from a homogeneous and good-looking
style. This is called the Stylekit.
The Stylekit can be easily customized to fit your application design's requirements. - The
table
andchart
controls have a new property called rebuild that can be used if you need to entirely change the data they rely on, including their structure.
Improvements and changes¶
taipy-gui
2.2.0
- The default property name for the
part
block was changed from render to class_name to allow for directly using the style classes from the Stylekit.
Please check the section on Styled Sections for more information. - The
expandable
block has a new property called on_change enabling to set a specific callback when the block is expanded or collapsed. - Better error messages when parsing Markdown content.
- Better support for auto-completion in IDE for the
Gui.run()
configuration parameters, based on a generated Python Interface Definition file. - The status entry point now provides information about the loaded element libraries and the elements they define.
- The
navigate()
function and the page property of thepart
block can now use, as their target, any URL. In the context of apart
block, the page will be rendered in an iframe.
See issue #621.
Significant bug fixes¶
taipy-gui
2.2.0
- Bound variable scope issues fixed when used by elements defined at the root page
level.
See issue #583. - Filters management fixed in the
table
controls.
See issue #667. - Communication with the server may break.
See issue #695.
taipy-core
2.2.3
- Error raised when running Orchestrator service in development mode after a function rename in the Config.
See issue #560.
2.2.2
- PostgreSQL and MySQL engines do not support "driver" argument.
See issue #544.
To avoid conflict between engines, the default value of the db_driver parameter in a SQL or a SQL table data node configuration has been removed.
Studio: 1.0¶
Published on 2023-02.
The first release of the
Taipy Studio
extension to Visual Studio Code.
Taipy Studio brings programmers tools that significantly improve productivity when building Taipy applications.
It mainly provides:
- A graphical editor for building configuration files, so one does not have to code configurations in Python any longer;
- IntelliSense applied to the Markdown syntax extension that Taipy GUI uses to define the visual elements in the interface pages.
You can refer to the Taipy Studio User Manual section for more information.
Community edition: 2.1¶
Published on 2023-01.
taipy
2.1 contains the latest
taipy-config
2.1,
taipy-gui
2.1,
taipy-core
2.1 and
taipy-rest
2.1 packages.
Please refer to the Migration page for details on how to migrate from version older than 2.1.
New Features¶
taipy
2.1
- Taipy and all its dependencies now support Python 3.11.
See Python documentation for details.
taipy-gui
2.1.0
- A security feature has been added: the file
.taipyignore
, located next to the Python main file, can list the paths that you want to prevent access to.
See issue #501 or this section for details. - Charts can use the new
Decimator
class to cleverly filter data points out to significantly improve performance.
See the paragraph on large datasets for specific information. - Charts now support polar, funnel, candlesticks and many other types of charts.
See the chart control section for details. - Charts now support the dark theme automatically.
- Tooltips can be set on individual table cells.
See the example for more information. - Long running callbacks have
been improved to allow for easily returning a value.
See the documentation of theinvoke_long_callback()
function or the issue #547 for more details. - Developers can specify the location of the Taipy webapp, for debugging purposes.
The--webapp-path
command line option allows to specify that location.
See issue #564.
taipy-core
2.1.0
- New version management system for Taipy applications. Users can now run an application in development
mode, save a version of the application as an experiment version, re-run older experiment versions,
and push a version to production.
See the Version management system documentation page for more details. - New data node named MongoCollectionDataNode. It represents the data from a MongoDB collection.
- New data node named ParquetDataNode. It represents tabular data stored in the Apache Parquet format.
- Added support for Modin as a new exposed type.
- Running the Orchestrator service is required to execute jobs. See
Orchestrator().run()
method. - The parent entities of a data node, a task, or a pipeline can be accessed via
DataNode.get_parents()
,Task.get_parents()
, orPipeline.get_parents()
, or by passing the data node entity, task entity or pipeline entity to the functiontaipy.get_parents()
. - New data node property expiration_date computed adding the validity_period duration to the last_edit_date of the data node.
- New data node property is_up_to_date equals to
True
if the data node has not expired (refer to expiration_date attribute).False
otherwise. - The sql repository_type is now available on community edition to store Taipy entities in an SQL database.
Improvements and changes¶
taipy-gui
2.1.0
- The Pie charts now use the values property to set values instead of x.
See Pie charts for details. - Unselected data points or traces in charts now preserve their original opacity.
See issue #496. class_name
is now a dynamic property.
See issue #480.- The allow_unsafe_werkzeug option of Werkzeug (that Flask depends on for the WSGI part) is forced to True when the Gui instance is run in Debug mode, because of a change in policy in recent updates.
taipy-core
2.1.1
- Add overload type descriptions for the
taipy.get()
method that supports multiple different combinations of argument types.
2.1.0
- Deprecation of the data node cacheable property. It is replaced by skippable property on tasks.
The mechanism remains unchanged but instead of setting cacheable property to
True
for all the outputs of a task that can be skipped, just set the task skippable property toTrue
. - The last_edit_date attribute of a data node is now updated when the corresponding data is modified by either a Taipy task execution or an external factor. This behavior is limited to file-based data nodes: CSV, Excel, JSON, and pickle data nodes only.
Significant bug fixes¶
taipy-core
2.1.2
- The version required for openpyxl has been downgraded from "openpyxl>=3.0.7,<4.0" to "openpyxl>=3.0.7,<3.1" to match the version used by Modin.
Community edition: 2.0¶
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.
New Features¶
taipy-gui
2.0.0
- 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
andon_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.
taipy-core
2.0.0
- 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
, orBLOCKED
can be canceled. When canceling the job, its subsequent jobs will be abandoned, and their statuses will be set toABANDONED
. When the cancel method is called on a job whose status is eitherRUNNING
,COMPLETED
, orSKIPPED
, its subsequent jobs will be abandoned while its status remains unchanged. A job whose status isFAILED
,CANCELED
orABANDONED
cannot be canceled. - Taipy Orchestrator can now be run as a service by using
Orchestrator().run()
ortp.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.
taipy-config
2.0.0
- The new
taipy-config
package was exposed to be used by any other Taipy package for configuration and logging.
Improvements and changes¶
taipy-gui
2.0.0
- 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.0
- 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.
Significant bug fixes¶
taipy-gui
2.0.2
image
control may not render properly.
See issue #436.- Clarify and improve the
editable
(andeditable[]
) property in thetable
control.
See issue #464. - [gui] section in configuration files breaks the application.
See issue #469.
2.0.1
- Bar charts' "barmode" set to "stack" is broken.
See issue #445.
taipy-core
2.0.4
- Do not update
last_edit_date
when a job fails or is abandoned. See issue #366.
Deprecations¶
taipy-core
2.0.0
- The field
*nb_of_workers*
within the Config has been deprecated in favor of*max_nb_of_workers*
.
Enterprise edition: 2.0¶
Published on 2022-10.
New Features¶
- SQLLite or MongoDB databases can now be used as alternatives to the filesystem to store Taipy entities.
Improvements and changes¶
- Simplification of the authentication API.
Community edition: 1.1¶
Published on 2022-06.
taipy
1.1 contains the latest
taipy-gui
1.1,
taipy-core
1.1 and
taipy-rest
1.1 packages.
Improvements and changes¶
taipy-gui
1.1.3
- The client-server communication settings are extended to accommodate various Flask deployment scenarios.
See the documentation for the async_mode parameter toGui.run()
for more information. - Implicit re-run of the
Gui
instance in Notebook environments.
See issue #320. - Test server/client versions for safe interoperability.
See issue #323. - Allow the edition of specific table columns.
See issue #366.
1.1.0
- The
State
instance can be initialized in a user-defined function. See the on_init attribute of theGui
class for more details. - Page definitions and the bound variables can be isolated in a module to clarify the
application code organization.
See this section for details. - The chart control
can display geo-referenced data on top of maps.
See this example for details. - The input and
- slider
controls have a new change_delay property that lets you tune how fast you want to propagate
changes.
This allows for a better user experience. - The input control has a new password property that, if True, obscures the user input.
- The input,
- number and selector controls have a new label property that lets you display a label inside the control.
- The layout block has new syntax that makes it easier to define a repetition of a column definition.
- Support for multiple assignments to variables in on_change().
taipy-core
1.1.0
- Execution modes: "development" mode (default) runs tasks in a synchronous way one task at a time, while "standalone" mode runs tasks in an asynchronous and parallel way using sub-processes.
- Retry policy to read entities: the global configuration attribute retry_read_entity indicates the number of times Taipy will retry in case of error.
- Performance improvements when reading and writing entities.
Significant bug fixes¶
taipy-gui
1.1.3
- Error fixed when modifying a State dictionary entry in a callback.
See issue #356. - Boolean values not editable in tables.
See issue #365. - Crash fixed when using a dictionary in the labels property of the slider control.
See issue #379.
1.1.0
- Concurrency issues were fixed.
- The attr_list extension can
be used to style individual Markdown elements without the need for a CSS file.
See issue #185. - Taipy supports HTTPS via reverse proxies.
See issue #263.
Deprecations¶
taipy-core
1.1.0
- The path attribute of
DataNodeConfig
, for CSV, Excel and Pickle types is now deprecated.
default_path must be used instead: it is the default path to use when instantiating a data node from the config. Note that the attribute in theDataNode
entity is still called path. - The last_edition_date attribute of data nodes is now deprecated.
last_edit_date must be used instead. - The edition_in_progress attribute of data nodes is now deprecated.
edit_in_progress must be used instead.
Enterprise edition: 1.1¶
Warning
Published on 2022-06.
This release contains all of taipy
1.1
as well as additional features.
Features¶
- User authentication.
- Authorization checks for all entities.
- Job recovery mechanism on application restart.
- Page generation based on the user's identity.
Community edition: 1.0¶
Published on 2022-04.
taipy
1.0 contains the latest
taipy-gui
1.0,
taipy-core
1.0 and
taipy-rest
1.0 packages.
Features¶
taipy-gui
1.0.0
- Multiple pages support
- Binding to global variables
- Python expression support in visual element properties
- Initial visual element set including tables and charts.
- Page content support for Markdown and HTML
- Jupyter Notebook support
taipy-core
1.0.0
- Full configuration system
- Data node management (read/write/filter/cache)
- Predefined data nodes (CSV, SQL, EXCEL, PICKLE)
- Scenario and cycle management
- Smart scheduling and execution (Scenario, Pipeline, and Task submission)
taipy-rest
1.0.0
- REST APIs on top of
taipy-core