cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
<arigato>
mattip (logs): thank you for answering on the cffi mailing list
jcea has joined #pypy
ronan has quit [Ping timeout: 252 seconds]
mattip_ has joined #pypy
YannickJadoul has joined #pypy
ronan has joined #pypy
Rhy0lite has joined #pypy
dddddd has joined #pypy
<YannickJadoul>
mattip_: I noticed that the version and ABI tags in nightly is now pp373-pypy36_pp73 for PyPy3. Is this just because the ABI is different between 3.6 and 3.7, or is there a plan to release multiple Python 3 versions of PyPy?
<YannickJadoul>
(Trying to make the cibuildwheel PR a little bit future-proof)
ronan has quit [Ping timeout: 245 seconds]
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
marky1991 has joined #pypy
<mattip_>
the second. When we release python3.7 version of pypy, there may be a time where python3.6 and python3.7 share the same pypy_version_info
<mattip_>
that was my motivation for changing the abi tag format
<mattip_>
pip/setuptools/wheel control the pytohn version tag pp373, if I could choose it would be pp3 or pp36 (using only the version_info, not the pypy_version_info
<mattip_>
)
<YannickJadoul>
Hmm, I see
<YannickJadoul>
Because indeed, the version tag wouldn't distinguish between PyPy 3.6 and PyPy 3.7
<YannickJadoul>
So in cibw, we have "build identifiers" like cp38-manylinux_x86_64 that can be selected and deselected
<YannickJadoul>
And for PyPy that would currently be something like pp372-manylinux_pypy_x86_64. But this way, we won't be able to distinguish 3.6 and 3.7
<mattip_>
if you are constructing this by hand, I think pp3 would be safely recognized as the python tag
<mattip_>
if you need a more specific solution, you should be using the abi tag instead of "none" anyway
ronan has joined #pypy
<YannickJadoul>
mattip_: Well, it's more of a cibw-specific thing, where the identifiers to select which versions to build are based on the PEP 425 version tag
<YannickJadoul>
Based, but not exact anymore, since we've merged manylinux1 and manylinux2010 into ...-manylinux...
<YannickJadoul>
But thanks for the extra info :-)
<mattip_>
manylinux2014 which was just released now supports aarch64, ppc64le, and s390x, as does travisCI
jvesely has joined #pypy
<mattip_>
and the PSF is hiring two developers to work on pip in 2020, see my comments in the logs
bendlas has joined #pypy
edd[m] has joined #pypy
extraymond[m] has joined #pypy
agates[m] has joined #pypy
ronan has quit [Ping timeout: 265 seconds]
ronan has joined #pypy
<YannickJadoul>
I don't know if it matters anything, but while the macOS download of PyPy says "(High Sierra >= 10.13, not for Sierra and below)", I've just managed to run it on an old 10.11 installation?
YannickJadoul has quit [Quit: Leaving]
<mattip_>
something around one of the time or datetime modules may not work properly
<mattip_>
does it pass lib-python tests?
ronan has quit [Remote host closed the connection]
YannickJadoul has joined #pypy
<YannickJadoul>
mattip_: To be fair, I didn't try that
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
<YannickJadoul>
OK, they don't. Something with undeclared identifier 'py_w_stopcode' and another fatal error on 'asyncgen'
<YannickJadoul>
Sorry; should've looked further, but I was just trying to figure out the version number to put in cibw
YannickJadoul has quit [Quit: Leaving]
<mattip_>
that wasn't what I was expecting. Now I wonder if the same thing happens on High Sierra
inhahe has quit []
inhahe has joined #pypy
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
Rhy0lite has quit [Quit: Leaving]
ronan has joined #pypy
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
marky1991 has quit [Ping timeout: 276 seconds]
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
i9zO5AP has quit [Quit: WeeChat 2.5]
ronan has quit [Ping timeout: 240 seconds]
ronan has joined #pypy
<kenaan>
rlamy hpy a4ddff5d8e92 /: A branch to create an HPy implementation in PyPy.
<mattip_>
some people are sprinting on it now, might want to wait until they release a version
<antocuni>
well, it's in very early stage so far
<Dejan>
for D <--> Python interop
<antocuni>
I'm not sure how it would help D<-->Python interop. It is an API for Python implementation <--> extension modules interop
marvin_ has quit [Remote host closed the connection]
marvin has joined #pypy
marvin is now known as Guest35071
Guest35071 has quit [Remote host closed the connection]
marvin__ has joined #pypy
ronan has quit [Ping timeout: 246 seconds]
lritter has joined #pypy
ronan has joined #pypy
tsaka_ has joined #pypy
ronan has quit [Ping timeout: 240 seconds]
<Dejan>
antocuni, what if I want to write an extension in D?
<Dejan>
that is what I had in mind
ronan has joined #pypy
<kenaan>
rlamy hpy 19d6e8fbace2 /pypy/module/hpy_universal/test/: (antocuni, ronan) Setup the infrastructure to compile and test HPy modules Vendor files from pyhandle/hpy inside pypy/...
<kenaan>
arigo default 4234613045bb /pypy/module/_socket/: Issue #3114 Allow general buffers in socket.setsockopt(), like CPython does
ronan has quit [Ping timeout: 265 seconds]
lritter has quit [Quit: Leaving]
lritter has joined #pypy
tos9_ has joined #pypy
tos9 has quit [Ping timeout: 268 seconds]
tos9_ is now known as tos9
mattip_ has quit [Ping timeout: 252 seconds]
asmeurer__ has joined #pypy
marky1991 has joined #pypy
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
marky1991 has quit [Remote host closed the connection]