home.social

#pypy3 — Public Fediverse posts

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

fetched live
  1. Hmmm… ASCII-art Mandelbrot sets. I forgot `pypy`'s build system generates those during builds.

    #Python #pypy3

  2. Hmmm… ASCII-art Mandelbrot sets. I forgot `pypy`'s build system generates those during builds.

    #Python #pypy3

  3. With CPython now actively merging "AI" slop in the form of co-authored commits from Anthropic Claude… I'm leery about starting new projects atop the reference #Python implementation.

    My projects remain slop-free at this point in time, and it is my intention that they stay that way. I can't afford the legal risk that comes with them: a machine cannot represent itself in court, therefore a machine cannot be held accountable for infractions of copyright law. This means the buck stops with the humans.

    Cursory glance at Pypy, it is compatible with Python 3.11 and, on the surface, does not show any co-authored commits. I've used it in the past and found it to be mostly compatible.

    Is it good enough for a fork? Did I miss something?

    github.com/pypy/pypy

    #Pypy #Pypy3 #NoAI

  4. With CPython now actively merging "AI" slop in the form of co-authored commits from Anthropic Claude… I'm leery about starting new projects atop the reference #Python implementation.

    My projects remain slop-free at this point in time, and it is my intention that they stay that way. I can't afford the legal risk that comes with them: a machine cannot represent itself in court, therefore a machine cannot be held accountable for infractions of copyright law. This means the buck stops with the humans.

    Cursory glance at Pypy, it is compatible with Python 3.11 and, on the surface, does not show any co-authored commits. I've used it in the past and found it to be mostly compatible.

    Is it good enough for a fork? Did I miss something?

    github.com/pypy/pypy

    #Pypy #Pypy3 #NoAI

  5. Wrzuciłem dzisiaj nową weresję #PyPy3.10 do #Gentoo, która poprawia, ekhm, "iterację po współprogramach przy pomocy API rozszerzeń C". Albo, mówiąc prościej, naprawia rozszerzenie yajl2_c w paczce ijson.

    Chciałbym z całego serca podziękować rtobar za włożenie wielkiego wysiłku, by rozkminić ten problem, naprawić PyPy i przy okazji poprawić kilka innych problemów po stronie ijson. Naprawdę taką współpracę chciałbym widywać codziennie!

    github.com/ICRAR/ijson/issues/
    foss.heptapod.net/pypy/pypy/-/

    #Python

  6. I've pushed a new #PyPy3.10 build to #Gentoo today with a fix for, err, "iterating over coroutines in C extension API". Or, to put it simpler, it fixes problems with yajl2_c extension in ijson.

    I'd like to wholeheartedly thank rtobar for going above and beyond the call of duty, figuring out where the problem is, fixing PyPy and making a bunch of fixes to ijson as well. This is really awesome kind of interaction I'd love to see every day!

    github.com/ICRAR/ijson/issues/
    foss.heptapod.net/pypy/pypy/-/

    #Python

  7. I've pushed a new #PyPy3.10 build to #Gentoo today with a fix for, err, "iterating over coroutines in C extension API". Or, to put it simpler, it fixes problems with yajl2_c extension in ijson.

    I'd like to wholeheartedly thank rtobar for going above and beyond the call of duty, figuring out where the problem is, fixing PyPy and making a bunch of fixes to ijson as well. This is really awesome kind of interaction I'd love to see every day!

    github.com/ICRAR/ijson/issues/
    foss.heptapod.net/pypy/pypy/-/

    #Python