[Spyce-users] Re: spyceconf.py

[John R. <joh...@gm...>]

Also,
> path +=3D os.environ['SPYCE_PATH'].split(';')
should probably be=20
path +=3D os.environ['SPYCE_PATH'].split(os.path.pathsep)
... no UNIX user would expect to have to put semicolon in a search path.

2005/5/19, John Reese <joh...@gm...>:
> I'm not wild about the new python configuration file.  Used to be, I
> could have a two-line conf file, containing only the one thing that I
> didn't want to be defaulted.  Now as far as I can tell I need to have
> about 41 lines of code, of which most will be defaults and one or two
> will be my own changes, which I'll have to comment and whatnot.
>=20
> It seems less clean, and all that logic in there will be disturbed if
> there's an upgrade that needs to change how sys.path is built, or
> supplement globaltags or something.
>=20
> I suppose one solution would be to do an import * from baseSpyceConf
> in the user spyceconf.py and override a few things.  But the direct
> sys.path modifications would have to be undone.  Maybe instead of
> changing sys.path directory in spyceconf.py, you could have users make
> a variable called syspath, and then do a sys.path.extend(syspath)
> after reading in the spyceconf.py module?
>=20
> I'm probably not being very clear.  Let me know and I'll buckle down
> and make sense.
>