| In In Sage: Any ideas? |
| Never mind. Leaving this up for those who might stumble. I'll try to think of a better title for the question so people find it. This seems bad, though. I suppose there isn't any way to notice when we are using "pure Python" commands and for the preparser to at least try not doing the whole |
| For others that stumble across this question, you can turn the Sage preparser off by calling |
Asked: Jun 14 '12
Seen: 160 times
Last updated: Jun 18 '12
powered by ASKBOT version 0.7.22
Copyright Sage, 2010. Some rights reserved under creative commons license.
This one has gotten me, too. It's very annoying.
John Palmieri (Jun 19 '12)See here.
bk322 (Jun 19 '12)@bk322 - right, if I'd gotten that error I would have thought of this, but it was the
kcrisman (Jun 19 '12)IndexErrorthat made it so weird. Because of course this error naturally appears anyway when you've tried to access a nonexistent group (likematches.group(3)would be above, I guess)