uvcdat "executable" should unset env or it might be using the "Wrong" python

[doutriaux1]

~ (140) uvcdat --output=""
UVCDAT setup already sourced for this install location.

@jbeezley are you still in charge of setup_runtime or should I re-assign this to @aashish24 or @dlonie

[aashish24]

@doutriaux1 always assign to me first.. and then I can figure out who is the best person to work on this.

On the issue note, I am not sure what's the issue here? an you explain more? We cannot clear out the environement because we don't know what user has in it. Undoing just what we add is I think some work.

[durack1]

@doutriaux1 It would be good if the setup scripts checked for existing python/uvcdat paths, and removed other installations.. I agree this would be painful to do, but would also attempt to resolve issues with tangled paths causing users problems in which no coherent error message will easily be able to explain (and consequently the user complains to you about it not working).

[aashish24]

I am ok with someone else with better idea on how to do it take over -:) this task.

[doutriaux1]

i think all we need for now is to unsetenv UVCDAT_SETUP_PATH at the begining of the script, it will not fix all tangled issues but should help. I'll take a pass at it if @jbeezley doesn't have time unless @durack1 wants to do it.

[durack1]

I'm happy to test the *.csh version.. In my bug free, shellshock-unaffected, robust, safe and secure tcsh environment..

[aashish24]

@doutriaux1 I am not sure about the issue though. Let's say that you open a terminal and run the setup script and now you realized that you ran the wrong one. Why cannot we open another terminal and run the setup script from other location.

[durack1]

@aashish24 an issue to point out here is that many users (me) have statements which are automagically executed upon initializing a shell (so in my .cshrc).. If you assume that a user has a 'vanilla' environment with nothing but the system python on their path that's one thing, but many centers have default environment initializations that drop the standard /bin or similar in a users path.. Scrubbing these instances of python (and other executables, e.g. ncdump) is key I think.. And what can quickly make these setup scripts very complicated to write (and test).. As it would appear I'm the solo tcsh-er (with a relatively complicated environment config), I'd be happy to test anything you folks manage to tweak..

[doutriaux1]

@aashish24 @durack1 I have an idea about this, as soon as I get 30mn free i will push a fix that should satisfy everybody. And yes @durack1 is right users have absolutely insane .bashrc/.tcshrc files! Years and years of copying for other users and adding random bits to it!