Skip to main content

Python SDK for Igloo Cloud

Project description

Igloo Python Connector

Igloo Python Connector is a Python wrapper for the Igloo Cloud API. It also provides additional useful methods and examples.

Installation

Note, we assume you have Python 3.9 or later already installed on your machine. If not, please download and install the latest version of Python from the official website. Also note, we recommend that you perform the installation within a Python virtual environment. See here for more info.

Once created, please activate your virtual environment and install the Igloo Python Connector package using the following command:

pip install wtwco-igloo

You should now be able to import the package in your Python code:

import wtwco_igloo

Connecting to the API

Connect to the API with device code flow:

from wtwco_igloo import Connection

connection = Connection.from_device_code(api_url, client_id, tenant_id)

# View your workspaces
print(connection.get_workspaces())

Documentation and Examples

For documentation and examples please see WTW Client Services.

Release Notes

2.0

Version 2.0 of the wtwco-igloo package is a major upgrade from the previous 1.0 release and supports all of the new features of Igloo Cloud 2025.1. The introduction of Workspaces has, however, lead to a number of breaking changes. These include:

  1. Functions for getting models, projects and calculation pools have been moved from the Connection class to a new Workspace class. You can fetch the list of workspaces in your Igloo Cloud environment by calling the new function Connection.get_workspaces. For simple examples of how to get models, projects and calculation pools in a workspace you can look at the example code in model_example.py, project_example.py and calculation_pool_example.py.
  2. Table and Column names returned by get_input_data are now capitalised according to how they have been defined in the model. Because Python is case-sensitive you may need to update any code that retrieves data from a Python dictionary that is keyed on a table or column name.
  3. Data tables that are expecting a run reference should now be updated by posting <ProjectName>\<RunName> as a string to the data table, rather than posting the run id value. Similarly when updating a data table that is expecting a reference to an uploaded file, you should use the uploaded file name rather than the id.

In addition to the changes above there are a number of new additions to the wtwco-igloo package, including:

  1. A new Workspace class representing a workspace in Igloo Cloud. This provides a new way for getting models, projects and other things that belong to the workspace.
  2. A new UploadedFile class representing an uploaded file in Igloo Cloud. This class allows you to rename and delete uploaded files as required.
  3. Some new attributes have been added to the Job class to allow you to see when a job was started and finished, as well as some other calculation job related properties.
  4. A new get_job method has been added to the Run class for getting the latest job information associated with a run.

For documentation and examples please see WTW Client Services.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

wtwco_igloo-2.0.0-py3-none-any.whl (53.6 kB view details)

Uploaded Python 3

File details

Details for the file wtwco_igloo-2.0.0-py3-none-any.whl.

File metadata

  • Download URL: wtwco_igloo-2.0.0-py3-none-any.whl
  • Upload date:
  • Size: 53.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.3

File hashes

Hashes for wtwco_igloo-2.0.0-py3-none-any.whl
Algorithm Hash digest
SHA256 7d2a79e650e8c81f7cf1ff98aa0a89f327839710a626ac703f0827108818375a
MD5 c537b326fb6bba8b9c93aca629cb6593
BLAKE2b-256 d9e8f3298a0a483434f6d2cb643fc8924b8764936faff416ac35b6a65712226a

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page