Im Allplan Connect Forum tauschen sich Anwender aus, geben wertvolle Tipps oder beraten sich bei ganz konkreten Aufgabenstellungen − auch international.
Und damit wirklich keine Frage unbeantwortet bleibt, unterstützen die Mitarbeiter des Technischen Supports ebenfalls aktiv das Forum.
Melden Sie sich jetzt an und diskutieren Sie mit!
Hello,
I tried to use the built in PythonPartSDK for the first time, and followed along the instructions.
https://pythonparts.allplan.com/2026/manual/getting_started/
If I open the created workspace, there are missing imports.
It seems not to work out of the box with Version Allplan 2026-1-4
What is possibly wrong?
Hi,
Looks like there has been some changes to pylint and it does not recognize the python paths automatically. You need to tell, what are the ALLPLAN's specific paths, it has to check for modules. Do following:
init-hook = import sys; import os; sys.path.extend(['C:\\Program Files\\Allplan\\Allplan 2026\\Prg', '<your_etc_path>\\PythonPartsFramework\\GeneralScripts', '<your_etc_path>\\PythonPartsFramework\\TestHelper', '<your_etc_path>\\PythonPartsFramework', '<your_etc_path>\\PythonParts-site-packages', '<your_std_path>\\PythonParts-site-packages', '<your_usr_path>\\PythonParts-site-packages', '<your_etc_path>\\PythonPartsFramework\\InterfaceStubs']); os.add_dll_directory('C:\\Program Files\\Allplan\\Allplan 2026\\Prg\\Plugins')
Best,
Bart
Thank you very much!
The problem is solved.
One additional request refering to this thread.
pylint works only within the folder "PythonPartsFramework"
The folder "PythonPartExampleScripts" is not affected by this adjustment.
What else is missing?