tags:

views:

419

answers:

3

So, we have had this: http://lucumr.pocoo.org/2009/3/1/the-1000-speedup-or-the-stdlib-sucks. It demonstrates a rather bad bug that is probably costing the universe a load of cycles even as we speak. It's fixed now, which is great.

So what parts of the standard library have you noticed to be evil?

I would expect all the responsible people to match up an answer with a bug report (if suitable) and a patch (if superman).

+8  A: 

Never attribute to malice that which can be adequately explained by stupidity.

Pete Kirkham
Stupidity is just a specialized form of laziness.
Mike
But still not malice.
S.Lott
Also, evil code does not necessarily imply intent of malice on its creation.
Ali A
@Ali A: Evil doesn't mean evil? Or evil doesn't mean malicious? Or what don't you mean? Or is the question poorly worded? I thought evil meant malicious.
S.Lott
If you are redefining 'evil' as 'does something you don't like', then you have problems well beyond anything stackoverflow can help you with. Inefficient code isn't evil, it's just in need of a little TLC.
Pete Kirkham
S.Lott: the code wasn't designed to be evil (ie malice by developers) but it is evil. There is no contradiction here.
Ali A
@Ali A: too subtle for me.
S.Lott
S.Lott: Fair enough.
Ali A
+3  A: 

The rexec module has so many security holes in it that it's almost useless.

Jason Baker
Rexec is deprecated in version 2.6 and removed in 3.0
dF
Yes indeed it is. It's deprecated due to being an evil module. :-)
Jason Baker
It's been disabled since 2.3.
Benjamin Peterson
+2  A: 

(since this is a different module, placing it in a different answer)

cgitb has some weird threading issues. See this bug report.

Jason Baker