GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||
GeezerVison is showing github.com — gh-88843: Do not allow to parse line breaks between quotes in sniffer regexes. by ptokarski · Pull Request #27256 · python/cpython Conversation
|
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
ptokarski has signed CLA, but piotr-profound has not. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thank you for the patch, and sorry for the long delay. On the main branch the sniffer was rewritten (gh-83273), so these regular expressions no longer exist there and the sample from the issue is detected correctly now. For the maintenance branches this change is too risky: a quoted field may legitimately contain a line break, and forbidding that in the pattern loses the evidence for the real delimiter. On 4000 generated samples it changes the guess for 1.4% of them, and in all of those cases the new guess is worse — for example |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.