I'm not clear enough on how the standard_transformations work to say if this should happen or not. We definitely need a better API to our parser to allow fixing this sort of issue.
By the way, there *is* something that is definitely a bug, though, which is that it happens in Python 3, even though 1l is not valid syntax in Python 3. Aaron Meurer On Thu, Aug 22, 2013 at 12:44 AM, Duane Nykamp <[email protected]> wrote: > Is this the desired behavior of parse_expr? > > In [16]: parse_expr("2log(x)", transformations=(standard_transformations+ > (implicit_multiplication,))) > Out[16]: 2⋅og⋅x > > In [17]: parse_expr("2log(x)", transformations=(standard_transformations+ > (implicit_multiplication_application,))) > Out[17]: 2⋅g⋅o⋅x > > It appears that the "l" from log gets sucked into the 2 turning it into 2L > and leaving just og(x) left over. Putting a space between 2 and log(x) > fixes the problem. > > I'd consider this unintuitive behavior and confusing to users. Would it make > sense to group the "l" with the "log" in this case? > > Duane > > -- > You received this message because you are subscribed to the Google Groups > "sympy" 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/sympy. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy. For more options, visit https://groups.google.com/groups/opt_out.
