Nick Coghlan writes:
> That would make the following the lowest impact resolution that still
> fixes the original reported problem:
>
> - update the ConfigParser (3.x) and SafeConfigParser (2.x) docs to
> explicitly say that "%%" works as an escape
> - update setuptools and
On 28 July 2017 at 15:39, Robert Collins wrote:
> On 28 July 2017 at 15:34, Nick Coghlan wrote:
>> Clarifying to add: I think this is a worthwhile change, as it helps to
>> ensure that the static config files actually *are* static, and hence
>> less
On 28 July 2017 at 15:34, Nick Coghlan wrote:
> On 28 July 2017 at 13:30, Nick Coghlan wrote:
>> On 28 July 2017 at 01:32, Jason R. Coombs wrote:
>>> I’d like feedback, in either ticket, about whether this change is worth the
>>>
On 28 July 2017 at 13:30, Nick Coghlan wrote:
> On 28 July 2017 at 01:32, Jason R. Coombs wrote:
>> I’d like feedback, in either ticket, about whether this change is worth the
>> trouble and if so if there are any ways to mitigate the risks of introducing
On 28 July 2017 at 01:32, Jason R. Coombs wrote:
> I’d like feedback, in either ticket, about whether this change is worth the
> trouble and if so if there are any ways to mitigate the risks of introducing
> such a change.
The one way I can see of doing this with a graceful
In Setuptools #889 (https://github.com/pypa/setuptools/issues/889) and Python
20754 (http://bugs.python.org/issue20754), setuptools and distutils are
proposing a backward-incompatible change - to remove ConfigParser interpolation
when parsing setup.cfg (and maybe other config) files.
I’d