[issue7935] Cross-reference ast.literal_eval() from eval() docs

2010-07-11 Thread Georg Brandl
Georg Brandl added the comment: Added reference in r82805. Thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue7935] Cross-reference ast.literal_eval() from eval() docs

2010-07-10 Thread Mark Lawrence
Changes by Mark Lawrence : -- assignee: georg.brandl -> d...@python nosy: +d...@python versions: +Python 3.2 -Python 2.6 ___ Python tracker ___ ___

[issue7935] Cross-reference ast.literal_eval() from eval() docs

2010-02-15 Thread Kent Johnson
New submission from Kent Johnson : eval() is a known security hole. Since Python 2.6 ast.literal_eval() provides a better alternative in many cases. literal_eval() is not as well known as eval() and not easy to find even if you know it exists (but don't remember the name). eval() comes up over