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 philwebster
Recipients JayKrish, Todd.Rovito, philwebster, terry.reedy
Date 2013-07-11.22:42:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks Terry, I will start PEP8-checking my code before I submit (as well as testing more thoroughly). I was thinking the same thing about the logic behind _decode and index functions needing to be combined.

How would you recommend adding functionality to the decode function to handle expressions like "1.2 +5 chars" or "1.0 lineend-5c"? (#18409) uses this kind of index, so it will be needed soon. I'm thinking that splitting off the base index then parsing the remaining modifier expressions is the way to go.

I was also thinking that a _checkIndex method would be good to have especially when using the +/-line and +/-char expressions.
Date User Action Args
2013-07-11 22:42:06philwebstersetrecipients: + philwebster, terry.reedy, Todd.Rovito, JayKrish
2013-07-11 22:42:06philwebstersetmessageid: <>
2013-07-11 22:42:06philwebsterlinkissue18365 messages
2013-07-11 22:42:06philwebstercreate