Thanks to everyone who has tried to help me with this problem. I will = try to make a command line option for this. The .py files in question belong to the user and I don't have any = control over where they are; and I don't know about them ahead of time so I = cannot precompile them. The user wrote the files so all I know is that someone = is trying to import something. Each of the hundreds or thousands of Pythons reads the same Python program. However, since we are using a parallel processor and the problems will run for minutes if not months, the cost = of any imports does not matter.=20 It is interesting that the other set of people who care about this are = doing little embedded stuff, sort of the exact opposite end of the computing spectrum. Paul > -----Original Message----- > From: guido@odiug.zope.com [mailto:guido@odiug.zope.com] On=20 > Behalf Of Guido van Rossum > Sent: Friday, January 10, 2003 10:37 AM > To: Aahz > Cc: Paul F Dubois; python-dev@python.org > Subject: Re: [Python-Dev] Parallel pyc construction >=20 >=20 > > Why not make the .py directory read-only? >=20 > Excellent suggestion for a work-around. >=20 > --Guido van Rossum (home page: http://www.python.org/~guido/) >=20
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4