Why is dateutil library available on only some of my Ignition deployments?

Hi, we developed a feature to implement a maintenance calendar of sorts. We ended using dateutil and dateutil.rrule to support recurring events and such. Initially that library appeared to be built-in (included with Ignition) but as we have gone to deploy the feature to other servers we found that library is not present on some Ignition installations.

I suspect the difference may be associated with Ignition modules that are installed on some and not others (Web Dev module and/or Kymera Influx DB module). I'm working to confirm that.

Is anyone aware of other possibilities that may cause the dateutil library to be available on some Ignition deployments and not others?

UPDATE: Both modules in question are installed on the Ignition server that is missing the dateutil library so missing modules does not appear to be the cause.

I don't think this is part of the standard python library. You or somebody else must have installed it on those servers.

4 Likes

Indeed, it appears dateUtil was a dependency for the boto3 library we added to /usr/local/bin/ignition/user-lib/pylib/site-packages.
My confusion stemmed from the fact that I found dateUtil it at /usr/local/bin/ignition/user-lib/pylib/dateutil on one of our servers, rather than the site-packages directory where we intended our additional libraries to exist. Likely our own misplaced copy attempt.

@Kevin.Herron, thanks for the quick response.