Author here. A friend mentioned this was on the front page so I wanted to stop by and make explicit that this advice is OUT OF DATE as far as I'm concerned. It's way too much hassle (I work in a much larger team now than I did then!) and doesn't play well with rebase etc.
These days I either recommend the jupytext approach (not tried it but seems sensible) or personally I just use Sphinx-gallery.
Advantages:
* Plain python files play well with IDE refactoring, Black formatter, etc etc.
* You now have a readymade 'tutorial' page for your docs.
* Files are run with every docs build, so you can configure things to alert you when they're broken.
Disadvantages:
* You end up editing a throwaway notebook file. If you forget to copy-paste your edits back to the source, and rebuild, you have lost your edits. However, this forces me to keep the 'temporary, exploratory' nature at the front of my mind and not allow the notebook code to grow too large before performing some clean-up.
Things are changing, slowly but surely. Those of you interested in this sort of work should check out http://rse.ac.uk/, and also https://software-carpentry.org/ (Run a workshop! Improve the software environment around you!)
This is something I've been giving some thought to recently. I came to the conclusion that the best way to go currently is git-clean filters built using jq. It's still a bit hacky though. Gentle write-up here: http://timstaley.co.uk/posts/making-git-and-jupyter-notebook...
While I see what you're saying, I doubt you would claim to 'use' assembly when writing a C++ codebase - because (unless you're doing very low-level hand optimizations of the kind that get ever rarer), someone else has done the hard work of creating a compiler to do the translation for you. Same thing with NumPy et al, except one level higher up the abstraction stack.
Interesting dilemma. I had assumed that re-writing in another language basically meant you were copyright free (as long as you're not literally transcribing or automatically translating), but it appears it's not that simple: http://imranontech.com/2006/12/04/are-algorithms-copyrightab...
It'll be a bit more expensive than your local store, but you could try ordering (decaf) beans online. Weirdly this seems to be a much bigger thing over here in the UK, but I did find this: http://dailygrind.com/index.php?cPath=22_27
tl;dr: A competitor to Virgin Galactic (space tourism) using what appears to be a more traditional booster rocket / parachute pod arrangement - except that the booster rocket self-lands after separation. Interesting to see another competitor in the space industry!
I disagree about this being worse for beginners - if we're teaching a new programmer about functions, surely a basic print function is a great introduction? Whereas before it was a one-off special case.
While I'll be interested to see how the blockchain gets exploited for new tech, there are a couple of problems with your statement. First, right now there is a problem with how we generate energy, and a centralized banking system should be a lot more efficient in that regard, for all its other flaws - Bitcoin relies on the calculations being difficult and therefore compute/energy intensive, after all. Second, even if we had perfectly clean energy generation, there is a limit to how much we can use unless we get into really crazy future tech like exhausting energy into space via refrigerant/laser system: see http://physics.ucsd.edu/do-the-math/2012/04/economist-meets-.... (also the `Sundiver' sci-fi!).
Interesting, I wondered if anyone else was playing with XFCE config this way. I have the important parts of my .config/xfce4 folder under git and replicated across 3 machines, which a branch for dual-screen tweaks on the desktop, etc. etc. I thought it was so cool that you can just figure this stuff out and get on with it!
Steuard is right, and astronomers have good reasons to expect this behaviour - wave dispersion. The best link I can find from a quick google is this:
http://en.wikipedia.org/wiki/Dispersion_(water_waves)
-which refers specifically to dispersion of water (typically, ocean) waves, but the concepts are the same.
(Edited to add) We expect dispersion effects in the case of fast radio bursts due to effects of propagation through the interstellar medium. Not my area of expertise, but see http://arxiv.org/abs/1310.8316 if you want a properly referenced starting point.
The raw representation is a somewhat cluttered (to the untrained eye, anyway) json file - especially if you have checkpointed images which are bascially base64 encoded blobs! So as far as I know it's pretty much the web-editor or nothing at the moment. Obviously a JSON-aware plug-in for something like PyDev or Pycharm would be pretty neat, but I think we're a ways off that. See also http://nbdiff.org/ which solves the issue of comparing version-tracked notebooks.
Author here. A friend mentioned this was on the front page so I wanted to stop by and make explicit that this advice is OUT OF DATE as far as I'm concerned. It's way too much hassle (I work in a much larger team now than I did then!) and doesn't play well with rebase etc.
These days I either recommend the jupytext approach (not tried it but seems sensible) or personally I just use Sphinx-gallery.
Advantages:
* Plain python files play well with IDE refactoring, Black formatter, etc etc.
* You now have a readymade 'tutorial' page for your docs.
* Files are run with every docs build, so you can configure things to alert you when they're broken.
Disadvantages:
* You end up editing a throwaway notebook file. If you forget to copy-paste your edits back to the source, and rebuild, you have lost your edits. However, this forces me to keep the 'temporary, exploratory' nature at the front of my mind and not allow the notebook code to grow too large before performing some clean-up.