From a1e2a03853bb6efebfc0e09679fef829d87745a9 Mon Sep 17 00:00:00 2001 From: Olivier Hallot Date: Wed, 17 Apr 2019 16:30:22 +0200 Subject: Fix PRODUCTNAME Change-Id: I11a5ac0e5c1a33eb6f28c32024dab0fceec91e14 Reviewed-on: https://gerrit.libreoffice.org/70888 Tested-by: Jenkins Reviewed-by: Olivier Hallot --- source/text/sbasic/python/python_import.xhp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/text/sbasic/python/python_import.xhp b/source/text/sbasic/python/python_import.xhp index 43ec281078..d8dc7a61d8 100644 --- a/source/text/sbasic/python/python_import.xhp +++ b/source/text/sbasic/python/python_import.xhp @@ -22,7 +22,7 @@ PythonLibraries

Importing Python Modules

- LibreOffice Python scripts come in three distinct flavors, they can be personal, shared or embedded in documents. They are stored in varying places described in Python Scripts Organization and Location. In order to import Python modules, their locations must be known from Python at run time. + %PRODUCTNAME Python scripts come in three distinct flavors, they can be personal, shared or embedded in documents. They are stored in varying places described in Python Scripts Organization and Location. In order to import Python modules, their locations must be known from Python at run time. This mechanism is illustrated for file system based modules and document based modules. Exception handling is omitted for clarity. The terms library or directory, scripts or modules are used interchangeably. A Python macro refers to a function inside a module. Note that <User Profile>/Scripts/python/pythonpath local directory is always explored when running a Python macro from <User Profile>/Scripts/python.

File System module import

-- cgit