On Apr 25, 2014, at 11:47 AM, Terry Reedy wrote:
>So I wonder whether the thought-to-be-buggy behavior is
>actually buggy with respect to *all* the supported styles or just some of them.
I can't how being able to write a file that isn't read back with the
same meaning could be anything but a bug
On Sat, Apr 26, 2014 at 7:23 AM, Steven D'Aprano wrote:
> But the entry in question wasn't a line, it was a key=value pair in a
> dict. Here's that line again:
>
> cp.read_dict({'DEFAULT': {';foo': 'bar'}})
>
> or it could have been:
>
> cp['DEFAULT'][';foo'] = 'bar'
>
> Either way, if there's no
I accidentally posted a question to here. I am returning to Python after a
couple years away and I am trying to brush up my skills and make the switch to
Python 3.x.
---Andrew
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.or
On Sat, Apr 26, 2014 at 01:59:27AM -0400, Fred Drake wrote:
> On Sat, Apr 26, 2014 at 1:34 AM, Steven D'Aprano wrote:
> > I think that a line beginning with "#spam" is ambiguous, it isn't clear
> > if it is intended as a comment "spam" or a key starting with #, so by
> > the Zen, configparser shou
Donald Stufft writes:
> For instance there are things on PyPI named after websites, like
> github, twitter, Facebook, etc. These things are not written by the
> companies behind those websites and are merely written to interface
> with those websites. Should we assume that those companies all
On Fri, Apr 25, 2014 at 08:42:02PM -0400, Donald Stufft wrote:
>
> On Apr 25, 2014, at 7:20 PM, Ethan Furman wrote:
>
> > On 04/25/2014 03:26 PM, Donald Stufft wrote:
> >>
> >> pep8.py doesn’t violate PEP8, it just takes a stricter view of it.
> >
> > If pep8 reports errors on things that PEP