BUG-__main__ is not recognized when using notebooks

[AlexandreSajus]

Description When selecting a function coming from main.py in a task node in Taipy Studio, it will define it in the config as main .function When running Taipy Core in Python scripts, taipy understands that main is in main.py When running in a notebook, taipy does not find the function

How to reproduce

Create a main.py with a function. Create a config with a task node calling that function: the config will save it as main .function Run the scenario inside a notebook; the notebook should return an error explaining that module main has no attribute function.

Expected behavior Don't convert main.py to main inside the config file, or help notebooks recognize that main can be the main.py file.

Runtime environment Please specify relevant indications.

• Taipy version: 2.2.0
• OS: Windows

[trgiangdo]

• Assume that there is a main.py file containing a preprocessing() method.

  

• When choosing a function to configure a new task, the main.py module is replaced by __main__ module.

  

• I propose we can:

  1. Replace __main__ by the main.py (when choose __main__ module, the actual module in the TOML file will be main.py).
  2. Allow the user to either choose __main__ or main.py.

[trgiangdo]

Also, there can be a hidden bug to this.

Assume that the project has:

• an app.py file which runs Taipy services, and
• an utils.py file which contains the methods for tasks.

Sometimes there can be a confusion of which file is actually the __main__ module.

Like in this case, the utils.py is now the __main__ module.

[FredLL-Avaiga]

in studio, the user can specify which is the main module: right click in the file explorer view :-)

[FredLL-Avaiga]

Allow the user to either choose main or main.py

I think that would be the easiest solution for everyone.

[trgiangdo]

in studio, the user can specify which is the main module: right click in the file explorer view :-)

Oh, I did not know that. Sorry 🥲

Allow the user to either choose main or main.py

I think that would be the easiest solution for everyone.

Yes I agree. Let's discuss with the CS team