This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ridgerat1611
Recipients eric.smith, ridgerat1611
Date 2021-03-16.02:42:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1615862522.61.0.603664347473.issue43483@roundup.psfhosted.org>
In-reply-to
Content
I can't find any real errors in documentation.  There are subtle design and implementation decisions that result in unexpected rare side effects.  After processing hundreds of thousands of lines one way, why would the parser suddenly decide to process the next line differently?  Well, because it can, and it happens to be convenient.  And that can catch users off-guard.

I'm considering whether posting an "enhancement" issue would be more appropriate... maybe there is a way to make the parser systems work more nearly the way people currently expect, without breaking things.
History
Date User Action Args
2021-03-16 02:42:02ridgerat1611setrecipients: + ridgerat1611, eric.smith
2021-03-16 02:42:02ridgerat1611setmessageid: <1615862522.61.0.603664347473.issue43483@roundup.psfhosted.org>
2021-03-16 02:42:02ridgerat1611linkissue43483 messages
2021-03-16 02:42:02ridgerat1611create