[gobolinux-users] $pythonpath

[Michael Homer]

On Nov 21, 2007 11:05 AM, Lucas C. Villa Real <lucasvr at gobolinux.org> wrote:
>
> On Nov 20, 2007 1:39 PM, Michael Homer <gobo-users-dufus at wotfun.com> wrote:
> > On Nov 21, 2007 3:34 AM, Daniele Maccari <gobo.users at gmail.com> wrote:
> > > I have a similar problem. Even if I export PYTHONPATH correctly Compile
> > > tells me it's not initialized as it should be.
> > >
> > > What could be the reason?
> > Are you running Compile under sudo? sudo clears the environment
> > variables before running the program, so either run Compile from a
> > root shell (and set the variable there), or run `sudo env
> > PYTHONPATH=$PYTHONPATH Compile ...`.
> >
> > I had the same problem when I was working on some Python recipes the
> > other day. We really should be shipping it in the environment files,
> > since the python build system or Compile seems to choke if it isn't
> > defined. Or Compile should be setting it automatically itself.
>
> Could you please add the following line to your $goboSettings/sudoers? :
>
> Defaults !env_reset, setenv
>
> This line is being included in the new version of the Sudo recipe /
> package and it was reported to fix that problem.
visudo: unknown defaults entry `setenv' referenced near line 9
Just "Defaults !env_reset" worked, and kept the environment variables
around. I am running a slightly old sudo, so if setenv is newer than
1.6.8 that would be the problem.
-Michael