cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | the secret reason for us trying to get PyPy users: to test the JIT well enough that we're somewhat confident about it
<kenaan>
antocuni extradoc b403731a96c4 /blog/draft/2018-09-cpyext/cpyext.rst: better to use PyObject* without a space: it renders better in an HTML page
<kenaan>
antocuni extradoc a4b382cdada7 /blog/draft/2018-09-cpyext/cpyext.rst: write another section, essentially explaing what we did in cpyext-avoid-roundtrips
<LarstiQ>
"Py-spy works by directly reading the memory of the python program using the process_vm_readv system call on Linux, the vm_read call on OSX or the ReadProcessMemory call on Windows."
<LarstiQ>
"Figuring out the call stack of the Python program is done by looking at the global PyInterpreterState variable to get all the Python threads running in the interpreter, and then iterating over each PyFrameObject in each thread to get the call stack. "
tayfun26 has joined #pypy
antocuni has joined #pypy
nunatak has quit [Quit: Leaving]
<vstinner>
antocuni: hi. thanks for your support. i feel less alone :)
<antocuni>
vstinner: hi
<antocuni>
not sure how actually helpful it is, though
<vstinner>
antocuni: as i wrote, at least i feel less alone :)
<vstinner>
antocuni: i didn't know that there were so many supporters of the current crappy C API :)
<vstinner>
antocuni: but well, i'm not surprised to meet people opposed to any kind of changes :)
<vstinner>
people are always afraid of change, for good reasons
<tos9>
vstinner: stockholm syndrome sucks
<antocuni>
I think that in general there are always people who opposes changing; and maybe it's a good thing, because too many changes are a problem as well
<vstinner>
tos9: haha
<vstinner>
sometimes, i like working on my toy projects, just because i can really modify *everything*
<jamesaxl>
I hope that you are interested about HardnenedBSD
marky1991 has joined #pypy
il_ratto has left #pypy [#pypy]
Garen_ has joined #pypy
Garen has quit [Ping timeout: 246 seconds]
marky1991 has quit [Ping timeout: 245 seconds]
alexband has joined #pypy
marky1991 has joined #pypy
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
tayfun26 has quit [Quit: tayfun26]
user24 has joined #pypy
user24 has quit [Quit: Leaving]
user24 has joined #pypy
user24 has quit [Client Quit]
forgottenone has quit [Quit: Konversation terminated!]
alexband has quit [Remote host closed the connection]
adamholmberg has joined #pypy
alexband has joined #pypy
alexband has quit [Ping timeout: 245 seconds]
user24 has joined #pypy
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 245 seconds]
marky1991 has quit [Ping timeout: 252 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 245 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Remote host closed the connection]
user24 has quit [Quit: Leaving]
adamholmberg has joined #pypy
marky1991 has joined #pypy
antocuni has quit [Ping timeout: 245 seconds]
arigato has joined #pypy
marky1991 has quit [Ping timeout: 252 seconds]
marky1991 has joined #pypy
marky1991 has quit [Ping timeout: 245 seconds]
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
inhahe_ has joined #pypy
inhahe has quit [Ping timeout: 240 seconds]
adamholmberg has quit [Ping timeout: 240 seconds]
adamholmberg has joined #pypy
raynold_ has joined #pypy
raynold_ has quit [Client Quit]
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 245 seconds]
marky1991 has joined #pypy
adamholmberg has joined #pypy
arigato has quit [Quit: Leaving]
<blachance>
it seems like contents of green variables always get guard_value'd in traces--does that sound accurate?
<blachance>
i'm curious because in some circumstances i'd rather a guard_class, and i a follow-up question would be: do RPython programmers have a way to control those green variable guards
<cfbolz>
blachance: if you want a guard_class you shouldn't list the variables as green
<cfbolz>
green indeed means that a guard_value is needed
<blachance>
figured as much, thanks :)
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
Garen_ has quit [Read error: Connection reset by peer]
Garen has joined #pypy
adamholmberg has quit [Ping timeout: 272 seconds]
<cfbolz>
blachance: you get a guard_class sort of automatically for every rpython-level method call you do on a (red) variable
speeder39 has joined #pypy
lritter has joined #pypy
nunatak has joined #pypy
adamholmberg has joined #pypy
<blachance>
cfbolz: ah right, and that gives me an idea. thanks!
nunatak has quit [Quit: Leaving]
lritter has quit [Remote host closed the connection]
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 245 seconds]
cjwelborn has quit [Remote host closed the connection]
kanaka has quit [Remote host closed the connection]
adamholmberg has joined #pypy
__pv has quit [Remote host closed the connection]
marky1991 has quit [Remote host closed the connection]