Message213092
As far as I can tell from scanning this ticket, there was no agreement on deprecating the parser argument to iterparse, but it has been documented as deprecated with no documentation about what to replace it with, nor any DeprecationWarning in the code that I can see. Should I remove the deprecation documentation and someone can figure out what to do about it in 3.5, or was the decision just not recorded here (or I missed it)? (It doesn't look like there's a programatic deprecation for the html argument either.) |
|
Date |
User |
Action |
Args |
2014-03-10 22:05:14 | r.david.murray | set | recipients:
+ r.david.murray, jcea, ncoghlan, scoder, jkloth, eli.bendersky, flox, ethan.furman, python-dev |
2014-03-10 22:05:14 | r.david.murray | set | messageid: <1394489114.53.0.266958516036.issue17741@psf.upfronthosting.co.za> |
2014-03-10 22:05:14 | r.david.murray | link | issue17741 messages |
2014-03-10 22:05:14 | r.david.murray | create | |
|