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
jacob22_ has quit [Read error: Connection reset by peer]
jacob22_ has joined #pypy
_whitelogger has joined #pypy
<mattip>
what is better: to delay the release in order to update stdlib to the latest versions, or ship now with bug fixes and new features?
<Dejan>
mattip, I think PyPy users are used to have versions behind the upstream anyway
<Dejan>
I for an example do not mind stdlib being slightly behind
<Dejan>
The moment 3.7 gets released I will make a ticket in our backlog to move to 3.7 even though we do not use PyPy extensively but I like our team to use version of Python that is supported in PyPy
<Dejan>
:)
<antocuni>
mattip: I think that releasing early is a good solution
<Dejan>
+1
<mattip>
thanks
<mattip>
it's not to late for hpy, if it can get merged this week
proteusguy has quit [Ping timeout: 258 seconds]
proteusguy has joined #pypy
<mattip>
I made a little sphinx extension that will allow searching on doc.pypy.org to find docs in rpython, and the other way around
<mattip>
for pytorch
<mattip>
let's see if it works
oberstet has joined #pypy
jcea has joined #pypy
<antocuni>
mattip: I plan to merge hpy into py3.6 sooninsh: can I do it, or it interferes with the release and I should wait?
jcea has quit [Remote host closed the connection]
<mattip>
cool, yeah go for it
<mattip>
antocuni ^^^
jcea has joined #pypy
<antocuni>
cool. I want to fix the tests first, though
* antocuni
fighting with test_ztranslation
<mattip>
as we discussed before, it is a backend, so only active if someone imports hpy, so should be harmless
<mattip>
famous last words
<antocuni>
true, but I would like to switch to a development workflow in which we develop hpy features inside branches, and merge with PRs, proper review and only if the hpy tests pass
<antocuni>
so better to start from a situation in which the tests already pass :)
Smigwell has joined #pypy
rubdos has quit [Ping timeout: 244 seconds]
rubdos has joined #pypy
marky1991 has quit [Ping timeout: 256 seconds]
LarstiQ has quit [Ping timeout: 265 seconds]
LarstiQ has joined #pypy
andrewsmedina has joined #pypy
lritter has joined #pypy
TheNewbie has joined #pypy
jcea has quit [Remote host closed the connection]
jcea has joined #pypy
andrewsmedina has quit [Ping timeout: 258 seconds]
andrewsmedina has joined #pypy
jvesely has joined #pypy
andrewsmedina has quit [Ping timeout: 246 seconds]
jvesely_ has joined #pypy
jvesely has quit [Read error: Connection reset by peer]
jvesely_ is now known as jvesely
<mattip>
it seems we implemented all the PyMemoryView_* C-API interfaces except the one that is always public
<mattip>
PyMemoryView_GetContiguous
<mattip>
the others, that we implemented, are behind some form of #if ndef(Py_LIMITED_API)
andrewsmedina has joined #pypy
TheNewbie has quit [Quit: Leaving]
omnipotententity has quit [Read error: Connection reset by peer]
omnipotententity has joined #pypy
omnipotententity has quit [Changing host]
omnipotententity has joined #pypy
jvesely has quit [Read error: Connection reset by peer]
jvesely has joined #pypy
lritter has quit [Ping timeout: 246 seconds]
andrewsmedina has quit [Ping timeout: 258 seconds]
lritter has joined #pypy
jacob22_ has quit [Read error: Connection reset by peer]