Swapping in the @$ operator to force resolution of the actual conda
entry point means that subprocess doesn't swallow stdout and
stderr. And given that this is already a xsh-based xontrib, it seems
reasonable that it would use xonsh syntax for this.
Should address #11
@scopatz, @asmeurer -- if either of you can try this out and confirm that it fixes your issue that would be great. Thanks!
Swapping in the
@$
operator to force resolution of the actualconda
entry point means thatsubprocess
doesn't swallowstdout
andstderr
. And given that this is already axsh
-based xontrib, it seems reasonable that it would use xonsh syntax for this.Should address #11
@scopatz, @asmeurer -- if either of you can try this out and confirm that it fixes your issue that would be great. Thanks!