Bug 179541 - [Windows] ActivePython cannot find logilab.astng module because of logilab.common in site-package
Summary: [Windows] ActivePython cannot find logilab.astng module because of logilab.co...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 179216
  Show dependency treegraph
 
Reported: 2017-11-10 12:23 PST by Basuke Suzuki
Modified: 2023-02-08 22:14 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Basuke Suzuki 2017-11-10 12:23:41 PST
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.
Comment 1 Basuke Suzuki 2017-11-10 12:25:20 PST
python's cli argument "-S" disables site-package which solve this issue, but need to figure out for the possibility of other new issue.
Comment 2 Basuke Suzuki 2017-11-10 12:32:09 PST
Actually "-S" doesn't work well because it prevents to load primitive modules.
Comment 3 Basuke Suzuki 2017-11-10 12:36:44 PST
I confirmed this issue also happens on Mac if logilab-common is installed globally.