Ned Deily added the comment:
This problem has been fixed with the changes for Issue7367 and, for 2.7,
Issue7425. They should appear in 3.3.0, 3.2.3, and 2.7.3.
--
resolution: -> duplicate
stage: test needed -> committed/rejected
status: open -> closed
superseder: -> pkgutil.walk_pac
Ned Deily added the comment:
This is essentially a duplicate of Issue11914. The root cause is that
pkgutil.iter_modules doesn't deal with permission errors when traversing paths.
Issue7367 is also related.
--
assignee: -> ned.deily
nosy: +ned.deily
Martin von Gagern added the comment:
The server continues all right. It's the browser window which displays the
error message. Not much better in my opinion, though.
To be completely accurate: currently the -b option doens't work as it should
due to issue #11432. But using "-p 0" and opening
Terry J. Reedy added the comment:
Do any of you three have anything to do with pydoc?
Given that the manual simply says "pydoc -b will start the server and
additionally open a web browser to a module index page." without
qualifications, quitting when started from certain locations strikes me
New submission from Martin von Gagern :
I'd like to be able to run "pydoc -b" in whatever directory I'm currently in.
Most of the time that would be the root of my home directory, which is an
ext4fs mount. So it has a subdirectory called "lost+found" for which I don't
have any access permissio
