bpo-25324: copy tok_name before changing it#1608
Conversation
|
@albertjan, thanks for your PR! By analyzing the history of the files in this pull request, we identified @serhiy-storchaka, @1st1 and @tpn to be potential reviewers. |
Sorry, something went wrong.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. Thanks again to your contribution and we look forward to looking at it! |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
I'm not sure that it's the right way to fix the issue: see http://bugs.python.org/issue25324 discussion. I also have comments on the change itself, but I will want until we agree on the way to fix the issue before reviewing the change.
Sorry, something went wrong.
|
Due to a new release of Sphinx, we had to fix the documentation to build on Travis again. Please do a merge to get these changes to help get Travis passing on your PR. |
Sorry, something went wrong.
|
Updated the PR. comments are now copied from token.h to token.py automatically. And I moved ERRORTOKEN back to where it was. |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
LGTM, but I added a new (last I hope) serie of nitpicking comments :-p
Sorry, something went wrong.
|
This should address your comments. Thanks for taking the time to review my PR. |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
LGTM. I will merge the change once tests pass.
Sorry, something went wrong.
|
Please wait with merging. I'm finishing my patch for generating |
Sorry, something went wrong.
Wait? Do you expect conflicts? |
Sorry, something went wrong.
|
Yes, conflicts, and maybe this will lead to redesigning both patches. |
Sorry, something went wrong.
|
Should I do a merge or a rebase to resolve the conflicts? |
Sorry, something went wrong.
As you want. |
Sorry, something went wrong.
f02a84e to
e7113fa
Compare
May 31, 2017 09:02
|
Nevermind @albertjan, looks like the issue I described here was caused by a merge issue. Thanks anyway :) |
Sorry, something went wrong.
Saw this open bug report, and since I was looking at tokenize.py anyway. I figured I address it.
This may catch people off guard though because they may be relying on
tok_namecontainingENCODING,COMMENTandNL. 🤷♂️