icon

Support Forum

[Frage] PythonParts SDK cannot be installed with Allplan 2025-1-7 [Gelöst]

Schlagworte:
  • Allplan
  • PythonParts
  • SDK
  • 2025-1-7
  • Plugin
  • Manager
  • Customization
uid-361146
uid-361146
06.02.2026 - 12:57

Hello everyone,

I am currently working intensively with PythonParts and want to install the PythonParts SDK to develop my own PythonParts[.]

According to the official documentation, the SDK should be installable either via the Allplan Plugin Manager or via GitHub:
pythonparts[.]allplan[.]com/2026/manual/getting_started/

Unfortunately, I am running into several issues:
The PythonParts SDK does not appear in the Allplan Plugin Manager
The download from GitHub cannot be imported via drag and drop
When importing SDK versions 2[.]0[.]0 or 2[.]0[.]1, I receive an error message stating that a newer Allplan version is required
This message does not seem correct to me, as I am working with Allplan 2025 version 2025-1-7[.]

My questions are therefore:

Are there any known limitations or incompatibilities between the PythonParts SDK and Allplan 2025-1-7?
Is there currently no compatible SDK version available for Allplan 2025-1-7?
Is there a recommended way to install the PythonParts SDK correctly with this Allplan version?
I have attached the file I tried to import as well as a screenshot of the error message[.]

Thank you in advance for your help[.]

Best regards
Fabian

Anhänge (1)

img
unabletoinstall.png
Typ: image/png
8-mal heruntergeladen
Größe: 7,22 KiB

Lösung anzeigen Lösung verbergen

bmarciniec
bmarciniec
09.02.2026 - 09:46 *

Hello Fabian,

All you described is true for ALLPLAN 2026. But you are working with ALLPLAN 2025. Please browse the PythonParts documentation for ALLPLAN 2025. You can select your version in the navigation bar, just next to the GitHub symbol.

In ALLPLAN 2025, there was no Plugin Manager yet and installing .allep packages was in its very early stages (e.g. it is no possible to uninstall). In 2026, breaking changes were introduced to Allep-Packaging standard, so that packges that work in 2025, won't work in 2026 and vice versa.

For ALLPLAN 2025, you have to download the SDK v1.1.2. You will find the link in the Getting Started Article for 2025 (or just here).

Best regards,
Bart

bmarciniec
bmarciniec
09.02.2026 - 09:46 * [Lösung]

Hello Fabian,

All you described is true for ALLPLAN 2026. But you are working with ALLPLAN 2025. Please browse the PythonParts documentation for ALLPLAN 2025. You can select your version in the navigation bar, just next to the GitHub symbol.

In ALLPLAN 2025, there was no Plugin Manager yet and installing .allep packages was in its very early stages (e.g. it is no possible to uninstall). In 2026, breaking changes were introduced to Allep-Packaging standard, so that packges that work in 2025, won't work in 2026 and vice versa.

For ALLPLAN 2025, you have to download the SDK v1.1.2. You will find the link in the Getting Started Article for 2025 (or just here).

Best regards,
Bart

uid-361146
uid-361146
09.02.2026 - 13:13

Hello Bart,

thank you very much for the clarification and the detailed explanation.
That helped a lot.

I followed your advice, downloaded the ALLPLAN 2025 SDK v1.1.2 from the Getting Started article and adjusted my setup accordingly. After that, everything worked as expected and the PythonPart is now running correctly in ALLPLAN 2025.

Best regards
Fabian