Skip to content

fix: use relative import in intesisbox.py to prevent system package conflict#70

Open
kesawi wants to merge 1 commit into
jnimmo:masterfrom
kesawi:fix/intesisbox-relative-import
Open

fix: use relative import in intesisbox.py to prevent system package conflict#70
kesawi wants to merge 1 commit into
jnimmo:masterfrom
kesawi:fix/intesisbox-relative-import

Conversation

@kesawi
Copy link
Copy Markdown

@kesawi kesawi commented May 14, 2026

intesisbox.py used an absolute import (from pyintesishome.intesisbase import IntesisBase) which breaks when pyintesishome is vendored inside another package, causing the system-installed package to be loaded instead of the vendored copy. All other files in the package use relative imports — this change makes intesisbox.py consistent with the rest of the package.

No impact on non-vendored use since relative imports within a package resolve correctly regardless of how the package is installed.

…onflict

intesisbox.py used an absolute import which breaks when pyintesishome is
vendored inside another package, causing the system-installed package to
be loaded instead of the vendored copy. Change to a relative import
consistent with all other files in the package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant