Message281500
| Author | barry |
|---|---|
| Recipients | Rosuav, barry, docs@python, ezio.melotti, lelit, mrabarnett, nedbat, serhiy.storchaka |
| Date | 2016-11-22.19:10:59 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1479841859.21.0.28946334616.issue28450@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I disagree that the documentation is at fault. This is known to break existing code, e.g. http://bugs.python.org/msg281496 I think it's not correct to change the documentation but leave the error-raising behavior for 3.6 because the deprecation was never documented in 3.5 so this will look like a gratuitous regression. issue27030 for reference. I also question whether it makes sense for such escapes to be illegal in the repl argument of re.sub(). I could understand for this limitation in the pattern argument, but that's not what's causing the error. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-11-22 19:10:59 | barry | set | recipients: + barry, nedbat, ezio.melotti, mrabarnett, docs@python, Rosuav, serhiy.storchaka, lelit |
| 2016-11-22 19:10:59 | barry | set | messageid: <1479841859.21.0.28946334616.issue28450@psf.upfronthosting.co.za> |
| 2016-11-22 19:10:59 | barry | link | issue28450 messages |
| 2016-11-22 19:10:59 | barry | create | |