Re: [pypy-dev] pypy specific code flags DONT_IMPLY_DEDENT and SOURCE_IS_UTF8

2019-12-16 Thread Rocky Bernstein
Thanks - got it. Many thanks for the clarification. I reread and missed the part where you mentioned that those two flags are conflicts in CPython as well. I am sorry for my confusion there. (I'll ask CPython folks what's up if there is need). On Mon, Dec 16, 2019 at 6:05 AM Armin Rigo wrote:

Re: [pypy-dev] pypy specific code flags DONT_IMPLY_DEDENT and SOURCE_IS_UTF8

2019-12-16 Thread Armin Rigo
Hi Rocky, On Mon, 16 Dec 2019 at 11:57, Rocky Bernstein wrote: > > I did a little test, and for this program: > > # from 3.7 test_asyncgen.py > def test_async_gen_iteration_01(self): > async def gen(): > await awaitable() > a = yield 123 > > the 3.6 ASYNC_GENERATOR flag is ad

Re: [pypy-dev] pypy specific code flags DONT_IMPLY_DEDENT and SOURCE_IS_UTF8

2019-12-16 Thread Rocky Bernstein
I did a little test, and for this program: # from 3.7 test_asyncgen.py def test_async_gen_iteration_01(self): async def gen(): await awaitable() a = yield 123 the 3.6 ASYNC_GENERATOR flag is added in the code object created for "gen()" as 3.6 does. So I infer that flag 0x200

Re: [pypy-dev] pypy specific code flags DONT_IMPLY_DEDENT and SOURCE_IS_UTF8

2019-12-16 Thread Armin Rigo
Hi, On Mon, 16 Dec 2019 at 11:24, Rocky Bernstein wrote: > I have a cross-version Python bytecode disassembler xdis > (https://pypi.org/project/xdis/) and I notice that flags 0x0100 and 0x0200 > (DONT_IMPLY_DEDENT and SOURCE_IS_UTF8 respectively) conflict in Pypy 3.6 with > Python 3.6's ITERA