Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-1061] ImportError: No module named six #4531

Closed
swift-ci opened this issue Mar 25, 2016 · 3 comments
Closed

[SR-1061] ImportError: No module named six #4531

swift-ci opened this issue Mar 25, 2016 · 3 comments
Labels
bug Something isn't working LLDB for Swift

Comments

@swift-ci
Copy link

Previous ID SR-1061
Radar None
Original Reporter muhasturk (JIRA User)
Type Bug
Status Resolved
Resolution Cannot Reproduce
Environment

OSX 10.11.4 (15E65)
Apple Swift version 2.2 (swiftlang-703.0.18.1 clang-703.0.29)
Target: x86_64-apple-macosx10.9

Additional Detail from JIRA
Votes 0
Component/s LLDB for Swift
Labels Bug
Assignee None
Priority Medium

md5: d6183fc90393ec083b1e21d18e34ca91

Issue Description:

Stable release of Swift 2.2 came with repl missing module warning.

When try to access Swift repl it shows me the following output

http://hastebin.com/obihaxujep.rb

@swift-ci
Copy link
Author

Comment by Kate Stone (JIRA)

The module "six" is part of the Python 2.7 package installed by default on OS X which is a required dependency of LLDB and therefore the Swift REPL. I don't suppose you have a custom version of Python installed?

You can debug the attempt to find modules by starting the Python interpreter in verbose mode:

$ python -v
<lots of output here>
>>> import six

  1. /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/six.pyc matches /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/six.py
    <more output here>

@swift-ci
Copy link
Author

Comment by Kate Stone (JIRA)

Works correctly on a typical OS X installation which includes the six module as part of Python 2.7.

@q-p
Copy link

q-p commented Jun 17, 2016

As a sort of addendum: This problem occurs when an Apple-provided lldb is launched with a custom python interpreter (e.g. one from homebrew) in the path ahead of the Apple provided system python. Unfortunately, lldb doesn't hard-code the path to the python it wants to use but instead takes the first one it happens to stumble upon in the path (which may be missing the required modules).

Also reported as rdar://25314779

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 7, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working LLDB for Swift
Projects
None yet
Development

No branches or pull requests

2 participants