Message146236
The PEP 387 suggests that deprecated objects or arguments are removed in version (n+1).
I've listed these DeprecationWarnings in 3.2, which are still in 3.3.
I assume that most of these deprecated objects or arguments could be removed before next release.
*_pyio*
argument "max_buffer_size" of BufferedWriter and BufferedRWPair
*argparse*
argument "version" and related methods of ArgumentParser
*asyncore*
shortcut "dispatcher.*" for "dispatcher.socket.*" attributes
*base64*
functions "encodestring" and "decodestring"
*cgi*
functions "parse_qs" and "parse_qsl"
*configparser*
"ParsingError.filename", "RawConfigParser.readfp", "SafeConfigParser"
*decimal*
"Context._clamp"
*difflib*
"SequenceMatcher.isbjunk", "SequenceMatcher.isbpopular"
*gzip*
"GzipFile.filename"
*http.client*
argument "strict" of HTTPResponse and HTTPConnection
*lib2to3*
methods "set_prefix" and "get_prefix" of "pytree.Base"
*mailbox*
argument of type "StringIO" or "text mode files"
*ntpath*
function "splitunc"
*tarfile*
argument "exclude" of "TarFile.add"
*trace*
old API
*unittest*
"assert{DictContainsSubset,RaisesRegexp,RegexpMatches}", "fail*"
*xml.etree*
"Element.getchildren", "XMLParser.doctype" |
|
Date |
User |
Action |
Args |
2011-10-23 17:49:46 | flox | set | recipients:
+ flox |
2011-10-23 17:49:46 | flox | set | messageid: <1319392186.66.0.823106983991.issue13248@psf.upfronthosting.co.za> |
2011-10-23 17:49:46 | flox | link | issue13248 messages |
2011-10-23 17:49:45 | flox | create | |
|