Bug 179541
| Summary: | [Windows] ActivePython cannot find logilab.astng module because of logilab.common in site-package | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Basuke Suzuki <basuke> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | basuke, fujii.hironori, lforschler |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 179216 | ||
Basuke Suzuki
ActivePython's installer installs logilab-common package into site-package, but not logilab-astng. Even if WebKitPy installs third party libraries by itself and sys.path is setup correctly, the packages in site-package have an priority to be loaded which prevent to import logilab.astng in the thirdpary/autoinstalled directory.
The workaround is to install logilab-astng manually globally, but that is not the right solution.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Basuke Suzuki
python's cli argument "-S" disables site-package which solve this issue, but need to figure out for the possibility of other new issue.
Basuke Suzuki
Actually "-S" doesn't work well because it prevents to load primitive modules.
Basuke Suzuki
I confirmed this issue also happens on Mac if logilab-common is installed globally.