Update

damianavila · Jun 25, 2016 · feb4242 · feb4242
1 parent 07b3a39
commit feb4242
Show file tree

Hide file tree

Showing 439 changed files with 3,160 additions and 2,557 deletions.
diff --git a/.doit.db.bak b/.doit.db.bak
diff --git a/.doit.db.dat b/.doit.db.dat
diff --git a/.doit.db.dir b/.doit.db.dir
diff --git a/cache/jinja/__jinja2_1424a9c95f5ec8e60d413c42a25bc77a4b63ee8b.cache b/cache/jinja/__jinja2_1424a9c95f5ec8e60d413c42a25bc77a4b63ee8b.cache
diff --git a/cache/jinja/__jinja2_42065261e76b7ac61d15945dd99b46d11ef2d31d.cache b/cache/jinja/__jinja2_42065261e76b7ac61d15945dd99b46d11ef2d31d.cache
diff --git a/cache/jinja/__jinja2_5e46cfeeff2a14274a55bed284465c9788e60bfe.cache b/cache/jinja/__jinja2_5e46cfeeff2a14274a55bed284465c9788e60bfe.cache
diff --git a/cache/jinja/__jinja2_6f282171a8cdf0b1d052845180e9f1d41795e21c.cache b/cache/jinja/__jinja2_6f282171a8cdf0b1d052845180e9f1d41795e21c.cache
diff --git a/cache/jinja/__jinja2_7830d3f16300ea9de776daccdd24768191c04b5d.cache b/cache/jinja/__jinja2_7830d3f16300ea9de776daccdd24768191c04b5d.cache
diff --git a/cache/jinja/__jinja2_84e16a5b9f3c1efa83de2b6ac826e4dbcb6178cc.cache b/cache/jinja/__jinja2_84e16a5b9f3c1efa83de2b6ac826e4dbcb6178cc.cache
diff --git a/cache/jinja/__jinja2_9291b64d965e3e2b21882411531c4d34140a55c5.cache b/cache/jinja/__jinja2_9291b64d965e3e2b21882411531c4d34140a55c5.cache
diff --git a/cache/jinja/__jinja2_95dcbcecedf99467da5bb0df105ee2a209178f70.cache b/cache/jinja/__jinja2_95dcbcecedf99467da5bb0df105ee2a209178f70.cache
diff --git a/cache/jinja/__jinja2_9a2dbf2f11ac9ceec1567e1477f9b082e5ba019a.cache b/cache/jinja/__jinja2_9a2dbf2f11ac9ceec1567e1477f9b082e5ba019a.cache
diff --git a/cache/jinja/__jinja2_aa4c5f9b2114de49dbb24f9795db3d027dcb6c9c.cache b/cache/jinja/__jinja2_aa4c5f9b2114de49dbb24f9795db3d027dcb6c9c.cache
diff --git a/cache/jinja/__jinja2_bf78ea284af06dd653f1623611857af052bad3c2.cache b/cache/jinja/__jinja2_bf78ea284af06dd653f1623611857af052bad3c2.cache
diff --git a/cache/jinja/__jinja2_cbc9a091eb48b5090675149305c77e62c07c71b3.cache b/cache/jinja/__jinja2_cbc9a091eb48b5090675149305c77e62c07c71b3.cache
diff --git a/cache/jinja/__jinja2_d06f80e87f6c1154a7feae3ec018611d7ca3c572.cache b/cache/jinja/__jinja2_d06f80e87f6c1154a7feae3ec018611d7ca3c572.cache
diff --git a/cache/jinja/__jinja2_dc70340a21ee55f35ec1d41b8d93a04a4e5ed57e.cache b/cache/jinja/__jinja2_dc70340a21ee55f35ec1d41b8d93a04a4e5ed57e.cache
diff --git a/cache/jinja/__jinja2_fe569e1a8fb097e480cc5158b505aca831f2517b.cache b/cache/jinja/__jinja2_fe569e1a8fb097e480cc5158b505aca831f2517b.cache
diff --git a/cache/posts/How-to-pin-Conda.html b/cache/posts/How-to-pin-Conda.html
diff --git a/cache/posts/How-to-pin-Conda.html.es b/cache/posts/How-to-pin-Conda.html.es
diff --git a/cache/posts/how-to-pin-conda.html b/cache/posts/how-to-pin-conda.html
@@ -4,21 +4,24 @@
 </div>
 <div class="inner_cell">
 <div class="text_cell_render border-box-sizing rendered_html">
-<p>One interesting advance feature in Conda in the capacity to pin packages from your environments so they can not be updated at all. If you are interested in <strong>that</strong> specific version of some package and not the next one because it breaks you completely or because some other reason, you are probably pinning that package (if this is not the case, you should do the pin in the way I will describe instead of adding the specific version in every command you run). But... is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?
+<p>One interesting advance feature in Conda is the capacity to pin packages from your environments so they can not be updated at all. If you are interested in <strong>that</strong> specific version of some package and not the next one because it breaks your work completely or for some other reason, you are probably <em>pinning</em> that package. If you are adding the specific version in every command you run instead of <em>pinning</em> the package, you are doing it wrong and you should keep reading ;-)</p>
+<p>But, is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?
 <!-- TEASER_END --></p>
 <p>If you don't know what Conda is, you should probably go <a href="http://conda.pydata.org/docs/">here</a> and learn a little bit about it. For the lazy ones:</p>
 <blockquote><p>Conda is an open source package management system and environment management system for installing multiple versions of software packages and their dependencies and switching easily between them. It works on Linux, OS X and Windows, and was created for Python programs but can package and distribute any software.</p>
 </blockquote>
-<p>One interesting behavior in Conda is that it gets updated to the latest version every time you try to install/update something else. That is a reasonable behavior in the general context but, for some specific use cases, that can be undesirable. And in the previous undesire you have the origin of the main question I raised before: is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?</p>
+<p>One interesting behavior in Conda is that it gets updated to the latest version every time you try to install/update something else. That is a reasonable behavior in the general context but, for some specific use cases, that can be undesirable. This motivates the main question I raised before: is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?</p>
 <p>I have heard a lot of people saying it is impossible to pin Conda, BUT that's not the case ;-)</p>
 <p>You can pin Conda the same way you pin any other package.</p>
-<p>Let me show you how you can do it... is <strong>really</strong> simple. Just one line:</p>
-<div class="highlight"><pre><span></span><span class="nb">echo</span> <span class="s2">&quot;conda ==4.0.0&quot;</span> &gt; ~/anaconda/conda-meta/pinned
+<p>Let me show you how you can do it... is <strong>really</strong> simple:</p>
+<div class="highlight"><pre><span></span><span class="nb">echo</span> <span class="s2">&quot;conda ==4.0.0&quot;</span> &gt;&gt; ~/anaconda/conda-meta/pinned
 </pre></div>
-<p>This will create a file called <code>pinned</code> containing the <code>conda</code> package version you are interested to keep (in this case, I choose the version <code>4.0.0</code>). This <code>pinned</code> file should be located in the <code>conda-meta</code> directory from your anaconda (or miniconda) installation. Then, every time you try to install or update something, this <code>pinned</code> file is read by Conda and the line with the <code>conda</code> specific version is added to the list sent to the SAT solver, hence you will always have that specification <em>enabled</em>, preventing you to update to a newer conda. Nice, don't you think?</p>
-<p>You can remove that file when you are ready to catch a new Conda version or alternative you can run <code>conda</code> install/update commands with the <code>--no-pin</code> option.</p>
+<p>This will create (or pass the string into) a file called <code>pinned</code> containing the <code>conda</code> package version you wish to keep (in this case, I choose the version <code>4.0.0</code>). This <code>pinned</code> file should be located in the <code>conda-meta</code> directory of your anaconda (or miniconda) installation. Then, every time you try to install or update something, this <code>pinned</code> file is read by Conda and the line with the <code>conda</code> specific version is added to the list sent to the SAT solver, hence you will always have that specification <em>enabled</em>, preventing you from updating to a newer Conda. Nice, don't you think?</p>
+<p>You can remove that file when you are ready to catch a new Conda version or alternatively you can run <code>conda</code> install/update commands with the <code>--no-pin</code> option.</p>
 <p>Hope this helps others! If not, at least, it was fun to play a little bit with this feature!</p>
 <p>See you next time!</p>
+<p><strong>PS1</strong>: Thanks Will for reviewing my wording!</p>
+<p><strong>PS2</strong>: Starting Conda version <code>4.0.9</code>, you have a new config option called <code>auto_update_conda</code> to disable the self update nature in Conda.</p>
 
 </div>
 </div>

diff --git a/cache/posts/how-to-pin-conda.html.es b/cache/posts/how-to-pin-conda.html.es
@@ -4,21 +4,24 @@
 </div>
 <div class="inner_cell">
 <div class="text_cell_render border-box-sizing rendered_html">
-<p>One interesting advance feature in Conda in the capacity to pin packages from your environments so they can not be updated at all. If you are interested in <strong>that</strong> specific version of some package and not the next one because it breaks you completely or because some other reason, you are probably pinning that package (if this is not the case, you should do the pin in the way I will describe instead of adding the specific version in every command you run). But... is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?
+<p>One interesting advance feature in Conda is the capacity to pin packages from your environments so they can not be updated at all. If you are interested in <strong>that</strong> specific version of some package and not the next one because it breaks your work completely or for some other reason, you are probably <em>pinning</em> that package. If you are adding the specific version in every command you run instead of <em>pinning</em> the package, you are doing it wrong and you should keep reading ;-)</p>
+<p>But, is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?
 <!-- TEASER_END --></p>
 <p>If you don't know what Conda is, you should probably go <a href="http://conda.pydata.org/docs/">here</a> and learn a little bit about it. For the lazy ones:</p>
 <blockquote><p>Conda is an open source package management system and environment management system for installing multiple versions of software packages and their dependencies and switching easily between them. It works on Linux, OS X and Windows, and was created for Python programs but can package and distribute any software.</p>
 </blockquote>
-<p>One interesting behavior in Conda is that it gets updated to the latest version every time you try to install/update something else. That is a reasonable behavior in the general context but, for some specific use cases, that can be undesirable. And in the previous undesire you have the origin of the main question I raised before: is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?</p>
+<p>One interesting behavior in Conda is that it gets updated to the latest version every time you try to install/update something else. That is a reasonable behavior in the general context but, for some specific use cases, that can be undesirable. This motivates the main question I raised before: is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?</p>
 <p>I have heard a lot of people saying it is impossible to pin Conda, BUT that's not the case ;-)</p>
 <p>You can pin Conda the same way you pin any other package.</p>
-<p>Let me show you how you can do it... is <strong>really</strong> simple. Just one line:</p>
-<div class="highlight"><pre><span></span><span class="nb">echo</span> <span class="s2">&quot;conda ==4.0.0&quot;</span> &gt; ~/anaconda/conda-meta/pinned
+<p>Let me show you how you can do it... is <strong>really</strong> simple:</p>
+<div class="highlight"><pre><span></span><span class="nb">echo</span> <span class="s2">&quot;conda ==4.0.0&quot;</span> &gt;&gt; ~/anaconda/conda-meta/pinned
 </pre></div>
-<p>This will create a file called <code>pinned</code> containing the <code>conda</code> package version you are interested to keep (in this case, I choose the version <code>4.0.0</code>). This <code>pinned</code> file should be located in the <code>conda-meta</code> directory from your anaconda (or miniconda) installation. Then, every time you try to install or update something, this <code>pinned</code> file is read by Conda and the line with the <code>conda</code> specific version is added to the list sent to the SAT solver, hence you will always have that specification <em>enabled</em>, preventing you to update to a newer conda. Nice, don't you think?</p>
-<p>You can remove that file when you are ready to catch a new Conda version or alternative you can run <code>conda</code> install/update commands with the <code>--no-pin</code> option.</p>
+<p>This will create (or pass the string into) a file called <code>pinned</code> containing the <code>conda</code> package version you wish to keep (in this case, I choose the version <code>4.0.0</code>). This <code>pinned</code> file should be located in the <code>conda-meta</code> directory of your anaconda (or miniconda) installation. Then, every time you try to install or update something, this <code>pinned</code> file is read by Conda and the line with the <code>conda</code> specific version is added to the list sent to the SAT solver, hence you will always have that specification <em>enabled</em>, preventing you from updating to a newer Conda. Nice, don't you think?</p>
+<p>You can remove that file when you are ready to catch a new Conda version or alternatively you can run <code>conda</code> install/update commands with the <code>--no-pin</code> option.</p>
 <p>Hope this helps others! If not, at least, it was fun to play a little bit with this feature!</p>
 <p>See you next time!</p>
+<p><strong>PS1</strong>: Thanks Will for reviewing my wording!</p>
+<p><strong>PS2</strong>: Starting Conda version <code>4.0.9</code>, you have a new config option called <code>auto_update_conda</code> to disable the self update nature in Conda.</p>
 
 </div>
 </div>