Message310899
| Author | nitishch |
|---|---|
| Recipients | CuriousLearner, cheryl.sabella, ncoghlan, nitishch, serhiy.storchaka, storymode7 |
| Date | 2018-01-27.23:49:50 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1517096990.03.0.467229070634.issue32685@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> For the right offset, I think we'll want to drop the initial XStrip call added for bpo-32028 entirely, and instead calculate the right offset as a PyUnicode_FindChar search for ";" (replacing it with the length of the input string if the separator isn't found). Are ';' and whitespace the only allowed characters following the print expression? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-01-27 23:49:50 | nitishch | set | recipients: + nitishch, ncoghlan, serhiy.storchaka, CuriousLearner, cheryl.sabella, storymode7 |
| 2018-01-27 23:49:50 | nitishch | set | messageid: <1517096990.03.0.467229070634.issue32685@psf.upfronthosting.co.za> |
| 2018-01-27 23:49:50 | nitishch | link | issue32685 messages |
| 2018-01-27 23:49:50 | nitishch | create | |