bpo-40246: Revert reporting of invalid string prefixes#19888
Conversation
Due to backwards compatibility concerns, that keywords immediately followed by a string without whitespace between them (like in `bg="#d00" if clear else"#fca"`) will fail to parse, PR19476 has to be reverted.
5f002af to
1c3eeaa
Compare
May 3, 2020 20:32
gvanrossum
left a comment
There was a problem hiding this comment.
Please also delete the NEWS item of the reverted change (Misc/NEWS.d/next/Core and Builtins/2020-04-11-17-52-03.bpo-40246.vXPze5.rst).
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 |
Sorry, something went wrong.
|
Can't find the news file. There is no file on master with |
Sorry, something went wrong.
|
That news file has already been merged to the changelog when 3.9.0a6 was released. I think this should explicitly add a new entry about the revert. |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @gvanrossum: please review the changes made to this pull request. |
Sorry, something went wrong.
|
I've backported this PR to Fedora's build of 3.9.0a6 and I still see: I will double check the patch was actually applied. |
Sorry, something went wrong.
|
It was a cache issue, it used an older, unpatched build. Sorry for the noise. In fact, this PR makes the problem go away, as ecpected. |
Sorry, something went wrong.
|
I'm not getting a |
Sorry, something went wrong.
Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
Due to backwards compatibility concerns, that keywords immediately
followed by a string without whitespace between them
(like in
bg="#d00" if clear else"#fca") will fail to parse,GH-19476 has to be reverted.
https://bugs.python.org/issue40246