Re: [jupyter] Possibility to separate the JupyterLab Web and Server

[Brian Granger]

What you are describing is possible, but there are a set of
constraints and trade-offs that may not give the experience you want.
Colab faces these same constraints and tradeoffs.

* JupyterLab/classic Notebook have a range of different service APIs -
kernels, contents (file/dirs), terminals, kernel specs (kernel
metadata), etc. The standard way of operating Jupyter is to deploy all
of these services in the same server, and to also serve the frontend
JS/HTML/CSS from that same server. In the abstraction, the
architecture certainly allows you to deploy different services on
different servers. However in practice, it is probably not what you
want to do. The reason is that the different services have coupling
that directly relates to the overall usability:

* Kernels and the file system are coupled, as a kernel needs to see
the same file system - to import other files sitting next to the
notebook, and to access co-located data files. So you can run the
kernel service separately, but it won't be useful for real work unless
you also figure out how to mount the same file system for that kernel.
* Terminals and the file system are coupled as users typically want to
see the real file system in the terminal.
* The frontend and kernels also have a coupling, because many kernel
libraries require frontend extensions to be installed.

These are exactly the tradeoffs made by colab, and they severely
limits its usefulness for real work. But I do think these trade offs
do make sense for some usage cases. Right now, the code base isn't
optimized for this more decoupled usage case, but we have different
efforts moving in this direction.

There is work to separate out the jupyter server and de coupled its
components here:

https://github.com/jupyter/jupyter_server

Unless I am misunderstanding your question, I don't think you are
looking to make changes to the frontend though - so I think the stock
JupyterLab or classic notebook would work fine. What you want is a
different way of factoring the server side of things. Probably the
most flexible way of refactoring the server would be to begin to use
the components of jupyter server, running in separate containers,
managed by something like docker compose with a traefik reverse proxy
in front. I would love to see explorations along these lines.

I should also note that the Jupyter enterprise gateway might help in this work:

https://github.com/jupyter/kernel_gateway

Hope this helps!

On Sat, Apr 27, 2019 at 1:50 AM Song Liu  wrote:
>
> Hi,
>
> Just like the Google Colab user experience, is that possible to separate the 
> JupyterLab Web and Backend ?
>
> That is the notebook viewing and editing functionality could be provided by 
> the JupyterLab web service just with minimum resource consumption.
> When running the Python code it could send it to a remote JupyterLab backend 
> (Server and Kernel).
>
> Thanks,
> Song
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/d9872648-8909-4ad8-84f7-853ae8c81460%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTTtNK71w9ewRvO_OeyXUg6u3HV5smUMQpnsFC8Cg%3DP%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Papermill 1.0 Released

[Brian Granger]

Many congrats to everyone who worked on this release of Papermill. I
am also excited to see nbconvert moving forward as part of this as
well, with widgets support, better LaTeX templates, execution
improvements, etc.

:-)

Cheers, Brian

On Thu, Apr 25, 2019 at 3:29 PM Matthew Seal  wrote:
>
> Papermill 1.0!
>
> After over a year of development and community growth, our targets we came up 
> with for feature completeness both in papermill and in upstream repositories 
> are all completed now. You can read the main milestone targets here. But at a 
> high level over the past several minor releases, we created scrapbook to 
> replace papermill's record and collection capabilities, upped test coverage 
> above 90%, made every component of papermill registerable for platform / user 
> extensions, added support for multiple cloud vendor io schemes, and hardened 
> upstream repositories like nbconvert.
>
> The release of 1.0 is tied to finalizing these initial goals to indicate we 
> have have feature completeness and no known major deficiencies in the code 
> base moving forward. We're happy to have new contributors and ideas in 
> tackling the next phase of improvements to the library, so don't feel shy to 
> poke around and see what you think should be added!
>
> Specific changes in 0.19.1 to 1.0.0 are as follows:
>
> Input and output paths can now reference input parameters. 
> `my_nb_{nb_type}.ipynb out_{nb_type}.ipynb -p nb_type test` will substitute 
> values into the paths passed in with python format application patterns.
> `read_notebook`, `read_notebooks`, `record`, and `display` api functions are 
> now removed.
> [from nbconvert 5.5] ipywidgets are now supported. See nbconvert docs for 
> details.
> [from nbconvert 5.5] notebook executions which run out of memory no longer 
> hang indefinitely when the kernel dies.
>
>
> Enjoy the changes and thanks for everyone's help getting here.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CAJF6vz5Bu7R7Vgon9XcO4s-EVtfM4dAT6s1_huUKG5J2G4rfhg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpS17LFnz-TtNRUjb4xVVjAvK6npu-az%3DeSd8xM%2BjW-LKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter Kernel Gateway 2.2.0 and NB2KG 0.5.0 are available

[Brian Granger]

Congrats Kevin!

On Tue, Feb 26, 2019 at 4:17 PM Kevin Bates  wrote:

> The combination of these releases essentially enable the serving of
> kernelspec resource files (primarily kernel icons) that wasn't available
> previously.
>
> NB2KG  is a Jupyter Notebook server
> extension that enables the Notebook server to use remote kernels hosted by
> a Jupyter "Gateway" (i.e., Kernel Gateway or Enterprise Gateway) - enabling
> a *bring-your-own-notebook* paradigm.  It has recently been embedded into
> the Notebook application so we expect this repository to move to a
> sustaining role shortly.
>
> Jupyter Kernel Gateway  is a
> headless web server built on Notebook that exposes the management of
> Jupyter kernels on a shared server.
>
> Jupyter Enterprise Gateway  
> extends
> JKG and manages kernels distributed across resource-managed clusters.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/c9e0399f-ccb9-40d6-b90d-21195886350e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQ-S2sOhETE%3DFJpxmq2vp%3DdjUzZGY0P%3D-4Og7EmovEhDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] JVM Magics

[Brian Granger]

Great news, thanks for sharing!

On Thu, Feb 21, 2019 at 5:20 PM Kyle Kelley  wrote:

> Hey all,
>
> A couple weeks ago a bunch of Scala kernel maintainers came together
> during the Notebook Enterprise Summit .
> One of the topics of discussion was making consistent magics across the
> various Scala & JVM kernels. Notes and proposals are here:
> https://github.com/nteract/nes/tree/master/jvm-kernel-magics
>
> Ryan Blue created jvm-magics as a result of this:
> https://github.com/rdblue/jvm-magics
>
> Please check it out if you're interested and post issues. When ready, we'd
> love to see this land in the jupyter org to support similarly to jvm-repr.
>
> --
> Kyle Kelley (@rgbkrk ; lambdaops.com)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CA%2BtbMaUOfo5c_ubJzEcA55TYwmTziS4OTs9VT38ndULp-iQZdA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQk5ypjHsNUpscQG_464Yc1AURCh3VQ4Y0bD22coFp%2B%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] nbformat: Removing code to read XML notebook files

[Brian Granger]

+1

On Mon, Feb 11, 2019 at 1:41 PM Matthew Seal  wrote:

> I'm 100% for removing -- I can't think of any recent tools that even
> support xml. Thanks for making the PR!
>
> On Mon, Feb 11, 2019 at 7:01 AM Thomas Kluyver  wrote:
>
>> Hi all,
>>
>> Way back in 2011, when the first version of the IPython Notebook was
>> being written, there was an option to store notebooks as XML. JSON was
>> chosen as the default, and has always been the format all of our
>> applications use. However, the code to read XML files stayed around, and
>> recently Danor Cohen pointed out that it is vulnerable to denial of service
>> attacks.
>>
>> I am proposing to *remove this code* rather than maintain it. None of our
>> applications call it, and I'm not aware of anyone else using it. The XML
>> format is, as far as I know, an abandoned concept.
>>
>> If you are using that code (nbformat.v2.*_xml), and you can't practically
>> move away from it, now would be a good time to take over maintenance of it.
>> ;-)
>>
>> The removal PR is here: https://github.com/jupyter/nbformat/pull/133
>>
>> Thanks,
>> Thomas
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAOvn4qh_0JMrZTLweN21eTxKX54q6uy7O%2BErWc6i2PQ8f3r3BA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAJF6vz7pOa0DAP%3DKxjhbHUtA4T5ZG1f3jDoduQhj-GywVvK22w%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRKyEKjuNkQ-QR43%3D72cp3AEAt14Fq1Kn8hvYBNXoEDNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: Javascript Extension to enable arbitrary control of JupyterLab

[Brian Granger]

I agree with Grant that the preferred way of doing this would be to use the
JupyterLab command system.  You could write a mime renderer that takes JSON
data and runs corresponding command. Then you don't have to send it
JavaScript code over the wire.

On Fri, Nov 30, 2018 at 9:17 AM Grant Nestor  wrote:

> Hi Florian,
>
> This certainly was one nice thing about classic notebook: the global
> `jupyter` variable.
>
> If you run JupyterLab in dev-mode, you get a global `window.lab` variable
> that gives you a handle on the application. This is a good starting point.
> To add a new cell, you can call
> `window.lab.commands.execute('notebook:insert-cell-below')`. You can call
> that in the browser console or in a cell:
>
> ```py
> %%js
> window.lab.commands.execute('notebook:insert-cell-below')
> ```
>
> If you want to run a cell:
> `window.lab.commands.execute('notebook:run-cell-and-select-next')`
>
> You can find these commands by searching the command palette and then
> searching the jupyterlab source code for the command title.
>
> Another relevant project is jyve which gives you several custom Jupyter
> JS-based kernels that expose JupyterLab internals outside of dev-mode:
> https://github.com/deathbeds/jyve
>
> We are weary to expose this outside of dev-mode by default because of the
> consequences that running arbitrary code could have on the user's lab
> environment and system. We could consider adding a setting to the
> javascript-extension allowing users to override this behavior so that it's
> not default but possible.
>
> Feel free to open an issue on the jupyterlab repo.
>
> Grant
>
> On Friday, November 30, 2018 at 3:16:09 AM UTC-6, Florian Wetschoreck
> wrote:
>>
>> Hi,
>>
>> there are good reasons why currently it is not allowed to execute
>> arbitrary Javascript in JupyterLab.
>> Also, there is a fix with the javascript extension package which exposes
>> the window, document and element objects.
>> https://github.com/jupyterlab/jupyterlab/pull/4515
>>
>> However, we need access to more (internal) objects if we want to add
>> cells or execute cells etc
>>
>> Therefore, I want to extend the current Javascript extension package to
>> expose even more context for users who know what they are doing.
>> The goal is to have another more powerful javascript extension which
>> exposes all relevant objects to fully manipulate JupyterLab without having
>> to go through the process of writing a custom extension.
>>
>> Do you have any advice on this endeavor? For example: *which objects to
>> expose?*
>> How to install the extension without interfering with the existing
>> javascript MimeRenderer. Or maybe: how to overwrite the existing Javascript
>> MimeRenderer. Is it possible to have both side by side? eg to import
>> Javascript and/or JavascriptFullAccess from IPython.display
>>
>> Any help is highly appreciated.
>>
>> Florian
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/e456cda7-901a-4d3d-a764-9078ff9fd68a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSsL3cYR-4s_1kyZ1-s-59DzTnjXxoudXHUixCGhw0RpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] How to authenticate same domain users from multiple OUs with ldapauthenticator?

[Brian Granger]

Something like keycloak could be helpful with things like this:

https://www.keycloak.org/

We have used it with JupyterHub successfully.

On Sun, Sep 23, 2018 at 7:18 PM Raymond Xie  wrote:

> Hi MinRK, everyone,
>
> Is it supported to authenticate same domain users from multiple OUs with
> ldapauthenticator?
>
> My config is as below and both two option are not working:
>
> c.LDAPAuthenticator.user_search_base = '(ou=ABC
> Users,dc=abc,dc=pri)|(ou=ABC Users (System),dc=abc,dc=pri)'
> #c.LDAPAuthenticator.user_search_base = 'ou=ABC Users|ou=ABC Users
> (System),dc=abc,dc=pri'
>
> We want to use a dedicated account which belongs to ABC Users (System) ou
> while all the regular user accounts belong ABC Users ou.
>
> Thank you very much.
>
>
> https://github.com/jupyterhub/ldapauthenticator/issues/102
> **
> *Sincerely yours,*
>
>
> *Raymond*
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAKZNNLJpB7YHsL28gbKPueE50Mcq5HigGyydKGfCvD_9GdSpPA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQaE2EXpA%2B4XEMKdTYK5CvYbOdojZo2FM1LdmdCHF6K%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: [IPython-dev] [ANN] Release of IPython 7.0 – you've awaited long enough

[Brian Granger]

Congrats to the entire team!

On Fri, Sep 28, 2018 at 11:29 AM Wes Turner  wrote:

>
>
> On Friday, September 28, 2018, Wes Turner  wrote:
>
>>
>> The new asyncio docs also look great and will likely be helpful for
>> learning async/await:
>>
>> New (3.7):
>> https://docs.python.org/3/library/asyncio.html
>>
>> Old (3.6)
>> https://docs.python.org/3.6/library/asyncio.html
>>
>
> “IPython 7.0, Async REPL” @Mbussonn
> https://blog.jupyter.org/ipython-7-0-async-repl-a35ce050f7f7
>
> > If you want to learn more we strongly recommend reading the Trio
> Tutorial Primer on async programming.
>
> https://trio.readthedocs.io/en/latest/tutorial.html
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CACfEFw_Mx8MZ%3DuqzgphW17tz%2BPCc8jPz7XGrpCs9a-o4SX%3DKxw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpR80Pkdu7HYCfH%2Badd5w7daxnM6R1OJAa%3DTdHABLfEu%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: commenting on someone else's Jupyter Notebook

[Brian Granger]

That poster is part of a new grant we have funded to work on commenting and
annotation in JupyterLab. It is just getting started, but there will be
activity related to this on GitHub as things begin to move forward.

On Fri, Sep 21, 2018 at 7:58 AM Colin Rowat  wrote:

> Thank you Jason and David.
>
> An abstract of the paper mentioned by David is available here:
> https://conferences.oreilly.com/jupyter/jup-ny/public/schedule/detail/71539
> .
>
> On Friday, September 21, 2018 at 9:42:33 AM UTC+1, Colin Rowat wrote:
>>
>> I am beginning to use Jupyter Notebook.
>>
>>
>> I want students to comment on each other's Notebooks as part of a
>> validation exercise.
>>
>>
>> I know how to insert markdown, etc., but have not found any 'automatic'
>> way to identify a comment's author. For example, comments that I insert in
>> an MS Word document are prefaced with my initials.
>>
>>
>> Does anyone know if there is such a feature, or whether an author needs
>> to manually enter their identify?
>>
>>
>> Thank you,
>>
>>
>> Colin
>>
>>
>> p.s. I've also posted this question at stackoverflow, at
>> https://bit.ly/2QNZYeg
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/08398caa-2146-48ca-baf7-467dd11192f4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSq8%2Be6oTB8JVMAKQb%2BiWiLNN5EBb6mJoTLa-i%3Dpj6zZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupytercon 2018 Conference Videos -- Where are the rest of them?

[Brian Granger]

It is part of our agreement with O'Reilly that full videos of all keynotes
and sessions will be posted publicly on YouTube.

What William said is correct - they are highly "produced" so it takes a
while for them to get them posted. I recall them saying it would take
"about a month" - so fingers crossed, that will be soon. If they don't show
up soon we will reach out to them to check the status.



On Thu, Sep 20, 2018 at 12:40 PM William Stein  wrote:

> On Thu, Sep 20, 2018 at 10:49 AM, Syrus Nemat-Nasser 
> wrote:
> > Hi Jupyter community! I have a questions for the project leaders and
> don't
> > know where to ask it.
> >
> > I was excited to check out the talks from Jupytercon this year, and as
> > Jupyter is in part publicly funded, I expected to see videos from all the
> > talks such as we get with PyCon or PyData conferences. To me, it looks
> like
> > only a small sample of talks have been posted on YouTube. Is this because
> > other talks were not recorded, or is this a for-profit play by O'reilly
> to
> > sell Safari subscriptions? Will we get free access to JupyterCon talks
> going
> > forward?
>
> For context, I think this is the playlist of videos that are available
> so far, which I think
> you're referring to:
>
> https://www.youtube.com/playlist?list=PL055Epbe6d5b572IRmYAHkUgcq3y6K3Ae
>
> I'm pretty sure my talk was recorded, and I'm not in the above list,
> so *my guess*
> is that all videos will be posted, and they just haven't finished yet.
> From what
> I saw, the "production value" of everything involving JupyterCon 2018 was
> very
> high, so my guess is it is just taking them a while.   (Also, as a
> speaker, I will loudly
> complain if my talk video were pay-walled.)
>
> >
> > Best regards, --Syrus
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Project Jupyter" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to jupyter+unsubscr...@googlegroups.com.
> > To post to this group, send email to jupyter@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jupyter/6de688de-7cb4-40b7-9062-0211228d57d0%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> William (http://wstein.org)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CACLE5GDk9WenqizgHMp%3DQWzUbXwQ%2BtE%2BkG_XK%3DV4%3D2brZFieaw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQa2_EUADavLWjZLbUC-BB1ai%2B%2BRfC4ipmhXGeYSxLc%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] [ANN] NBConvert 5.4 -- A year's worth of changes

[Brian Granger]

Matthew, many thanks for all your work on nbconvert and congrats to
everyone who helped out!

On Thu, Sep 6, 2018 at 1:06 PM Matthew Seal  wrote:

> NBConvert 5.4
>
> After a long period between releases, we are pleased to announced
> nbconvert 5.4.0!
>
> It is available via pypi (pip install nbconvert -U) and conda-forge (conda
> install nbconvert -c conda-forge).
>
> For full details about the release, see the changelog
> ,
> but we've highlighted the significant changes below.
>
>
> Significant Changes
>
> Deprecations
>
> Python 3.3 support was dropped. The version of python is no longer common
> and new versions have many fixes and interface improvements that warrant
> the change in support.
>
>
> Changes in how we handle metadata
>
> There were a few new metadata fields which are now respected in nbconvert.
>
> ``nb.metadata.authors`` metadata attribute will be respected in latex
> exports. Multiple authors will be added with ``,`` separation against their
> names.
>
> ``nb.metadata.title`` will be respected ahead of ``nb.metadata.name`` for
> title assignment. This better matches with the notebook format.
>
> ``nb.metadata.filename`` will override the default
> ``output_filename_template`` when extracting notebook resources in the
> ``ExtractOutputPreprocessor``. The attribute is helpful for when you want
> to consistently fix to a particular output filename, especially when you
> need to set image filenames for your exports.
>
> The ``raises-exception`` cell tag
> (``nb.cells[].metadata.tags[raises-exception]``) allows for cell exceptions
> to not halt execution. The tag is respected in the same way by `nbval <
> https://github.com/computationalmodelling/nbval>`_ and other notebook
> interfaces. ``nb.metadata.allow_errors`` will apply this rule for all
> cells. This feature is toggleable with the ``force_raise_errors``
> configuration option.
> Errors from executing the notebook can be allowed with a
> ``raises-exception`` tag on a single cell, or the ``allow_errors``
> configurable option for all cells. An allowed error will be recorded in
> notebook output, and execution will continue.
> If an error occurs when it is not explicitly allowed, a
> ``CellExecutionError`` will be raised.
> If ``force_raise_errors`` is True, ``CellExecutionError`` will be raised
> for any error that occurs while executing the notebook. This overrides both
> the ``allow_errors`` option and the ``raises-exception`` cell tags.
>
>
> Configurable kernel managers when executing notebooks
>
> The kernel manager can now be optionally passed into the
> ``ExecutePreprocessor.preprocess`` and the ``executenb`` functions as the
> keyword argument ``km``. This means that the kernel can be configured as
> desired before beginning preprocessing.
>
> This is useful for executing in a context where the kernel has external
> dependencies that need to be set to non-default values. An example of this
> might be a Spark kernel where you wish to configure the Spark cluster
> location ahead of time without building a new kernel.
>
> Overall the ExecutePreprocessor has been reworked to make it easier to
> use. Future releases will continue this trend to make this section of the
> code more inheritable and reusable by others. We encourage you read the
> source code for this version if you're interested in the detailed
> improvements.
>
>
> Surfacing exporters in front-ends
>
> Exporters are now exposed for front-ends to consume, including classic
> notebook. As an example, this means that latex exporter will be made
> available for latex 'text/latex' media type from the Download As interface.
>
>
> Raw Templates
>
> Template exporters can now be assigned raw templates as string attributes
> by setting the ``raw_template`` variable.
>
> .. code-block::
>
>   class AttrExporter(TemplateExporter):
>   # If the class has a special template and you want it defined within
> the class
>   raw_template = """{%- extends 'rst.tpl' -%}
>   {%- block in_prompt -%}
>   raw template
>   {%- endblock in_prompt -%}
>   """
>   exporter_attr = AttrExporter()
>   output_attr, _ = exporter_attr.from_notebook_node(nb)
>   assert "raw template" in output_attr
>
>
> New command line flags
>
> The ``--no-input`` will hide input cells on export. This is great for
> notebooks which generate "reports" where you want the code that was
> executed to not appear by default in the extracts.
>
> An alias for ``notebook`` was added to exporter commands. Now ``--to
> ipynb`` will behave as ``--to notebook`` does.
>
>
> Contributors
>
> The following 35 authors contributed 329 commits.
>
> * Anton Akhmerov
> * Benjamin Ragan-Kelley
> * berleon
> * Correoso Garcia
> * Damian Avila
> * Danilo J. S. Bellini
> * Doug Devine
> * geniusupgrader
> * Hagai Hargil
> * Igor Mikushkin
> * Josh Barnes
> * Leo Gallucci
> * Lukasz 

Re: [jupyter] nbdime 1.0.0 released

[Brian Granger]

Congrats!

On Tue, May 15, 2018 at 4:27 AM, Carol Willing  wrote:
> Congrats Vidar and all who contributed to nbime :D
>
>
> On May 15, 2018, at 5:33 AM, Vidar Tonaas Fauske  wrote:
>
> We've just release version 1.0 of nbdime!
>
> Some highlights:
>
> - Added jupyterlab extension.
>
> - Added ability for git diff driver to integrate with git filters (e.g. if
> you have nbstripout configured, that will be run before taking the diff).
>
> - Added config system to allow for configuring the various entrypoints.
> Especially useful for customizing which keys to ignore when diffing.
>
>
> See the changelog for more details on the changes, and the documentation in
> general for more info!
>
> Vidar
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CADZ1C%3Dy4UxaNhUeFnf9n3y%3DFk10ZWQyZ1%3D2-PFKVvexm30Ttzg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/EFCDB11B-E98A-446B-979A-E013F8DCF8BA%40gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRaiT49Wdk9u%2BsUjTYPPV0Qk1%3D9J-c4-QxZHxrjpB80kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] https://beta.observablehq.com

[Brian Granger]

I would love to see a high quality reactive data flow kernel for
Jupyter. I think we have most of the pieces in place to do this type
of thing in Jupyter (we have updatable outputs now).

On Mon, May 14, 2018 at 9:08 AM, 'Aaron Watters' via Project Jupyter
 wrote:
> Hi folks.
>
> I just stumbled into an interesting project called "Observable" by the folks
> who came up with D3.
> Looks like it may be partially inspired by Jupyter.
>
> It looks promising to me :).
>
> It would be interesting to see to what extent Jupyter kernels, for example
> might be used
> within an Observable context.
>
> Comments or thoughts?
>
> https://beta.observablehq.com
>
>   -- Aaron Watters
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/cff296b2-3ecc-4f2e-acb5-38d24c4b1c39%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpS9EMpPSHHJkagzvoLT0is8U%2BEbz42%2BN35AOjeGSgwmxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Notebook 5.5 RC1

[Brian Granger]

Hi Thomas thanks for the notice.

Has there been anything that changed that might be leaking file descriptors?

I started to see that last week

Sent from my iPhone

> On May 1, 2018, at 1:00 PM, Thomas Kluyver  wrote:
> 
> I've just uploaded a release candidate of notebook 5.5 to PyPI.
> 
> While there's no headline new feature in this release, there are quite a lot 
> of smaller changes, and there's a good chance we've unwittingly broken 
> something. So if you've been looking for ways to contribute to Jupyter, 
> here's an easy way to get started! We'd like as many of you as possible to 
> install the release candidate and try working with it.
> 
> To install the new version:
> 
>pip install --upgrade --pre notebook
> 
> Please report bugs at https://github.com/jupyter/notebook - and if you feel 
> like trying to fix bugs as well, go for it.
> 
> You can find more about what's new in the changelog - I've tried to organise 
> the entries so they're easier to scan through:
> 
> 
> http://jupyter-notebook.readthedocs.io/en/latest/changelog.html#release-5-5-0
> 
> Thank you to all the contributors, especially a number of new contributors 
> who have their first changes in this release. :-)
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CAOvn4qjhMogan%3DFGs6sepAiTpA7XUT6sne%2BKZjAo0z-vnByEPg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/6EE118B0-9EC3-4F47-8AE3-1FD2142C6F99%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Resources for learning JavaScript/TypeScript online

[Brian Granger]

Kyle, many thanks, that is *perfect*!

On Sun, Apr 22, 2018 at 4:19 PM, Kyle Kelley <rgb...@gmail.com> wrote:
> I use egghead.io quite a bit, though it's not a comprehensive one-track
> curriculum.
>
> On Sun, Apr 22, 2018 at 1:05 PM Brian Granger <elliso...@gmail.com> wrote:
>>
>> Hi all,
>>
>> We are getting started with the Summer 2018 Jupyter internship at Cal
>> Poly. In previous years, I had used CodeSchool to get the interns
>> started learning things like
>>
>> HTML/CSS/JavaScript/TypeScript/Node/React.
>>
>> However, it looks like CodeSchool is going away (bought by
>> PluralSight, and being "assimilated").
>>
>> Does anyone know of any good resources for learning these things? I am
>> particularly interested in things that start out similar to how
>> CodeSchool worked - completely online, that don't require a complex
>> local dev setup - at least initially.
>>
>> Thanks!
>>
>> Cheers,
>>
>> Brian
>>
>>
>>
>>
>>
>> --
>> Brian E. Granger
>> Associate Professor of Physics and Data Science
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgran...@calpoly.edu and elliso...@gmail.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAH4pYpT1wsWULVdU-LbuEFLf%2BKS18v3u0RVQspjTPNvbGH7h8Q%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> Kyle Kelley (@rgbkrk; lambdaops.com)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CA%2BtbMaUQpRHO0snNtQ6AxpCBcYzEwm7TXCkDvJixdvc33PYgvg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTnBHbTD7oJ4fsdUAuWbbSVg0evuDSr5Ezs8RvBLOBXGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Resources for learning JavaScript/TypeScript online

[Brian Granger]

Hi all,

We are getting started with the Summer 2018 Jupyter internship at Cal
Poly. In previous years, I had used CodeSchool to get the interns
started learning things like

HTML/CSS/JavaScript/TypeScript/Node/React.

However, it looks like CodeSchool is going away (bought by
PluralSight, and being "assimilated").

Does anyone know of any good resources for learning these things? I am
particularly interested in things that start out similar to how
CodeSchool worked - completely online, that don't require a complex
local dev setup - at least initially.

Thanks!

Cheers,

Brian





-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpT1wsWULVdU-LbuEFLf%2BKS18v3u0RVQspjTPNvbGH7h8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Vega3 support in JupyterLab

[Brian Granger]

For the 0.31 release it was a separate package:

https://www.npmjs.com/package/@jupyterlab/vega3-extension

That package is still available on npm, so you should be able to
install it on 0.31 with:

jupyter labextension install @jupyterlab/vega3-extension

In JupyterLab master and moving forward it is built into JupyterLab
itself, so no additional extension is needed (but vega2 will be a
separate package moving forward).

What version of lab are you using? How did you try to install/use it?

See this PR for more information:

https://github.com/altair-viz/altair/pull/566

On Mon, Mar 12, 2018 at 7:47 AM, Dave Dixon  wrote:
> In the last few days, the Vega3 extension for JupyterLab seems to have
> disappeared. I was able to install it on my machine, and not long after had
> a colleague try it and he was getting errors. It appears the Github
> repository has been replaced with a Vega2 extension, and I gather from
> looking through the JupyterLab Github issues that this is planned, with
> Vega3 support becoming the default in JupyterLab. But it doesn't seem to be
> in the current release. Is there any way I can get my colleague up and
> running with Vega3? Thanks.
>
> Dave
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/002c603c-3830-45a6-b157-a003ba5116a9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSy_5URZqmxq_emoEpYQ8n5eoaG3SDfq%2BcQZa%2Bv8QaxxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] tmpnb.org is shutdown

[Brian Granger]

Thanks Min!

On Sun, Mar 4, 2018 at 11:20 AM, Kyle Kelley  wrote:

>  Thank you Min and all the Binder folks! 
>
> On Sun, Mar 4, 2018 at 4:33 AM, MinRK  wrote:
>
>> As announced earlier on this list, the tmpnb.org service is now shutdown
>> in favor of Binder . The kitchen-sink demo image
>> that we used is now retired as well. Instead of adding every possible demo
>> to a single image, Kernel authors are encourages to create a demo
>> themselves (e.g. on Binder, but not necessarily) and add a link to the try
>> jupyter page . This can be done by adding an
>> entry to the try data yaml file
>> 
>> and a logo to the assets
>>  if
>> there isn’t an appropriate one already.
>>
>> Right now, we have links to the IPython-in-depth tutorial, the JuptyerLab
>> demo repo, and one for each of R and Julia. It would be extra great if
>> people in the Julia and/or R communities could replace the R and Julia
>> links to more appropriate demos of working with Jupyter in their respective
>> areas. I suspect the ipython-in-depth link should be replaced with a more
>> dedicated quick introduction repo that's yet to exist on the jupyter github
>> org.
>>
>> -Min
>> ​
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jupyter/CAHNn8BXYP74epHa90u6ye0O-K%3DZM%
>> 2BLRRM0Hf8OhMBd2VtTu1dw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Kyle Kelley (@rgbkrk ; lambdaops.com)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jupyter/CA%2BtbMaUtTyHRqXWdhBTWRzvwAHHkLz
> oBqD6H5RvQ0yvLQwvnJA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTcK3JCOTiSs%2BfFuAzYXH%2B5NeH3%2BL9%3DD06V8%3Dn6bd7ZcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter Lab and ISO 8601

[Brian Granger]

On a call right now, but I really like the example from Gnome that
Thomas posted.

On Wed, Feb 28, 2018 at 2:27 PM, Matthias Bussonnier
<bussonniermatth...@gmail.com> wrote:
>
>
> On 28 February 2018 at 13:42, Brian Granger <elliso...@gmail.com> wrote:
>>
>> Matthias, helpful thoughts! I think your example points to a third
>> question a user might be trying to answer:
>>
>> 3) "How are the last modified times of these notebooks differ?"
>>
>> I fully agree that seeing a set of notebooks with a time of "X Y ago"
>> is not helpful tin answering that question. However, I don't think the
>> usability issues are unique to "long times" ago. For example, it would
>> be just as painful to see a few notebooks that say "5 minutes ago" as
>> "5 month ago" if I am trying to answer this third question.
>
>
> Yes, except ISO 8601 does not "loose granularity" when time passes. I'm
> going to assume that if we format to iso, we'll add HH:MM but not SS,
> so having 5 notebooks "at 14:16" or 5 notebooks "5 minutes ago" is the same.
> You can't differentiate regardless  of moment.js vs iso.
> If the 5 notebooks are from 5 different days in Jan, with ISO I can still
> distinguish, with moment I can't.
>
> So I believe issues are exacerbated with old files.
>
> in other words, the issue with moment.js "Smart" format is that 2 notebooks
> differentiable today, will not be tomorrow. The buckets get larger too fast.
> I like Thomas' example of Gnome, which does (seem to) strike a nice balance.
> --
> M
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CANJQusVbXHaQX7xozAeBfxQAkPDrjEZxiFKqGgrWOK1FCtMsiw%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSxvGoc2i6QFoLtNd8kmm%3DzcaLJU%2BumHa1HCA1CmED5ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter Lab and ISO 8601

[Brian Granger]

Sorry folks, things are crazy this week so I am a bit behind on emails...

>From the user experience perspective there are two questions a user
might be interested in:

1) At what exact time was this document last edited? The ISO 8601
format is possibly the right format for that information. I am not
arguing against the ISO standard.
2) How long ago did I edit that document (in human terms)? ISO 8601 is
sub-optimal for that as a user has to look at something like
"2018-02-28T15:25:47+00:00", then look at their current time and do
that math to figure out "oh, that was 5 minutes ago". The moment js
style is optimized to answer this question. I would love to do a
quantitative users test for that (probably won't happen due to time).

The difference between these two outputs isn't about standards, it is
about what question the user is trying to answer. Furthermore, that
question may change depending on what a user is doing (it changes over
time for a single user). Because of that, I don't think putting this
as a configuration option makes sense. Having a UI control that allows
a user to quickly switch date formats on the fly is probably more
appropriate. In terms of the default, my hypothesis is that question
2) above is the question users are asking the majority of the time.






On Wed, Feb 28, 2018 at 2:59 AM, Björn Johansson  wrote:
> It is also standard in many European countries as well and recommended by
> xkcd...
>
> On Tuesday, February 27, 2018 at 6:11:21 AM UTC, Lawrence D’Oliveiro wrote:
>>
>> On Saturday, February 24, 2018 at 5:55:20 PM UTC+13, ellisonbg wrote:
>>>
>>> Not sure how I feel about showing users ISO 8601 formatted datetimes
>>> though.
>>>
>>> It is not a particularly human friendly datetime format.
>>
>>
>> It’s standard in Japan. And it is an international standard, after all.
>> Besides which, it makes logical sense.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/71b33713-d5b9-4574-94be-60be34ad02d3%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQCadAo%2BQwDQ2bJS-Foa62fMPiLS_iaLB9%3DvP9GcOOiOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] [ANN] nbconflux: Publish notebooks as Atlassian Confluence pages

[Brian Granger]

Pete,

Thanks for sharing! I have never used Confluence, but this look like
it would be useful.

Cheers,

Brian

On Mon, Feb 26, 2018 at 8:34 AM, Peter Parente  wrote:
> Hi all,
>
> I wanted to make you aware of a utility we recently open sourced called
> nbconflux, a tool for publishing Jupyter Notebooks as Atlassian Confluence
> pages based on nbconvert.
>
> https://github.com/Valassis-Digital-Media/nbconflux
>
> nbconflux is useful when:
>
> * You use Jupyter notebooks to author computational narratives
> * Your organization uses Confluence to store institutional knowledge
> * You want an easy way to publish your work in that knowledge base
>
> It's compatible with Confluence Cloud and Confluence Server, and does the
> following:
>
> * Converts most cell inputs and outputs to valid Confluence storage format
> * Attaches image outputs (e.g., matplotlib PNGs) to a page, shows them
> inline, and maintains the page-image association in the version history
> * Attaches the source notebook to a page, links to it from the page footer,
> and maintains the page-notebook association in the version history
> * Supports sweep-select Confluence comments over most input and output
> content
> * Excludes input, output, or entire cells based on notebook cell tags
> noinput, nooutput, or nocell
> * Labels pages with nbconflux to identify content that originated as
> notebooks
> * Inserts a table of contents macro at the top of the page based on notebook
> headings
> * Applies the NBViewer stylesheet to pages to blend Confluence styling with
> Jupyter notebook styling (requires the CSS macro)
> * Enables MathJax rendering (requires the HTML macro)
> * Supports raw-cell passthrough of Confluence storage format markup (e.g.,
> to include Confluence macros)
>
> Cheers,
> Pete
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/f4ce0962-f95c-4d4a-8321-758874cf60ba%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQczdQVMJcyYgqtcbHd6hQX3EjFYLk_7gXosuLvv9RdiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter Lab and ISO 8601

[Brian Granger]

I think we are using moment.js. Not sure how I feel about showing
users ISO 8601 formatted datetimes though. It is not a particularly
human friendly datetime format. Maybe having some sort of toggle in
the UI to switch between the moment.js times and a more human friendly
variant of the ISO 8601 information? We aren't alone in using the
moment.js style date/times (GitHub does for everything).

On Thu, Feb 22, 2018 at 1:41 PM, Milos Miljkovic
 wrote:
> OK, I will open an issue. OTOH, I haven't seen the behavior you described
> for the notebook to switch to ISO date when a file is older than certain
> limit.
>
> On Thursday, February 22, 2018 at 2:23:37 PM UTC-5, Matthias Bussonnier
> wrote:
>>
>> Probably,
>>
>> If it's using moment.js it's possible, but I haven't touched that part of
>> the code base. We could do something similar as the notebook and switch to
>> iso-date when the file is older than a couple of hours/days.
>> I would suggest opening an issue.
>>
>> On 22 February 2018 at 11:15, Milos Miljkovic  wrote:
>>>
>>> Thanks Matthias! Indeed, there's a tooltip if you hover over current
>>> vague time stamp. Is there a way to make this "a xyz ago" malarkey go away
>>> and show what's in the tooltip in its place?
>>>
>>> On Thursday, February 22, 2018 at 1:49:02 PM UTC-5, Matthias Bussonnier
>>> wrote:

 I believe if you hover over the date, there should be a tooltip with the
 exact date and time.
 --
 M

 On 22 February 2018 at 10:35, Milos Miljkovic 
 wrote:
>
> Hiya,
>
> Is there a way in Jupyter Lab to display "Last modified" column in
> Files tab in ISO 8601 format? Current format of "a xyz ago" is utterly
> useless. If there isn't a way to do this, where should I have a peek for a
> PR.
>
> Cheers,
>
> Miloš.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jupyter+u...@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/4330075a-a9f0-4430-8344-107d44da3dd8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Project Jupyter" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jupyter+u...@googlegroups.com.
>>> To post to this group, send email to jup...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jupyter/41710833-158a-41fa-9acc-2002f1ed1e48%40googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/fcbc4bbb-8d0d-453c-97ff-b48c64ae312c%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSkJv0hPtuuimo2m1CwvbPzRo6QTEWqGbTS1TGEw-7%2B9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Time Travel Analysis or Undo in Jupyter

[Brian Granger]

I built something similar to reinteract as well last year. Doing the
simple case isn't very hard - was just deep copying the namespace
before exec'ing each cell and storing those as a python list. As
Robert mentions, doing this type of thing well and efficiently, gets
to be much more difficult.

However, it is important that Jupyter doesn't make any assumptions
about these things or place limitations on the model of the kernel. As
an example here is a python kernel for Jupyter that implements a
dataflow model:

https://github.com/dataflownb/dfkernel



On Fri, Feb 23, 2018 at 12:13 PM, Robert Schroll
 wrote:
> Hi Jayme,
>
> A while back, I was involved in the Reinteract project [1], which had the
> same goal as you with a different mechanism. Reinteract provided a
> notebook-like interface, but it recorded the state in which each expression
> was executed. When you went back to a previous line, it would rewind the
> state and execute in the appropriate historical state.
>
> That was the goal at least. To avoid copying the whole state every step, it
> relied on heuristics at the syntax level to guess whether code would modify
> objects. Reinteract would then only copy things that changed. This worked
> 98% of the time, which was enough for me, but it still produced a few odd
> corner cases where its behavior was incomprehensible to those who didn't
> know its internals.
>
> I'm happy to talk more about Reinteract if you're interested, but I've
> already bored this mailing list once about it.
>
> Robert
>
> [1] http://www.reinteract.org/
>
>
> On Feb 22 2018, at 2:39 am, Jayme Bird  wrote:
>
>
> Dear all,
>
> I would appreciate your feedback with a potential research area,
> specifically within Jupyter - and perhaps more generally in Python.
>
> Interactive data analysis in frameworks like jupyter notebooks has a common
> issue - the modification of potentially large datasets within an interactive
> session. Unintentional modification is frequent, and the common solution is
> to re-run the steps that were required to get from a data file to the point
> in question. This reduces the usability of the analysis tools, makes
> “what-if” exploration difficult, and creates a lot of unnecessary overhead
> for either manually saving state or re-running scripts to recreate it.
>
> I'm investigating a proposed project focused on the use of relational
> Multi-Version Concurrency Control (MVCC) techniques from database systems
> for these interactive workloads. In essence allowing a control z undo
> functionality to return to the previous state after running a particular
> step of an interactive script.
>
> I would appreciate knowing if any development of this has been discussed -
> as well as ideas or useful feedback in general?
>
> Kind regards
> Jayme Bird
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/1410954636.3371205.1519295968702.JavaMail.zimbra%40cwi.nl.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/local-ac90a11e-2fb9-v1.1.4-22d9f20d%40mando.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSAZnYqNhAzrYzy9z%3DmWrHZH6bVaYx726fSFLMtwo%2BccA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] An example of what can be built with the JupyterLab ecosystem

[Brian Granger]

Very cool, thanks for sharing!

On Fri, Feb 9, 2018 at 12:24 AM, Simon Biggs  wrote:
> Hi,
>
> Standing upon the shoulders of giants I have created a tool that allows one
> to quickly and easily create powerful reactive form like front ends for
> python
> scripts and packages using markdown.
>
> Check out https://github.com/SimonBiggs/scriptedforms to take it for a spin.
> Should take less than 5 mins to be able to see the power of what it can do.
>
> Building this was only possible because the upcoming JupyterLab has been
> built in such a beautifully modular way.
>
> Thank you Team Jupyter! :)
>
> Cheers,
> Simon
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/34a804fb-e852-41b2-8b60-c35f92b2faf4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTk-Ws27qsJtJQxwCAdK8t9iy3c6FCuf20h534KXOy7JA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Just ran "conda upgrade notebook" to get .5.3.1 now notebook won't start

[Brian Granger]

can you try updating the jupyter_core package using conda or pip. We
may have forgotten to update a dependency version.

On Mon, Jan 22, 2018 at 1:28 PM, Tom Brander  wrote:
> Got no error on the upgrade but get this now when trying to run notebook so
> I'm stuck!
> Some sort of config issue?
> Help appreciated!
>
> tom@tomServal:~$ jupyter notebook
> Traceback (most recent call last):
>   File "/home/tom/anaconda3/bin/jupyter-notebook", line 4, in 
> import notebook.notebookapp
>   File
> "/home/tom/anaconda3/lib/python3.6/site-packages/notebook/__init__.py", line
> 25, in 
> from .nbextensions import install_nbextension
>   File
> "/home/tom/anaconda3/lib/python3.6/site-packages/notebook/nbextensions.py",
> line 27, in 
> from jupyter_core.utils import ensure_dir_exists
> ImportError: cannot import name 'ensure_dir_exists'
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/2fa07753-7e2d-44db-81d4-627de8d5ab58%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQMO3919ZfTFHaTewGMG5kNosLWPBmE4wHAcMzX8O1dQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Organizing posting on the Jupyter Blog.

[Brian Granger]

Thanks Matthias, this sounds great!

Also, if drafts are being done on Google Drive or Dropbox Paper,
please paste a link to the draft in the draft Medium post so others
can find it.

Cheers,

Brian

On Sat, Jan 6, 2018 at 3:25 AM, Matthias Bussonnier
 wrote:
> Happy new year everyone,
>
> I hope 2018 is stating well for you. We have a couple of blog posts in the
> making, and in doing so some of us realize that we needed some organisation
> to try to better schedule when things get published.
>
> First I want to remind everyone that the Jupyter blog being hosted on
> Medium, we can easily have guests publications, we had some in the past and
> hope to have more in 2018. If you have Jupyter related topics feel free to
> contact us if you wish to put them on the Jupyter blog.
>
> For those of you already having access to the blog as writer or editor, we
> realized that a couple of planned blog posts were likely to collide. Indeed
> there is no schedule with what is planned to be published and when. This is
> in particular due to the draft edition process being often on another
> platform like google docs, dropbox paper... In order to have a vague idea of
> what is going to be published, we propose that quasi-empty drafts post with
> the expected subjects and dates get submitted as early as possible. That
> help other to know whether there are empty weeks, or overcharged weeks and
> plan accordingly.
>
>
> TL:DR;
> When publishing on blog.jupyter.org, please submit drafts (even empty) as
> early as possible with subject and planned dates.
>
>
> Thanks !
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CANJQusUE5%3DL_cpOAS2rFeHevSAUMGaDtOqKzVGjHkhJ__9mhVQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpR_XBwJ3Qy4igsVb-kmcfe87C2XKFxyQ7WJYcs-9_Ty%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Rich representation of exceptions/tracebacks

[Brian Granger]

One further question - do you think there is anything we can do in the
meantime in upstream libraries such as Altair so support rich reprs of
errors? Sure we could just publish a mimebundle, but then then we
can't raise, right?

On Mon, Nov 27, 2017 at 11:38 AM, Brian Granger <elliso...@gmail.com> wrote:
>> I poked at it some time ago (sorry no branches), and plan to do refactoring
>> of IPython's error machinery to improve that. One issue is that the
>> Traceback fromatter does tokenizing and coloring at the same time (with raw
>> escape sequences) instead of yielding data structures that can be formatted
>> later. This was one of my reason to push Python 3 : to use generators, yield
>> and yield-from in this part of the codebase.
>> It is still _way_ too messy now, but better than it was a year ago.
>
> OK, that is helpful!
>
>> That's technically, for the overview, I also discussed a bit with Kyle at
>> spring dev meeting (and looked at tonic dev). I think that having some "get
>> together" with kernels author from multiple languages would be useful. In
>> particular I'd like to integrate the discussion about a debugger protocol
>> into this as well and/or link from error messages to code cells, which need
>> a bit more coordination than "just" mimebundles.
>
> Yeah I could imagine something more structured that mimebundles might
> be helpful in this context.
>
>>
>> I also tweeted
>> [that](https://twitter.com/Mbussonn/status/933418933994098688) in response
>> to same blog post, so you are 4 days late :-)
>
> :-) Thanks for the update, glad I wasn't alone in thinking about these things.
>
> Cheers, Brian
>
>> --
>> Matthias
>>
>>
>> On Sun, Nov 26, 2017 at 7:04 PM, Brian Granger <elliso...@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> Has anyone done work on using rich MIME based representations of
>>> exceptions and tracebacks in IPython+Jupyter?
>>>
>>> This nice blog post got me thinking about providing more helpful
>>> representations of errors to users:
>>>
>>> https://blog.keras.io/user-experience-design-for-apis.html
>>>
>>> Cheers,
>>>
>>> Brian
>>>
>>> --
>>> Brian E. Granger
>>> Associate Professor of Physics and Data Science
>>> Cal Poly State University, San Luis Obispo
>>> @ellisonbg on Twitter and GitHub
>>> bgran...@calpoly.edu and elliso...@gmail.com
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Project Jupyter" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jupyter+unsubscr...@googlegroups.com.
>>> To post to this group, send email to jupyter@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jupyter/CAH4pYpSCR6o-JFk--t0Sn3SjY%2B%2BZ_%2BFC0WAXSRCqt_Qy%3DEddyg%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CANJQusUvjhb%3DZ1HP93cssJ%3Dzk19%2BK0fqO%3DZnm8P4hVAjchrt6A%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgran...@calpoly.edu and elliso...@gmail.com



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQgrXNk60bL7wMbOV80RDyzgJzgontpehyAdMvprz%3DoGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Rich representation of exceptions/tracebacks

[Brian Granger]

> I poked at it some time ago (sorry no branches), and plan to do refactoring
> of IPython's error machinery to improve that. One issue is that the
> Traceback fromatter does tokenizing and coloring at the same time (with raw
> escape sequences) instead of yielding data structures that can be formatted
> later. This was one of my reason to push Python 3 : to use generators, yield
> and yield-from in this part of the codebase.
> It is still _way_ too messy now, but better than it was a year ago.

OK, that is helpful!

> That's technically, for the overview, I also discussed a bit with Kyle at
> spring dev meeting (and looked at tonic dev). I think that having some "get
> together" with kernels author from multiple languages would be useful. In
> particular I'd like to integrate the discussion about a debugger protocol
> into this as well and/or link from error messages to code cells, which need
> a bit more coordination than "just" mimebundles.

Yeah I could imagine something more structured that mimebundles might
be helpful in this context.

>
> I also tweeted
> [that](https://twitter.com/Mbussonn/status/933418933994098688) in response
> to same blog post, so you are 4 days late :-)

:-) Thanks for the update, glad I wasn't alone in thinking about these things.

Cheers, Brian

> --
> Matthias
>
>
> On Sun, Nov 26, 2017 at 7:04 PM, Brian Granger <elliso...@gmail.com> wrote:
>>
>> Hi all,
>>
>> Has anyone done work on using rich MIME based representations of
>> exceptions and tracebacks in IPython+Jupyter?
>>
>> This nice blog post got me thinking about providing more helpful
>> representations of errors to users:
>>
>> https://blog.keras.io/user-experience-design-for-apis.html
>>
>> Cheers,
>>
>> Brian
>>
>> --
>> Brian E. Granger
>> Associate Professor of Physics and Data Science
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgran...@calpoly.edu and elliso...@gmail.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAH4pYpSCR6o-JFk--t0Sn3SjY%2B%2BZ_%2BFC0WAXSRCqt_Qy%3DEddyg%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CANJQusUvjhb%3DZ1HP93cssJ%3Dzk19%2BK0fqO%3DZnm8P4hVAjchrt6A%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpS5HCsy%3DTk1mNFKLZSnVWuo1omHNatDGx601xU7mKc8pA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Rich representation of exceptions/tracebacks

[Brian Granger]

Hi all,

Has anyone done work on using rich MIME based representations of
exceptions and tracebacks in IPython+Jupyter?

This nice blog post got me thinking about providing more helpful
representations of errors to users:

https://blog.keras.io/user-experience-design-for-apis.html

Cheers,

Brian

-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSCR6o-JFk--t0Sn3SjY%2B%2BZ_%2BFC0WAXSRCqt_Qy%3DEddyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: The Kernel appears to have died. It will restart automatically ? Please help !

[Brian Granger]

I haven't looked into the details of your configuration, but in
general, Jupyter and the python kernels have no problem using whatever
RAM the system makes available to it. I have created single NumPY
arrays with 1TB of RAM with no problem. If you are running out of RAM,
it is a system level thing related to the configuration of the system,
physical RAM of the system and your deployment of Jupyter.

On Mon, Nov 20, 2017 at 11:58 AM, Karthik Ram  wrote:
> Argg. Thank you Thomas. It did run longer(17 min as opposed to 10 min) this
> time after I un-commented those lines, but still saw the same issue. Is
> there any limitation in Jupyter that it cannot handle more than certain GB
> data or query more than certain million or billion rows from post gre SQL DB
> ?
>
> Its strange because when I do run the SQL script from SQL work bench locally
> on my machine(which is less powerful than the server on which jupyter is
> running), I do get the resulting rows.
>
> On Mon, Nov 20, 2017 at 3:35 AM, Thomas Kluyver  wrote:
>>
>> On 19 November 2017 at 22:28, Karthik Ram  wrote:
>>>
>>> I also changed the following in jupyterhub_config.py file. But still
>>> seeing the issue.
>>>
>>> ...
>>>
>>> #c.Spawner.mem_guarantee = 8G
>>>
>>
>> You'll need to uncomment these lines for them to affect anything, i.e.
>> remove the # from the beginning. It also probably needs to be a string - put
>> "8G" inside quotation marks.
>>
>> Thomas
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Project Jupyter" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jupyter/hY0Jq-E5Ki0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAOvn4qiR9cRz4ydTya2nwPivkbjsS_yuT4RwwqXO3_T6oSti5g%40mail.gmail.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> "In the depth of winter, I finally learned that within me there lay an
> invincible summer"
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAFZay%2Bh5L-6fMTE8dX8DHhS2ZRByaojFbTa-HeNS01SiYyOwaA%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRjuTYMXdRT%2BfRf5OPgN3W2CLYuqtu9C3s2Udf1QWaK8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Moving Terminado into Jupyter maintenance

[Brian Granger]

+1, let me know if you want help reaching out to MSFT folks

On Mon, Nov 20, 2017 at 6:59 AM, Matthias Bussonnier
 wrote:
> I'm +1 to transferring the repository. I would also try to ping
> whoever-we-know at Microsoft, as enabling this will likely impact them
> the most.
> --
> Matthias
>
> On Mon, Nov 20, 2017 at 2:50 PM, Thomas Kluyver  wrote:
>> Terminado (http://terminado.readthedocs.io/en/latest/ ) is part of the
>> machinery that we use for interactive terminals in the browser. Xterm.js
>> (https://xtermjs.org/ ) provides the frontend in the browser, which is where
>> most of the complexity is needed, while Terminado is a relatively simple
>> part that runs on the server. It integrates with the Tornado web framework,
>> which the Jupyter Notebook is built on.
>>
>> Currently, Terminado is purely for Unix-like systems. However, there is a
>> library called winpty which provides the underlying feature to make similar
>> functionality possible on Windows. The Spyder developers have done some
>> impressive work to package this up in a form that is readily accessible from
>> Python and pip-installable, and Steven has opened a pull request on
>> Terminado to use this.
>>
>> It would certainly be nice to provide terminals on Windows as well, but I'm
>> not confident I understand the Windows side of things well enough to
>> maintain it. Steven has offered to help with maintenance (thanks!), but I'd
>> like to propose moving it into the Jupyter organisation to make this easier,
>> and to facilitate other people contributing to its maintenance.
>>
>> Terminado has generally been a very low-maintenance project - it's simple
>> glue between a Unix pty and a tornado websocket. Windows support may add
>> some load, but I don't see it ever needing many changes. Jupyter is the only
>> user I'm aware of, though over 100 people have 'starred' it, so it may have
>> some others.
>>
>> Thanks,
>> Thomas
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAOvn4qhY97amb4qoajB58U%3DQuxbFKA90XpefM7CJS3FY8C-ZiA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CANJQusUghzVD-PvsmmfZw6zMSLGs4iT1SNMjT6Ox%2Bew_Qn3P_A%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQQWvEZjpbD6FJQUi2dSY1h2%3DdkMGa8JuQRwXzR_4QyDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Supported Markdown syntax

[Brian Granger]

Unfortunately, our best answer currently is "whatever our particular
markdown parser supports". We know that is a painful situation to be
in. It is our intention to document the syntax supported in the
classic notebook and then begin to make changes to support commonmark.
The repo that Matthias pointed was a beginning attempt to document how
our markdown compares the commonmark, but the differences were
substantial in the small details.

On Fri, Nov 10, 2017 at 10:46 AM, Matthias Bussonnier
 wrote:
> Hi Bruno,
>
> There've been am effort to try to document that; see
> (https://github.com/jupyter/jupyter_markdown), but we're pretty low
> and bandwidth and would need some help.
>
> Cheers,
> --
> Matthias
>
> On Thu, Nov 9, 2017 at 3:11 AM, Bruno  wrote:
>> Dear all,
>>
>> What is the exact supported syntax for markdown cells in Jupyter?
>>
>> I am asking because there are plenty of markdown dialects, such as the ones
>> supported by pandoc (and many more I guess). I'd like to experiment a
>> Jupyter writer in pandoc to be able to convert (as best as possible)
>> documents in Markdown or other formats to Jupyter notebooks, putting code
>> blocks into code cells and the rest in markdown cells.
>>
>> Thanks!
>> Bruno
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/1ddf1a4e-124c-4e92-a8ce-15a7a84eb536%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CANJQusWM6x0G2ugUeaVLmKosWjNB9SjdvM9%2Bq6KBNZVBW0anRw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpR848kz1dGzX7CkT0edEpTM9Kv%2Bot2RTPNN%3DLqs0P3TWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Moving nbmanager into Jupyter Github org?

[Brian Granger]

Yes, fully agree!

Sent from my iPhone

> On Nov 11, 2017, at 4:32 AM, Thomas Kluyver <tak...@gmail.com> wrote:
> 
> I see this thread as a lightweight mechanism that preserves the spirit of the 
> formal process - we get a consensus from the core developers before moving a 
> project into the Jupyter org. So far there seems to be a clear consensus in 
> favour of the move, so hopefully this will suffice.
> 
> I'm keen that we don't accumulating bureaucracy and formal 'processes' for 
> things like this - I've tried to work with Debian before, and the rules 
> around the project contributed to an unwelcoming environment where it was 
> hard to get anything done.
> 
> 
> 
>> On 10 November 2017 at 17:01, Damián Avila <damianav...@gmail.com> wrote:
>> I am OK to moving it, just I think we need to follow the guidelines: 
>> https://github.com/jupyter/governance/blob/master/newsubprojects.md#incorporation-of-an-existing-external-subproject
>> 
>> It is already incubated, so the proposal should be accepted quickly... I 
>> know it is probably a formality but still I think it makes sense to go that 
>> route.
>> 
>> Cheers.
>> 
>> 2017-11-10 12:53 GMT-03:00 Brian Granger <elliso...@gmail.com>:
>>> As a side point - we are adding these types of capabilities to the
>>> JupyterLab electron app, including smart searching for all the
>>> python+jupyter installations and envs on a system...
>>> 
>>> On Fri, Nov 10, 2017 at 7:52 AM, Brian Granger <elliso...@gmail.com> wrote:
>>> > +1
>>> >
>>> > On Fri, Nov 10, 2017 at 7:39 AM, Carol Willing <willi...@gmail.com> wrote:
>>> >> Sounds like a great plan for sustainable development. +1
>>> >>
>>> >> On Nov 10, 2017 7:02 AM, "MinRK" <benjami...@gmail.com> wrote:
>>> >>>
>>> >>> +1 to moving it to into Jupyter from me
>>> >>>
>>> >>> On Fri, Nov 10, 2017 at 3:58 PM, Thomas Kluyver <tak...@gmail.com> 
>>> >>> wrote:
>>> >>>>
>>> >>>> Hi all,
>>> >>>>
>>> >>>> Some time ago, I wrote nbmanager 
>>> >>>> (https://github.com/takluyver/nbmanager
>>> >>>> ), a small PyQt application to list running notebook servers and shut 
>>> >>>> them
>>> >>>> down. It has a steady trickle of people using it, or attempting to use 
>>> >>>> it
>>> >>>> and running into problems, but I only occasionally use it myself, and 
>>> >>>> I'm
>>> >>>> not maintaining it very well.
>>> >>>>
>>> >>>> One person who has worked on it recently is Philipp Angerer (Github 
>>> >>>> user
>>> >>>> flying-sheep), who has already adopted most of the maintenance of 
>>> >>>> IRkernel.
>>> >>>> He has accepted my offer to be a maintainer of nbmanager as well.
>>> >>>>
>>> >>>> It would feel slightly disingenuous to keep the repo under my own name 
>>> >>>> on
>>> >>>> Github while encouraging someone else to do most of the work, so I am
>>> >>>> proposing that we move it into the Jupyter Github org, and add Philipp 
>>> >>>> as a
>>> >>>> collaborator there. This would also reduce the bottleneck on any one 
>>> >>>> person,
>>> >>>> because other Jupyter developers could commit or add a new 
>>> >>>> collaborator.
>>> >>>>
>>> >>>> Are people happy with this plan? Or should we maintain it somewhere 
>>> >>>> else?
>>> >>>>
>>> >>>> Thomas
>>> >>>>
>>> >>>> --
>>> >>>> You received this message because you are subscribed to the Google 
>>> >>>> Groups
>>> >>>> "Project Jupyter" group.
>>> >>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> >>>> an
>>> >>>> email to jupyter+unsubscr...@googlegroups.com.
>>> >>>> To post to this group, send email to jupyter@googlegroups.com.
>>> >>>> To view this discussion on the web visit
>>> >>>> https://groups.google.com/d/msgid/jupyter/CAOvn4qiqioR_rvn2HEb%3

Re: [jupyter] Moving nbmanager into Jupyter Github org?

[Brian Granger]

As a side point - we are adding these types of capabilities to the
JupyterLab electron app, including smart searching for all the
python+jupyter installations and envs on a system...

On Fri, Nov 10, 2017 at 7:52 AM, Brian Granger <elliso...@gmail.com> wrote:
> +1
>
> On Fri, Nov 10, 2017 at 7:39 AM, Carol Willing <willi...@gmail.com> wrote:
>> Sounds like a great plan for sustainable development. +1
>>
>> On Nov 10, 2017 7:02 AM, "MinRK" <benjami...@gmail.com> wrote:
>>>
>>> +1 to moving it to into Jupyter from me
>>>
>>> On Fri, Nov 10, 2017 at 3:58 PM, Thomas Kluyver <tak...@gmail.com> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Some time ago, I wrote nbmanager (https://github.com/takluyver/nbmanager
>>>> ), a small PyQt application to list running notebook servers and shut them
>>>> down. It has a steady trickle of people using it, or attempting to use it
>>>> and running into problems, but I only occasionally use it myself, and I'm
>>>> not maintaining it very well.
>>>>
>>>> One person who has worked on it recently is Philipp Angerer (Github user
>>>> flying-sheep), who has already adopted most of the maintenance of IRkernel.
>>>> He has accepted my offer to be a maintainer of nbmanager as well.
>>>>
>>>> It would feel slightly disingenuous to keep the repo under my own name on
>>>> Github while encouraging someone else to do most of the work, so I am
>>>> proposing that we move it into the Jupyter Github org, and add Philipp as a
>>>> collaborator there. This would also reduce the bottleneck on any one 
>>>> person,
>>>> because other Jupyter developers could commit or add a new collaborator.
>>>>
>>>> Are people happy with this plan? Or should we maintain it somewhere else?
>>>>
>>>> Thomas
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups
>>>> "Project Jupyter" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an
>>>> email to jupyter+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to jupyter@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jupyter/CAOvn4qiqioR_rvn2HEb%3DEeaTWYfHKp2B%2BpveEBS0aPrUkS5-og%40mail.gmail.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Project Jupyter" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jupyter+unsubscr...@googlegroups.com.
>>> To post to this group, send email to jupyter@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jupyter/CAHNn8BV2_QhWe38M_XhXS2Xt3%2BZc9CFEsqCjXjE5%2B3GJ9XkEVQ%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAM3Vvhw9To2K4R0W60%3DG7G4hE3gGp%2BEUxX%2B1_Rcpkc9dTzsnnA%40mail.gmail.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgran...@calpoly.edu and elliso...@gmail.com



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRge0g0XMRShXXOP3iA4q4th%2BPyq1K8N1Op%3DrYDqn3MfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Help contribute to science and determine the future of exploratory data analysis and visualization t

[Brian Granger]

Thanks for sharing this! I definitely encourage anyone in the Jupyter
community to participate in this study. The research and software
coming out of Jeff's group at UW is actively being integrated into
JupyterLab so there is a very practical Jupyter-related impact in the
work.

Cheers,

Brian

On Thu, Nov 9, 2017 at 7:52 PM, Kanit Wongsuphasawat <kan...@gmail.com> wrote:
> Our team at University of Washington are conducting an interview study on
> exploratory data analysis and visualization tools. As we have been
> collaborating with Brian Granger on visualization tools like Vega-Lite,
> Altair, and Voyager, he suggests that we should post in Jupyter user groups
> as many people in this community would be a good fit.
>
> If you regularly perform exploratory data analysis as a part of your work,
> we would like to invite you to join our study!
>
> We are looking to conduct an interview for 45-minutes to 2 hours during
> November 8 to December 6 (in person for participants in Greater Seattle area
> or via a video conference otherwise).  In this interview, we will ask
> open-ended questions about your experience in analysis scenarios and, if
> possible, optionally share your analysis outcomes.  You will receive a $15
> Amazon.com gift card as a thank you for your participation. Participation in
> the study is completely voluntary. Any personally identifying information
> will be kept strictly confidential.
>
> If you are qualified and are interested in participating in this study,
> please answer this survey (https://goo.gl/forms/kBdddPCjDa9VBXWt2) to apply
> to join our study.  We will contact you to schedule an interview shortly if
> you are qualified for the interviews. Please  email us
> (kan...@cs.washington.edu and yl...@cs.washington.edu) if you have any
> questions.
>
> Sincerely,
>
> Kanit Wongsuphasawat, Graduate Student
> Yang Liu, Graduate Student
> Jeffrey Heer, Ph.D., Associate Professor
>
> Computer Science & Engineering
> University of Washington
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/439b1964-afba-4c90-8c12-adb399df3ebb%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTWux1z48eEv2188UNOsVZ4xY5Ct5uQdKLFiXAT84t1tQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Fork or Revert Kernel?

[Brian Granger]

Cool, thanks for posting Robert!

On Thu, Nov 2, 2017 at 6:10 PM, Robert Schroll
<rob...@thedataincubator.com> wrote:
> This is tangentially related at best, but several years ago, I worked on a
> project called Reinteract [1] that tried to do something similar.  Working
> at the AST level, we were able to identify 99% of the mutations that would
> occur, allowing Reinteract to save and rewind to checkpoints.
> Unfortunately, that last 1% proved to be essentially impossible to detect
> with this approach.
>
> I'm happy to discuss this further if there's interest, but I'll hold off on
> further thread hijacking for now.
>
> Robert
>
> [1] http://www.reinteract.org/
>
>
> On Nov 2 2017, at 4:16 pm, Brian Granger <elliso...@gmail.com> wrote:
>>
>> JupyterLab has a "Code Console" that is similar to this Scratchpad,
>> but allows more flexibility in terms of which kernel is used.
>>
>> As far as 1) and 2) are concerned, I don't know of any general way of
>> forking, rewinding a full runtime without full blown process level
>> checkpointing. I am guessing that would take you down a rabbit hole.
>> You could begin to explore some of the immutable namespace ideas from
>> my talk at UCSD though. But keep in mind, there a ton of subtleties in
>> getting that to work robustly (have to serialize state to disk to
>> avoid growing memory, not all objects are easy to serialize).
>>
>>
>>
>> On Thu, Nov 2, 2017 at 3:51 PM, Adam Rule <acr...@gmail.com> wrote:
>>
>> I am modifying Min's Scratchpad extension and am wondering if there is a
>> way
>> to make it so code executed in the scratchpad does not impact the main
>> notebook. As it is, if I mess with parameters in the scratchpad, it will
>> change those parameters in the notebook as both share the same kernel.
>> Would
>> it be possible to either:
>>
>> Fork the kernel to start a new one for risk-free experimenting (this seems
>> to break the one kernel per notebook paradigm)
>> Revert the kernel to a prior state when the scratchpad is closed?
>>
>> I'll look through the kernel management source code in the meantime.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/jupyter/7bc20957-5fc2-4442-97f2-aee3200d1660%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> -- br />Brian E. Granger
>> Associate Professor of Physics and Data Science
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgran...@calpoly.edu and elliso...@gmail.com
>>
>> -- br />You received this message because you are subscribed too the
>> Google Groups "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAH4pYpTAJuVamp4zaU2rcYDDZiZ-NVGMZLLZu2pCRFBPCsJwUQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/local-bc6edb9e-9f58%40mando.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQfUmiUjCrcsJn-F2MgvZj7rFfmy1fKo9mk_wNdYMpOKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Repo for exploring a debugger protocol + UI for Jupyter

[Brian Granger]

Hi all,

Wanted to let the community know that we have created a repo for
exploring an interactive debugger protocol and UI for Jupyter:

https://github.com/jupyter/debugger

We will be using this repo for discussions, research and prototypes of
the different pieces. If you are interested in debuggers for Jupyter,
we encourage you to join in!

Cheers,

Brian

-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSe8q%2BcCrCTGtX3LGuPekuc3oH3q9aYeEnEy%2BSz%3Drwz-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Fork or Revert Kernel?

[Brian Granger]

JupyterLab has a "Code Console" that is similar to this Scratchpad,
but allows more flexibility in terms of which kernel is used.

As far as 1) and 2) are concerned, I don't know of any general way of
forking, rewinding a full runtime without full blown process level
checkpointing. I am guessing that would take you down a rabbit hole.
You could begin to explore some of the immutable namespace ideas from
my talk at UCSD though. But keep in mind, there a ton of subtleties in
getting that to work robustly (have to serialize state to disk to
avoid growing memory, not all objects are easy to serialize).



On Thu, Nov 2, 2017 at 3:51 PM, Adam Rule  wrote:
> I am modifying Min's Scratchpad extension and am wondering if there is a way
> to make it so code executed in the scratchpad does not impact the main
> notebook. As it is, if I mess with parameters in the scratchpad, it will
> change those parameters in the notebook as both share the same kernel. Would
> it be possible to either:
>
> Fork the kernel to start a new one for risk-free experimenting (this seems
> to break the one kernel per notebook paradigm)
> Revert the kernel to a prior state when the scratchpad is closed?
>
> I'll look through the kernel management source code in the meantime.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/7bc20957-5fc2-4442-97f2-aee3200d1660%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTAJuVamp4zaU2rcYDDZiZ-NVGMZLLZu2pCRFBPCsJwUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] enlarge GUI's stop button

[Brian Granger]

Also, the stop button is bound to the "i i" (double press i in command
mode). In the browser we have fewer keyboard options available -
however, you should be able to customize that shortcut in the Help
menu -> Edit Keyboard shortcuts.

On Wed, Nov 1, 2017 at 1:08 PM, Brian Granger <elliso...@gmail.com> wrote:
> see discussion here:
>
> https://github.com/jupyter/notebook/pull/2965
>
>
>
> On Tue, Oct 31, 2017 at 1:55 PM, Camille Goudeseune <c...@uiuc.edu> wrote:
>> Can the GUI include the letters "stop" beside that button, just like the run
>> button?
>> That makes it a bigger target for the mouse.
>>
>> Or, can classic Visual Studio keyboard shortcuts Ctrl+F5 be bound to those
>> buttons?
>>
>> Optimize for frequent operations...
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/f5ba5e1c-c2d5-4b63-b08e-ffd020e13912%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgran...@calpoly.edu and elliso...@gmail.com



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSYjs0i%3D_xU%3DdsF14r7wZTT0RCvKySHyw5KkK1n6oDGmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] enlarge GUI's stop button

[Brian Granger]

see discussion here:

https://github.com/jupyter/notebook/pull/2965



On Tue, Oct 31, 2017 at 1:55 PM, Camille Goudeseune  wrote:
> Can the GUI include the letters "stop" beside that button, just like the run
> button?
> That makes it a bigger target for the mouse.
>
> Or, can classic Visual Studio keyboard shortcuts Ctrl+F5 be bound to those
> buttons?
>
> Optimize for frequent operations...
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/f5ba5e1c-c2d5-4b63-b08e-ffd020e13912%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTZQO2tw4r1iqXo2_F3ZVWOWA-yy-CRfr-yxJ%2BRW7sLmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: Any kernels with immutable namespaces

[Brian Granger]

Hi Doug!

Most Jupyter kernels that I know of have a persistent namespace that
is mutable - each new block of code is executed in that namespace and
can mutate its state. In python this is something like exec(code,
global_ns, local_ns).

I am looking for any examples where there is persistent state in the
kernel, but that state isn't mutable. The simplest model is a single
immutable namespace that is passed to each new block of code, similar
to the redux pattern:

run_code(old_state, code) -> new_state

But other patterns of immutable state are possible such as reactive
data flows. I am looking for any examples of immutable but persistent
kernel state.

On Sun, Oct 22, 2017 at 3:28 PM, Doug Blank  wrote:
> On Sunday, October 22, 2017 at 3:23:03 PM UTC-4, ellisonbg wrote:
>>
>> Hi all,
>>
>> Does anyone know of any Jupyter kernels that have an immutable
>> namespace that flows between blocks of code? I am looking at how pure
>> functional languages implement persistent state in Jupyter kernels.
>
>
> I'm not sure what you mean about "an immutable namespace that flows between
> blocks of code", but our Calysto Processing kernel has each cell as its own
> "sketch". Each cell is preprocessed by Processing, compiled by Java (to give
> good error messages), and then rendered by Javascript. Here is an example
> notebook:
>
> https://jupyter.brynmawr.edu/services/public/dblank/CS110%20Intro%20to%20Computing/2017-Fall/Notebooks/05-Movement.ipynb
>
> There is no persistent state between cells, but if I were to try to tackle
> that, I'd probably do something like beakerX's "auto translate" and use JSON
> as an intermediary form.
>
> -Doug
>
>>
>>
>> Cheers,
>>
>> Brian
>>
>> --
>> Brian E. Granger
>> Associate Professor of Physics and Data Science
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgra...@calpoly.edu and elli...@gmail.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/b2640b34-4791-4652-ad41-f09e7ccaaab5%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSWsWrru1go-OXCekt%2BgzssTHoefmcvns3%2BOakSv1JSkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Any kernels with immutable namespaces

[Brian Granger]

Hi all,

Does anyone know of any Jupyter kernels that have an immutable
namespace that flows between blocks of code? I am looking at how pure
functional languages implement persistent state in Jupyter kernels.

Cheers,

Brian

-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQU%3D_7ruS0XBmvUsgCu56KVSTGxxQ%3DHAC_PbccuMywmqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: Congratulations to Thomas Kluyver

[Brian Granger]

Thomas, many congrats on this recognition of your wide reaching, fantastic work!

On Sat, Oct 14, 2017 at 1:12 PM, Carlos Córdoba  wrote:
> Congrats Thomas!! Thanks for all your hard work in IPython/Jupyter, it's
> been a terrific contribution to all the Scientific Python community!
>
>
> Cheers,
> Carlos
>
> El 14/10/17 a las 06:22, Steven Silvester escribió:
>
> Congratulations Thomas!  Your contributions to and engagement with the open
> source community are astounding.
>
>
> On Thursday, October 12, 2017 at 2:21:42 PM UTC-5, Carol Willing wrote:
>>
>> Please join me in thanking Thomas for all that he does for the Python and
>> Jupyter communities. Congrats on the Python/PSF Community Service Award. We
>> are so happy for you.
>>
>>
>> http://pyfound.blogspot.com/2017/10/thomas-kluyver-community-service-award.html
>>
>>
>>
>>
>> Carol Willing
>>
>> Research Software Engineer
>> Project Jupyter at Cal Poly State University, San Luis Obispo
>> @willingc on GitHub and @willingcarol on Twitter
>> will...@gmail.com and cawi...@calpoly.edu
>>
>> Signature Strengths
>> Empathy - Relator - Ideation - Strategic - Learner
>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/2d3a8cf8-21fd-4a7f-9d11-d15665e3b620%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/5debba49-dd61-4feb-13da-15e18635263e%40gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRXzsUjNkao2vWT8M%3DY5d8VwOhz36HrivmdwfDyZmXP_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter Notebook 5.2.0

[Brian Granger]

Congrats everyone!

On Fri, Oct 13, 2017 at 10:55 AM, Grant Nestor  wrote:
> We are pleased to announce the release of Jupyter Notebook 5.2.0. This is a
> minor release that includes mostly bug fixes and improvements with the
> notable addition of RTL (right-to-left) support.
>
> You can install the new version of the notebook now using pip:
>
> pip install --upgrade notebook
>
> Or conda (it may be a few days before packages are available):
>
> conda upgrade notebook
>
> Changelog
>
> Make all files in the dashboard editable by default and provide a whitelist
> of viewable file extensions (#2911).
> Ensure that the root directory is not hidden (#2907).
> Fix CodeMirror styling issue (#2880).
> Update error handling on APIHandlers (#2853).
> Upgrade xterm.js to 2.9.2 (#2849).
> Add Chinese translations (depends on upcoming UI implementation) (#2804).
> Allow for simpler customization of output_prompt in custom.js (#2774).
> Use RFC5987 encoding for filenames (#2767).
> Add path to the resources metadata (#2753).
> Make extraKeys consistent between notebook and editor views (#2745).
> Add RTL (right-to-left) support (#2357).
>
> Credits
>
> This release has been a team effort and we would like to thank the following
> 23 people who contributed:
>
> Matthias Bussonnier (Carreau)
> Alex Rothberg (cancan101)
> Damian Avila (damianavila)
> Gabriel Nützi (gabyx)
> Grant Nestor (gnestor)
> Douglas Hanley (iamlemec)
> John B Nelson (jbn)
> Josh Barnes (jcb91)
> jianzi123 (jianzi123)
> Min RK (minrk)
> M Pacer (mpacer)
> Michael Scott Cuthbert (mscuthbert)
> Matej Urbas (mupdt982)
> Peter Parente (parente)
> Roland Weber (rolweber)
> Samar Sultan (samarsultan)
> Thomas Kluyver (takluyver)
> Till Hoffmann (tillahoffmann)
> Vidar Tonaas Fauske (vidartf)
> Jacob Niehus (wilywampa)
> Yang-Le Wu (yangle)
> Yuvi Panda (yuvipanda)
> Gao, Xiang (zasdfgbnm)
>
> We look forward to your feedback and contributions!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/7af32d02-e450-449a-bf36-6ade9c282e06%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQ-bDTik0cnCw7Q8FQB_3MDWU3Kq_euhUMXKi5ZM60C9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Introducing the binderhub-dev mailing list

[Brian Granger]

Thanks Yuvi!

On Tue, Oct 10, 2017 at 9:06 AM, Yuvi Panda  wrote:
> Heya!
>
> With the increasing number of people involved in the development of
> beta.mybinder.org, we've created a mailing list to coordinate and be
> more transparent about development activities.
>
> https://groups.google.com/forum/#!forum/binderhub-dev is the new
> mailing list. Expect discussions about the social and technical
> aspects of developing and building binderhub. Please keep this list
> focused on **development** activities.
>
> **Support** questions for getting your repository working on
> mybinder.org should be filed at https://github.com/jupyterhub/binder
>
> We also have a gitter channel where most public discussion happens:
> https://gitter.im/jupyterhub/binder. Three repositories also have
> active discussion and work going on in them:
>
> - http://github.com/jupyterhub/binderhub Core implementation of a binderhub
> - http://github.com/jupyter/repo2docker Utility for converting repos
> to docker images
> - http://github.com/jupyterhub/mybinder.org-deploy/ Deployment
> configuration specific to mybinder.org
>
> Moving forward, we're committed to making binderhub development
> inclusive and productive. Subscribe, participate, and share your
> thoughts on how we can make it easy for you to be involved!
>
> Yuvi Panda
> (on behalf of the BinderHub team: MinRK, Carol Willing & Chris Holdgraf)
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CAFw%3DySjzvuxMBGfL7NnsuvxN0tG6FODEgX5%3DQm77Y1ygN9e99Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpStZ9zskd1WuYG9xbCn0LYOAxeocPMUrhsZesWLvp%2BtDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] [ANN] JupyterHub 0.8

[Brian Granger]

Nice! Many congrats to the JupyterHub team!

On Tue, Oct 3, 2017 at 12:55 PM, MinRK  wrote:
> We’ve just released JupyterHub 0.8 to PyPI. Tagged Docker images and
> conda-forge should propagate shortly.
>
> This is a big one with lots of fixes and exciting improvements. See the blog
> post for an overview and the changelog for more details.
>
> You can upgrade with:
>
> pip install jupyterhub==0.8.0
>
> There are significant changes to internal communication between the Hub and
> single-user servers, so it is important when you upgrade JupyterHub to
> upgrade the version inside your user environments as well. This means adding
> a line like
>
> pip install jupyterhub==0.8.0
>
> to your Dockerfiles if you are using a container-based deployment to ensure
> that the Hub and single-user servers have the same version.
>
> Thanks to everyone who helped put this release together.
>
> -Min
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAHNn8BWJsUbPwQDybkWYCFBEx74ZVP_3Ggukxe-tpaO4Azb2gQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQfvSEd2pLu74Ldz%3DDquhUm0NoVBnuPTmMzxr_8TaLVog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] ipywidgets 7.0.0

[Brian Granger]

Many congratulations to the entire ipywidgets team, especially the
many new contributors! This is a huge release!

On Fri, Aug 18, 2017 at 5:40 PM, Jason Grout  wrote:
> We are pleased to announce the ipywidgets 7.0.0 release, along with the
> corresponding python package widgetsnbextension 3.0.0 and the corresponding
> npm packages @jupyter-widgets/base 1.0.0, @jupyter-widgets/controls 1.0.0,
> and @jupyter-widgets/output 1.0.0. We also have released compatible versions
> of several other related npm packages, including
> @jupyter-widgets/html-manager, @jupyter-widgets/jupyterlab-manager, and
> @jupyter-widgets/schema.
>
> The ipywidgets 7.0.0 and widgetsnbextension 3.0.0 releases have been
> uploaded to PyPI, and you can install them via pip now:
>
> pip install ipywidgets
> jupyter nbextension enable --sys-prefix --py widgetsnbextension
>
> We are working on uploading them to conda-forge as well.
>
> Please see the changelog
> (https://github.com/jupyter-widgets/ipywidgets/blob/master/docs/source/changelog.md#70)
> for a high-level list of changes.
>
> It has been 171 days since the ipywidgets 6.0 release. In this release, we
> closed 142 issues and 259 pull requests (see
> https://github.com/jupyter-widgets/ipywidgets/milestone/12?closed=1). We had
> 989 non-merge commits and 261 merges, for a total of 1250 commits
> (https://github.com/jupyter-widgets/ipywidgets/compare/6.0.0...7.0.0).
>
> We thank the following 19 individuals (listed in alphabetical order) who
> submitted a commit to the 7.0 release, and we especially congratulate the 13
> new contributors.
>
> * Benjamin Ragan-Kelley
> * Charnpreet Singh (new contributor)
> * Dave Hirschfeld
> * Fermi Paradox (new contributor)
> * Jan Lübbe (new contributor)
> * Janki Akhani (new contributor)
> * Jason Grout
> * Kiko Correoso (new contributor)
> * Luke Zoltan Kelley (new contributor)
> * Maarten Breddels
> * Maksim Noy (new contributor)
> * Matthew Craig
> * Nick Fernandez (new contributor)
> * Pascal Bugnion (new contributor)
> * Ribamar Santarosa (new contributor)
> * Rick Teachey (new contributor)
> * Scott Sievert (new contributor)
> * Sylvain Corlay
> * Vidar Tonaas Fauske (new contributor)
>
> Thanks,
>
> The ipywidgets team
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAPDWZHwAacMchZ8SoGiw6WducB%3DWYSSn0ejCCZb6dYE5aZdMwQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRcejO_6gTmQkxajpTiHHQ4dWCze7-JCv3JUCdUaFR01A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] [ANN] nbformat 4.4.0

[Brian Granger]

Hmm, I think there has been a significant miscommunication about the
purpose of the `source_hidden` and `outputs_hidden` metadata.

Here is a summary of my understanding:

https://github.com/jupyterlab/jupyterlab/issues/2740

I remember us specifically talking as a groupt at the in person
meeting and it being said that the entire purpose of persisting this
metadata was so that nbconvert and other tools could work with it.
nbconvert may have different ways of hiding content based on tags, but
I don't see why it wouldn't respect this notion.

More importantly, metadata state that is stored in the document can't
be used as the view state as it should not be shared between users in
the real-time collab setting. My comments in the above issue address
these subtleties. Most importantly, the PR that implemented these
flags does not mention the restrictions about these not being used in
nbconvert (https://github.com/jupyter/nbformat/pull/94/files).

I realize you have been asking for feedback on how nbconvert handles
these things and I apologize my time has been so sparse.

On Sun, Aug 20, 2017 at 8:36 PM, M Pacer  wrote:
> We are pleased to announced the release of nbformat 4.4.0.
>
> On top of the usual doc improvements and bug fixes, this minor release does
> a few things especially worthy of note by the wider Jupyter community.
>
> It introduces in cell metadata the metadata.jupyter namespace for jupyter
> official metadata fields, and includes the source_hidden and outputs_hidden
> fields for front-ends to store whether input or output is hidden when
> viewing a notebook. These fields will not be used to hide input or outputs
> on export using nbconvert.
>
> The nbformat.validate function now has a new optional argument
> relax_add_props, which when set to true will allow validating a notebook
> that has properties in addition to those required by nbformat. This is
> particularly useful for the creation of intermediate representations in
> applications such as nbconvert.
>
> You can now assign dict-like values to attributes on nbformat.NotebookNode
> objects and they will be converted to be NotebookNode objects. This also
> works if you update a NotebookNode object with a dict-like object (or keys
> with dict-like values).
>
> Please see the change-log for more information:
> http://nbformat.readthedocs.io/en/latest/changelog.html#id1
>
> The conda-forge update is underway
> (https://github.com/conda-forge/nbformat-feedstock/pull/8).
>
> We thank the following 7 authors who contributed 44 commits to this release.
>
> * Benjamin Ragan-Kelley
> * Brian E. Granger
> * Jason Grout
> * Kyle Kelley
> * M Pacer
> * madhu
> * Thomas Kluyver
>
> Cheers,
> The nbformat team
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAM3SX44LyRYfuuyoSvbYEqbUcenC-0mfox5EW3GzJ%2B8LMPKo3w%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTZByHB%3D4Ef-Uhxtzf2TXCDaoR_h84EtyueKUSyNgP%3DDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: [jupyter-education] nbgrader v0.5.2 released

[Brian Granger]

Very nice!

On Thu, Jul 20, 2017 at 11:55 AM, Jessica B. Hamrick
 wrote:
> Hi all,
>
> nbgrader version 0.5.2 has been released. This is a bugfix release, with
> most of the bugs being discovered and subsequently fixed by the sprinters at
> SciPy 2017! A huge thank you to everybody who contributed at sprints; we
> were able to find and fix a lot of edge cases that crept into 0.5.0.
>
> The following PRs were merged:
>
> PR #852: Fix spelling wordlist, again
> PR #850: Include extension with feedback template filename
> PR #848: Add links to the scipy talk
> PR #847: Fix html export config options to avoid warnings
> PR #846: Disallow negative point values
> PR #845: Don't install assignment list on windows
> PR #844: Reveal ids if names aren't set
> PR #843: Update spelling wordlist
> PR #840: Avoid extension errors when exchange is missing
> PR #839: Always raise on convert failure
> PR #837: Report mismatch extension versions
> PR #836: Add documentation for course_id and release
> PR #835: DOC: correct Cell Toolbar location
> PR #833: Include quickstart .ipynb header
> PR #831: Fix typo on Managing assignment docs
> PR #830: Print out app subcommands by default
> PR #825: Add directory structure example
> PR #824: Add FAQ sections
> PR #823: Typo fix.
> PR #819: Update install instructions
> PR #816: Add jupyter logo
> PR #802: Fix bug with autograding when there is no timestamp
>
> Thanks to the following users who submitted PRs or reported issues that were
> fixed for the 0.5.2 release:
>
> arcticbarra
> BjornFJohansson
> hetland
> ixjlyons
> jhamrick
> katyhuff
> ksunden
> lgpage
> ncclementi
> Ruin0x11
>
> Cheers,
> Jess
>
> --
> You received this message because you are subscribed to the Google Groups
> "Teaching with Jupyter Notebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter-education+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter-educat...@googlegroups.com.
> Visit this group at https://groups.google.com/group/jupyter-education.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter-education/CALUXcBwcyfhnX1CumOxyCLC4fCyzv68gW6P1gww7%2B3fmt-kPog%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpS0s4Juz70QM3eD%2B-_MrfO74dNnjB0HfFo5_y-T%3DPZkaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: [jupyter-education] nbgrader v0.5.0 released

[Brian Granger]

Jess,

Many congrats on this release, I look forward to using it!

Cheers,

Brian

On Sat, Jul 8, 2017 at 1:36 PM, Jessica B. Hamrick
 wrote:
> Hi all,
>
> I am excited to announce that the nbgrader v0.5.0 has been released! You can
> install it via pip:
>
> pip install -U nbgrader
>
> And very shortly the conda package will be available on conda-forge as well.
>
> nbgrader version 0.5.0 is another very large release with some very exciting
> new features! The highlights include:
>
> The formgrader is now an extension to the notebook, rather than a standalone
> service.
> The formgrader also includes functionality for running `nbgrader assign`,
> `nbgrader release`, `nbgrader collect`, and `nbgrader autograde` directly
> from the browser.
> A new command `nbgrader zip_collect`, which helps with collecting assignment
> files downloaded from a LMS.
> Hidden test cases are now supported.
> A lot of functionality has moved into standalone objects that can be called
> directly from Python, as well as a high-level Python API in
> `nbgrader.apps.NbGraderAPI` (see
> http://nbgrader.readthedocs.io/en/latest/api/high_level_api.html ).
> A new **Validate** notebook extension, which allows students to validate an
> assignment notebook from the notebook itself (this is equivalent
> functionality to the "Validate" button in the Assignment List extension, but
> without requiring students to be using the Assignment List).
> A new command `nbgrader db upgrade`, which allows you to migrate your
> nbgrader database to the latest version without having to manually execute
> SQL commands.
> New cells when using the Create Assignment extension will automatically
> given randomly generated ids, so you don't have to set them yourself.
>
> - You can assign extra credit when using the formgrader.
>
> **Important**: Users updating from 0.4.x to 0.5.0 should be aware that they
> will need to update their nbgrader database using `nbgrader db upgrade` and
> will need to reinstall the nbgrader extensions (see
> http://nbgrader.readthedocs.io/en/latest/user_guide/installation.html ).
> Additionally, the configuration necessary to use the formgrader with
> JupyterHub has changed, though it is now much more straightforward (see
> http://nbgrader.readthedocs.io/en/latest/configuration/jupyterhub_config.html
> ).
>
> The full list of merged PRs includes:
>
> - PR #789: Fix more inaccurate nbextension test failures after reruns
> - PR #788: Fix inaccurate nbextension test failures after reruns
> - PR #787: Fix slow API calls
> - PR #786: Update documentation for nbgrader as a webapp
> - PR #784: Fix race condition in validate extension tests
> - PR #782: Implement nbgrader as a webapp
> - PR #781: Assign missing notebooks a score of zero and mark as not needing
> grading
> - PR #780: Create a new high-level python API for nbgrader
> - PR #779: Update the year!
> - PR #778: Create and set permissions for exchange directory when using
> `nbgrader release`
> - PR #774: Add missing config options
> - PR #772: Standalone versions of nbgrader assign, autograde, and feedback
> - PR #771: Fix mathjax rendering
> - PR #770: Better cleanup when nbconvert-based apps crash
> - PR #769: Fix nbgrader validate globbing for real this time
> - PR #768: Extra credit
> - PR #766: Make sure validation works with notebook globs
> - PR #764: Migrate database with alembic
> - PR #762: More robust saving of the notebook in create assignment tests
> - PR #761: Validate assignment extension
> - PR #759: Fix nbextension tests
> - PR #758: Set random cell ids
> - PR #756: Fix deprecations and small bugs
> - PR #755: Fast validate
> - PR #754: Set correct permissions when submitting assignments
> - PR #752: Add some more informative error messages in zip collect
> - PR #751: Don't create the gradebook database until formgrader is accessed
> - PR #750: Add documentation for how to pass numeric ids
> - PR #747: Skip over students with empty submissions
> - PR #746: Fix bug with --to in custom exporters
> - PR #738: Refactor the filtering of existing submission notebooks for
> formgrader
> - PR #735: Add DataTables functionality to existing formgrade tables
> - PR #732: Fix the collecting of submission files for multiple attempts of
> multiple notebook assignments
> - PR #731: Reset late submission penalty before checking if submission is
> late or not
> - PR #717: Update docs regarding solution delimeters
> - PR #714: Preserve kernelspec when autograding
> - PR #713: Use new exchange functionality in assignment list app
> - PR #712: Move exchange functionality into non-application classes
> - PR #711: Move some config options into a CourseDirectory object.
> - PR #709: Fix formgrader tests link for 0.4.x branch (docs)
> - PR #707: Force rerun nbgrader commands
> - PR #704: Fix nbextension tests
> - PR #701: Set proxy-type=none in phantomjs
> - PR #700: use check_call for extension installation in tests
> - PR #698: Force phantomjs service 

Re: [jupyter] How to share a Jupyter installation for team notebook development

[Brian Granger]

Jean,

Thanks for the feedback! The pain you are feeling around collaboration
isn't unique. We are hearing the same things from many users and that
feedback is strongly driving our roadmap...but it takes time...years
in many cases to build a robust architecture that supports these
things. I realize that telling you "we are building things...some day
soon..." doesn't help you ability to get things today. But we do
appreciate your sharing about your usage case and experiences.

Cheers,

Brian

On Tue, Jun 6, 2017 at 6:54 PM, Jean Bigboute  wrote:
> Matthias and Team:
>
> On Tuesday, June 6, 2017 at 5:04:29 PM UTC-7, Matthias Bussonnier wrote:
>>
>> On Tue, Jun 6, 2017 at 4:12 PM, Jean Bigboute  wrote:
>> > Thank you for posting this and I hope you are successful.  As an
>> > occasional Jupyter user, I have struggled to understand its use for
>> > collaborative work when so much depends on future developments and
>> > additional infrastructure.  In my work environment we can't deploy IT
>> > services such as servers, containers etc. on our own.  We don't always have
>> > access to help sites either.  It is hard to know when to push and when to
>> > punt.  I don't feel so alone any more.
>>
>> The usage for collaborative work should become easier soon. We had our
>> dev meeting last week, and a version that allow some[1] syncing  via
>> google drive is almost ready (Ian did and does a fantastic job). You
>> will probably see that in JupyterLab in one of the next releases (at
>> least as an extension). ...
>
>
>
> Thanks for your prompt response.  With due respect, I would like to point
> out that Google Drive doesn't solve the problem.  In corporate environments
> where proprietary data and algorithms are at stake, it is highly unlikely
> that users will be allowed access to Google Drive, Github, NBViewer,
> StackOverflow, etc.  That is certainly true with my employer so I can only
> post completely generic questions and then again from my own account.  In
> the present IT security environment (which is only going to get more
> restrictive) any type of added service requires multiple levels of scrutiny
> and review all tied into business cases.  Bypassing the system or attempting
> to do so will be detected quickly and the people responsible will get fired.
> Unless the product or service is incredibly compelling (see below) no one
> will go through the effort to get a product approved because the odds of
> success are practically zero.
>
> Additionally, I looked up JupyterLab just now and read that
> "JupyterLab computational environment. This is a very early preview, and is
> not suitable for general usage yet. "
> This has been the case for quite some time.
>
>>
>> Finding the right balance between consumers of Jupyter that want to
>> deploy that on large number of nodes with hundreds of users – ...
>
> [deletia]
>>
>>
>> The documentation can definitively get improvement – and as you might
>> have seen in an earlier mail Jessica is starting to work with us on
>> that and we are thrilled – but we can't cover all the ground. We also
>> tend to assume more and more that people have internet to get help if
>> you have an interest if having our docs offline and we don't provide a
>> link please open an issue and we'll try to find time to make that
>> happen. If you have experience in deploying in a difficult environment
>> and have manage to go around some pain point, please let us know – or
>> even better make a PR against our documentation. We'd love to have a
>> clearer way of expressing the advantages drawback of each deployment
>> but so far didn't had the time to sit down and write these as things
>> are moving really fast even for us.
>
>
> And this is the key point.  I have been following IPython then Jupyter now
> Jupyter +Lab and +Hub since about 2014.  The pace of developments is
> incredibly fast and I admire the team for doing so much.  But, I think the
> mindset is very much from academia.  I love academia, its ethos, and the
> exuberance but Jupyter is now fully promoting into other areas which have
> very different cultures and needs.  Documentation, user testing, stability,
> self-containment,... these are all important and I don't think are being
> given sufficient consideration.  There's a fascinating blogpost on making
> Jupyter Notebooks more reproducible:
>
> https://jakevdp.github.io/blog/2017/03/03/reproducible-data-analysis-in-jupyter/
>
> The author uses Github as a repository and a standalone text editor among
> other tools to accomplish this.  In one of the comments, he remarks "I agree
> that collaborating on notebooks is tough. I mostly avoid it, and instead
> collaborate on plain-text documents like markdown and code files."  Then, he
> recommends the nbdime project as another workaround.  I bring him into this
> discussion because I think he is incredibly smart, an advocate for the
> project, highly experienced with the tool,  and yet 

Re: [jupyter] Syncronize Code Between Jupyter and External Scripts

[Brian Granger]

I think the best way to start playing with this is to build it as an
extension, and use notebook metadata that tracks separate file should
be pointed to by a given cell. I completely agree this is an good
usage case.

On Sat, Jun 3, 2017 at 11:19 AM, Utkonos  wrote:
> I have been running into the following problem with regards to developing in
> Jupyter and then deploying the code elsewhere. The code as deployed may have
> a bug or change that needs to occur, and then the code from the cell where
> it was located in the Jupyter notebook is now different and out of sync. I
> would like to know how to keep code in a cell synchronized with code outside
> in another file. I found the following question on StackOverflow that
> pertains to this problem exactly:
> https://stackoverflow.com/questions/38770604/synchronizing-code-between-jupyter-ipython-notebook-script-and-class-methods
>
> I will try this method of workflow, but I am curious whether there is a
> better mousetrap out there.
>
> Here is my alternative, and I'd like to know the feasibility of it and
> whether it's a good idea or not:
>
> There are multiple types of cell in Jupyter, and they behave differently. I
> am proposing a new type of cell called "Linked Snippet". A linked snippet
> cell would initially have a start and end line number and a file path. As
> long as the user the notebook is running as has write access the file path,
> the lines of code would be pulled into the cell. This code would be editable
> in jupyter, but would have the option of saving the contents of the cell and
> replacing the code between the two line numbers in the external file. This
> means no cells can overlap line numbers, and this would need to be enforced
> properly in Jupyter. Ideally, this would be bi-directional, and if the code
> in the external file changed, Jupyter would offer the user a chance to
> reload the cell before running. It also may need to change the line numbers
> that are syncronized at this point to make sure that the expected code is
> loaded into the cell.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/ae6819f5-f422-43aa-b7bf-0ba63bc523cd%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTGeiAUkKbSE6efow10_2wjZCpt7%2BS1qof4-GFgT%2Bo8vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] [ANN] nbconvert 5.2.1 release

[Brian Granger]

Many congrats Mike!

On Fri, May 26, 2017 at 5:31 AM, Damián Avila  wrote:
> Congrats on the release Michael !!
>
> Cheers.
>
> 2017-05-26 1:03 GMT-03:00 Matthias Bussonnier
> :
>>
>> Thanks ! That's great congratulation on the release !
>>
>> --
>> M (the other one)
>>
>> On Thu, May 25, 2017 at 8:06 PM, Michael Pacer 
>> wrote:
>> > We are pleased to announce the release of nbconvert 5.2.1. Nbconvert is
>> > the
>> > tool you need to do things with your notebooks (after they are written).
>> >
>> > # Installation
>> > pip install -U nbconvert
>> >
>> > # Major features
>> >
>> > In this release (along with the usual bugfixes and documentation
>> > improvements, which are legion) we have a few new major features that
>> > have
>> > been requested for a long time:
>> >
>> > ## Global Content Filtering
>> >
>> > You now have the ability to remove input or output from code cells,
>> > markdown
>> > cells and the input and output prompts. The easiest way to access all of
>> > these is by using traitlets like TemplateExporter.exclude_input = True
>> > (or,
>> > for example HTMLExporter.exclude_markdown = True if you wanted to make
>> > it
>> > specific to HTML output). On the command line if you just want to not
>> > have
>> > input or output prompts just use --no-prompt.
>> >
>> > ## Execute notebooks from a function
>> >
>> > You can now use the executenb function to execute notebooks as though
>> > you
>> > ran the execute preprocessor on the notebooks. It returns the standard
>> > notebook and resources options.
>> >
>> > ## Remove cells based on regex pattern
>> >
>> > This removes cells based on their matching a regex pattern (by default,
>> > empty cells). This is the RegexRemovePreprocessor.
>> >
>> > ## Script exporter entrypoints for nonpython scripts
>> >
>> > Now there is an entrypoint for having an exporter specific to the type
>> > of
>> > script that is being exported. While designed for use with the IRkernel
>> > in
>> > particular (with a script exporter focused on exporting R scripts) other
>> > non-python kernels that wish to have a language specific exporter can
>> > now
>> > surface that directly.
>> >
>> > # Credits
>> >
>> > This release has been larger than previous releases. In it 33 authors
>> > contributed a total of 546 commits.
>> >
>> > Many thanks to the following individuals who contributed to this release
>> > (in
>> > alphabetical order):
>> >
>> > * Adam Chainz
>> > * Andreas Mueller
>> > * Bartosz T
>> > * Benjamin Ragan-Kelley
>> > * Carol Willing
>> > * Damián Avila
>> > * Elliot Marsden
>> > * Gao, Xiang
>> > * Jaeho Shin
>> > * Jan Schulz
>> > * Jeremy Kun
>> > * Jessica B. Hamrick
>> > * John B Nelson
>> > * juhasch
>> > * Livia Barazzetti
>> > * M Pacer
>> > * Matej Urbas
>> > * Matthias Bussonnier
>> > * Matthias Geier
>> > * Maximilian Albert
>> > * Michael Scott Cuthbert
>> > * Nicholas Bollweg
>> > * Paul Gowder
>> > * Paulo Villegas
>> > * Peter Parente
>> > * Philipp A
>> > * Scott Sanderson
>> > * Srinivas Reddy Thatiparthy
>> > * Sylvain Corlay
>> > * Thomas Kluyver
>> > * Till Hoffmann
>> > * Xiang Gao
>> > * YuviPanda
>> >
>> > Enjoy converting!
>> >
>> > Cheers,
>> > M
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Project Jupyter" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to jupyter+unsubscr...@googlegroups.com.
>> > To post to this group, send email to jupyter@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/jupyter/CAM3SX44t_fxfwb9JMwPcb9_3rQQHnikXAdAkbkV9aBuKYY3DCQ%40mail.gmail.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CANJQusVRqrk6SbH147p%3DzAp7vcY-DuQY%2BAV-QqA8FnGHrUv_Wg%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Damián Avila
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAH%2BmRR2krEjGJKRWGnt_xt8%2B4kVr%2B5FySRA-6P%2BBjtB5ZsPwAw%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State 

Re: [jupyter] Jupyter Notebook Frontend Extension wait for other Frontend Extension

[Brian Granger]

Yes, the classic notebook is not really setup for multiple runtime
extensions to resolve their runtime dependencies. This dependency
resolution is independent of the code loading on the page through
require.js. We have solved these things with the new extension system
in JupyterLab, but doing it well takes a huge amount of work and would
break the classic notebook APIs. It is my opinion that we are better
off keeping the classic notebook as is in this respect and relying on
JupyterLab when these things are needed.

On Thu, May 18, 2017 at 7:26 AM, Zelphir Kaltstahl
 wrote:
> Hi,
>
> I am writing some extensions which I need. The extensions have different
> purposes, but I'd like to ensure, that one of them has run before the other
> ones are run.
>
> What is a good way to do this? (no busy wait if not necessary)
>
> In each of the extensions I am listening for the notebook to be loaded like
> this:
>
>
> /// BEGIN
> function load_ipython_extension() {
> if (Jupyter.notebook !== undefined &&
> Jupyter.notebook._fully_loaded) {
> if (!initialized) {
> init();
> }
> } else {
> if (!initialized) {
> events.on('notebook_loaded.Notebook', () => {
> init();
> });
> }
> }
> }
> /// END
>
> Then in init happens the actual work.
> This was a practice suggested in some issue on Github and I already adopted
> that, but how can I be sure that extension A runs before extensions B, C and
> D, regardless of the specifics of what they do? Is there some event I could
> listen to, which contains the name of the extension? Maybe something like:
>
> /// BEGIN
> events.on('extension_loaded.ExtensionName')
> /// END
>
> Or a simple way to introduce such an event myself, without changing the
> notebook source code itself, maybe some generic event sending, where I can
> put in any name I want for the event and then listen for that in the other
> extensions?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/926c0539-e9a1-43d2-aad7-b3128df2936d%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRoOqJxvJcFpZs0csnPKdfemv77L7EOS6ijStURzeuB_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter Notebook Mobile Experience Study

[Brian Granger]

Thanks, Cameron!

On Tue, Apr 25, 2017 at 9:32 AM, Cameron Oelsen  wrote:
> Hey everyone!
>
> Over the next week or two, I am going to be conducting a study on how the
> Jupyter Notebook / JupyterLab should function in a mobile app. If you use
> the Notebook or JupyterLab and are available to answer some questions over
> the phone next week about your usage, reply to this thread with an email I
> could reach out to you with.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/ee108668-93a9-4c4b-8478-b6994e1342e8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRtG80-0%2BeGEPMn9nUv-52PZ_oOBwYHVzrDPACugmyZNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Transportation Data Challenge (May 2-3, Seattle, WA)

[Brian Granger]

Very cool!!!

On Fri, Apr 21, 2017 at 10:30 AM, Ian Rose  wrote:
> Hi Jupyter community,
>
> This is both an advertisement for an event and a request for information.
> The NSF-sponsored West Big Data Innovation Hub is hosting a series of
> workshops/hackathons focused on transportation and pedestrian safety over
> the next few months:
> https://www.bigdatahubs.io/
> The launch event for this series will be in Seattle at UW on May 2-3, and I
> encourage anyone from the community who is interested in transporation,
> urban data, and livable cities to RSVP if you can make it:
> https://bit.ly/Seattle0502
>
> Now the request for information: Is anybody aware of cool projects using
> Project Jupyter for analysis of transit/transportation data (especially as
> results to pedestrian safety)? I will be attending the workshop as a Jupyter
> representative, and it would be nice to be able to advertise (with proper
> attribution, of course) any work that the community is doing in this space.
>
> Best,
> Ian
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/870efffb-8d0d-4083-b174-778a6bb323bd%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpR1hWtU8G_CRU4yO_3yF%2BWLWjCW0rUtVW9_4J40FTZ02A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] newbie how to reflow comments?

[Brian Granger]

+1 fully agree!

I have opened an issue on the JupyterLab repo where we would implement this:

https://github.com/jupyterlab/jupyterlab/issues/2056

On Tue, Apr 18, 2017 at 12:18 PM, Andy Davidson
 wrote:
> Hi
>
> One features I mis from R-studio is the ability to reflow comments. For
> example lets say I paste the following comment in a code cell
>
> "This dataset checks that your code always picks the first-occurring
> Profile-most Probable k-mer in a given sequence of Dna. In the first
> sequence (“GCCCAA”), “GCC” and “CCA” are both Profile-most Probable k-mers.
> However, you must return “GCC” since it occurs earlier than “CCA”. Thus, if
> the first sequence of your output is “CCA”, this test case fails your code.”
>
> After “reflow” the comment looks like
>
> # test data set 1
> # This dataset checks that your code always picks the first-occurring
> # Profile-most Probable k-mer in a given sequence of Dna. In the first
> # sequence (“GCCCAA”), “GCC” and “CCA” are both Profile-most Probable
> # k-mers. However, you must return “GCC” since it occurs earlier than
> # “CCA”. Thus, if the first sequence of your output is “CCA”, this test
> # case fails your code.
>
>
> Now if I go through and edit the commented section all I have to is
> ‘re-flow’ and it will reformat my comments so that no line is more than a
> fixed length
>
> Kind regards
>
> Andy
>
> P.s. I am using a mac. Hopefully their is a keyboard short cut
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/D51BB4A3.572D9%25Andy%40SantaCruzIntegration.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRYoKGa7J91LuyUQdu5OT%2BnHQE%3DDYKZNEW6dmi6-_5StQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Jupyter JVM Repr

[Brian Granger]

Great!

On Thu, Apr 6, 2017 at 1:39 PM, Kyle Kelley  wrote:
> It is now done.
>
> https://github.com/jupyter/jvm-repr is now live! Thanks all.
>
> On Thu, Apr 6, 2017 at 7:13 AM, Damián Avila  wrote:
>>
>> > If we have a steering council member sponsoring/facilitating it, and
>> > there is an active community working on it, then I'm +1 to giving it a repo
>> > under the Jupyter github org. Thanks Kyle and everyone involved!
>>
>> I second that.
>>
>> 2017-04-06 0:55 GMT-03:00 s...@draves.org :
>>>
>>> Thank you Ryan this library is a great idea. How about we discuss this
>>> type/class question on the new issue tracker after it gets created?
>>>
>>> On Wed, Apr 5, 2017 at 11:03 PM, 'Ryan Blue' via Project Jupyter
>>>  wrote:

 The com.github.jupyter group does come from jitpack. If there's a better
 way to publish Jars from the Jupyter organization, I'm all for that.
 Otherwise, I think the simplicity of jitpack is worth the trade-off of
 having a weird groupId.

 On the wrapper class, the choice of a Map was to keep things a simple
 and close to the spec as possible. Since a MIMEContainer class doesn't do
 anything a map wouldn't, I didn't see a reason to include one.

 rb

 On Wednesday, April 5, 2017 at 12:56:06 PM UTC-7, sp...@draves.org
 wrote:
>
> Sounds like a good standard to have, we will support in BeakerX.  I
> already filed an issue: https://github.com/twosigma/beakerx/issues/5120
>
> Is that the right namespace though?  Shouldn't it be
> org.jupyter.something?  Is jitpack enforcing that?
>
> Also, it looks like it's using a Map as the mime type.  I think it's
> normal to define a class specifically for this purpose (MIMEContainer or
> MIMEResult or something).
> Here's BeakerX's version (which we would be happy to replace with a
> class from this standard):
> https://github.com/twosigma/beakerx/blob/37816a828fb2d3f8343182695720214650385823/kernel/base/src/main/java/com/twosigma/beaker/mimetype/MIMEContainer.java
>
> Best, -Scott
>
>
> On Wed, Apr 5, 2017 at 3:00 PM, Kyle Kelley  wrote:
>>
>> Hey all,
>>
>> Following up on the Scala discussion and action list, Ryan created
>> https://github.com/rdblue/jupyter-repr-api to standardize JVM object
>> representation to benefit both libraries and kernels.
>>
>> I'd like folks to be able to keep moving on this (while still
>> advancing Toree and other kernels) with the confidence they're supported 
>> by
>> Jupyter. As part of this I created the JVM team on the jupyter 
>> organization.
>> I'll continue to act as a sponsor and facilitator, and look forward to
>> others taking charge to lead within the jupyter ecosystem for JVM based
>> tooling as time goes on.
>>
>> I'd enjoy it if https://github.com/rdblue/jupyter-repr-api was moved
>> into this org as github.com/jupyter/jvm-repr, which will package jars on
>> jitpack (https://jitpack.io/docs/BUILDING/#gradle-projects), with the
>> namespace com.github.jupyter
>>
>> Thoughts?
>>
>> --
>> Kyle Kelley (@rgbkrk; lambdaops.com)
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to jupyter+u...@googlegroups.com.
>> To post to this group, send email to jup...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CA%2BtbMaVy7UzAo_2cGEXUU6JJNZpen-x0O-WJCXvQAxF792V3eQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> BeakerNotebook.com
> ScottDraves.com
> @Scott_Draves
>
 --
 You received this message because you are subscribed to the Google
 Groups "Project Jupyter" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jupyter+unsubscr...@googlegroups.com.
 To post to this group, send email to jupyter@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jupyter/1f69f848-8970-4b78-8d2e-e6e2209da47d%40googlegroups.com.

 For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>>
>>> --
>>> BeakerNotebook.com
>>> ScottDraves.com
>>> @Scott_Draves
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Project Jupyter" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jupyter+unsubscr...@googlegroups.com.
>>> To post to this group, send email to jupyter@googlegroups.com.
>>> To view this discussion on the web visit
>>> 

Re: [jupyter] Jupyter JVM Repr

[Brian Granger]

I am +1 on this proposal. I think having good JVM support is really
important and there is a huge benefit to having it "in-org". Thanks
for working on this stuff Kyle!

On Wed, Apr 5, 2017 at 12:00 PM, Kyle Kelley  wrote:
> Hey all,
>
> Following up on the Scala discussion and action list, Ryan created
> https://github.com/rdblue/jupyter-repr-api to standardize JVM object
> representation to benefit both libraries and kernels.
>
> I'd like folks to be able to keep moving on this (while still advancing
> Toree and other kernels) with the confidence they're supported by Jupyter.
> As part of this I created the JVM team on the jupyter organization. I'll
> continue to act as a sponsor and facilitator, and look forward to others
> taking charge to lead within the jupyter ecosystem for JVM based tooling as
> time goes on.
>
> I'd enjoy it if https://github.com/rdblue/jupyter-repr-api was moved into
> this org as github.com/jupyter/jvm-repr, which will package jars on jitpack
> (https://jitpack.io/docs/BUILDING/#gradle-projects), with the namespace
> com.github.jupyter
>
> Thoughts?
>
> --
> Kyle Kelley (@rgbkrk; lambdaops.com)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CA%2BtbMaVy7UzAo_2cGEXUU6JJNZpen-x0O-WJCXvQAxF792V3eQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSpoiAZVxcJ7g5h5_OzqZ2qwEtm5f3aCwbWFRgWidntGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Scala Kernel Discussion

[Brian Granger]

Thanks for taking the lead on this Kyle!

On Fri, Mar 3, 2017 at 5:14 PM, Kyle Kelley  wrote:
> On February 27, 2017 a group of us met to talk about Scala kernels and pave
> a path forward for Scala users. There is a youtube video available of the
> discussion available here:
>
>
> https://www.youtube.com/watch?v=0NRONVuct0E
>
>
> What follows is a summary from the call, mostly in linear order from the
> video itself.
>
> Attendees
>
> Alexander Archambault - Jupyter Scala, Ammonium
>
> Ryan Blue (Netflix) - Toree
>
> Gino Bustelo (IBM) - Toree
>
> Joy Chakraborty (Bloomberg) - Spark Magic with Livy
>
> Kyle Kelley (Netflix) - Jupyter
>
> Haley Most (Cloudera) - Toree
>
> Marius van Niekerk (Maxpoint) - Toree, Spylon
>
> Peter Parente (Maxpoint) - Jupyter
>
> Corey Stubbs (IBM) - Toree
>
> Jamie Whitacre (Berkeley) - Jupyter
>
> Tristan Zajonc (Cloudera) - Toree, Livy
>
>
> Each of the people on the call has a preferred kernel, way of building it,
> and integrating it. We have a significant user experience problem in terms
> of users installing and using Scala kernels, beyond just Spark usage. The
> overarching goal is to create a cohesive experience for Scala users when
> they use Jupyter.
>
>
> When a Scala user tries to come to the Jupyter ecosystem (or even a familiar
> Python developer), they face many options for kernels. Being faced with
> choice when trying to get things done is creating new friction points for
> users. As examples see
> https://twitter.com/chrisalbon/status/833156959150841856 and
> https://twitter.com/sarah_guido/status/833165030296322049.
>
> What are our foundations for REPL libraries in Scala?
>
>
> Toree was built on top of the Spark REPL and developers tried to use as much
> code as possible from Spark. For Alex’s jupyter-scala, he recognized that
> the Spark REPL was changing a lot from version to version. At the same time,
> Ammonite was created to assist in Scala scripting. In order to make big data
> frameworks such as Spark, Flink, and Scio to work well in this environment,
> a fork called Ammonium was created. There is some amount of trepidation in
> using a separate fork as part of the kernel community. We should make sure
> to unify with the originating Ammonite and contribute back as part of a
> larger scala community that can maintain these together.
>
> Action Items:
>
> Renew focus on Scala within Toree, improve outward messaging about how Toree
> provides a scala kernel
>
> Unify Ammonite and Ammonium (+alexandre.archamba...@gmail.com)
>
> To be used in jupyter-scala, potentially for spylon
>
> There is more than one implementation of the Jupyter protocol in the Java
> Stack.
>
>
> Toree has one, jupyter-scala does one, clojure kernels have their own.
> People would like to see a stable Jupyter library for the JVM. Some think
> it’s better to have one per language. Regardless of choice, we should have a
> well supported Jupyter library.
>
> Action Items:
>
>
> Create an idiomatic Java Library for the Jupyter messaging protocol -
> propose this as an incubation project within Jupyter
>
> Decouple Spark from Scala in kernels
>
>
> Decouple language specific parts from the computing framework to allow for
> using other computing frameworks. This is paramount for R and Python. When
> we inevitably want to connect to a GPU cluster, we want to be able to use
> the same foundations of a kernel. The reason that these end up being coupled
> is that Spark does “slightly weird things” for how it wants its classes
> compiled. It’s thought that there is some amount of specialization and that
> we can work around it. At the very least, we can bake it into the core and
> leave room for other frameworks to have solid built in support if necessary.
>
>
> An approach being worked on in Toree right now is lazy loading of spark. One
> concern that is different between jupyter-scala and Toree is that
> jupyter-scala can dynamically load spark versions whereas for Toree is bound
> to a version of Spark on deployment. For end users that have
> operators/admins, kernels can be configured per version of spark it will use
> (common for Python, R). Spark drives lots of interest in Scala kernel, many
> kernels conflate the two. This results in poor messaging and experiences for
> users getting started.
>
> Action Items:
>
>
> Lazy load spark within Toree
>
> Focus efforts within kernel communities
>
>
> Larger in scope than just the Scala kernel, we need jupyter to acknowledge
> fully supported kernels. In contrast, the whole community in Zeppelin
> collaborates in one repository around their interpreters.
>
>
> “Fragmentation of kernels makes it harder for large enterprises to adopt
> them.”
>
> - Tristan Zajonc (Cloudera)
>
>
> Beyond the technical implementation of what is a supported kernel, we also
> need the messaging to end users to be simple and clear. There are several
> objectives we need to do to improve our messaging, organization, and
> technical 

Re: [jupyter] Preparing for IPython 6.0

[Brian Granger]

Thanks Matthias, very exciting!

On Tue, Feb 28, 2017 at 4:04 PM, Matthias Bussonnier
 wrote:
> Hi all
>
> I think we are closing-in on IPython 6.0
>
> There are about 30 issues/PR open [1], I've opened a meta issue to discuss
> remaining changes and potentially problematic issues[2], and I've started to
> write/fomat the what's new [3]
>
> There are about 7 issues marked "Need contributors" that should be relatively
> easy if you are new to the codebase or to Python. Next week I'll be in 
> Berkeley
> participating to the docathon [4]. I'd love help to go through the docs and
> make things cleaner/better/valid for most English
> lexer/parser/compiler/interpreters.
>
> If you have any critical issues that are not marked as 6.0, let us know. Even
> if they are marked as 6.0 they may be bumped to later if there is not much
> interest, involve too much changes, or are beyond what we are capable of 
> doing.
>
> Looking forward for your help to test, review, document. As usual if
> you have any question they are welcome.
>
> Thanks,
> --
> Matthias
>
> 1: https://github.com/ipython/ipython/milestone/33
> 2: https://github.com/ipython/ipython/issues/10329
> 3: http://ipython.readthedocs.io/en/latest/whatsnew/development.html
> 4: https://bids.github.io/docathon/
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CANJQusXvcxtVnTS02TDm5iJBOA_r%3DZxK%2BKqauOjY9OKAnObtng%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpT6usYz866NcgZKBxRqcvoMMjY6o3TT87rdy4dEFh4iOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: Formalizing preparing a release

[Brian Granger]

Thanks for the update, sounds good!

On Mon, Feb 20, 2017 at 12:24 PM, MinRK <benjami...@gmail.com> wrote:
>
>
> On Sun, Feb 19, 2017 at 8:01 PM, Brian Granger <elliso...@gmail.com> wrote:
>>
>> I teach during the dev meetings this quarter. Was a decision reached on
>> this?
>
>
> We didn't formalise a process, but we did come up with a few things:
>
> 1. open an Issue on the package's repo to track preparing for a large
> release, tagging Jamie for project management
> 2. solicit input / testing on the mailing list
> 3. keep the process light for the smaller releases and repos
>
> -Min
>
>>
>>
>> On Mon, Feb 13, 2017 at 2:51 AM, MinRK <benjami...@gmail.com> wrote:
>> >
>> >
>> > On Sat, Feb 11, 2017 at 12:15 PM, Thomas Kluyver <tak...@gmail.com>
>> > wrote:
>> >>
>> >> I'm assuming it's already automated? I also like that page; I have
>> >> trouble
>> >> remembering the release status of different projects.
>> >
>> >
>> > The page is updated automatically. The only thing that's not automated
>> > is
>> > the list of repos, which it could get programmatically by checking for
>> > all
>> > repos on our orgs that have at least one tag.
>> >
>> > -Min
>> >
>> >>
>> >> On 10 February 2017 at 22:35, Jason Grout <ja...@jasongrout.org> wrote:
>> >>>
>> >>> It would be great if we could automate that page showing unreleased
>> >>> commits in each project. I really like that.
>> >>>
>> >>> On Fri, Feb 10, 2017 at 10:06 AM MinRK <benjami...@gmail.com> wrote:
>> >>>>
>> >>>> I made this PR earlier this week to get ready to release jupyter-core
>> >>>> 4.3. It is a tiny release (add support for one environment variable).
>> >>>> Is
>> >>>> there anything more that I should do before cutting that release?
>> >>>>
>> >>>> I just opened this issue for releasing jupyter-client 5.0. It is a
>> >>>> major
>> >>>> version bump due to a technically backward-incompatible change
>> >>>> (timezone-aware datetime objects), but it is still a ‘small’ release,
>> >>>> since
>> >>>> that is in a feature that is rarely used (only in IPython parallel,
>> >>>> to my
>> >>>> knowledge, which already supports the changes in master). Should I
>> >>>> open an
>> >>>> issue on project-mgt about this?
>> >>>>
>> >>>> I think a release calendar is tough for many repos, as most won’t
>> >>>> have
>> >>>> planned releases until a certain amount of changes have been
>> >>>> accumulated.
>> >>>> Communicating upcoming major releases for the bigger user-facing
>> >>>> projects
>> >>>> (notebook, ipython, nbconvert) is definitely important. The mailing
>> >>>> list
>> >>>> seems like the most logical place to signal "We're trying to get
>> >>>> ready for
>> >>>> release, please help with extra testing, catching regressions, etc."
>> >>>> that
>> >>>> should catch people who don't follow GitHub issues.
>> >>>>
>> >>>> I made this page as an exercise a while ago, which summarizes how
>> >>>> much
>> >>>> we have that’s unreleased. It doesn’t give an indicator of how close
>> >>>> we are
>> >>>> to any given release, but it does (roughly) indicate how much we have
>> >>>> unreleased, which can be used as a reminder to start pushing toward a
>> >>>> release, especially on the easily forgotten smaller repos.
>> >>>>
>> >>>> -Min
>> >>>>
>> >>>> On Fri, Feb 10, 2017 at 2:59 AM, Steven Silvester
>> >>>> <ssilves...@continuum.io> wrote:
>> >>>>>
>> >>>>> 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

Re: [jupyter] Re: Formalizing preparing a release

[Brian Granger]

I teach during the dev meetings this quarter. Was a decision reached on this?

On Mon, Feb 13, 2017 at 2:51 AM, MinRK  wrote:
>
>
> On Sat, Feb 11, 2017 at 12:15 PM, Thomas Kluyver  wrote:
>>
>> I'm assuming it's already automated? I also like that page; I have trouble
>> remembering the release status of different projects.
>
>
> The page is updated automatically. The only thing that's not automated is
> the list of repos, which it could get programmatically by checking for all
> repos on our orgs that have at least one tag.
>
> -Min
>
>>
>> On 10 February 2017 at 22:35, Jason Grout  wrote:
>>>
>>> It would be great if we could automate that page showing unreleased
>>> commits in each project. I really like that.
>>>
>>> On Fri, Feb 10, 2017 at 10:06 AM MinRK  wrote:

 I made this PR earlier this week to get ready to release jupyter-core
 4.3. It is a tiny release (add support for one environment variable). Is
 there anything more that I should do before cutting that release?

 I just opened this issue for releasing jupyter-client 5.0. It is a major
 version bump due to a technically backward-incompatible change
 (timezone-aware datetime objects), but it is still a ‘small’ release, since
 that is in a feature that is rarely used (only in IPython parallel, to my
 knowledge, which already supports the changes in master). Should I open an
 issue on project-mgt about this?

 I think a release calendar is tough for many repos, as most won’t have
 planned releases until a certain amount of changes have been accumulated.
 Communicating upcoming major releases for the bigger user-facing projects
 (notebook, ipython, nbconvert) is definitely important. The mailing list
 seems like the most logical place to signal "We're trying to get ready for
 release, please help with extra testing, catching regressions, etc." that
 should catch people who don't follow GitHub issues.

 I made this page as an exercise a while ago, which summarizes how much
 we have that’s unreleased. It doesn’t give an indicator of how close we are
 to any given release, but it does (roughly) indicate how much we have
 unreleased, which can be used as a reminder to start pushing toward a
 release, especially on the easily forgotten smaller repos.

 -Min

 On Fri, Feb 10, 2017 at 2:59 AM, Steven Silvester
  wrote:
>
> 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 attention to some of us that with the
>> increasing number of projects we have it can be hard to follow when
>> packages are going to be released, which often leads to very short
>> windows of time to give feedback or test the new version with existing
>> software.
>>
>> 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
>> plugins/extensions. There are likely others in the community who did
>> not realize the 5.0 release was so close, who would need some time to
>> test their extensions/plugins and give feedback.
>>
>> How would the team and everyone else feel if we encouraged Jupyter
>> projects to open an issue when a major release started to take shape
>> which clearly listed the planned schedule for the release and
>> highlighted what was new in the release? The upcoming release and this
>> issue would be announced on the mailing list. People interested in
>> following the release updates could subscribe to this issue.
>>
>> That would be of course on a per-project/per-maintainer basis, but the
>> project would try  to encourage it for major releases, or maybe even
>> minor releases.
>>
>> Thanks,
>> --
>> Matthias, with the help of Jamie, Jason, Brian and Fernando.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/15e15697-328a-4903-882b-5c1506bee00a%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

 --
 You received this message because you are subscribed to the Google
 Groups "Project 

Re: [jupyter] Re: Jupyter Notebook 5.0 beta 1

[Brian Granger]

Tony,

Great questions and feedback! Inline thoughts below...

> - will Jupyter notebooks continue to be available as such once Jupyterlab is
> available? (could a jupyterlab instance be configured to just mimic a simple
> notebook UI, for example)

Yes, the core JS component in JupyterLab are very well decoupled and
designed to be used and reused in different ways. The JupyterLab team
is very aware of the need to provide a UI that remains as simple as
possible. Allowing individual notebooks to be edited in their own
browser tab is *one* way of providing that. We have other ideas as
well and will continue to explore these things for the 1.0 release and
beyond. I spend much of my time teaching undergrads with the notebook
and I know first hand how important it is to have something simple.

> - will Jupyterhub continue to supplort multiuser deployment of Jupyter
> notebooks?

Yep, already works fine with JupyterHub. I have been using
JupyterLab+Hub for the past 2 months in my data science course. Simply
pip installing jupyterlab (and enabling its serverextension) was all
that was needed.

>
> One of the attractions of Jupyter notebooks in education and for supporting
> use of code outside computing discipline is that the notebook interface is
> relatively simple and friendly without all the sidebar chrome and menus and
> features and tools and stuff that make IDEs a terrifying experience for most
> people. I'm keen to be able to keep using a simple clean interface from the
> off with students and nontechies.

Yes absolutely. Keeping JupyterLab simple while still providing the
extra power has been one of my main design priorities. We are *not*
there yet, but this is super important.

>
> I'm lobbying my institution to make notebooks available locally, a process
> that will take 3-6 months to get deployed and then be expected to not change
> much for a chunk of time. What should I be lobbying for?! I'm pitching for
> novices to be able to access simple notebook UIs without any need for too
> many features in the first instance.

It depends on when you are doing this.

If it was today, I would just stick with the classic jupyter notebook
+ jupyterhub. When JupyterLab comes out *midyear* (I don't know where
Matthias got the idea it might be delayed until 2018 - that isn't the
case), it should be easy to optionally add JupyterLab (literally just
an extra pip install), but to keep classic notebook as well. Both run
fine side by side in the same JupyterHub deployment and a user can
pick which to use if both are installed.

>
> (eg if/when nteract ships with a bundled kernel, I can see it being great
> for use with this user community (even more so if the ability to launch
> temporary or multiuser nteract instances from a remote instituional server
> accessed via a browser).)

Yeah the most difficult thing to install is not the UI - but the kernels.

>
> By way of trying to express my general concerns, as opposed to just being
> critical of the new... Looking at things like RStudio, it used to be
> relatively simple... but as it gets richer features and more powerful tools,
> and experts who've grown with it just have to keep up with it, and maybe
> also demand more of it as they get more expert/professional, it just gets
> more complicated and scary for novices coming to it for the first time.
> Sometimes less is more. The on-ramp needs to be kept simple. (Or at least,
> it helps if there is a simple on-ramp somewhere...). There are risks to
> always developing more and moving away from the simple offering that
> appealed to folk in the first place... Which isn't to say I don't like the
> new features that appear with each new release of eg Jupyter notebooks and
> isn't to say that Jupyter project shouldn't become an ever more powerful
> tool for expert and power scientific computing users.

+100.

>
> But it's easy to forget that the experience of welcoming new features as you
> perceive they're missing, because you're growing in expertise as the tool
> acquires more powerful features, is different to someone coming to the
> environment for the first time - as a simple notebook that did what it did 3
> years ago, to the more complex notebook it is now, to the yet more complex
> Jupyterlab view?

Can you be more specific about the "complexity" here. I am not denying
the notebook has become more complex or that JupyterLab is more
complex than the notebook. But there are many types of complexities
and I am interested about which you are thinking about here. Some that
I can think of that could be an issue (in any software):

* Multiple "acitvities" on a single page
* Complexity of the code base
* Visual complexity
* Feature complexity (too many visual elements, too many borders,
regions, colors, etc.)
* Bad UI/UX design (distracting, overwhelming, etc.)

Would love any specific concrete feedback you have on these things to
help us refine JupyterLab.

Cheers,

Brian

>
> --tony
>
> On Wednesday, 15 February 2017 

Re: [jupyter] Load Testing JupyterHub

[Brian Granger]

In general, the bottleneck is always going to be the
N_students*resources_per_student.

That varies widely by what the students are doing. In our data science
courses, we give each students 2GB RAM and approximately 4 students
per CPU core. The CPU stuff isn't typically the issue - RAM *always*
is.

For more basic python programming stuff, you could use less RAM per
student, but I wouldn't go below around 500MB per student.

Cheers,

Brian

On Thu, Feb 16, 2017 at 3:53 AM, Doug Blank  wrote:
> On Thu, Feb 16, 2017 at 6:23 AM, Thomas Kluyver  wrote:
>>
>> On 16 February 2017 at 10:00, DVD PS  wrote:
>>>
>>> we won't deploy it till we have some understanding of how many we can
>>> handle
>>
>>
>> I don't know of any tools to help you with this, unfortunately.
>>
>> Running the notebook servers takes ~40MB memory per user, and each Python
>> kernel started is another ~30MB before loading any libraries. But resource
>> use will often be dominated by what code users are running inside their
>> notebooks.
>
>
> We've been using JupyterHub since it was almost ready to use, and there
> isn't an easy way to answer the question "how many students can a machine
> handle?" We use a variety of kernels, and some languages are better than
> others. We have some Javascript kernels that have a small impact on the
> server, and Java kernels that just a dozen of students can bring a machine
> to its knees (at least for a short time, while compiling). IPython is pretty
> good, but of course it depends on what they are doing.
>
> We use JupyterHub across Physics, Biology, and Computer Science. The Physics
> courses tend to have the highest load per cell, partly due to their style of
> processing, but also because of their problem sets.
>
> Our server has 512 gigabytes of RAM, and 12 cores. It is actually just the
> head node on a cluster. Our goal is to get it set up such that a student's
> kernel would spin up on the node that is most available (probably using
> docker). But we have to figure out how that plays with the other jobs and
> the scheduler.
>
> I had tried a CPU limiter in the past. Our load is getting so high now, we
> may have to revisit that.
>
> I'd be glad to help answer this question as we have a live, operating setup.
> Feel free to contact me directly if there is something I can do (e.g.,
> provide other stats, run a test program, etc.)
>
> -Doug
>
>>
>>
>> Thomas
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAOvn4qgxVXwS97MUQXxRQ8FioJh_DmjOTtcX9-KottgLmkVfJw%40mail.gmail.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAAusYCgQ4LWvd-btUC8z%3DgbR5u6q2GWsY%3DwcBuJVoEOEwgMwdA%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSNRL7miCwDCLd%3D%2BJLRCWW3RbS%2B-r%2BgeGa7QOmTwVds4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Formalizing preparing a release

[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
broader set of stakeholders who are affected by upcoming releases.

Many of these stakeholders don't follow our weekly meetings/notes
closely and wouldn't be able to follow all of our repos (even our core
devs working full time are not able to follow these things). Because
of that a post on the mailing list about each major release is about
as good as we can do to let the community know a release is
approaching.

In terms of where to open an issue, I almost think the project
management repo makes sense:

https://github.com/jupyter/project-mgt

That is a great way of keeping Jamie in the loop on these things. But
I am also fine with using other repos for the issues.

On Wed, Feb 8, 2017 at 7:12 PM, Matthias Bussonnier
 wrote:
> Hello all,
>
> It recently came to the attention to some of us that with the
> increasing number of projects we have it can be hard to follow when
> packages are going to be released, which often leads to very short
> windows of time to give feedback or test the new version with existing
> software.
>
> 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
> plugins/extensions. There are likely others in the community who did
> not realize the 5.0 release was so close, who would need some time to
> test their extensions/plugins and give feedback.
>
> How would the team and everyone else feel if we encouraged Jupyter
> projects to open an issue when a major release started to take shape
> which clearly listed the planned schedule for the release and
> highlighted what was new in the release? The upcoming release and this
> issue would be announced on the mailing list. People interested in
> following the release updates could subscribe to this issue.
>
> That would be of course on a per-project/per-maintainer basis, but the
> project would try  to encourage it for major releases, or maybe even
> minor releases.
>
> Thanks,
> --
> Matthias, with the help of Jamie, Jason, Brian and Fernando.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CANJQusV%3DVYmhw%2B5mAGYPx6MHLDXyL9tfNqvTvftM%2BOa2g0m9Hg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQ7L8MCk%2Bm16nDZE0HqDje-s4ey%2ByH7d-kU4gDoETaQNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: Ironing out some issues with nbextension/serverextensions in notebook 5.0 and 4.x

[Brian Granger]

Looks like discussion is happening here:

https://github.com/jupyter/notebook/issues/2141

On Tue, Feb 7, 2017 at 1:43 AM, Sylvain Corlay <sylvain.cor...@gmail.com> wrote:
> Hi Brian,
>
> The JEP on the Jupyter server
>
> https://github.com/jupyter/enhancement-proposals/pull/21
>
> proposes semantics on prioritization and defaults for system vs sys-prefix
> vs user installation.
>
> There has already be some discussion on this in this PR.
>
> Sylvain
>
> On Thursday, December 22, 2016 at 10:34:30 PM UTC+1, ellisonbg wrote:
>>
>> And to answer my own questions:
>>
>> * Consistent handling of sys-prefix, system and user options
>>   - Which is default?
>>   - Which has priority?
>>   - How are they combined into the final config
>> * Make it easy to disable or uninstall all extensions for
>> system/sys-prefix/user
>>
>> Cheers,
>>
>> Brian
>>
>>
>> On Thu, Dec 22, 2016 at 2:32 PM, Brian Granger <elli...@gmail.com> wrote:
>> > Hi all,
>> >
>> > We have just released notebook 4.3.1 and are starting to look towards
>> > a notebook 5.0 release. We have a number of small issues related to
>> > the installation and enabling of nextensions and serverextensions in
>> > the 4.x release series and 5.0/master.
>> >
>> > Because the notebook 5.0 will likely be the first notebook release to
>> > simultaneously support jupyterlab 1.0, I think it is important to iron
>> > out some of these problems before its release.
>> >
>> > Here are the currently open issues that I know of related to this:
>> >
>> > https://github.com/jupyter/notebook/issues/1992
>> > https://github.com/jupyter/notebook/issues/1797
>> > https://github.com/jupyter/notebook/issues/1706
>> > https://github.com/jupyter/notebook/issues/1617
>> > https://github.com/jupyter/notebook/issues/1508
>> >
>> > I would like to have a video meeting about these issues after the new
>> > year. In the meantime, let's use this email thread to try to better
>> > understand the big picture of what needs to get done for 5.0.
>> >
>> > IMPORTANT: I know we are wanting to move towards a completely
>> > different approach (the so called "conf.d" approach), but I don't
>> > think we can delay notebook 5.0 for that release. Also recent work by
>> > Sylvain suggests we may want to wait to do that once the server is its
>> > own separate repo/project.
>> >
>> > Cheers,
>> >
>> > Brian
>> >
>> > --
>> > Brian E. Granger
>> > Associate Professor of Physics and Data Science
>> > Cal Poly State University, San Luis Obispo
>> > @ellisonbg on Twitter and GitHub
>> > bgra...@calpoly.edu and elli...@gmail.com
>>
>>
>>
>> --
>> Brian E. Granger
>> Associate Professor of Physics and Data Science
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgra...@calpoly.edu and elli...@gmail.com



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTAzQNRvr3c4-i-0Zds6HdSYTfuPbPxoZTd-sDfurvk7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Looking for a co-presenter for a security-related talk at JupyterCon

[Brian Granger]

Great! This is definitely the right place to ask...

On Mon, Feb 6, 2017 at 4:25 PM, Steven Anton  wrote:
> Hi everyone, I'm really looking forward to JupyterCon in August. I'd like to
> submit a talk regarding some work I've done to enable working with encrypted
> notebooks. (My company deals with a lot of PII. To protect that data, we
> GPG-encrypt our notebooks on disk on-the-fly.) But the 40-minute format
> seems a bit much for my topic. Is anyone interested in co-presenting
> something else that is notebook security related (i.e. so each of us
> presents 20 minutes)?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/6d653eca-3c74-43ca-b305-ea6eb340eb37%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTSEaBAvZt7UUDCtGnhzXdEmPQKFvPF5TgWrRG6kj-5yw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: Ironing out some issues with nbextension/serverextensions in notebook 5.0 and 4.x

[Brian Granger]

Pinging everyone on this one again...we need to resolve this stuff
before notebook 5.0 goes out the door...

On Thu, Dec 22, 2016 at 1:32 PM, Brian Granger <elliso...@gmail.com> wrote:
> Hi all,
>
> We have just released notebook 4.3.1 and are starting to look towards
> a notebook 5.0 release. We have a number of small issues related to
> the installation and enabling of nextensions and serverextensions in
> the 4.x release series and 5.0/master.
>
> Because the notebook 5.0 will likely be the first notebook release to
> simultaneously support jupyterlab 1.0, I think it is important to iron
> out some of these problems before its release.
>
> Here are the currently open issues that I know of related to this:
>
> https://github.com/jupyter/notebook/issues/1992
> https://github.com/jupyter/notebook/issues/1797
> https://github.com/jupyter/notebook/issues/1706
> https://github.com/jupyter/notebook/issues/1617
> https://github.com/jupyter/notebook/issues/1508
>
> I would like to have a video meeting about these issues after the new
> year. In the meantime, let's use this email thread to try to better
> understand the big picture of what needs to get done for 5.0.
>
> IMPORTANT: I know we are wanting to move towards a completely
> different approach (the so called "conf.d" approach), but I don't
> think we can delay notebook 5.0 for that release. Also recent work by
> Sylvain suggests we may want to wait to do that once the server is its
> own separate repo/project.
>
> Cheers,
>
> Brian
>
> --
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgran...@calpoly.edu and elliso...@gmail.com



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSmmjUMiGzjJ4UvSH5n%3DP%3DyWWR1OhjJHNuaJpbqQx_Q3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] New notebook gallery site

[Brian Granger]

I have talked with these folks and seen this. The main difference is
that users must upload notebooks, rather than simply renering
notebooks from URLs/github as nbviewer does.

On Fri, Jan 27, 2017 at 10:11 AM, Thomas Kluyver  wrote:
> On 27 January 2017 at 12:03, Kiko  wrote:
>>
>> Could you extend about the "Secret" concern?
>
>
> Guessing a bit, but I think that Matthias is referring to 'secret URLs',
> where you hide a document simply by putting it at a long, hard to guess URL,
> and then only sharing that URL with the people you want to see it. It
> occurred to us at some point that people could share such notebooks using
> nbviewer, and that if we ever exposed a list of 'recently viewed notebooks'
> there, it would reveal the secret URLs to anyone.
>
> I don't think it should be a problem for a service built from the beginning
> as a sharing site, like you're proposing.
>
> Thomas
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAOvn4qhSvTfGd7SkQnsHHYAWQvT7m5qf97hP6AP%3DeJ59%2BpTsEQ%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSZhyP%2Bm%2B8zPsd80hthmxSbcA6wrRRsfT7J5ww8f4dCJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Smooth interaction with graphics

[Brian Granger]

The main thing I have found with using matplotlib with interact is
that you have to do a bit of extra work to make sure that the overall
frame/ticks/limits/etc are the same as you vary your parameter.
Because each call to plt.plot is new, matplotlib has no way of knowing
it should hold those things invariant.

On Sat, Jan 14, 2017 at 9:17 AM,   wrote:
> On Saturday, January 14, 2017 at 9:55:31 AM UTC-5, Sylvain Corlay wrote:
>
>> The problem is that the rendering logic for matplotlib resides in the
>> backend. I would recommand using the "notebook" backend for matplotlib which
>> should improve the situation.
>>
>> Or you can use a plotting library for the notebook such as bqplot.
>
>
> Thanks! the notebook backend seemed much worse. bqplot seems very new and,
> I'm guessing that it will be the way to work with 2D graphics in the
> notebook. For the record, I was able to piece together the following after a
> little fiddling:
>
> import numpy as np
> from bqplot import pyplot as plt
> from ipywidgets import interact, FloatSlider
>
> fig = plt.figure(1)
> def myplot(a):
> xs = np.linspace(-3,3,100)
> ys = np.sin(a*xs)
> if fig.marks == []:
> plt.plot(xs,ys)
> else:
> fig.marks[0].y = ys
> demo = interact(myplot, a=FloatSlider(value=1, min=-3, max=3, step=0.01))
> plt.ylim(-1.1,1.1)
> plt.show()
>
> This seems to work quite well.
>
> Thanks again!
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/1d4935fd-b035-4c7f-bbf7-8aa04ed20d4b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQdJ2pNrV6MRBumct7PqJMygJy%2BpcqWBQRhOwBNk%3DSDYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Writeup of JupyterLab style issues/milestones: application to jupyter/notebook

[Brian Granger]

Hi all,

I have opened this PR describing how we are using labels/milestones in
JupyterLab:

https://github.com/jupyter/governance/pull/29

I recently restructured the notebook labels/milestones to use this
approach. In the coming weeks, I would like to work with Grant - and
anyone else wanting to help - to do a pass on the jupyter/notebook
issues to:

* Implement this approach
* Close ones that are stale or outdated
* Target many/most new feature requests towards the JupyterLab
milestone (eventually to be migrated to the jlab repo)
* Try to narrow down the work that needs to be done for the 5.0 and
4.4. milestones.
* Start to perform regular visualizations of the notebook issues
similar to this:

https://github.com/jupyterlab/jupyterlab/issues/1439

Hopefully this will enable us to get a better handle on where things
are at with the notebook repo and aid in the smooth migration to
JupyterLab.

Cheers,

Brian


-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTQh9fWcHVsUPG%3DEBgPkpmn2-KJbEMJ1BCp-T%3DA%3Dt2uRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Jupyter/governance: document describing how we are using labels/milestones

[Brian Granger]

Hi all,

In the JupyterLab repo, we have been experimenting with a slightly
more formal and structured approach to using Github labels and
milestones. The flat nature of the GitHub label namespace makes it
difficult to manage large numbers of issues. We have come up with a
label taxonomy that is helping us mange issues in the JupyterLab repo.

Here is the document/PR describing this approach:

https://github.com/jupyter/governance/pull/29

Here is the JupyterLab repo's labels, milestones and issues links that
use this approach:

https://github.com/jupyterlab/jupyterlab/issues
https://github.com/jupyterlab/jupyterlab/labels
https://github.com/jupyterlab/jupyterlab/milestones

Right now I have written this to be descriptive rather than
prescriptive; IOW it is completely optional for other subprojects to
adopt. However, part of the motivation here is to see if we can come
up with an approach that more of our subprojects can use. This would
allow us to query our issues and PRs in a structured way across
repos/orgs.

Please provide feedback and comments here:

https://github.com/jupyter/governance/pull/29

Cheers,

Brian

-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpT46tk78gpBi_uVkwmONJYZwt3yhi3_t09uPy-%2BnEpuBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: Ironing out some issues with nbextension/serverextensions in notebook 5.0 and 4.x

[Brian Granger]

And to answer my own questions:

* Consistent handling of sys-prefix, system and user options
  - Which is default?
  - Which has priority?
  - How are they combined into the final config
* Make it easy to disable or uninstall all extensions for system/sys-prefix/user

Cheers,

Brian


On Thu, Dec 22, 2016 at 2:32 PM, Brian Granger <elliso...@gmail.com> wrote:
> Hi all,
>
> We have just released notebook 4.3.1 and are starting to look towards
> a notebook 5.0 release. We have a number of small issues related to
> the installation and enabling of nextensions and serverextensions in
> the 4.x release series and 5.0/master.
>
> Because the notebook 5.0 will likely be the first notebook release to
> simultaneously support jupyterlab 1.0, I think it is important to iron
> out some of these problems before its release.
>
> Here are the currently open issues that I know of related to this:
>
> https://github.com/jupyter/notebook/issues/1992
> https://github.com/jupyter/notebook/issues/1797
> https://github.com/jupyter/notebook/issues/1706
> https://github.com/jupyter/notebook/issues/1617
> https://github.com/jupyter/notebook/issues/1508
>
> I would like to have a video meeting about these issues after the new
> year. In the meantime, let's use this email thread to try to better
> understand the big picture of what needs to get done for 5.0.
>
> IMPORTANT: I know we are wanting to move towards a completely
> different approach (the so called "conf.d" approach), but I don't
> think we can delay notebook 5.0 for that release. Also recent work by
> Sylvain suggests we may want to wait to do that once the server is its
> own separate repo/project.
>
> Cheers,
>
> Brian
>
> --
> Brian E. Granger
> Associate Professor of Physics and Data Science
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgran...@calpoly.edu and elliso...@gmail.com



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTTPKLGXbiA75KrRBF-JtUVM9Xe7c%2BtUWMJqF3J4WcZjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Ironing out some issues with nbextension/serverextensions in notebook 5.0 and 4.x

[Brian Granger]

Hi all,

We have just released notebook 4.3.1 and are starting to look towards
a notebook 5.0 release. We have a number of small issues related to
the installation and enabling of nextensions and serverextensions in
the 4.x release series and 5.0/master.

Because the notebook 5.0 will likely be the first notebook release to
simultaneously support jupyterlab 1.0, I think it is important to iron
out some of these problems before its release.

Here are the currently open issues that I know of related to this:

https://github.com/jupyter/notebook/issues/1992
https://github.com/jupyter/notebook/issues/1797
https://github.com/jupyter/notebook/issues/1706
https://github.com/jupyter/notebook/issues/1617
https://github.com/jupyter/notebook/issues/1508

I would like to have a video meeting about these issues after the new
year. In the meantime, let's use this email thread to try to better
understand the big picture of what needs to get done for 5.0.

IMPORTANT: I know we are wanting to move towards a completely
different approach (the so called "conf.d" approach), but I don't
think we can delay notebook 5.0 for that release. Also recent work by
Sylvain suggests we may want to wait to do that once the server is its
own separate repo/project.

Cheers,

Brian

-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQruqBVhj7ftLV_ZM4xaS1KvdgU1aSKab__6_TWeHzbrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Governance: draft process for authoring papers

[Brian Granger]

Hi all,

I have submitted a PR to the governance repo adding a process for
authoring papers. In particular, at this point, I have specified a
detailed process for writing papers for the Journal of Open Source
Software (http://joss.theoj.org/). Because JOSS papers are very short
the process is a bit different than for other longer-form papers.

Probably the biggest point to discuss are the Authorship Criteria,
which I have copied from SymPy's recent PeerJ preprint:

https://github.com/sympy/sympy-paper

Once this PR is merged, we will try it out on a few of our repos and
get some papers published!!!

Here is the PR:

https://github.com/jupyter/governance/pull/27

Cheers,

Brian

-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpSbr7XpEWx0X5wwDDSGoOX3t6M1%2BgSaTSQr%3DyycXua2LA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: Clarification of the widget landscape

[Brian Granger]

Brad,

Great question. Nick has done a great job and answering this question
and providing a lot of background. I wanted to fill in a few other
aspects that may help you decide what fits for you and where things
are headed.

In general, there are a number of factors that go into where the
project is headed:

* The planning and roadmap work from the core project contributors
about where we want to go
* Which of the various options are attracting users
* Which of the various options are attracting developers
* Which of the various options have funding to hire developers
* etc.

On all of these fronts, I think ipywidgets is the best bet:

* It has the largest number of users of the various options and has
been around the longest
* We have funding to work on it
* There are a number of core developers putting a lot of time into it
* There are a number of third parties building on top of it
* It continues to be our top priority on the roadmap in this area

The other thing to note is that much of what you describe in your
original question can be done with ipywidgets out of the box. In other
words, you can probably get a lot done by importing ipywidgets and
using it - without diving into JavaScript and building custom widgets.

I should mention though that ipywidgets is going through a phase of
massive change and development right now. Because of this, lots of
internal details will change over the next year. However, we are
working hard to make sure  the Python APIs change minimally, if at
all. But even on the JavaScript side, we are working hard to minimize
the changes needed. The good news, is that all of the work being done
reflects the fact that ipywidgets is moving quickly and getting a lot
of improvements.

Hope this helps.

Cheers,

Brian

On Mon, Dec 19, 2016 at 8:33 AM, Nicholas Bollweg
 wrote:
> Brad:
>
> Thanks for the interest!
>
> We're excited to help you do really cool things with notebooks, widgets,
> etc. I guess it depends on what you mean by "application." Do you want
> something that lives "close" to the notebook, such that a scientist can use
> it during their work, with full access to kernels, etc. or is it a "display"
> that just shows information? Or a SaaS? Or a presentation? Or actually a
> "dashboard" on a device?!
>
> With those questions in mind, I'll answer your last question first:
>
>> I would also be grateful for pointers to any resources that you think
>> would be useful in understanding this landscape.
>
>
> I just updated this example to the newer APIs, based on this very dated
> example. This is more of a "replace the old broken computer next to my
> scientific equipment," rather than "what is the scheduling status of this
> machine?" On the API maturity side, it took about five minutes to get it
> working, which isn't that bad considering two years had elapsed, in which we
> split everything up, and have done many releases of every component! I can
> vouch for python-driven widgets being a sound way to build up rich,
> maintainable GUIs!
>
> Here is a recent talk I did at PyData ATL (sorry, no recording) which is
> arguably an application, in that it is (a number of) live coding
> environment(s). In that talk, to make matters worse, I use nbpresent, as
> another way of laying out notebook content, including widgets (sort of a
> sibling/competitor to Jupyter Dashboards).
>
> Ok, to your specific stuff:
>
>> IPython widgets
>
>
> ipywidgets is (historically) the reference implementation of Jupyter
> Widgets.
>
> When you install the python module of ipywidgets, it also updates some
> JavaScript (jupyter-js-widgets), which is loaded into the notebook.
>
> For many kinds of interactive computing activities, you might not need to
> write any JavaScript, CSS and HTML, and get the full complement of GUI
> stand-bys: buttons, sliders, layouts, etc. With a little bit of CSS
> knowledge (written in a pythonic way), you can have pretty attractive
> content. See the example at the beginning!
>
>> Jupyter declarative widgets
>
>
> Declarative widgets gives access to the underlying widget API: Instead of
> python, you're mainly writing HTML and JavaScript. The bits and pieces gets
> installed via bower, yet another javascript dependency management ecosystem,
> instead of a python-focused one.
>
>>
>> Jupyter dashboards
>
>
> The Jupyter Dashboard has two components: the authoring tool and the server.
> The authoring tool lets you visually construct content on a single-screen
> scrollable dashboard, where the individual content pieces can be markdown,
> code, output or any widget (including, therefore, declarative widgets...
> though it does take some extra work), and bundle up the content. The Server
> can accept these bundles, and host them in a relatively secure way via
> Docker and clever proxies, and as such can be good for standing up
> "hands-off" dashboards like kiosks and NOC/EOC kind of big displays.
>
>>
>> Polymer
>
>
> Polymer is the mother-of-all 

Re: [jupyter] [ANN] nbconvert 5.0

[Brian Granger]

Many congrats, great to see nbconvert moving forward!

On Fri, Dec 16, 2016 at 7:09 AM, MinRK  wrote:
> We’ve just released nbconvert 5.0, with lots of nice fixes and improvements.
> Among the key changes are switching the default latex engine from pdflatex
> to xelatex, which should get much better unicode and font handling, among
> other things. There is also a new ASCIDoc Exporter, and loads of other
> bugfixes and improvements over the past year, especially in the ways
> nbconver interacts with pandoc and latex.
>
> pip install --upgrade nbconvert
>
> See the changelog for more details.
>
> Special thanks to Michael Pacer for leading the release process.
>
> -Min
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAHNn8BWNPfkRDGjcJTBSLZd3QD9sqCpKAzEiOXsmx4xffS5r%2BA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpT3aaEjqXfs2FAs%2B8qT5AAyc76owN%3DgBCGuuovsErieew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] We are hiring a contract based technical writer for Projet Jupyter

[Brian Granger]

Hi all,

We wanted to let the broader community know that we are in the process
of hiring a technical writer for Project Jupyter that will focus on
the documentation.

Here is a quick sketch of the position:

* Work would be on a contract basis
* 6-12 month contract on part or full-time basis
* Prefer local SF Bay Area
* Knowledge of our ecosystem and open-source
* Working knowledge of Sphinx
* Experience in technical writing
* Primary responsibility will be working on our documentation

If you are interested or you know anyone who is interested, please
email Fernando Perez (fernando.pe...@berkeley.edu), and include links
to existing work and/or a resume.

Feel free to pass this around to any other relevant mailing lists,
communities, individuals, etc.

Cheers,

Brian



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQN2UG5yUY8WA7ccvd44nPqozH2e%2BqsZSBD1hsPNRjXQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Find the rogue train: nice example of notebook use

[Brian Granger]

At one point I played with a notebook -> medium post converter, but
the Medium API was pretty limited. More specifically, it was pretty
tough to format cells with multiple outputs in a manner that was in
any way reasonable. I think they also don't have any support for
LaTeX.

However, if you have really simple notebooks that lack these
complications, I don't think it was very difficult to do this. Here is
a rough sketch:

* Use nbconvert to convert a notebook to HTMl or markdown
* Use the Medium Python API to upload it:

https://github.com/Medium/medium-sdk-python

Cheers,

Brian


On Sat, Dec 10, 2016 at 3:22 PM, John Lam  wrote:
> Perhaps I'm missing something here, but while the authors claim they used a 
> notebook to do the computations, what I saw at the end of the link was a 
> Medium post. It seems to me like what they did was manually convert their 
> Jupyter notebook into a Medium post, which was probably a lot of work.
>
> Is there some way of easily taking a Jupyter notebook and just publishing its 
> HTML as a fragment that could be embedded in a Medium post, and with an 
> accompanying link to the .ipynb file (or better yet to where the .ipynb file 
> is hosted in an Azure Notebook service library?)
>
> Would love to see something like this happen. Please let me know what we can 
> / should do to make this happen.
>
> Thx!
> -John (PM on the Azure Notebook Service).
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/89f27d9e-a6a0-405a-9600-d986169a3a86%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTEqs46NbvtVAnTLUhKSHQMuiYNtfvCSACco1SgaMwAMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] PyCon tutorial

[Brian Granger]

I don't know my travel schedule yet, but I would like to be able to go
to PyCon. Please feel free to put my name down to help with any
tutorial there...

On Sun, Nov 27, 2016 at 1:45 AM, MinRK  wrote:
> Hi Matthias and Mike!
>
> I think doing the IPython-in-depth is a good choice at PyCon. I’d like to
> not be the submitting presenter, since I cannot commit to the travel at this
> point. I opened a PR updating the existing proposal; we can finish putting
> it together there. The only thing I’d like to switch up is IPython parallel
> as the last segment - I think that’s a bit too much to bite off for the
> audience of the first section.
>
> https://github.com/ipython/ipython-in-depth/pull/38
>
> -Min
>
>
> On Sun, Nov 27, 2016 at 12:50 AM, Matthias Bussonnier
>  wrote:
>>
>> Hey Min,
>>
>>
>> On Wed, Nov 23, 2016 at 12:11 PM, MinRK  wrote:
>> > Carol brought up the idea that an IPython and/or Jupyter tutorial at
>> > PyCon
>> > would be a good idea, since we didn't do one last year. The deadline for
>> > tutorials in next week, 30 November
>> >
>> > We have a few tutorials available, which we can derive from what we've
>> > done
>> > in the past:
>> >
>> > - classic "IPython in Depth", giving a broad overview and introduction
>> > - Deploying notebooks - JupyterHub in particular, possibly including
>> > things
>> > like tmpnb, kernel-gateway, using docker, etc.
>> > - A more widgets-centric, or other advanced IPython tutorial
>>
>> I'm in, there is a couple of things where I would need to catch up a
>> bit, but I can definitively give a hand especially if it's close to
>> IPython-in-depth.
>>
>> Is there a shared document for current proposal ?
>>
>> Cheers,
>> --
>> M
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CANJQusWntH4aO3QgJ4G_5FYnW4DS21m3n4kFTaMfRsP3q1rRkQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAHNn8BWzfogBJGPDUvBocP3NwfP1BUChizzkhouj8dTHxZu7Tg%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTQ7O%3D7ET7ycC0Je6H%2BkuV7m7KtGAgJhCAb%3DGUPqR2%2BYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] PDF Viewer

[Brian Granger]

Here is an example of a plugin that has a custom file viewer:

https://github.com/jupyterlab/jupyterlab_geojson

That would get you started. Let us know if you have questions...

On Fri, Oct 28, 2016 at 2:23 PM, Chris Colbert  wrote:
> We don't have a way to do that out of the box, but I imagine you could use
> something like pdf.js to write a plugin to do that.
>
> https://mozilla.github.io/pdf.js/
>
> On Fri, Oct 28, 2016 at 2:43 PM, Pedro Rodriguez 
> wrote:
>>
>> Hi All,
>>
>> I am curious if there is a way to view a PDF within Jupyter lab.
>>
>> Thanks!
>> Pedro Rodriguez
>> PhD Student in Machine Learning | CU Boulder
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/15061c45-4f38-4974-bbe5-0abd4ba00431%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAPc_zRVPyURoaGMfCxPBgYSP%3DbJPV%3Dqzq_vauFeJRwt%2B6%3D5Z4Q%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRddiONjo6VUsoenYdr6B0XyZX%2Bk8oGqsPKhHGEfNCPig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Propose change in how frontends handle payloads

[Brian Granger]

> payloads are more than the pager. I think we are only talking about the
> pager payload, not other payloads like set_next_input that allow creation of
> cells, etc.

Yes, sorry about being too vague...just the pager...

> have implemented IPython’s ? and ?? twice in the message specification:
>
> invoking %pinfo formats output and triggers display via the pager payload
> inspect_request requests the same information at the protocol level,
> triggering the same code at the Python leel, but skipping the pager. This is
> how tooltips are produced (shift-enter some places, automatically others).
>
> Summarizing some discussion from the dev meeting: I support deprecating the
> pager in JupyterLab, and moving IPython’s default behavior of ? to produce
> regular output (I’ve used extensions to do this since about the beginning of
> the notebook, and it sounds like others have, too). The fact that JupyterLab
> can tear off output puts a big dent in the main reason to keep the pager in
> the notebook: that it can be independent of the document scrolling, and kept
> for reference.
>
> Argument for keeping the pager: not all frontends have JupyterLab’s setup.
> The console, for instance, would still benefit from sending this to the
> pager for the same reason terminal IPython does.
>
> -Min
>
>
> On Mon, Sep 26, 2016 at 8:07 PM, Jason Grout <ja...@jasongrout.org> wrote:
>>
>> That's how the Sage notebook has worked for as long as I remember: A cell
>> executed with ? and ?? render the relevant docs inline as output.
>> SageMathCloud does this too:
>> https://cloud.sagemath.com/projects/82a3ca9f-7a34-400b-86ee-98fb0b07f23c/files/2016-05-05-133427.sagews.
>> It is handy having it inline - the Sage tutorial uses this to explain ? and
>> ??, for example, and many other tutorials will discuss a function and then
>> do the function? to show the docs inline. HOWEVER, doing something like
>> `math.cos?` and pressing *tab* (instead of shift-enter) will either pop up
>> the completion (SMC) or render it temporarily in the output above existing
>> output, with an option to pop the output out into a dialog (old sage
>> notebook)
>>
>> This also would make the notebook more consistent with the terminal
>> console, where docs are rendered as outputs.
>>
>> Thanks,
>>
>> Jason
>>
>>
>> On Mon, Sep 26, 2016 at 10:06 AM Kyle Kelley <rgb...@gmail.com> wrote:
>>>
>>> Part of the reason we put the pager data within the output area was that
>>> we didn't want that "popup" experience and people seemed to like having it
>>> inline. We then faced, exactly as you put it, a lack of reproducibility of
>>> the notebook - people wanted to see that "output" of documentation right
>>> there.
>>>
>>> On Mon, Sep 26, 2016 at 8:01 AM, Brian Granger <elliso...@gmail.com>
>>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> For a while, the ipython kernel has had a flag that lets you send
>>>> payload message to regular output. I have run my ipython with this
>>>> enabled for a long time. In talking with Kyle this weekend, nteract
>>>> has decided to always render payloads as output.
>>>>
>>>> I would like to propose that we start to do the same in the classic
>>>> notebook and jupyterlab.
>>>>
>>>> The reasons are these:
>>>>
>>>> * If you have a cell with a ? ("math.cos?") no-one can see the result
>>>> of running that code in the notebook document (on github, nbviewer).
>>>> This means that the notebook isn't really reproducible.
>>>> * In JupyterLab, outputs can be dragged anywhere in the dock panel.
>>>> Thus, if you want the separate pager like experience we can still
>>>> offer it.
>>>> * The existing inspector in juptyerlab is overly complicated. This
>>>> would allow it to just focus on tooltips as the user types.
>>>>
>>>> Cheers,
>>>>
>>>> Brian
>>>>
>>>> --
>>>> Brian E. Granger
>>>> Associate Professor of Physics and Data Science
>>>> Cal Poly State University, San Luis Obispo
>>>> @ellisonbg on Twitter and GitHub
>>>> bgran...@calpoly.edu and elliso...@gmail.com
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Project Jupyter" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>

Re: [jupyter] CSS for cell output in notebook

[Brian Granger]

Kyle,

Thanks for posting about the JSON table schema here. I do think it
would be great to start building support for that...

Cheers,

Brian

On Thu, Sep 29, 2016 at 7:27 PM, Kyle Kelley  wrote:
> Since I noticed deep within you mentioned nice custom table formatting --
> would you consider exporting a custom mimetype that uses
> http://specs.frictionlessdata.io/json-table-schema/ for the table spec? We
> can then write CSS to match tables and their output types directly.
>
>
> The difficulty with adjusting CSS is that it's not something specced at the
> same degree as the notebook format and message protocol are. We can always
> provide a "solution" that interoperates with some amount of CSS, but it's
> not a good long term solution.
>
> -- Kyle
>
> P.S. I totally use 

Re: [jupyter] nbconvert_reportlab: Alternative to convert notebooks to PDFs

[Brian Granger]

O, very nice!!!

On Thu, Sep 29, 2016 at 9:29 AM, Thomas Kluyver  wrote:
> In the last few days, I've put together an nbconvert plugin that uses
> Reportlab to generate PDFs directly, rather than building a Latex document
> and converting it to PDF.
>
> This is very new and experimental, and there are lots of things it doesn't
> support yet, but it has the potential to avoid a lot of the complexity that
> arises from generating and compiling Latex. It can also be entirely
> installed with pip, as the functionality it needs is all in Python packages.
>
> Example output:
> https://github.com/takluyver/nbconvert-reportlab/blob/master/Trapezoid%20Rule.pdf
>
> So far, it supports:
>
> - Code cells
> - Plain text output
> - PNG image output
> - Basic Markdown (no tables or footnotes yet)
> - Block maths (using matplotlib's mathtext renderer)
>
> Install with:
>
> pip install nbconvert_reportlab
>
> And use with:
>
> jupyter nbconvert --to pdf-rl MyNotebook.ipynb
>
> This also forms an example of shipping an exporter outside the nbconvert
> package, and of an
> exporter which does not use a template.
>
> Feel free to kick the tyres!
>
> Thomas
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAOvn4qg1fnpRoAyqS8uyPFhQMEqEQVk3fXpxMThSWxtbpQtReA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQD-W4XsBfP3nTM2AD04kGtvWHP_y_sJOCkeMM%3DM8nzjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Renewed tmpnb.org

[Brian Granger]

Thanks!

On Sat, Sep 24, 2016 at 6:03 PM, Kyle Kelley  wrote:
> Just thought I'd let everyone know I've renewed the domain for tmpnb.org.
>
> I also renewed http://armadalovelace.com, a domain I purchased as a tribute
> to Ada Lovelace and distributed computing? I'm not using it yet, but I sure
> hope someday I come up with something.
>
> --
> Kyle Kelley (@rgbkrk; lambdaops.com)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CA%2BtbMaVqsiiqRk5%2BD99ORz_sXzC4jKpEULH1JnGagEmCSD2QfQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpRhFX241czNtH_jafKbHP8Dci%2BLYO0C8GumF44FGkY_Vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Incorporate spell check into Markdown cells of notebooks?

[Brian Granger]

Thanks Doug, I opened an issue on the JupyterLab repo:

https://github.com/jupyter/jupyterlab/issues/846

On Sat, Sep 3, 2016 at 4:48 AM, Doug Blank <doug.bl...@gmail.com> wrote:
> On Fri, Sep 2, 2016 at 7:59 PM, Brian Granger <elliso...@gmail.com> wrote:
>>
>> Doug, is the spell checking code in the form a standalone npm package?
>
>
> I don't know. But the extension now installs with the standard jupyter
> methodology:
>
> $ git clone https://github.com/Calysto/notebook-extensions.git
> $ cd notebook-extensions
> $ jupyter nbextension install calysto --user
>
> Here is the code:
>
> https://github.com/Calysto/notebook-extensions/tree/master/calysto/spell-check
>
> It uses typo [1], with license here ("Typo.js is free software, licensed
> under the Modified BSD License."):
>
> https://github.com/Calysto/notebook-extensions/blob/master/calysto/spell-check/typo/license.txt
>
> Currently, only the English dictionary is included, but there are others
> available. There is also a custom word dictionary, but no UI for that.
>
> Please feel free to bring it under your umbrella. I would be glad to help
> continue to make it better.
>
> -Doug
>
> [1] - https://www.npmjs.com/package/typo-js
>
>
>>
>>
>> On Thu, Sep 1, 2016 at 7:30 AM, Doug Blank <doug.bl...@gmail.com> wrote:
>> > +1 from me too!
>> >
>> > I'd be glad to hand the Calysto spell checking code over to the Jupyter
>> > Project. The first time I met Fernando I mentioned that spelling
>> > checking is
>> > the most needed part of Jupyter. Couldn't live without it! It doesn't
>> > have
>> > right-click replace-with-correction, but still useable just as it is.
>> >
>> > You have to turn it on, but it should be always on, and no need for a
>> > button, IMHO.
>> >
>> > -Doug
>> >
>> > On Mon, Aug 29, 2016 at 6:23 AM, Logan Page <page...@gmail.com> wrote:
>> >>
>> >> +1 for spell check being a default feature.
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "Project Jupyter" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> >> an
>> >> email to jupyter+unsubscr...@googlegroups.com.
>> >> To post to this group, send email to jupyter@googlegroups.com.
>> >> To view this discussion on the web visit
>> >>
>> >> https://groups.google.com/d/msgid/jupyter/7a508c92-0538-4b00-9f34-ac3acd8aa0bf%40googlegroups.com.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Project Jupyter" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to jupyter+unsubscr...@googlegroups.com.
>> > To post to this group, send email to jupyter@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/jupyter/CAAusYCjj%3DeB4EPg%2BNeazwEUrMCNGdekeAht6UDtJFLyQsbsCgg%40mail.gmail.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Brian E. Granger
>> Associate Professor of Physics and Data Science
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgran...@calpoly.edu and elliso...@gmail.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAH4pYpQZzLZ77N%2B86o6a%3DLQ5Y4kuGvVtcdwO_7HNU0DqYOoMXA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAAusYChcjpix1Tzokm5zmfXZnscLjuK%2Bi2_iW-62%3DCMosGOoow%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQu_y6j17i_jtyi%2BjLgyi34kUcFwhAy3SrXEgNX4Egnhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Incorporate spell check into Markdown cells of notebooks?

[Brian Granger]

Doug, is the spell checking code in the form a standalone npm package?

On Thu, Sep 1, 2016 at 7:30 AM, Doug Blank  wrote:
> +1 from me too!
>
> I'd be glad to hand the Calysto spell checking code over to the Jupyter
> Project. The first time I met Fernando I mentioned that spelling checking is
> the most needed part of Jupyter. Couldn't live without it! It doesn't have
> right-click replace-with-correction, but still useable just as it is.
>
> You have to turn it on, but it should be always on, and no need for a
> button, IMHO.
>
> -Doug
>
> On Mon, Aug 29, 2016 at 6:23 AM, Logan Page  wrote:
>>
>> +1 for spell check being a default feature.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/7a508c92-0538-4b00-9f34-ac3acd8aa0bf%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAAusYCjj%3DeB4EPg%2BNeazwEUrMCNGdekeAht6UDtJFLyQsbsCgg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpQZzLZ77N%2B86o6a%3DLQ5Y4kuGvVtcdwO_7HNU0DqYOoMXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Our licenses have drifted from "pure" BSD, we should fix that...

[Brian Granger]

Great, thanks!

On Thu, Aug 18, 2016 at 5:43 PM, Fernando Perez  wrote:
>
> On Thu, Aug 18, 2016 at 11:43 AM, ellisonbg  wrote:
>>
>> Fernando,
>>
>> I think we should move forward with a decision on this issue. Some things
>> under consideration:
>>
>> * Replace "Project Jupyter Team" by "Jupyter Contributors" in our
>> copyright notice in files.
>> * Move to an exact copy of the BSD license rather than one with subtle
>> changes.
>>
>> Jason has proposed using the version of the BSD license from the OSI:
>>
>> https://opensource.org/
>>
>> I think you should make the call so we can move forward with things (or
>> not).
>>
>> If folks have concerns they have not voiced, please do so now :)
>
>
> Correct, this is what I said in Jason's open PR
> (https://github.com/jupyter/jupyterlab/pull/543):
>
> """
>
> I'm happy to merge it, and I'm +1 on the changes. Even accepting a certain
> amount of legal ambiguity around the notion of "contributors" as a copyright
> holder, I think right now it's the best we have to communicate the more
> complex and nuanced mouthful of "everyone in the repo holds individual
> copyrights to their changes, and therefore the copyright of the whole repo
> is the sum total of those contributions, all of which are jointly licensed
> under the BSD terms..."
>
> It's also somewhat accepted community-wide, so I think it's the best we're
> going to get for now. We can't paralyze every step of our process until the
> Supreme Court gives us an opinion :)
>
> """
>
> For reference, that PR already makes the changes listed by Brian above,
> which I think make sense (thanks Jason!).  Even if a lot of the open source
> community --us included-- is using this notion of "collective copyright"
> that will not satisfy a legal scholar, I also don't think it's a completely
> unreasonable stance to take.
>
> For the sake of community input, I'll leave it open now and will merge
> tomorrow Friday if there's no *new* concerns raised. If so, please put them
> up on the PR itself.
>
> Cheers,
>
> f
>
>
> --
> Fernando Perez (@fperez_org; http://fperez.org)
> fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
> fernando.perez-at-berkeley: contact me here for any direct mail



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTQvdmv0wPQfQzbvaueh_XkUKcQ3_jkHLSacT%3D%3D-yBRyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Moving towards a more structured team setup

[Brian Granger]

I want to emphasize that the content Fernando is sharing ghere is the
result of a process that started in April and has involved:

* A survey of core developers about which areas of the project they are
interested in and what level of effort they are planning on
* A series of semi-weekly meetings between myself, Jamie and Fernando going
through the results of that survey along with the different areas of the
project (repos, areas of focus, activities)
* Lots of offline work by Jamie is organizing everything

Cheers,

Brian

On Tue, Aug 16, 2016 at 12:52 AM, Fernando Perez <fperez@gmail.com>
wrote:

> Hi all,
>
> this is an email that is long overdue... As the project has grown in size
> and complexity, we have at times struggled with how to effectively
> coordinate, communicate and work in this larger context.
>
> At the dev meeting we conducted a survey of the folks who were there,
> looking for a way to slice the project into major areas and to identify who
> could assume leadership of each of these areas.  As usual, "leadership"
> here means mostly responsibility, not some vertical, unilateral definition
> of authority. In every area of the project we maintain an ethos of openness
> and collaboration, and we want participation to continue increasing.
>
> But the reality is that, at this size and number of moving parts, it's
> becoming detrimental not to have designated leads who can move things
> forward, focus and keep an eye on their area, and sometimes make decisions
> needed to get the ball rolling.  While I'm happy to maintain my role as
> project's BDFL as long as the community wants me to, that role can't mean
> that I make final decisions up and down our massive number of repos and
> project areas.
>
> In summary, this is about delegating for efficiency and improved
> communication.
>
> I'd like to post here the table of what we have so far.  Thanks to Jamie's
> dedicated crunching of the info, we have it now broken down by large areas
> and all active repos are assigned to an area.
>
> This isn't perfect, and in particular what is called tentatively "user
> engagement" includes a LOT of work on the broad/public-facing aspects of
> the project that will probably require more refinement.  But I don't want
> to keep delaying this any further.
>
> Please take a look at the table below, and let's see if we can agree on
> the roles and rough slicing.  In particular, folks whose name appears in a
> leadership role should mention whether they are OK with the idea, whether
> there's any other area they'd prefer to focus on, etc.
>
> I want to clarify that we did our best to digest people's survey
> responses, but I also did some moving around in an attempt to cover
> everything we have in the air.  If I moved you around in a way you didn't
> want, I apologize and just let's figure out a better solution.  I didn't
> intend to strong-arm anyone.
>
> Cheers,
>
> f
>
>
> Core
>
>
> Leader
> Min?
>
> Mostly FT Work
> Min Ragan-Kelley
>
> Mostly PT Work
> Carol Willing
> Thomas Kluyver
> Matthias Bussonnier
> Jason Grout
> Steven Silvester
>
> Projects/Functional Areas Repos
> jupyter_core jupyter_core <https://github.com/jupyter/jupyter_core>
> jupyter client jupyter_client <https://github.com/jupyter/jupyter_client>
> Python 2 Support
> message spec
> testpath <https://github.com/jupyter/testpath>
> jupyter_kernel_test <https://github.com/jupyter/jupyter_kernel_test>
> JupyterLab and J. Notebook
>
> Leader
> Brian Granger
> Matthias Bussonnier
> Jason Grout
>
> Mostly FT Work
> Steven Silvester
>
> Mostly PT Work
> Nicholas Bollweg
> Chris Colbert
> Afshin Darian
> Fernando Perez
> Peter Parente
> Thomas Kluyver
> Carol Willing
> Min Ragan-Kelley
> Damián Avila
> Projects/Functional Areas Repos
> single user server jupyter-drive
> <https://github.com/jupyter/jupyter-drive>
> classical notebook UI notebook <https://github.com/jupyter/notebook>
> Real Time Collaboration (RTC)
> Dashboarding (incubation)
> Element filtering
> jupyterlab jupyterlab <https://github.com/jupyter/jupyterlab>
> jupyter-js-services <https://github.com/jupyter/jupyter-js-services>
> jupyter-js-utils <https://github.com/jupyter/jupyter-js-utils>
> jupyter_logger <https://github.com/jupyter/jupyter_logger>
> Widgets
>
> Leader
> Sylvain?
>
> Mostly FT Work
> Grant Nestor
>
> Mostly PT Work
> Peter Parente
> Jason Grout
> Afshin Darian
> Steven Silvester
> Nicholas Bollweg
> Brian Granger
> Jonathan Frederic
> Projects/Functional Areas Repos
> ipywidgets ipywidgets <https://github.com/ipyt

Re: [jupyter] Real-time collaboration

[Brian Granger]

To clarify, we do plan on adding real-time collaboration to JupyterLab

On Fri, Aug 5, 2016 at 9:09 AM, Matthias Bussonnier
 wrote:
> Hi Pablo,
>
> The current state of JupyterLab is to reach feature parity with the
> current notebook, then we will look at extending the functionality.
> We'll likely start to investigate before, but not at full speed.
>
> We don't have the ability yet in lab to have the notebook in it's own page.
> --
> M
>
> On Thu, Aug 4, 2016 at 9:29 PM,   wrote:
>> Hi Fernando,
>>
>> What is the scope of JupyterLab?
>> https://github.com/jupyter/jupyterlab
>>
>> The README says:
>> "An extensible computational environment for Jupyter"
>>
>> I'm not sure what it means but it seems to have a broader scope than just
>> hooks for OT.
>> Will I be able to use OT with a notebook with minimal UI? For example
>> without a file browser.
>>
>> Is there a specific issue can I track for progress?
>>
>> Thanks
>>
>> On Thursday, August 4, 2016 at 4:00:15 AM UTC+3, Fernando Perez wrote:
>>>
>>> Hi Pablo,
>>>
>>> On Wed, Aug 3, 2016 at 5:46 PM,  wrote:

 Hi,

 Can several users edit the same notebook in real-time or maybe it's on
 the roadmap?

 If not, how can we implement it?
 What's needed is a way to handle operational transformation ops per cell
 on the server and client.
 On the server we need a gateway between the client and the kernel that
 will transform ops and inform other clients.
 On the client we need a way to receive ops, transform them and push
 changes to cells.

 Any pointer?
>>>
>>>
>>> Yup, we think that with the APIs in JupyterLab this will be in general
>>> much easier to implement, as they have been designed precisely with that in
>>> mind.  Ian Rose is a new postdoc starting in a few weeks with me at Berkeley
>>> who will focus on that problem; now that we're getting JLab in a pretty
>>> usable state for everyday work, we hope to move quickly on this...
>>>
>>> Cheers
>>>
>>> f
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/ec7505c3-b7b3-4c13-b6d6-8e183957b3bd%40googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/CANJQusXhNO0xgCRzVkHAP3SGmm0B1YZ%2BkoHg0TSNKjA74Zcv2g%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAH4pYpTqYrTp6VpQ5HzU9YJZUARRAVLU_-D61E1xgvaBGzaWow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Our licenses have drifted from "pure" BSD, we should fix that...

[Brian Granger]

Thanks!

On Mon, Jul 25, 2016 at 8:16 PM, Jason Grout <ja...@jasongrout.org> wrote:
> Makes sense. I've put in a PR to JupyterLab with this change so we can see
> what it looks like: https://github.com/jupyter/jupyterlab/pull/543/files
>
> I also switched the clauses to use numbering, like on the opensource.org
> website template.
>
> Jason
>
>
>
> On Mon, Jul 25, 2016 at 11:12 PM Brian Granger <elliso...@gmail.com> wrote:
>>
>> On Mon, Jul 25, 2016 at 7:58 PM, Jason Grout <ja...@jasongrout.org> wrote:
>> > For a specific project, say JupyterLab, should we "JupyterLab
>> > contributors",
>> > to indicate that those individuals who contributed to that specific
>> > project
>> > are the ones that hold copyright? Or should we give the generic "Project
>> > Jupyter Contributors"
>>
>> Because people tend to move fluidly between different
>> repos/subprojects, I would prefer the generic "Project Jupyter
>> Contributors". Also this more easily covers situations where we
>> re-organize code between repos/subprojects, as tends to happen
>> sometimes...
>>
>> Cheers,
>>
>> Brian
>>
>> >
>> > Also, FYI, the Wikipedia text has the place for 'copyright holders' as a
>> > templated term, perhaps that's where we got the other text:
>> >
>> > https://en.wikipedia.org/wiki/BSD_licenses#3-clause_license_.28.22Revised_BSD_License.22.2C_.22New_BSD_License.22.2C_or_.22Modified_BSD_License.22.29
>> >
>> > Thanks,
>> >
>> > Jason
>> >
>> >
>> >
>> >
>> > On Mon, Jul 25, 2016 at 7:50 AM Damián Avila <damianav...@gmail.com>
>> > wrote:
>> >>
>> >> +1 to use the real BSD.
>> >>
>> >> >But if using the plural "Contributors" text is clearer than the
>> >> > collective "Team", that's fine, too, and changes no meaning.
>> >>
>> >> +1 too.
>> >>
>> >>
>> >>
>> >> 2016-07-25 8:40 GMT-03:00 MinRK <benjami...@gmail.com>:
>> >>>
>> >>> +1 to the change. Not quite sure how we drifted there, but it may well
>> >>> have been my doing during the split. We have defined in our IPython
>> >>> license
>> >>> file "The IPython Development Team is the set of all contributors to
>> >>> the
>> >>> IPython project," so it is already synonymous with Contributors, and
>> >>> has
>> >>> never been an entity. But if using the plural "Contributors" text is
>> >>> clearer
>> >>> than the collective "Team", that's fine, too, and changes no meaning.
>> >>>
>> >>> -MinRK
>> >>>
>> >>> On Sat, Jul 23, 2016 at 3:44 AM, Fernando Perez <fperez@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi all,
>> >>>>
>> >>>> I recently noticed that there's something funny about the way our
>> >>>> license is worded compared to the BSD template...
>> >>>>
>> >>>> Our licenses say
>> >>>>
>> >>>> "Neither the name of JupyterLab...", "... name of Jupyter...", etc...
>> >>>>
>> >>>> But the original BSD template reads
>> >>>> (https://opensource.org/licenses/BSD-3-Clause)
>> >>>>
>> >>>> "Neither the name of the copyright holder..."
>> >>>>
>> >>>> and the term "copyright holder" isn't a variable to template over,
>> >>>> just
>> >>>> the words "copyright holder".  In our case, that is "Project Jupyter"
>> >>>> in
>> >>>> some licenses, and I'd argue it should read "Project Jupyter Team" to
>> >>>> indicate that it's the *people*, not the abstract/legal project
>> >>>> entity...
>> >>>>
>> >>>> I didn't realize that our licenses had changed in this way, but in a
>> >>>> sense we are NOT using BSD!  We've made a subtle but important
>> >>>> change, as
>> >>>> we've basically added a trademark barrier in the third clause (hence
>> >>>> this
>> >>>> question the person is asking), whereas the original third c

Re: [jupyter] Thanks for SciPy, and Tomorrow's JupyterHub Miniworkshop

[Brian Granger]

Matthias,

Thanks for the thoughtful and complete summary!

Cheers,

Brian

On Thu, Jul 21, 2016 at 11:55 AM, Matthias Bussonnier
 wrote:
> Hello all,
>
> As you might have seen, last week was SciPy2016 in Austin, so most of us
> were
> overwhelmed during a week, it will take us quite some time to catch up with
> the
> back-log. If you've asked a question, opened an issue, and still don't have
> a
> response, it probably slipped through the crack, so as usual feel free to
> ping
> us after some time, or open a new one !
>
> We can and will do better ! If you are a new user looking to start
> contributing
> a few new issues on IPython and JupyterLab are easy for a beginner and would
> have a high impact ! Feel free to come by!
>
> I feel like I'm seeing more and more answer on the mailing list and on
> GitHub
> done by many who are not among the main developers. Thanks to all of you who
> pitch in on Stack Overflow, Reddit, HackerNews, Twitter and the various
> mailing
> list, and even to those that do Jupyter Tech Support in person ! We try to
> blur
> the line between developers and users, and seeing a good chunk of the
> knowledge
> to be in the community hands is great !
>
> Many of side projects I have seen last week are of really good quality and
> it
> would be worth discussing integrating then into the main repositories by
> default.
>
> SciPy was an extremely extremely useful event, to meet with our user base,
> and
> even to be able to work with other developers we only have the chance to
> meet
> every now and then. Thanks to all the sponsors who allowed that to happen.
>
> I want to send big thanks to all the JupyterLab team who worked hard behind
> the
> scene, and did a fantastic job before SciPy and an even better one during
> SciPy, literally fixing bug and rebasing PRs at the last minutes before the
> JupyterLab presentation.
>
> Afshin, Chris, David, Jason, Steven, Sylvain as well as Ryan who help with
> one
> of the first JupyterLab plug-in before the Main presentation, and have been
> pushing JupyterLab and Phosphor forward for a year now.
>
> Huge thanks to Brian and the CalPoly folks that are also doing a lot of work
> that often does not end up in GitHub metrics. In particular a huge chunk of
> SciPy was spent doing user testing on the new JupyterLab, so thanks to:
>
> Charnpreet, Elliot, Farica, Katie, Matt, Reese, Roshan, Spoorthy, as well as
> the ~30 users that gave us some of their time to be guinea pig and tried the
> new JupyterLab, while they were recording [they got a new triblend Jupyter
> Shirt].
>
> We also had various kind of feedback from users, like for example concern
> about
> wether the notebook format would change (No it will not), and various other
> comments and questions we will try to address during the next few weeks
> while we
> catch up and get through all the notes we have taken.
>
> If you were there you might have met Ana who took care of the organisation
> (we/you wouldn't have Jupyter T-shirt without her), Jamie our project
> manager,
> who is making sure we keep our head on our shoulders, and Carol our
> Documentation grand master.
>
> Let's not forget Min, who gave a multiple talks on ipyparallel/Dask, Jess
> who gave an extremely popular talk about nbflow, and Mike who is slowly
> starting
> to get up to speed on the project.
>
> We missed many of you who couldn't made it this year, like Fernando, Thomas,
> Kyle, Jon, ... And hope to see you next year.
>
> Don't forget to subscribe/ check the newsletter, that should get more
> information and links soon ! (https://newsletter.jupyter.org/)
>
> And don't forget to join tomorrow JupyterHub MiniWorkshop:
>
>> https://github.com/jupyter/jupyterhub-2016-workshop
>
> I'm  sure I've forgotten something/someone and will realize just after
> posting this, apologies if it's the case.
>
> Thanks to all,
>
> --
> M
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/797ae351-c395-4431-b08b-bf47e2d26c9a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgran...@calpoly.edu and elliso...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit