By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,583 Members | 1,770 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,583 IT Pros & Developers. It's quick & easy.

Resticted mode still active (error?)

P: n/a
I thought restricted mode had been removed from Python
but it seems to be active for Python 2.3.5 +.

I'm using the JEP product which allows integration
of Java with Python (see via
starting a Python interpreter in the same process as the
This integrates with python via the C interface, allowing
the user to 'eval' python code (amongst other features).

It seems that since Python 2.3.5 any threads (using the
threading module) created via code that has been
evaluated through the jep.eval() interface (i.e.Python C
interface )are executed in restricted mode and cannot,
for example, create files. Code that is just evaled (i.e not
in a subthread) thread has no restrictions.

The error reported is:
IOError: file() constructor not accessible in restricted

thread_id=1247793&forum_id=376782) - I've given a JEP
specific example here.

There seems to be a similar problem with mod_python

Reading through the release notes for Python 2.3.5
I see:
Bug #754449: threading.Thread will no longer mask
exceptions raised during interpreter shutdown with
another exception caused by attempting to output the
initial exception. This fix also includes a backport of rev.
1.41 from HEAD.

This might be the problem as it seems to involve the
porting of 2.4 threading code back to the 2.3 tree.

The error output is:
Exception in thread Thread-1:
Traceback (most recent call last):
File "C:\Python24\Lib\", line 442, in
File "<string>", line 5, in run
IOError: file() constructor not accessible in restricted

2.4.1c1 (#63, Mar 10 2005, 10:36:41) [MSC v.1310 32
bit (Intel)]
Creating file from main thread...
Creating file from sub thread...

Has anyone got any ideas about this?

Thanks in advance,
Jul 18 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Is there a script that causes this problem, without using mod_python or
jepp? If so, please attach it to the sourceforge bug.

Version: GnuPG v1.2.1 (GNU/Linux)


Jul 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.