[jupyter] Re: Formalizing preparing a release

2017-02-09 Thread Steven Silvester
I like the idea of handling the tracking and coordination on the https://github.com/jupyter/project-mgt and having a snapshot in the weekly dev meeting report as well. On Wednesday, February 8, 2017 at 9:12:24 PM UTC-6, Matthias Bussonnier wrote: > > Hello all, > > It recently came to the

Re: [jupyter] Formalizing preparing a release

2017-02-09 Thread Brian Granger
I am definitely in favor of this. We have millions of users, with many of them organizations, universities, non-profits, researchers, etc. who are relying on our software and building on top of it. So, in addition to our own developers needing to know about and discuss releases, we also have a

Re: [jupyter] Formalizing preparing a release

2017-02-09 Thread Carol Willing
It would be a good idea to include a tentative release calendar at the bottom of the weekly development update that Matthias has been helpfully sending to this list. Capturing information in a release planning table would be beneficial; it would have been hugely helpful last year for planning

Re: [jupyter] Formalizing preparing a release

2017-02-09 Thread Jason Grout
I think announcing and coordinating major (and probably even minor) releases in the way that Matthias outlines is a great idea. I agree with Thomas that bugfix releases should be easier and more frequently released. On Thu, Feb 9, 2017 at 6:53 AM Thomas Kluyver wrote: > On 9

Re: [jupyter] Formalizing preparing a release

2017-02-09 Thread Thomas Kluyver
On 9 February 2017 at 03:12, Matthias Bussonnier < bussonniermatth...@gmail.com> wrote: > For example, several developers were surprised yesterday with the > announcement of an upcoming notebook 5.0 release, and are now > struggling to catch up on what is new and to test their >

Re: [jupyter] Unicode Greek letters in matplotlib images with nbconvert's python API

2017-02-09 Thread Thomas Kluyver
On 8 February 2017 at 23:58, Paul Hobson wrote: > nbdata = nbformat.read(nbf, as_version=4, encoding='utf-8') For reference, I'm pretty sure that passing encoding= on this line has no effect - it's not passed down to anything that takes an encoding argument. Passing it to

Re: [jupyter] Getting the port number in an IPython noteboook

2017-02-09 Thread Johannes Feist
Hi DG, I see, I didn't get that your analysis is interactive in the first part. While I'm not a Jupyter developer, I think what you want could be achieved with some Javascript more easily. If you make a cell with %%javascript var nb = Jupyter.notebook; nb.save_checkpoint();