[issue27467] distutils.config API different between <=3.5.1 and 3.5.2

Berker Peksag added the comment: I was thinking to document issue 20120 in Misc/NEWS. It turns out I was looking at the wrong commit and it was already documented in eae59b6bf133. -- resolution: -> not a bug stage: needs patch -> resolved status: open -> closed

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2

Xiang Zhang added the comment: Berker, what doc needs to be changed? Although RawConfigParser is legacy but that does not mean it's deprecated, right? We can still use it although the doc suggests us use ConfigParser. -- ___ Python tracker

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2

Berker Peksag added the comment: Thanks for the report. Yes, the RawConfigParser change was intentional and it was discussed in issue 20120. I'm marking this as a documentation issue. -- assignee: -> docs@python components: +Documentation nosy: +berker.peksag, docs@python stage: ->

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2

Xiang Zhang added the comment: I think it's intentional. You can see issue20120. -- nosy: +xiang.zhang ___ Python tracker ___

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2

New submission from Joe: In Python 3k releases leading up to 3.5.2, distutils.config imported "ConfigParser", but now imports "RawConfigParser" in the latest release. The documentation indicates "RawConfigParser" is considered legacy and "ConfigParser" should be used in its place. Was this