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
bpo-29940: Add follow_wrapped option to help() #12915
Conversation
There are no tests. Can we find useful ones to add that will also demonstrate the reason for this change? e.g. showing correct help for functions wrapped with class-based decorators I think that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add some tests?
incr cannot be larger than INT_MAX: downcast to int explicitly.
On Windows, fix asyncio recv_into() return value when the socket/pipe is closed (BrokenPipeError): return 0 rather than an empty byte string (b'').
…ythonGH-17536) Co-authored-by: Jeffrey Kintscher <websurfer@surf2c.net>
…han duplicating it in 'compile.c' (pythonGH-21714) Generate information about jumps from 'opcode.py' rather than duplicate it in 'compile.c'
…1479) See PEP 623 for detail.
Explicitly cast PyHKEYObject* to PyObject* to call _PyObject_Init().
Split newsize calculation into new function. dictresize() now accepts exact newsize.
PyUnicodeEncodeError_Create has been deprecated with `Py_DEPRECATED` macro. But it was not documented.
…H-21768) gdb 9.2 on Fedora Rawhide is not reliable, see: * https://bugs.python.org/issue41473 * https://bugzilla.redhat.com/show_bug.cgi?id=1866884
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
oops. sorry!!!!! |
i am preparing a new pr for this... sorry for the nnoise. |
@eamanu, no problem and no need to apologize, it happens all too often with git. Just in case you haven't, I recommend reading the "Lifecycle of a Pull Requst" section on the devguide, which may be helpful. You're also welcome to ask anything on the Python IRC and Zulip chat channels and get immediate help. |
I was under the impression that this happened only when rebasing/fast-forwarding with |
In this case it appears the @eamanu accidentally merged in another branch, which may have been similary re-based or based on a different commit. |
Hi I make this PR: #22390
I need practice my git skills. I don't like the rebase (or I don't understand yet) and I did an rebase from master, and then I did (and I think that was my error) |
When print the docstring using help builtin for an wrapper function
it doesn't correspond to the function wrapped. For avoid this
this PR add the follow_wrapped option to help() function.
https://bugs.python.org/issue29940