Thanks for the feedback, everyone. I'm satisfied that the bytecodes are
stable enough to work for my purpose. Now I just have to find time to work
on it around my schoolwork.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an ema
06.04.20 06:48, Jonathan Goble пише:
My question is, are the opcodes guaranteed stable across the lifetime of
a single 3.x release? In other words, are they guaranteed to not change
values or semantics between 3.x.y and 3.x.(y+1)? Reading through the
list of opcodes in the dis documentation, it
On Mon, 6 Apr 2020, 06:30 Brandt Bucher, wrote:
> > The best way to look at this is to consider how long a .pyc file is
> valid. They're currently named something like
> __pycache__/modulename.cpython-38.pyc which is a fairly clear indication
> that the cached compiled module should be valid for
> The best way to look at this is to consider how long a .pyc file is valid.
> They're currently named something like __pycache__/modulename.cpython-38.pyc
> which is a fairly clear indication that the cached compiled module should be
> valid for any CPython 3.8.x release.
Perhaps an even bette
On Mon, Apr 6, 2020 at 12:02 AM Chris Angelico wrote:
> On Mon, Apr 6, 2020 at 1:53 PM Jonathan Goble wrote:
> >
> > I'm getting ready to get back into an old personal project with some new
> ideas. Before I do, I need to ask a question regarding the stability of
> CPython bytecode. Before you s
On Mon, Apr 6, 2020 at 1:53 PM Jonathan Goble wrote:
>
> I'm getting ready to get back into an old personal project with some new
> ideas. Before I do, I need to ask a question regarding the stability of
> CPython bytecode. Before you say it, I am well aware and fully understand
> that the opco
