►
From YouTube: Jupyter/IPython Dev Meeting, December 13, 2016
Description
Meeting of the IPython/Jupyter development team, December 13, 2016
A
Let's
see
looking
at
the
hack
pad
for
this
week,
it
looks
like
in
the
project
management
realm.
We
have
the
code
of
conduct
materials
that
are
almost
ready
and
we'll
finish
that
up
in
the
next
day
or
two
and
we'll
update
the
PR,
the
Jupiter
governance
number
23
to
remove
the
whipped
label.
So
we
can
wrap
that
up,
so
you
can
look
for
it
there
do
you
want
to.
B
Yeah
yeah
I'll
try
to
get
that
I
already
have
the
remaining
documents
for
the
conduct
that
we're
missing
so
I'll.
Try
to
have
a
pushed
out
today
tomorrow
and
with
different
con
I
think
it's
time
that
we
start
telling
people
to
put
it
on
their
calendars,
because
the
the
ink
is
dry
on
the
contract
for
Jupiter
con
will
make
an
announcement,
my
mailing
list
and
we're
working
on
a
call
for
proposals.
But
but
at
least
now,
I
think
we're
completely
confident
that
it
will
happen
on
august
twenty-first
through
the
25th.
B
It
will
be
in
New,
York
City,
and
so
anyone
who
has
ideas
suggestions
speakers
would
make
good
invited
keynote.
Speakers
I
mean
obviously
we'll
have
a
standard
on
call
for
proposals
for
to
review
talks,
but
for
invited
speakers
on
ideas
of
cool
things.
We
could
or
should
do
please
pitch
in
I'll,
be
sending
in
an
elephant
the
mailing
list
as
soon
as
I
can
and
we're
working
on
the
CFP.
B
If
anyone
I
deliberately
didn't
try
to
add
everyone
in
our
group
to
the
to
be
the
program
committee,
because,
first
of
all,
we
want
to
spread
out
a
mix
of
people
in
the
team
and
in
the
community
and
second
I,
don't
want
to
sort
of
over
loved
everyone
in
the
development
team
with
that
kind
of
work.
But
if
everyone
really
really
really
wants
to
be
in
the
program
committee,
obviously
let
us
know
it's
basically
going
to
be
a
combination
of
reviewing
talks
and
some
other
tasks
related
to
sort
of
confidence.
A
I'm
catching
up
from
being
out
of
that
room
about
four
days
a
week.
That's
pretty
sick!
Last
week,
so
I
only
had
one
day
of
work
on
that
one
day,
I
was
really
able
to
get
any
work
in,
hopefully
had
some
give
it
to
Fernando
and
so
tonight
I'm,
giving
a
talk
at
for
highlighting
hi.
Ladies
at
Bloomberg,
we're
going
to
do
a
beginner
demo
an
overview
and
have
a
little
install
party
to
get
people
started
with
with
the
Jupiter,
so
it'll
probably
be
recorded.
B
A
D
Can
I
can
say
a
thing
or
two
so
grant
released
notebook,
4.3
I
fixed
some
bugs
and
AZ
yeah?
It
was
fantastic,
I
fixed,
some
bugs
and
the
async
stuff
and
got
a
added
functionality
to
get
the
ipad
widgets
output
widget.
Finally,
working
and
there
was
a
yeah
there
was
a
push
to
get
4.3
out.
So
fixing
remaining
issues
for
4.3
Oh.
B
Jason
one
foot
comment:
it
might
be
a
good
idea
to
send
a
send
I
mean
I,
know
that
now
we
have
more
frequent
small
releases
but
still
to
send
an
email
to
the
things
was
good
for
free
one
before
the
general
mailing
list.
Okay.
Over
with,
where
is
it
one
bit
up,
but
it's
covered
that
just
right
away?
Okay,
so
let's
do
the
fourth
we
won
and
then
maybe
something
that's
been
to
the
mailing
list
at
the
time
but
yeah
it
gets
good
visibility
to
put
things
on
the
general
Danvers.
Yes,.
D
About
that,
but
then
I
realized
that
they
I'd
mention
it
in
the
dev
meeting,
notes
and
I
just
had
missed
it
in
the
dev
meeting
notes.
So
so
the
protocol,
I
think,
was
followed
up
to
the
release
yeah,
but
I
would
just
remind
people
to
please
let
everyone
know
about
the
release.
Wait
for
the
dev
meeting.
If
you
can,
let
everyone
know
about
the
release
to
see
if
there's
any
any
changes
that
need
to
go
in
and.
B
Actually,
things
like
this
are
still
I
mean.
The
mailing
list
is
still
there
precisely
for
a
good
reason
that
it's
a
good
place
to
broadcast
these
kinds
of
things.
So,
for
example,
if
somebody
has
a
hey
last
call
we're
ready
for
release,
that's
the
kind
of
message
that
is
good
to
have
on
the
gentleman
list,
but
we
all
see
it-
everybody
everybody
gets
it
on.
Even
if
people
just
read
that
heading
up
a
message,
and/or
have
it
right
away,
at
least
if
in
black
yeah
yep.
F
Just
continuing
on
some
state
restoration
stuff,
there
isn't
really
a
visual
difference
from
what
was
there
last
week,
but
there
were
some
bugs
and
also
the
interface
for
plug-in.
Authors
is
a
lot
simpler
now.
So,
if
you
look
at
that
outstanding
PR,
you
will
see
that
each
of
the
plugins
the
way
it
the
way
it
restores
its
state
is
just
a
lot
simpler.
So
hopefully
that
lowers
the
barrier
for
plugin
authors
and
I'm.
Just
continuing
on
that.
That's
it
for
me,
oh
very
ni!
B
I
just
wanted
to
thank
you
for
all
that
all
that
work
on
on
state
management
because
I've
been
benefiting
from
it
lately
I've
given
a
couple
of
demos
and
talks,
and
it's
been
really
really
useful
good
to
be
able
to
get
my
get
all
my
stuff
back
whenever
load
the
page,
oh
yeah,
great
work.
Oh,
that's
a
huge
usability
improvement
and.
D
B
D
B
F
D
It's
been
a
busy
week
against
Elvin
and
Paul.
Even
off
and
I
have
been
working
on
it.
A
lot
and
grant
has
been
working
on
a
little
bit
and
mike
has
been
working
on
it
from
the
env
converting
goal
as
well.
So
sylvans
been
working
hard
on
getting
widgets
working
in
the
docs
they
would.
They
apparently
work
in
the
docks
now
and
as
of
a
few
minutes
ago,
working
in
B
convert.
D
So
this
is
rendering
the
widgets
and
a
static
page
I
got
the
output
widget
working
in
the
classic
notebook
and
tracked
down
some
bugs
in
the
classic
notebooks
that
were
from
that
that
we're
exposed
by
it.
We
also
were
working
just
on
a
overhauling
some
widgets
and
getting
ready
for
a
six-point
o
release
on
fixing
bugs
that
were
cropping
up,
and
we
were
looking
at
lots
of
more
complicated
examples
involving
widgets.
It's.
B
D
D
Of
the
things
that
I
wanted
to
get
in
so
they're
slated
for
5x
a
five-point,
oh
right
now
it
I
don't
think
I've
seen
too
many
effects
of
these
bugs
it
was
just
when
we
had
a
complicated
which
an
example.
We
realized
that
there
was
a
problem
with
the
way
we
were
dealing
with:
async
async,
related
messages
and
stuff.
B
D
It's
pretty
complicated
example:
it
was
it's
funny
how
you
can
get
a
complicated
example.
You
realize
wait,
that's
really
odd.
It's
just
some
little
minor
thing
that
doesn't
look
quite
right
and
then
you
trace
it
back
to
a
fundamental
bug
in
the
lower
levels
of
the
notebook.
Oh
we've
had
this
bug
all
along.
You
know
how
that
works.
Okay,.
D
So
I
mean
there's
no
there's
no
extra
bugs
in
4.3,
but
by
point
oh
five
point:
it
will
fix
some
of
that
and
I
would
just
I
just
add
for
whoever's
interested
typescript
2.1
was
released,
which
brings
a
lot
of
sort
of
game-changing
stuff
to
the
table,
a
sink,
a
weight
works
for
es5,
which
is
which
is
fantastic
and
some
of
the
other
there's
some
other
cool
typing
stuff
that
came
with
it,
so
we'll
probably
migrate
to
typescript
2.1
and
fairly
soon.
That's.
A
G
A
It's
been
a
quiet
week,
press
we're
just
responding
to
questions
and
issues
on
the
new
07
release.
We
are
working
on
updating
the
ansible
scripts
for
the
teaching
deployment
and
brians,
giving
us
some
input
on
that
as
well,
and
Jupiter
de
Paris
went
well
and
there
is
actually
a
new
mailing
list
for
this.
That
didn't
see
the
email
Jupiter
in
hpc
and
that's
it
for
this
week,
a
quick.
C
C
A
B
A
F
I
was
a
you
were
the
experience.
Ya
know
it
was
pretty
good,
more
about
I,
think
like
75
people,
and
we
did
a
bunch
of
demos
of
Jupiter
lab
I
pie,
widgets
mb
dime.
There
was
a
sage
math
cloud
talk.
There
was
a
talk
on
Jupiter
hub
and
because
most
of
the
people
there
were
either
affiliated
with
the
University
of
Paris,
south
or
or
academics
who
knew
those
people.
F
It
tended
to
be
the
case
that
I
think
the
things
that
most
caught
their
interest
were
Jupiter
hub
and
how
to
basically
use
Jupiter
for
classes.
So
I
think
it
would
have
been
really
good
if
we
could
have
had
maybe
like
an
MB
greater
talk
or
something
and-
and
it
seems
like
there's
a
lot
of
interest
for
doing
it
next
year
as
well.
But
the
whole
thing
I
think
went
off
pretty
well
is
it
was
a
success?
F
F
If
we
had
some
out
of
out
of
band
method
of
communication
that
didn't
rely
on
simply
filling
in
cell
outputs,
so
I
think
there's
a
lot
of
room
for
giving
people
a
more
formal
way
to
solve
some
problems
that
currently
they're
finding
ingenious
but
sort
of
a
key
ways
around.
But
in
general,
that
talk
was
probably
a
little
over
my
head,
I
think.
Next
time
we
have
men
or
Thomas
on
the
line.
Maybe
or
Sylvan
was
there
too?
You
know
they'll
have
some
more
to
contribute,
but
it
was
it
was.
It
was
pretty
solid.
B
No
thanks
this
is
this
is
wonderful
and
and
yeah
it
would
be.
It
would
be
nice
if
that
person
is
on
the
HP
CM
elements
that
they
post
any
links
to
their
material
materials
or
whatnot
it.
It
sounds
like
an
interesting
news
station.
We
have
a
work,
we're
having
a
lot
of
HTC
usage
here,
both
at
Berkeley
on
campus
and
at
lbl,
and
so,
and
so
we
kind
of
exchange
notes
with
those
people
and
figure
out
what
what
what
they're
doing,
but
thanks
this
is
great
appreciate
it
cool,
yep,
ok,.
G
As
Jason
said
and
be,
convert
was
just
merged
and
now
has
a
better
widget
support.
There's
a
little
bit
of
a
caveat
there,
where
it
only
works.
If
you
have
already
the
available
javascript
rendering
engine
stuff
in
available
to
you,
we
can
embed
it
manually
but
I
needed
to.
We
need
to
hash
that
out
and
that's
not
an
appropriate
topic
for
it.
Here.
G
I've
got
some
further
progress
and
header
IDs
now
using
a
github
project
to
organize
that
effort,
as
I
talked
about
last
week
and
the
docs
are
broken,
they've
been
broken
for
a
month
and
Carol
and
I
have
taken
a
long
look
at
it
and
haven't
figured
out.
Why
and
we're
going
to
look
at
it
together.
More.
A
And
right
now
it's
linking
to
the
stable
doc.
So
folks,
don't
necessarily
think
it's
broken
and
it
seems
to
be
I've
tried
a
whole
bunch
of
combinations
this
weekend,
Mike
and
I'm,
getting
the
sense
that
it's
a
redox
build
tool
issue
as
opposed
to
our
configuration,
but
I
need
to
confirm
that
by
running
a
few
more
tests,
so
okay.
G
A
G
A
And
it's
it
I
think
it's
the
way,
its
handling
a
set
up
high
for
a
dev
release
and
that's
why
it's
dropping
it
back
down
to
the
stable
versus
our
dev
release,
but
yeah
so
more
to
be
done
so
in
the
help
menu
of
the
traffic
notebook.
There's
a
link
to
additional
documentation
on
the
notebook
react
through
to
I
think
it
likes
to
any
viewer.
Actually,
it's
a
mess,
that's
broken.
I
was
just
kind
of
poking.
Around
I
was
trying
to
do
my
going
round
to
do
a
tour
for
the
demo
tonight.
A
So
when
you
open
the
classic
notebook,
can
you
go
to
the
help
menu?
One
of
the
first
voices
in
that
menu
and,
like
you
know,
additional,
oh
and
I
got
a
503
error
on
that
and
Phi
all
day
issue
and
then
BB,
where
we
should
make
sure
that
and
we'll
look
at
it
later,
but
no
papel,
Roberto
yeah.
If
it's
503
it
vehicles
have
not
been
pressing.
Ok,
yeah!
I
love
my
pocket
night.
Yes,.
B
A
B
It's
sort
of
it's
beginning
to
feel
really
like
something
that
I
mean
I,
beginning
to
tell
people
I
get
a
long
talk
yesterday
here
with
some
kind
of
geophysics
colleagues
and
I,
basically
put
them
guys
start
using
this
start
telling
us
what
works
and
what
doesn't
I'm
not
being
shy
anymore
about
it,
because
I
am
using
it
quite
extensively
and
so
I
I'd
like
to
begin
prodding
you
guys
as
to
when
do
you
feel
comfortable
kind
of
calling
it
a
beta
and
beginning
to
tell
people
to
hop
on
it?
I
mean
we
label
it.
B
H
B
B
It's
I
mean
it's
really
good
work
and
and
I.
Don't
think
that
this
point
would
be
throwing
we'd
be,
throwing
you
users
into
any
particularly
uncomfortable
place
as
long
as
we're
kind
of
up
front
about
any
any
known.
The
other
thing
is
to
have
a
document.
I
think
that
this
is
one
thing
that
we
do
need
to
begin
doing
now,
that
shouldn't
be
done
to
the
night
before
it's
to
have
a
document
where
we
fly
really
things
that
we
know
are
still
limitations
and
things
that
we
know
may
be
important.
B
Your
changes
are
both
for
users
to
know
so
they
can
adapt
and
also
to
give
us
feedback
on
whether
that
behavior
change
is
really
too
much
to
deal
with
and
and
and
maybe
maybe
it's
something
that
we
need
to
reconsider
and
an
adjacent
I
know.
We
have
talked
about
opening
kind
of
an
issue
with
weight
with
with
that
kind
of
structure,
for
people
to
report
to
I,
don't
know
if
it
hasn't
been
opened
or
not,
but
but
I
think
that's
one
thing
that
you
should
do.
D
F
Steve
meet
at
the
guy
remote
we're
Gary
I'm,
not
too
sure
about
the
API
changes,
but
actually
I
probably
just
brings
up
a
good
boy
itself
and
that
I
think
before
we
call
it
a
beta.
We
should
take
make
sure
we
resolve
the
pain
of
each
upgrade,
because
until
we
switch
to
the
the
sub
packages
that
were
moving
toward
each
upgrade
has
the
potential
or
no
not.
F
F
Robotspeak
said
it
makes
it:
okay,
I
believe
Jason
just
said:
I
think
that
speaks
to
the
API
compatibility
that
Steve
alluded
to.
And
yes,
if
that's
the
case,
that
is
correct.
We
then
that
is
I,
think
the
biggest
pre-beta
issue
that
should
be
resolved
because
everything
else
is
features,
but
that's
actually
that
will
affect
usability
and
that
will
frustrate
people.
So
if
we
can
resolve
about
vegan,
I
literally
just
put
words
in
Jason's
enough,
so
I
don't
know
if
they're,
accurate,
but
I
hope
they
were.
B
D
B
D
B
That
boundary
is
fluid
so
rather
than
trying
to
say
users
or
developers,
I
think
this
is
this
is
why
I
think
what
needs
to
come
out
is
a
document
explaining.
This
is
a
beta
with
the
following
caveats.
Right
and
those
caveats
are
very
clearly
explained.
So
people
know
what
they're
getting
themselves
into
and
they
can
they
can
choose.
They
can
choose
that.
We're
not
expecting
these
to
be
packaged
in
a
condom
when
it
comes
out
kind
of
for
people
to
just
update
and
all
of
a
sudden,
that's
the
incident.
They
see
it's
nothing
like
that.
C
One
proposal,
if
you
enter
beta
and
since
last
week,
credit
super
crown,
so
we
could
have
a
repository
that
just
installed
everything,
including
freaking,
written
by
users
and
run
a
weekly
bill
to
see
if
the
development
Fedora
is
breaking
other
tickets.
Oh
that's
sounds
great
and
we
could
do
that
for
basically
everything
not
seven
for
the
ipython
because
it
ran
with
liquid
latest.
C
B
Hello
yeah
so
they're
in
maybe
maybe
you
guys
could
open
an
issue
on
this
API
question
just
to
have
it.
Have
it
right
there
and
that's
way
you
can
track
and
I
think.
As
long
as
we
document
those
facts,
it's
fine
and
then
users
can
decide
what
which
user
or
developer
hat
they
wear
when
they
play
with
it,
but
they
can
still
play
with
it.
B
F
Like
this
is
this
is
the
major,
a
major
thing
that
it
Steve's
been
working
on.
So
I
think,
there's
there's
there's
an
issue
working.
Yes,
sir
I
did
okay
yeah,
but
yeah
I
mean
that
this
wasn't
III
didn't
mean
to
sort
of
push
back
against
the
notion
of
going
to
beta
beta.
I
just
wanted
to
point
out
what
I
think
is
the
biggest
remaining
outstanding
issue.
Otherwise
it's
actually
really
good
to
hear
that
that
you're,
finding
its
stable
and
you're
finding
it
a
good
enough
experience
that
we
r
editor,
that's
really
positive.
So
thanks
no.
B
No,
no
in
your
comments
are
exactly
what
the
kind
of
conversation
right
that
that
we
need
to
have
and
obviously
I
may
have
missed
something.
It's
not
like,
I'm
using
every
dark
corner,
but
I'm
just
saying
that
in
real
world
non-trivial
usage,
it's
feeling
great
job
guys.
Thank
you.
That's
that's
all.
I
want
to
say
cool.
A
H
I
was
just
going
to
stay
with
with
respect
to
timing,
as
we
approach
the
end
of
the
year,
we
have
my
team
be
out
the
last
two
weeks
of
december.
I
believe
I'm
assuming
I
still
have
that
correctly
and
my
guys
haven't
changed
your
minds,
but
this
would
basically
be
our
last
week
of
the
year
before
we
all
head
off
for
holidays.
Okay,
thanks
for
letting
us.
B
B
I
I
So
if
you
were
to
read
the
docs,
you
see
all
the
widgets
working
and
live
in
line
now
I'm
working
on
getting
them
to
work
with,
like
a
cube,
Bratton
refugees
and
thanks
to
the
hard
work
of
Mike,
we
got,
needs
code
complete
for
and
be
converted
in
the
ewer
and
I'm,
just
hoping
that
name
or
Tomas
or
anyone
who
is
more.
You
know
involved
in
this
project,
makes
a
man
early
so
that
we
have
widget
CinemaCon
road.
Finally,
Oh.
A
B
Holidays
have
a
great
break
great
work,
everyone
and
we
can
touch
bases
next
week.
If
there's
anyone
around
10
for
last
and
last
minute,
things
have
a
brief
one,
but
if
not
no
worries
I
mean
I,
know,
that's
you,
so
how
these
are
beginning
to
kick
into
gear.
So
I
hope
everybody
has
a
really
a
break
honey.