[IronPython] Setting Recursion Limit On Embedded PythonEngine

[Michael Foord]

Dino Viehland wrote:
> Yep, this another is one of those spots where the engine isolation falls down :(.  Unfortunately this one is currently by design.  SystemState not being a real module was done to better support multiple engines as well.  We probably won't fix that in v1.x but maybe in v2.x it could become a normal module.
>
>   
Ok :-)

Thanks for the quick reply.

Michael
> -----Original Message-----
> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Michael Foord
> Sent: Thursday, April 05, 2007 2:47 PM
> To: Discussion of IronPython
> Subject: [IronPython] Setting Recursion Limit On Embedded PythonEngine
>
> Hello all,
>
> Setting the recursion limit on an embedded PythonEngine also affects the
> current engine. (We were hoping that using an embedded engine would
> shield our main environment from our users doing daft things like this
> in their code).
>
>  >>> from IronPython.Hosting import PythonEngine
>  >>>
>  >>> e = PythonEngine()
>  >>> e.Sys.getrecursionlimit()
> 2147483647
>  >>> e.Sys.setrecursionlimit(2)
>  >>> import sys
>  >>> sys.getrecursionlimit()
> 2
>  >>> e.Sys.getrecursionlimit()
> 2
>
> By the way - the 'sys' module is a 'SystemState' object, which isn't in
> the API documentation (at least not in 1.0.1).
>
> We had to dig into the sources (which wasn't such a bad thing) to learn
> about it.
>
> Thanks
>
> Michael Foord
> http://www.voidspace.org.uk/ironpython/index.shtml
> _______________________________________________
> users mailing list
> users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
> _______________________________________________
> users mailing list
> users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
>