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
speeder39_ has joined #pypy
Alex_Gaynor has quit [Ping timeout: 272 seconds]
Alex_Gaynor has joined #pypy
jacob22 has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
oberstet_ has quit [Remote host closed the connection]
speeder39_ has quit [Quit: Connection closed for inactivity]
glyph has quit [Quit: End of line.]
glyph has joined #pypy
jcea has quit [Remote host closed the connection]
jcea has joined #pypy
epsilonKNOT_ has quit [Ping timeout: 260 seconds]
epsilonKNOT has joined #pypy
jcea has quit [Quit: jcea]
<mattip> a PyStructSeq in CPython has .... quirks. We emulate them with python code in lib_pypy/_structseq.py
<mattip> posix.sched_param is a structseq with a single field sched_priority
<mattip> so CPython lets you do posix.sched_param(sched_priority=0) using a kwarg
<mattip> as far as I can tell, using a kwarg is not well supported for any of the other posix structseq like posix.times_result
<mattip> you can do something like posix.times_result(range(5), {'user': 10}), but the kwarg is ignored
<mattip> so the point of all this is that the redo-pr-639 branch adds posix.sched_param
<mattip> but the lib-python test for it does posix.sched_param(sched_priority=0), which we don't support
<mattip> however posix.sched_param(0) works fine now, even though the arg is not a sequence
<mattip> since I special-cased a structseq with only one field
jeroud has quit [Ping timeout: 240 seconds]
jeroud has joined #pypy
tos9 has quit [Ping timeout: 240 seconds]
Taggnostr has quit [Ping timeout: 240 seconds]
tos9 has joined #pypy
jacob22 has quit [Read error: Connection reset by peer]
Taggnostr has joined #pypy
jacob22 has joined #pypy
todda7 has joined #pypy
<mattip> arigato: rather than sys.is_untranslated, I used an environment variable in 42f538e60a6b
<mattip> does that seem reasonable?
oberstet has joined #pypy
jacob22 has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
todda7 has quit [Ping timeout: 265 seconds]
<agronholm> how far along is pypy's 3.7 support?
<arigato> mattip: sched_param(sched_priority=0): I think we should just support that for all lib_pypy/_structseq objects, there shouldn't be an issue, right?
<arigato> mattip: 42f538e60a6b: this is obscure and a "security risk", please just use monkey-patching
<arigato> mattip: in fact, a better idea would be to have WE_ARE_TRANSLATED = True in the module, and temporarily monkey-patch it to False both in test_app_main.py and in "if __name__=='__main__'" in app_main.py
<arigato> for test_app_main.py, use monkeypatch.setattr()
todda7 has joined #pypy
* arigato tries to fix this
Ai9zO5AP has joined #pypy
andi- has quit [Ping timeout: 260 seconds]
<mattip> thanks
<mattip> agronholm: basically ready for a release I think
<mattip> the win32 support is still not running lib-python tests to completion, I would like to try to clear that problem
<mattip> and I am hoping the hpy support will be merged before the release
<agronholm> that's great to hear
<agronholm> I set the minimum Python version requirement according to the latest pypy3 release in my projects
andi- has joined #pypy
andi- has quit [Excess Flood]
andi- has joined #pypy
<antocuni> mattip: do you have an ETA for the release?
<antocuni> depending on when it is, we might be able to include some hpy support
<antocuni> ronan: are you still actively working on the branch? If not, I can do it
todda7 has quit [Ping timeout: 272 seconds]
<antocuni> another question is whether we WANT to include hpy in the upcoming release; the API is still changing relatively fast, so it is likely that the _hpy_universal included in the release would become obsolete very soon
<mattip> whatever you guys feel
<mattip> I may just give up on win32, but I would like to understand why the py3.7 lib-python run times out
<mattip> so that is why I am trying to get own tests working on top of pypy
<mattip> arigato: 1443744a7f56 won't work for TestInteraction and TestNonInteractive
<mattip> since they are run as "hostpython path/to/app_main.py <extra args>"
<mattip> or did I miss something?
<antocuni> mattip: I think it's a good idea to merge the hpy branch into py3.6, and continue the development there (possibily with more sub-branches). This way, we can have continuous nighlies with latest hpy support
<mattip> ahh, yes I missed the assignment in __main__ at the bottom
<mattip> +1
lritter has joined #pypy
<mattip> it's not like there are tons of hpy c-extensions out there that will break because of an old version of hpy :)
<antocuni> yes, having hpy included in the next official release is probably a no-op. If you want to try hpy, you will very likely need a nightly; if you don't care about hpy, its presence is harmless
<antocuni> so, I vote for: let's do the release whenever it's ready; if hpy has already been merged, that's good. If not, too bad
Rhy0lite has joined #pypy
otisolsen70 has joined #pypy
epsilonKNOT has quit [Ping timeout: 240 seconds]
epsilonKNOT_ has joined #pypy
jcea has joined #pypy
epsilonKNOT_ has quit [Read error: Connection reset by peer]
epsilonKNOT has joined #pypy
<ronan> antocuni: I haven't done anything since Thursday, but I'll continue today
<mattip> I would like it to be in for the release so we can generate some buzz around HPy, even if it is a no-op
<mattip> optics are important
todda7 has joined #pypy
YannickJadoul has joined #pypy
<YannickJadoul> Hi all! Do you know about CMake's problem with generating correct extension module filenames?
<YannickJadoul> Cfr. https://gitlab.kitware.com/cmake/cmake/-/issues/21070; "Here, I think the pypy implementation is wrong. As clearly stated by PEP 3149, SOABI is the module extension without the shared library suffix specific to the platform (i.e. .so or whatever)."
Smigwell has joined #pypy
dddddd has quit [Ping timeout: 240 seconds]
Alex_Gaynor has quit [Ping timeout: 240 seconds]
altendky has quit [Ping timeout: 240 seconds]
Taggnostr has quit [Remote host closed the connection]
petronny has quit [Ping timeout: 240 seconds]
epsilonKNOT has quit [Ping timeout: 240 seconds]
Rhy0lite has quit [Ping timeout: 240 seconds]
Olorin has quit [Ping timeout: 240 seconds]
tos9 has quit [Ping timeout: 240 seconds]
igitoor has quit [Ping timeout: 240 seconds]
Taggnostr has joined #pypy
Taggnostr has quit [Excess Flood]
nulano has quit [Ping timeout: 240 seconds]
ctismer has quit [Ping timeout: 240 seconds]
Ashleee has quit [*.net *.split]
gutworth has quit [*.net *.split]
pmp-p has quit [*.net *.split]
kanaka has quit [*.net *.split]
LarstiQ has quit [*.net *.split]
jerith has quit [*.net *.split]
_aegis_ has quit [*.net *.split]
oberstet has quit [*.net *.split]
ccamel has quit [*.net *.split]
Ninpo has quit [*.net *.split]
dmalcolm has quit [*.net *.split]
Cheery has quit [*.net *.split]
atomizer has quit [*.net *.split]
iko_ has quit [*.net *.split]
lastmikoi has quit [*.net *.split]
danilonc has quit [*.net *.split]
ulope has quit [*.net *.split]
runciter has quit [*.net *.split]
bogner has quit [*.net *.split]
andi- has quit [*.net *.split]
epony has quit [*.net *.split]
ebarrett has quit [*.net *.split]
_whitelogger has joined #pypy
otisolsen70_ has quit [Ping timeout: 240 seconds]
todda7 has quit [Ping timeout: 244 seconds]
epsilonKNOT_ has quit [Quit: ZNC - https://znc.in]
epsilonKNOT has joined #pypy
<mattip> no, it is a pretty trivial fix
<mattip> actually, for 2.7 it seems like the SOABI is correct, the problem is only 3.6+
<mattip> YannickJadoul: uhoh. Not so simple: see this comment
<mattip> it seems wheel 0.34.2 needed a "bad" value, but now there is wheel 0.35
<mattip> so not clear what we should do now
<mattip> LarstiQ: can you point me to the issue you were discussing?
todda7 has joined #pypy
rubdos_ has quit [Ping timeout: 265 seconds]
Ai9zO5AP has quit [Remote host closed the connection]
Ai9zO5AP has joined #pypy
epsilonKNOT has quit [Quit: ZNC - https://znc.in]
epsilonKNOT has joined #pypy
todda7 has quit [Ping timeout: 244 seconds]
<LarstiQ> mattip: https://gitlab.kitware.com/cmake/cmake/-/issues/21070 is what YannickJadoul pasted
rubdos has joined #pypy
otisolsen70_ has joined #pypy
jthistle has joined #pypy
otisolsen70_ has quit [Ping timeout: 265 seconds]
danchr_ is now known as danchr
andr_ has joined #pypy
Ai9zO5AP has quit [Ping timeout: 240 seconds]
Ai9zO5AP has joined #pypy
Smigwell has left #pypy [#pypy]
lritter has quit [Quit: Leaving]
<mattip> LarstiQ, YannickJadoul: https://github.com/pypa/wheel/issues/372
<mattip> we cannot update the SOABI tag without coordinating with wheel
<YannickJadoul> mattip, LarstiQ: Auwtch :-(
<YannickJadoul> I already wondered why I never saw problems, before switching to this new FindPython in CMake
<mattip> at least CMake seems to have solved the problem by avoiding SOABI
<YannickJadoul> Oh, they did?
<YannickJadoul> I thought that was only for PyPy with Python 2?
<YannickJadoul> I tried just this afternoon, with CMake 3.18.2 and a PyPy 3 nightly
YannickJadoul has quit [Quit: Leaving]
<mattip> YannickJadoul: (for the logs) and it fails?
Ai9zO5AP has quit [Ping timeout: 240 seconds]
Ai9zO5AP has joined #pypy
jthistle has quit [Quit: Connection closed]
YannickJadoul has joined #pypy
<YannickJadoul> mattip: Yup, it did :-( That's how I noticed in the first place: CMake creates a `.so` file that PyPy 3 can't load
<YannickJadoul> (well, a filename that PyPy 3 doesn't look for)
<YannickJadoul> PyPy 2 works perfectly, creates and imports `example.pypy-73.so`
<YannickJadoul> mattip, LarstiQ: Something else I just thought of. Does this just need to be coordinated with wheel? Isn't it setuptools which determines the name of the .so file?
dje_ has quit [Quit: Leaving]
jcea has quit [Ping timeout: 240 seconds]
jcea has joined #pypy
ronan has quit [Ping timeout: 272 seconds]
ronan has joined #pypy
ronan is now known as Guest27220
jcea has quit [Quit: jcea]