>This one is huge and requires example to be run to see the actual error. Is
>that a minimal example? I don't even have an idea fails there.
Obviously small files might work, but that's no help. I didn't have the time to
spend to make the example smaller. It is not *that* large, but it is
On Sat, Apr 27, 2013 at 12:24 PM, Vinay Sajip wrote:
> anatoly techtonik gmail.com> writes:
> > Why reinvent own format when there is already YAML with indented
> sections?
> > Yes, I have to see examples to write in this format, but it is readable
> and
> > familiar across a broad range of produ
On Apr 27, 2013, at 5:24 AM, Vinay Sajip wrote:
> anatoly techtonik gmail.com> writes:
>> Why reinvent own format when there is already YAML with indented sections?
>> Yes, I have to see examples to write in this format, but it is readable and
>> familiar across a broad range of products. It is
anatoly techtonik gmail.com> writes:
> Why reinvent own format when there is already YAML with indented sections?
> Yes, I have to see examples to write in this format, but it is readable and
> familiar across a broad range of products. It is better than JSON at least,
> because it doesn't require
On Thu, Apr 25, 2013 at 4:58 PM, Daniel Holth wrote:
> I would prefer to see PEP 390 withdrawn and I think this has been
> suggested before. The metadata is already sourced from different files
> depending on your build system.
>
> The .ini format and our parsers for it are really awful. I always