[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

2019-04-18 Thread mollison
mollison added the comment: @brett.cannon: PR is at https://github.com/python/cpython/pull/12879 -- ___ Python tracker <https://bugs.python.org/issue36

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

2019-04-18 Thread mollison
Change by mollison : -- keywords: +patch pull_requests: +12803 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36645> ___ ___ Python-

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

2019-04-17 Thread mollison
mollison added the comment: @brett.cannon: Yes, I will submit a PR. I have the code ready to go already. I just submitted the Python contributor agreement. I think it will take the system a day or two to register that. Then, I will submit the PR

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

2019-04-16 Thread mollison
mollison added the comment: You have not understood my message. I know that text is already there. My point is that because it's in a separate paragraph, it looks like it's not part of Changed in 3.7. There is nowhere else on the page where a change description is in a separate

[issue36645] re.sub() library entry does not adequately document surprising change in behavior between versions

2019-04-16 Thread mollison
New submission from mollison : This is regarding the change to re.sub() between 3.6 and 3.7 that results in different behavior even for simple cases like the following: re.sub('a*','b', 'a') returns 'b' in 3.6 and 'bb' in 3.7 This change