►
From YouTube: Jupyter/IPython Dev Meeting, October 11, 2016
Description
Meeting of the Jupyter/IPython development team, October 11, 2016
Meeting Notes: https://jupyter.hackpad.com/October-2016-PiBXzGlzu8l
A
Great
good
morning,
everyone,
today's
a
tuesday
october
eleventh.
This
is
the
Jupiter
dev
meeting
and
I
just
have
a
couple
brief
announcements
today,
actually
just
one
we're
ramping
up
for
the
fall
dev
meeting,
otherwise
known
as
the
fall
project.
Meeting
Thank
You
Thomas
for
disambiguating.
That
and
you'll
be
seeing
some
messages
from
us.
Looking
for
just
feed
back
on
road
map,
stuff
team
team
questions
that
type
of
thing
also
we're
working
on
the
Jupiter
annual
report,
so
I've
dropped
a
link
in
the
hack
pad.
B
That's
my
main
thing
and
then
I've
also
been
running
around
various
projects
of
protocols
and
formats,
and
things
covering
some
some
updates
to
author
metadata
and
adding
a
the
ability
for
display
data
messages
to
update,
be
updated
in
place,
and
some
pics
is
needed
to
the
notebook
format
for
proper
Jason
output.
So
people
who
are
interested
in
those
things
can
up
on
the
issues
I
liked,
but
that's
it
for
me.
Okay,.
C
Hi
everyone
pretty
much
what
min
said
working
on
Doc's
40.7,
Jupiter
hub,
also
doing
a
user
test
of
the
installation,
instructions
for
the
Jupiter
hub
deployment
for
teaching
and
going
to
rework
some
of
those
documents
and
docker
spawner.
We've
done
some
updates
on
docs
that
we're
working
through
and
I
think
that
pretty
much
just
triaging
and
getting
ready
for
Grace
Hopper
next
week.
Thank.
A
C
D
So
I'm
the
disembodied
voice.
This
week
I
was
working.
I
was
working
with
Brian
and
Jason
in
person
last
week
to
get
this
Jupiter
lab
extension
that
adds
navigation
links
to
the
Jupiter
hub,
ready
for
prime
time
and
I
have
a
working
prototype.
I
should
be
able
to
push
that
up
there
tomorrow.
There
are
two
changes,
one
to
the
hub
and
one
to
the
lab
that
have
to
be
made
to
pass
the
configuration
about
what
the
hub,
prefix
and
hub
hosts
are
from
the
hub
configuration
into
the
lab.
D
You
I
and
so
I'd
appreciate
some
general
feedback
on
whether
this
is
a
same
way
to
do.
That,
I
think
it's
going
to
end
up
being
a
two-stage
process,
where
we
have
to
unfortunately,
make
aware
of
Jupiter
hub
and
put
some
specific
fields
in
there
for
now
and
then
once
we're
ready
to
release
a
new
version
of
the
notebook
server
and
require
that
version
we
can.
We
can
do
this
a
different
way
where
we
we
don't
need
to
have
a
hard-coded
hub
information
in
Jupiter
lab.
E
A
E
Let's
see
I
wanted
to
say
a
few
weeks
back,
I
put
on
the
hog
POG
we
released
07
of
the
cloud
of
widgets
and
really
the
most
notable
part
of
that
release
was
that
we
added
this
thing.
This
function
called
Explorer,
which
I
think
folks,
my
5
talked
about
it.
In
the
past.
You
basically
passed
a
data
frame
of
any
type
to
this
Explorer
function
and
puts
out
this
Richie.
E
Why
that
allows
you
to
do
queries
and
visualizations
on
on
a
data
frame,
so
I
want
people
to
go
check
that
out
and
give
us
feedback
it's
our
first
iteration
of
this
of
this
support
and
I
think
it
has
a
lot
of
room
for
improvement,
but
it's
a
good
first
step.
Basically,
a
single
line
of
code
I
generates
a
lot
of
usable
interface
to
querying
and
visualizing
your
data
so
go
check
that
out.
E
Actually,
the
recently
my
focus
has
shifted
a
little
bit
away
from
the
Jupiter
project,
proper
projects
that
we
have
in
Jupiter
2
a
related
project
that
we
have
an
Apache
called
Tory,
which
is
a
kernel
or
for
Jupiter
that
does.
It
basically
allows
you
use
Scala
as
a
language,
and
so
recently
one
of
our
dependencies
zeromq
was
realizing.
E
That's
not
a
development
preview
or
anything
surreal,
incubator
release
ettore
with
with
the
right
licenses
and
so
we're
doing
that
at
the
same
time
we're
trying
to
get
a
spark
to
point
o
version
of
Tori
out
also
as
well,
though,
there's
a
lot
of
activity
now
on
that
project
because
of
the
work
that
happened
in
giro
mq,
that's
pretty
much.
It.
A
E
Put
a
link
in
the
hot
pad
it
basically
there's
two
there
either
on
the
declarative,
widgets
project
or
there's
a
sibling
project
called
acquired
of
widgets
explorer,
which
is
the
widget
the
rich
widget
for
exploration.
They
can
also
get
feedback
there,
but
I'll
put
both
links
on
the
hack
pad.
So
people
know
where
to
go
great.
A
F
Yes,
I'm
working
on
some
inconsistency
up
with
the
focus,
tracker
and
Jupiter
lab
some
of
the
more
esoteric
seeming
bugs
that
we
have
are.
Actually,
I
think,
all
stemming
from
this
were
basically
different
kinds
of
entities
that
you
can
launch
like
consoles,
notebooks
terminals,
whatever
they
all
have
their
own
focused
tracker
that
doesn't
and
they
don't
use
the
system-wide
focus
tracker.
F
So
there
are
cases
where
this
the
application
wide
focus
tracker
knows
that
you're
now
in
this
new
tab,
doing
this
thing,
but
the
say
the
notebook
specific
one
doesn't
actually
know
so
you
might
get
weird
behaviors
when
you
run
commands,
because
it's
referring
to
an
old
notebook
or
something
like
that.
There's
there
some
subtle
bugs.
Basically
that
occasionally
arise-
and
I
think
this
will
get
to
the
bottom
of
that.
F
So
that's
what
I'm
working
on
I
posted
an
issue
and
I
added
the
needs,
discussion
labeled
to
it,
and
it's
in
Jupiter
11,
it's
linked
on
the
hack
pad.
It's
about
how
we
handle
sessions
and
I
think
I
think
we're
heading
toward
a
consensus
on
what
ought
to
be
done.
But
you
know
if
there's
actual
there
might
be
some
finer
points.
I
need
to
be
hashed
out.
F
A
Great
thanks
a
lot,
so
it
looks
like
the
rest
of
the
folks
on
the
hacked
ad.
Don't
have
anything
they
want
to
share
I,
just
pasted
the
back
pad
link
into
the
chat
window.
So
those
of
you
who
arrived
a
little
bit
later
can
easily
access
it.
I
noticed:
let's
see,
Sylvan
I
think
you
arrived
a
little
bit
after
we
started.
Do
you
have
anything
you
want
to
share
with
the
group
today.
G
Actually
yeah
just
heads
up
that
warehouse.
The
merge
finally
happened.
So
now
you
have.
The
data
requires
Python
info
being
held
in
that
database
appropriately,
and
so
now
it's
just
waiting
on
pi
PI
legacy
and
then
we
will
be
able
to
have
a
nice
safe
release.
We're
like
we
can
have
people
upgrade
to
python
if
they
they
have
Python
3
that
make
an
upgrade
and
if
they
don't
have
Python
3
them,
they
don't
are
not
forced
to
and
it
doesn't
break
their
build.