Maciej Fijalkowski wrote: > Hello, > > The thing is pypy's taint code is broken. Basically you don't only > need to patch all places that return pyobject, but also all places > that might modify anything. (All side effects) For example innocently > looking call to addition might end up calling arbitrary python code > (and have arbitrary side effects). There is a question how do you > approach such things?
Taint isn't an easy problem, but PyPy is still a *much* better platform for that kind of experimentation than CPython. RPython, objects spaces, the code generation, etc all give you much more powerful tools to play with than the raw C code of the reference interpreter. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
