[Debian-science-sagemath] [sage-devel] Upcoming Debian freeze

[E. Madison Bray]

Getting back on the general topic....

On Mon, Jan 7, 2019 at 3:09 PM Thierry <sage-googlesucks at lma.metelu.net> wrote:
> After a very quick look at the Debian build logs, regarding numpy, some
> errors are due to te fact that 1.16 is not out yet (hence not in sage),
> but Debian uses its release candidate.
>
> Gap 4.10 is merged, networkx 2.2 is on the way (#26326), and we have to
> wait for upstream for numpy 1.16 (stay tuned at #27000). Perhaps could we
> start to make a branch there with 1.16.rc2 so that we can already work on
> the issues and be faster when 1.16 will be out ?

As I commented on #27000, the main problem with Numpy 1.16 seems to
just be deprecation warnings that originate from matplotlib (use of
np.asscalar()).  As far as I can tell there aren't any Numpy
DeprecationWarnings originating from Sage itself.  I could be wrong,
but I don't see any other obvious problems resulting from using Sage
with Numpy 1.16.

The bug is already fixed in matplotlib
(https://github.com/matplotlib/matplotlib/pull/12478) and has been
backported to v2.2.4, so at most all we need is a patch in the
matplotlib package.