Closed jpsmith5 closed 4 years ago
I don't think it's possible to affect the PATH after calling bashrc, and anyway, in strict mode we don't want to run that anyway.
So, strict mode now disables your .bashrc as you suggested (on dev). can you give another try?
Okay. Will try to test this out. Majority of my testing had been on local linux desktop in the office/lab, but will try to do something similar on Rivanna.
you can of course also run bulker on your local desktop...
I haven't figured out how to run it on windows yet...
When I had done brief efforts I was having issues getting it to be callable at the command line.
Could pip install but then it didn't see bulker as a callable command.
you're still using windows? ouch... :stuck_out_tongue_winking_eye:
https://www.howtogeek.com/413564/windows-10-is-getting-a-built-in-linux-kernel/
Cool. Hadn't come across this. Will go down the rabbit hole briefly.
Ok the new dev branch appears to solve this... I haven't tested extensively though.
I think this is fixed in 0.5.0. please re-open if you run into this problem again.
If a user's
.bashrc
file prepends or appends thePATH
envvar, this is carried over to bulker's path, even in--strict
mode. If--strict
is truly that, likely should not be calling.bashrc
, or maybe it should overwritePATH
only after calling.bashrc
.