Skip to content

Reconsider loading of Python modules from the compstate #40

@prophile

Description

@prophile

We have support for loading custom modules for scoring mechanisms, rankers etc from compstates. Currently these are imported in the same environment as all the rest of the code, including slightly surprising modifications to sys.path.

Should/could we consider some kind of isolation - multiprocessing, subprocesses, or subinterpeters perhaps - to give these a more predictable environment, contain any leakage of changes to interpreter globals, and make it easier to clean up after a compstate is unloaded?

(From a discussion with @PeterJCLaw)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions