Re: Bug#937657: Issue with numpy under Python 3.8

2019-11-17 Thread Sandro Tosi
On Sun, Nov 17, 2019 at 10:58 AM Andrey Rahmatullin wrote: > > On Sun, Nov 17, 2019 at 04:29:56PM +0100, Andreas Tille wrote: > > > If you look on the numpy tracker page [1], you'll see there is a note: > > > > > > "This package is part of the ongoing testing transition known as > > > python3.8. P

Re: Bug#937657: Issue with numpy under Python 3.8

2019-11-17 Thread Andrey Rahmatullin
On Sun, Nov 17, 2019 at 04:29:56PM +0100, Andreas Tille wrote: > > If you look on the numpy tracker page [1], you'll see there is a note: > > > > "This package is part of the ongoing testing transition known as > > python3.8. Please avoid uploads unrelated to this transition, they > > would likely

Re: Bug#937657: Issue with numpy under Python 3.8

2019-11-17 Thread Andreas Tille
Hi Graham, On Sun, Nov 17, 2019 at 02:16:29PM +0200, Graham Inggs wrote: > If you look on the numpy tracker page [1], you'll see there is a note: > > "This package is part of the ongoing testing transition known as > python3.8. Please avoid uploads unrelated to this transition, they > would likel

Re: Bug#937657: Issue with numpy under Python 3.8

2019-11-17 Thread Graham Inggs
Hi Andreas On Sat, 16 Nov 2019 at 16:09, Andreas Tille wrote: > Its not about testing. Its the usual build time test. If I'd do a > source upload of this package it will FTBFS under the current state > of the archive. If you look on the numpy tracker page [1], you'll see there is a note: "Thi

Re: Bug#937657: Issue with numpy under Python 3.8

2019-11-16 Thread Andreas Tille
Hi Rebecca, On Sat, Nov 16, 2019 at 09:16:17AM +, Rebecca N. Palmer wrote: > I think that just means "numpy hasn't yet been rebuilt for Python 3.8". (In > Python modules that include a C extension, the .py files are shared but the > C part is compiled separately for each Python version.) > >