This causes a minor issue with newer versions of sys-apps/portage that want to use socket.sethostname(), notibly [1]. When using ebuild or the emerge frontend, the following message will show up in build logs: Unable to set hostname: module 'socket' has no attribute 'sethostname' (for FEATURES="network-sandbox") Reproduce with: pypy3 -c 'import socket; print(socket.sethostname)' [1]: https://github.com/gentoo/portage/commit/28ce410d2aa2eb33d0e61fbf272e1929b734622d
Confirmed. Except that issue using pypy3 with portage is seamless
We could add a workaround to Portage, I guess, as we load libc anyway.
(In reply to Michał Górny from comment #2) > We could add a workaround to Portage, I guess, as we load libc anyway. https://gitweb.gentoo.org/proj/portage.git/commit/?id=c35f39af1ae591c9df50da52e83067428a10f80a
it has returned as different error in pypy-7.3.2. Unable to set hostname: expected unicode, got bytes object (for FEATURES="network-sandbox")
I meant pypy3-7.3.2 ofc.
Confirmed
(In reply to Reva Denis from comment #6) > Confirmed I mean I can reproduce it in pypy3-7.3.2
This should be fixed in -r1 now.
(of pypy3-exe/-bin)