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
_whitelogger has joined #pypy
andi- has quit [Ping timeout: 244 seconds]
andi- has joined #pypy
<mattip> whoops, forgot to add 3.7 to the table on www.pypy.org/download.html
<mattip> no typos in the blog post?
_whitelogger has joined #pypy
<LarstiQ> mattip: I can't seem to view that
<mattip> hmm, they must have changed the permissions. OK, thanks for trying
<mattip> it won't be the first time I publish a blog post with typos
<LarstiQ> can I view it another way?
<mattip> published, so it is here
<mattip> hah, "transitioning to"
<LarstiQ> good will -> goodwill. `It is based off PyPy 3.6`, might be me but `based off of` feels more correct. One paragraph later there is `are based on` fwiw.
<LarstiQ> `We recommend using CFFI rather than c-extensions to interact with C`, is there maybe a link to the reasons why? I'm already convinced but others may not be
<LarstiQ> `A new contributor took us up on the challenge to get windows 64-bit support.`, mention their name/point to the work?
<LarstiQ> mattip: that's it for what stands out to me
<LarstiQ> (and the transitioning you mentioned)
<mattip> ok, thanks. I think I will put your edits into the release note but let the blog post stand
<mattip> I didn't want to call out the contributor by name, because so far all we know is their heptapod handle
<mattip> and I would prefer people reach out to seriously support the work
<mattip> rather than get "please finish this, it's really important to me" comments on the PR, with no offers of help or money
<mattip> could someone link to the blog post on the twitter feed?
<mgorny> mattip: https://downloads.python.org/pypy/pypy2.7-v7.3.2-src.tar.bz2 doesn't seem to work (it's weird because all other files seem to work already)
<mattip> thanks, checking
<mattip> strange. That site is a mirror of https://buildbot.pypy.org/pypy/,
<mattip> is there a stupid typo?
<mgorny> don't think so, i've used ebuild template
<mgorny> maybe some missync?
lritter has joined #pypy
<mattip> darn. It is all "automatic" so I will have to reach out to #python-infra
<mattip> I can change the link from the pypy.org web page
<mattip> but that won't help your tooling
<mgorny> yeah, i suppose i can switch to buildbot.pypy.org permanently if it's not going away anytime soon
<mattip> it better not go away, we would be in big trouble then
<mattip> the https://buildbot.pypy.org/pypy/ link is a nicely formatted symlink to
<mattip> which is the actual file source location
<mattip> on another note, I tried to upstream the vmprof changes in https://github.com/vmprof/vmprof-python/pull/225
<mattip> but something is off on MacOS, it fails to import _test_stack even though the build is successful
<mattip> if someone with a mac could try that out it would be nice
<mattip> I will probably merge the changes anyway, and resync default pypy/rpython/rlib/rvmprof
<LarstiQ> > < mattip> I didn't want to call out the contributor by name, because so far all we know is their heptapod handle
<LarstiQ> right
oberstet has joined #pypy
<LarstiQ> I appear in some changelogs just by handle and that's fine by me (and in one project had a contributor who specifically didn't want their realname used).
<LarstiQ> and some people don't appreciate the attention either way
<LarstiQ> so balancing that with gratitude
travis-ci has joined #pypy
<travis-ci> vmprof/vmprof-python@master: The build was broken. (https://travis-ci.org/vmprof/vmprof-python/builds/730184896)
travis-ci has left #pypy [#pypy]
<mattip> LarstiQ: I updated the release note with your suggestions, thanks
<cfbolz> mattip: thanks and congratulations for all your work on the release!
<mgorny> boo, 3 parallel translations have made me run OOM :-(
<mgorny> well, 12-job build of chromium probably helped ;-)
<mattip> cfbolz: I will try to be less noisy in the next few weeks
<cfbolz> mattip: you mean as in commits? That goes with the territory :-)
<antocuni> mattip: congrats for the release!
bewees has joined #pypy
bewees has left #pypy ["https://quassel-irc.org - Komfortabler Chat. Überall. "]
<mattip> cfbolz: no, more like bothering people continuously on the mailing list and here
<Cheery> I consider writing a push/enter lisp interpreter in RPython.
<Cheery> I know you got no shortage of those lol
<Cheery> it's de-bruijn indexed, so I call it lijsp
<danchr> with a bit of luck, macports will soon have updated ports for all three versions of pypy, with setuptools and pip as new additions :)
<mgorny> new pypys now in gentoo
<mattip> thanks!
jacob22 has quit [Read error: Connection reset by peer]
wleslie has quit [Ping timeout: 272 seconds]
jacob22 has joined #pypy
wleslie has joined #pypy
ulope has quit [Ping timeout: 256 seconds]
ulope has joined #pypy
Smigwell has left #pypy [#pypy]
wilbowma has quit [Ping timeout: 264 seconds]
wilbowma has joined #pypy
jacob22 has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
dansan has quit [Quit: The C preprocessor is a pathway to many abilities some consider to be unnatural.]
lritter has quit [Ping timeout: 265 seconds]
dansan has joined #pypy
oberstet has quit [Remote host closed the connection]
jacob22 has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
jcea has joined #pypy
jcea has quit [Remote host closed the connection]
jcea has joined #pypy
jcea has quit [Ping timeout: 260 seconds]
jcea has joined #pypy
jcea has quit [Quit: jcea]
jcea has joined #pypy