➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients ned.deily, opstad, ronaldoussoren
Date 2018-01-03.19:17:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515007067.79.0.467229070634.issue32488@psf.upfronthosting.co.za>
In-reply-to
Content
Glad you solved the immediate problem.  Under the covers, pydoc (either pydoc2 or pydoc3) tries to import all the modules associated with the interpreter instance it's running under - from the Python standard library plus any additional vendor-supplied modules and and any you install (with pip et al).  It seems likely that the Python 2 instance associated with the "pydoc" on your shell path (not "pydoc3" and Python 3) has at least one broken module installed.  It may be a case of a third-party module being compiled against one version of Python 2.7 (say, a Homebrew version) and being executed with another (say the Apple-supplied system Python 2.7).  See, for example, https://stackoverflow.com/questions/35640529/what-does-fatal-python-error-pythreadstate-get-no-current-thread-mean
History
Date User Action Args
2018-01-03 19:17:47ned.deilysetrecipients: + ned.deily, ronaldoussoren, opstad
2018-01-03 19:17:47ned.deilysetmessageid: <1515007067.79.0.467229070634.issue32488@psf.upfronthosting.co.za>
2018-01-03 19:17:47ned.deilylinkissue32488 messages
2018-01-03 19:17:47ned.deilycreate