[IronPython] Temp directory for IronPython?

[Jim Hugunin]

It's just a bug that these go in the current directory.  The site.dll file should be placed in the same directory as site.py as it is the logical equivalent of site.pyc.  I don't know how hard this will be to implement.

The snippets.dll file has no reason to be written to disk.  This is only done for purposes of debugging the IronPython code generator.  We should just not generate this file unless started in a debugInternals kind of mode.

We'll look into both of these for the next release if they're easy and a little further in the future if they turn out to be hard.

Thanks - Jim 

________________________________________
From: users-ironpython.com-bounces at lists.ironpython.com [mailto:users-ironpython.com-bounces at lists.ironpython.com] On Behalf Of Keith J. Farmer
Sent: Tuesday, May 03, 2005 11:45 PM
To: Discussion of IronPython
Subject: [IronPython] Temp directory for IronPython?

I'm noticing as I use IronPython that my disk is getting littered with site.* and snippets.* files.  I realize this allows for different sets of snippets, but could a more centralized cache be used?

IronPython/Cache/<FilePathHash>/

.. or the like

.....

Gave up on trying to use the global environment variable settings to manage my PATH variable, and have migrated toward user-level.  Disappointing story there, but something more directly addressable by the OS development teams.