[Debian-astro-maintainers] Bug#851437: astroplan: FTBFS (requires Internet to build)
Ole Streicher
olebole at debian.org
Wed Jan 25 13:22:49 UTC 2017
There are quite a couple of problems, some of which are due to bugs in
astropy (namely #852550), and others already solved upstream:
https://github.com/astropy/astroplan/pull/273
https://github.com/astropy/astroplan/pull/274
https://github.com/astropy/astroplan/pull/281
https://github.com/astropy/astroplan/files/726302/diff.txt
The remaining problems are in test_transitioner,
test_priority_scheduler, test_sequential_scheduler:
______________________________ test_transitioner _______________________________
self = <astropy.coordinates.baseframe.TimeFrameAttribute object at 0x7f80365e23c8>
instance = <[ValueError("attribute obstime should be scalar or have shape (2, 1), but is has shape (2,) and could not be broadcast.") raised in repr()] AltAz object at 0x7f8032fb2470>
frame_cls = <class 'astropy.coordinates.builtin_frames.altaz.AltAz'>
def __get__(self, instance, frame_cls=None):
[...]
if instance is not None:
instance_shape = getattr(instance, 'shape', None)
if instance_shape is not None and (getattr(out, 'size', 1) > 1 and
out.shape != instance_shape):
# If the shapes do not match, try broadcasting.
try:
if isinstance(out, ShapedLikeNDArray):
out = out._apply(np_broadcast_to, shape=instance_shape,
> subok=True)
[...]
/usr/lib/python3/dist-packages/numpy/lib/stride_tricks.py:174:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
array = array([ 2457424.5, 2457424.5]), shape = (2, 1), subok = True
readonly = True
def _broadcast_to(array, shape, subok, readonly):
[...]
broadcast = np.nditer(
(array,), flags=['multi_index', 'refs_ok', 'zerosize_ok'] + extras,
> op_flags=[op_flag], itershape=shape, order='C').itviews[0]
E ValueError: operands could not be broadcast together with remapped shapes [original->remapped]: (2,) and requested shape (2,1)
/usr/lib/python3/dist-packages/numpy/lib/stride_tricks.py:129: ValueError
It is unclear (to me) whether this is a problem in astroplan or in astropy.
More information about the Debian-astro-maintainers
mailing list