mercredi 16 décembre 2020

Callable Python object as an independent process

I've got a Python system which parses and loads a large complex object, which takes a long time to load, and some scripts which use the object.

Currently, I have it setup so I call my main function, which loads the object, and then calls the various scripts that use the object.

However, this makes development tedious, since a bug in one of the scripts means I need to reload everything.

This problem is solved by using iPython of course, but I would like to have the main loading and the scripts decoupled in production too.

Thus, I want an independent script that loads the object, and have other scripts that can call the object, almost like a daemon or a service.

I've seen there are ways of making a daemon in Python, but I'm not sure if this is the best design pattern for my use-case. What design patterns make sense here?

Aucun commentaire:

Enregistrer un commentaire