The current CPython plan is to deprecate distutils in 3.10 and 3.11,
and then remove it in 3.12.
https://www.python.org/dev/peps/pep-0632/
On 2018-03-24 00:03:12 + (+), Simon McVittie wrote:
[...]
> On Fri, 23 Mar 2018 at 20:30:17 +, Jeremy Stanley wrote:
> > This may also serve to help narrow down (via reverse dependency) the
> > list of packages which will trigger violent reactions when mixed in
> > the same context with
On Sat, 24 Mar 2018 at 07:09:23 +0800, Matthias Klose wrote:
> On 24.03.2018 03:35, Simon McVittie wrote:
> > I assume there is a reason (size on disk? dependencies? update
> > frequency?) why most of distutils shouldn't be in -stdlib, but in the
> > absence of a reference in the changelog, I can o
On Fri, 23 Mar 2018 at 19:35:55 +, Simon McVittie wrote:
> When a small subset of distutils moved back, I assume that the
> intention was to un-break the relatively common(?) case of users of
> distutils.version that do not need the rest of the module, such as
> the gdbus-codegen tool in libgli
On 24.03.2018 03:35, Simon McVittie wrote:
> Package: python3-distutils
> Version: 3.6.5~rc1-2
> Severity: wishlist
> X-Debbugs-Cc: debian-pyt...@lists.debian.org
>
> I'm confused about the current status of distutils, and what should be
> done by packages that depend on it to be as future-proof a
This may also serve to help narrow down (via reverse dependency) the
list of packages which will trigger violent reactions when mixed in
the same context with pip 10 invocations, per
https://github.com/pypa/pip/issues/4805 .
--
Jeremy Stanley
Package: python3-distutils
Version: 3.6.5~rc1-2
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org
I'm confused about the current status of distutils, and what should be
done by packages that depend on it to be as future-proof as possible. I
don't think I'm the only one confused by th
7 matches
Mail list logo
