Message 166468 - Python tracker

➜

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	vinay.sajip
Recipients	Arfrever, ncoghlan, vinay.sajip
Date	2012-07-26.08:55:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1343292943.33.0.721984694938.issue15452@psf.upfronthosting.co.za>
In-reply-to

Content
It's not actually the PEP 391 implementation - dictConfig() - that uses eval(). Rather, it's the older fileConfig() API which was part of the original logging package when added to Python 2.3. The use of eval() by fileConfig() was documented at that time, IIRC. I have no problem in principle with updating fileConfig() - which uses eval() in just one private function - to use ast.literal_eval(), but it may break existing, innocuous code which can't be handled by ast.literal_eval().

It's not actually the PEP 391 implementation - dictConfig() - that uses eval(). Rather, it's the older fileConfig() API which was part of the original logging package when added to Python 2.3. The use of eval() by fileConfig() was documented at that time, IIRC.

I have no problem in principle with updating fileConfig() - which uses eval() in just one private function - to use ast.literal_eval(), but it may break existing, innocuous code which can't be handled by ast.literal_eval().

History
Date	User	Action	Args
2012-07-26 08:55:43	vinay.sajip	set	recipients: + vinay.sajip, ncoghlan, Arfrever
2012-07-26 08:55:43	vinay.sajip	set	messageid: <1343292943.33.0.721984694938.issue15452@psf.upfronthosting.co.za>
2012-07-26 08:55:42	vinay.sajip	link	issue15452 messages
2012-07-26 08:55:42	vinay.sajip	create