Sorry, I misunderstood your reply. I thought with "3)..." you were referring to MY number 3), but you probably referred to your sys.path?
I cannot add your code (print (sys.path)?) in my program to see what the variable contains because the execution of main is stopped already during the initialization of the pseudo code.
Yes, I still am using the long paths. I agree that that is ugly and requires a lot of typing, but to organize the many files on the disk in a number of folders, it's not bad. And in the python manuals I see no mentioning of a limit on the path length? Additionally since the path is constructed by the python installer itself, I assume that also the long path should work? If that long pathname would not work, then there is an error in the default installer logic that creates the pathname, and that should then be corrected asap.
You were correct, a colon was missing in "selfwrittenmodule.py". It "fell of" while I copied the lines of code from the real python code into the reply on this forum. The real python code has that colon.
I will test with the other 2 methods and come back here.
If I understand your comment correctly, then you save the "main.py" module and the "selfwrittenmodule.py" in the same Win10 folder. Initially I worked in that same way: the modules dedicated to the system I was writing and the "general use" modules were in the same folder, and everything worked fine. But then I wanted to change the way I organize the folders so that they beter reflect their content. Because "main.py" is code dedicated to a specific application, and "selfwrittenmodule.py" contains code that is intended to be used by many different systems (= NOT dedicated to one particular system), I would like to store them in 2 different folders: 1 for modules dedicated to the specific application, and one for "general use" modules.
To be sure that the length of the path is not causing the problem: does anybody here on this forum know about a limit on the pathname in python?
I cannot add your code (print (sys.path)?) in my program to see what the variable contains because the execution of main is stopped already during the initialization of the pseudo code.
Yes, I still am using the long paths. I agree that that is ugly and requires a lot of typing, but to organize the many files on the disk in a number of folders, it's not bad. And in the python manuals I see no mentioning of a limit on the path length? Additionally since the path is constructed by the python installer itself, I assume that also the long path should work? If that long pathname would not work, then there is an error in the default installer logic that creates the pathname, and that should then be corrected asap.
You were correct, a colon was missing in "selfwrittenmodule.py". It "fell of" while I copied the lines of code from the real python code into the reply on this forum. The real python code has that colon.
I will test with the other 2 methods and come back here.
If I understand your comment correctly, then you save the "main.py" module and the "selfwrittenmodule.py" in the same Win10 folder. Initially I worked in that same way: the modules dedicated to the system I was writing and the "general use" modules were in the same folder, and everything worked fine. But then I wanted to change the way I organize the folders so that they beter reflect their content. Because "main.py" is code dedicated to a specific application, and "selfwrittenmodule.py" contains code that is intended to be used by many different systems (= NOT dedicated to one particular system), I would like to store them in 2 different folders: 1 for modules dedicated to the specific application, and one for "general use" modules.
To be sure that the length of the path is not causing the problem: does anybody here on this forum know about a limit on the pathname in python?