<?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>Python3 on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/python3/</link><description>Recent content in Python3 on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sun, 31 Jan 2016 16:22:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/python3/index.xml" rel="self" type="application/rss+xml"/><item><title>Why ‘print’ became a function in Python 3</title><link>http://karpoke.ignaciocano.com/2016/01/31/why-print-became-a-function-in-python-3/</link><pubDate>Sun, 31 Jan 2016 16:22:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/01/31/why-print-became-a-function-in-python-3/</guid><description>&lt;blockquote&gt;
&lt;p&gt;But the real key to the print function is somewhat subtle and it all
has to do with flexibility, both for the users and the Python
development team. For users, making print a function lets you use
print as an expression, unlike the print statement which can only be
used as a statement.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Brett Cannon | &lt;a href="http://www.snarky.ca/why-print-became-a-function-in-python-3"&gt;snarky.ca&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>