Not sure exactly what broke in the chain of my toolset for building reportlab. I have a github action which fails with
ls: cannot access /opt/python/cp27-cp27mu/bin: No such file or directory
so because I have fixed the checkout version of the multibuild area itself I suppose that something else changed/updated
since the last build which was successful on Jan 22.
has multibuild / manylinux decided to abandon the python 2.7 version or is there something I can do to get my builds
As an aside is it worth trying to fix the version of multibuild or should I just assume that most of the variability
will come from the many docker layers that seem to be used.
> Digest: sha256:efc8a9832a07678fc17026ab35aa6444c02a665ccd5e6552c90d036045d78b17
> Status: Downloaded newer image for quay.io/pypa/manylinux2010_x86_64:latest
> + break
> + '[' 5 -eq 0 ']'
> + return 0
> + docker run --rm -e 'BUILD_COMMANDS=build_wheel reportlab' -e PYTHON_VERSION=2.7 -e MB_PYTHON_VERSION=2.7 -e UNICODE_WIDTH=32 -e BUILD_COMMIT=HEAD -e CONFIG_PATH=.travis-config.sh -e ENV_VARS_PATH= -e WHEEL_SDIR=wheelhouse -e MANYLINUX_URL= -e BUILD_DEPENDS= -e USE_CCACHE= -e REPO_DIR=reportlab -e PLAT=x86_64 -e MB_ML_VER=2010 -v /home/runner/work/reportlab-mirror/reportlab-mirror:/io -v /home/runner:/parent-home quay.io/pypa/manylinux2010_x86_64 /io/multibuild/docker_build_wrap.sh
> ls: cannot access /opt/python/cp27-cp27mu/bin: No such file or directory
> Error: Process completed with exit code 2.
Thanks Jeremy, I will check those out. I thought that maybe there was a
simple flag I could pass in to python -m build that would allow me to
override a value in setup.cfg, but I should probably read through
PEP517/PEP518 in full to get a better overview of this process.
> From: Jeremy Stanley <fungi(a)yuggoth.org>
> Date: Tue, Feb 9, 2021 at 3:26 PM
> Subject: [Distutils] Re: Building Pre-releases with setup.cfg
> To: <distutils-sig(a)python.org>
> On 2021-02-09 09:48:31 -0500 (-0500), Matthew Gilbert wrote:
> > I'm wondering if it is possibly to build pre-release tags using only a
> > setup.cfg file? From
> > it seems like this is possible via setup.py, but I was unable to find
> > anything related to setup.cfg.
> > Possibly this can be configured using the --config-setting flag but I
> > been unable to get this to work or find any documentation on it. Ideally
> > would be able to pass a string so I can build a dev version for testing
> > uploads to Test PyPI, e.g. "0.0.1devHASH"
> I'm probably misunderstanding your question, but typically I've seen
> something like PBR or Setuptools-SCM used to automatically calculate
> the version at dist build time (including inferring something based
> on the number of commits on the branch since the last tag, embedding
> abbreviated Git commit IDs, or whatever).
> Jeremy Stanley
> Distutils-SIG mailing list -- distutils-sig(a)python.org
> To unsubscribe send an email to distutils-sig-leave(a)python.org
> Message archived at
I'm wondering if it is possibly to build pre-release tags using only a
setup.cfg file? From
it seems like this is possible via setup.py, but I was unable to find
anything related to setup.cfg. An abridged version of my setup.cfg file
name = tester_project
version = attr: tester_project.__version__
setuptools >= 40.9.0
build-backend = setuptools.build_meta
Which I was building using
$ python -m build --sdist --wheel --outdir dist
Possibly this can be configured using the --config-setting flag but I have
been unable to get this to work or find any documentation on it. Ideally I
would be able to pass a string so I can build a dev version for testing
uploads to Test PyPI, e.g. "0.0.1devHASH"
Any info or references is much appreciated!