title: Why is there {Raw,Safe}ConfigParser in Python 3?
body: <p>Am surprised there's 3 different forms: <code>RawConfigParser</code>, <code>SafeConfigParser</code> and <code>ConfigParser</code> (<a href="http://docs.python.org/library/configparser" rel="noreferrer">docs</a>). I read the differences but why isn't everyone using <code>SafeConfigParser</code>, since it seems, well, safe? I can understand that in the case for Python 2 that the other two were kept for backward compatibility.</p>
  
  <p><strong>UPDATE</strong>: In Python 3.2, SafeConfigParser has been renamed to ConfigParser, and the old ConfigParser has been removed (source: <a href="http://docs.python.org/py3k/whatsnew/3.2.html#configparser" rel="noreferrer">NEWS for Python 3.2</a>).</p>