[pypy-dev] Use of marshal in the sandbox: is stdlib marshal OK?

Maciej Fijalkowski fijall at gmail.com
Thu Dec 29 17:00:04 CET 2011


On Thu, Dec 29, 2011 at 2:36 PM, Ned Batchelder <ned at nedbatchelder.com> wrote:
> On 12/28/2011 11:49 AM, Armin Rigo wrote:
>>
>> Hi Ned,
>>
>> On Wed, Dec 28, 2011 at 15:34, Ned Batchelder<ned at nedbatchelder.com>
>>  wrote:
>>>
>>> The problem with "bundling pypy's marshal.py" is that it pulls in a lot
>>> of
>>> infrastructure modules, which bulks up the calling process.
>>
>> Unsure what you mean.  It seems to me that lib_pypy/marshal.py just
>> imports lib_pypy/_marshal.py, which itself doesn't import any
>> non-standard Python module.
>
> True, but we use py to import it, why is that?  Perhaps I'm barking up the
> wrong tree trying to reduce the size of the pypy source tree I need
> alongside my sandbox.
>

No, it's actually good to keep sandbox relatively separate from the pypy tree.


More information about the pypy-dev mailing list