Re: python-mkdocs new dependancy

2016-05-10 Thread Piotr Ożarowski
[Brian May, 2016-05-10] > Brian May writes: > > >> export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/mkdocs/themes/ > > > > Was hoping to avoid the need to add /usr/share/mkdocs/themes to the > > sys.path. > > This results in the following lintian warning: > > E: mkdocs-bootstrap: package-

pypy pakages

2016-05-10 Thread Michael Fladischer
Hi, is there a specific reason why there are so few pypy-* packages in the archive? Is it just a lack of interest or are any practical reasons not to have them? I just tried to add pypy support to some of my packages and it was a pretty straight forward thing to do. If it's just a lack of intere

Re: pypy pakages

2016-05-10 Thread Barry Warsaw
On May 10, 2016, at 07:23 PM, Michael Fladischer wrote: >is there a specific reason why there are so few pypy-* packages in the >archive? Is it just a lack of interest or are any practical reasons not >to have them? I don't think there are too many practical reasons other than every package that

Re: pypy pakages

2016-05-10 Thread Dmitry Shachnev
Hi Michael, On Tue, May 10, 2016 at 07:23:33PM +0200, Michael Fladischer wrote: > is there a specific reason why there are so few pypy-* packages in the > archive? Is it just a lack of interest or are any practical reasons not > to have them? I personally don't support pypy 2.x because: 1) It's

Re: pypy pakages

2016-05-10 Thread Stefano Rivera
Hi Michael (2016.05.10_19:23:33_+0200) > is there a specific reason why there are so few pypy-* packages in the > archive? Is it just a lack of interest or are any practical reasons not > to have them? I think we're all kind of waiting for PyPy 3, so that we don't have to bring up an entire stack

Re: pypy pakages

2016-05-10 Thread Tristan Seligmann
On Tue, 10 May 2016 at 23:29 Stefano Rivera wrote: > Hi Michael (2016.05.10_19:23:33_+0200) > > is there a specific reason why there are so few pypy-* packages in the > > archive? Is it just a lack of interest or are any practical reasons not > > to have them? > > I think we're all kind of waitin

Re: python-mkdocs new dependancy

2016-05-10 Thread Brian May
Piotr Ożarowski writes: > dh_python* is checking usr/share/mkdocs-bootstrap by default (among > other dirs). If you want it to check usr/share/mkdocs as well, you have > to point it to, f.e. like this: > > override_dh_python3: > dh_python3 -N mkdocs-bootstrap > dh_python3 -p mkdocs-bo