This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author stevemerritt
Recipients berker.peksag, serhiy.storchaka, stevemerritt
Date 2017-01-01.22:11:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
We're using Python dictionaries to express sizeable (read: 100-600 lines)
chunks of configuration data. We previously used JSON, but we now use
Jinja2 to template chunks of this configuration data, and JSON's inability
to handle trailing commas creates a problem here. So we've been using
ast.literal_eval, but the lack of line numbers makes debugging problems
with the configurations a painful process.

On Sun, Jan 1, 2017 at 2:41 AM Serhiy Storchaka <>

> Serhiy Storchaka added the comment:
> Usually literal_eval() is used with short one-line input. For what large
> documents do you use it?
> ----------
> nosy: +serhiy.storchaka
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2017-01-01 22:11:46stevemerrittsetrecipients: + stevemerritt, berker.peksag, serhiy.storchaka
2017-01-01 22:11:46stevemerrittlinkissue28964 messages
2017-01-01 22:11:46stevemerrittcreate