Re: MBF for deprecating Python2 usage

2017-08-03 Thread Piotr Ożarowski
[Scott Kitterman, 2017-08-04] > Read it. I remain completely convinced that /usr/bin/python pointing > at a python3 version is utterly wrong and a disservice to our users. > Even after we remove python2.7, people will be locally compiling it > and using it for a decade. > > Such a change would be

Re: MBF for deprecating Python2 usage

2017-08-03 Thread Scott Kitterman
Dropped d-devel. On August 3, 2017 9:08:10 PM EDT, ba...@debian.org wrote: >On Aug 3, 2017, at 17:57, Matthias Klose wrote: >> >> While at DebCamp, Stefano Rivera and I sat down to analyze what needs >to be done >> to deprecate Python2 usage within the distribution. It might not be >possible to

Re: MBF for deprecating Python2 usage

2017-08-03 Thread barry
On Aug 3, 2017, at 17:57, Matthias Klose wrote: > > While at DebCamp, Stefano Rivera and I sat down to analyze what needs to be > done > to deprecate Python2 usage within the distribution. It might not be possible > to > drop Python2 for the next release, but there are still too many issues wi

MBF for deprecating Python2 usage

2017-08-03 Thread Matthias Klose
While at DebCamp, Stefano Rivera and I sat down to analyze what needs to be done to deprecate Python2 usage within the distribution. It might not be possible to drop Python2 for the next release, but there are still too many issues with packages. For now we identified some categories which need f

RE:building manpages via setup.py

2017-08-03 Thread PICCA Frederic-Emmanuel
Ok, If I replace '{interpreter} setup.py build_man' by 'env; setup.py build_man' I get this HOME=/home/picca PYTHONPATH=/home/picca/Debian/silx/silx/.pybuild/pythonX.Y_2.7/build but If I read the code of def create_pydistutils_cfg(func): """distutils doesn't have sane command-line API

RE:building manpages via setup.py

2017-08-03 Thread PICCA Frederic-Emmanuel
So I am sltill investigating with some debug output, I can see this the first build part gives dh_auto_build -- --after-build '{interpreter} setup.py build_man' pybuild --build -i python{version} -p 2.7 --after-build "{interpreter} setup.py build_man" D: pybuild pybuild:474: version: 2.2

Re: packaging problems with python3.5 and python 3.6

2017-08-03 Thread barry
On Aug 2, 2017, at 15:34, Steve Langasek wrote: > > Except the python packaging policy already mentions build dependencies: > > "The python3-all-dev should be used when building extensions for any or all > Python 3 versions. The python-all-dev should be used when building > extensions for any o

RE:building manpages via setup.py

2017-08-03 Thread PICCA Frederic-Emmanuel
Hello Piotr, I am struggling, with the build system. I will speak about this solution > | override_dh_auto_build: > | dh_auto_build -- --after-build '{interpreter} setup.py build_man' the code instrumented of the BuildMan is this one class BuildMan(Command): """Command to build man p