home.social

#pypy — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pypy, aggregated by home.social.

  1. CW: Roleta do Unfollow

    Sou um caçador de bugs em Python, bom em fuçar código dos outros e achar problemas.

    Um dia, adotei uma ferramenta existente de achar bugs (#fusil), De outra vez, criei uma (#lafleur).

    Aí comecei a usar LLMs pra ajudar na caça aos bugs. Funcionou, daí criei plugins de caça aos bugs para usar com o Claude Code.

    Hoje faço e uso essas ferramentas de IA para achar centenas de bugs em projetos #Python e no #CPython, #PyPy, etc.

    Usuário e desenvolvedor de ferramentas de IA. Dscp.

  2. CW: Roleta do Unfollow

    Sou um caçador de bugs em Python, bom em fuçar código dos outros e achar problemas.

    Um dia, adotei uma ferramenta existente de achar bugs (#fusil), De outra vez, criei uma (#lafleur).

    Aí comecei a usar LLMs pra ajudar na caça aos bugs. Funcionou, daí criei plugins de caça aos bugs para usar com o Claude Code.

    Hoje faço e uso essas ferramentas de IA para achar centenas de bugs em projetos #Python e no #CPython, #PyPy, etc.

    Usuário e desenvolvedor de ferramentas de IA. Dscp.

  3. CW: Roleta do Unfollow

    Sou um caçador de bugs em Python, bom em fuçar código dos outros e achar problemas.

    Um dia, adotei uma ferramenta existente de achar bugs (#fusil), De outra vez, criei uma (#lafleur).

    Aí comecei a usar LLMs pra ajudar na caça aos bugs. Funcionou, daí criei plugins de caça aos bugs para usar com o Claude Code.

    Hoje faço e uso essas ferramentas de IA para achar centenas de bugs em projetos #Python e no #CPython, #PyPy, etc.

    Usuário e desenvolvedor de ferramentas de IA. Dscp.

  4. CW: Roleta do Unfollow

    Sou um caçador de bugs em Python, bom em fuçar código dos outros e achar problemas.

    Um dia, adotei uma ferramenta existente de achar bugs (#fusil), De outra vez, criei uma (#lafleur).

    Aí comecei a usar LLMs pra ajudar na caça aos bugs. Funcionou, daí criei plugins de caça aos bugs para usar com o Claude Code.

    Hoje faço e uso essas ferramentas de IA para achar centenas de bugs em projetos #Python e no #CPython, #PyPy, etc.

    Usuário e desenvolvedor de ferramentas de IA. Dscp.

  5. CW: Roleta do Unfollow

    Sou um caçador de bugs em Python, bom em fuçar código dos outros e achar problemas.

    Um dia, adotei uma ferramenta existente de achar bugs (#fusil), De outra vez, criei uma (#lafleur).

    Aí comecei a usar LLMs pra ajudar na caça aos bugs. Funcionou, daí criei plugins de caça aos bugs para usar com o Claude Code.

    Hoje faço e uso essas ferramentas de IA para achar centenas de bugs em projetos #Python e no #CPython, #PyPy, etc.

    Usuário e desenvolvedor de ferramentas de IA. Dscp.

  6. The music of Pypy (think π) shifted from punk flavored psychedelia to an upbeat and angular post-punk when they re-emerged in '24 after a 10-year break between albums.

    Find out more about their music at thepropagandasite.com/artist/p

    #music #musicdiscovery #tPsNewEntry #PyPy

  7. The music of Pypy (think π) shifted from punk flavored psychedelia to an upbeat and angular post-punk when they re-emerged in '24 after a 10-year break between albums.

    Find out more about their music at thepropagandasite.com/artist/p

    #music #musicdiscovery #tPsNewEntry #PyPy

  8. The music of Pypy (think π) shifted from punk flavored psychedelia to an upbeat and angular post-punk when they re-emerged in '24 after a 10-year break between albums.

    Find out more about their music at thepropagandasite.com/artist/p

    #music #musicdiscovery #tPsNewEntry #PyPy

  9. The music of Pypy (think π) shifted from punk flavored psychedelia to an upbeat and angular post-punk when they re-emerged in '24 after a 10-year break between albums.

    Find out more about their music at thepropagandasite.com/artist/p

    #music #musicdiscovery #tPsNewEntry #PyPy

  10. The music of Pypy (think π) shifted from punk flavored psychedelia to an upbeat and angular post-punk when they re-emerged in '24 after a 10-year break between albums.

    Find out more about their music at thepropagandasite.com/artist/p

    #music #musicdiscovery #tPsNewEntry #PyPy

  11. The next PyPy will be 8.0.0 and should add support for Python 3.12 and be the last to support 3.11, and require glibc 2.28 (AlmaLinux8, Amazon Linux 2023, Debian 10, Ubuntu 20.04).

    pypy.org/posts/2026/07/moving-

    #Python #PyPy

  12. The next PyPy will be 8.0.0 and should add support for Python 3.12 and be the last to support 3.11, and require glibc 2.28 (AlmaLinux8, Amazon Linux 2023, Debian 10, Ubuntu 20.04).

    pypy.org/posts/2026/07/moving-

    #Python #PyPy

  13. The next PyPy will be 8.0.0 and should add support for Python 3.12 and be the last to support 3.11, and require glibc 2.28 (AlmaLinux8, Amazon Linux 2023, Debian 10, Ubuntu 20.04).

    pypy.org/posts/2026/07/moving-

    #Python #PyPy

  14. The next PyPy will be 8.0.0 and should add support for Python 3.12 and be the last to support 3.11, and require glibc 2.28 (AlmaLinux8, Amazon Linux 2023, Debian 10, Ubuntu 20.04).

    pypy.org/posts/2026/07/moving-

    #Python #PyPy

  15. The next PyPy will be 8.0.0 and should add support for Python 3.12 and be the last to support 3.11, and require glibc 2.28 (AlmaLinux8, Amazon Linux 2023, Debian 10, Ubuntu 20.04).

    pypy.org/posts/2026/07/moving-

    #Python #PyPy

  16. If you've been wondering whether anyone's written a song from the POV of a single sock missing its pair, you're in luck, because our #SongoftheDay is "Lonely Striped Sock" by PyPy. A fun post-punk with bursts of noise.

    🎧 Listen at thepropagandasite.com

    #music #nowplaying #SOTD #tPsSotD #PyPy

  17. If you've been wondering whether anyone's written a song from the POV of a single sock missing its pair, you're in luck, because our #SongoftheDay is "Lonely Striped Sock" by PyPy. A fun post-punk with bursts of noise.

    🎧 Listen at thepropagandasite.com

    #music #nowplaying #SOTD #tPsSotD #PyPy

  18. If you've been wondering whether anyone's written a song from the POV of a single sock missing its pair, you're in luck, because our #SongoftheDay is "Lonely Striped Sock" by PyPy. A fun post-punk with bursts of noise.

    🎧 Listen at thepropagandasite.com

    #music #nowplaying #SOTD #tPsSotD #PyPy

  19. @schenklklopfer Huh, interesting.

    cPython 3.12.3:
    9475.86 MB/s

    PyPy (nightly, default settings):
    4378.93 MB/s

    PyPy (nightly, --jit off):
    3676.98 MB/s

    My guess: Most of the time is spent in bytes.find(), which is a highly optimized C function in #cPython already. The actual python overhead is so small that my parser even beats #rust (emmett-core) in this benchmark. #PyPy does not have much room for its #JIT to do anything, and seems to have a less optimized stdlib?

  20. @schenklklopfer Huh, interesting.

    cPython 3.12.3:
    9475.86 MB/s

    PyPy (nightly, default settings):
    4378.93 MB/s

    PyPy (nightly, --jit off):
    3676.98 MB/s

    My guess: Most of the time is spent in bytes.find(), which is a highly optimized C function in #cPython already. The actual python overhead is so small that my parser even beats #rust (emmett-core) in this benchmark. #PyPy does not have much room for its #JIT to do anything, and seems to have a less optimized stdlib?

  21. @schenklklopfer Huh, interesting.

    cPython 3.12.3:
    9475.86 MB/s

    PyPy (nightly, default settings):
    4378.93 MB/s

    PyPy (nightly, --jit off):
    3676.98 MB/s

    My guess: Most of the time is spent in bytes.find(), which is a highly optimized C function in #cPython already. The actual python overhead is so small that my parser even beats #rust (emmett-core) in this benchmark. #PyPy does not have much room for its #JIT to do anything, and seems to have a less optimized stdlib?

  22. @schenklklopfer Huh, interesting.

    cPython 3.12.3:
    9475.86 MB/s

    PyPy (nightly, default settings):
    4378.93 MB/s

    PyPy (nightly, --jit off):
    3676.98 MB/s

    My guess: Most of the time is spent in bytes.find(), which is a highly optimized C function in #cPython already. The actual python overhead is so small that my parser even beats #rust (emmett-core) in this benchmark. #PyPy does not have much room for its #JIT to do anything, and seems to have a less optimized stdlib?

  23. @schenklklopfer Huh, interesting.

    cPython 3.12.3:
    9475.86 MB/s

    PyPy (nightly, default settings):
    4378.93 MB/s

    PyPy (nightly, --jit off):
    3676.98 MB/s

    My guess: Most of the time is spent in bytes.find(), which is a highly optimized C function in #cPython already. The actual python overhead is so small that my parser even beats #rust (emmett-core) in this benchmark. #PyPy does not have much room for its #JIT to do anything, and seems to have a less optimized stdlib?

  24. I've been sad about the upcoming removal of #PyPy from #Gentoo, but given how many regressions I've been seeing recently in a variety of #Python packages, I'm eagerly waiting for the day when I'll remove the support and be able to stop having to deal with the test failures somehow. Not that at this point any other way of dealing besides skipping them makes any sense.

  25. I've been sad about the upcoming removal of #PyPy from #Gentoo, but given how many regressions I've been seeing recently in a variety of #Python packages, I'm eagerly waiting for the day when I'll remove the support and be able to stop having to deal with the test failures somehow. Not that at this point any other way of dealing besides skipping them makes any sense.

  26. I've been sad about the upcoming removal of #PyPy from #Gentoo, but given how many regressions I've been seeing recently in a variety of #Python packages, I'm eagerly waiting for the day when I'll remove the support and be able to stop having to deal with the test failures somehow. Not that at this point any other way of dealing besides skipping them makes any sense.

  27. I've been sad about the upcoming removal of #PyPy from #Gentoo, but given how many regressions I've been seeing recently in a variety of #Python packages, I'm eagerly waiting for the day when I'll remove the support and be able to stop having to deal with the test failures somehow. Not that at this point any other way of dealing besides skipping them makes any sense.

  28. I've been sad about the upcoming removal of #PyPy from #Gentoo, but given how many regressions I've been seeing recently in a variety of #Python packages, I'm eagerly waiting for the day when I'll remove the support and be able to stop having to deal with the test failures somehow. Not that at this point any other way of dealing besides skipping them makes any sense.

  29. There's been a noticeable increase in PyPy development activity in the last couple of months. Makes me very happy.

    A lot of that comes from new energy from @stanfromireland, the newest PyPY core developer. But it also seems @mattip and @cfbolz are more active too, and users seem to be filing more issues and even proposing more PRs.

    I can't explain this uptick in activity, any theories?

    #Python #PyPy

  30. There's been a noticeable increase in PyPy development activity in the last couple of months. Makes me very happy.

    A lot of that comes from new energy from @stanfromireland, the newest PyPY core developer. But it also seems @mattip and @cfbolz are more active too, and users seem to be filing more issues and even proposing more PRs.

    I can't explain this uptick in activity, any theories?

    #Python #PyPy

  31. There's been a noticeable increase in PyPy development activity in the last couple of months. Makes me very happy.

    A lot of that comes from new energy from @stanfromireland, the newest PyPY core developer. But it also seems @mattip and @cfbolz are more active too, and users seem to be filing more issues and even proposing more PRs.

    I can't explain this uptick in activity, any theories?

    #Python #PyPy

  32. There's been a noticeable increase in PyPy development activity in the last couple of months. Makes me very happy.

    A lot of that comes from new energy from @stanfromireland, the newest PyPY core developer. But it also seems @mattip and @cfbolz are more active too, and users seem to be filing more issues and even proposing more PRs.

    I can't explain this uptick in activity, any theories?

    #Python #PyPy

  33. There's been a noticeable increase in PyPy development activity in the last couple of months. Makes me very happy.

    A lot of that comes from new energy from @stanfromireland, the newest PyPY core developer. But it also seems @mattip and @cfbolz are more active too, and users seem to be filing more issues and even proposing more PRs.

    I can't explain this uptick in activity, any theories?

    #Python #PyPy

  34. #gentoo plans to switch from Python 3.13 to πthon 3.14 on 2026-06-01. gentoo.org/support/news-items/

    "Other πthon implementations
    ============================
    At the same time, we are also going to remove the target support for πthon 3.11 (πthon3_11) and ππ 3.11 (ππ3_11). Since there are
    no plans to release a πthon 3.12-compatible ππ version yet, Gentoo will be removing ππ support for the time being."
    :-(

    #PyPy

  35. #gentoo plans to switch from Python 3.13 to πthon 3.14 on 2026-06-01. gentoo.org/support/news-items/

    "Other πthon implementations
    ============================
    At the same time, we are also going to remove the target support for πthon 3.11 (πthon3_11) and ππ 3.11 (ππ3_11). Since there are
    no plans to release a πthon 3.12-compatible ππ version yet, Gentoo will be removing ππ support for the time being."
    :-(

    #PyPy

  36. #gentoo plans to switch from Python 3.13 to πthon 3.14 on 2026-06-01. gentoo.org/support/news-items/

    "Other πthon implementations
    ============================
    At the same time, we are also going to remove the target support for πthon 3.11 (πthon3_11) and ππ 3.11 (ππ3_11). Since there are
    no plans to release a πthon 3.12-compatible ππ version yet, Gentoo will be removing ππ support for the time being."
    :-(

    #PyPy

  37. #gentoo plans to switch from Python 3.13 to πthon 3.14 on 2026-06-01. gentoo.org/support/news-items/

    "Other πthon implementations
    ============================
    At the same time, we are also going to remove the target support for πthon 3.11 (πthon3_11) and ππ 3.11 (ππ3_11). Since there are
    no plans to release a πthon 3.12-compatible ππ version yet, Gentoo will be removing ππ support for the time being."
    :-(

    #PyPy

  38. PSA: The annual #Gentoo #Python switch planned for 2026-06-01. CPython 3.14 becomes the default, 3.11 and #PyPy 3.11 go out. The latter fills me with sadness but keeping it is unrealistic now that projects are aggressively pushing for 3.12+.

    Of course, we'll continue shipping the interpreters, so you can use venvs if you like. However, that's going to become harder to use since many projects either don't ship PyPy wheels or don't work on PyPy at all without patching.

    We will revisit PyPy support if a version compatible with Python 3.12 appears in reasonable time.

    public-inbox.gentoo.org/gentoo
    public-inbox.gentoo.org/gentoo

  39. PSA: The annual #Gentoo #Python switch planned for 2026-06-01. CPython 3.14 becomes the default, 3.11 and #PyPy 3.11 go out. The latter fills me with sadness but keeping it is unrealistic now that projects are aggressively pushing for 3.12+.

    Of course, we'll continue shipping the interpreters, so you can use venvs if you like. However, that's going to become harder to use since many projects either don't ship PyPy wheels or don't work on PyPy at all without patching.

    We will revisit PyPy support if a version compatible with Python 3.12 appears in reasonable time.

    public-inbox.gentoo.org/gentoo
    public-inbox.gentoo.org/gentoo

  40. PSA: The annual #Gentoo #Python switch planned for 2026-06-01. CPython 3.14 becomes the default, 3.11 and #PyPy 3.11 go out. The latter fills me with sadness but keeping it is unrealistic now that projects are aggressively pushing for 3.12+.

    Of course, we'll continue shipping the interpreters, so you can use venvs if you like. However, that's going to become harder to use since many projects either don't ship PyPy wheels or don't work on PyPy at all without patching.

    We will revisit PyPy support if a version compatible with Python 3.12 appears in reasonable time.

    public-inbox.gentoo.org/gentoo
    public-inbox.gentoo.org/gentoo

  41. PSA: The annual #Gentoo #Python switch planned for 2026-06-01. CPython 3.14 becomes the default, 3.11 and #PyPy 3.11 go out. The latter fills me with sadness but keeping it is unrealistic now that projects are aggressively pushing for 3.12+.

    Of course, we'll continue shipping the interpreters, so you can use venvs if you like. However, that's going to become harder to use since many projects either don't ship PyPy wheels or don't work on PyPy at all without patching.

    We will revisit PyPy support if a version compatible with Python 3.12 appears in reasonable time.

    public-inbox.gentoo.org/gentoo
    public-inbox.gentoo.org/gentoo

  42. PSA: The annual #Gentoo #Python switch planned for 2026-06-01. CPython 3.14 becomes the default, 3.11 and #PyPy 3.11 go out. The latter fills me with sadness but keeping it is unrealistic now that projects are aggressively pushing for 3.12+.

    Of course, we'll continue shipping the interpreters, so you can use venvs if you like. However, that's going to become harder to use since many projects either don't ship PyPy wheels or don't work on PyPy at all without patching.

    We will revisit PyPy support if a version compatible with Python 3.12 appears in reasonable time.

    public-inbox.gentoo.org/gentoo
    public-inbox.gentoo.org/gentoo

  43. I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.

    I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.

    #Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex

  44. I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.

    I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.

    #Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex

  45. I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.

    I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.

    #Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex

  46. I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.

    I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.

    #Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex

  47. I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.

    I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.

    #Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex