use strings to call functions
in [Python]
|
From: OdarR on 9 Feb 2010 13:11 On 9 fév, 11:01, Stefan Behnel <stefan...(a)behnel.de> wrote: > Klaus Neuner, 09.02.2010 10:04: > > > my program is supposed to parse files that I have created myself and that > > are on my laptop. It is not supposed to interact with anybody else > > than me. > > Famous last words. > > Stefan I knew it. Olivier
From: Klaus Neuner on 10 Feb 2010 03:58 On Feb 9, 11:01 am, Stefan Behnel <stefan...(a)behnel.de> wrote: > KlausNeuner, 09.02.2010 10:04: > > > my program is supposed to parse files that I have created myself and that > > are on my laptop. It is not supposed to interact with anybody else > > than me. > > Famous last words. > > Stefan All right, I admit that eval() is evil and should never be used. Under no circumstances. (Which is, of course, the reason, why Python has eval().) The same applies to knives. You shouldn't use them. You shouldn't even use them in your own kitchen. A man might enter your kitchen, take your knife away and use it against you.
From: Bruno Desthuilliers on 10 Feb 2010 06:55 Klaus Neuner a �crit : > > All right, I admit that eval() is evil and should never be used. Can you tell the difference between your above statement and the following: """ eval() is potentially dangerous and can make code harder to debug. 99% of the proposed use case for eval() are covered by simpler, less dangerous and easier to understand solutions, so the GoodPractice(tm) is to favor these solutions and only use eval() - with appropriate care - for the remaining 1% _real_ use case. """ If you can't tell the difference, then you're about as (im)mature as my 13 year old son and it might eventually be time to grow up. > The same applies to knives. You shouldn't use them. You > shouldn't even use them in your own kitchen. A man might enter your > kitchen, take your knife away and use it against you. Knives - specially the kind I use in my kitchen - are indeed potentially dangerous, and I indeed had to educate my son so he wouldn't do anything stupid with them - like pointing a knife at someone, running across the house with a knife in his hand, or using them instead of a more appropriate tool. The probability that someone will enter your kitchen and use one of your knives against you, while not null, are low enough to be ignored IMHO. I whish I could say the same about script kiddies or more educated (and dangerous) bad guys trying to attack our servers. But you obviously never had to neither fix a compromised server nor raise a kid - else you'd now better. Hopefully you didn't raise my kid - now I just pray none of your code will ever run on our servers.
From: Klaus Neuner on 10 Feb 2010 08:24 On Feb 10, 12:55 pm, Bruno Desthuilliers <bruno. 42.desthuilli...(a)websiteburo.invalid> wrote: > KlausNeunera écrit : > > > > > All right, I admit that eval() is evil and should never be used. > > Can you tell the difference between your above statement and the following: As already pointed out in my second post (though perhaps not explicitly enough), I like the getattr-stuff better than eval(). That is why I will not use eval(). I don't have a reason to use eval(). All I wanted to say is this: If there are no circumstances at all under which eval() can reasonably be used, then it should not be part of Python. As it is part of Python (and as Python is a carefully designed language), there will most probably some situations in which one might want to use it.
From: Bruno Desthuilliers on 10 Feb 2010 08:51
Klaus Neuner a �crit : > On Feb 10, 12:55 pm, Bruno Desthuilliers <bruno. > 42.desthuilli...(a)websiteburo.invalid> wrote: >> KlausNeunera �crit : >> >> >> >>> All right, I admit that eval() is evil and should never be used. >> Can you tell the difference between your above statement and the following: > > As already pointed out in my second post (though perhaps not > explicitly enough), Or perhaps is it me that failed to re-read a bit more of the thread before answering - I obviously missed the irony (and made an a... of myself), sorry :-/ > All > I wanted to say is this: If there are no circumstances at all under > which eval() can reasonably be used, then it should not be part of > Python. As it is part of Python (and as Python is a carefully designed > language), there will most probably some situations in which one might > want to use it. Indeed. |