Importing my user defined modules

[ztminhas]

Good Morning,

I have made a set of python modules (using APSO) in the “My Macros” section. I would like to use them in my base application. The python code within my base file should be able to import my modules. however i get the error:

<class 'ModuleNotFoundError'>: No module named 'ModuleDbConnections'
  File "D:\Program Files\LibreOffice\App\libreoffice\program\pythonscript.py", line 1057, in getScript
    mod = self.provCtx.getModuleByUrl( fileUri )
  File "D:\Program Files\LibreOffice\App\libreoffice\program\pythonscript.py", line 494, in getModuleByUrl
    exec(code, entry.module.__dict__)
  File "vnd.sun.star.tdoc:/728267628/Scripts/python/LbryCuttingDescriptions/ModuleCuttingDescriptions.py", line 8, in <module>
  File "D:\Program Files\LibreOffice\App\libreoffice\program\uno.py", line 346, in _uno_import
    return _builtin_import(name, *optargs, **kwargs)

[mikekaganski]

More context is needed: most desirable is some simple action sequence allowing to repro the problem from scratch on any system. But at least, what is in the respective import directive in your python code within your base? Or the URL in the call to getModuleByUrl / getScript.
vnd.sun.star.tdoc:/728267628/... looks odd. The vnd.sun.star.tdoc: means document context; it’s unexpected that it is followed by only a single slash. But maybe it’s OK, since it seemingly works…
The D:\Program Files\LibreOffice\App\libreoffice\program path is unusual, but likely you have some custom preference, making the actual LibreOffice installation path nested under additional LibreOffice\App.

[Wanderer]

IMHO there was a discussion (recently?) where they mentioned APSO to hide pythonpath. This would prevent using the internal use of modules in python without special counter-measures.
.
Check the following as explanation, there are also some work-arounds (above the linked entry):

Using APSO to embed scripts in python, how to import functions from one module to another?

APSO hides the pythonpath subdirectory. In order to fix this, I once submitted an APSO pull request, but the developer rejected the modified code, saying that APSO is designed for simple macros only, not for extension development or other large projects where one module imports another. So, to answer your question: The proper way is to not use APSO, and instead do things the direct way using pythonpath. Yes, it’s possible to mess with sys.path to get it to work anyway, but I would not recomm…

[ztminhas]

@Using APSO to embed scripts in python

pythonpath

Thank you. I will check on that.