[Python-modules-team] Bug#942235: Adding Python 3.8 as a supported Python3 version

[Matthias Klose]

On 18.11.19 07:52, Alastair McKinstry wrote:
> So I've uploaded a python-xarray 0.14.0-2 which passes on python3.7.
> 
> Its failing on python 3.8 but apparently due to pandas not ready on 3.8, so it
> should be ok to pass as the transition completes.
> 
> xarray really needs dask >= 2.0 but version 1 is in unstable; I've disabled some
> functionality (dask='parallelize') and marked some tests xfail until this is done.
> 
> Alastair

yes, people are aware of a needed dask update, see #942235. There's now also a
dask 2.8 release available, I didn't look at that yet.

> On 07/11/2019 14:08, Matthias Klose wrote:
>> This weekend, I am planning to upload python3-defaults, adding python3.8 as a
>> supported Python3 version.  This may introduce some churn in unstable until
>> the basic binNMUs are available as well.
>>
>>
>>  - python-xarray #944044. 1.4 is already broken with Python 3.7. For
>>    Ubuntu I fell back to 1.2.1. 1.2.3 might work as well, still seeing
>>    one or two test failures.
>>
>> Packages building on top of numpy/scipy/pandas, like the PyAstro stack,
>> continue to work with these updates, despite some new test failures.
>>
>> Matthias
>>
>> [1] https://wiki.debian.org/Python/Python3.8.
>> [2]
>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.8;users=debian-python@lists.debian.org
>>
>>