[issue19841] ConfigParser PEP issues

2016-02-14 Thread Berker Peksag
Berker Peksag added the comment: Thanks for the patch, Ivailo. The following changes are going to break the public API: -def get(self, section, option, raw=False, vars=None): +def get(self, section, option, raw=False, vvars=None): -def items(self, section, raw=False, va

[issue19841] ConfigParser PEP issues

2014-06-27 Thread brian yardy
brian yardy added the comment: Do you mean PEP 8 violations? These aren’t usually enough to cause a change.'http://www.einstantloan.co.uk/' -- nosy: +brianyardy ___ Python tracker

[issue19841] ConfigParser PEP issues

2013-12-06 Thread Éric Araujo
Éric Araujo added the comment: Do you mean PEP 8 violations? These aren’t usually enough to cause a change. -- nosy: +eric.araujo ___ Python tracker ___

[issue19841] ConfigParser PEP issues

2013-11-30 Thread R. David Murray
R. David Murray added the comment: Oh, and even if we decided there was enough reason to want to change the parameter names (which so far it doesn't look like there is), it could never be applied to 2.7, since the 2.7 API is frozen. -- ___ Python tr

[issue19841] ConfigParser PEP issues

2013-11-30 Thread R. David Murray
R. David Murray added the comment: Can you explain what the source of the problem is that you are trying to solve? It sounds like a bug in Nuitka, whatever that is. It is doubtful that this patch would be applied, for the backward compatibility reasons you cite. -- nosy: +r.david.mur

[issue19841] ConfigParser PEP issues

2013-11-30 Thread Ivailo Monev
New submission from Ivailo Monev: There are a few PEP violations like namespace clashes, the attached patch fixes some of them thus solving a problem for me where shared library build with Nuitka segmentation faults. The patch does not make the code backwards compatible with the vars and map a