the PyOxidizer target looks in the py2.txt file for requirements instead of py3

I didn't realize this was available on Windows. Is this stable enough that we could add it to the packaging, so that tweakdefaults is consistent across platforms? I just discovered the interface on Linux, and it is so much nicer than the default -i menu.

If this is purely from --config instead of a file and you're collecting metrics, would you want this to be an InputError? (I'm happy to queue this as-is, I just wanted to double check)

I decided to raise InputError here because the user should adapt

Queued to here, thanks

Queued, up to here, thanks.

Superseded by D9360

This seems like the right choice to me, confusing the local and remote revisions would be bad.

I accidentally interrupted phabsend with this series, so let me know if there are issue importing it. It looks like it's all here, and only that I don't have the URL embedded locally.

I haven't followed all of the sharesafe stuff, but should the nonsharedhgrc be folded into the hgrc when downgrading or unsharing? I don't see that, at least in the unshare code.

more test recording noise

more test recording noise

Queued to here, thanks

Queued, thanks

This causes problems on Windows (since python3 == python.exe)- for example, all test-check-* but one are skipped because hghave is failing, complaining python3 is missing. The only way I can think of to work around this is to use $PYTHON to run the scripts instead of directly executing them. Before I do that, is there some other simpler mechanism that I'm overlooking? I tried to add alias python3="py -3" to the script that gets generated when MSYSTEM is in the environment around run-tests.py:1760, but that didn't help (likely env doesn't know about it).