Re: [jupyter] Checkpoints and Autosaves under Jupyter

[DG]

Like for many others, this *DOES NOT WORK FOR ME.*

I really dislike autosave. PLEASE give us a way to permanently turn that 
off.


Thank you.

dg





On Monday, January 4, 2016 at 1:20:06 AM UTC-8, Min RK wrote:
>
> On Mon, Jan 4, 2016 at 1:21 AM, Jean Bigboute  > wrote:
>
> I often download Python tutorial notebooks from Github and go through them 
>> on my local machine. Notebook's Autosave updates the files as I am playing 
>> with them. If I want to discard my modifications and start fresh, the only 
>> way I seem to be able to is to either make a backup before starting or to 
>> download the notebook file again from Github. 
>>
>> I am running Python 2.7 via Anaconda on Mac OSX El Capitan 10.11.2 using 
>> Safari (mostly) and Firefox (occasionally).
>>
>> Questions:
>> 1) Is it possible to save more than one Checkpoint? If I save/restore, I 
>> only see one item in the Restore Checkpoint flyout
>>
> With a custom CheckpointsManager, but not the default one. I’m not sure if 
> there is one readily available that provides this.
>
>
>> 2) Is it possible to turn off Auto Save by default?
>>
> Yes, in ~/.jupyter/custom/custom.js:
>
> require(['base/js/namespace', 'base/js/events'], function (IPython, events) {
>   events.on("notebook_loaded.Notebook", function () {
> IPython.notebook.minimum_autosave_interval = 0; // disable autosave
>
>   });
> });
>
> -MinRK
>
>
>> I found some threads on this for IPython notebooks using magics and 
>> config files. Magics have to be executed per notebook and I understand 
>> there have been changes to the config file system in general in Jupyter.
>>
>> Unrelated question:  Is there a way to interact with this group from a 
>> newsreader?  gmane.comp.programming.jupyter allows reading but not posting.
>>
>> -- 
>> 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/07d5a480-aca3-41e6-8285-d7e0a7a8b8fc%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/85edcd2b-1319-42b5-96e2-7f742df4d1c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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.

[jupyter] Preparing for IPython 6.0

[Matthias Bussonnier]

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.

[jupyter] Jupyter Dev Meeting, 2017, Week 9 summary

[Matthias Bussonnier]

Hi Everyone,

This is my attempt at writing a weekly summary of our video meeting we have 
each
Tuesday. I’m using the notes that have been taken during the meeting by the
collective effort so the quality of the section depends highly on the 
quality of
the notes taken.

There was no summary last week, so no week 8, as I got stuck because of 
weather.
Sorry about that. As usual any help welcome. I also try to keep writing this
summary under 30 min.

With S3 outage, I had difficulty getting the notes in a markdown format so
edition of notes will be likely really lite this week. 
Weekly news by organization 

We’re experimenting with weekly auto generation of statistics. 

   - IPython 
    
   (in progress) 
   - Jupyter 
    
   (in progress) 
   - JupyterLab 
   
 
   - Jupyter-widgets 
   

 
   - JupyterHub 
    

Carol still run these by hand, any help would be welcome to streamline this 
using travis-ci crons. 
Project management 
   
   - We’ll use Dropbox paper for another month 
   - Project management tools team tutorial held last Friday, February 24. 
   I will
   post the video and summary to the mailing list after finishing the annual
   report due Weds. 
   - Attended the 
*Hacking at time-bound events*  
   workshop at *CSCW* in
   Portland this last Saturday, February 25 (http://cscw.acm.org/2017 -
   Computer-Supported Cooperative Work and Social Computing). Next step is 
   to
   share workshop outcomes with @Safia & @Kyle K in preparation for 
   JupyterCon
   sprints. 
   - *Binder* sustainability work is moving forward. Next discussion is 
   early
   next week. 
   - *I’ll be at UC Davis next Wednesday morning* to observe Tracy Teal’s 
   launch
   of the Publishing and Sharing lessons from the Data Carpentry 
   Reproducible
   Research Curriculum. 
   - Giving a *Jupyter overview talk* for the Association for Women in 
   Science
   (AWIS) next Wednesday night in SF. 
   - Min and Carol are visiting UC Berkeley next week 
   - Ryan Lovett will try to record the 
*accessibility workshop next Monday, March 6*. So far, Pete, Min, Mike, 
   Darian, Ian, Matthias, and Yuvi are attending. 

IPython 

We are closing in on 6.0 (https://github.com/ipython/ipython/milestone/33) 
less
than 25 open issues/PR. Help and feedback welcome. If there are any issue 
that
you care about not targetted fro 6.0 let us know. 

There’s some work ongoing on automating release steps
(https://github.com/ipython/ipython/issues/10342), to reduce the amount of 
time
we need to spend making releases. Hopefully this will generalize to other
projects.

Meeseeksdev infer branch to backport to (based on milestone). Just need to 
do
@meeseeksdev backport now. 5 more seconds gained to backport PRs !

We are attending a Docathon next week, we’ll focus on writing more docs for
IPython and Jupyter. Feel free to join us to help and contribute ! See the
docathon website: https://bids.github.io/docathon/

Some Ideas:

   - Cross-link more function/class/module names in docs with sphinx’s 
   :any: role 
   - Make config options individually linkable with a custom role (see what 
   we do
   for magics as an example) 
   - Document JSON config: https://github.com/jupyter/jupyter/issues/242 

Notebook (Grant, Thomas, Jason) 

Closing in on 5.0 (https://github.com/jupyter/notebook/milestone/5) - 4 open
issues remaining. We’ll hopefully have RC1 or beta2 in the next couple of 
days.

Improving UI for move files dialog: 
https://github.com/jupyter/notebook/pull/2234
nbconvert (Mike) 
   
   - 
   
   Wrestling with fonts, encodings, LaTeX, Unicode coverage and Travis (see
   issue 533  and pr
   537 )
   - The solution may be to just have a more directly controllable server on
  which we test using a custom build (rather than trying to convince 
  travis to
  behave nicely). 
  - If anyone has particularly strong feelings about fonts/typography, 
  the
  solution is likely to involve changing the default export fonts, so 
  you may
  want to keep an eye on that issue and pr. 
  - I’m going to be thinking about how to move to a more configurable 
  setup for
  people to customise 
   
Services - kernel gateway, docker-stacks (Pete) 

nbviewer has been having issues hitting the GitHub API rate limit recently.
After some investigation, a few SEO bots have been identified as the primary
cause, and action taken:

   1. block two ips driving a huge amount of traffic (in fastly) 
   2. 

Re: [jupyter] Re: Release statistics

[Matthias Bussonnier]

A little late but look in ipython/tools/github_stats.py that's what we
use for each IPython release.
-- 
M

On Tue, Feb 28, 2017 at 2:51 PM, Jason Grout  wrote:
> A start, specific to the ipywidgets release, is at
> https://gist.github.com/jasongrout/b788f91ef2dfcafa12775e931c3553c5
>
> On Tue, Feb 28, 2017 at 3:01 PM Jason Grout  wrote:
>>
>> We're writing the release notes for ipywidgets. Does anyone happen to know
>> or use a script to generate various stats from git or GitHub for releases?
>> Things like number of committers, first-time committers, how long it's been
>> since the last release, how many PRs were merged or issues closed, how many
>> commits, etc.?
>>
>> (If not, we may just write one... :)
>>
>> Thanks,
>>
>> Jason
>>
> --
> 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/CAPDWZHz6bHbuCY5qtAgzD-OucKwP2NWbjGjWcGjoMFUei3zbRw%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/CANJQusWMzF9THz52nFijS5B3xJWEdt0Of-x3YeFu-7f74TJ63A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: Release statistics

[Jason Grout]

A start, specific to the ipywidgets release, is at
https://gist.github.com/jasongrout/b788f91ef2dfcafa12775e931c3553c5

On Tue, Feb 28, 2017 at 3:01 PM Jason Grout  wrote:

> We're writing the release notes for ipywidgets. Does anyone happen to know
> or use a script to generate various stats from git or GitHub for releases?
> Things like number of committers, first-time committers, how long it's been
> since the last release, how many PRs were merged or issues closed, how many
> commits, etc.?
>
> (If not, we may just write one... :)
>
> Thanks,
>
> Jason
>
>

-- 
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/CAPDWZHz6bHbuCY5qtAgzD-OucKwP2NWbjGjWcGjoMFUei3zbRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Re: Second release candidate for ipywidgets 6.0

[Jason Grout]

We've already uploaded 6.0 (shh, we're still writing out the release notes
and getting conda-forge packages built). However, I think we could probably
push out a 6.0.1 with this and whatever other issues might crop up in the
first few days.

Thanks,

Jason


On Tue, Feb 28, 2017 at 5:41 PM nicolas.fr <
nicolas.lecle...@synchrotron-soleil.fr> wrote:

> Hi Sylvain,
> - It seems that the new 'bar_color
> ' style attribute is
> only available for IntProgress. Is there a change to also have it for
> FloatProgress in the release 6?
> - Thanks a lot for switching back to lowercase by default for buttons.
> Nicolas.
>
>
>
>
> Le lundi 27 février 2017 20:18:22 UTC+1, Sylvain Corlay a écrit :
>
> Hi All,
>
> A few days after the first release candidate, and thanks to the useful
> feedback on the first release candidate, I am pleased to announce a new
> release candidate for ipywidgets 6.0.
>
> This has been a team effort of many, many individuals. We want to
> especially mention the following developers who have made major
> contributions in this release (alphabetical order).
>
> Afshin Darian
> Jeroen Demeyer
> Jonathan Frederic
> Brian Granger
> Jason Grout
> Paul Ivanov
> Grant Nestor
> Cameron Oelsen
>
> There are many changes in the 6.0 release of ipywidgets, including the
> items currently listed in the changelog at http://ipywidgets
> .readthedocs.io/en/latest/changelog.html.
>
> You can check out this release candidate by running the following commands
>
> pip install ipywidgets --pre
> jupyter nbextension enable --py --sys-prefix widgetsnbextension
>
> We encourage you to test the RC and let us know of any issues you find. We
> expect this release candidate to be the last one and cut a final release in
> the next couple of days.
>
> Thanks,
>
> Sylvain
>
> --
> 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/70509fef-cc5f-46eb-9797-076ece5beea9%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/CAPDWZHwnB_kGOYov%2BqkGAWcA%2Bq6qDKOnaUaidERB%2BAJoDNKmBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Re: Second release candidate for ipywidgets 6.0

[nicolas.fr]

Hi Sylvain,
- It seems that the new 'bar_color 
' style attribute is only 
available for IntProgress. Is there a change to also have it for 
FloatProgress in the release 6?
- Thanks a lot for switching back to lowercase by default for buttons. 
Nicolas.




Le lundi 27 février 2017 20:18:22 UTC+1, Sylvain Corlay a écrit :
>
> Hi All,
>
> A few days after the first release candidate, and thanks to the useful 
> feedback on the first release candidate, I am pleased to announce a new 
> release candidate for ipywidgets 6.0.
>
> This has been a team effort of many, many individuals. We want to 
> especially mention the following developers who have made major 
> contributions in this release (alphabetical order).
>
> Afshin Darian
> Jeroen Demeyer
> Jonathan Frederic
> Brian Granger
> Jason Grout
> Paul Ivanov
> Grant Nestor
> Cameron Oelsen
>
> There are many changes in the 6.0 release of ipywidgets, including the 
> items currently listed in the changelog at http://ipywidgets
> .readthedocs.io/en/latest/changelog.html.
>
> You can check out this release candidate by running the following commands
>
> pip install ipywidgets --pre
> jupyter nbextension enable --py --sys-prefix widgetsnbextension
>
> We encourage you to test the RC and let us know of any issues you find. We 
> expect this release candidate to be the last one and cut a final release in 
> the next couple of days.
>
> Thanks,
>
> Sylvain
>

-- 
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/70509fef-cc5f-46eb-9797-076ece5beea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Release statistics

[Jason Grout]

We're writing the release notes for ipywidgets. Does anyone happen to know
or use a script to generate various stats from git or GitHub for releases?
Things like number of committers, first-time committers, how long it's been
since the last release, how many PRs were merged or issues closed, how many
commits, etc.?

(If not, we may just write one... :)

Thanks,

Jason

-- 
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/CAPDWZHx9uOe8qU2xro_yt8untVx%2B1t5h_1BZu-n6750wo8bRpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Second release candidate for ipywidgets 6.0

[Paul Hobson]

Thanks Sylvain. The docs are very well done!

On Mon, Feb 27, 2017 at 11:18 AM, Sylvain Corlay 
wrote:

> Hi All,
>
> A few days after the first release candidate, and thanks to the useful
> feedback on the first release candidate, I am pleased to announce a new
> release candidate for ipywidgets 6.0.
>
> This has been a team effort of many, many individuals. We want to
> especially mention the following developers who have made major
> contributions in this release (alphabetical order).
>
> Afshin Darian
> Jeroen Demeyer
> Jonathan Frederic
> Brian Granger
> Jason Grout
> Paul Ivanov
> Grant Nestor
> Cameron Oelsen
>
> There are many changes in the 6.0 release of ipywidgets, including the
> items currently listed in the changelog at http://ipywidgets.readthedo
> cs.io/en/latest/changelog.html.
>
> You can check out this release candidate by running the following commands
>
> pip install ipywidgets --pre
> jupyter nbextension enable --py --sys-prefix widgetsnbextension
>
> We encourage you to test the RC and let us know of any issues you find. We
> expect this release candidate to be the last one and cut a final release in
> the next couple of days.
>
> Thanks,
>
> Sylvain
>
> --
> 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/CAK%3DPhk6eRJDuTBO7kgPbau-xhGqHTVwd4hHA69tAoOpfO-bx8Q%
> 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/CADT3MEAO6ATDjX8oBkAG4SE2jZBqai0s71H7D%2B1jKhky-U8V9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.