[issue30181] Correct the parsing of a test case docstring.

Chris Jerdonek added the comment: I'm closing this as a duplicate of issue 39450, which has been resolved. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> unittest TestCase shortDescription does not strip whitespace _

[issue30181] Correct the parsing of a test case docstring.

Chris Jerdonek added the comment: I believe this was addressed by issue 39450, which I think was technically a duplicate of this issue. -- nosy: +chris.jerdonek ___ Python tracker __

[issue30181] Correct the parsing of a test case docstring.

R. David Murray added the comment: It's not the PSF, it's the dev team, and it is "just" a matter of tooling. Which means help improving the tooling is welcome :) -- ___ Python tracker ___

[issue30181] Correct the parsing of a test case docstring.

Ben Finney added the comment: > I have already created such a pull requests. It is bidirectionally linked to > this ticket. I hope the PSF can start accepting contributions without that laundering, but until then: thank you for taking that on. -- _

[issue30181] Correct the parsing of a test case docstring.

R. David Murray added the comment: Ah, yes, that's a bug in our workflow we'll need to fix. The CLA signed on the bug tracker is the ultimate authority, so we need some way to manually bypass the bot for cases like this. A committer should be able to bypass the problem and get the patch pushe

[issue30181] Correct the parsing of a test case docstring.

Ben Finney added the comment: > if you upload a patch generated from your branch here, someone else will > create the github PR so we can get it processed. The branch has several commits. I have generated the patches, and am now uploading them as a tarball. It may be easier to simply merge fr

[issue30181] Correct the parsing of a test case docstring.

Brian May added the comment: I have already created such a pull requests. It is bidirectionally linked to this ticket. However concerns have been raised that the automatic bot hasn't recognised that Ben Finney has signed the CLA. Hence it appears the pull request might be rejected. Sure ther

[issue30181] Correct the parsing of a test case docstring.

R. David Murray added the comment: Our tooling and workflow is indeed dependent on github. We should repurpose the current 'remote hg repo' to allow the entry of a non-github git repo, but someone will have to write that code. In the meantime, if you upload a patch generated from your branch

[issue30181] Correct the parsing of a test case docstring.

Ben Finney added the comment: > No, your contribution will not be rejected by "you don't maintain the repo on > GitHub", everyone can send the patch (PR) to python/cpython. I am glad to know that. I won't be maintaining a GitHub account because I disagree with the terms of service. > Ben, if

[issue30181] Correct the parsing of a test case docstring.

Ben Finney added the comment: Apparently there is some consternation about my bugs.python.org identity. This is Ben Finney of WSP Digital, in Melbourne, Australia. A GitHub account is wholly irrelevant to this account. A GitHub account is wholly irrelevant to accepting the PSF CLA. This bugs.

[issue30181] Correct the parsing of a test case docstring.

Brian May added the comment: Me getting confused at the newline in the comparison output. -- ___ Python tracker ___ ___ Python-bugs-li

[issue30181] Correct the parsing of a test case docstring.

Brian May added the comment: I made an attempt at a PR. Unfortunately some of the tests appear to fail on some environments, and the messages produced don't exactly clarify why. -- ___ Python tracker _

[issue30181] Correct the parsing of a test case docstring.

Changes by Roundup Robot : -- pull_requests: +1606 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue30181] Correct the parsing of a test case docstring.

Louie Lu added the comment: Ben, if you have any problem about how to get on with GitHub, I can help you at #python-dev @ freenode, ping louielu on the chatroom. -- ___ Python tracker _

[issue30181] Correct the parsing of a test case docstring.

Louie Lu added the comment: > Thank you. I'll re-base my branch onto the master branch found at the GitHub > repository. You may re-clone a GitHub repository instead of rebase bitbucket repo. > I don't maintain repositories at GitHub. Does that mean the contribution must > be rejected? No,

[issue30181] Correct the parsing of a test case docstring.

Ben Finney added the comment: On 2017-05-01 17:45, Louie Lu wrote: > Ben, the process of submitting PR was migrated to GitHub Thank you. I'll re-base my branch onto the master branch found at the GitHub repository. > you will need to use a GitHub account to do it I don't maintain repositories

[issue30181] Correct the parsing of a test case docstring.

Louie Lu added the comment: Ben, the process of submitting PR was migrated to GitHub, you will need to use a GitHub account to do it. You can refer to devguide for how to submit a PR here: http://cpython-devguide.readthedocs.io/pullrequest.html --

[issue30181] Correct the parsing of a test case docstring.

Ben Finney added the comment: Howdy R. David, Okay, I have put together a series of commits to address this bug. The changes are in my personal fork of the ‘cpython’ repository, so this is a pull request from ‘wip/issue/issue30181_parse-docstring-using-pydoc’ in that repository. The following c