I created a Python 3 port of UXP out of boredom...

[Moonchild]

That odd powershell.exe message is one I haven't been seeing on my system and for whatever reason haven't been able to reproduce. The reason it's particularly odd is that I don't recall ever adding anything powershell-related or touching any files that mention it.

Just a thought but maybe it invokes powershell because it uses file associations and it gets invoked that way? Might be a python for Windows oddity, and may need to configuration of python itself to avoid?

[__Sandra__]

This is what warning about powershell looks like. It appears almost immediately and in the future, it does not seem to affect the project build process in any way.

powershell.png

And another question, I don’t know how much it relates inconsequentially to the topic. I'm building a project with the arch:AVX option. When compiling some files, there are many override warnings, for example cl: command line warning D9025: override \"/arch:AVX\" to \"/arch:SSE2\". Where a file is compiled whose name mentions optimization for SSE2, this is understandable (for example, sse_optimized.cpp, nsTextFragmentSSE2.cpp). But there are also overrides “in the other direction” (cl: command line warning D9025: override \"/arch:SSE2\" to \"/arch:AVX\""). How normal is this situation?

[plumsh]

Does this Python 3 port include any code from this port?

[athenian200]

Does this Python 3 port include any code from this port?

Actually, wound up not needing to use anything from that one. Partially because everything was just shared as a single, monolithic diff across the entire codebase and I couldn't make heads or tails of it, plus I had already started working on my port before that one was ready. I did, however, get snippets of code from Copilot as I went... but I was making one change at a time and rebuilding to see where it failed (outside of where I used 2to3 of course, but that was a normal code replacement script rather than AI), validating behavior the same way I always did when applying and fixing up patches from Bugzilla and other sources to match our codebase.

So it's really kind of a combination here... there were parts where I used 2to3 and traditional code replacement scripts, parts where I referenced Bugzilla, parts where I just learned how Python 3 worked and applied the same mechanical fixes to the same class of problem so often it became easy, and parts that used a snippet of code from Stack Overflow or Copilot applied to our codebase.