LabVIEW
Python node ignoring file extension
I've noticed that the python node is ignoring the file extension. I'm wondering if this is a bug or a feature...
This VI was running example.py. I chose example.sqc by mistake and noticed it was still returning the right value.
Hi lucian,
@lucian.grec wrote:
I've noticed that the python node is ignoring the file extension. I'm wondering if this is a bug or a feature...
This VI was running example.py. I chose example.sqc by mistake and noticed it was still returning the right value.
Why do you think it is a bug when the Python node executes the Python file that you provide with your filepath!?
("File extension" is just a concept for Windows to decide which executable might be appropriate to handle a certain file…)
Hi lucian,
@lucian.grec wrote:
Because example.sqc is a file that doesn't exist
You didn't say so in your first message…
I honestly doubt that LabVIEW itself does this. LabVIEW is mostly file ending agnostic as far as the underlaying platform allows that and for instance will happily load a file with any ending as a VI as long as its internal file structure is indeed a VI.
Python as multiplatform application is also fairly file ending agnostics. And it seems that it even has a feature in the API, that LabVIEW uses to interface to the Python engine, and this feature tries to attempt to load a file with alternative file ending if it couldn't find the indicated file. Most likely this comes from the fact that you have both source and compiled files in Python with the ending .py and .pyc. This feature makes sure that even if the user specifies explicitly a pyc file, that it will still work when there is actually a py file in that location but no pyc file (or when loading of the pyc file failed because it is not in the same version as the current Python execution engine).
