sagemath/sage

Update setuptools to 63.2.0

mkoeppe opened this issue · 11 comments

https://setuptools.pypa.io/en/latest/history.html#v63-1-0

This will get rid of the annoying "package init file ... not found" warnings for namespace packages. (#33011 comment:65)

CC: @kwankyu @jhpalmieri

Component: packages: standard

Author: Matthias Koeppe

Branch/Commit: d60fa18

Reviewer: John Palmieri

Issue created by migration from https://trac.sagemath.org/ticket/34177

Commit: 989217f

New commits:

989217fbuild/pkgs/setuptools: Update to 63.1.0

Branch pushed to git repo; I updated commit sha1. New commits:

d60fa18build/pkgs/setuptools: Update to 63.2.0

Changed commit from 989217f to d60fa18

Reviewer: John Palmieri

comment:6

Looks good to me. Straightforward update.

comment:7

Thanks!

comment:8

By the way, I see many messages like this in package log files:

      ############################
      # Package would be ignored #
      ############################
      Python recognizes 'terminado._static' as an importable package,
      but it is not listed in the `packages` configuration of setuptools.

      'terminado._static' has been automatically added to the distribution only
      because it may contain data files, but this behavior is likely to change
      in future versions of setuptools (and therefore is considered deprecated).

      Please make sure that 'terminado._static' is included as a package by using
      the `packages` configuration field or the proper discovery methods
      (for example by using `find_namespace_packages(...)`/`find_namespace:`
      instead of `find_packages(...)`/`find:`).

      You can read more about "package discovery" and "data files" on setuptools
      documentation page.

(There are lots of hits for "Package would be ignored".) This is unaffected by the update to setuptools. Is this something to worry about?

comment:9

This is a warning about a future breaking change in setuptools. When we do the update to the future version in which this change is done, we'll have to update all packages that currently show this warning. Nothing to worry about.