Sorry for my question because William wrote :
*The relevant function is divide_into_blocks in parsing.py, which I'veattached to this email, in case anybody wants to fix it for me, sincepeople like Robert Bradshaw and you guys are way better at writingparsers than I am! :-)* So I will look at that thursday. 2013/11/3 Christophe Bal <[email protected]> > Quickly, what are the functions to change ? What is the feature wanted for > parsing.py ? This will help me to try to improve your code. > > > 2013/11/3 Christophe Bal <[email protected]> > >> Thanks for the reactivity. I have no time today to implement this but >> indeed it is a very simple task to do. If no one gives you something, I can >> try to adapt your code. Just tell us in this discussion if someone has done >> the job. >> >> For my part, I could only look at this this french thursday. >> >> Best regards. >> Christophe. >> >> >> 2013/11/3 William Stein <[email protected]> >> >>> On Sun, Nov 3, 2013 at 9:36 AM, Nils Bruin <[email protected]> wrote: >>> > On Sunday, November 3, 2013 2:29:20 AM UTC-8, projetmbc wrote: >>> >> >>> >> Hello. >>> >> >>> >> I think that is not good to have an error with the following code. >>> >> >>> >> ---------------------------------------- >>> >> for i in range(10): >>> >> # Here is a basic comment... >>> >> print i, "-->", i**2 >>> >> ---------------------------------------- >>> > >>> > >>> > I cannot reproduce the error in the notebook nor on the command line. >>> The >>> > code executes properly for me. >>> >>> This is a bug that is my fault in the SMC notebook. I modified how >>> blocks of code are evaluated, to address a longstanding complaint >>> people have with sagenb. For example, if you type >>> >>> 2+2 >>> 3+5 >>> >>> in sagenb (or IPython notebook), then you see only 8, but in SMC you >>> see 4 then 8. Also, if you type >>> >>> for i in range(10): >>> i >>> for j in range(5): >>> j*j >>> >>> you'll see output from both in SMC, but not in sagenb. In sagenb you >>> see only the j stuff. In Ipython notebook you see *nothing*. >>> >>> The relevant function is divide_into_blocks in parsing.py, which I've >>> attached to this email, in case anybody wants to fix it for me, since >>> people like Robert Bradshaw and you guys are way better at writing >>> parsers than I am! :-) >>> >>> >>> >>> -- >>> William Stein >>> Professor of Mathematics >>> University of Washington >>> http://wstein.org >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "sage-support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/sage-support. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
