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
<LarstiQ>
https://github.com/pyston/pyston/wiki/Semantic-changes "We think of Pyston as an "optimized build" in the same way that an optimized binary will be harder to debug than a debug-enabled binary. If you want the removed features you can use the "debug build" of stock Python because they are interchangeable."
<fijal>
is pyston also FB?
<LarstiQ>
I was only aware of Pyston being Dropbox
gef has joined #pypy
gef has quit [Ping timeout: 246 seconds]
<cfbolz>
LarstiQ: not anymore
<mattip>
it is independent, the devs have their own consulting company
<Dejan>
I did not even know this existed until my colleague told me earlier
freema has joined #pypy
freema has quit [Quit: Connection closed]
<krono>
hey. did something in rpython change in the last year regarding unification of strings/unicode?
<fijal>
Dejan: alternative python implementations come and go
<fijal>
it's sad, but turns out your whitepaper looks always much better than pypy, so you are like "lol, those people are complete idiots, we at company X are much smarter"
<fijal>
... and inevitably it's more work than you thought it is
<Dejan>
I guess they actually use it in production
<Dejan>
Idk... I did not try it
<fijal>
I've been asked so many times about that "what do you think about this whitepaper?" and the answer usually is "well, let's see how it'll pan out in practice. whitepaper looks very ambitious"
<cfbolz>
krono: not intentionally
<mattip>
krono: do you mean after the utf-8 change?
<krono>
mattip: I don't know. the last checkout I tried is pre-2020, the current from a few weeks back
<simpson>
fijal: This is the flip side of when product managers tell me that no, compilers aren't special, and they can be Agile'd up into bite-size pieces.
<simpson>
The same product managers sign off on these ambitious compiler projects precisely because they don't understand that a compiler pass, as a deliverable, is usually all-or-nothing in terms of branch coverage and feature-completeness.
Dejan_ has quit [Quit: Leaving]
<simpson>
(This is also incidentally why they usually prefer to alter CPython; it is very Agile to alter an existing deliverable.)
Dejan has joined #pypy
Dejan has quit [Changing host]
Dejan has joined #pypy
<cfbolz>
krono: go up in the pdb und then do "callg graph" once you find a graph variable
<cfbolz>
then inspect the flow graphs
Gustavo6046_ has joined #pypy
Gustavo6046 has quit [Ping timeout: 250 seconds]
Gustavo6046_ is now known as Gustavo6046
<ronan>
krono: that looks like a bug in rpython. I guess int(unicode) is broken
<krono>
oh dear
<krono>
I'll also probably run into ord(unicode) problems down the line
<simpson>
ord() should work; you do have to prove that its len() is 1, but that's usually inferred easily.
<krono>
well... `ord('🔥')` will break
<simpson>
Can't mix strs and unicode; gotta be distinct and clear about what you want. Personally, I paid the tax for the Unicode sandwich, and use u'' literals all the time.
<krono>
simpson: yeah sorry, I meant u''. I got confused, too many python-layers/combinations
asmeurer has joined #pypy
<ronan>
krono: ord('🔥') should work. RPython unicode is UTF-32
<krono>
neat. thats good to know, one thing less to worry about
gef has quit [Ping timeout: 246 seconds]
nimaje has quit [Remote host closed the connection]
nimaje has joined #pypy
gef has joined #pypy
<ronan>
krono: I pushed an untested fix. Can you try again?
gef has quit [Ping timeout: 268 seconds]
<krono>
ronan: what branch?
<ronan>
krono: default
<krono>
ah I see
<krono>
thanks
<krono>
ronan: looks much better, thanks!
<krono>
yea it translates
otisolsen70_ has joined #pypy
otisolsen70_ has quit [Remote host closed the connection]
otisolsen70 has quit [Ping timeout: 260 seconds]
gef has joined #pypy
tbodt_ has joined #pypy
tbodt_ has quit [Ping timeout: 268 seconds]
gef has quit [Ping timeout: 240 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 265 seconds]
asmeurer has quit [Quit: asmeurer]
gef has joined #pypy
gef has quit [Ping timeout: 252 seconds]
gef has joined #pypy
lritter has quit [Ping timeout: 260 seconds]
gef has quit [Ping timeout: 260 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 252 seconds]
asmeurer has joined #pypy
gef has joined #pypy
asmeurer has quit [Quit: asmeurer]
gef has quit [Ping timeout: 246 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 252 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 260 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 240 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 240 seconds]
gef has joined #pypy
gef has quit [Ping timeout: 265 seconds]
<mattip>
the win64 rc2 is failing the numpy test suite (cd numpy; pypy -m ensurepip; pypy -m pip install -r test_requirements.txt; pypy -m runtests.py)
<mattip>
the failures look like int/longlong mixups