Project

General

Profile

Actions

Story #20311

open

Update Python packages to build with PEP 517/518

Added by Brett Smith about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Assuming we want to continue to build with setuptools, this means converting our packages' current setup.py to setup.cfg, then adding a (boilerplate) setup.py and pyproject.toml to them.

Reasons to do this:

  • Gives us the option to build packages using other systems in the future if we need or want that for any reason.
  • In my experience, maintining setup.cfg is nicer than setup.py, since it's more declarative.
  • Some of the interfaces of setup.py are deprecated (I think we're already getting warnings about this), and this gives us a clear migration path off those too.

Background reading:

No data to display

Actions

Also available in: Atom PDF