➜

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 Kyle Graehl
Recipients Kyle Graehl, demian.brecht, riklaunim
Date 2015-10-22.22:24:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445552670.56.0.778747852503.issue23930@psf.upfronthosting.co.za>
In-reply-to
Content 
r"(\s+|;|$|,)"   # Ending either at space, semicolon, or EOS. ( or comma...)

I remember running into this same problem like 5 years ago.

I added a comma as a valid regexp for ending the pattern, and removed it as a valid _LegalKeyChars

I also think adding the "Priority" reserved key might make sense (or at least have options for handling it)
History
Date User Action Args
2015-10-22 22:24:30Kyle Graehlsetrecipients: + Kyle Graehl, demian.brecht, riklaunim
2015-10-22 22:24:30Kyle Graehlsetmessageid: <1445552670.56.0.778747852503.issue23930@psf.upfronthosting.co.za>
2015-10-22 22:24:30Kyle Graehllinkissue23930 messages
2015-10-22 22:24:30Kyle Graehlcreate