New post
AllAccepted answers
Guillaume Rongier · Jan 16, 2023

My guess is that you try to use some outdated nativeapi drivers.
https://github.com/intersystems/quickstarts-multimodel-python <- outdate more than 3 years old
I encourage you to use this git for drivers : https://github.com/intersystems-community/iris-driver-distribution

If you are looking for python expérience on IRIS have a look at those git :

BTW : a more complete DB-API and SQL Alchemy support is under development

Guillaume Rongier · Dec 20, 2022

Just to be clear, the remove of the private web server is just for IRIS and IRIS for Health. IRIS and IRIS for Health community edition still has the private web server.

Then, the question is, what is the cost of this decision for end-developers like most of here.

I would say not that much as you think. The main raison is that most of the developer use the community edition. And the community edition still has the private web server. Then if you have an preinstalled IRIS, you will keep the private server.

The main cost is for the new developer that don't have an preinstalled IRIS and that don't want to use the community edition. I agree that installing a web server is not that easy if you sick on windows. But it is not that hard if you are on Linux or Mac.

For windows developers, may be we can provide simple installer that install a web server and configure it for IRIS.

Now, if we take a step back on the ease of use. I think, this decision is a good one, because it's the first major step of breaking down the monolith. From this point, we can start to make the product more modular. And of course, there is a lot of work to do.

I agree with you that we must improve our client libraries and drivers. Put them in direct distribution, make them more easy to use and with modern features.

Guillaume Rongier · Dec 19, 2022

This post has been edited to make use of the IRIS Embedded Python Wrapper : https://github.com/grongierisc/iris-embedded-python-wrapper.

The old version :

alias irisvenv="/opt/intersystems/iris/bin/irispython -m venv .venv; rm .venv/bin/python3; ln -s /opt/intersystems/iris/bin/irispython .venv/bin/python3; source .venv/bin/activate;"

Was in fact not working, because of the irispython interpretor that doesn't support venv yet.

To make embedded python works with venv, please use :

alias irisvenv="python3 -m venv .venv; source .venv/bin/activate; pip install https://github.com/grongierisc/iris-embedded-python-wrapper/releases/download/v0.0.1/iris-0.0.1-py3-none-any.whl"

and make sure that the environment variable named IRISINSTALLDIR is pointing to the InterSystems IRIS installation directory.

export IRISINSTALLDIR=/opt/iris
Guillaume Rongier · Dec 16, 2022

Major update :

Now this module is available on Pypi:

Install with PyPI

pip3 install iris-pex-embedded-python

Import the ObjectScript classes, open an embedded python shell and run :

from grongier.pex import Utils
Utils.setup()

Known issues

If the module is not updated, make sure to remove the old version :

pip3 uninstall iris-pex-embedded-python

or manually remove the grongier folder in <iris_installation>/lib/python/

or force the installation with pip :

pip3 install --upgrade iris-pex-embedded-python --target <iris_installation>/lib/python/
Guillaume Rongier · Oct 21, 2022

Hi,

You need to fill in some environment variables that allow you to authenticate yourself and therefore connect.

The variables are :

IRISUSERNAME
IRISPASSWORD
IRISNAMESPACE

In a docker file for example :

# environment variables for embedded python
ENV IRISUSERNAME "SuperUser"
ENV IRISPASSWORD "SYS"
ENV IRISNAMESPACE "IRISAPP"

In a shell :

export IRISUSERNAME=SuperUser
export IRISPASSWORD=SYS
export IRISNAMESPACE=IRISAPP