Closed zyv closed 1 year ago
The build for M1 is not working
8.452 running build_ext
8.452 building 'asyncpg.pgproto.pgproto' extension
8.452 creating build/temp.linux-aarch64-cpython-312
8.452 creating build/temp.linux-aarch64-cpython-312/asyncpg
8.452 creating build/temp.linux-aarch64-cpython-312/asyncpg/pgproto
8.452 gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC -I/tmp/tmpbxit6d8s/.venv/include -I/usr/local/include/python3.12 -c asyncpg/pgproto/pgproto.c -o build/temp.linux-aarch64-cpython-312/asyncpg/pgproto/pgproto.o -O2 -fsigned-char -Wall -Wsign-compare -Wconversion
8.452 error: command 'gcc' failed: No such file or directory
8.452
8.452
8.452 at /usr/local/lib/python3.12/site-packages/poetry/installation/chef.py:147 in _prepare
8.454 143│
8.454 144│ error = ChefBuildError("\n\n".join(message_parts))
8.454 145│
8.454 146│ if error is not None:
8.454 → 147│ raise error from None
8.454 148│
8.454 149│ return path
8.454 150│
8.454 151│ def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:
8.454
8.454 Note: This error originates from the build backend, and is likely not a problem with poetry but with asyncpg (0.28.0) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "asyncpg (==0.28.0)"'.
A new release 0.29.0 is out and it comes with Python 3.12 wheels, so I'm closing this. Thanks @elprans !
Hey, could you please either build the wheels for 0.28.0 / Python 3.12 or make a new release? We are moving the codebase to Python 3.12 and installations are currently failing without a C compiler. Thanks!