These are chat archives for ipython/ipython

28th
Jan 2015
Thomas Kluyver
@takluyver
Jan 28 2015 17:46
There are over 1000 issues and PRs closed with the 3.0 milestone :clap:
Sylvain Corlay
@SylvainCorlay
Jan 28 2015 17:47
:100:
come on, there is a 100 icon but not 1000?
This message was deleted
This message was deleted
Thomas Kluyver
@takluyver
Jan 28 2015 17:52
:100: 0
tada!
Sylvain Corlay
@SylvainCorlay
Jan 28 2015 17:52
doesn't work, tried with :o:
Thomas Kluyver
@takluyver
Jan 28 2015 17:53
1 :loop: :o:
Sylvain Corlay
@SylvainCorlay
Jan 28 2015 17:53
This message was deleted
One needs to reach 1024.
Anton Akhmerov
@akhmerov
Jan 28 2015 17:55
By the way, how come github considers 2.1.0 the latest release?
Min RK
@minrk
Jan 28 2015 17:59
@akhmerov GitHub is weird. tags ~= releases
but the release list only shows tags with manual comments added
Anton Akhmerov
@akhmerov
Jan 28 2015 18:01
Ah, ok. Makes perfect sense.
Min RK
@minrk
Jan 28 2015 18:01
Since we really publish releases on PyPI, not GitHub, the GitHub release list isn't super useful.
Anton Akhmerov
@akhmerov
Jan 28 2015 18:02
Yes, sure. Just curious.
3.0 won't have any impact on static widgets? jakevdp/ipywidgets are immensely useful when using notebooks for teaching, but it's Jake's pet project that didn't see light of day for more than a year.
Min RK
@minrk
Jan 28 2015 18:06
I'm not sure. Lots of widget APIs have changed.
Though, if I recall, Jake's stuff doesn't use our widget APIs, but rather raw HTML, javascript output
those should remain fine
Anton Akhmerov
@akhmerov
Jan 28 2015 18:07
Exactly. I rather wondered if any of new stuff makes creation of static widgets easier.
Min RK
@minrk
Jan 28 2015 18:07
To some degree. We wanted to get farther, but we got a few building blocks in place.
Jason Grout
@jasongrout
Jan 28 2015 19:22
Yes, I think some of the new stuff makes static widgets easier. There's built-in functionality to store widget state, hook widgets up to each other in javascript (so it would work with a static notebook), etc.
Anton Akhmerov
@akhmerov
Jan 28 2015 19:22
Where is the widget state stored? In the notebook?
Jason Grout
@jasongrout
Jan 28 2015 19:22
it's not all there yet, but I agree with @minrk that there are some good building blocks now in place.
You can store the widget state wherever you want - by default, it uses html5 localstorage.
so in the browser. But you could easily store it in notebook metadata
Anton Akhmerov
@akhmerov
Jan 28 2015 19:23
Ok, that sounds very cool indeed.
Future will be wonderful, too bad it's too late for the launch of my course. Well, maybe somewhere midway.
Thomas Kluyver
@takluyver
Jan 28 2015 22:22
@jdfreder @minrk and any others who might be interested - does anyone want to offer further opinions on #7609, Jason's PR to simplify install_nbextension() to only take one file/folder at a time? If not, I'll click the button.
Sylvain Corlay
@SylvainCorlay
Jan 28 2015 22:26
+1
if you have a green-button-urge, feel free to #7603
nevermind :)
Thomas Kluyver
@takluyver
Jan 28 2015 22:27
the urge isn't strong enough to merge things marked 4.0
I'm not an addict (I can stop any time I like) ;-)
Sylvain Corlay
@SylvainCorlay
Jan 28 2015 22:27
bummer
Brian E. Granger
@ellisonbg
Jan 28 2015 23:23
Hi folks, I used latest master for a presentation today. Things are looking really good! Lots of jaws hit the floor...
Jason Grout
@jasongrout
Jan 28 2015 23:24
Awesome!
Were they familiar with 2.1?
(was it the new stuff between 2.1 and 3.0, or just the general notebook/other things?)
Brian E. Granger
@ellisonbg
Jan 28 2015 23:26
A mix of new and existing users
Jason Grout
@jasongrout
Jan 28 2015 23:26
what in particular was well-received? I'm really curious.
Anton Akhmerov
@akhmerov
Jan 28 2015 23:26
And which particular things were looking good?
Jason Grout
@jasongrout
Jan 28 2015 23:56
@takluyver: a simple bug in the nbextension stuff: ipython/ipython#7625