antocuni changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | "PyPy: the Gradual Reduction of Magic (tm)"
danieljabailey has quit [Quit: ZNC 1.6.5+deb2build2 - http://znc.in]
danieljabailey has joined #pypy
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
tbodt has joined #pypy
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<sh4rm4^bnc>
again, i won't let other package managers mess up my sys
<Jonno_FTW>
that's perfectly fine
<sh4rm4^bnc>
if i install pypy, i will write a proper recipe
<Jonno_FTW>
just use pyenv to manage different versions of python outside the package mangetr
<Jonno_FTW>
it installs them in ~/.pyenv/versions
<Jonno_FTW>
you only need these packages or their equivalents to install python: libssl-dev zlib1g-dev libbz2-dev libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev xz-utils
<sh4rm4^bnc>
thanks for info. i will consider installing pypy eventually. in the moment i'm asking questions to see if it is suitable for my plans.
<Jonno_FTW>
why no cpython?
<sh4rm4^bnc>
i was asking previously about using pypy's rpython to implement own language.
<Jonno_FTW>
ah
<Jonno_FTW>
my pypy keeps crashing with this error: Fatal RPython error: AssertionError
<arigato>
there's basically only one error. it could be fixed by editing cairo to not dig inside PyBaseExceptionObject like this
<arigato>
or we could support it, with a bit more effort, inside pypy
<arigato>
the proper fix to cairo would be to call PyObject_GetAttributeString(self, "args") instead of self->base.args
<arigato>
PyObject_GetAttrString(self, "args")
<xqb>
well it's nice to hear it could be (easily?) done
<xqb>
this might sound selfish but might we expect this to happen in the near future?
<xqb>
a month, two?
<fijal>
xqb: on its own - a bit unlikely
marr has joined #pypy
<fijal>
someone has to either be interested in fixing pycairo etc or pay someone else to do it
<xqb>
yeah I see
<xqb>
that's a pity I wanted to use PyPy badly :)
<arigato>
it's really a 5-minutes change, but then it needs to be tested again and maybe we'll see more issues
<arigato>
from our point of view, we're more likely to fix pypy
<xqb>
well I'd be happy to do it myself it's just I'm far from competent to do so
<xqb>
:)
<arigato>
but you can try to tell the pycairo developers what I just said and they may try
<xqb>
okay, will do
<xqb>
I'll save this somewhere and probably submit an 'official' issue or something
<xqb>
I don't feel like chasing them on IRC :)
<arigato>
yes, makes sense too
<fijal>
well there is a chance it's not the only one
<fijal>
but it's also likely that a lot of them are like this (maybe all)
<xqb>
I see
<xqb>
I'll do this later today/tomorrow and I'll let you all know what happened
forgottenone has quit [Quit: Konversation terminated!]
forgottenone has joined #pypy
asmeurer__ has quit [Quit: asmeurer__]
lazy1 has quit [Ping timeout: 276 seconds]
<kenaan_>
cfbolz default 7add90a647dc /pypy/: merge mapdict-size-limit stop using mapdict after 80 attributes to prevent linear lookups on attributes when usin...
xqb has quit [Changing host]
xqb has joined #pypy
xqb has joined #pypy
amaury has joined #pypy
amaury has quit [Read error: Connection reset by peer]
raynold has quit [Quit: Connection closed for inactivity]
amaury has quit [Ping timeout: 256 seconds]
Hotpot33 has quit [Ping timeout: 248 seconds]
lazy1 has joined #pypy
Hotpot33 has joined #pypy
jamesaxl has quit [Read error: Connection reset by peer]
glyph has quit [Ping timeout: 252 seconds]
jamesaxl has joined #pypy
glyph has joined #pypy
Hotpot33 has quit [Ping timeout: 248 seconds]
Hotpot33 has joined #pypy
<xqb>
fijal, arigato: might someone assist me with the issue; should I just cp the conversation above, should I strip your nicknames, should I start it as "I've talked to PyPy developers who think that this and that yada yada"...? sorry if this is too silly, but..not sure :)
<fijal>
xqb: feel free to use our names if it's helpful - the general problem is "this is not an official use of CPython C API and as such does not work on pypy - here is how to use it in a more official way"
<xqb>
fijal: ok, thanks, what about the title itself? :)
<fijal>
"Unofficial Python C API usage" maybe?
<arigato>
it's certainly not officially documented
<kenaan_>
cfbolz py3.5 5ad0629dd41b /pypy/interpreter/: make sure that the error message for invalid characters in byte string literals contains position information. impro...
forgottenone has quit [Ping timeout: 240 seconds]
<kenaan_>
cfbolz py3.5 095d5a88a186 /pypy/interpreter/: while I am touching that code: make the error offset more precise when there are several bytes literals after each o...
adamholmberg has joined #pypy
Thinh has quit [Quit: Bye!]
Thinh has joined #pypy
Thinh has quit [Client Quit]
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Remote host closed the connection]
Thinh has joined #pypy
adamholmberg has joined #pypy
Thinh has quit [Client Quit]
Thinh has joined #pypy
yuyichao_ has quit [Ping timeout: 240 seconds]
<kenaan_>
cfbolz default 2cb74fa177c2 /pypy/interpreter/: fix pypy2 version of the bug fixed in 095d5a88a186 (which is on py3.5)
yuyichao_ has joined #pypy
Rhy0lite has joined #pypy
gcbirzan has quit [Ping timeout: 256 seconds]
marky1991 has joined #pypy
<arigato>
cfbolz: there's a pdb.set_trace() in 2cb74fa177c2
gcbirzan_ has joined #pypy
<cfbolz>
arigato: ouch, thanks
<arigato>
:-)
<cfbolz>
u"\x"
<cfbolz>
x = u"a" u"c" u"c" \
<cfbolz>
arigato: essential improvement to our error messages, if you write errors like this: