<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Exceptions on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/exceptions/</link><description>Recent content in Exceptions on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Tue, 29 May 2012 16:30:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/exceptions/index.xml" rel="self" type="application/rss+xml"/><item><title>Being exceptional</title><link>http://karpoke.ignaciocano.com/2012/05/29/being-exceptional/</link><pubDate>Tue, 29 May 2012 16:30:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/05/29/being-exceptional/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Apparently, in Python, it is easier to ask for forgiveness rather than
seek permission. That is to say, the normal approach when writing
Python code is to assume that what you are trying to do will work
properly. If something exceptional happens and the code doesn’t work
the way you were hoping, then the Python interpreter will tell you of
the error so that you can handle that exceptional circumstance. This
general approach, of trying to do something, then cleaning up if
something goes wrong is acronymically called EAFP (”easier to ask for
forgiveness than permission”).&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>