How can I avoid the traceback in xonsh scripts when using $RAISE_SUBPROC_ERROR = True?

[halloleo]

In a xonsh script like

$RAISE_SUBPROC_ERROR = True
cp nonexisting_file.txt other_name.txt
print("after the failure")

I do not get to the last line (print("after the failure")). Instead I get messagesubprocess.CalledProcessError: Command '['cp', 'nonexisting_file.txt', 'other_name.txt']' returned non-zero exit status 1.

That's great. Exactly what I want. 😄 However before the message I get the whole stack trace. How can I avoid this? I tried $XONSH_SHOW_TRACEBACK = False in the script, but that doesn't seem to help.

[xmnlab]

hi everyone! I have the same problem, I would love to know if there is a way to workaround this problem

[anki-code]

Here should be the fix (short traceback in case $XONSH_SHOW_TRACEBACK = False):

xonsh/xonsh/procs/pipelines.py

Lines 597 to 599 in eae3fcc

	if rtn is not None and rtn != 0 and XSH.env.get("RAISE_SUBPROC_ERROR"):
	try:
	raise subprocess.CalledProcessError(rtn, spec.args, output=self.output)

PR is welcome!

[xmnlab]

A PR is coming :) #5066
a review would be very appreciated. it is my first time contributing here .. so I am not super familiar with the code base yet

[anki-code]

Thanks and welcome! I already commented the PR )

[xmnlab]

this issue is already fixed on the master branch.
@anki-code do you have any idea about when a next release will be published?

[anki-code]

Usually release going quarterly but it depends on maintainers load.
You can install xonsh and use from master branch easily with pip or xpip:

xpip install -U git+https://github.com/xonsh/xonsh
# restart xonsh

[xmnlab]

thanks for the information!