Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

> > > https://refi64.com/posts/the-magic-of-rpython.html > > Note that this was written back when I used "like" and "really" in every > sentence, and when I used to think that Python copied tuples (don't ask). > Thanks! And thanks for making the RPython language a bit more explicit for the

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

> Message-ID: <20180206034013.gz26...@ando.pearwood.info> > > On Sat, Feb 03, 2018 at 11:45:15AM +0100, asrp wrote: > > > > Can you give an example of how you would do that? I don't mean the > > > mechanism used, I mean how would a developer implement a new syntactic > > > feature. Suppose I

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On Tue, Feb 6, 2018 at 3:40 AM, Steven D'Aprano wrote: > On Sat, Feb 03, 2018 at 11:45:15AM +0100, asrp wrote: > > ​[...] > > Here's a faked session showing the sort of thing I am referring to. > (Note that this is just an example, not a proposal for a new language >

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

https://refi64.com/posts/the-magic-of-rpython.html Note that this was written back when I used "like" and "really" in every sentence, and when I used to think that Python copied tuples (don't ask). On Feb 3, 2018 at 10:05 AM, > wrote: > Are you aware of pypy? > Yes, but I do not know it

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On Sat, Feb 03, 2018 at 11:45:15AM +0100, asrp wrote: > > Can you give an example of how you would do that? I don't mean the > > mechanism used, I mean how would a developer implement a new syntactic > > feature. Suppose I wanted to add a new clause to for...else, let's say: > > > > for ...

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

Oh and I forgot to mention that since everything is mostly done at run time, there could just be different modules for (slightly) different languages. I don't know if that'd be problematic for maintenance though. asrp > Sent: Saturday, February 03, 2018 at 3:17 PM > From: asrp

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

> Are you aware of pypy? > Yes, but I do not know it well. It seems to be more focused on JIT compiling with many of its functions written for special cases and I did not find a way to make experimental changes easily. I even tried (briefly) to have the main loop of this interpreter run in

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

Hi, (My other reply to Alex and Steven doesn't seems to appear, at least not on pipermail so I hope these don't come in the wrong order.) > In the readme to python_terp you say: > > """ > python_terp is intended to make language modification to Python easier > to preview changes more quickly

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

Hi user with no real name yet, On 03.02.18 01:01, asrp asrp wrote: > Hello, > > I don't know if this is the right place to post this. Please redirect as > needed. > > I've made a small Python interpreter in Python with runtime AST node > semantics and edit-and-continue. I thought it could

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On 03.02.18 08:12, Steven D'Aprano wrote: > On Sat, Feb 03, 2018 at 12:50:11AM -0500, Terry Reedy wrote: >> On 2/2/2018 7:01 PM, asrp asrp wrote: >>> I don't know if this is the right place to post this. Please redirect as >>> needed. >> >> This list is for development *of* cpython. Development

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On Sat, Feb 03, 2018 at 01:01:30AM +0100, asrp asrp wrote: > I've made a small Python interpreter in Python with runtime AST node > semantics and edit-and-continue. I thought it could make prototyping > language changes more easily and visualize usage before writing them > in C. That sounds

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On Sat, Feb 03, 2018 at 12:50:11AM -0500, Terry Reedy wrote: > On 2/2/2018 7:01 PM, asrp asrp wrote: > >I don't know if this is the right place to post this. Please redirect as > >needed. > > This list is for development *of* cpython. Development *with* python in > general belongs on

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

On 2/2/2018 7:01 PM, asrp asrp wrote: I don't know if this is the right place to post this. Please redirect as needed. This list is for development *of* cpython. Development *with* python in general belongs on python-list. -- Terry Jan Reedy

Re: [Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

Are you aware of pypy? > -Original Message- > From: Python-Dev [mailto:python-dev-bounces+tritium- > list=sdamon@python.org] On Behalf Of asrp asrp > Sent: Friday, February 2, 2018 7:02 PM > To: python-dev@python.org > Subject: [Python-Dev] A minimal Python interpreter written in

[Python-Dev] A minimal Python interpreter written in Python for experimenting with language changes

Hello, I don't know if this is the right place to post this. Please redirect as needed. I've made a small Python interpreter in Python with runtime AST node semantics and edit-and-continue. I thought it could make prototyping language changes more easily and visualize usage before writing them