PR: Fix redirection flag for micromamba (IPython console)

[mrclary]

Description of Changes

micromamba does not recognize the redirection flag --live-stream (--no-capture-output). However, its equivalent flag is --attach ""

Issue(s) Resolved

Fixes #22240

Affirmation

By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

[mrclary]

@ccordoba12, I was able to reproduce the error in #22240, and confirmed that this PR fixes it.

[ccordoba12]

Thanks @mrclary! Just some suggestions about comments for you.

[ccordoba12]

Thanks @mrclary!

[jhaskinsPhD]

Stumbled onto this after facing similar issues getting spyder to launch from inside a micromamba installation to find the pull request was merged last week. Is the updated fix available on the conda-forge channel yet for installation? I'm not familiar with installing dev versions from GitHub directly, but downgrading to v5.5.5 did not work for me.

[mrclary]

Stumbled onto this after facing similar issues getting spyder to launch from inside a micromamba installation to find the pull request was merged last week. Is the updated fix available on the conda-forge channel yet for installation? I'm not familiar with installing dev versions from GitHub directly, but downgrading to v5.5.5 did not work for me.

@jhaskinsPhD, this PR addresses an issue for our yet-to-be-released 6.0 version of Spyder being able to interact with external environments when the main conda executable is micromamba, and should not affect launching Spyder. If you are unable to launch Spyder from a micromamba environment, will you please open a new issue so that we can address your specific situation?

[jhaskinsPhD]

I should clarify...

I was able to launch the latest release of spyder downloaded via conda-forge this week from a new micromamba (v1.5.8) environment installed on a linux x64 machine, but I got the identical spyder kernels error that issue #22240 raised with the Ipython kernel not functioning/ being able to load and got here by googling around on the error. I initially tried downgrading to spyder v5.5.5 as suggested by the other users encountering the error, but that didn't work. Subsequently, I tried copying over your commits to see if they fixed my issues, but that made more errors since I didn't pull the other updates too & since this style of dev is pretty beyond my skill level, I stopped messing with it. So, I deleted that env, made a new one, and tried installing spyder v5.4.5 in that fresh env, which actually did address my spyder-kernels issue in the Ipython console since I last posted. So, I don't think this is a separate issue I was encountering, but if you think it is, I'm happy to raise a new issue and do a full description of my setup/issue.

I should also note, I was playing around with miniforge3 as well and actually encountered the same error trying to launch the most recent version of spyder in a new environment on that distribution, which makes me think its more of a spyder issue than a micromamba/miniforge3 issue.

[mrclary]

I should clarify...

@jhaskinsPhD, thanks for the clarification. While it may be similar to (or the same as) #22240, I think it will be best to open a new issue. I want to be sure to identify your problem explicitly with confusing your setup with anyone else's.