Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
See inline comments
While you are working on the module, please remove PyModule_GetDict() and replace the code with PyModule_AddStringConstant().
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
See inline comments While you are working on the module, please remove PyModule_GetDict() and replace the code with PyModule_AddStringConstant(). I could merge #23101 into this PR. Would that be acceptable? |
Sorry, something went wrong.
|
See inline comments I could merge #23101 into this PR. Would that be acceptable? +1, good idea You'll get bonus points for using PyModule_AddObjectRef. |
Sorry, something went wrong.
|
You'll get bonus points for using PyModule_AddObjectRef. GH-23101 merged with commit 38e3cd7. |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @tiran: please review the changes made to this pull request. |
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm awesome,
I ran manually some tests and works well.
Sorry, something went wrong.
There was a problem hiding this comment.
But I want to know why this behavior is changed.
Sorry, something went wrong.
|
But I want to know why this behavior is changed. I find that odd as well. At first, I though it was just the AC that messed up the argument list, but it's not. The docstring is clearly there in line 1214. Try this: >>> import re
>>> p = re.compile('')
>>> help(p.sub)
It seems to happen only with methods with the defining_class converter. Could it be a bug in AC? UPDATE Seems like dbm has the same problem. For example, the _dbm.dbm.keys method, which also has a defining_class converter, and is a method defined on a type belonging to the module: >>> import dbm
>>> d = dbm.open('test.db', 'c')
>>> d
<_gdbm.gdbm object at 0x103eeb500>
>>> d.keys.__doc__ # <= this returns None iso. the docstring as defined in AC
>>> help(d.keys) # <= this displays the docstring as defined in AC
|
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
Actually, tests should pass now because test runners will use revised idlelib. |
Sorry, something went wrong.
|
@tiran The IDLE test failure is gone. Do you still want changes? |
Sorry, something went wrong.
|
@corona10 IDLE has been fixed, so tests pass fine now. I'll file an issue about the missing __doc__ strings in builtin methods. |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
https://bugs.python.org/issue1635741