cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
nexussfan has quit [Ping timeout: 264 seconds]
mjacob has quit [Ping timeout: 252 seconds]
Dagger has quit [Ping timeout: 268 seconds]
alice has quit [Ping timeout: 268 seconds]
mjacob has joined #pypy
Dagger has joined #pypy
Dagger has quit [Ping timeout: 264 seconds]
alice has joined #pypy
Dagger has joined #pypy
_whitelogger has joined #pypy
_whitelogger has joined #pypy
BarrensZeppelin has quit [Ping timeout: 245 seconds]
BarrensZeppelin has joined #pypy
BarrensZeppelin has quit [Remote host closed the connection]
lritter has joined #pypy
<closet5> korvo: i'm writing my own parser and i don't have experience with rlib.parsing (i wanted to use it, but i couldn't find how). maybe i can help if you have a code i can try ?
<korvo> closet5: I'm still investigating. So far, I've found that it also happens with ParseError, so it's a problem with how lines and columns are being computed. I've also found that it can happen in the bootstrap parser (the thing which compiles our PEGs to RPython classes during translation) so it's some structural issue with how characters are counted.
<korvo> If *you* have questions for *me* about how to use rlib.parsing then please ask them! I'll try my best to answer.
<closet5> thanks. i'm still running my parser in python3 so i won't rewrite it to rlib now, but are there examples on how to use rlib.parsing ?
<closet5> (once i get to using it i plan to document what i can find, just in case)
<korvo> https://rpython.readthedocs.io/en/latest/rlib.html#parsing has part of a JSON parser. https://gist.github.com/MostAwesomeDude/9aad072ad32d990fff73f7128d221cbc is a recent toy I wrote; the parser recognizes a Smalltalk-like block language.
<korvo> vixenc.py, lines 10-17, are how to make a parser and AST transformer. MakeAST is called on line 282 at runtime, after parsing.
<korvo> This was adapted from rlib.parsing.main FWIW.
<closet5> thanks
BarrensZeppelin has joined #pypy
<closet5> i found this on HN about uv and pypy: https://news.ycombinator.com/item?id=47293415
<closet5> (tldr: people are saying pypy is unmaintained)
BarrensZeppelin has quit [Remote host closed the connection]
<LarstiQ> unmaintained is a little harsh, but more people pitching in would be nice
<LarstiQ> I see that post has already been replied to by devs
<korvo> closet5: Don't worry, it's standard FUD from the CPython community. This is an evergreen complaint; for example, here's the same silliness from 2yrs ago: https://lobste.rs/s/m55u77/pypy_has_been_quietly_working_for_me_for#c_cy6gxb
<korvo> It's in the sibling comment there, and also in https://lobste.rs/s/ijxsix/pypy_v7_3_17_release by the same commentor. It's something of a pattern.
nexussfan has joined #pypy
lritter has quit [Quit: Leaving]
mvdschaaf has joined #pypy
<cfbolz> uv showing a warning to people installing pypy is a bit of an escalation though
<cfbolz> but I think the fundamental critique is correct: we don't have enough people to catch up with cpython, version wise (despite BarrensZeppelin's excellent recent PRs)
BarrensZeppelin has joined #pypy
Dejan has joined #pypy
BarrensZeppelin has quit [Quit: BarrensZeppelin]
Dejan has quit [Quit: Leaving]
nexussfan has quit [Ping timeout: 248 seconds]