Re: [pypy-dev] Porting PyPy/rpython to Python 3

2015-04-17 Thread VanL
Hi Armin, I am not trying to force you (or anyone) to use Py3. I have been working on this in a private branch for a little bit, and I am happy to continue to do so. As I said earlier in the thread, I had gotten the impression that these changes would not make you or the other PyPy devs happy, so

Re: [pypy-dev] Porting PyPy/rpython to Python 3

2015-04-17 Thread Armin Rigo
Hi, I have kept quiet on this issue, but I'd like to mention that I'm not looking forward at all --but would accept it anyway if others deemed it a good idea-- to have to write all my code in all of "rpython/" in the restricted style of 2+3 mixed-mode code bases. This might create a source of fri

Re: [pypy-dev] Porting PyPy/rpython to Python 3

2015-04-17 Thread Ronan Lamy
Le 17/04/15 16:58, VanL a écrit : A question came up in the discussion of a pull request: What is the allowable scope? I propose pypy/ and rpython/ as those are fairly intertwined. Comments? You've stated that your goal is to allow the building of pypy[2|3] with pypy[2|3], but that requires s

Re: [pypy-dev] Can someone explain __extend__?

2015-04-17 Thread Maciej Fijalkowski
I suggest IRC for such questions Generally __extend__ extends an existing class (so just adds methods). __extend__(pairtype(...)) is an implementation of double-dispatch multimethods On Fri, Apr 17, 2015 at 6:58 PM, VanL wrote: > I am having some trouble wrapping my head around it. Reading throu

[pypy-dev] Can someone explain __extend__?

2015-04-17 Thread VanL
I am having some trouble wrapping my head around it. Reading through rpython/tools/pairtype.py, it looks like it could be one or more of a number of things: - An implementation of javascript-style prototypes. (The similarity: you don't subclass an object in js - you use the base object as a protot

Re: [pypy-dev] Porting PyPy/rpython to Python 3

2015-04-17 Thread Maciej Fijalkowski
rpython/ and pypy/ should not be intervined. In fact we're putting effort into making them two separate projects On Fri, Apr 17, 2015 at 5:58 PM, VanL wrote: > A question came up in the discussion of a pull request: What is the > allowable scope? I propose pypy/ and rpython/ as those are fairly >

Re: [pypy-dev] Porting PyPy/rpython to Python 3

2015-04-17 Thread Alex Gaynor
Where possible (e.g. syntax changes), I'd love to constrain the scope as much as possible. It's MUCH easier to review 100 20-line pull requests than it is to review a 2000-line PR. Alex On Fri, Apr 17, 2015 at 11:58 AM, VanL wrote: > A question came up in the discussion of a pull request: What

Re: [pypy-dev] Porting PyPy/rpython to Python 3

2015-04-17 Thread VanL
A question came up in the discussion of a pull request: What is the allowable scope? I propose pypy/ and rpython/ as those are fairly intertwined. Comments? ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev