Re: [pypy-dev] How to organize the py3k branch
Hi Amaury,
On 13/10/11 16:37, Amaury Forgeot d'Arc wrote:
All these changes occur in strings that start with
app = gateway.applevel('''
NOT_RPYTHON
This code is not RPython, and is processed by the new compiler.
Normally, the host python should not see this code.
Anyway, I run cpython2.6 for my tests, which does not
allow this new metaclass syntax.
I agree that RPython should stay at version 2.x for the near future.
For example, space.wrap(hello) takes a 8bit string and produces a W_Unicode...
Thanks for looking at all this!
that's true, but from the commits I saw it seems that you are destroying
support for the Python 2 interpreter anyway. Is it correct?
I renew my suggestion of having a meeting where to decide which strategy to
follow.
Who would like to participate at the meeting?
ciao,
Anto
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] How to organize the py3k branch
Hi, 2011/10/14 Antonio Cuni anto.c...@gmail.com that's true, but from the commits I saw it seems that you are destroying support for the Python 2 interpreter anyway. Is it correct? Yes, that's true. It seemed to me that supporting both versions in the same files would be too much of a hassle. I'd prefer regularly merge branches, conflicts should be limited since the 2.7 version won't grow new Python features. But we could revisit this, I just would like to avoid tons of #ifdef around the changes... I renew my suggestion of having a meeting where to decide which strategy to follow. Unfortunately I'm travelling early this afternoon, and I'm not sure to have a connection during the week-end. It will be easier next week, for example around 17:00 CEST. -- Amaury Forgeot d'Arc ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] How to organize the py3k branch (was: [pypy-commit] pypy py3k: Remove print statement)
Hi Amaury, r47983 be8493f31b60 py3k | amauryfa | 2011-10-12 22:19 +0200 pypy/module/sys/system.py pypy/module/sys/version.py pypy/module/sys/vm.py Fix some metaclasses, and the sys module can now be imported Please wait a second before doing all these changes. You are changing the RPython code to be Python 3. Doing so is Yet Another option that we never really discussed so far: moving RPython to be RPython 3. I suppose that, by now, we should really consider this as another possible option too; but we must definitely consider what it implies. It seems to imply changing the whole of PyPy (including the whole translation toolchain) to be Python 3. But we cannot drop the Python 2 version. So it seems to me that we'll end up with two versions of the whole translation toolchain (and I'll leave you the merging pains). That sounds bad. A bientôt, Armin. ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] How to organize the py3k branch (was: [pypy-commit] pypy py3k: Remove print statement)
2011/10/13 Armin Rigo ar...@tunes.org:
r47983 be8493f31b60 py3k | amauryfa | 2011-10-12 22:19 +0200
pypy/module/sys/system.py
pypy/module/sys/version.py
pypy/module/sys/vm.py
Fix some metaclasses, and the sys module can now be imported
Please wait a second before doing all these changes. You are changing
the RPython code to be Python 3. Doing so is Yet Another option that
we never really discussed so far: moving RPython to be RPython 3. I
suppose that, by now, we should really consider this as another
possible option too; but we must definitely consider what it implies.
All these changes occur in strings that start with
app = gateway.applevel('''
NOT_RPYTHON
This code is not RPython, and is processed by the new compiler.
Normally, the host python should not see this code.
Anyway, I run cpython2.6 for my tests, which does not
allow this new metaclass syntax.
I agree that RPython should stay at version 2.x for the near future.
For example, space.wrap(hello) takes a 8bit string and produces a W_Unicode...
Thanks for looking at all this!
--
Amaury Forgeot d'Arc
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] How to organize the py3k branch (was: [pypy-commit] pypy py3k: Remove print statement)
Hi Amaury,
On Thu, Oct 13, 2011 at 16:37, Amaury Forgeot d'Arc amaur...@gmail.com wrote:
All these changes occur in strings that start with
app = gateway.applevel('''
Oups! Indeed. Sorry, I mistook that.
A bientôt,
Armin.
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
