Hello support, I came across some very strange behavior recently regarding docstrings in functions. In the notebook in 3.2.alpha0 and 3.0.6, putting an apostrophe in the docstring causes various bugs. It doesn't have to be in any particular spot, as far as I can tell; in fact, it took a long time to pinpoint this as the source of the problem!
More precisely, it seems to cause the preparser to turn off or something, because it disallows the following (in the function definition): f(x)=x^3 because of the f(x), and f=x^3 because of the ^ used instead of ** (the error message for the first is very mysterious at times, but the second one is always clear when you try to use the function). I can post a link to a worksheet if it's really necessary, but hopefully this will be enough for someone to help. I checked Sage and Python docs about documentation strings, but couldn't find anything about it being bad to have apostrophes; in fact, some Sage docstrings have them (e.g. for declaring variables). I didn't try this in the command line, so it is possible it's only a notebook issue. Thanks for any help! - kcrisman --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
