►
From YouTube: SunPy Developer Discussion
Description
Topics:
PRs
0.6 sprint
C
B
You
really
need
to
look
at
something
else:
cuz,
it
is
scaring
quiet.
Second,
there
are
31
open
pr's
like
an
orphanage
15,
a
martyr's
review.
Most
of
those
are
passing
Travis.
Oh
till
Travis
fell
on
its
sword
in
a
very
graceful
manner.
Over
Christmas.
A
C
A
C
A
C
D
C
B
A
C
C
C
C
C
G
Is
very
very
closely
hey
somewhere
somewhere
yeah
yeah.
H
C
B
B
H
C
F
H
C
H
Just
that
there
is
some
money
array,
sparse
one
side
to
another
and
and
so
many
units
that
they
have
need
to
be
properly
set,
because
you
have
the
frequency
on
the
side.
You
have
the
data
units
of
the
measure
by
the
instrument
and
how
their
I
mean
all
this
magic
from
Florian
how
they
get
parts
to
one
side.
Another
is
kind
of
an
interesting.
C
We
add
a
priority
tags
to
these,
just
so
that
yes,
please
yeah,
so
that
you
know
I
think
a
priority
tag
would
be
good
anyway,
but
for
this
so
that
we
know
which
ones
to
attack
first
and
that
way
you
know
the
high
party
ones
hopefully
get
finished
and
then
other
ones
if
they
don't
get
to
it.
It's
okay.
B
C
B
B
B
C
C
E
B
B
F
B
H
B
A
How
would
you
prioritize,
how
would
you
implement
a
prioritization
check.
C
C
B
C
B
C
This
is
something
I've
been
doing
myself,
and
maybe
we
should
consider
having
it
more
general,
which
is
like
we
can
have
tests
that
ship
with
some
pie,
which
tell
you
whether
some
pie
works,
but
then
we
can
have
some
more
extensive
tests
that
we
don't
ship
with
some
pie.
This
is
something
we
do
ourselves.
B
A
C
Okay,
sure
sure,
okay,
so
that
means
really
would
want
I
mean.
B
C
C
B
C
C
A
B
A
C
Especially
for
binary
files,
you
could
just
make
sure
that
it
goes
up
it.
Like
knows,
you
know,
checks
the
my
plot
live
version
that
you
have,
and
then
it
goes
off
and
downloads
the
proper
files,
because
every
we
would
have
to
recreate
the
files.
You
know
it
would
be
a
one-time
event.
You
recreate
all
the
files,
presumably
put
them
in
a
new
directory,
and
then
you
still
have
the
old
ones.
It
would
be
a
of
a
set
event
when
that
would
happen.
B
Mm-Hmm
well,
I
mean
I.
Suppose
the
bed
did
actually
the
best
solution
is
get
annex,
but
that
brings
a
long,
a
whole
novel
level
of
pain
because
people
have
to
have
get
up,
get
annex
you
stall
to
use
it,
and
then
we
have
to
have
somewhere
to
host
the
date.
I
don't
know
it's
not
it's
not
a
problem
with
an
easy
solution
that
anything.
C
B
E
C
C
So
I
would
think
that
a
besides
looking
at
the
percentage,
I
think
it
would
be
good
for
us
to
just
look
through
all
the
tests
and
add
the
things
we
need
think
we
need-
or
at
least
stubs
for
things,
that
we
need
and
then
and
not
worry
about
this
percentage
coverage
thing
so
much.
C
B
C
A
C
But
then
don't
necessarily
overlap
right.
You
may
you
may
write
a
test
when
you
know
that
there's
another
test
that
needs
to
be
done,
even
though
it
covers
the
other
test,
is
important
and
covers
the
code.
It's
already
covered
technically,
but
they'll
decide
to
write
the
test
for
something
that's
uncovered
and
ignore
the
other
thing
that
needs
to
be
done
as
well.
A
B
Sure
there
are
bits
that
are
missing
still,
but
in
some
respects
having
some
test
coverage,
at
least
if
we
get
to
the
point
where
we're
executing
every
line
of
code
they're
going
to
reduce
our
bugs
by
a
like
reduced,
where
the
box
behind
by
an
amount.
Obviously
you
can
still
have
light.
You
can
still
not
test
edge
cases
and
execute
every
line
of
code,
but
we're
not
even
a
queer,
not
even
importing
all
of
the
different
modules
when
we
run
our
tests.
B
Cesses
test
cases,
women
while
I'm-
definitely
not
disagreeing
with
Steve
I-
think
it's
more
important
to
actually
do
something
for
Allah
a
percentage
of
some
part
than
it
is
to
get
oh
yeah.
Obviously,
both
are
important.
The
late
I
don't
think
that
there,
by
when
we
hit
like
ninety
percent
test
companies,
and
yet
we
can
start
making
issues
that
go
through
and
go.
You
know
this
needs
more
tests
missing
stuff,
yeah.
A
C
That's
a
hard
question
answer:
I'd
have
to
look
through
I.
Just
remember,
I
mean
if
you
look
at
a
lot
of
our
test.
Suites
they're
fairly,
sparse
and
you
know
a
lot
of
them,
for
example,
don't
even
really
test
all
the
input
input
possibilities,
for
example
crew
yeah,
so
it
it
looks
like
you
know
it's
well
tested,
but
in
reality
you
know
it
has
some
holes,
so
I
just
thought
I'd
bring
that
up,
but
I
think
it.
We
can
follow
this
and
and
I
mean
you're
talking
about
test
quality
right
I
mean
yeah
yeah.
A
C
B
B
Need
prophase
testing,
it
is
one
of
our
most
beautiful
eating.
Bits
of
API
is
are
playing
API
and
the
fact
that
it
breaks
racially
bike
goes
peak
goes
peak,
is
broken
or
not.
Point
5,
I'm
a
public
one
point
for
its
map.
What
they've
changed?
Some
things
you
broke,
we
didn't
know
about
it
until
I
got
a
message
of
Larry
Manning
on
hangouts,
a
few
easy
for
going
here,
broken
and
like.
B
B
F
A
C
C
C
B
C
B
C
C
B
C
But
I
mean
/
for
most
people
they
most
people
would
not
be
running
this.
Let's
I
would
say
what
we
need
to
do
is
come
up
with
a
solution
that
we
can
run
it's
not
as
a
part
of
the
perfect
solution,
but
it's
something
that
you
know
we
have
available
to
us
and
then
we
can
consider
how
we
would
make
it
possible
for
anyone
and
to
check
and
run,
but.
B
B
A
B
C
B
B
B
If
something
breaks-
and
it
comes
up
with
an
arrow-
we
know
that
they
come
up
with
an
error
when
you
try
and
plot
it
yeah
well,
they'll
get
there
is
a
phenomenal
improvement
or
where
we
are
the
moment.
Even
if
we're
not
testing
the
output
from
the
damn
thing,
yeah
in
fact,
actually
I
opened
an
issue
to
facilitate
that
change.
Yeah
in
fact,
I
over
the
pull
request
to
facilitate
that
train
key
of
the
day
where's
he
gone
1232.