Re: [sympy] eval() evil - sympify() safe?

2013-05-23 Thread Aaron Meurer
sympify is *NOT* safe. It calls eval. The same tricks that you can use to do nasty things with eval can be used from sympify. Who is hyping it as safe? I don't think it can be made safe either (if anyone has any ideas, feel free to discuss them, though). The only way to protect against arbitrar

[sympy] eval() evil - sympify() safe?

2013-05-23 Thread Ja Genau
Hi there, sympify() is hyped as the safe alternative to evil eval(). Is it really that safe that there is no way to pass a string to sympy.sympify().evalf() to harm the system? -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this

Re: [sympy] args invariant

2013-05-23 Thread Stefan Krastanov
>> I suspect these people are falling into the trap of seeing the >> simplicity of the option 1 invariant over the option 3 invariant, >> without noticing that it really leads to more complicated code. > > I am clearly one of those nutheads. From their perspective it's a reasonable > assumption t

Re: [sympy] args invariant

2013-05-23 Thread Matthew Rocklin
Sorry, I was traveling and away from the computer for a while. > So my recommendation here goes back to using Symbol as the first > argument of MatrixSymbol. Also, the class should clearly not subclass > from Symbol in this case (I don't remember if it already does). MatrixSymbol does not subc