I agree that the env vars and the .pth present a migration path -- and that's a
good thing I don't intend to disagree with.
Freezing of modules: funny you should mention that. I recall a somewhat
undermentioned feature of assemblies being composable from several seperate
files, referred to a
On 27/04/05, Keith J. Farmer <[EMAIL PROTECTED]> wrote:
> I'd set a user-level environment variable as well, checking that out, but it
> seemed a kludge at best. In a multi-user environment it'd be a hassle. For
> deployment to multiple machines, it'd be annoying at best.
Indeed. In that scena
on was my favorite language until C# came along. Maybe with
IronPython-omega with generics...)
From: [EMAIL PROTECTED] on behalf of Brian Dorsey
Sent: Wed 4/27/2005 1:23 PM
To: Discussion of IronPython
Subjec
On 27/04/05, Keith J. Farmer <[EMAIL PROTECTED]> wrote:
> I've switched to using a normal user account on my machine, and discovered I
> couldn't change the global IRONPYTHON_HOME variable I'd created (my path
> includes %IRONPYTHON_HOME% as a convenience thing)? So I switched to admin,
> chang
override with Environment Variables
From: [EMAIL PROTECTED] on behalf of Martin Maly
Sent: Wed 4/27/2005 10:20 AM
To: Discussion of IronPython
Subject: RE: [IronPython] Saving sys.path
There are, as far as I can see, three different ways to help in this case and I
am looking into
need for your
work, correct? We will try to get this update out even sooner than usual.
Martin
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer
Sent: Tuesday, April 26, 2005 4:02
PM
To: Discussion of IronPython
Subject: RE: [IronPython] Saving
sys.path
Perhaps (to at least keep the .NET way) a .config file instead of an
environment variable?
That file *could* specify one or more startup files, to maintain the Python
mystique.
From: [EMAIL PROTECTED] on behalf of Michael Spencer
Sent: Tue 4/26/2005 3:52 PM
To
