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
lritter has quit [Remote host closed the connection]
andrewsmedina has quit [Quit: Connection closed for inactivity]
astrojl_matrix has quit [Quit: killed]
suhdonghwi[m] has quit [Quit: killed]
toad_polo has quit [Quit: killed]
omasanori[m] has quit [Quit: killed]
the_drow[m] has quit [Quit: killed]
the_drow[m] has joined #pypy
Dejan has joined #pypy
Dejan has joined #pypy
Dejan has quit [Changing host]
astrojl_matrix has joined #pypy
toad_polo has joined #pypy
omasanori[m] has joined #pypy
suhdonghwi[m] has joined #pypy
<nulano>
arigato, AFAICT, libffi_msvc is not tested with test_longdouble_precision on CPython
<mattip>
nulano: the failures of win64 on the win64 branch look very similar to the failures of win32 on default
<nulano>
I mean for CFFI
<mattip>
sorry, I was changing the subject to pypy in general
<nulano>
ah, right
<mattip>
so I am getting close to wanting to merge it
<mattip>
one consideration is then we would have to be careful about merging default to py3.6, since it might break things there,
<mattip>
would it be reasonable to start a win64-py3.6 branch off py3.6, merge win64 into it, and test it out?
<nulano>
I'm not very familiar with hg yet, but the I'm thinking the following might make sense: open branch win64-py3.6 from py3.6, merge win64 into this branch
<nulano>
resolve any issues that might come up in there, merge win64 into default, merge default into py3.6 but ignore all changes, then merge win64-py3.6 into py3.6
<nulano>
hm... am I making it too complicated?
cjmcdonald has joined #pypy
<mattip>
that sounds about right to me
<mattip>
let's see how the latest py.36 builds tonite