This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author joshtriplett
Recipients joshtriplett
Date 2011-05-15.23:49:41
SpamBayes Score 1.646714e-08
Marked as misclassified No
Message-id <1305503381.77.0.166373977.issue12083@psf.upfronthosting.co.za>
In-reply-to
Content
PEP 304 provides a runtime option to avoid saving generating bytecode files.  However, for embedded usage, it would help to have a compile-time option to remove all the file-writing code entirely, hardcoding PYTHONBYTECODEBASE="".  I ran into this when porting Python to an embedded platform, which will never support any form of filesystem write operations; currently, I have to provide dummy functions for writing files, which error out when attempting to write to anything other than stdout or stderr.
History
Date User Action Args
2011-05-15 23:49:41joshtriplettsetrecipients: + joshtriplett
2011-05-15 23:49:41joshtriplettsetmessageid: <1305503381.77.0.166373977.issue12083@psf.upfronthosting.co.za>
2011-05-15 23:49:41joshtriplettlinkissue12083 messages
2011-05-15 23:49:41joshtriplettcreate