-
https://app.zenhub.com/workspaces/taipy-613ef328affde6000ff77fb3/issues/avaiga/taipy-gui/363
-
### Description :
The purpose is keep the decoupling between the scheduler from the dispatcher. The final target is to only have the queue in common.
This ticket is about starting the Dispatcher of …
-
Step 0:
We need to add to the release process the deployment of taipy on Conda.
- [x] Taipy
- [x] Taipy-core
- [x] Taipy-gui
- [x] Taipy-rest
First step: Deploy manually based on the [documentation…
-
-
- [x] create taipy-config containing config and logger
- [x] remove TaipyLogger from core
- [x] remove all config from core
-
**Description**
A problem arises when scenarios are submitted.
```
Traceback (most recent call last):
File "c:\Users\jacta\Desktop\Stage\Avaiga\Code\taipy-CFM\convert_old_scenarios.py", line 1…
-
The Ref manual on taipy-core is confusing, in particular the 2 entry points config and config.core.
It should be more clear.
-
Dosomething similar to
https://github.com/Avaiga/taipy-core/pull/200
-
Today we have two workflow:
- release: tag and release Taipy on Github
- Publish: Publish the Taipy package on Pypi
We should merge both.
- [ ] taipy
- [x] taipy-core
- [ ] taipy-gui
- [ ] taipy-res…
-
**What would that feature address**
It is not possible to give a callback function to change the state of one user or for all the users. For example, it will allow the user to add a callback function…