intersystems-iris
Compatibility shim: import intersystems_iris resolves to the iris module from intersystems-irispython.
The problem
The InterSystems IRIS Python client is distributed as intersystems-irispython but imported as iris. This mismatch between package name and import name has led the community to independently converge on intersystems_iris as a more intuitive import name — and several widely-used packages depend on it:
sqlalchemy-iris(caretdev) —import intersystems_iris.dbapi._DBAPIin 4 filesdjango-iris(caretdev) —import intersystems_iris.dbapi._DBAPI as Databaseiris-kafka-python(grongierisc / ISC) —import intersystems_iris+intersystems_iris.IRIS(conn)iris-vector-graph(intersystems-community) —import intersystems_irisin bulk_loader and engine
These packages were not wrong. intersystems_iris was the intended public import name of the legacy intersystems-iris distribution before ISC renamed the package to intersystems-irispython and shortened the import to iris. This shim restores that name so all of the above packages work without modification.
import intersystems_iris # same as: import iris
intersystems_iris.connect(...) # works
intersystems_iris.createIRIS(...) # works
intersystems_iris.dbapi # works
intersystems_iris.IRIS(conn) # works
Install
pip install intersystems-iris
Pulls in intersystems-irispython automatically.
For new code
Use import iris directly. This package exists for ecosystem compatibility.
import iris
conn = iris.connect("iris://_SYSTEM:SYS@localhost:1972/USER")
Embedded Python (in-process)
When running inside IRIS via irispython, import iris is provided by the IRIS runtime — intersystems-irispython is not installed. The intersystems_iris shim still works because it imports from iris, which is always present.
# Inside irispython — no pip install needed
import intersystems_iris # resolves to the embedded iris module
intersystems_iris.sql.exec("SELECT 1")
Metadata
Release files for intersystems-iris 5.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| intersystems_iris-5.3.3.tar.gz | 2.5 kB | Without provenance | Details for intersystems_iris-5.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| intersystems_iris-5.3.3-py3-none-any.whl | Python 3 | none | any | Details for intersystems_iris-5.3.3-py3-none-any.whl |
Total release size: 5.1 kB
Release files / intersystems_iris-5.3.3.tar.gz
| Download URL | intersystems_iris-5.3.3.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ab19a34f690da6c79bf9f392fa28f3b4e51f3be5c70b040ff1cadafe1cb5454
|
|
BLAKE2b-256 checksum How to use checksums |
47d3ecc052c8fee32c36128b69c7c55b0f2d8dfb40681a0386ef2451a2435735
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / intersystems_iris-5.3.3-py3-none-any.whl
| Download URL | intersystems_iris-5.3.3-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c9a14c72e72ae69e49c8811ccfb74914c44149c787657f0db31a18d05ef2a6a
|
|
BLAKE2b-256 checksum How to use checksums |
a11986661bb151c813c9eb012d59c22c3a1f4834b036f0c92a6bf14e2ac7d951
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for intersystems-iris 5.3.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.