Skip to content

Limitations of relative imports #75

Open
@duckie

Description

@duckie

Relative imports can have various impacts when the package is used from an external script, since said script may execute in the right virtual env but maybe not the right python context module wise.

There is two solutions to this:

  • Expose symbols between modules in the main init file
  • Use fully qualified imports

Unfortunately, the fully qualified break the possibility to "relocate" the module, ie, making it a submodule of another, which is required here for it to be usable as Ansible module utils.

No action is specifically required, this issue is merely a reminder of previous work in case the question arise later on.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions