gmane.comp.python.pypy archive

413 archived articles, newest first (page 1 of 5). Latest articles →

Re: RFC: experimenting with using claude to drive the rpython python3 port and python parity
Thu, 20 Aug 2026 04:13:28 +0300
matti picus via pypy-dev <[email protected]> • #16777
Re: RFC: experimenting with using claude to drive the rpython python3 port and python parity
Wed, 19 Aug 2026 20:30:29 +0200
"Yury V. Zaytsev" <[email protected]> • #16776
RFC: experimenting with using claude to drive the rpython python3 port and python parity
Wed, 19 Aug 2026 15:47:48 +0200
Ronny Pfannschmidt <[email protected]> • #16775
Re: A new build-summary.pypy.org service and benchmark runner benchmarker2
Mon, 01 Jun 2026 13:53:07 +0200
Jacob Hallén <[email protected]> • #16774
A new build-summary.pypy.org service and benchmark runner benchmarker2
Mon, 1 Jun 2026 09:40:48 +0300
matti picus via pypy-dev <[email protected]> • #16773
PyPy 7.3.23 release
Wed, 27 May 2026 10:34:20 +0300
matti picus via pypy-dev <[email protected]> • #16772
PyPy v7.3.22 is out
Tue, 28 Apr 2026 17:31:18 +0300
matti picus via pypy-dev <[email protected]> • #16771
Re: PyPy v7.3.21 has been released
Thu, 19 Mar 2026 16:25:07 +0100
Simon Cross via pypy-dev <[email protected]> • #16770
PyPy v7.3.21 has been released
Fri, 13 Mar 2026 12:52:42 +0200
matti picus via pypy-dev <[email protected]> • #16769
Interest in helping out.
Wed, 11 Mar 2026 02:46:06 +0000
chris ivanov via pypy-dev <[email protected]> • #16768
Re: I want to further develop the project as it's last update from 2017
Mon, 12 Jan 2026 02:03:33 +0600
Umor faruk suptoo via pypy-dev <[email protected]> • #16767
Re: I want to further develop the project as it's last update from 2017
Mon, 12 Jan 2026 06:54:29 +1100
matti picus via pypy-dev <[email protected]> • #16766
I want to further develop the project as it's last update from 2017
Sun, 11 Jan 2026 17:43:18 +0600
Umor faruk suptoo via pypy-dev <[email protected]> • #16765
Re: RPython page on PyPI with wrong link
Fri, 17 Oct 2025 09:45:46 +0300
matti picus via pypy-dev <[email protected]> • #16764
RPython page on PyPI with wrong link
Fri, 17 Oct 2025 01:17:08 +0000
Felipe Maia via pypy-dev <[email protected]> • #16763
Re: Faster PyPy build
Thu, 11 Sep 2025 07:39:38 +0200
Maciej Fijalkowski via pypy-dev <[email protected]> • #16762
Re: regex is much slower in pypy than cpython
Wed, 03 Sep 2025 06:15:40 +0200
Michał Górny <[email protected]> • #16761
Re: regex is much slower in pypy than cpython
Wed, 3 Sep 2025 07:23:06 +0300
matti picus via pypy-dev <[email protected]> • #16760
regex is much slower in pypy than cpython
Wed, 3 Sep 2025 10:16:52 +0800
Li Li via pypy-dev <[email protected]> • #16759
Faster PyPy build
Mon, 21 Jul 2025 15:31:31 +0200 (CEST)
PIERRE AUGIER via pypy-dev <[email protected]> • #16758
Re: PyPy v7.3.20 was released
Sat, 5 Jul 2025 00:25:34 +0200
Simon Cross via pypy-dev <[email protected]> • #16757
PyPy v7.3.20 was released
Fri, 4 Jul 2025 17:29:46 +0300
matti picus via pypy-dev <[email protected]> • #16756
Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Fri, 6 Jun 2025 13:28:06 +0300
matti picus via pypy-dev <[email protected]> • #16755
Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Fri, 6 Jun 2025 11:39:24 +0200 (CEST)
PIERRE AUGIER via pypy-dev <[email protected]> • #16754
Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Thu, 5 Jun 2025 09:53:42 +0200
CF Bolz-Tereick via pypy-dev <[email protected]> • #16753
Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Wed, 4 Jun 2025 01:44:05 +0200 (CEST)
PIERRE AUGIER via pypy-dev <[email protected]> • #16752
Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Sun, 18 May 2025 13:28:44 +0200
Marcus Harnisch <[email protected]> • #16751
Re: Better compatibility of the Python scientific/data stack with fast Python interpreters
Thu, 15 May 2025 15:41:52 +0200 (CEST)
PIERRE AUGIER via NumPy-Discussion <[email protected]> • #16750
Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Wed, 07 May 2025 11:55:43 -0000
Techran CO via pypy-dev <[email protected]> • #16749
Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Tue, 6 May 2025 14:23:13 +0200
CF Bolz-Tereick via pypy-dev <[email protected]> • #16748
Re: Question about ref counting and non-movable objects
Mon, 5 May 2025 23:03:11 +0200
Simon Cross via hpy-dev <[email protected]> • #16747
Question about ref counting and non-movable objects
Mon, 5 May 2025 17:57:33 +0200 (CEST)
PIERRE AUGIER via hpy-dev <[email protected]> • #16746
Re: [pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Mon, 5 May 2025 15:32:19 +0200 (CEST)
PIERRE AUGIER via hpy-dev <[email protected]> • #16745
Re: [pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Fri, 2 May 2025 11:05:51 +0300
matti picus via hpy-dev <[email protected]> • #16744
Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters
Wed, 30 Apr 2025 14:24:09 +0200
Michał Górny <[email protected]> • #16743
Re: [Numpy-discussion] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters
Wed, 30 Apr 2025 14:08:36 +0200 (CEST)
PIERRE AUGIER <[email protected]> • #16742
Re: Better compatibility of the Python scientific/data stack with fast Python interpreters
Wed, 30 Apr 2025 07:32:44 +0200
Ralf Gommers via NumPy-Discussion <[email protected]> • #16741
Better compatibility of the Python scientific/data stack with fast Python interpreters
Tue, 29 Apr 2025 11:20:28 +0200 (CEST)
PIERRE AUGIER <[email protected]> • #16740
Re: FYI: question related to HPy on discuss.python.org
Mon, 28 Apr 2025 14:35:38 +0200 (CEST)
PIERRE AUGIER <[email protected]> • #16739
Re: Are the stdlib test.regrtest supposed to pass?
Wed, 12 Mar 2025 23:44:44 -0000
Liam Ellison via pypy-dev <[email protected]> • #16738
Re: Are the stdlib test.regrtest supposed to pass?
Tue, 4 Mar 2025 19:34:41 +0100
"Yury V. Zaytsev" <[email protected]> • #16737
Re: Are the stdlib test.regrtest supposed to pass?
Tue, 04 Mar 2025 17:40:00 -0000
Jamima Tariqa via pypy-dev <[email protected]> • #16736
Re: Are the stdlib test.regrtest supposed to pass?
Fri, 28 Feb 2025 05:32:43 +0200
Matti Picus via pypy-dev <[email protected]> • #16735
Re: Are the stdlib test.regrtest supposed to pass?
Thu, 27 Feb 2025 12:05:59 +0100
Michał Górny <[email protected]> • #16734
Are the stdlib test.regrtest supposed to pass?
Thu, 27 Feb 2025 12:00:49 +0100
Miro Hrončok <[email protected]> • #16733
Bug fix release of v7.3.19
Wed, 26 Feb 2025 14:24:30 +0200
matti picus via pypy-dev <[email protected]> • #16732
Release of v7.3.18 with python2.7, 3.10, 3.11
Thu, 6 Feb 2025 22:02:28 +1100
Matti Picus via pypy-dev <[email protected]> • #16731
Re: Users of PyPy2.7 ?
Mon, 18 Nov 2024 17:58:32 +0200
matti picus via pypy-dev <[email protected]> • #16730
Free-threading and PyPy ?
Mon, 18 Nov 2024 16:37:54 +0100 (CET)
PIERRE AUGIER <[email protected]> • #16729
Users of PyPy2.7 ?
Mon, 18 Nov 2024 16:22:34 +0100 (CET)
PIERRE AUGIER <[email protected]> • #16728
Re: Minor Bug Report for PyPy
Thu, 07 Nov 2024 16:23:10 +0100
CF Bolz-Tereick via pypy-dev <[email protected]> • #16727
Minor Bug Report for PyPy
Thu, 7 Nov 2024 15:24:31 +0100
Denil Bouafia via pypy-dev <[email protected]> • #16726
[Python-announce] Python Security Survey - Your Expertise Needed!
Sun, 13 Oct 2024 05:44:13 +0000
Reem Mutairy via Python-announce-list <[email protected]> • #16725
Re: issue with portable python pypy in alpine linux 3.20.3
Wed, 9 Oct 2024 09:28:48 +0200
CF Bolz-Tereick via pypy-dev <[email protected]> • #16724
Re: issue with portable python pypy in alpine linux 3.20.3
Wed, 9 Oct 2024 16:07:33 +0900
Dima Tisnek via pypy-dev <[email protected]> • #16723
issue with portable python pypy in alpine linux 3.20.3
Tue, 8 Oct 2024 15:08:24 +0000
"Ophir, Avishay via pypy-dev" <[email protected]> • #16722
Re: Help me understand why PyPy is so slow in my benchmark
Mon, 23 Sep 2024 15:35:35 -0400
Jeremy Brown <[email protected]> • #16721
Re: Help me understand why PyPy is so slow in my benchmark
Fri, 20 Sep 2024 11:33:30 +0200
CF Bolz-Tereick via pypy-dev <[email protected]> • #16720
Re: Help me understand why PyPy is so slow in my benchmark
Fri, 20 Sep 2024 11:26:04 +0200
CF Bolz-Tereick via pypy-dev <[email protected]> • #16719
Re: Help me understand why PyPy is so slow in my benchmark
Thu, 19 Sep 2024 22:16:32 -0400
Jeremy Brown <[email protected]> • #16718
Re: Help me understand why PyPy is so slow in my benchmark
Wed, 18 Sep 2024 23:30:59 +0200
Armin Rigo via pypy-dev <[email protected]> • #16717
Re: Help me understand why PyPy is so slow in my benchmark
Wed, 18 Sep 2024 23:04:55 +0200
CF Bolz-Tereick via pypy-dev <[email protected]> • #16716
Re: Help me understand why PyPy is so slow in my benchmark
Wed, 18 Sep 2024 21:32:59 +0200
Manuel Jacob <[email protected]> • #16715
Help me understand why PyPy is so slow in my benchmark
Tue, 17 Sep 2024 23:43:06 -0400
Jeremy Brown <[email protected]> • #16714
Operating system package...
Wed, 4 Sep 2024 21:52:32 -0400
"[email protected]" <[email protected]> • #16713
Re: How to test code that uses weakrefs
Wed, 4 Sep 2024 15:37:52 +0200
Christian Tismer-Sperling <[email protected]> • #16712
Re: How to test code that uses weakrefs
Mon, 02 Sep 2024 16:02:55 -0000
[email protected] • #16711
How to test code that uses weakrefs
Mon, 2 Sep 2024 16:43:56 +0900
Dima Tisnek <[email protected]> • #16710
Release of PyPy7.3.17
Thu, 29 Aug 2024 11:50:16 +0300
matti picus <[email protected]> • #16709
Re: Contribute a RISC-V 64 JIT backend
Sun, 11 Aug 2024 21:22:18 -0700
Logan Chien <[email protected]> • #16708
Re: Windows zip file for pypy3.10-v7.3.16 is not completed
Wed, 24 Apr 2024 14:35:36 +0800
yanglei <[email protected]> • #16707
Re: Windows zip file for pypy3.10-v7.3.16 is not completed
Wed, 24 Apr 2024 15:56:29 +1000
Matti Picus <[email protected]> • #16706
Re: Windows zip file for pypy3.10-v7.3.16 is not completed
Wed, 24 Apr 2024 13:30:35 +0800
yanglei <[email protected]> • #16705
Re: Windows zip file for pypy3.10-v7.3.16 is not completed
Wed, 24 Apr 2024 14:57:22 +1000
Matti Picus <[email protected]> • #16704
Windows zip file for pypy3.10-v7.3.16 is not completed
Wed, 24 Apr 2024 12:20:55 +0800
yanglei <[email protected]> • #16703
Release of pypy 7.3.16
Wed, 24 Apr 2024 08:45:11 +1000
Matti Picus <[email protected]> • #16702
Re: Contribute a RISC-V 64 JIT backend
Fri, 1 Mar 2024 11:52:39 -0800
Logan Chien <[email protected]> • #16701
Re: Contribute a RISC-V 64 JIT backend
Thu, 29 Feb 2024 13:44:28 +0100
Armin Rigo <[email protected]> • #16700
Re: Contribute a RISC-V 64 JIT backend
Wed, 28 Feb 2024 23:34:40 -0800
Logan Chien <[email protected]> • #16699
Fwd:
Mon, 26 Feb 2024 16:35:17 +0000
Emre Yıldırım <[email protected]> • #16698
Re: Contribute a RISC-V 64 JIT backend
Wed, 21 Feb 2024 21:57:56 -0800
Logan Chien <[email protected]> • #16697
Re: Contribute a RISC-V 64 JIT backend
Tue, 20 Feb 2024 07:05:15 +0100
Armin Rigo <[email protected]> • #16696
Re: Contribute a RISC-V 64 JIT backend
Mon, 19 Feb 2024 20:08:22 -0800
Logan Chien <[email protected]> • #16695
Re: Contribute a RISC-V 64 JIT backend
Mon, 19 Feb 2024 08:06:09 +0100
Armin Rigo <[email protected]> • #16694
Re: Contribute a RISC-V 64 JIT backend
Sun, 18 Feb 2024 20:02:42 -0800
Logan Chien <[email protected]> • #16693
Re: Contribute a RISC-V 64 JIT backend
Fri, 16 Feb 2024 10:38:06 +0100
Armin Rigo <[email protected]> • #16692
Re: Contribute a RISC-V 64 JIT backend
Thu, 15 Feb 2024 22:45:24 -0800
Logan Chien <[email protected]> • #16691
Re: Contribute a RISC-V 64 JIT backend
Mon, 29 Jan 2024 18:51:15 -0800
Logan Chien <[email protected]> • #16690
Re: Contribute a RISC-V 64 JIT backend
Mon, 29 Jan 2024 09:36:37 +0100
CF Bolz-Tereick via pypy-dev <[email protected]> • #16689
Re: Contribute a RISC-V 64 JIT backend
Mon, 29 Jan 2024 09:27:58 +0100
CF Bolz-Tereick via pypy-dev <[email protected]> • #16688
Re: Contribute a RISC-V 64 JIT backend
Sun, 28 Jan 2024 19:26:46 -0800
Logan Chien <[email protected]> • #16687
Re: Contribute a RISC-V 64 JIT backend
Mon, 22 Jan 2024 22:19:35 -0800
Logan Chien <[email protected]> • #16686
Re: Contribute a RISC-V 64 JIT backend
Mon, 22 Jan 2024 08:36:38 +0200
Maciej Fijalkowski <[email protected]> • #16685
Re: Contribute a RISC-V 64 JIT backend
Tue, 16 Jan 2024 18:32:48 -0800
Logan Chien <[email protected]> • #16684
Re: Contribute a RISC-V 64 JIT backend
Tue, 16 Jan 2024 10:50:16 +0200
Matti Picus <[email protected]> • #16683
Re: Contribute a RISC-V 64 JIT backend
Mon, 15 Jan 2024 21:02:37 -0800
Logan Chien <[email protected]> • #16682
Re: Contribute a RISC-V 64 JIT backend
Mon, 15 Jan 2024 20:54:06 -0800
Logan Chien <[email protected]> • #16681
Release v7.3.15 of PyPy
Mon, 15 Jan 2024 08:50:12 +0200
Matti Picus <[email protected]> • #16680
Re: Contribute a RISC-V 64 JIT backend
Thu, 11 Jan 2024 12:44:39 +0200
Maciej Fijalkowski <[email protected]> • #16679
Re: Contribute a RISC-V 64 JIT backend
Tue, 9 Jan 2024 22:39:17 -0800
Logan Chien <[email protected]> • #16678
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.