Great, Thank you,
I was not sure that the version printed in the head of listing was read in the steering file or in the systel.cfg or if it was a kind of signature of the execution.
v6p1 and v6p2 on one side and v6p3 and v7p0 on the other side do not have exactly the same structure.
As I can't have two different PATH related to the directory of XXX.py :
- if PATH is v6p2 or v6p1/pytel ...telemac2d.py -c gforv6p3 returns...
The code requested is not installed on this system : telemac2d
- if PATH points to v6p3/scripts/python27 ... telemac2d.py -c gforv6p2 returns ...
I could not locate the source code in C:\opentelemac\v6p1\sources
Either the root key in your cfg file is not valid, or you are using a past version of the system.
Anyway...it's not a big deal, I just have to write the full path to telemac2d.py in the command.
I guess, "python scripts are not linked to version" is true for v6p1 and V6p2 one one side and v6p3-v7p0 on the other.