OK, a short post to give you some material to play with over the weekend ;-).
+
Today, I woke up early and whereas I was drinking a mate (a native drink here in Argentina) for breakfast, I remember a tweet from Nikhil Sonnad where I was mentioned:
The themes are css files, so we can create a new profile for each theme and add the css content to the custom.css file inside each profile.
+To do it, I use some little magic tricks from IPython...
Now, I want to try it... quickly... so I launch a new IPython server for each profile in specific ports. I also pass the --no-browser option to avoid opening 48 tabs in a row (depending of your computing power this can be problematic).
Finally, because I am lazy ;-), I build the urls to see this same notebook with each different theme (don't forget to use the incognito mode of your browser to avoid css caching and at least IPython 2.0).
OK, a lot of IPython servers opened, let's kill them all!!! I feel like George R. R. Martin ;-).
+
+
+
+
+
+
+
In [ ]:
+
+
+
!killall -9 ipython
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
Obviously, this command also killed the current notebook (remember, this post is in fact an IPython notebook, and you can get it from the source link at the top of the post)... but I am right with that... this is the end of this post.
+
Final note: I did not like any complete theme, but I really like some part from several themes, so it worths to see them to take each nice part and make my own theme in the future.
+
Good weekend!
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/48-themes-for-your-ipython-notebook.es.html.dep b/cache/posts/48-themes-for-your-ipython-notebook.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/a-little-hack-to-get-a-pdf-from-your-ipython-slides.es.html b/cache/posts/a-little-hack-to-get-a-pdf-from-your-ipython-slides.es.html
new file mode 100644
index 00000000..f28ec323
--- /dev/null
+++ b/cache/posts/a-little-hack-to-get-a-pdf-from-your-ipython-slides.es.html
@@ -0,0 +1,27 @@
+
+
+
+
+
+
A lot of users of the slides option in IPython.nbconvert asked me about how to get a pdf from the generated Reveal.js-based slideshow.
+
To make the story short, here you have the detailed steps:
+
So, time to write some code and do a PR... in the meantime use this hack ;-)
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/a-little-hack-to-get-a-pdf-from-your-ipython-slides.es.html.dep b/cache/posts/a-little-hack-to-get-a-pdf-from-your-ipython-slides.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/a-new-nikolas-theme-for-my-site-zen.es.html b/cache/posts/a-new-nikolas-theme-for-my-site-zen.es.html
new file mode 100644
index 00000000..8f322a08
--- /dev/null
+++ b/cache/posts/a-new-nikolas-theme-for-my-site-zen.es.html
@@ -0,0 +1,20 @@
+
+
+
+
+
+
Some days ago, Aru Sahni wrote to Nikola's forum and posted a link to his site... I really like the theme he was using so I though to take it as a starting point to develop my own theme.
+
+
I had to re-wrote some things to accommodate the templates to the last Nikola v6.0.0 release (in fact, I usually use master from Github, but I recommend you to use the released code for production), and to make the theme more generic one and easy to re-use by others.
+
I got a clean and (I think) easy to read theme, with awesome icons (Font-awesome's if you didn't recognize yet), supporting both desktops/laptops and mobile devices and... I like it very much ;-)
+
It was a great exercise to learn more about html, js, css and less (a very interesting approach to deal with css).
+
I will publish the generic zen theme and the zen-ipython theme (which I'm using and you are seeing... right now) at the Nikola theme repository in a few days, after some more testing and customization.
+
Thanks again Aru Sahni, you are in some way the trigger for this theme... and very fun hours I experienced developing and learning by doing.
+
Damián.
+
PS: If you have any to say about the overall design, ideas for improvements, things you hate about this theme, just let me know in the comments. Thanks.
+
+
+
+
+
+
diff --git a/cache/posts/a-new-nikolas-theme-for-my-site-zen.es.html.dep b/cache/posts/a-new-nikolas-theme-for-my-site-zen.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/a-poor-man-spell-checker-for-the-ipython-notebook.es.html b/cache/posts/a-poor-man-spell-checker-for-the-ipython-notebook.es.html
new file mode 100644
index 00000000..55ceabb2
--- /dev/null
+++ b/cache/posts/a-poor-man-spell-checker-for-the-ipython-notebook.es.html
@@ -0,0 +1,190 @@
+
+
+
+
+
+
OK, today I will release another IPythonjs extension: Spellchecker, which obviously do what you are thinking... spell check the content of your IPython notebook cells.
+
And why it is a poor man extension? Because it is a simple workaround to get the spell checker functionality and not a broad solution... but it works, and solve my spelling problems!
+
+
The main idea here is to use the spell checker functionality provided by your browser [yes, let to the others the complex things ;-)]. But, as you know, the spell checking functionality is disable inside the IPython notebook... and this is because each cell you actually see is a codemirror instance... and codemirror does not support spell checking by design... in fact, the codemirror text area (editor) is not a common html text area, hence the browser can not actually run the spell checker in this new text area.
+
So, are we prohibited to apply a spell checker functionality over a codemirror instance? In fact, no... there is a way to do it applying something called codemirror layouts and using js spell checker libraries...
+
But, I don't want to do this job yet (because of several causes which I do not describe here now), so I thought workaround and use the IPythonjs machinery to get a simple, narrow but useful solution.
+
The workaround is simple:
+
+
The spell checker will do its job at the cell level.
+
+
+
+
We need a way to get the content of the selected IPython notebook cell:
1 /*
+ 2 * ----------------------------------------------------------------------------
+ 3 * Copyright (c) 2013 - Damián Avila
+ 4 *
+ 5 * Distributed under the terms of the Modified BSD License.
+ 6 *
+ 7 * A little extension to spell check the selected cell from the IPython notebook.
+ 8 * ----------------------------------------------------------------------------
+ 9 */
+ 10
+ 11 function spellCheckerCSS() {
+ 12 var link = document.createElement("link");
+ 13 link.type = "text/css";
+ 14 link.rel = "stylesheet";
+ 15 link.href = require.toUrl("./custom/spellchecker/main.css");
+ 16 document.getElementsByTagName("head")[0].appendChild(link);
+ 17 }
+ 18
+ 19 function spellChecker(dummy) {
+ 20 console.log(dummy);
+ 21
+ 22 spellCheckerCSS();
+ 23
+ 24 var input = IPython.notebook.get_selected_cell().get_text()
+ 25
+ 26 var textarea = $('<textarea/>')
+ 27 .attr('rows','15')
+ 28 .attr('cols','80')
+ 29 .attr('name','source')
+ 30 .text(input);
+ 31
+ 32 var dialogform = $('<div/>')
+ 33 .append(
+ 34 $('<form/>').append(
+ 35 $('<fieldset/>').append(
+ 36 $('<label/>')
+ 37 .attr('for','source')
+ 38 .text("Now you can edit the cell content and use " +
+ 39 "the spellchecker support of your browser over it. " +
+ 40 "In Chromium, just focus in the text area and " +
+ 41 "select the text you want to spell check. Then you will " +
+ 42 "be able to use the contextual menu (right click) to get " +
+ 43 "words suggestion and other configuration options (lang). " +
+ 44 "Finally press OK to get the corrected cell content into " +
+ 45 "your selected IPython notebook cell.")
+ 46 )
+ 47 .append($('<br/>'))
+ 48 .append(
+ 49 textarea
+ 50 )
+ 51 )
+ 52 );
+ 53
+ 54 IPython.dialog.modal({
+ 55 title: "Edit and spell check your cell content",
+ 56 body: dialogform,
+ 57 buttons: {
+ 58 "OK": { class : "btn-primary",
+ 59 click: function() {
+ 60 var corr_input = $.trim($(textarea).val());
+ 61 console.log(corr_input);
+ 62 IPython.notebook.get_selected_cell().set_text(corr_input);
+ 63 }},
+ 64 Cancel: {}
+ 65 }
+ 66 });
+ 67
+ 68 }
+ 69
+ 70 define(function() {
+ 71 return {
+ 72 parameters: function setup(param1) {
+ 73 IPython.toolbar.add_buttons_group([
+ 74 {
+ 75 'label' : 'Spell check your selected cell content',
+ 76 'icon' : 'icon-check-sign',
+ 77 'callback': function(){spellChecker(param1)},
+ 78 'id' : 'start_spellcheck'
+ 79 },
+ 80 ]);
+ 81 var document_keydown = function(event) {
+ 82 if (event.which == 83 && event.altKey) {
+ 83 spellChecker(param1);
+ 84 return false;
+ 85 };
+ 86 return true;
+ 87 };
+ 88 $(document).keydown(document_keydown);
+ 89 }
+ 90 }
+ 91 });
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As you can see at the end of the code... you have not only a button but also a keyboard shortcut to activate the spell checker extension: ALT + S (remember that the same goes for the Tweet me extension, but with ALT + T).
+
Again, the extension lives in this new repo: mIPyex, where I will upload the development versions of my own extensions. When I get them enough stable, I will make a copy of them in the IPython notebook extensions repo where you can get a lot of and useful interesting extensions.
+
OK, I hope you enjoy and use this extension... because the IPython notebook is not only for write code... it is also powered to write other things, such as this blog post, and we have to keep spelling mistakes as low as possible to make the read of our content pleasant...
+
See you...
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/a-poor-man-spell-checker-for-the-ipython-notebook.es.html.dep b/cache/posts/a-poor-man-spell-checker-for-the-ipython-notebook.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/a-simple-minimap-for-your-nbconverted-ipynb.es.html b/cache/posts/a-simple-minimap-for-your-nbconverted-ipynb.es.html
new file mode 100644
index 00000000..a364e90c
--- /dev/null
+++ b/cache/posts/a-simple-minimap-for-your-nbconverted-ipynb.es.html
@@ -0,0 +1,95 @@
+
+
+
+
+
+
Some days ago, I presented a way to mimic the execution of nbconvertedIPython notebooks (ipynb). Today, I will show you how to add a simple minimap to these static html documents.
+
But, what is a minimap? Do you know SublimeText or Ninja-IDE? They are IDEs with a thin column to the right (of the main window) which provides an overview of the code we are working on... OK, you don't have an idea what am I talking about? Just go ahead and you will see...
+
+
Addendum note: There are some performance issues with Firefox, but in Chromium it is working OK! Simplicity comes with some hidden costs ;-)
+
NOTE: if you are impatient, just go the beginning of this post and press the Minimap link next to the Source link... and surprise!
+
Well, my first thought to develop this feature was to look if anybody had this same idea (a minimap for html-based documents) before, and obviously, there was somebody ;-)
+
Mr. Google pointed me to a blog where I found a nice js-based (working) solution.
+
The implementation was very simple and we used the same strategy from the last blog posts: pass a template in the IPython.nbconvert call from the command line (but please, do not forget that you can also use a config file to pass the template name -and other things - to the IPython.nbconvert infrastructure).
+
OK, but we needed to write the template before passing it, so we did it:
Do not forget!: There are some performance issues with Firefox, but in Chromium it is working OK! Simplicity comes with some hidden costs ;-)
+
Nice, don't you think?
+
We also did the same (with minor modifications) with our NikolaZen theme (probably you had already tested it because I assume you are impatient!).
+
Now, with this simple feature, you not only can quickly get an idea of the length of your documents (blog post, article, lecture, whatever...) but also they are easier to scroll and navigate!
+
NOTE: If you are thinking "I want this minimap with in my IPython notebooks", you will have to hack the source code of the js library I used because it was designed for simple windows and not for more complex structures such as the notebook itself.
+
Enjoy your minimaps!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/a-simple-minimap-for-your-nbconverted-ipynb.es.html.dep b/cache/posts/a-simple-minimap-for-your-nbconverted-ipynb.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/a-simple-overview-of-viper.es.html b/cache/posts/a-simple-overview-of-viper.es.html
new file mode 100644
index 00000000..6efcb6d6
--- /dev/null
+++ b/cache/posts/a-simple-overview-of-viper.es.html
@@ -0,0 +1,7 @@
+
La idea de este post es mostrar, a través de un simple video, algunas de las
+principales funciones de vIPer.
+
Aquí va:
+
+
La "limpieza" del código esta casi lista, por lo que lo liberaré en los próximos días...
+
Nos vemos pronto.
+
Damián.
diff --git a/cache/posts/a-simple-overview-of-viper.es.html.dep b/cache/posts/a-simple-overview-of-viper.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/beginning.es.html b/cache/posts/beginning.es.html
new file mode 100644
index 00000000..f5bb7337
--- /dev/null
+++ b/cache/posts/beginning.es.html
@@ -0,0 +1,13 @@
+
Durante 5 años, prácticamente todos los dias hábiles,
+he viajado desde La Plata hasta C.A.B.A. (ida y vuelta).
+He utilizado múltiples medios de locomoción: auto, colectivo, subte, tren...
+Muchas horas de transporte público han corrido "bajo el puente".
+Como podrán imaginar, durante estos "tiempos" he leído muchos papers, libros y diarios.
+He escuchado cientos de canciones. He charlado con varios amigos.
+También he dormido (mucho)... Pero no he escrito (en realidad, he escrito algunas cosas,
+pero esta actividad ha ocupado niveles de tiempo mínimos comparado con las
+actividades anteriormente mencionadas).
+Por lo tanto, he decidido que, desde este instante, y hasta que termine mi trabajo en C.A.B.A.,
+invertiré mis "tiempos" de viaje para escribir algunas "cosas" que luego publicaré en este blog.
+
Así que, ¡nos vemos pronto!
+
Damián.
diff --git a/cache/posts/beginning.es.html.dep b/cache/posts/beginning.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.es.html b/cache/posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.es.html
new file mode 100644
index 00000000..ffe24ac1
--- /dev/null
+++ b/cache/posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.es.html
@@ -0,0 +1,278 @@
+
+
+
+
+
+
The idea of this blog post is to show you how you can achieve an efficient bidirectional workflow to write your blog posts using great tools/features derived from IPython and Nikola.
+
Probably, this would be interesting not only for the people using IPython and Nikola to write their blog post, but also to other people because this would be a simple but nice example of how you can integrate this two applications to better suit your needs.
+
OK, first of all, let's go to the folder containing my blog:
+
+
+
+
+
+
+
+
+
+
+
damian@damian-S400CA:~$ cd /media/datos/Desarrollos/damian_blog
+
+damian@damian-S400CA:/media/datos/Desarrollos/damian_blog$
+
+
+
+
+
+
+
+
+
Then I activate my virtualenv specifically filled to build my blog:
+
+
+
+
+
+
+
+
+
+
damian@damian-S400CA:/media/datos/Desarrollos/damian_blog$ workon blog
+
+(blog)damian@damian-S400CA:/media/datos/Desarrollos/damian_blog$
+
+
+
+
+
+
+
+
+
Now, we are ready to the next step, calling the nikola console:
+
+
+
+
+
+
+
+
+
+
(blog)damian@damian-S400CA:/media/datos/Desarrollos/damian_blog$ nikola console
+Scanning posts......done!
+Python 2.7.4 (default, Apr 19 2013, 18:28:01)
+Type "copyright", "credits" or "license" for more information.
+
+IPython 1.1.0 -- An enhanced Interactive Python.
+? -> Introduction and overview of IPython's features.
+%quickref -> Quick reference.
+help -> Python's own help system.
+object? -> Details about 'object', use 'object??' for extra details.
+
+
+Nikola v6.1.1 -- IPython Console (conf = configuration, SITE = site engine)
+
+
+
+
+
+
+
+
+
Yes... Nikola offers a feature called nikola console which immediately opens an IPython console (if you have installed IPython, of course) where you can do a lot of things, as I will show you later, but also have direct access to Nikola internals through the conf (configuration) and SITE (site engine) objects. We can explore this objects using the tab completion from the IPython machinery:
But, we will probably go back to these objects in another blog post... now, we go again to the Nikola IPython console because we want to create a new post. The easiest way to do it is just calling the proper Nikola command using the ! to pass it from the Nikola IPython console to the shell.
+
+
In [1]: !nikola new_post -f ipynb
+
+
+
But we can do it better ;-)
+We can pass arguments to the nikola new_post command such as the title, tags, format (we have already pass the format with -f ipynb), etc. So, let me create some variables for these arguments inside my Nikola IPython console session:
+
+
In [1]: title = "Bidirectional IPython-Nikola workflow to write your blog post"
+
+In [2]: tags_list = ['python', 'IPython', 'nikola', 'blog', 'extension', 'gh-pages', 'git', 'workflow']
+
+In [3]: tags = ', '.join(tags_list)
+
+In [4]: tags
+Out[4]: u'python, IPython, nikola, blog, extension, gh-pages, git, workflow'
+
+
+
Here I have the string title containing the title for the current blog post and a list called tags_list containing the corresponding tags. Later I call the .join method because I will need to pass a string with the tags sepatarated by commas to the nikola new_post command.
+
But, wait a minute... I have Python variables containing the title and the tags for my blog post. How can pass this variables to the shell to use them as arguments of the nikola new_post command???
+
OK, to solve this problem we will use an exciting feature from IPython, just see the following line:
which will create the desired ipynb and the corresponding .meta file containing the title and tags.
+
+
Creating New Post
+-----------------
+
+Title: Bidirectional IPython-Nikola workflow to write your blog post
+Scanning posts......done!
+Your post's metadata is at: posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.meta
+[2013-10-15T19:21:28Z] NOTICE: new_post: Your post's text is at: posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.ipynb
+
+
+
Que me contusi! (or... do you see the bidirectional nature of this interaction? Nice, don't you think?)
+
Yes, inside IPython, we can use the braces to pass Python variables to the shell... ;-)
+
Do you see the possibilities we have with this little feature?
+
Now, I cd into the post folder of my site and open the IPython notebook with my custom extensions.
+
+
In [6]: cd posts/
+/media/datos/Desarrollos/damian_blog/posts
+
+In [7]: !ipython notebook --profile=myext
+
+
+
In the IPython Dashboard, I will open the new ipynb called bidirectional-ipython-nikola-workflow-to-write-your-blog-post.ipynb and write the content (I am writing right now).
+
Then, when I am done with the blog post, I need to deploy my new content to somewhere to make available to the public...
+
And this is very easy...
+
First, Nikola have a nikola deploy command which you can customize with your conf.py file. You can see it here my configuration:
+
+
+
+
+
+
+
In [8]:
+
+
+
!sed -n 197,208p conf.py
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
# Commands to execute to deploy. Can be anything, for example,
+# you may use rsync:
+# "rsync -rav output/* joe@my.site:/srv/www/site"
+# And then do a backup, or ping pingomatic.
+# To do manual deployment, set it to []
+DEPLOY_COMMANDS = ["git add .",
+ "git commit -am 'Update'",
+ "git push origin master",
+ "git subtree split --prefix output -b gh-pages",
+ "git push -f origin gh-pages:gh-pages",
+ "git branch -D gh-pages"]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The instructions are very easy to understand, if you need more details just read this post I wrote some weeks ago.
+
I am essentially pushing the content to master, creating a split and deploy it later to gh-pages.
+
OK, but because I am lazy ;-), some weeks ago I wrote an IPythonjavascript extension which let me execute this nikola deploy command from a button in the IPython notebook toolbar. Essentially something like this (don't worry, I will release the extension soon):
As you can see, I call nikola clean to clean my site, the I built it with nikola build, and deploy it with my customized nikola deploy... and all these actions with just a click!
+
And now you have the complete workflow! A very simple one, because you can make a lot of modifications to improve it. However, this workflow show you how you can integrate two exciting projects, communicate one with the other and viceversa, and get beautiful results.
+
Hope you enjoy it!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.es.html.dep b/cache/posts/bidirectional-ipython-nikola-workflow-to-write-your-blog-post.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/binder-+-nikola-+-jupyter-+-github-blogging-resourceless.es.html b/cache/posts/binder-+-nikola-+-jupyter-+-github-blogging-resourceless.es.html
new file mode 100644
index 00000000..ff71796e
--- /dev/null
+++ b/cache/posts/binder-+-nikola-+-jupyter-+-github-blogging-resourceless.es.html
@@ -0,0 +1,1674 @@
+
+
+
+
+
+
You are in vacation time but you want to blog something nice to share with your friends.
+
And your blog is powered by Nikola.
+
And you are a Jupyter Notebook user.
+
But you don't have your laptop with you, because you are on vacation time, remember? ;-)
+
But you still have your phone and some connectivity.
+
What do you think if I say that you have a complete workflow to write your blogpost, build the site and deploy it just using your phone? But without using computational resources from it (that would be also interesting, btw).
+
Don't you believe me? Just read this post and I will show you how you can make this possible... and fun!
+
+
NOTE: This post is long but I promise will be interesting! Also, there are multiple cells generating a lot of output, remember that you can hide the output clicking on "Click me to hide the output" button at the bottom/right conner of each cell.
We launch a binder instance from a Github repo containing my Nikola-powered blog site and write some content into a new blog post (using the Jupyter Notebook), then I rebuild the site using Nikola (already installed in my binder instance) and finally push the updated site to Github's gh-pages to finally publish the new content (from my binder instance as well).
Do you know Binder, right? In simple words it Turn a GitHub repo into a collection of interactive notebooks. You can find more info about Binder at https://mybinder.readthedocs.io/en/latest/.
+For the purpose of this post (and the next ones), I just created a new binder filling my blog site Github repo url into the URL field at mybinder.org (and the path to a specific notebook file) and I got a new url to access my binder instance at https://mybinder.org/v2/gh/damianavila/damian_blog/master?filepath=Start.ipynb
+
In fact, I am writing this blog post in a binder instance (I love to do meta stuff ;-)
+
+
That url pointed me to a Start.ipynb notebook file where I have some cells to create a new post with some Nikola tags. I run those cells and I have a new ipynb file under the posts directory, in this case: binder-+-nikola-+-jupyter-+-github-blogging-resourceless.ipynb where I can write my new content.
OK, this is one is easy, it is this very same post ;-) as you probably expected.
+
BTW, one interesting note, since your binder is using git for internal stuff, you have git installed and ready to do your stuff as well. For instance, if my connection is flaky and given that my binder in transient. I can commit the work done so far. Just save the notebook file and run:
+
+
+
+
+
+
+
In [1]:
+
+
+
!git status
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
On branch master
+Your branch is up-to-date with 'origin/master'.
+Changes not staged for commit:
+ (use "git add <file>..." to update what will be committed)
+ (use "git checkout -- <file>..." to discard changes in working directory)
+
+ modified: ../.ipynb_checkpoints/Start-checkpoint.ipynb
+ modified: ../Start.ipynb
+ modified: ../__pycache__/conf.cpython-35.pyc
+ modified: ../plugins/upgrade_metadata/__pycache__/upgrade_metadata.cpython-35.pyc
+
+Untracked files:
+ (use "git add <file>..." to include in what will be committed)
+
+ ../.bash_logout
+ ../.bashrc
+ ../.ipython/
+ ../.local/
+ ../.profile
+ .ipynb_checkpoints/binder-+-nikola-+-jupyter-+-github-blogging-resourceless-checkpoint.ipynb
+ binder-+-nikola-+-jupyter-+-github-blogging-resourceless.ipynb
+
+no changes added to commit (use "git add" and/or "git commit -a")
+
[master 7c7f9890] Add (incomplete) new post
+ 1 file changed, 146 insertions(+)
+ create mode 100644 posts/binder-+-nikola-+-jupyter-+-github-blogging-resourceless.ipynb
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
OK, now you need to push this content and if you try to git push it, it will fail unless you have permissions to push to your own repo. To achieve that from a binder instance you need to create a personal access token from Github: https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/. And now you will be able to push your stuff.
+
Note this personal access token will be useful for further pushes down the road, so keep it close.
+
Also, we need a terminal to be able to provide the username and the token. And the Jupyter interface give us that terminal pretty easily, you just go to the /tree (dashboard) and start a terminal from the dropdown menu (I can probably write a little extension to perform this step from the notebook itself... but going to the terminal is pretty easy and quick).
+
+
Now your repository is updated, so next time you launch a binder from it, it will contain your new post, meaning you can write your stuff iteratevely even in a transient platform, sweet!
When your post is ready, you need to rebuild the site using Nikola, but how Nikola end up in my binder instance?
+Easy as well, you just need to provide a requirements.txt file with the dependencies you need and those ones will be included in your binder instance: https://mybinder.readthedocs.io/en/latest/using.html#simple-python-dependencies
This could be an issue because Nikola offers a nikola serve command to preview your site, but using it inside Binder is probably not trivial. And you can do a little trick to be able to explore the new content. You just need to deploy the output folder contaning the updated site under the same gh-pages branch from where you usually serve your site.
+
And you can do that quite easily with:
+
Note: git stash is only needed here because I am executing git commands from this very same future blog post
+
+
+
+
+
+
+
In [11]:
+
+
+
!git stash
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Saved working directory and index state WIP on master: 658c5e23 Build the site in my binder instance
+HEAD is now at 658c5e23 Build the site in my binder instance
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In [12]:
+
+
+
!git checkout gh-pages
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Switched to branch 'gh-pages'
+Your branch is up-to-date with 'origin/gh-pages'.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In [14]:
+
+
+
!git checkout master -- ../output
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
In [15]:
+
+
+
!git commit -m "Add output dir to gh-pages to pre-visualize the changes"
+
And now, you just push the content into the gh-pages branch with git push origin gh-pages (use the terminal as I indicarted before) and you can visit your draft site appeding output to the base url, in my case: http://www.damian.oquanta.info/output/.
+
If you are not happy with it, if it does not looks like right, just iterate with more changes! Otherwise you can go to the deploy step!
Switched to branch 'master'
+Your branch is up-to-date with 'origin/master'.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In [19]:
+
+
+
!git add -u
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
In [20]:
+
+
+
!git commit -m "Add new stuff to the blog post (mostly deploy section)"
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
[master 7927ad63] Add new stuff to the blog post (mostly deploy section)
+ 1 file changed, 291 insertions(+), 25 deletions(-)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In the terminal: git push origin master to persist the latest content... again. And use a subtree approach to split the output directory and put it as a new gh-pages branch.
+
Note: First delete the existing gh-pages branch to avoid conflicts and cd .. because you need to subtree from the top directory.
+
+
+
+
+
+
+
In [21]:
+
+
+
!git branch -d gh-pages
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
warning: deleting branch 'gh-pages' that has been merged to
+ 'refs/remotes/origin/gh-pages', but not yet merged to HEAD.
+Deleted branch gh-pages (was 4fb3a46f).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In [22]:
+
+
+
cd..
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
/home/jovyan
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In [23]:
+
+
+
!git subtree split --prefix output -b gh-pages
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Created branch 'gh-pages'
+7092c69ccde3f7cd2a5d31c2a86b74739d665ac0
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Finally, in the terminal: git push -f origin gh-pages:gh-pages to deploy your site and remove the local gh-pages with git branch -D gh-pages.
+
And you are done!!!
+
Note: As you probably realized, you can run all the commands I described from the terminal and use the notebook just to write the blog posts. That would be, probably, the most common pattern. But this post in nicer and more explanatory if I run most of the commands here ;-)
Install Nikola and IPython (probably you have IPython installed if you are reading this post).
+
Install the site-ipython theme in your Nikola instalation. You can see some the documentation about how to do it here.
+
+
NOTE: Another way to do it is copying the site-ipython theme inside the nikola/data/themes folder BEFORE installing Nikola.
+
NOTE2: The recommended way to do it would be copying the site-ipython theme inside your_site after initialization of your_site. See below.
+
+
Initialize your_site:
+
+
nikola init your_site
+
you can ask for
+
nikola --help
+
for other available options.
+
+
Create a plugins folder inside your_site
+
Copy the compile_ipynb plugin (compile_ipynb.plugin file and the compile_ipynb folder, which are is located inside the extra-plugins folder in the Nikola master) in your_site/plugins/ folder.
+
Then, download the custom nbconvert and nbformat from here and put them inside your_site/plugins/compile_ipynb/ folder.
in your conf.py file of your_site (you can modified the other pieces inside conf.py according to your needs).
+
+
+
+
+
+
+
+
+
NOTE: This setup is done only once time a life... hehe¶
+
+
+
+
+
+
+
+
USE:
+
+
+
+
+
+
+
+
+
+
First create a new post:
+
+
nikola new_post -f ipynb
+
+
+
+
+
+
+
+
+
NOTE: IGNORE the -2 option in nikola new_page (it is no sense with the current implementation).
+
+
+
+
+
+
+
+
+
You will be asked for a title (you can also add the title and tags in the previous call).
+
+
+
+
+
+
+
+
+
Then, two files will be created by Nikola in the /posts folder of your_site: a meta file containing title, slug, time, tags (you can modified them with any text processor) and a naive ipynb file with the corresponding title.
+
+
+
+
+
+
+
+
+
You can init the ipython notebook inside this folder and modified the "post" notebook as you wish (do not forget to save the changes inside your notebook).
+
+
+
+
+
+
+
+
+
+
Finally, just:
+
+
nikola build
+
+
+
+
+
+
+
+
+
and deploy the output folder containing your_site... to see it locally:
+Welcome to pylab, a matplotlib-based Python environment [backend: module://IPython.zmq.pylab.backend_inline].
+For more information, type 'help(pylab)'.
+
+---------------------------------------------------------------------------
+ZeroDivisionError Traceback (most recent call last)
+<ipython-input-4-dc39888fd1d2> in <module>()
+ 1 x =1
+ 2 y =4
+----> 3z = y/(1-x)
+
+ZeroDivisionError: integer division or modulo by zero
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Courtesy of MathJax, you can include mathematical expressions both inline:
+$e^{i\pi} + 1 = 0$ and displayed:
fromIPython.displayimportYouTubeVideo
+# a talk about IPython at Sage Days at U. Washington, Seattle.
+# Video credit: William Stein.
+YouTubeVideo('1j_HxD4iLn8')
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Out[6]:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
OK, enough... see you soon!
+
+
+
+
+
+
diff --git a/cache/posts/blogging-with-nikola-and-ipython.es.html.dep b/cache/posts/blogging-with-nikola-and-ipython.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/change-the-ipython-slides-defaults-with-an-ipython-config-file.es.html b/cache/posts/change-the-ipython-slides-defaults-with-an-ipython-config-file.es.html
new file mode 100644
index 00000000..f6e3b263
--- /dev/null
+++ b/cache/posts/change-the-ipython-slides-defaults-with-an-ipython-config-file.es.html
@@ -0,0 +1,199 @@
+
+
+
+
+
+
Some people are asking me how to change the IPython slides's defaults. You can see the description of the request here. Essentially, he wants to change the default transition between the slides.
+
To solve this question, we introduce the notion of IPython config files, which let us easily change things inside IPython.nbconvert (the library where the IPython slides lives) to achieve our desires, at least in the slideshow generation issue ;-)
+
First of all, you need to know some details:
+
+
+
The IPython slides are generated using a series of Jinja templates, so we are going to modify one of the templates to render the slideshow accordingly with our own defaults.
+
The IPython.nbconvert library was developed taking into account the need from some users to use customized things (where thing will be a template in this case, but we could modify other parts of IPython.nbconvert, probably I will cover this ideas in other posts).
+
The IPython machinery is very configurable through a Traitlets system! And because of this feature, IPython.nbconvert is able to take a custom config file and use it to render our IPython slides (or any other IPython.nbconvertformats).
+
+
OK, can you show me an example config file? Of course, here we go:
+
+
+
+
+
+
+
In [1]:
+
+
+
!cat /media/datos/Ejemplos/slides_config.py
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
c = get_config()
+
+c.Exporter.template_file = 'default_transition'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
From the IPython docs:
+
A configuration file is simply a pure Python file that sets the attributes of a global, pre-created configuration object. This configuration object is a Config instance. While in a configuration file, to get a reference to this object, simply call the get_config() function. We inject this function into the global name-space that the configuration file is executed in,
+
+
So, we have to call the get_config() function and then use a custom template called 'default_transition' and assign it to c.Exporter.template_file attribute.
+
Oh, we need to write the 'default_transition' template yet, so here we go... again:
{%- extends 'slides_reveal.tpl' -%}
+
+
+{% block body %}
+
+{{ super() }}
+
+<script>
+
+Reveal.initialize({
+
+ // Display controls in the bottom right corner
+ //controls: true,
+
+ // Display a presentation progress bar
+ //progress: true,
+
+ // Push each slide change to the browser history
+ //history: false,
+
+ // Enable keyboard shortcuts for navigation
+ //keyboard: true,
+
+ // Enable touch events for navigation
+ //touch: true,
+
+ // Enable the slide overview mode
+ //overview: true,
+
+ // Vertical centering of slides
+ //center: true,
+
+ // Loop the presentation
+ //loop: false,
+
+ // Change the presentation direction to be RTL
+ //rtl: false,
+
+ // Number of milliseconds between automatically proceeding to the
+ // next slide, disabled when set to 0, this value can be overwritten
+ // by using a data-autoslide attribute on your slides
+ //autoSlide: 0,
+
+ // Enable slide navigation via mouse wheel
+ //mouseWheel: false,
+
+ // Transition style
+ transition: 'concave', // default/cube/page/concave/zoom/linear/fade/none
+
+ // Transition speed
+ //transitionSpeed: 'default', // default/fast/slow
+
+ // Transition style for full page backgrounds
+ //backgroundTransition: 'default', // default/linear/none
+
+ // Theme
+ theme: 'sky' // available themes are in /css/theme
+
+});
+
+</script>
+
+{% endblock body %}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In the first line, {%- extends 'slides_reveal.tpl' -%} tells to the Jinja system that we are going to extend slides_reveal template (the default one, which IPython.nbconvert uses to build our common slides by default). Then, inside the {% block body %}, we call super():
+
From the Jinja docs:
+
Super Blocks
+It’s possible to render the contents of the parent block by calling super.
+
+
We did it in this way because we want to render all the parent content and, after that, add our own content, essentially a config script for Reveal.js, calling Reveal.initialize.
+
OK, I have written a lot of configurable options you can play with, but I only left uncommented (and hence, they will be applied) the transition: 'concave' and theme: 'sky' options with my new choices, you can use your own ones.
+
Finally, you have to use the IPython.nbconvert library from command line, as usual, but pointing to the IPython config file you pretend to apply:
NOTE: Don't forget to put your ipynb, slides_config.py and default_transition.tpl files in the same folder where you will run the IPython.nbconvert command.
+
As you can see, the potentiality of this system (Jinja templating plus a powerful config system) is really big! We can achieve awesome things in a very easy way!
+
Any help, just let me know!
+
Addemdum: the use of default_transition.tpl generates an invalid but useful final html document. The cause behind this issue is the script containing the Reveal.initialize function, which is located after the closing body tag. All modern browser render this sort of invalid html witout any difficult. But a commenter arose this issue and I think is important to make it available in the post itself.
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/change-the-ipython-slides-defaults-with-an-ipython-config-file.es.html.dep b/cache/posts/change-the-ipython-slides-defaults-with-an-ipython-config-file.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/coming-back.es.html b/cache/posts/coming-back.es.html
new file mode 100644
index 00000000..747930db
--- /dev/null
+++ b/cache/posts/coming-back.es.html
@@ -0,0 +1,28 @@
+
+
+
+
+
+
OK... two years since my last post... exactly. Time goes fast, really fast! And a lot of things happened in the last two years.
+
+
+
I am planning to write about those past things... about the experience I acquired during this time. But I am also interested into discuss new and exciting things, not only in the technical side, but also in other aspects of my interests and feelings.
+
I am hoping to write at least one post per week. Time constraints are really against this frequency but I will try it!
+
Let's do a quick update:
+
+
My son, Facundo, is 3 years old now... and he's my Sun.
+
I live at Cordoba now... with my fiance, and my Moon, Daniela.
+
I have a lovely kitty called Bituinas (between us ;-)
+
I still do Software Development (for a living and for free) and I enjoy it a lot.
+
I am still involved with the Jupyter project. I am a Jupyter core developer and a Jupyter Steering Council member. RISE, the live Jupyter slideshow machinery, is widely used but I need to give it more love (and time).
+
Now, I am a gluten-free guy and because of that, I have lost weight and improved my arterial tension measurements ;-)
+
Recently, I restarted to practice Aikido.
+
+
And a lot of other things I should mention but I don't want to make this too long.
+
So... welcome back... again!
+
+
+
+
+
+
diff --git a/cache/posts/coming-back.es.html.dep b/cache/posts/coming-back.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/customizing-your-ipython-slides.es.html b/cache/posts/customizing-your-ipython-slides.es.html
new file mode 100644
index 00000000..13a2e3b5
--- /dev/null
+++ b/cache/posts/customizing-your-ipython-slides.es.html
@@ -0,0 +1,179 @@
+
+
+
+
+
+
Some days ago, I received this message on G+:
+
In a future release, would be handy to add custom classes to slides so that you can use CSS rules to choose certain layouts for image slides, text, multiple charts, etc.
+
+
But... we already support this kind of customization! And it is clearly my fault that you don't know about this feature... so:
+
+
+
I am very sorry for the lack of proper documentation (I am working on that ;-)).
+
In the meantime, you can look at this blog where I am documenting some important things for this slideshow platform.
+
You can also ask me whatever you want by twitter, G+, open issues at Github or make comments here, in my blog.
+
+
Using this message as a trigger (and following with the serie of blog posts explaining some of the IPython slides features), I will explain you how to customize your IPython slides in just two steps:
+
NOTE: I will use, as a starting point, the following slides of a talk I gave to journalist and designers at Hacks/HackersBA, a story to write in another blog post...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Step 1. Create a custom.css file containing your css rules.
/*Some css fixes to use night theme with IPython slides*/
+body {
+background-color: #111111;
+}
+.reveal p {
+color: white;
+}
+.reveal ul, ol {
+color: white;
+}
+div.output_area pre {
+color: white;
+}
+div.output_stderr {
+background: #F00;
+}
+.reveal table th, .reveal table td {
+color: white;
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Step 2. Put this custom.css file in the same dir where your slides lives.
+
+
+
+
+
+
+
In [3]:
+
+
+
!ls /media/datos/Desarrollos/hackperiodismo
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
custom.css figs index2.html index.html
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
NOTE: Here, I previously renamed my notebook.slides.html to index.html but it is not necessary for the customization.
+
And you are done!
+
The slideshow will read the custom.css file at last and overwrite the css rules according to your desires.
+
Pretty easy! ;-)
+
And now, the example slides rendered with a new darker style...
+
NOTE: In this case I applied the NIGHT reveal theme (adding ?theme=night to the url) and used the custom.css file to adjust some details ;-) (darker reveal themes need this kind of customization to be rendered OK).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
You can change more fundamental things and make crazy stuff... just go ahead and let me know.
+
Enjoy!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/customizing-your-ipython-slides.es.html.dep b/cache/posts/customizing-your-ipython-slides.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/deploy-your-nikola-powered-blog-content-from-the-ipython-notebook.es.html b/cache/posts/deploy-your-nikola-powered-blog-content-from-the-ipython-notebook.es.html
new file mode 100644
index 00000000..d0d124fb
--- /dev/null
+++ b/cache/posts/deploy-your-nikola-powered-blog-content-from-the-ipython-notebook.es.html
@@ -0,0 +1,139 @@
+
+
+
+
+
+
Following the idea to release all the extensions I had working on in the last few weeks/months, today I will release an old but very useful IPython notebook extension for people blogging with Nikola: the nikola_deploy extension.
+
+
Yes, I am always very original picking the names of the extensions ;-). A pic to illustrate the extension button at the toolbar:
+
+
Note: Nikola supports the ipynb file as an input... and using the IPython.nbconvert machinery it is able to render the static HTML representation of your ipynbs inside the complete infrastructure of a powerful static site engine.
+
+
First, to know some things about my blogging workflow using IPython, Nikola, git and gh-pages, I suggest you to re-read these previous posts:
OK, coming back to the extension, the idea behind this one is very simple: I will call the nikola deploy command from inside the IPython notebook using our beloved IPython.notebook.kernel.execute method, and also taking the advantage of passing commands to the underlying system just pre-pending with the ! mark. The relevant lines are below:
After writing the content of my post following the workflow explained in previous posts, I just click on the nikola_deploy extension button and the site is cleaned (if you choose this option to True in the config file, please set it to False if you want a quick building), built and deployedautomagically ;-)
1 /*
+ 2 * ----------------------------------------------------------------------------
+ 3 * Copyright (c) 2013 - Damián Avila
+ 4 *
+ 5 * Distributed under the terms of the Modified BSD License.
+ 6 *
+ 7 * A little extension to deploy a nikola site/blog from the IPython notebook.
+ 8 * -----------------------------------------------------------------------------
+ 9 */
+ 10
+ 11 function messager() {
+ 12 var message = $('<div/>').append(
+ 13 $("<p/></p>").addClass('dialog').html(
+ 14 "Your ipynb-based site/blog post is being deployed now..."
+ 15 )
+ 16 ).append(
+ 17 $("<p/></p>").addClass('dialog').html(
+ 18 "We clean (configurable), build and deploy your Nikola " +
+ 19 "site/blog for you!"
+ 20 )
+ 21 );
+ 22
+ 23 IPython.dialog.modal({
+ 24 title : "Nikola deployment",
+ 25 body : message,
+ 26 buttons : {
+ 27 OK : {class: "btn-danger"}
+ 28 }
+ 29 });
+ 30
+ 31 }
+ 32
+ 33 function nikolaDeploy(path, clean) {
+ 34 IPython.notebook.kernel.execute('%bookmark root');
+ 35 IPython.notebook.kernel.execute('%cd ' + path);
+ 36 if (clean=="True") {
+ 37 IPython.notebook.kernel.execute('!nikola clean');
+ 38 }
+ 39 IPython.notebook.kernel.execute('!nikola build');
+ 40 IPython.notebook.kernel.execute('!nikola deploy');
+ 41 IPython.notebook.kernel.execute('%cd -b root');
+ 42 messager();
+ 43 }
+ 44
+ 45 define(function() {
+ 46 return {
+ 47 parameters: function setup(param1, param2) {
+ 48 IPython.toolbar.add_buttons_group([
+ 49 {
+ 50 'label' : 'Deploy Nikola site/blog',
+ 51 'icon' : 'icon-upload-alt',
+ 52 'callback': function(){nikolaDeploy(param1, param2)},
+ 53 'id' : 'start_nikola_deploy'
+ 54 },
+ 55 ])
+ 56 }
+ 57 }
+ 58 });
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Again, the extension lives in this new repo: mIPyex, where I will upload the development versions of my own extensions. When I get them enough stable, I will make a copy of them in the IPython notebook extensions repo where you can get a lot of and useful interesting extensions.
+
OK, as you can see... it is very simple to blog with IPython and Nikola, so I invite you to try it now and let me know any ideas, comments or critics.
+
Enjoy!
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/deploy-your-nikola-powered-blog-content-from-the-ipython-notebook.es.html.dep b/cache/posts/deploy-your-nikola-powered-blog-content-from-the-ipython-notebook.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/different-ways-to-lead-an-open-source-project.es.html b/cache/posts/different-ways-to-lead-an-open-source-project.es.html
new file mode 100644
index 00000000..c338212b
--- /dev/null
+++ b/cache/posts/different-ways-to-lead-an-open-source-project.es.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+
Just a few lines, to trigger the discussion... to describe my point, I will pick two projects I have contributed (and I want to contribute even more): IPython and Nikola.
+
Some months ago, Brian Granger, a core developer from the IPython project gave a talk at SciPy 2013 where he said:
+
+
Make features fight hard to be accepted and implemented. Communicate to the community and developers that the default answer to new feature requests is no (it's not personal!). Don't even consider implementation until the much of the community is crying "we absolutely must have this."
+
+
Some days ago, Roberto Alsina, a core developer from the Nikola project made a blog post where he said:
+
If you propose something you are getting heard and I am giving the proposal a fair shake. I may reject it, but not out of hand, but instead after some thought. And if I am unsure, it’s accepted. I would rather get something I am not fond of than drive out a contributor because I may change my mind, but a contributor that’s gone is not coming back.
+
+
Both projects are very successful, however they seems to go in opposite directions in the way they deal with features and contributors.
+
Probably they are living in different "times"... I mean, I see a "pattern" here:
+
Nikola, the younger, is toward the "left" side, embracing the "radical" view of the “universe”, whereas IPython, the older, is toward the "right" side, embracing the "conservative" view...
+
Let me be clear, I am not saying anything about the political ideas of those developers, I do not even know their political ideas... I just described a pattern I saw before with people, but it seems to be also relevant for open source projects.
+
I will probably write more about that, but I would like to know you ideas ;-)
+
Like I said at the beginning, just a few lines, to trigger the discussion...
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/different-ways-to-lead-an-open-source-project.es.html.dep b/cache/posts/different-ways-to-lead-an-open-source-project.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/dont-write-scripts-just-write-ipyscripts.es.html b/cache/posts/dont-write-scripts-just-write-ipyscripts.es.html
new file mode 100644
index 00000000..c37b2d97
--- /dev/null
+++ b/cache/posts/dont-write-scripts-just-write-ipyscripts.es.html
@@ -0,0 +1,237 @@
+
+
+
+
+
+
I usually have some repetitive tasks in my daily work-flow. You probably have some of those too. To save some minutes from your day, you probably write little scripts to do these jobs.
+
I used to do that... but now I am only writing little IPython notebooks to do these simple jobs, I call them ipyscripts (yes, I won a prize for originality, he he!).
+
These ipyscripts are IPython-powered, so we can use all the IPython's machinery to do complex things in a simple way...
+
+
In fact, you are reading a example ipyscript, because this is an IPython notebook (and a blog post too), and the following example deal with a repetitive task I do frequently: the git update of some projects (I contribute to some of them, I follow some others).
+
First, I load a simple list with the projects I want to update:
You can see here how I am using a lot of tricks from the IPython machinery to make a lot of things in a couple of lines.
+
The main idea is cd into a specific project folder. I use the braces to pass python variables and expressions to the shell. In this case, I will pass an element of the list_of_projects, I mean the name of the folder containing the desired project. Then, I do the git stuff, just prepending the command with the ! sign to pass them to the underlying shell. Finally, I cd into the main directory to get the things prepared to the next loop.
+
Fourth, I do a simple for loop to iterate through the elements inside the list_of_projects and to do the git update in each of these projects.
But, this is an example, and I wanted to emphasize the fact that you can pass complex arguments inside the braces... Thanks Lex for your comment, I forgot to add this explanation!
+
+
And that's all! The next time you have to do this task, just run this notebook (properly customized for your projects) and you will get the job done!
+
NOTE: And now, the icing on the cake... if you are in IPython master, you do not even need to open the notebook to run it... just open an IPython console or notebook and write the next sentence:
+
%run your_ipyscript.ipynb
+
Yes, you can use the %run magic to run all the code cells from the notebook you pass as an argument ;-) Niceeeeeeeeeee!
+
NOTE 2: There is an ongoing PR to make this %run notebook extensive to notebooks containing non-code cells.
+
OK, I hope you enjoy this post. And I also hope you begin to write ipyscripts.
+
See you!
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/dont-write-scripts-just-write-ipyscripts.es.html.dep b/cache/posts/dont-write-scripts-just-write-ipyscripts.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/facundo.es.html b/cache/posts/facundo.es.html
new file mode 100644
index 00000000..aa915104
--- /dev/null
+++ b/cache/posts/facundo.es.html
@@ -0,0 +1,69 @@
+
Facu llegó... y ¡antes de lo esperado!
+
Nació ayer, 7 de noviembre, a las 8:00 am en ciudad de La Plata.
+36 semanas de gestación (un mes antes de lo previsto), 2400 gr. y la altura, para la próxima...
+
Toda la aventura fue muy rápida. Alrededor de las 4:30 am, Lore logró despertarme (me había dormido sólo un par de horas antes).
+Se sentía dolorida. Pero en ese momento, nada nos hacía pensar que estuviese comenzando con el trabajo de parto.
+Era un dolor leve, pero molesto. Pasaron los minutos. Los dolores aumentaron en intensidad y se hicieron regulares: contracciones.
+Empezamos a sospechar. Llamamos a la partera, quien nos recomendó esperar al menos dos horas más, cuantificando las contracciones
+en intensidad (fácilmente... a través de las caras que ponía Lore) y, sobre todo, la frecuencia. Hicimos caso. En parte...
+
+
Al cabo de una hora, y con contracciones que duraban un minuto (e intervalos de relajación de dos minutos),
+llamamos nuevamente a la partera quien nos recomendó, amablemente, acercarnos a la clínica con la mayor celeridad posible.
+Por las dudas, tuve el tupé de armar el bolso de Facu (sí, deberíamos haberlo armado un tiempo antes),
+terminar de armar el bolso de Lore y preparar mi mochila.
+
A las 6:30, sólo 2 horas después de las primeras molestias, Lore estaba realmente dolorida, al punto que me costó subirla al auto.
+Llegamos a la clínica. La partera nos estaba esperando. La llave de la sala de parto viajaba en el bolsillo de alguna enfermera.
+Tuvimos que esperar unos 15 minutos. Para Lore fue una espera de dos horas.
+
Y entramos a la sala, sentamos a Lore en el sillón de parto y resulta que tenía dilatación completa. En criollo...
+"Facu, aguantá que la obstetra todavía no llegó". Pasaron cinco minutos. O diez. Finalmente, llegó.
+Tres o cuatro pujes. Facu llorando. Yo también. El momento de mi vida.
+
Facu estaba en perfectas condiciones. Lore estaba muy bien. El día avanzó entre visitas de los seres queridos.
+Entramos a la clínica el martes a 7:00 am, salimos al día siguiente (hoy) al mediodía.
+
Ya estamos en casa. Acaban de dormirse. Yo, cocinando, ordenando y escribiendo.
+
Sólo quería contarles...
+
Damián.
+
PD: algunas fotitos para que se deleiten... las primeras con el celu... las últimas con la cámara...
+
+
+
¡Qué largo y flaco que soy!
+
+
+
+
Y ahora de costadete...
+
+
+
+
Parece que tenía hambre...
+
+
+
+
Durmiendo en brazos del papi.
+
+
+
+
¡Uy! Me olvidé de avisar...
+
+
+
+
¡Otra vez sopa... digo, teta!
+
+
+
+
¡Qué lindo es dormir! Episodio I
+
+
+
+
¡Qué lindo es dormir! Episodio II
+
+
+
+
¡Qué lindo es dormir! Episodio III
+
+
+
+
¡Cómo podría ser de otra manera... jeje!
+
+
+
+
Cuna improvisada... se nota que llegó un mes antes, ¿no? jeje!
+
diff --git a/cache/posts/facundo.es.html.dep b/cache/posts/facundo.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/hello-world-again.es.html b/cache/posts/hello-world-again.es.html
new file mode 100644
index 00000000..4aee3cda
--- /dev/null
+++ b/cache/posts/hello-world-again.es.html
@@ -0,0 +1,6 @@
+
Ustedes saben que, en otras épocas, he tratado de mantener "vivos" un par de blogs.
+Este es un nuevo ensayo...
+Esta vez, no les prometo postear todos los días... pero si tienen paciencia,
+podrán leer algunas "cosas" interesantes (al menos interesantes para mi).
+
Nos vemos pronto!
+
Damián.
diff --git a/cache/posts/hello-world-again.es.html.dep b/cache/posts/hello-world-again.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/hide-the-input-cells-from-your-ipython-slides.es.html b/cache/posts/hide-the-input-cells-from-your-ipython-slides.es.html
new file mode 100644
index 00000000..b779e98a
--- /dev/null
+++ b/cache/posts/hide-the-input-cells-from-your-ipython-slides.es.html
@@ -0,0 +1,120 @@
+
+
+
+
+
+
A tweet arrived...
+
@damian_avila Is there a way to only show the output of a cell in an NB slideshow?
How we can easily do it? Just follow these few steps:
+
+
Rational: We are going to use the power of IPython.nbconvert library to use a modified jinja template which will let us hide theinput cells in our IPython slides. To achieve this goal, we are going to use the same approach described in a previous post. Hence, our input cells will be hidden by default, but they will show up if we click on the corresponding output cell area.
+
OK, I first wrote a custom template and named it as output_toggle.tpl:
The code is simple, but for a detailed explanation see my previous post.
+
Briefly, I just changed obvious things such as the encompassing of the input_group and the calling of .prev() method (instead of .next() one) inside the little javascript snippet.
and I got something like this (navigate and try it!):
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
OK, as you have seen in the example, your IPython slides will be delivered showing just the output cells... but if you need to show some input cells, just click on the corresponding output cell and you will get them. Nice, uh!
+
Hope it helps Thomas (and all the other people using the IPython slides)!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/hide-the-input-cells-from-your-ipython-slides.es.html.dep b/cache/posts/hide-the-input-cells-from-your-ipython-slides.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/how-to-pin-conda.es.html b/cache/posts/how-to-pin-conda.es.html
new file mode 100644
index 00000000..a39820da
--- /dev/null
+++ b/cache/posts/how-to-pin-conda.es.html
@@ -0,0 +1,29 @@
+
+
+
+
+
+
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 that specific version of some package and not the next one because it breaks your work completely or for some other reason, you are probably pinning that package. If you are adding the specific version in every command you run instead of pinning the package, you are doing it wrong and you should keep reading ;-)
+
But, is it possible to pin Conda itself so it does not get updated every time you try to install/update something else?
+
+
If you don't know what Conda is, you should probably go here and learn a little bit about it. For the lazy ones:
+
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.
+
+
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?
+
I have heard a lot of people saying it is impossible to pin Conda, BUT that's not the case ;-)
+
You can pin Conda the same way you pin any other package.
+
Let me show you how you can do it... is really simple:
This will create (or pass the string into) a file called pinned containing the conda package version you wish to keep (in this case, I choose the version 4.0.0). This pinned file should be located in the conda-meta directory of your anaconda (or miniconda) installation. Then, every time you try to install or update something, this pinned file is read by Conda and the line with the conda specific version is added to the list sent to the SAT solver, hence you will always have that specification enabled, preventing you from updating to a newer Conda. Nice, don't you think?
+
You can remove that file when you are ready to catch a new Conda version or alternatively you can run conda install/update commands with the --no-pin option.
+
Hope this helps others! If not, at least, it was fun to play a little bit with this feature!
+
See you next time!
+
PS1: Thanks Will for reviewing my wording!
+
PS2: Starting Conda version 4.0.9, you have a new config option called auto_update_conda to disable the self update nature in Conda.
+
+
+
+
+
+
diff --git a/cache/posts/how-to-pin-conda.es.html.dep b/cache/posts/how-to-pin-conda.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/improving-viper-slideshows-styling.es.html b/cache/posts/improving-viper-slideshows-styling.es.html
new file mode 100644
index 00000000..f6c90305
--- /dev/null
+++ b/cache/posts/improving-viper-slideshows-styling.es.html
@@ -0,0 +1,7 @@
+
Este último fin de semana tuve un ratito para trabajar en el "styling" de las presentaciones que provee vIPer
+(a partir de los notebooks de IPython).
+
A continuación pueden ver un ejemplo:
+
+
Si presionan la tecla "h" verán, sobre la izquierda, las opciones disponibles en la presentación.
+
¡Diviértanse!
+
Damián.
diff --git a/cache/posts/improving-viper-slideshows-styling.es.html.dep b/cache/posts/improving-viper-slideshows-styling.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/ipython-plugin-for-nikola-updated.es.html b/cache/posts/ipython-plugin-for-nikola-updated.es.html
new file mode 100644
index 00000000..042023b6
--- /dev/null
+++ b/cache/posts/ipython-plugin-for-nikola-updated.es.html
@@ -0,0 +1,65 @@
+
+
+
+
+
+
I am pleased to announce the new version of the IPython plugin for Nikola.
+
This new version has been incorporated into Nikola master a few weeks ago, so it is now available in the last release of Nikola, 5.5.1.
+
Now that IPython has achieved the 1.0 release, and with the incorporation of nbconvert as a part of the IPython machinery, the IPython plugin no longer needs to use a customized version of the old nbconvert, instead it is now using the the power of the new IPython.nbconvert infrastructure to export the ipynb files to HTML pieces to be rendered by Nikola.
+
With the simplification of the infrastructure, it is now easier to setup your blog to use the plugin following this five steps:
+
+
Note: I will explain from the ground, you probably can skip some steps if you are an IPython and Nikola user...
+
+
Install (you can do it using pip install inside a virtualenv):
+
+
IPython 1.0 (also pyzmq, tornado and jinja2, as notebook dependencies)
+
Nikola 5.5.1
+
Requests
+
Sphinx
+
+
+
Init your site:
+
+
nikola init your_blog
+
cd in your_blog
+
+
+
Download the IPython theme:
+
+
nikola install_theme -l to list all the available themes in Nikola
+
nikola install_theme jinja-site-ipython or any theme with the ipython word in their names ie, you have a xkcd-site-ipython theme if you want a xkcd sytling for your blog ;-).
+
+
+
+
Note: Beware of the available sub_themes because probably you will need some css adjustments to use it. You can also write your custom theme if you want ;-).
Note: You have to do all this four steps just once, then you will only do step 5 for writing your post.
+
+
Finally:
+
To write a new post, just: nikola new_post -f ipynb (you can avoid -f ipynb if you have only ipynb references in your post_pages).
+
Then, nikola build to build the site and nikola serve to see it.
+
+
+
+
Easier, don't you think?
+
Ok, if you need any help or find any bug, just let us known open an issue on github or blame on me here ;-)
+
Cheers.
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/ipython-plugin-for-nikola-updated.es.html.dep b/cache/posts/ipython-plugin-for-nikola-updated.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/live-trading-logbook.es.html b/cache/posts/live-trading-logbook.es.html
new file mode 100644
index 00000000..0a972a8b
--- /dev/null
+++ b/cache/posts/live-trading-logbook.es.html
@@ -0,0 +1,69 @@
+
+
+
+
+
+
After some weeks of silence, he he... I come back with a short post about live trading in the forex market.
+As you probably know [if not, you are knowing it right now ;-)], one of my interests is the analysis, modeling and forecasting of financial time series. To make it short, I have developed some statistical models to forecast the dynamic of selected portfolios.
+Currently, I am trading equities and other more complex financial derivatives. But my models are also suitable to apply to other markets, ie. the foreign exchange market (yes... forex). So, I made a quick research on some interesting forex pairs and then I started a little account to perform some live trades accordingly to these models.
+And now, I pretend to log the trades from this little account in a subset of post on my blog, a sort of public live trading logbook.
+
OK, we can start the logging right now! I opened two short positions some days ago:
+
+
+
+
Ticket
+
Date
+
Transaction
+
Currency Pair
+
Price
+
+
+
1350434307
+
2013-11-05 22:08:02
+
Sell Market
+
GBP/AUD
+
1.68983
+
+
+
1350434298
+
2013-11-05 22:07:59
+
Sell Market
+
AUD/USD
+
0.94939
+
+
And is time to close them... so closing them whereas I am writing this post (just wait me a minute, I will be back!).
+
OK, I closed both positions:
+
+
+
Ticket
+
Date
+
Transaction
+
Currency Pair
+
Price
+
+
+
1355893384
+
2013-11-13 01:25:10
+
Close Trade
+
GBP/AUD
+
1.70790
+
+
+
1355893378
+
2013-11-13 01:25:09
+
Close Trade
+
AUD/USD
+
0.93063
+
+
And I added some pics to illustrate these trades:
+
+
+
With these trades, we had a net increment of 4.5% in the balance!
+
Nice beginning! Let's see how far we can go...
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/live-trading-logbook.es.html.dep b/cache/posts/live-trading-logbook.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/loader-and-writer-ipython-nbextensions-to-easily-edit-your-text.es.html b/cache/posts/loader-and-writer-ipython-nbextensions-to-easily-edit-your-text.es.html
new file mode 100644
index 00000000..b06fbafd
--- /dev/null
+++ b/cache/posts/loader-and-writer-ipython-nbextensions-to-easily-edit-your-text.es.html
@@ -0,0 +1,128 @@
+
+
+
+
+
+
Coming back to the nice practice of release my own IPythonnbextensions, today I will release two extensions I use a lot in my daily workflow: loader and writer, useful extensions to load files into the IPython notebook and to write the content to the same (or another) file.
+
+
Note: These extensions were developed some months ago, and probably you can write better versions of them using the new IPython widget infrastructure, but these were nice hacks and they are still useful in th IPython 1.x and 2.x series, so I think they deserve to go public.
+
I used the IPython notebook a lot, you know that if you are frequently reading my blog. Not only to write blog posts, but also to write other kind of stuff, for instance: code. Some time ago, I used to write code in a plain text editor next to an IPython console, sometimes I used NINJA-IDE because it is a nice and featured platform. But right now, I am developing inside the IPython notebook because it gives me the text editor and the console in one place, with a lot of other useful features. But I will postpone the description of my workflow for some post to come in the future.
+
I just want to tell you how I easily fixed a missing feature (for now, because it will be present in the future, for sure) in the IPython notebook using nbextensions. The problem was simple, you can use the %load and %write_file magics to load and write files. But I want some minimal user inteface to:
+
+
select which file to load,
+
write a cell content to a file with just a click.
+
+
So I wrote loader and writer...
+
loadernbextension use FileReader() capability of modern browsers. The implementation is simple and you can find more complex examples on the web:
So after selecting a cell, I click on the loader button, I get this:
+
+
And if I click on Seleccionar archivo (Select file) I can navigate trough my file system to get the file I want to load. For instance, I will load some text, in this case a Bokeh plot, in the next cell:
+
+
+
+
+
+
+
In [ ]:
+
+
+
name:themes.py
+type:text/x-python
+size:1055bytes
+----
+# -*- coding: utf-8 -*-
+
+importnumpyasnp
+importscipy.special
+frombokeh.plottingimport*
+
+mu,sigma=0,0.5
+
+measured=np.random.normal(mu,sigma,1000)
+hist,edges=np.histogram(measured,density=True,bins=20)
+
+x=np.linspace(-2,2,1000)
+pdf=1/(sigma*np.sqrt(2*np.pi))*np.exp(-(x-mu)**2/(2*sigma**2))
+cdf=(1+scipy.special.erf((x-mu)/np.sqrt(2*sigma**2)))/2
+
+output_file('histogram.html')
+
+hold()
+
+figure(title="Normal Distribution (μ=0, σ=0.5)",tools="previewsave",
+ background_fill="#E5E5E5")
+quad(top=hist,bottom=np.zeros(len(hist)),left=edges[:-1],right=edges[1:],
+ fill_color="#333333",line_color="#E5E5E5",line_width=3)
+
+# Use `line` renderers to display the PDF and CDF
+line(x,pdf,line_color="#348abd",line_width=8,alpha=0.7,legend="PDF")
+line(x,cdf,line_color="#7a68a6",line_width=8,alpha=0.7,legend="CDF")
+
+xgrid().grid_line_color="white"
+xgrid().grid_line_width=3
+ygrid().grid_line_color="white"
+ygrid().grid_line_width=3
+
+legend().orientation="top_left"
+
+show()
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
Which gives me this nice plot... but I will post in detail about Bokeh soon ;-)
+
+
As you can see, the three first lines of the loaded text give you information about the file itself. Under the ---- rule, you will have the file content. Then, you can do whatever modification you want and write it to a file (the same or another one) using the writernbextension:
+
+
writernbextension is using %writefile magic under the hood:
As you can see loader and writer work in pairs! And they make the laod, edit and save of any text file really quick and successful. I want to keep this post short, so I will stop here, but you can easily see how these simple extensions can help you a lot in your daily workflow.
+
As usual, the extensions live in this repo: mIPyex, where I will upload the development versions of my own extensions. You can see the full implementation there. When I get them enough stable, I will make a copy of them in the IPython notebook extensions repo where you can get a lot of and useful interesting extensions.
+
OK, as you can see... now it is very simple to load, edit an save text with the IPython notebook. And it will be easier in the future...
+
Enjoy!
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/loader-and-writer-ipython-nbextensions-to-easily-edit-your-text.es.html.dep b/cache/posts/loader-and-writer-ipython-nbextensions-to-easily-edit-your-text.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/make-your-slides-with-ipython.es.html b/cache/posts/make-your-slides-with-ipython.es.html
new file mode 100644
index 00000000..c31e9ab8
--- /dev/null
+++ b/cache/posts/make-your-slides-with-ipython.es.html
@@ -0,0 +1,58 @@
+
+
+
+
+
+
With the integration of nbconvert inside IPython, the last 1.0 release has the possibility to export the ipynb to other formats such as rst, markdown, latex, html and slides (info).
+
The slides option generates a Reveal.js-powered HTML slideshow, like this one:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
These are my slides from the talk I gave at SciPy 2013 (Texas) featuring this exporter I previously developed in the old nbconvert project and now merged (and available) in the last release (1.0) of IPython.
+
You can also see the video of the talk:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As you can see, before I had to use an independent nbconvert library... now is easier ;-)
+
Just one line:
+
ipython nbconvert your_slides.ipynb --to slides
+
But, the resulting slideshow has to be served by an HTTP server. Because, we care of you ;-), just add --post serve at the command-line:
And your browser will open a tab containing your slides...
+
There is a lot of possibility from here... but I will write some of them later.
+
Enjoy it!
+
Damián
+
PS: Please report any bug or give me you feedback to make this tool better!
+
+
+
+
+
+
diff --git a/cache/posts/make-your-slides-with-ipython.es.html.dep b/cache/posts/make-your-slides-with-ipython.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/mimic-the-ipython-notebook-cell-execution.es.html b/cache/posts/mimic-the-ipython-notebook-cell-execution.es.html
new file mode 100644
index 00000000..4e24c1b8
--- /dev/null
+++ b/cache/posts/mimic-the-ipython-notebook-cell-execution.es.html
@@ -0,0 +1,263 @@
+
+
+
+
+
+
Yesterday, I was visiting the Jake VanderPlas's Scientific Python Course site because of some issues raised at the ipython-dev mailing list (and obviously, because Jake usually do amazing things).
+
To build his site, Jake wrote an Hyde plugin to render ipynb files to static html files using the IPython.convert platform. You can see an example of the final rendered document here.
+
When I saw the final document, I wondered if we could have hidden output cells which automatically get visible after a click over the input cell... and then, I made some experiments using the power of the IPython.nbconvert library ;-)
+
+
NOTE: From here, to see the output of each cell, please click on the input area and surprise yourself!
+
First, we needed to rewrite some things at the Jinja template level:
We had to rewrite the output_group block to encompass it with a new output_hidden-classed div, which we would use in a simple Javascript function later.
+
Second, we needed to write that little Javascript snippet:
Here, we used the .slideToggle() method to display or hide the output_hidden-classed div elements (with a nice sliding motion) when the user makes a click on the input cells. We was using jQuery, so we needed to load jQquery, ie. using the following line:
To use it, just add --template toggle to your ipython nbconvert call, ie:
+
ipython nbconvert your_notebook.ipynb --to html --template toggle --post serve
+
or add the toggle.tpl file to you IPython nbconvert config file.
+
If you are reading this line, you probably have already experienced the demo in this post (btw, I like to do demos explaining the tools with the tools themselves).
+
Obviously, I quickly implemented this functionality inside Nikola and, as a consequence, in Nikola master, you now have the possibility to pass an IPython config dict to your Nikolaconf.py file, making the ipynb plugin for Nikola more powerful than before ;-)
+
To conclude, the possibility to mimic the IPython notebook execution is very useful for introductory courses and to publish content in a shorter but more interactive way.
+
Hope you enjoy it!
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/mimic-the-ipython-notebook-cell-execution.es.html.dep b/cache/posts/mimic-the-ipython-notebook-cell-execution.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/my-aikido-shodan-test.es.html b/cache/posts/my-aikido-shodan-test.es.html
new file mode 100644
index 00000000..776f0388
--- /dev/null
+++ b/cache/posts/my-aikido-shodan-test.es.html
@@ -0,0 +1,29 @@
+
+
+
+
+
+
Querés saber como se vé un exámen de Aikido para 1er Dan? Bueno, esta es tu oportunidad! Sólo necesitás seguir leyendo un ratito más ;-)
+
+
Tuvimos un seminario de Aikido e Iaido durante dos días dictado por el Shihan Ricardo Corbal.
+Ayer, al término de dos clases muy buenas (y llenas de gente) se tomaron exámenes para kyus y danes. Y rendí para el grado de Shodan (1er cinturón negro de Aikido).
+
Este es final de un largo camino... o realidad, el comienzo!
+
Empecé a practicar Aikido en 1999 bajo la dirección de Sensei Oscar Medina. Y practiqué allí durante (más o menos) 5 años. Pero por varias razones, incluyendo la trágica muerte de mi Sensei y amigo en un accidente de tránsito, dejé la práctica. Pasaron muchas cosas en mi vida, pero luego de muchos años, en 2016 (si, 11 años después) retomé la práctica en Córdoba Aikikai (conocido previamente como Kogarashi dojo) bajo la dirección de Sensei José Delgado y Sensei Eugenio Fernández, y más recientemente, bajo la dirección de Sensei Nico Coll. Practiqué durante todo el 2016, pero 2017 me sorprendió con muchos viajes nacionales e internacionales, por lo que retomé la práctica nuevamente en 2018.
+
Por lo tanto, después de 7-8 años de práctica discontinuada, finalmente estaba listo para rendir para el grado de Shodan.
+
Quisiera agradecer a muchas personas que me ayudaron en esta fase:
+
+
Sensei Oscar Medina, quién me introdujo al Arte del Aikido y se transformó en uno de mis mejores amigos (te extraño, Oscar!)
+
Sensei José y Sensei Eugenio, quienes me abrieron las puertas de Kogarashi y me re-introdujeron a la práctica del Aikido. Estos tipos son seres maravillosos y amigos
+
Sensei Nico, quien recientemente, junto con José y Eugenio, comenzaron un nuevo camino llamado Córdoba Aikikai (Sensei, gracias por ser mi uke en el exámen!)
+
Toda la comunidad de Córdoba Aikikai, gente recorriendo sus propios caminos en el Aikido y ayudándose mutuamente en el día a día.
+
Shihan Ricardo Corbal, que nos dejó sus enseñanzas y fue quién me tomó el exámen (gracias por los consejos post-exámen, trabajaré en esos puntos para mejorarlos)
+
Daniela, mi amor, que me aguanta y me ha ayudado en todo este proceso
+
+
OK, este es el video, en caso de que quieran ver un poco de acción ;-)
+
Como he dicho anteriormente, éste es sólo el comienzo de una nueva fase en mi práctica de Aikido... y estoy seguro que la disfrutaré!
+
+
+
+
+
+
diff --git a/cache/posts/my-aikido-shodan-test.es.html.dep b/cache/posts/my-aikido-shodan-test.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/my-aikido-shodan-test.es.html.es b/cache/posts/my-aikido-shodan-test.es.html.es
new file mode 100644
index 00000000..776f0388
--- /dev/null
+++ b/cache/posts/my-aikido-shodan-test.es.html.es
@@ -0,0 +1,29 @@
+
+
+
+
+
+
Querés saber como se vé un exámen de Aikido para 1er Dan? Bueno, esta es tu oportunidad! Sólo necesitás seguir leyendo un ratito más ;-)
+
+
Tuvimos un seminario de Aikido e Iaido durante dos días dictado por el Shihan Ricardo Corbal.
+Ayer, al término de dos clases muy buenas (y llenas de gente) se tomaron exámenes para kyus y danes. Y rendí para el grado de Shodan (1er cinturón negro de Aikido).
+
Este es final de un largo camino... o realidad, el comienzo!
+
Empecé a practicar Aikido en 1999 bajo la dirección de Sensei Oscar Medina. Y practiqué allí durante (más o menos) 5 años. Pero por varias razones, incluyendo la trágica muerte de mi Sensei y amigo en un accidente de tránsito, dejé la práctica. Pasaron muchas cosas en mi vida, pero luego de muchos años, en 2016 (si, 11 años después) retomé la práctica en Córdoba Aikikai (conocido previamente como Kogarashi dojo) bajo la dirección de Sensei José Delgado y Sensei Eugenio Fernández, y más recientemente, bajo la dirección de Sensei Nico Coll. Practiqué durante todo el 2016, pero 2017 me sorprendió con muchos viajes nacionales e internacionales, por lo que retomé la práctica nuevamente en 2018.
+
Por lo tanto, después de 7-8 años de práctica discontinuada, finalmente estaba listo para rendir para el grado de Shodan.
+
Quisiera agradecer a muchas personas que me ayudaron en esta fase:
+
+
Sensei Oscar Medina, quién me introdujo al Arte del Aikido y se transformó en uno de mis mejores amigos (te extraño, Oscar!)
+
Sensei José y Sensei Eugenio, quienes me abrieron las puertas de Kogarashi y me re-introdujeron a la práctica del Aikido. Estos tipos son seres maravillosos y amigos
+
Sensei Nico, quien recientemente, junto con José y Eugenio, comenzaron un nuevo camino llamado Córdoba Aikikai (Sensei, gracias por ser mi uke en el exámen!)
+
Toda la comunidad de Córdoba Aikikai, gente recorriendo sus propios caminos en el Aikido y ayudándose mutuamente en el día a día.
+
Shihan Ricardo Corbal, que nos dejó sus enseñanzas y fue quién me tomó el exámen (gracias por los consejos post-exámen, trabajaré en esos puntos para mejorarlos)
+
Daniela, mi amor, que me aguanta y me ha ayudado en todo este proceso
+
+
OK, este es el video, en caso de que quieran ver un poco de acción ;-)
+
Como he dicho anteriormente, éste es sólo el comienzo de una nueva fase en mi práctica de Aikido... y estoy seguro que la disfrutaré!
+
+
+
+
+
+
diff --git a/cache/posts/my-aikido-shodan-test.es.html.es.dep b/cache/posts/my-aikido-shodan-test.es.html.es.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/my-aikido-shodan-test.html.es b/cache/posts/my-aikido-shodan-test.html.es
index 6b3e272c..776f0388 100644
--- a/cache/posts/my-aikido-shodan-test.html.es
+++ b/cache/posts/my-aikido-shodan-test.html.es
@@ -3,31 +3,24 @@
-
Do you want to see how an Aikido Shodan test looks like?
-Well, this is your opportunity!!
-You just need to keep reading for a little bit ;-)
+
Querés saber como se vé un exámen de Aikido para 1er Dan? Bueno, esta es tu oportunidad! Sólo necesitás seguir leyendo un ratito más ;-)
Yesterday, after two really nice and crowded classes, we had some kyu and dan tests.
-And I tested for the Shodan degree (1st black belt in Aikido).
-
This is the conclusion of a long journey... or, actually the beginning!
-
I started to practice Aikido in 1999 under Sensei Oscar Medina.
-And I practiced there for about 5 years.
-But for several reasons, included the tragic death of my Sensei and friend in a traffic accident, I discontinued my practice.
-Then, a lot of happened in my life, and after several years, in 2016 (yes, about 11 years later) I restarted to practice again in Córdoba Aikikai (previously known as Kogarashi dojo) under the teaching of Sensei José Delgado and Sensei Eugenio Fernández, and more recently also under the teaching of Sensei Nico Coll.
-I practiced the whole 2016, but 2017 surprised me with a lot of international and national travels, so I re-restarted again in 2018.
-
So, after about 7-8 years of discontinued practice, I finally was ready to test for the Shodan degree.
-
I want to thank a lot of people who helped me in this phase:
+
Tuvimos un seminario de Aikido e Iaido durante dos días dictado por el Shihan Ricardo Corbal.
+Ayer, al término de dos clases muy buenas (y llenas de gente) se tomaron exámenes para kyus y danes. Y rendí para el grado de Shodan (1er cinturón negro de Aikido).
+
Este es final de un largo camino... o realidad, el comienzo!
+
Empecé a practicar Aikido en 1999 bajo la dirección de Sensei Oscar Medina. Y practiqué allí durante (más o menos) 5 años. Pero por varias razones, incluyendo la trágica muerte de mi Sensei y amigo en un accidente de tránsito, dejé la práctica. Pasaron muchas cosas en mi vida, pero luego de muchos años, en 2016 (si, 11 años después) retomé la práctica en Córdoba Aikikai (conocido previamente como Kogarashi dojo) bajo la dirección de Sensei José Delgado y Sensei Eugenio Fernández, y más recientemente, bajo la dirección de Sensei Nico Coll. Practiqué durante todo el 2016, pero 2017 me sorprendió con muchos viajes nacionales e internacionales, por lo que retomé la práctica nuevamente en 2018.
+
Por lo tanto, después de 7-8 años de práctica discontinuada, finalmente estaba listo para rendir para el grado de Shodan.
+
Quisiera agradecer a muchas personas que me ayudaron en esta fase:
-
Sensei Oscar Medina, who introduced me to the art of Aikido and became one of my most beloved friends (I miss you!)
-
Sensei José and Sensei Eugenio, who opened me the doors of Kogarashi and re-introduce me in the Aikido practice. Those two guys are wonderful human beings and friends
-
Sensei Nico, who recently joined José and Eugenio to start a new journey called Córdoba Aikikai (Sensei, thanks for being my uke in the test!)
-
All the Córdoba Aikikai community, a lot of people who are transiting their own paths in Aikido helping each other on a daily basis
-
Shihan Ricardo Corbal, who kindly provided us with this teachings and took my test (thanks for the post-test tips, I will work hard on those points to make them better)
-
Daniela, my love, who is really supportive and helped me in all this process
+
Sensei Oscar Medina, quién me introdujo al Arte del Aikido y se transformó en uno de mis mejores amigos (te extraño, Oscar!)
+
Sensei José y Sensei Eugenio, quienes me abrieron las puertas de Kogarashi y me re-introdujeron a la práctica del Aikido. Estos tipos son seres maravillosos y amigos
+
Sensei Nico, quien recientemente, junto con José y Eugenio, comenzaron un nuevo camino llamado Córdoba Aikikai (Sensei, gracias por ser mi uke en el exámen!)
+
Toda la comunidad de Córdoba Aikikai, gente recorriendo sus propios caminos en el Aikido y ayudándose mutuamente en el día a día.
+
Shihan Ricardo Corbal, que nos dejó sus enseñanzas y fue quién me tomó el exámen (gracias por los consejos post-exámen, trabajaré en esos puntos para mejorarlos)
+
Daniela, mi amor, que me aguanta y me ha ayudado en todo este proceso
-
OK, this is video, in case you want to see some action ;-)
-
As I said before, this is just the beginning of a new phase in my Aikido practice and I am pretty sure I will enjoy it!
+
OK, este es el video, en caso de que quieran ver un poco de acción ;-)
+
Como he dicho anteriormente, éste es sólo el comienzo de una nueva fase en mi práctica de Aikido... y estoy seguro que la disfrutaré!
diff --git a/cache/posts/my-ipython-powered-semi-automatic-git-workflow.es.html b/cache/posts/my-ipython-powered-semi-automatic-git-workflow.es.html
new file mode 100644
index 00000000..373d3a8b
--- /dev/null
+++ b/cache/posts/my-ipython-powered-semi-automatic-git-workflow.es.html
@@ -0,0 +1,998 @@
+
+
+
+
+
+
This is the last post of this year, so I try to do my best to give you something interesting to think about...
+
In this case, I will show you my git workflow... and you know there are a lot of workflows out there... and probably better than mine, but I just want to share with you the place where I find myself comfortable.
+
And yes... my git workflow is also powered by IPython (I am very repetitive when I love a project!).
+And it is a semi-automatic one, using the IPython notebooks (ipynbs) as a sort of templates, transforming them into a new conceptual entity: the ipytmpl (and yes, I love to invent names too!).
+
+
Because my workflow have essentially two cycles, in this post, I will show you the general set up of the environment and the first Short cycle, leaving the second Extended cycle (and other details) for other post (after the new year, of course).
+
I will also show you my workflow with a realPR (pull-request) to the IPython project.
First, we need to set up the environment to make our work:
+
+
+
+
+
+
+
+
+
+
Check the current working directory:
+
+
+
+
+
+
+
+
In [1]:
+
+
+
%pwd
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Out[1]:
+
+
+
+
+
+
u'/media/datos/Desarrollos'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Make a new folder to isolate our work and cd into it:
+
+
+
+
+
+
+
+
In [2]:
+
+
+
!mkdir devel_example
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
In [3]:
+
+
+
%cd devel_example/
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
/media/datos/Desarrollos/devel_example
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
NOTE: You can avoid these steps opening the notebook in the proper directory, but in this case I want to have the example isolated to not overwrite my current development environment.
Clone the project and connect the local repo with my Github fork:
+
+
+
+
+
+
+
+
In [5]:
+
+
+
# Get a read-only copy of the project
+!git clone $project_remote
+
+# cd into the local project folder
+%cd $project_name
+
+# Link the local repo with my Github fork
+!git remote add $my_fork_remote_name$my_fork_remote
+
+# Check remotes
+!git remote -v
+
NOTE: A lot of git workflows use origin to point to our fork and upstream to point to the project repo. But I do not like that configuration. It seems more natural to me to clone the project repo (the origin repo) and add a connection to my fork called damianavila... and the next steps take into consideration this last approach.
This short cycle just create a new branch to work on, make the needed changes in the source code and upload the local changes to our Github fork to finally submit a pull-request:
# Make sure we are in master branch
+!git checkout $master_branch
+
+# Pull the changes from origin/master
+!git pull $project_remote_name
+
+# Start a new branch to work on
+!git checkout -b $feature_branch
+
+# Check where we are
+!git status
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Ya está en «master»
+Already up-to-date.
+Switched to a new branch 'doc_post_serve'
+# En la rama doc_post_serve
+nothing to commit, working directory clean
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Make the changes you want to do:
+
+
NOTE: In this example, I will update the IPython docs about some details using the IPython slides and the post-serve post-processor (IPython.nbconvert).
+
+
+
+
+
+
+
+
In [9]:
+
+
+
# list the files structure to find the needed files
+%ls
+
%load docs/source/interactive/nbconvert.rst
+# After executing %load, a new cell containing the source code will be added.
+# Be sure to add the next line (with the proper path) to overwrite the file
+# with you changes.
+#
+# %%writefile docs/source/interactive/nbconvert.rst
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
In [11]:
+
+
+
%%writefile docs/source/interactive/nbconvert.rst
+.. _nbconvert:
+
+Converting notebooks to other formats
+=====================================
+
+Newly added in the 1.0 release of IPython is the ``nbconvert`` tool, which
+allows you to convert an ``.ipynb`` notebook document file into various static
+formats.
+
+Currently, ``nbconvert`` is provided as a command line tool, run as a script
+using IPython. A direct export capability from within the
+IPython Notebook web app is planned.
+
+The command-line syntax to run the ``nbconvert`` script is::
+
+ $ ipython nbconvert --to FORMAT notebook.ipynb
+
+This will convert the IPython document file ``notebook.ipynb`` into the output
+format given by the ``FORMAT`` string.
+
+The default output format is html, for which the ``--to`` argument may be
+omitted::
+
+ $ ipython nbconvert notebook.ipynb
+
+IPython provides a few templates for some output formats, and these can be
+specified via an additional ``--template`` argument.
+
+The currently supported export formats are:
+
+* ``--to html``
+
+ - ``--template full`` (default)
+
+ A full static HTML render of the notebook.
+ This looks very similar to the interactive view.
+
+ - ``--template basic``
+
+ Simplified HTML, useful for embedding in webpages, blogs, etc.
+ This excludes HTML headers.
+
+* ``--to latex``
+
+ Latex export. This generates ``NOTEBOOK_NAME.tex`` file,
+ ready for export. You can automatically run latex on it to generate a PDF
+ by adding ``--post PDF``.
+
+ - ``--template article`` (default)
+
+ Latex article, derived from Sphinx's howto template.
+
+ - ``--template book``
+
+ Latex book, derived from Sphinx's manual template.
+
+ - ``--template basic``
+
+ Very basic latex output - mainly meant as a starting point for custom templates.
+
+* ``--to slides``
+
+ This generates a Reveal.js HTML slideshow.
+ It must be served by an HTTP server. The easiest way to do this is adding
+ ``--post serve`` on the command-line. The ``--post serve`` post-processor
+ proxies Reveal.js requests to a CDN if no local Reveal.js library is present.
+ For low connectivity environments, just place the Reveal.js library in the
+ same directory where your_talk.slides.html is located or point to another
+ directory using the ``--reveal-prefix`` alias.
+
+* ``--to markdown``
+
+ Simple markdown output. Markdown cells are unaffected,
+ and code cells are placed in triple-backtick (```````) blocks.
+
+* ``--to rst``
+
+ Basic reStructuredText output. Useful as a starting point for embedding notebooks
+ in Sphinx docs.
+
+* ``--to python``
+
+ Convert a notebook to an executable Python script.
+ This is the simplest way to get a Python script out of a notebook.
+ If there were any magics in the notebook, this may only be executable from
+ an IPython session.
+
+.. note::
+
+ nbconvert uses pandoc_ to convert between various markup languages,
+ so pandoc is a dependency of most nbconvert transforms,
+ excluding Markdown and Python.
+
+.. _pandoc: http://johnmacfarlane.net/pandoc/
+
+The output file created by ``nbconvert`` will have the same base name as
+the notebook and will be placed in the current working directory. Any
+supporting files (graphics, etc) will be placed in a new directory with the
+same base name as the notebook, suffixed with ``_files``::
+
+ $ ipython nbconvert notebook.ipynb
+ $ ls
+ notebook.ipynb notebook.html notebook_files/
+
+For simple single-file output, such as html, markdown, etc.,
+the output may be sent to standard output with::
+
+ $ ipython nbconvert --to markdown notebook.ipynb --stdout
+
+Multiple notebooks can be specified from the command line::
+
+ $ ipython nbconvert notebook*.ipynb
+ $ ipython nbconvert notebook1.ipynb notebook2.ipynb
+
+or via a list in a configuration file, say ``mycfg.py``, containing the text::
+
+ c = get_config()
+ c.NbConvertApp.notebooks = ["notebook1.ipynb", "notebook2.ipynb"]
+
+and using the command::
+
+ $ ipython nbconvert --config mycfg.py
+
+
+.. _notebook_format:
+
+LaTeX citations
+---------------
+
+``nbconvert`` now has support for LaTeX citations. With this capability you
+can:
+
+* Manage citations using BibTeX.
+* Cite those citations in Markdown cells using HTML data attributes.
+* Have ``nbconvert`` generate proper LaTeX citations and run BibTeX.
+
+For an example of how this works, please see the citations example in
+the nbconvert-examples_ repository.
+
+.. _nbconvert-examples: https://github.com/ipython/nbconvert-examples
+
+Notebook JSON file format
+-------------------------
+
+Notebook documents are JSON files with an ``.ipynb`` extension, formatted
+as legibly as possible with minimal extra indentation and cell content broken
+across lines to make them reasonably friendly to use in version-control
+workflows. You should be very careful if you ever manually edit this JSON
+data, as it is extremely easy to corrupt its internal structure and make the
+file impossible to load. In general, you should consider the notebook as a
+file meant only to be edited by the IPython Notebook app itself, not for
+hand-editing.
+
+.. note::
+
+ Binary data such as figures are also saved directly in the JSON file.
+ This provides convenient single-file portability, but means that the
+ files can be large; a ``diff`` of binary data is also not very
+ meaningful. Since the binary blobs are encoded in a single line, they
+ affect only one line of the ``diff`` output, but they are typically very
+ long lines. You can use the ``Cell | All Output | Clear`` menu option to
+ remove all output from a notebook prior to committing it to version
+ control, if this is a concern.
+
+The notebook server can also generate a pure Python version of your notebook,
+using the ``File | Download as`` menu option. The resulting ``.py`` file will
+contain all the code cells from your notebook verbatim, and all Markdown cells
+prepended with a comment marker. The separation between code and Markdown
+cells is indicated with special comments and there is a header indicating the
+format version. All output is removed when exporting to Python.
+
+As an example, consider a simple notebook called ``simple.ipynb`` which
+contains one Markdown cell, with the content ``The simplest notebook.``, one
+code input cell with the content ``print "Hello, IPython!"``, and the
+corresponding output.
+
+The contents of the notebook document ``simple.ipynb`` is the following JSON
+container::
+
+ {
+ "metadata": {
+ "name": "simple"
+ },
+ "nbformat": 3,
+ "nbformat_minor": 0,
+ "worksheets": [
+ {
+ "cells": [
+ {
+ "cell_type": "markdown",
+ "metadata": {},
+ "source": "The simplest notebook."
+ },
+ {
+ "cell_type": "code",
+ "collapsed": false,
+ "input": "print \"Hello, IPython\"",
+ "language": "python",
+ "metadata": {},
+ "outputs": [
+ {
+ "output_type": "stream",
+ "stream": "stdout",
+ "text": "Hello, IPython\n"
+ }
+ ],
+ "prompt_number": 1
+ }
+ ],
+ "metadata": {}
+ }
+ ]
+ }
+
+
+The corresponding Python script is::
+
+ # -*- coding: utf-8 -*-
+ # <nbformat>3.0</nbformat>
+
+ # <markdowncell>
+
+ # The simplest notebook.
+
+ # <codecell>
+
+ print "Hello, IPython"
+
+Note that indeed the output of the code cell, which is present in the JSON
+container, has been removed in the ``.py`` script.
+
# En la rama doc_post_serve
+# Cambios no preparados para el commit:
+# (use «git add <archivo>...» para actualizar lo que se ejecutará)
+# (use «git checkout -- <archivo>...« para descartar cambios en le directorio de trabajo)
+#
+# modificado: docs/source/interactive/nbconvert.rst
+#
+no hay cambios agregados al commit (use «git add» o «git commit -a»)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In [13]:
+
+
+
# See the diff
+!git diff
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/source/interactive/nbconvert.rst b/docs/source/interactive/nbconvert.rst
+index 1789a62..610edf0 100644
+--- a/docs/source/interactive/nbconvert.rst
++++ b/docs/source/interactive/nbconvert.rst
+@@ -61,8 +61,12 @@ The currently supported export formats are:
+ * ``--to slides``
+
+ This generates a Reveal.js HTML slideshow.
+- It must be served by an HTTP server. The easiest way to do this is adding
+- ``--post serve`` on the command-line.
++ It must be served by an HTTP server. The easiest way to do this is adding
++ ``--post serve`` on the command-line. The ``--post serve`` post-processor
++ proxies Reveal.js requests to a CDN if no local Reveal.js library is present.
++ For low connectivity environments, just place the Reveal.js library in the
++ same directory where your_talk.slides.html is located or point to another
++ directory using the ``--reveal-prefix`` alias.
+
+ * ``--to markdown``
+
+@@ -224,4 +228,3 @@ The corresponding Python script is::
+
+ Note that indeed the output of the code cell, which is present in the JSON
+ container, has been removed in the ``.py`` script.
+-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Add the changes an commit them:
+
+
+
+
+
+
+
+
In [14]:
+
+
+
# Add the modified files to the stage
+!git add .
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
In [15]:
+
+
+
# And do your commit
+!git commit -am "Added --post-serve explanation into the nbconvert docs."
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
[doc_post_serve c87ac2f] Added --post-serve explanation into the nbconvert docs.
+ 1 file changed, 6 insertions(+), 3 deletions(-)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Finally, push your local development branch to your Github fork:
+
+
+
+
+
+
+
+
In [16]:
+
+
+
# Push updates from your local branch to your github branch
+!git push $my_fork_remote_name$feature_branch
+
NOTE: The merging of your Github development branch into the master is done via pull-request on the Github website. For reference, you can see the proposed PR here: https://github.com/ipython/ipython/pull/4751
+
+
+
+
+
+
+
+
+
+
As you can see, this workflow is very simple... and with the aid of this ipytmpl is easier than before (before = making the same but in your traditional console).
+
You set up the environment, fill the variables to use a posteriori, and you have only to be concern about the changes you want to introduce (or remove) from the source code. All the other steps, all those git calls are predetermined and will be called whereas you advance in the workflow...
+
After making the PR at the Github website, you will receive some feedback and if you have to modified something, just start the short cycle again... Sometimes you will need more... I mean, because you are working in a communitary project, if somebody changes the same file as you, there will be some conflicts at the merge step, so it will be necessary to rebase the "thing". But this is the central idea of the second Extended cycle which I will describe you in a second part of this post.
+
As always, I am waiting for your comments and critics!
+
OK, too long... I hope you did not get bored!
+
Have a nice New Year! And I see you in 2014 ;-)
+
Cheers.
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/my-ipython-powered-semi-automatic-git-workflow.es.html.dep b/cache/posts/my-ipython-powered-semi-automatic-git-workflow.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/nikola-nbconvert.es.html b/cache/posts/nikola-nbconvert.es.html
new file mode 100644
index 00000000..a32ce9e6
--- /dev/null
+++ b/cache/posts/nikola-nbconvert.es.html
@@ -0,0 +1,2659 @@
+
Importando, en un posteo del blog, un html estático (obtenido con nbconvert)
+de un notebook (ejemplo) de IPython:
+
+.. raw:: html
+ :file: /Users/davila/devel/damian_blog/files/Test.html
+
+
+
Funciona! Pueden verlo a continuación... pronto estarán los themes disponibles.
+
+
+
Update: made full github repo for blog-as-notebooks, and updated instructions on how to more easily configure everything and use the newest nbconvert for a more streamlined workflow.
+
Since the notebook was introduced with IPython 0.12, it has proved to be very popular, and we are seeing great adoption of the tool and the underlying file format in research and education. One persistent question we've had since the beginning (even prior to its official release) was whether it would be possible to easily write blog posts using the notebook. The combination of easy editing in markdown with the notebook's ability to contain code, figures and results, makes it an ideal platform for quick authoring of technical documents, so being able to post to a blog is a natural request.
+
Today, in answering a query about this from a colleague, I decided to try again the status of our conversion pipeline, and I'm happy to report that with a bit of elbow-grease, at least on Blogger things work pretty well!
+
The purpose of this post is to quickly provide a set of instructions on how I got it to work, and to test things out. Please note: this requires code that isn't quite ready for prime-time and is still under heavy development, so expect some assembly.
+
+
+
+ Converting your notebook to html with nbconvert
+
+
+
+
The first thing you will need is our nbconvert tool that converts notebooks across formats. The README file in the repo contains the requirements for nbconvert (basically python-markdown, pandoc, docutils from SVN and pygments).
+
Once you have nbconvert installed, you can convert your notebook to Blogger-friendly html with:
+
nbconvert -f blogger-html your_notebook.ipynb
+
+
This will leave two files in your computer, one named your_notebook.html and one named your_noteboook_header.html; it might also create a directory called your_notebook_files if needed for ancillary files. The first file will contain the body of your post and can be pasted wholesale into the Blogger editing area. The second file contains the CSS and Javascript material needed for the notebook to display correctly, you should only need to use this once to configure your blogger setup (see below):
+
# Only one notebook so far
+(master)longs[blog]> ls
+120907-Blogging with the IPython Notebook.ipynb fig/ old/
+
+# Now run the conversion:
+(master)longs[blog]> nbconvert.py -f blogger-html 120907-Blogging\ with\ the\ IPython\ Notebook.ipynb
+
+# This creates the header and html body files
+(master)longs[blog]> ls
+120907-Blogging with the IPython Notebook_header.html fig/
+120907-Blogging with the IPython Notebook.html old/
+120907-Blogging with the IPython Notebook.ipynb
+
+
+
+
+ Configuring your Blogger blog to accept notebooks
+
+
+
+
The notebook uses a lot of custom CSS for formatting input and output, as well as Javascript from MathJax to display mathematical notation. You will need all this CSS and the Javascript calls in your blog's configuration for your notebook-based posts to display correctly:
+
+
Once authenticated, go to your blog's overview page by clicking on its title.
+
Click on templates (left column) and customize using the Advanced options.
+
Scroll down the middle column until you see an "Add CSS" option.
+
Copy entire the contents of the _header file into the CSS box.
+
+
+
+
That's it, and you shouldn't need to do anything else as long as the CSS we use in the notebooks doesn't drastically change. This customization of your blog needs to be done only once.
+
While you are at it, I recommend you change the width of your blog so that cells have enough space for clean display; in experimenting I found out that the default template was too narrow to properly display code cells, producing a lot of text wrapping that impaired readability. I ended up using a layout with a single column for all blog contents, putting the blog archive at the bottom. Otherwise, if I kept the right sidebar, code cells got too squished in the post area.
+
I also had problems using some of the fancier templates available from 'Dynamic Views', in that I could never get inline math to render. But sticking to those from the Simple or 'Picture Window' categories worked fine and they still allow for a lot of customization.
+
Note: if you change blog templates, Blogger does destroy your custom CSS, so you may need to repeat the above steps in that case.
+
+
+
+ Adding the actual posts
+
+
+
+
+
Now, whenever you want to write a new post as a notebook, simply convert the .ipynb file to blogger-html and copy its entire contents to the clipboard. Then go to the 'raw html' view of the post, remove anything Blogger may have put there by default, and paste. You should also click on the 'options' tab (right hand side) and select both Show HTML literally and Use <br> tag, else your paragraph breaks will look all wrong.
+
That's it!
+
+
+
+ What can you put in?
+
+
+
+
I will now add a few bits of code, plots, math, etc, to show which kinds of content can be put in and work out of the box. These are mostly bits copied from our example notebooks so the actual content doesn't matter, I'm just illustrating the kind of content that works.
+
+
+
+
In [1]:
+
+
# Let's initialize pylab so we can plot later
+%pylabinline
+
+
+
+
+
+
+
+
+
+
+Welcome to pylab, a matplotlib-based Python environment [backend: module://IPython.zmq.pylab.backend_inline].
+For more information, type 'help(pylab)'.
+
+
+
+
+
+
+
+
With pylab loaded, the usual matplotlib operations work
The notebook, thanks to MathJax, has great LaTeX support, so that you can type inline math $(1,\gamma,\ldots, \infty)$ as well as displayed equations:
+
$$
+e^{i \pi}+1=0
+$$
+
but by loading the sympy extension, it's easy showcase math output from Python computations, where we don't type the math expressions in text, and instead the results of code execution are displayed in mathematical format:
+
+
+
+
In [3]:
+
+
%load_extsympyprinting
+importsympyassym
+fromsympyimport*
+x,y,z=sym.symbols("x y z")
+
Using our various script cell magics, it's easy to include code in a variety of other languages
+
+
+
+
In [10]:
+
+
%%ruby
+puts"Hello from Ruby #{RUBY_VERSION}"
+
+
+
+
+
+
+
+
+
+
Hello from Ruby 1.8.7
+
+
+
+
+
+
+
+
+
In [11]:
+
+
%%bash
+echo"hello from $BASH"
+
+
+
+
+
+
+
+
+
+
hello from /bin/bash
+
+
+
+
+
+
+
+
And tools like the Octave and R magics let you interface with entire computational systems directly from the notebook; this is the Octave magic for which our example notebook contains more details:
+ Keep in mind, this is still experimental code!
+
+
+
+
Hopefully this post shows that the system is already useful to communicate technical content in blog form with a minimal amount of effort. But please note that we're still in heavy development of many of these features, so things are susceptible to changing in the near future. By all means join the IPython dev mailing list if you'd like to participate and help us make IPython a better tool!
+
+
Damián.
diff --git a/cache/posts/nikola-nbconvert.es.html.dep b/cache/posts/nikola-nbconvert.es.html.dep
new file mode 100644
index 00000000..517e718b
--- /dev/null
+++ b/cache/posts/nikola-nbconvert.es.html.dep
@@ -0,0 +1 @@
+files/Test.html
\ No newline at end of file
diff --git a/cache/posts/nikola-nbconvert.html b/cache/posts/nikola-nbconvert.html
index 6dccc20f..88d12d8d 100644
--- a/cache/posts/nikola-nbconvert.html
+++ b/cache/posts/nikola-nbconvert.html
@@ -2,7 +2,7 @@
one IPython example notebook into a nikola blog post:
.. raw:: html
- :file: /media/data/devel/damian_blog/files/Test.html
+ :file: /Users/davila/devel/damian_blog/files/Test.html
It works! You can see below... the themes will be available soon.
diff --git a/cache/posts/nikolas-zen-theme-finally-released.es.html b/cache/posts/nikolas-zen-theme-finally-released.es.html
new file mode 100644
index 00000000..e78d584b
--- /dev/null
+++ b/cache/posts/nikolas-zen-theme-finally-released.es.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+
Just a quick update... Some weeks ago I blogged about my new Nikola's theme family called Zen. In fact, you are seeing the zen-ipython theme powering my blog right now.
+
I have used them for several days without any remarkable issue, so I decided to release them at the Nikola's theme repository.
+
There, you will see three Zen themes:
+
+
zen, based in mako templates
+
zen-jinja, the same zen theme but based (obviously) in jinja templates
+
zen-ipython, a jinja-based zen theme suited to be used with the IPython notebooks.
+
+
As you know, you can easily install them using the following command inside your Nikola site folder:
I have developed the Zen theme family with a high customization concept in my mind... but this approach has a cost because you need to use a properconf.py file to run them ok (the default one will not work, but you can find a working example looking at my blog conf.pyfile).
+
OK, it's all for this post.
+
Enjoy the Zen themes and, as usually, report me any problem...
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/nikolas-zen-theme-finally-released.es.html.dep b/cache/posts/nikolas-zen-theme-finally-released.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/one-line-deployment-of-your-site-to-gh-pages.es.html b/cache/posts/one-line-deployment-of-your-site-to-gh-pages.es.html
new file mode 100644
index 00000000..795ffc9f
--- /dev/null
+++ b/cache/posts/one-line-deployment-of-your-site-to-gh-pages.es.html
@@ -0,0 +1,52 @@
+
+
+
+
+
+
Do you want to easily deploy your site to Github pages?
+
OK, here we go...
+
+
You have to upload your complete blog/site to a new Github repository (you know how to do it... if not, probably you need to learn some things before try this one, hehe). As a plus, now your blog/site is version-controlled!
+
+
Almost for sure, your site/blog lives in the master branch of the new repository, but you need to generated a gh-pages branch to push your build or output folder, I mean your site/blog content to deploy... not all the machinery of your site/blog platform (Nikola in my case):
+
+
+
+
git checkout -b gh-pages
+
git rm -rf .
+
git commit -am "First commit to gh-pages branch"
+
git push origin gh-pages
+
+
+
Now, we will use a git-subtree technique to push the build or output content to the gh-pages branch:
Finally, you will need to run the following line every time you want to update your site/blog!
+
+
git subtree push --prefix output origin gh-pages
+
+
+
+
Note: Are you getting git errors? Just use the sweet line again and force the update...
+
If you are using Nikola, you can add some of this lines to the DEPLOY_COMMANDS in your conf.py file and just run nikola deploy after building your site/blog.
+
More easier... impossible... ;-)
+
Damián.
+
UPDATE: Not enough happy with step 3 and 4 (essentially because of some git errors), I figured out a cleaner solution:
+
New 3. Now, we will use a git-subtree technique to push the build or output content to the gh-pages branch. You will need to run the following lines every time you want to update your site/blog!
+
+
git checkout master # you can avoid this line if you are in master...
+
git subtree split --prefix output -b gh-pages # create a local gh-pages branch containing the splitted output folder
+
git push -f origin gh-pages:gh-pages # force the push of the gh-pages branch to the remote gh-pages branch at origin
+
git branch -D gh-pages # delete the local gh-pages because you will need it: ref
+
+
+
+
+
+
+
diff --git a/cache/posts/one-line-deployment-of-your-site-to-gh-pages.es.html.dep b/cache/posts/one-line-deployment-of-your-site-to-gh-pages.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/paraguay.es.html b/cache/posts/paraguay.es.html
new file mode 100644
index 00000000..0d06b2b4
--- /dev/null
+++ b/cache/posts/paraguay.es.html
@@ -0,0 +1,11 @@
+
Lo que esta viviendo hoy el Paraguay me causa mucha tristeza...
+
¡¿Cómo puede ser que a comienzos del siglo XXI,
+la retrógrada derecha latinoamericana no se haya superado y alcanzado
+el nivel democrático necesario para, al menos, respetar que otros han ganado
+las elecciones y, por tanto, éstos deben detentar el poder hasta que finalice el mandato
+impuesto por la Constitución Nacional?!
diff --git a/cache/posts/paraguay.es.html.dep b/cache/posts/paraguay.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/powered-by-nikola.es.html b/cache/posts/powered-by-nikola.es.html
new file mode 100644
index 00000000..755c60b0
--- /dev/null
+++ b/cache/posts/powered-by-nikola.es.html
@@ -0,0 +1,11 @@
+
Nikola es un generador de sitios estáticos creado por uno de los miembros de la comunidad
+de PyAr (Roberto Alsina). Es un excelente proyecto y, también,
+la herramienta pythonica que he elegido para construir mi nuevo blog...
+
Espero poder con contribuir al proyecto en el futuro cercano (ya le prometí a Roberto que
+enviaría unas mejoras a través de github, pero aún no lo he hecho... lo haré pronto).
+
La página web del proyecto es http://nikola.ralsina.com.ar, y fue construída utilizándose
+el mismo generador, desde luego.
+
¡Disfrútenlo!
+
Damián.
+
PD: El "tema" que están viendo ahora mismo en el blog no está incluído en Nikola,
+lo postearé pronto, cuando esté listo para "salir del horno"...
diff --git a/cache/posts/powered-by-nikola.es.html.dep b/cache/posts/powered-by-nikola.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/pyconar-2013.es.html b/cache/posts/pyconar-2013.es.html
new file mode 100644
index 00000000..0bd63415
--- /dev/null
+++ b/cache/posts/pyconar-2013.es.html
@@ -0,0 +1,56 @@
+
+
+
+
+
+
Note: Post only in spanish (but also interesting!)
+
Hace un par de semanas, terminando el mes de Octubre, se llevó a cabo en la ciudad de Rosario, la 5° Conferencia Anual de Python Argentina - PyConAr 2013.
+
En esta oportunidad, presenté dos charlas:
+
+
+
la clásica, Introducción a Python Científico (slides),
+
la nueva, IPython-fu: el camino de la "nbconversión" (slides).
+
+
Me sentí muy cómodo dictando las dos charlas, y encima me di el gusto de "meter" una charla íntegra del notebook de IPython, sobre el cual vengo "pregonando" hace rato.
+
Por otro lado, gracias al esfuerzo puesto en juego por la organización del evento, tenemos videograbación de toda la conferencia.
+
A continuación, les adjunto los videos de mis charlas... por si se perdieron alguna:
+
+
+
+
+
+
+
+
+
+
Introducción a Python Científico
+
+
+
+
+
+
+
+
+
+
+
IPython-fu: el camino de la "nbconversión"
+
+
+
+
+
+
+
+
+
+
Una vez más, participar en la PyConAr fue una gran experiencia, no sólo desde el punto de vista técnico, sino también, y más importante aún, desde el punto de vista humano.
+
Aún resta saber dónde será la próxima edición.
+
¡Allí estaremos!
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/pyconar-2013.es.html.dep b/cache/posts/pyconar-2013.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/reveal_converter-mini-tutorial.es.html b/cache/posts/reveal_converter-mini-tutorial.es.html
new file mode 100644
index 00000000..8e633bc7
--- /dev/null
+++ b/cache/posts/reveal_converter-mini-tutorial.es.html
@@ -0,0 +1,61 @@
+
+
+
+
+
+
Alert! This post is outdated, please goto ;-) this link to get updated information.
+
+
+
+
+
+
+
+
+
+
After some weeks of work and a lot of useful colaboration with the IPython team, we now have the reveal converter merged in nbconvert (a conversion utilities for the IPython notebook format).
+
Currently nbconvert is being rewritten... but we also have a reveal converter in the new codebase, so you do not have problems if you begin to use it now, you will be able to use it tomorrow :-)
+
I wrote a little tutorial (a reveal-based notebook slideshow, of course) about how to use reveal converter option inside nbconvert
If you want to see it without leaving this page (I do not recommend this last option, it is a small iframe).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
I hope you use it and report any problem.
+
Cheers.
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/reveal_converter-mini-tutorial.es.html.dep b/cache/posts/reveal_converter-mini-tutorial.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/rise-400b1-is-available-please-test-it.es.html b/cache/posts/rise-400b1-is-available-please-test-it.es.html
new file mode 100644
index 00000000..ddc91340
--- /dev/null
+++ b/cache/posts/rise-400b1-is-available-please-test-it.es.html
@@ -0,0 +1,21 @@
+
+
+
+
+
+
Quick post! I have beta packages available for you to test RISE, if you can test it that would be awesome!!
+
In case you don't know about it, with RISE you get your Jupyter notebook rendered as a Reveal.js-based slideshow, where you can execute code on the fly or show to the audience whatever you can show/do inside the notebook itself (but in a "slidy" way).
I don't want to repeat myself ;-) so go the the above link and check it.
+
The 4.0.0 release essentially deals with packaging and stuff to be compatible with the latest mechanisms on the Jupyter notebook to install and enable nbextensions (and RISE is a nbextension). But also fixes bugs and provide some enhancements.
This released was focused in updating Reveal.js to the latest (3.5.0) and fix several bugs in the config mechanism. We also re-did the scrolling feature and, finally, we built the python 3.6 conda packages.
PS: If you are using/developing RISE from master (I strongly recommend you to use the packaged solutions if you don't want to develop on it), it would a good idea to reinstall the whole thing from scratch to avoid collisions between the previous way to get Reveal.js and the current one. For more information about the development installation, please check https://github.com/damianavila/RISE#development
+
+
+
+
+
+
diff --git a/cache/posts/rise-500-is-out.es.html.dep b/cache/posts/rise-500-is-out.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/rise-510-is-out.es.html b/cache/posts/rise-510-is-out.es.html
new file mode 100644
index 00000000..aa9370c3
--- /dev/null
+++ b/cache/posts/rise-510-is-out.es.html
@@ -0,0 +1,42 @@
+
+
+
+
+
+
We're pleased to announce the release of RISE 5.1.0!
+
RISE allows you show your Jupyter notebooks rendered as an executableReveal.js-based slideshow. It is your very same notebook but presented in a slidy way!
+
What are the new goodies for this release?
+
+
+
autolaunch config option to enable immediate launch of the slideshow view as soon as you open your notebook, very useful to use at mybinder.
+
smart exec allows you to execute cells and then proceed to the next cell WHEN the context permits, pretty similar to the native experience in the notebook view but it takes into consideration the slideshow view limitations and particularities
+
auto_select allows you to automatically select the first (or first code) cell any time you either move to a new slide, subslide or when you show (or hide) a new fragment
+
new overlay, header, background and footer customizable options
+
customizable CSS
+
keyboard customization through the notebook keyboard manager
+
new keyboard shortcuts to toggle cells as slide, subslides and fragments
+
+
For more information about all these new enhancements/features, please check the usage and the customization sections in the docs.
For more information about the how to contribute, please check the developer docs.
+
Special mentions
+
I want to truly thanks to Thierry Parmentelat, aka as @parmentelat, for all the contributions he made in the last couple of months. He is responsible of most the new features coming into this new release.
+
BIG THANK YOU!
+
I also want to mention and thanks to Chris Holdgraf@choldgraf, one of the members of the Binder team who quickly caugth the release and made it available at Binder (add also contributed with the autolaunch options and docs).
+
Enjoy it!
+
And thanks for using RISE!
+
ADDENDUM
+
We have detected some issues trying to install RISE on win boxes reported here. I have rebuilt the packages and they seem to be working OK by now. Let us know if you have further issues. Thanks.
+
+
+
+
+
+
diff --git a/cache/posts/rise-510-is-out.es.html.dep b/cache/posts/rise-510-is-out.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/rise-520-is-out.es.html b/cache/posts/rise-520-is-out.es.html
new file mode 100644
index 00000000..0acb58a3
--- /dev/null
+++ b/cache/posts/rise-520-is-out.es.html
@@ -0,0 +1,22 @@
+
+
+
+
+
+
We're pleased to announce the release of RISE 5.2.0!
+
RISE let's you show yout Jupyter notebook rendered as an executable Reveal.js-based slideshow. It is your very same notebook but in a slidy way!
+
+
How you can get it?
+
If you are a conda/anaconda user, you can install it with conda install -c damianavila82 rise.
This released was mainly focused in some source code cleanup and normalization, several fixes and enhancements in the documentation, new default values for the auto_select and start_slideshow_at config options and a scroll-aware behavior for the output observer.
This released was mainly focused on a general documentation review, fixes and improvements (now we have the docs deployed with readthedocs), a general setup.py review, simplification and improvement, RISE compliance with the nbextensions_configurator project, and auto enabling behavior when installing with pip, plus some other specific bugfixes and enhancements.
This released was mainly focused on setup.py enhancements, documentation updates (mainly in the PDF section), compatibility fixes, and two new nice features: chalkboard functionality and speaker notes!!
+
+
diff --git a/cache/posts/rise-541-is-out.es.html.dep b/cache/posts/rise-541-is-out.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/rise-meets-jupyterlab.es.html b/cache/posts/rise-meets-jupyterlab.es.html
new file mode 100644
index 00000000..7766eb25
--- /dev/null
+++ b/cache/posts/rise-meets-jupyterlab.es.html
@@ -0,0 +1,20 @@
+
+
+
+
+
+
JupyterLab is the future for the notebook/authoring experience.
+
And people started to ask me if we will have RISE on JupyterLab
+
Do you want to know the answer?
+
+
OK, first, an important note, this is just a afternoon hack with the jupyterlab extensions machinery.
+This is a very early PoC showing that things are possible, but it is not a shareable code base, at least, not yet ;-)
+
+
diff --git a/cache/posts/rise-meets-jupyterlab.es.html.dep b/cache/posts/rise-meets-jupyterlab.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/scipycon-argentina-2013.es.html b/cache/posts/scipycon-argentina-2013.es.html
new file mode 100644
index 00000000..4c98738c
--- /dev/null
+++ b/cache/posts/scipycon-argentina-2013.es.html
@@ -0,0 +1,37 @@
+
+
+
+
+
+
This is the first SciPy Conference in Argentina (as far as I know, it is also the first one in Latin American).
+
It will be held from 16 to 18th of May in Puerto Madryn, at the Patagonia Argentina (more details at SciPyCon homepage).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
I am very proud to have this kind of conference in my country, and I would like to thanks to the organizers (and the sponsors) for all their hard work to make it happens.
+
The conference will have exciting talks, tutorials and poster presentations. You can check the schedulehere
+
I will be presenting a tutorial called, Python Científico: Episodio I (Scientific Python: Episode I). You can check the details here.
+
And I will be also presenting a talk called, IPython notebook: el "paper ejecutable" (IPython notebook: the "executable paper").
+
This conference will be a boost for our growing Scientific Pythonic Community and an exciting beginning!
+
Why I am writing in English about a Spanish Conference? Because I want to spread the word about this conference as much as I can and because there are international speakers scheduled (and I would love to see more in the next conference!)
+
I hope to see you there!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/scipycon-argentina-2013.es.html.dep b/cache/posts/scipycon-argentina-2013.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/slider-for-nbconvert.es.html b/cache/posts/slider-for-nbconvert.es.html
new file mode 100644
index 00000000..f987f28f
--- /dev/null
+++ b/cache/posts/slider-for-nbconvert.es.html
@@ -0,0 +1,25 @@
+
I have implemented reveal.js slides for vIPer (I will publish a
+post about that the next days...).
You can see a video showing the basic functionality here
+(big sorry for the quality, I will post a better one soon):
+
There is a lot of stuff to do with that... I will do it when I get some free time.
+
Just my two cents!
+
Enjoy!
+
Damián.
diff --git a/cache/posts/slider-for-nbconvert.es.html.dep b/cache/posts/slider-for-nbconvert.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/slideviewer-a-simple-way-to-share-your-ipython-slides.es.html b/cache/posts/slideviewer-a-simple-way-to-share-your-ipython-slides.es.html
new file mode 100644
index 00000000..c7c68844
--- /dev/null
+++ b/cache/posts/slideviewer-a-simple-way-to-share-your-ipython-slides.es.html
@@ -0,0 +1,41 @@
+
+
+
+
+
+
Short Notice:
+
After some months of silence, I am back... A lot of things have happened in my life lately, some of them are really good things... some others don't. And all those things kept me very busy, but finally I have made me some time to write again! ;-)
+
OK, I have a long list of news, topics, ideas and developments I want to share with you, but we have to begin with one of them, and the chosen one is Slideviewer.
+
+
When I was at SciPy 2013, one of the talks I presented was about the IPython slides (if you dont know what I am talking about, just check some of these posts). And one of the last things I presented in that talk was an early prototype of Slideviewer, an NBviewer's clon, but able to render IPython slides instead of plain IPython notebooks (.ipynb).
+
The main idea behind Slideviewer was to provide you an easy way to share your IPython slides. As I pointed out in older posts and comments, you can deploy your IPython slides (the slides.html file plus the reveal.js library) using Github pages or any other service, but with Slideviewer, you only need to host your .ipynb somewhere (ie, Github repo, gist, etc.), and just pass the url to the Slideviewer service (the same way you do it with the NBviewer service) which will render your .ipynb to an IPython slide automagically.
+
Slideviewer will follow NBviewer updates once a week, as close as it can be, essentially because some things are relevant for both apps, but others don't.
+
And, in the future, we can probably merge the Slideviewer app onto the NBviewer app, but we need to make some things first, so I think is useful to have a separate service running right now, to help people to easily spread their IPython slides.
If you have an IPython slides worth to be included in the main page, just let me know and I will add it.
+
Note: Slideviewer does not support custom.css from Github (because Github does not serve the css), but you can always use another place to host your .ipynb and custom.css or change the html source code pointing to another url where the css was deployed and served. If you need help with this issue, let me know. I will try to figure out a native solution soon.
+
OK, I hope you find this service useful!
+
See you soon.
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/slideviewer-a-simple-way-to-share-your-ipython-slides.es.html.dep b/cache/posts/slideviewer-a-simple-way-to-share-your-ipython-slides.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/some-thoughts-about-the-2017-acm-software-system-award-for-project-jupyter.es.html b/cache/posts/some-thoughts-about-the-2017-acm-software-system-award-for-project-jupyter.es.html
new file mode 100644
index 00000000..dc022812
--- /dev/null
+++ b/cache/posts/some-thoughts-about-the-2017-acm-software-system-award-for-project-jupyter.es.html
@@ -0,0 +1,32 @@
+
+
+
+
+
+
I am very happy to inform you that Project Jupyter has been awarded the 2017 ACM Software System Award!
+
As part of the Jupyter Steering Council, I am one of the official recipients of the award, but I wanted to highlight that I am just one member of a large group of people (contributors and users) working together to push the Project Jupyter forward and beyond its limits.
+
Project Jupyter is an essential part of my life. It gave me the opportunity to work with amazing people, to learn a lot of new things, to help other people. Some years ago, I left academia for several reasons, but one of the most important ones was to find an opportunity to make a substantial impact on people’s lives. I wanted to be involved in something that could empower people to do amazing things. And I certainly believe that Project Jupyter filled that space and allowed me to achieve that goal more than I could imagine.
+
There are several reasons, but let’s focus on the following:
+
1) Jupyter is explicitly designed for the task of computing interactively
+
Jupyter has become an important part of the daily workflow in research, education, journalism, and industry allowing people to process, analyze, and manipulate data and get insights from it in a fluid, pleasant, and effective way.
+
2) Jupyter fosters communication and collaboration through open standardized formats
+
The open and standardized Jupyter notebook file format is designed to capture, display and share natural language, code, and results in a single computational narrative. This is a key aspect of the scientific and research life cycle. You want to share your findings and thoughts with other people and Jupyter helps with that goal providing a self-contained and powerful computational narrative.
+
The stability and interoperability of open standards also provide a foundation for others to experiment, collaborate, and build tools inspired by their unique goals and perspectives. We have also provided tools to support Jupyter deployment in multi-user environments, making it easier to access common computational resources and share live computational environments. JupyterHub (and Binder) now supports industry deployment, large-scale education and reproducible research.
+
But the most important thing here, as I said before, is the Jupyter Community. IPython and Jupyter have grown to be the product of thousands of contributors and users. We are always seeking to ensure the project is welcoming, supports an increasingly diverse community, and helps solidify a foundation for it to be sustainable.
+
Let’s make it crystal clear: The project exists to serve the community and wouldn’t be possible without you.
+
So, thank YOU for your continuous support, contributions, and feedback!
+
PS
+
On a personal note, I would also like to thank Anaconda, Inc. I have been working here for a long time now and it was/is a great experience. I am grateful for the generous support they provided in building the next Jupyter experience, JupyterLab. And I am also grateful for the continuous support in my involvement with the Jupyter community. I really appreciate that!
Last weekend a big part of the Jupyter team received the announced prize in the ACM 2018 banquet at San Francisco, CA.
+Some pics or it did not happen!
+
+
A better quality one ;-)
+
+
Thanks again to all who contributes to the project!
+
+
+
+
+
+
diff --git a/cache/posts/some-thoughts-about-the-2017-acm-software-system-award-for-project-jupyter.es.html.dep b/cache/posts/some-thoughts-about-the-2017-acm-software-system-award-for-project-jupyter.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/teasers-with-the-ipython-notebook-plugin.es.html b/cache/posts/teasers-with-the-ipython-notebook-plugin.es.html
new file mode 100644
index 00000000..1320856f
--- /dev/null
+++ b/cache/posts/teasers-with-the-ipython-notebook-plugin.es.html
@@ -0,0 +1,21 @@
+
+
+
+
+
+
Just a little tip...
+
You know that Nikola support TEASERS... if not, you can read more about that here:
+teasers_info.
+
In a few words, if you don't want to show the complete content of your posts at the index page, but instead display only the beginning of them, you only need to add a "magical comment" in a markdown cell:
+
+
+
<!-- TEASER_END -->
+
And all the content after this "magical comment" will not be rendered at the index page.
+
In this way, you can avoid the load of "heavy" things at the index and make your site main page loading faster... nice, don't you think?
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/teasers-with-the-ipython-notebook-plugin.es.html.dep b/cache/posts/teasers-with-the-ipython-notebook-plugin.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/trading-logbook-update-22-nov-2013.es.html b/cache/posts/trading-logbook-update-22-nov-2013.es.html
new file mode 100644
index 00000000..6b167f71
--- /dev/null
+++ b/cache/posts/trading-logbook-update-22-nov-2013.es.html
@@ -0,0 +1,113 @@
+
+
+
+
+
+
OK, logging my trades in the forex market, as I promised in the last post.
+
FYI, I am a daily trader, so you will see me holding positions over several days.
+Last week, I performed some real account trades accordingly to my models, opening positions at several currencies pairs. You can see the detailed information in the table below:
+
+
+
+
Ticket
+
Date
+
Transaction
+
Currency Pair
+
Price
+
Relative Balance
+
+
+
+
+
1362844650
+
2013-11-20 23:00:22
+
Close Trade
+
USD/CHF
+
0.91738
+
1.08
+
+
+
1362844642
+
2013-11-20 23:00:16
+
Close Trade
+
EUR/CHF
+
1.23149
+
1.05
+
+
+
1360865177
+
2013-11-19 01:04:03
+
Sell Market
+
AUD/USD
+
0.93788
+
1.05
+
+
+
1360865168
+
2013-11-19 01:03:59
+
Close Trade
+
NZD/USD
+
0.83213
+
1.05
+
+
+
1360033467
+
2013-11-18 02:06:02
+
Buy Market
+
EUR/CHF
+
1.23416
+
1.03
+
+
+
1360033461
+
2013-11-18 02:05:58
+
Buy Market
+
USD/CHF
+
0.91494
+
1.03
+
+
+
1360032042
+
2013-11-18 02:00:11
+
Buy Market
+
AUD/USD
+
0.93982
+
1.03
+
+
+
1360032001
+
2013-11-18 02:00:06
+
Sell Market
+
NZD/USD
+
0.83540
+
1.04
+
+
+
1356809252
+
2013-11-13 21:27:53
+
Sell Market
+
AUD/USD
+
0.93724
+
1.04
+
+
+
1356809209
+
2013-11-13 21:27:47
+
Sell Market
+
GBP/AUD
+
1.71226
+
1.04
+
+
+
+
As you can see, I have yet some open positions because I am waiting to see how these positions evolve over the next week and, obviously, because my models do not signal me to close these trades... yet ;-)
+
As a plus, I have added a new column to the table containing my Relative Balance (because it is not probably a good idea that you know my current balance), and after this week, we have an overall net profit of 8%. You have to take into account that I have set up this account to trade at a high risk profile... so understand this net profit in terms of this high risk.
+
Finally, I have also decided to live tweet the trades from this account, so if you follow me on twitter, you will see these trades on real time, or you can wait to the Fridays when I will post another sheet of this sort of logbook.
+
Good weekend!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/trading-logbook-update-22-nov-2013.es.html.dep b/cache/posts/trading-logbook-update-22-nov-2013.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/trading-logbook-update-3.es.html b/cache/posts/trading-logbook-update-3.es.html
new file mode 100644
index 00000000..2beed1a2
--- /dev/null
+++ b/cache/posts/trading-logbook-update-3.es.html
@@ -0,0 +1,103 @@
+
+
+
+
+
+
OK, I have run my models again and it was time to enter the market.
+
Early today, I opened two positions:
+
+
+
+
Date
+
Transaction
+
Currency Pair
+
Price
+
+
+
+
+
06/26/2017 08:23:35
+
BuyMarket
+
EUR/CHF
+
1.08806
+
+
+
06/26/2017 08:23:31
+
BuyMarket
+
USD/CHF
+
0.97356
+
+
+
+
Update 27-Jun-2017
+
I have opened two more positions:
+
+
+
Date
+
Transaction
+
Currency Pair
+
Price
+
+
+
+
+
06/27/2017 10:02:27
+
BuyMarket
+
EUR/CHF
+
1.08908
+
+
+
06/27/2017 10:02:09
+
BuyMarket
+
USD/CHF
+
0.96524
+
+
+
+
Let's see how things evolve in the next few days.
+
Update 07-Jul-2017
+
Things have evolved, so it was time to close the positions:
+
+
+
Date
+
Transaction
+
Currency Pair
+
Price
+
+
+
+
+
07/7/2017, 3:35:58 PM
+
Close Trade
+
USD/CHF
+
0.96406
+
+
+
07/7/2017, 3:35:58 PM
+
Close Trade
+
USD/CHF
+
0.96406
+
+
+
07/7/2017, 3:35:54 PM
+
Close Trade
+
EUR/CHF
+
1.09948
+
+
+
07/7/2017, 3:35:54 PM
+
Close Trade
+
EUR/CHF
+
1.09948
+
+
+
+
And we are closed in the positive side ;-)
+
Let's see if the model continues to perform well in the next few weeks.
+
Happy trading!
+
+
+
+
+
+
diff --git a/cache/posts/trading-logbook-update-3.es.html.dep b/cache/posts/trading-logbook-update-3.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/tweet-me-said-an-ipython-notebook-cell-and-i-did-it.es.html b/cache/posts/tweet-me-said-an-ipython-notebook-cell-and-i-did-it.es.html
new file mode 100644
index 00000000..490fce65
--- /dev/null
+++ b/cache/posts/tweet-me-said-an-ipython-notebook-cell-and-i-did-it.es.html
@@ -0,0 +1,125 @@
+
+
+
+
+
+
It is time to release some extensions I wrote the last weeks.
+And because it is Friday, and it is a great moment to begin with the "relax" and procrastination, I will release the tweet me extension...
+
+
You don't have any idea what I am talking about? OK, a few words...
+Probably you know that spend a lot of time inside IPython notebooks and I was tired to switch windows to send or answer a tweet. So, I wrote a little js extension to capture the input of the selected cell and tweet it just pressing the twitter icon at the IPython toolbar.
+
+
But this js extension is IPython-powered itself, because I am using the IPython js machinery to execute python files calling the python kernel! Yes... it seems weird, but once you get the idea, you can achieve a lot of things. You can see the relevant part of the code below:
The secret is to use the IPython.notebook.kernel.execute(whatever) method and pass it whatever you want, even IPythonmagics functions! Yes again... too much Inception movie for the last weeks ;-)
+
OK, the extension lives in this new repo: mIPyex, where I will upload the development versions of my own extensions. When I get them enough stable, I will make a copy of them in the IPython notebook extensions repo where you can get a lot of and useful interesting extensions.
+
Do you want to try it?
+It is easy... just follow the README to install all the necessary tools (I used the PTT library to deal with the Twitter API) and then just click the twitter button when you want to share something with the world!
+
Hope you enjoy it a lot!
+
Damián
+
+
+
+
+
+
+
+
+
PD: I will use the next cell to tweet about this new blog post! ;-)
+
+
+
+
+
+
+
+
+
New blog post!
+Tweet me... said an IPython notebook cell and I did it.
+http://goo.gl/ry9Umi
+
+
+
+
+
+
+
+
+
Addendum:
+You can now send tweets from cells with multi-line content (my first implementation only worked with one-line strings).
+
+
+
+
+
+
+
+
+
Addendum 2: You have not only a button but also a keyboard shortcut to activate the Tweet me extension: ALT + T.
+
+
+
+
+
+
diff --git a/cache/posts/tweet-me-said-an-ipython-notebook-cell-and-i-did-it.es.html.dep b/cache/posts/tweet-me-said-an-ipython-notebook-cell-and-i-did-it.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/under-the-sea-en-la-plata.es.html b/cache/posts/under-the-sea-en-la-plata.es.html
new file mode 100644
index 00000000..15515135
--- /dev/null
+++ b/cache/posts/under-the-sea-en-la-plata.es.html
@@ -0,0 +1,101 @@
+
+
+
+
+
+
Han pasado casi tres semanas... El 2 de abril cayeron sobre la ciudad de La Plata casi 400 mm de agua en 24 hs, concentrándose la mayor parte de dicho caudal en dos o tres horas por la tarde, lo que dio lugar a la más grande inundación que la ciudad haya registrado en toda su historia.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Impresionante, no les parece?
+
Lamentablemente, en casa el agua llego a 1,60 mts.
+
Obviamente, la mayoría de las pertenencias quedaron bajo el agua: muebles, electrodomesticos, ropa, biblioteca, documentos, etc.
+
Aca pueden ver la imagen con la que me encontré al día siguiente de la inundación:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Y Lore tratando de esbozar una sonrisa que obviamente enmascaraba una gran tristeza al ver la pieza de Facu en esas condiciones.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Gracias a Dios, no tuvimos que vivir la inundación "in situ" ya que estábamos volviendo de Córdoba (nos habíamos tomado unos días para descansar) en el momento en el que la tormenta se desató con mayor intensidad. Hubiese sido un momento complicadísimo, probablemente subiendo al techo con Facu a cuestas... mejor no imaginarlo, o si... para estar preparado.
+
Hemos podido salvar algunos muebles, algunos electrodomésticos, muchas fotos y la mayoría de la ropa y el calzado. Pero hemos pérdido otras tantas cosas, por ejemplo, la biblioteca, muchos documentos y las computadoras.
+
Ya han pasado tres semanas desde la tormenta, y aún no pudimos volver a casa. Los hongos se hacen un festín en estas situaciones y todavía quedan algunos creciendo en las paredes a pesar de la limpieza a diario. Probablemente estemos volviendo a fines de esta semana.
+
Y después... viene la recontrucción, la albañilería, la pintura, arreglar estufas, etc y comprar todo lo que se perdió y es necesario para la vida diaria. Para los arreglos, todas las manos son bienvenidas, jeje...
+
Quisiera aprovechar este espacio para agradecer a todos aquellos que se preocuparon por nosotros. A todos aquellos que nos dieron una mano, no sólo física, poniendo el hombro a la hora de la limpieza, sino también dándonos su apoyo constante:
+
+
Melisa, Diego y Flavio.
+
Romi y las hijas de Lore: Clarita y Marina.
+
Cintia y Pedro.
+
Michelle y Lucas.
+
Todo el grupo de amigos del IBYME: Xime, Carito, Norber, Evan, Andre, Nico, Ger, Mer, Gaby y los Galectinos.
+
David y la gente del LISIN.
+
La gente de PyAr: Martin Gaitán, Fisa, entre otros.
+
y muchos más que no estoy nombrando, pero que también estuvieron atentos para subsanar cualquier necesidad.
+
+
Y unos últimos agradecimientos adicionales:
+
+
Papi y Mami, que siempre están al pie del cañon.
+
Dan, gracias por estar pendiente en todo momento... y por ser un apoyo constante.
+
Lore, que puedo decir que no te haya dicho... Gracias por aguantarme, por apoyarme, por todo tu esfuerzo y sacrificio.
+
Facu, gracias por existir y ser el sol que alumbra y alumbrará todos mis días.
+
+
Gracias totales!
+
Nos vemos en el próximo post!
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/under-the-sea-en-la-plata.es.html.dep b/cache/posts/under-the-sea-en-la-plata.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/using-a-local-revealjs-library-with-your-ipython-slides.es.html b/cache/posts/using-a-local-revealjs-library-with-your-ipython-slides.es.html
new file mode 100644
index 00000000..83131288
--- /dev/null
+++ b/cache/posts/using-a-local-revealjs-library-with-your-ipython-slides.es.html
@@ -0,0 +1,78 @@
+
+
+
+
+
+
IPython slides are powered by Reveal.js library, you probably already know that.
+
But... you probably don't know that we use jsdelivr CDN to load all the necessary js and css files. As a consequence, you don't need to download Reveal.js, but also, the speaker notes are not working by default.
+
But... what happens, if you have low connectivity in the place where you will be presenting your talk (or if you want to use the speaker notes feature)?
+
+
In this case, it would be better to use a local copy of the Reveal.js library. And you can easily configure this behavior using a config object from the IPython machinery.
+
Below, you have one way to do it:
+
+
+
+
+
+
+
In [1]:
+
+
+
fromIPython.nbconvert.exportersimportSlidesExporter
+fromIPython.configimportConfig
+
+fromIPython.nbformatimportcurrentasnbformat
+
+infile="talk.ipynb"# load the name of your slideshow
+outfile="talk.slides.html"
+
+notebook=open(infile).read()
+notebook_json=nbformat.reads_json(notebook)
+
+# This is the config object I talked before:
+# After the 'url_prefix', you can set the location of your
+# local reveal.js library, i.e. if the reveal.js is located
+# in the same directory as your talk.slides.html, then
+# set 'url_prefix':'reveal.js'.
+
+c=Config({
+ 'RevealHelpTransformer':{
+ 'enabled':True,
+ 'url_prefix':'reveal.js',
+ },
+ })
+
+exportHtml=SlidesExporter(config=c)
+(body,resources)=exportHtml.from_notebook_node(notebook_json)
+
+open(outfile,'w').write(body.encode('utf-8'))
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
Then, just serve the directory:
+
python -m SimpleHTTPServer 8000
+
open the browser and point it to http://localhost:port, ie:
+
xdg-open http://127.0.0.1:8000
+
OK, that's all... you don't need connectivity anymore ;-) OK, just kidding... he he!
+
NOTE: If you are using master, it is even simpler... because now --post serve post-processor uses tornado to forward requests to the CDN if and only if local Reveal.js is unavailable (PR merged here, thanks MinRK). So, just locate the reveal.js in the same directory as your talk.slides.html lives and run (as usually):
+
+
diff --git a/cache/posts/using-a-local-revealjs-library-with-your-ipython-slides.es.html.dep b/cache/posts/using-a-local-revealjs-library-with-your-ipython-slides.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/viper-is-now-using-ipythonnbconvert.es.html b/cache/posts/viper-is-now-using-ipythonnbconvert.es.html
new file mode 100644
index 00000000..adc6b3a8
--- /dev/null
+++ b/cache/posts/viper-is-now-using-ipythonnbconvert.es.html
@@ -0,0 +1,69 @@
+
+
+
+
+
+
As you know (if not, probably the following lines gives you an idea), vIPer was originally designed to export from ipynb files to:
+
+
a plain static html
+
a slideshow powered by Landslide
+
+
With the last release, IPython support this kind of exportation using the well designed and easily extensible IPython.nbconvert library. Now, it is easier to incorporate the IPython machinery inside vIPer and support the exportation to several formats.
+
+
Note: if you want to know more about vIPer, just see the following talk I gave about it at SciPy 2013.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Up to now, I have replaced the old converters by the new ones: the HTMLExporter and the SlidesExporter from IPython.nbconvert. As a consequence, vIPer now supports the generation of IPython slides (deprecating the use of Landslide to get the html-powered slideshow... thank you very much to the Landslide developers for their work... and to make my life easier at the first days of vIPer).
+
Remarkably, trying to serve the IPython slides inside vIPer was very educational, because IPython.nbconvert already supports the serve of the resulting slides, so I tried to use this functionality and, because I needed to work in parallel, this led me to work a little bit with QtCore.QThreads.
It is important to highlight that I needed to call the start() method to run the run() method from the ServeThread class.
+
And now, vIPer support serving the IPython slides automatically after the conversion step with just a click of a button.
+
OK, just try vIPer (Github repo) and let me know any bug... and I hope you find the Qt-derived threads information useful, or at least, interesting! ;-)
+
Damián
+
+
+
+
+
+
diff --git a/cache/posts/viper-is-now-using-ipythonnbconvert.es.html.dep b/cache/posts/viper-is-now-using-ipythonnbconvert.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/viper.es.html b/cache/posts/viper.es.html
new file mode 100644
index 00000000..ee0c9b82
--- /dev/null
+++ b/cache/posts/viper.es.html
@@ -0,0 +1,13 @@
+
vIPer es una aplicación específicamente diseñada para trabajar
+con los notebooks the IPython.
+
Es un proyecto que he estado desarrollando durante las últimas semanas...
+
A continuación, pueden ver un video en el cual demuestro una de mis funciones predilectas:
+la posibilidad de tener una vista "presentación" para el notebook con el cual estoy trabajando
+(súper útil a la hora de exponer resultados o preparar charlas, por ejemplo).
+
+
Iba a darlo a conocer en SciPy US 2012, pues me habían aceptado la charla. Sin embargo,
+lamentablemente, no fuí elegido para una de las becas que la conferencia otorgaba
+(y Texas está medio lejos, vió...), así que, muy probablemente, lo presente en la próxima PyConAr.
+
Obviamente, vIPer estará disponible muy pronto...
+
Nos vemos.
+
Damián.
diff --git a/cache/posts/viper.es.html.dep b/cache/posts/viper.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/we-are-above-1000-stars.es.html b/cache/posts/we-are-above-1000-stars.es.html
new file mode 100644
index 00000000..d41de4f0
--- /dev/null
+++ b/cache/posts/we-are-above-1000-stars.es.html
@@ -0,0 +1,21 @@
+
+
+
+
+
+
Github has a way to measure projects popularity through stars.
+
And those stars are given by the users themselves.
+
And we are just above a remarkable line...
+
+
+
As you can see below (or in the RISE github repo):
+
+
We are above 1000 stars!!!
+
I just want to give a big THANK YOU to all the RISE users out there.
+
See you soon!
+
+
+
+
+
+
diff --git a/cache/posts/we-are-above-1000-stars.es.html.dep b/cache/posts/we-are-above-1000-stars.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/zen-mode-extension-for-the-ipython-notebook.es.html b/cache/posts/zen-mode-extension-for-the-ipython-notebook.es.html
new file mode 100644
index 00000000..9c44a948
--- /dev/null
+++ b/cache/posts/zen-mode-extension-for-the-ipython-notebook.es.html
@@ -0,0 +1,67 @@
+
+
+
+
+
+
I write a lot stuff inside the IPython notebook.
+
And I thought it would be great to have a sort of Zen mode for the notebook...
+
I mean, a peaceful user interface to write my blog posts (and other stuff, of course).
+
So I wrote a little js extension which give me this Zen mode.
+
You can see some screen shots below:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
And a little video showing the extension in action:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Do you want it? You can get it!
+
It is available inside the IPython-notebook-extensions repo under the IPython-contrib organization [1].
+
In the custom.js file you can select which background image do you want to use (there are some available inside the extension, but you can also use your own image ;-)).
+
Enjoy it!
+
Damián
+
PS: As usual, open any issue (bug or idea) at the Github repo (or report me here at the comments). Thanks!
+
+
diff --git a/cache/posts/zen-mode-extension-for-the-ipython-notebook.es.html.dep b/cache/posts/zen-mode-extension-for-the-ipython-notebook.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/posts/zen-themes-updated.es.html b/cache/posts/zen-themes-updated.es.html
new file mode 100644
index 00000000..e5bf945c
--- /dev/null
+++ b/cache/posts/zen-themes-updated.es.html
@@ -0,0 +1,166 @@
+
+
+
+
+
+
OK, time to recap some things... As you know, Nikola 7.0.0 was released some weeks ago. It has a lot of improvements, bug fixes and new features. I recommend you to download and try it!
+As part of the release, we paid attention to update all the plugins and themes inside the Nikola Github organization (don't forget you can contribute with your own plugins and themes!). So, I updated my own themes, in particular, the Zen ones.
+
+
As you also now, IPython 2.x was released just some weeks ago too. So, I took into account this two releases and updated the Zen themes to be compatible with both of them.
+As a consequence of the update, the zen-ipython theme has change a little bit, some bugs were fixed and some features enabled. You can probably has noticed that if you visit my blog in the last two weeks. If you did not notice, first, buy some glasses ;-), and then, take a tour, visit some of my old posts (there are interesting new comments every week) and enjoy the new theme.
+
And... don't forget! You can get the Zen themes very easily. First, to list all the available themes at the Nikola themes repo:
Of course, don't use the ! at the beginning of the line if you are outside IPython.
+
To install one of them, just write:
+
+
+
+
+
+
+
In [2]:
+
+
+
!nikola install_theme zen-ipython
+
+
+
+ Click me to hide the output
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
[2014-05-30T18:28:23Z] WARNING: Nikola: Cannot load theme "zen-ipython", using 'bootstrap' instead.
+[2014-05-30T18:28:24Z] INFO: install_theme: Downloading: http://themes.getnikola.com/v7/zen-ipython.zip
+[2014-05-30T18:28:24Z] INFO: install_theme: Extracting: zen-ipython into themes
+[2014-05-30T18:28:24Z] NOTICE: install_theme: This theme has a sample config file. Integrate it with yours in order to make this theme work!
+Contents of the conf.py.sample file:
+
+ NAVIGATION_LINKS = {
+ DEFAULT_LANG: (
+ ('/index.html', 'Home', 'icon-home'),
+ ('/archive.html', 'Archives', 'icon-folder-open-alt'),
+ ('/categories/index.html', 'Tags', 'icon-tags'),
+ ('/rss.xml', 'RSS', 'icon-rss'),
+ ('http://getnikola.com', 'About me', 'icon-user'),
+ ('https://twitter.com/getnikola', 'My Twitter', 'icon-twitter'),
+ ('https://github.com/getnikola', 'My Github', 'icon-github'),
+ )
+ }
+
+[2014-05-30T18:28:24Z] INFO: install_theme: Downloading: http://themes.getnikola.com/v7/zen-jinja.zip
+[2014-05-30T18:28:26Z] INFO: install_theme: Extracting: zen-jinja into themes
+[2014-05-30T18:28:26Z] NOTICE: install_theme: This theme has a sample config file. Integrate it with yours in order to make this theme work!
+Contents of the conf.py.sample file:
+
+ NAVIGATION_LINKS = {
+ DEFAULT_LANG: (
+ ('/index.html', 'Home', 'icon-home'),
+ ('/archive.html', 'Archives', 'icon-folder-open-alt'),
+ ('/categories/index.html', 'Tags', 'icon-tags'),
+ ('/rss.xml', 'RSS', 'icon-rss'),
+ ('http://getnikola.com', 'About me', 'icon-user'),
+ ('https://twitter.com/getnikola', 'My Twitter', 'icon-twitter'),
+ ('https://github.com/getnikola', 'My Github', 'icon-github'),
+ )
+ }
+
+[2014-05-30T18:28:26Z] NOTICE: install_theme: Remember to set THEME="zen-ipython" in conf.py to use this theme.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
and your theme will be available at the themes folder in your site.
+
OK, short post for today, more coming soon.
+
Damián.
+
+
+
+
+
+
diff --git a/cache/posts/zen-themes-updated.es.html.dep b/cache/posts/zen-themes-updated.es.html.dep
new file mode 100644
index 00000000..e69de29b
diff --git a/cache/stories/about-me.es.html b/cache/stories/about-me.es.html
new file mode 100644
index 00000000..dc0c6630
--- /dev/null
+++ b/cache/stories/about-me.es.html
@@ -0,0 +1,43 @@
+
I'm a "data scientist", but also a biochemist (currently finished a PhD program in a biological science: Immunology, you can see my biological CV clicking here) from the U.N.L.P. - Buenos Aires, Argentina. I'm also a TA in Immunology courses at U.N.L.P. and I taught biostatistics courses at the Colegio de Bioquímicos - Colegio Zonal XII - Buenos Aires. I'm a member of Python Argentina (PyAr) [1] and Quantitative Finance Club (QFClub) [2].
+
My main focus is the quantitative financial time series research and analysis using Python as the main computational tool. But, I also develop several data science, computer vision, and IPython-related projects.
+
Recently, I have presented talks and posters in several international and national conferences:
In the open development area, I can list the following projects:
+
+
IPython plugin for NINJA-IDE, which gives IPython notebook support to this IDE (written and focused in Python) [20].
+
vIPer (based in the plugin described before), an independent application with several features focused to the visualization and publication of the IPython notebooks [21].
+
+
and also some contributions to other projects:
+
+
IPython project, with development ideas, specially in the nbconvert repository, providing support for the generation of static html-slideshows from IPython notebooks [22 - 23(demo)].
+
Nikola, a static site generator, providing support for publishing posts with IPython notebooks, a "smart" mathjax loader and a new reveal.js-based theme [24 - 25].
+
+
+
+
+
+
+
