[EMAIL PROTECTED] Thu, Nov 18, 2004 at 12:07:01PM +0100]
> Author: arigo
> Date: Thu Nov 18 12:07:01 2004
> New Revision: 7364
>
> [... wrestling commits with appspace-modules ... ]
>
> Directly testing the class 'complex' buried in __builtin__module.py is funny,
> beacuse it's difficult to import this __builtin__module.py directly into
> CPython. Well, it's not impossible, given sufficiently obscure hacks. Yadda
> yadda boum. Committing applevel_in_cpython.py for that purpose, i.e.: testing
> directly in CPython some of the app-level code written in the
> module/*module.py files.
>
> That's obviously a wrong solution. We need something more like splitting the
> module/*module.py into several files (e.g. class complex:...) and most of them
> could just be imported in CPython too.
Such modules should probably be allowed to be a directory which can have
multiple files, all of which will be put into module's namespace.
This should also make it easier to test them from CPython ...
holger
_______________________________________________
[EMAIL PROTECTED]
http://codespeak.net/mailman/listinfo/pypy-dev
