-
Notifications
You must be signed in to change notification settings - Fork 85
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
Segfault 11 on Mac (10.10.5) with Python 3.4.4 for outlook.com's IMAP #198
Comments
Original comment by Menno Smits (Bitbucket: mjs0): The only way you could be getting a segfault from IMAPClient is if one of the C extensions it depends on is failing. The likely candidates are pyOpenSSL, cryptography.io and cffi. Possibly related tickets:
Is this problem still happening for you? If so could you please run the following from a Python shell in your environment and post the output here? import cffi, cryptography, OpenSSL
print("cffi: ", cffi.__version__)
print("cryptography: ", cryptography.__version__)
print("pyOpenSSL: ", OpenSSL.__version__) |
Original comment by Paul Hammant (Bitbucket: paul_hammant): Output from your script, Menno, after pip3 install all three today:
I've new work Mac, so I'm stating over on this. The script I refer to from the https://imapclient.readthedocs.org page:
Sure, that's a different error. Other Python projects are reporting "[Errno 32] EPIPE". Homebrew put Python 3.5.1 on the Mac. Should I roll back to 3.4 and retest ? |
Original comment by Paul Hammant (Bitbucket: paul_hammant): Incidentally, I think the dict lookup should be b'EXISTS' not 'EXISTS' |
Original comment by Menno Smits (Bitbucket: mjs0): If it's not too hard for you to try with Python 3.4, then yes please. Which version of OS X is the new laptop running? This is certainly a different problem to what you were seeing before, given that this is an exception and you were seeing a segfault before. Based on what I've been reading it's possible the segfault was fixed in cffi 0.15.1 so I wonder if you were running an older version of cffi earlier and are now past that? There's been a bunch of problems people running pyOpenSSL on OS X. Very frustrating. I'm investigating the possibility of making the use of backports.ssl and pyOpenSSL etc optional, especially for versions of Python with improved SSL support built-in (2.7.9 and later, and 3.4 and later). |
Original comment by Paul Hammant (Bitbucket: paul_hammant): Installing with Python 3.4 (tricky with homebrew - https://github.com/zoidbergwill/homebrew-python)
Trying the https://imapclient.readthedocs.org example (with the b'EXISTS' fix):
OSX is 10.11.5 If you could leave, backports.ssl (etc) behind, I think you'd be better off. |
Probably related to an incompatibility between MacOS/Python/backports.ssl. I believe this issue can be closed. |
IMAPClient 2.x will no longer use backports.ssl etc. This problem will go away when that happens. |
Originally reported by: Paul Hammant (Bitbucket: paul_hammant)
$ python3 testtt.py
Traceback (most recent call last):
File "testtt.py", line 18, in
print('%d messages in INBOX' % select_info['EXISTS'])
KeyError: 'EXISTS'
Segmentation fault: 11
I can reproduce this on two Macs. One a MacBookAir (2011), one a MacBookPro (2014). Both running Yosemite 10.10.5. I was trying first with Python 3.5.1, but I note that is not listed as supported, so I downgraded and tried again.
I would test the same script on Windows10/Python334 but I get SSL errors. See below.
Note - I was logging issues with backport.ssl too - alekstorm/backports.ssl#16 and alekstorm/backports.ssl#15 and alekstorm/backports.ssl#14
The text was updated successfully, but these errors were encountered: