Danny Yoo wrote:
>>I hate to admit it, but there are times when fear should be listened to,
>>and I think this is one of them. So, I guess I'll move on to parsing it
>>myself. Seems a shame though.
>>
>>
>
>Hi DS,
>
>Yeah, I'd recommend listening to fear. *grin* Python's a powerful
>languag
> I hate to admit it, but there are times when fear should be listened to,
> and I think this is one of them. So, I guess I'll move on to parsing it
> myself. Seems a shame though.
Hi DS,
Yeah, I'd recommend listening to fear. *grin* Python's a powerful
language, and I'd recommend erring on th
Kent Johnson wrote:
>It is very challenging to even come close to safety. If you search
>comp.lang.python for eval or exec you will find many discussions of
>this. For example
>http://groups.google.com/group/comp.lang.python/browse_frm/thread/cf6093c5551a6587/23ddf23a6dfc3e11?q=eval&rnum=1#23ddf
On Tue, 14 Feb 2006, Kent Johnson wrote:
> Bottom line - it's a very hard problem which I don't think anyone has
> solved to the satisfaction of all observers, though there are limited
> solutions which some people find acceptable.
I think it's telling that the restricted execution modules, rex
DS wrote:
> I have been writing a web-based application in which users would be able
> to input expressions which would be evaluated on the server. I had read
> about the dangers of using eval for such things, and so I parse the
> expressions myself, and calculate the expressions using my own code
I have been writing a web-based application in which users would be able
to input expressions which would be evaluated on the server. I had read
about the dangers of using eval for such things, and so I parse the
expressions myself, and calculate the expressions using my own code.
This wasn't too
