How to select pypy3? about multibuild HOT 8 CLOSED

The numpy-wheels recipe uses MB_PYTHON_VERSION: "pypy3.7-7.3.5". PyPy is no longer supporting python3.6. What happens if you try MB_PYTHON_VERSION=pypy3.7-7.3.5?

from multibuild.

I get the same exact error: https://github.com/fonttools/skia-pathops/pull/46/checks?check_run_id=3222260850#step:7:286

In fact, I think you stumbled over this as well: https://github.com/matthew-brett/multibuild/pull/314#issuecomment-592989981

from multibuild.

This is failing in the post-build test phase. The test docker images in matthewbrett/trusty:64 have not been updated for quite a while. Please use the docker images from multibuild/xenial_* by specifying DOCKER_TEST_IMAGE: multibuild/xenial_{PLAT}

from multibuild.

Ok, thanks. Is it advisable to use that image for everything?

from multibuild.

Do you mean for all testing? I would suggest to since trusty is Ubuntu 14.04 and really old (even xenial 16.04 is old, I should build some focal 20.04 ones). The Ubuntu containers are not used for building since that must be done in the regular manylinux containers in order to get manylinuxXXX compatibility.

from multibuild.

Ok thanks, will do.

I found something new though: https://github.com/fonttools/skia-pathops/pull/46/checks?check_run_id=3222590296#step:7:378 -- it's happening in the install_run $PLAT phase.

from multibuild.

Now I think we have moved past multibuild and into your test suite, I will comment on the PR

from multibuild.

Thanks for your help, I think this issue can be closed now.

The solution for whoever might stumble on this issue:

1. Use MB_PYTHON_VERSION="pypy3.7-7.3.5"
2. Use DOCKER_TEST_IMAGE="multibuild/xenial_{PLAT}" where PLAT is your target architecture.

from multibuild.