[issue13691] pydoc help (or help('help')) should show the doc for help

Nick Coghlan added the comment: Belatedly removing the "easy" tag, since that turned out to be thoroughly incorrect... -- keywords: -easy ___ Python tracker

[issue13691] pydoc help (or help('help')) should show the doc for help

e __help__()), and then pydoc would render the help based on that. Regardless of the exact approach, it would be a task requiring a PEP to resolve, since rendered documentation appears in so many different contexts. -- ___ Python tracker <rep...@bugs.pyth

[issue13691] pydoc help (or help('help')) should show the doc for help

Serhiy Storchaka added the comment: > It does make me wonder whether it might be worth defining a __help__ magic > method that completely overrides what help(obj) displays. This should be very complex protocol if take to account that help() outputs formatted and highlighted text and pyd

[issue13691] pydoc help (or help('help')) should show the doc for help

Nick Coghlan added the comment: After reviewing Sanyam's PR at https://github.com/python/cpython/pull/172 I ended up rejecting it as an approach to resolving this issue. The core problem with the approach is that accessing `_sitebuiltins._Helper` is an implementation detail twice over: -

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Xiang Zhang added the comment: New changeset 0710d754255e731e6fcc3f206b51db6156da17c8 by Xiang Zhang in branch 'master': bpo-29770: remove outdated PYO related info (GH-590) https://github.com/python/cpython/commit/0710d754255e731e6fcc3f206b51db6156da17c8 --

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Xiang Zhang added the comment: New changeset 16416c22f9b8d9e067506d3a98f661756c80389c by Xiang Zhang in branch '3.6': bpo-29770: remove outdated PYO related info (GH-590) (GH-612) https://github.com/python/cpython/commit/16416c22f9b8d9e067506d3a98f661756c80389c --

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Xiang Zhang added the comment: New changeset ce222c87706b1062f7fc03867d1867aa4848dd7b by Xiang Zhang in branch '3.5': bpo-29770: remove outdated PYO related info (GH-590) (GH-613) https://github.com/python/cpython/commit/ce222c87706b1062f7fc03867d1867aa4848dd7b -- nosy: +xiang.zhang

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Wolfgang Langner added the comment: Thanks for fixing this so fast. Good work. -- ___ Python tracker ___ ___

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Xiang Zhang : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Xiang Zhang : -- pull_requests: +506 ___ Python tracker ___ ___ Python-bugs-list

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Xiang Zhang : -- pull_requests: +505 ___ Python tracker ___ ___ Python-bugs-list

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Xiang Zhang : -- pull_requests: +486 ___ Python tracker ___ ___ Python-bugs-list

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Serhiy Storchaka : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue29770] Executable help output (--help) at commandline is wrong for option -B

New submission from Wolfgang Langner: The output for "python --help" for the option -B is wrong. It contains also the old pyo files. But they were removed. Output is: -B : don't write .py[co] files on import; also PYTHONDONTWRITEBYTECODE=x should be: -B : don't write

[issue13691] pydoc help (or help('help')) should show the doc for help

Changes by Jaysinh shukla : -- nosy: +jaysinh.shukla ___ Python tracker ___ ___

[issue13691] pydoc help (or help('help')) should show the doc for help

Changes by Sanyam Khurana : -- pull_requests: +138 ___ Python tracker ___ ___

[issue13691] pydoc help (or help('help')) should show the doc for help

Nick Coghlan added the comment: Recapping the situations that need test cases before this can be merged: * behaviour when "help" is entered at the interactive help prompt (as the current behaviour is correct and should *not* change) * behaviour when calling "help(help)&qu

[issue13691] pydoc help (or help('help')) should show the doc for help

Sanyam Khurana added the comment: Hi, I'm working on fixing this issue. -- nosy: +CuriousLearner ___ Python tracker ___

[issue13691] pydoc help (or help('help')) should show the doc for help

R. David Murray added the comment: No 3.4 can't be patched, this is not a security issue. A patch to make the behvior what we want should be generated against either 3.5 or 3.6, and the committer will deal with any issues arising from 3.5 vs 3.6 issues. -- versions: +Python 3.5,

[issue13691] pydoc help (or help('help')) should show the doc for help

Changes by SilentGhost : -- nosy: +Cubky, Devin Jeanpierre, eric.araujo, ezio.melotti, jairotrad, jbitcm-, mikehoy, r.david.murray, terry.reedy -lissacoffeyx ___ Python tracker

[issue13691] pydoc help (or help('help')) should show the doc for help

Changes by SilentGhost : -- Removed message: http://bugs.python.org/msg272582 ___ Python tracker ___

[issue13691] pydoc help (or help('help')) should show the doc for help

lissacoffeyx added the comment: I just tested this issue in Python 3.6.0a0 and got this behavior: help('help') brings "Help on _Helper in module _sitebuiltins object:" help(help) brings: Help on _Helper in module _sitebuiltins object: help() invokes the help command line. So this

[issue13691] pydoc help (or help('help')) should show the doc for help

Jairo Trad added the comment: I just tested this issue in Python 3.6.0a0 and got this behavior: help('help') brings Help on _Helper in module _sitebuiltins object: help(help) brings: Help on _Helper in module _sitebuiltins object: help() invokes the help command line. So this was fixes

[issue13691] pydoc help (or help('help')) should show the doc for help

Terry J. Reedy added the comment: 3.5 is the same as 3.6 in that now both help(help) and help('help') show the not terribly helpful Help on _Helper in module site object: Buried in the text is | Calling help() at the Python prompt starts an interactive help session. | Calling help

Re: Help father help son / Install Version 2.6 on Mac OSX 10.9

On 24Feb2014 21:57, Ned Deily n...@acm.org wrote: In article CAPTjJmp-UDAdJz=28ywCggkepFcTTJ-=9rEvtpsXO_Vgup=q...@mail.gmail.com, Chris Angelico ros...@gmail.com wrote: On Tue, Feb 25, 2014 at 4:28 PM, quequ...@gmail.com wrote: Trying to install Python 2.6 because PyGames says it will

Help father help son / Install Version 2.6 on Mac OSX 10.9

I just want to help him get the environment set up. Running Mac Maverick, OSX 10.9 Trying to install Python 2.6 because PyGames says it will only install if Python 2.6 is present. When I run make framework install I am treated to: gcc -c -fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g

Re: Help father help son / Install Version 2.6 on Mac OSX 10.9

On Tue, Feb 25, 2014 at 4:28 PM, quequ...@gmail.com wrote: Trying to install Python 2.6 because PyGames says it will only install if Python 2.6 is present. Are you sure you need 2.6 and not 2.7? This suggests 2.7 works: http://pygame.org/wiki/MacCompile ChrisA --

Re: Help father help son / Install Version 2.6 on Mac OSX 10.9

In article CAPTjJmp-UDAdJz=28ywCggkepFcTTJ-=9rEvtpsXO_Vgup=q...@mail.gmail.com, Chris Angelico ros...@gmail.com wrote: On Tue, Feb 25, 2014 at 4:28 PM, quequ...@gmail.com wrote: Trying to install Python 2.6 because PyGames says it will only install if Python 2.6 is present. Are you

[issue13691] pydoc help (or help('help')) should show the doc for help

Éric Araujo added the comment: Cool! Can you add tests? -- stage: needs patch - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___

[issue13691] pydoc help (or help('help')) should show the doc for help

Mike Hoy added the comment: Cool! Can you add tests? Nope, I can't add tests. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___ ___

[issue13691] pydoc help (or help('help')) should show the doc for help

Éric Araujo added the comment: I was addressing the author of the patch :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___ ___

[issue13691] pydoc help (or help('help')) should show the doc for help

Changes by Mike Hoy mho...@gmail.com: -- nosy: +mikehoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___ ___ Python-bugs-list mailing list

[issue13691] pydoc help (or help('help')) should show the doc for help

Mike Hoy added the comment: I imported this patch on 3.4 and it worked as expected on my system. help('help') brings up info about help() help(object) prints the docstring help() invokes the help -- ___ Python tracker rep...@bugs.python.org http

[issue13691] pydoc help (or help('help')) should show the doc for help

Éric Araujo added the comment: What about pydoc help? -- versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___ ___ Python

[issue13691] pydoc help (or help('help')) should show the doc for help

Mike Hoy added the comment: What about pydoc help? $ ./python -m pydoc help Help on built-in function help: help(...) Invoke the built-in help system. help() The interactive help system starts on the interpreter console. help(string) The string is looked up as the name

[issue13691] pydoc help (or help('help')) should show the doc for help

Petr Kubat killm...@gmail.com added the comment: I see. So calling help('help') should produce the documentation on the help() function and typing help at the help prompt should print the help for the prompt. Tricky indeed. I think I'll look at it during the day after tomorrow and post some

[issue13691] pydoc help (or help('help')) should show the doc for help

Petr Kubat killm...@gmail.com added the comment: Is anyone still working on this? If not I would like to make this work. Although I'm not exactly sure how to tackle this problem since the built-in help function is defined as a wrapper around pydoc.help and so the docstring used for printing

[issue13691] pydoc help (or help('help')) should show the doc for help

at the code you are patching) it seems likely that the change to the if statement is going to break *something*. Probably what happens when you type 'help' at the 'help' prompt, at a guess. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org

[issue13691] pydoc help (or help('help')) should show the doc for help

Petr Kubat killm...@gmail.com added the comment: Help at the help prompt does work, I tested that. But if you (or anyone) thought of a better way to fix this issue I would be glad to change it. -- ___ Python tracker rep...@bugs.python.org http

[issue13691] pydoc help (or help('help')) should show the doc for help

R. David Murray rdmur...@bitdance.com added the comment: works in the sense that it produces output. But it doesn't produce the output it used to, which is the same text as the initial banner when you type help(). I believe the existing behavior in this case is correct. With your patch

[issue13691] pydoc help (or help('help')) should show the doc for help

R. David Murray rdmur...@bitdance.com added the comment: Oh, that wouldn't fix 'pydoc help', would it. So there are probably two places where the special case has to be added, which means the code itself should go in pydoc and be called from _Helper.__call__ somehow. (Note, I'm just throwing

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

Éric Araujo mer...@netwok.org added the comment: Just a heads-up: I’ll be offline between January 19 and the end of the month, so don’t worry if you make a patch and it’s not reviewed immediately (at least not by me, other developers may do it :) --

[issue13691] pydoc help (or help('help')) should show the doc for help

Changes by Éric Araujo mer...@netwok.org: -- title: pydoc help (or help('help')) claims to run a help utility; does nothing - pydoc help (or help('help')) should show the doc for help ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

jbitcm- chakrapacka...@gmail.com added the comment: I am working on it -- nosy: +jbitcm- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

Éric Araujo mer...@netwok.org added the comment: I’m interested in this, so I’m taking assignment. If a contributor is interested in making a patch I’ll review it, otherwise I’ll say when I start on a patch. -- assignee: - eric.araujo keywords: +easy

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

Éric Araujo mer...@netwok.org added the comment: IMO, help('help') should document the help function, not start an interactive help session (that’d be help()). -- nosy: +eric.araujo versions: +Python 3.3 -Python 2.6 ___ Python tracker rep

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

Terry J. Reedy tjre...@udel.edu added the comment: I agree. It should explain the three options: help(object): help on object or class of object, except help('name'): help on object/module named 'name' help(): run utility, which starts with utility help help(help) prints unhelpful Help

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

Devin Jeanpierre jeanpierr...@gmail.com added the comment: IMO, help('help') should document the help function, not start an interactive help session (that’d be help()). Ahhh, that explains it. help('help') isn't ever meant to be called; it's supposed to be: help() ... help help

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti stage: - needs patch type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13691 ___

[issue13691] pydoc help (or help('help')) claims to run a help utility; does nothing

New submission from Devin Jeanpierre jeanpierr...@gmail.com: What follows is a copy-paste of a shell session. Notice that at the end, rather than being inside the online help utility, I'm still in the interactive interpreter. I was able to duplicate this on python3.2, python2.7, and python2.6

Help on help()

Is there any technique for preventing help from recursing into the module tree?? If I do: import my_module help(my_module) I'd like to see ONLY help on my_module, NOT help on all the functions inherited from the various parent classes . . . A quick search of the documentation didn't turn up

Re: Help on help()

If I do: import my_module help(my_module) I'd like to see ONLY help on my_module, NOT help on all the functions inherited from the various parent classes . . . I would do print my_module.__doc__ HTH, Martin -- http://mail.python.org/mailman/listinfo/python-list

Fwd: RE: [Python-Help] Python Help

Forwarding full message to the Python list: Hello, I am trying to create a script. I have most of it wrote, but it isn't working like it should. Could you please take a look and let me know whats wrong with it? What happens is that there is an array that is created and I verified the

Re: [Python-Help] Programming help

On Mon, 6 Dec 2004, Alfred Canoy wrote: Please help me out:(.. I've been trying to figure this out for 2 days now.. I don't know what to use to print all the list of numbers. I hve know idea how should I do this. I tried a lot of trial error for the the def, dict, .list( ). have no luck

Re: [Python-Help] Programming help

Mathews On Mon, 6 Dec 2004 12:07:58 +1000, Alfred Canoy [EMAIL PROTECTED] wrote: Please help me out:(.. I've been trying to figure this out for 2 days now.. I don't know what to use to print all the list of numbers. I hve know idea how should I do this. I tried a lot of trial error