python3-openvdb: build against the default python3 version

2020-03-27 Thread Mathieu Malaterre
Hi all, Could anyone point me at a Debian package (possibly using dh) where multiple compilation are done (one against python3.7 and one against python3.8). I'd like to avoid re-inventing the wheel for building a cmake package (c++) which ships a single python module (so I need to do one configure

Re: python3-openvdb: build against the default python3 version

2020-03-27 Thread Scott Kitterman
Pybuild has a cmake plugin that I think is relatively new. It may handle the complexity for you, but I've never tried it. We used to do this with pykde4, which is available on snapshot..d.o. Scott K On Friday, March 27, 2020 8:48:33 AM EDT Mathieu Malaterre wrote: > Hi all, > > Could anyone

Python3.8 as default final status

2020-03-27 Thread Scott Kitterman
The python3-defaults with python3.8 as the default python3 has migrated to Testing thanks to the release team hammering things around until it went. Most of the outstanding autipkgtest failures with python3.8 were fixed either in unstable or in git/BTS. Here are the remaining issues that someon

Re: Python3.8 as default final status

2020-03-27 Thread Sergio Durigan Junior
On Friday, March 27 2020, Scott Kitterman wrote: > The python3-defaults with python3.8 as the default python3 has migrated to > Testing thanks to the release team hammering things around until it went. Thanks for this. > Most of the outstanding autipkgtest failures with python3.8 were fixed eit

Re: Python3.8 as default final status

2020-03-27 Thread Håvard Flaget Aasen
On 27.03.2020 20:09, Sergio Durigan Junior wrote: > On Friday, March 27 2020, Scott Kitterman wrote: > >> The python3-defaults with python3.8 as the default python3 has migrated to >> Testing thanks to the release team hammering things around until it went. > > Thanks for this. > >> Most of

Re: Python3.8 as default final status

2020-03-27 Thread Scott Kitterman
On Friday, March 27, 2020 3:21:38 PM EDT Håvard Flaget Aasen wrote: > On 27.03.2020 20:09, Sergio Durigan Junior wrote: > > On Friday, March 27 2020, Scott Kitterman wrote: > >> The python3-defaults with python3.8 as the default python3 has migrated > >> to > >> Testing thanks to the release team h

Re: Python3.8 as default final status

2020-03-27 Thread Simon McVittie
On Fri, 27 Mar 2020 at 11:12:35 -0400, Scott Kitterman wrote: > meson/0.52.1-1: #952610 This is fixed in experimental. The version in experimental is an unrelated new upstream release candidate, but the relevant packaging change seems readily backportable. smcv

Re: Python3.8 as default final status

2020-03-27 Thread Scott Kitterman
On Friday, March 27, 2020 3:39:30 PM EDT Scott Kitterman wrote: > On Friday, March 27, 2020 3:21:38 PM EDT Håvard Flaget Aasen wrote: > > On 27.03.2020 20:09, Sergio Durigan Junior wrote: > > > On Friday, March 27 2020, Scott Kitterman wrote: > > >> The python3-defaults with python3.8 as the defaul

Re: Python3.8 as default final status

2020-03-27 Thread Håvard Flaget Aasen
On 27.03.2020 20:44, Scott Kitterman wrote: > On Friday, March 27, 2020 3:39:30 PM EDT Scott Kitterman wrote: >> On Friday, March 27, 2020 3:21:38 PM EDT Håvard Flaget Aasen wrote: >>> On 27.03.2020 20:09, Sergio Durigan Junior wrote: On Friday, March 27 2020, Scott Kitterman wrote: > T

Re: Python3.8 as default final status

2020-03-27 Thread Sergio Durigan Junior
On Friday, March 27 2020, Håvard Flaget Aasen wrote: > On 27.03.2020 20:09, Sergio Durigan Junior wrote: >> On Friday, March 27 2020, Scott Kitterman wrote: >> >>> The python3-defaults with python3.8 as the default python3 has migrated to >>> Testing thanks to the release team hammering things a

Re: Python3.8 as default final status

2020-03-27 Thread Scott Kitterman
On March 28, 2020 5:10:42 AM UTC, Sergio Durigan Junior wrote: >On Friday, March 27 2020, Håvard Flaget Aasen wrote: > >> On 27.03.2020 20:09, Sergio Durigan Junior wrote: >>> On Friday, March 27 2020, Scott Kitterman wrote: >>> The python3-defaults with python3.8 as the default python3