Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #9680

Re: packaging problems with python3.5 and python 3.6

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Aug 02, 2017 at 12:10:05PM -0400, barry@debian.org wrote:
> On Jul 30, 2017, at 02:41, Steve Langasek <vorlon@debian.org> wrote:

> >> https://wiki.debian.org/Python/LibraryStyleGuide where it states:
> >> 	You'll want to have at least the following build dependencies:
> >> 	...
> >> 	python3-all
> >> but the
> >> 	python[,3]-all-dev
> >> are never mentioned. So sorry, I didn't know about them and searched
> >> for the required header files, and added the respective packages.

> > Ok, that was the first hit I got but I discounted it because it spoke of
> > packaging "libraries", not modules or extensions.

> “Libraries” is typically the term we’ve used to describe things you import from other things.  In Python, everything you import is a module, and packages are just special kinds of modules, whereas extensions are module implemented in a compiled language instead of native Python.  It may not be the best nomenclature, but it’s what we’ve been using for a long time.

> > Perhaps someone should make this wiki page a redirect to the python policy
> > manual?  https://www.debian.org/doc/packaging-manuals/python-policy/

> No, because LibraryStyleGuide *isn’t* policy, it’s an opinionated
> collection of best practices, and it is better suited for a wiki because
> those best practices do change over time.

> Policy is what you MUST do, and the barrier for changing policy is — and
> needs to be — higher.

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.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

packaging problems with python3.5 and python 3.6 Norbert Preining <norbert@preining.info> - 2017-07-30 02:10 +0200
  Re: packaging problems with python3.5 and python 3.6 Steve Langasek <vorlon@debian.org> - 2017-07-30 07:50 +0200
    Re: packaging problems with python3.5 and python 3.6 Norbert Preining <norbert@preining.info> - 2017-07-30 08:40 +0200
      Re: packaging problems with python3.5 and python 3.6 Steve Langasek <vorlon@debian.org> - 2017-07-30 08:50 +0200
        Re: packaging problems with python3.5 and python 3.6 Norbert Preining <norbert@preining.info> - 2017-07-30 09:20 +0200
        Re: packaging problems with python3.5 and python 3.6 barry@debian.org - 2017-08-02 18:20 +0200
          Re: packaging problems with python3.5 and python 3.6 Steve Langasek <vorlon@debian.org> - 2017-08-02 21:40 +0200
            Re: packaging problems with python3.5 and python 3.6 barry@debian.org - 2017-08-03 15:10 +0200

csiph-web