[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: packaging problems with python3.5 and python 3.6



On Aug 2, 2017, at 15:34, Steve Langasek <vorlon@debian.org> 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 or all Python 2 versions."
> 
>  https://www.debian.org/doc/packaging-manuals/python-policy/ap-build_dependencies.html
> 
> But this is then shadowed by the less precise/complete recommendation in the
> wiki.

Note that the LSG does link to the policy page and even says:

"It is not intended to supplant the Debian Python Policy and in fact, if you have not read that document, stop now and go read it.”

and goes on:

"Instead, this page captures in example form, best practices for simple Python libraries that you might find on the Python Package Index.”

Maybe packages containing extensions are simple enough to include on this page.  It’s a wiki so, 1) it’s a living document; 2) contributions welcome! :)

-Barry

Attachment: signature.asc
Description: Message signed with OpenPGP


Reply to: