Skip to content
Snippets Groups Projects
  1. Nov 27, 2024
    • Matt Harbison's avatar
      ci: disable caching of the wheels that get built to save space · 1a09563a
      Matt Harbison authored
      I had a pile of these one-shot wheels cached on the mac, taking about 1.2G of
      space from the few weeks we've been building wheels to test, and with the few
      times the macOS tests were actually run.  There's not much point in caching
      these, since the tests run from a wheel file the tests are force fed.  There is
      still an issue with one wheel from the tests being cached (probably on install),
      but that's 1/6 of the original problem.
      
      I'm putting this in the `pyproject.toml` because I think that's where we should
      have all of the `cibuildwheel` config collected.  There's a concurrent effort to
      modernize `setup.py` and use this file more, so I'll hold off on pushing most of
      the config in here for now.  But this applies the setting to all OSes, as well
      as when run through either CI or the individual buid scripts, so I think this is
      clearly the right way to go.
      
      Note that the docs for `cibuildwheel` talks about the intention to move from
      `pip` to `build` some day.  This config only covers the former, so the other
      config example[1] with the latter may be needed at some point.  But I don't see
      an obvious option for that tool, so we'll cross that bridge when we come to it.
      
      [1] https://cibuildwheel.pypa.io/en/v2.22.0/options/#examples_6
      1a09563a
  2. Oct 10, 2024
  3. Sep 09, 2021
    • Raphaël Gomès's avatar
      pep-517: remove the `build-backend` key to allow for users to build extensions · 58fe6d12
      Raphaël Gomès authored
      PEP 517 changed how projects should define their build dependencies.
      The presence of a `pyproject.toml` file changes the behavior of `pip` to
      conform to PEP 517.
      Since we haven't updated the `setup.py` file yet (I'm not even sure we're not
      an edge case which would make it harder/impossible, I have not tried yet), this
      is a workaround to issue6589: it allows users to pass `--no-use-pep517` to pip
      to revert to the legacy installer. The build backend is simply assumed to be
      the `build_meta:__legacy__` one.
      
      Differential Revision: https://phab.mercurial-scm.org/D11393
      58fe6d12
  4. Dec 01, 2020
Loading