Python SDK Suddenly Failing to Import

Hi All,

I have databricks notebooks that import SailPoint data into database tables for auditing/backup purposes. These notebooks use the SailPoint Python SDKs and have been working fine for a year now until late last week.

The error I get is “ModuleNotFoundError: No module named ‘sailpoint.v2025’”
I get this when simply trying to import like “import sailpoint.v2025”

Trying to replace v2025 with v2026 and v3 both fail. Did something change with the versioning for these Python SDKs? I can’t find any documentation or announcement that would imply as much.

Hi @benjaminoriold

There was a change in the API Versioning strategy (post below). It was supposed to not affect any of the old endpoints (v2025/v2026/v3) and they should all still be supported until 2028/2029, but there is some chatter in there that it may have broken some integrations.

I think the consensus in there is to open a support case if you’re seeing endpoints not work that previously did.

Hi Benjamin,

You likely just need to pin your requirements.txt to the earlier version of the python SDK 1.4.2 Or you can upgrade to the latest and use the 2.0.x versions but then you will need update your code to use the new versioning strategy. We will have a script available to you in the next week or so to make switching to the SDK easier

Hi Philip,

Thanks for reaching out with help. I’m not sure what you mean though, making switching to the SDK easier?

This is an existing script that’s been using the SDK for the past year and suddenly started failing to import.

For reference this is set up in Databricks notebooks like in the examples here: SailPoint and data lake houses

We will be providing a script that you can run against your existing repo to migrate it to the new 2.x versioning strategy endpoints. It should be available by the end of this week if all goes well.

Here is the repo where the script lives: GitHub - sailpoint-oss/python-sdk-template · GitHub You can run it using python migrate_sdk.py \[target\]