Recently I embarked upon a mission, and that mission was to package my Ignition project, which was built based on my scripting needs, but did not make use of all System Functions.

As time passed the project grew along with my needs, but after a comment made by RadicalRumin at Inductive Automation Forum, I got the boost I needed to implement all System Functions, and created branches for each active version.

Almost a year after RadicalRumin’s comment, a user by the name kgamble commented about using Ignition on Visual Studio Code, something I had not been able to accomplish. And their comment did not resonate until almost a year later.

So, a couple of months ago I started experimenting with packaging Ignition, and all that it entails. But after adding a file, and trying python install, I was still not able to get code completion on Visual Studio Code.

I finally got the courage to try PyPI, so I read the “Packaging Python Projects” tutorial, and the “Packaging and distributing projects” guide, and based my first file insipired by navdeep-G’s project, psf’s black, and requests.

Here it is in its splendor:

#!/usr/bin/env python2
# -*- coding: utf-8 -*-

"""Ignition API."""

import os
from codecs import open

from setuptools import find_packages, setup

here = os.path.abspath(os.path.dirname(__file__))

about = {}
with open(os.path.join(here, "src", "system", ""), "r") as f:
    exec (, about)

with open("", "r", "utf-8") as f:
    readme =

    package_dir={"": "src"},
        "Intended Audience :: Information Technology",
        "Intended Audience :: Manufacturing",
        "License :: OSI Approved :: MIT License",
        "Operating System :: MacOS :: MacOS X",
        "Operating System :: Microsoft :: Windows",
        "Operating System :: POSIX :: Linux",
        "Programming Language :: Python",
        "Programming Language :: Python :: 2 :: Only",
        "Programming Language :: Python :: 2.7",
        "Topic :: Software Development :: Libraries :: Python Modules",
        "Topic :: Software Development :: Testing :: Mocking",

Finally, I published it into PyPI as ignition-api for the pure Python code, and ignition-api-jython for the Jython implementation.

But calamity struck. I was getting an error when trying to install the package on Jython: “ERROR: No matching distribution found for setuptools>=40.8.0”. But I found that Jython 2.7.2 comes with version 41.0.1, so it didn’t make sense. What was this madness?

Then I tried to install youtube-dl from GitHub releases, and it succeeded! What was the difference between that project and mine? It turned out, that just like normanius mentioned on an issue they created, the culprit was the presence of pyproject.toml.

I was using pyproject.toml for configuring black and pydocstyle, but nothing else. So, an easy fix was to move all settings for flake8, isort, and pydocstyle into setup.cfg and create a workflow for checking code quality using pylint and black.

name: CI

on: [push, pull_request]


    runs-on: ubuntu-latest

    - uses: actions/checkout@v2
    - name: Set up Python 3.9
      uses: actions/setup-python@v2
        python-version: 3.9
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        python -m pip install pylint
        python -m pip install black
    - name: Checking the code with black
      run: |
        black --check --line-length 79 --target-version py27 src
    - name: Analysing the code with pylint
      run: |
        pylint src

A small diversion, GitHub actions’ starter workflow for pylint is essentially broken. And I have a PR that should fix that: actions#1108.

And that did it!

Happy ending? No.

I continued refactoring my project, and moved some duplicate code to the corresponding package: com.inductiveautomation. Code, code, code. Type, type, type. Problems arose.

On my “Configuring Jython in PyCharm” guide I wrote about having issues with Jython 2.7.2 when it was set as the project interpreter, but now 2.7.1 doesn’t work either. No big deal, right? They’ll fix both issues I’ve submitted, right? PY-44759 and PY-50491, right? Right? Maybe.

But! There’s always a but. Jython fails to import modules/subpackages under com.inductiveautomation. See: jython#131. And that, my friends, is what made me pull the plug on Ignition’s jython branch, and marking ignition-api-jython as Inactive.

Could this be fixed? I don’t think so, as Jython is somewhat a graveyard at this moment, and I don’t have the knowledge nor interest in working on a possible fix. But still, I decided to move the jython branch to its own repo (ignition-api-jython) in case there is a solution in the future, or if someone is willing to fork it.

Finally, I learned about automating publishing to PyPI via GitHub actions, as well as moving away from and use pyproject.toml and setup.cfg instead, and installing Python packages’ extras and using them for pre-commit. But that, my friends, will be a story for another time.

Thanks for reading. And happy coding.