[issue12902] help("modules") executes module code

Dev Player added the comment: Mentioned for informational purposes only. I too experience the running of external packages with a different library when doing help('modules') in the interpreter. This is a fresh install of Python 3.4 on WinXP. The text I get in the python.exe interpreter is: "

[issue12902] help("modules") executes module code

Terry J. Reedy added the comment: #13902 is essentially a duplicate of this and I may close it. I am thinking now that executing unknown amounts of unknown code from unknown modules is a really bad idea. If a module just crashes the system, as happened with the OP of the above, there is no way

[issue12902] help("modules") executes module code

Ezio Melotti added the comment: > A separate issue would be a feature request to not do that (assuming it > really does). I tried to verify this (the fact that modules get imported with help('modules')). Here are the results: * Lib/foobar.py: - help('modules'): foobar in the list, code

[issue12902] help("modules") executes module code

Ezio Melotti added the comment: Right, I missed that. If we change the way the list is created this bug will be probably get fixed too. If we don't, we should open another issue. -- ___ Python tracker __

[issue12902] help("modules") executes module code

Terry J. Reedy added the comment: As I said in msg143786, the second time only c-coded modules are listed. -- ___ Python tracker ___

[issue12902] help("modules") executes module code

Ezio Melotti added the comment: Since help("modules") just shows a list of modules without any description, maybe it could avoid importing them until further information about individual modules are requested. Also while trying to do help("modules") twice on py3k, I noticed that the second t

[issue12902] help("modules") executes module code

Ezio Melotti added the comment: > "Warning: gathering the results for the topic 'modules' can take > considerable time and have side effects as it imports *every* module > available to get at its doc string." http://docs.python.org/documenting/style.html#affirmative-tone -- __

[issue12902] help("modules") executes module code

Terry J. Reedy added the comment: The immediate issue is improvement of the entries for help and help(): In builtin functions section: Expand "Invoke the built-in help system." to "Invoke the built-in help system, which uses *pydoc*." where *pydoc* is linked to the pydoc section. Add to the e

[issue12902] help("modules") executes module code

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12902] help("modules") executes module code

Éric Araujo added the comment: Thanks for the report. This comes from the fact that pydoc imports the modules in order to get their documentation. Your message makes me think that the KWallet Python modules have a problem: they should not pop GUIs at import time! Please report this to them

[issue12902] help("modules") executes module code

New submission from dronus : When running help("modules"), some code of the modules seems to be run. For example, on my Gnome system KWallet configuration GUI pops up and stalls further opereation. I think no one expect help("modules") run abitrary code instead of just outputting a list of mo