Jason R. Coombs

Sorry for the delay. Been busy. Will test this soon.

I'm sad to report that the behavior is still undesirable when running out of the box: ``` .venv/Scripts/python -m pip install git+https://github.com/blink1073/dnspython@windows-ctypes Collecting git+https://github.com/blink1073/dnspython@windows-ctypes Cloning https://github.com/blink1073/dnspython (to revision windows-ctypes) to...

> @jaraco were you able to confirm that using `set_config_method` addresses the undesirable behavior? I only got as far as confirming that using `set_config_method` has the intended effect on the...

I'd like to make the case that ruff should not be relying on declared configuration and should instead rely on the [core metadata](https://packaging.python.org/en/latest/specifications/core-metadata/#requires-python) for the package. Although `pyproject.toml` is a...

> workarounds like `extend = "pyproject.toml"` I recently learned that this workaround isn't as elegant as I'd originally expected (see jaraco/skeleton#155). While it does work for skeleton-based projects, the addition...

It occurs to me that one possible workaround might be to simply reset `COMSPEC` in my xonsh profile. No, that doesn't work, because `make_default_aliases` will already have been run and...

Another workaround could be to remove those aliases or replace them with something that will work.

The overriding of COMSPEC also affects launching of `.cmd` files. ``` ~ 🐚 ls ~/scoop/shims/scoop* scoop scoop.cmd scoop.ps1 ~ 🐚 scoop --help xonsh: /c: No such file or directory. ```...

> Otherwise, have you tried this setting for example, instead of changing COMSPEC?: Changing that setting doesn't set a default shell for Windows. It only sets a default profile (shell)...

PR #5779 submitted with one possible solution. In reviewing, I did find that `SystemRoot` is preferable to `WINDIR`, the former being more canonical since Windows NT. Another possible approach could...