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

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

Re: upstream python concerns, python3-full package for bullseye

Show key headers only | View raw

Hi Elana (2021.02.11_18:12:34_+0000)
> - Stefano: Update python-policy to describe "python3-full".

I have prepared a policy MR for this:
https://salsa.debian.org/cpython-team/python3-defaults/-/merge_requests/8
It catches up on the current split situation, too.

diff --git a/debian/python-policy.dbk b/debian/python-policy.dbk
index 875b281..8b67f4a 100644
--- a/debian/python-policy.dbk
+++ b/debian/python-policy.dbk
@@ -233,17 +233,28 @@
 	  some exceptions.
 	</para>
 	<para>
-	  Excluded are modules that cannot be included for licensing reasons
-	  (for example the <literal>profile</literal> module), for dependency tracking
-	  purposes (for example the GPL-licensed <literal>gdbm</literal> module), or
-	  that should not be included for packaging reasons (for example
-	  the <literal>tk</literal> module which depends on Xorg).
+	  Excluded are modules that cannot be included for licensing reasons,
+	  for dependency tracking purposes (for example the GPL-licensed
+	  <literal>gdbm</literal> module), or that should not be included
+	  for packaging reasons (for example the <literal>tk</literal>
+	  module which depends on Xorg and the <literal>venv</literal>
+	  module which depends on wheels to bootstrap pip).
+	  Modules that would interfere with system package management (for example
+	  <literal>ensurepip</literal>, when used outside virtual environments) are
+	  modified to print a message explaining the problem and recommending
+	  alternatives.
 	</para>
 	<para>
 	  Some tools and files for the <emphasis>development</emphasis> of Python
 	  modules are split off in a separate binary package
 	  <literal>python<replaceable>X</replaceable>.<replaceable>Y</replaceable>-dev</literal>.
 	</para>
+	<para>
+	  Modules only used for <emphasis>building</emphasis> of Python modules
+	  (e.g. <literal>distutils</literal> and <literal>lib2to3</literal>) are
+	  split into separate packages.
+	  The <literal>python3-venv</literal> binary package depends on these.
+	</para>
 	<para>
 	  Documentation will be provided separately as well.
 	</para>
@@ -255,6 +266,15 @@
 	  the <literal>python3.<replaceable>Y</replaceable></literal> package that installs
 	  the executable.
 	</para>
+	<para>
+	  A <literal>python3-full</literal> binary package must ensure that the
+	  entire Python standard library is available, including all modules
+	  split into separate packages (but excluding modules excluded from
+	  Debian for licensing reasons).
+	  This package exists for the convenience of python developers, and
+	  must not be used in dependencies by python module or application
+	  packages.
+	</para>
 	<para>
 	  The version of the <literal>python3</literal> package must be
 	  greater than or equal to 3.<replaceable>Y</replaceable> and lower than

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

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

Thread

upstream python concerns, python3-full package for bullseye Elana Hashman <ehashman@debian.org> - 2021-02-11 19:20 +0100
  Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-11 19:30 +0100
    Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-16 05:30 +0100
      Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-16 17:30 +0100
  Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-12 01:20 +0100
    Re: upstream python concerns, python3-full package for bullseye stefanor@debian.org - 2021-02-12 01:50 +0100
      Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-12 09:20 +0100
        Re: upstream python concerns, python3-full package for bullseye Raphael Hertzog <hertzog@debian.org> - 2021-02-12 09:40 +0100
          Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-12 10:20 +0100
            Re: upstream python concerns, python3-full package for bullseye Martin <debacle@debian.org> - 2021-02-12 11:30 +0100
            Re: upstream python concerns, python3-full package for bullseye Christian Kastner <ckk@debian.org> - 2021-02-12 13:20 +0100
            Re: upstream python concerns, python3-full package for bullseye Julien Palard <julien@palard.fr> - 2021-02-12 14:10 +0100
              Re: upstream python concerns, python3-full package for bullseye Matthias Klose <doko@debian.org> - 2021-02-12 17:40 +0100
              Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-13 23:10 +0100
            Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-12 21:20 +0100
        Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-12 21:00 +0100
          Re: upstream python concerns, python3-full package for bullseye Michael Kesper <mkesper@schokokeks.org> - 2021-02-12 21:50 +0100
      Re: upstream python concerns, python3-full package for bullseye Tristan Seligmann <mithrandi@mithrandi.net> - 2021-02-12 10:30 +0100
        Re: upstream python concerns, python3-full package for bullseye Valentin Vidic <vvidic@debian.org> - 2021-02-12 10:50 +0100
          Re: upstream python concerns, python3-full package for bullseye Jonathan Carter <jcc@debian.org> - 2021-02-12 11:40 +0100
            Re: upstream python concerns, python3-full package for bullseye Valentin Vidic <vvidic@debian.org> - 2021-02-12 12:10 +0100
          Re: upstream python concerns, python3-full package for bullseye Simon McVittie <smcv@debian.org> - 2021-02-12 15:20 +0100
            Re: upstream python concerns, python3-full package for bullseye Andrius Merkys <merkys@debian.org> - 2021-02-12 17:00 +0100
              Re: upstream python concerns, python3-full package for bullseye Valentin Vidic <vvidic@debian.org> - 2021-02-12 17:20 +0100
    Re: upstream python concerns, python3-full package for bullseye Michael Kesper <mkesper@schokokeks.org> - 2021-02-12 11:00 +0100
    Re: upstream python concerns, python3-full package for bullseye Jeremy Stanley <fungi@yuggoth.org> - 2021-02-12 18:00 +0100
    Re: upstream python concerns, python3-full package for bullseye Bastian Venthur <venthur@debian.org> - 2021-02-16 10:20 +0100
      Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-16 19:30 +0100
        Re: upstream python concerns, python3-full package for bullseye Jeremy Stanley <fungi@yuggoth.org> - 2021-02-16 20:20 +0100
      Python package situation Martin <debacle@debian.org> - 2021-02-16 21:50 +0100
        Re: Python package situation Andrey Rahmatullin <wrar@debian.org> - 2021-02-16 22:20 +0100
          Re: Python package situation Martin <debacle@debian.org> - 2021-02-16 23:20 +0100
          Re: Python package situation Brian May <bam@debian.org> - 2021-02-17 02:10 +0100
            Re: Python package situation Andrey Rahmatullin <wrar@debian.org> - 2021-02-17 08:00 +0100
            Re: Python package situation Raphael Hertzog <hertzog@debian.org> - 2021-02-17 10:30 +0100

csiph-web