Installer/target architecture mismatch
An odd suggestion/request here, hope it's the right place to discuss it. So I was trying to install python on the Xbox series S (yup..), so far I got the embedded x86_64 version for windows to work, however, I was unable to get packages to install properly. I'm not familiar enough with Windows to know how the installation is supposed to be laid out, but I figured it might be just a side affect from using the embedded version. Now I need to mention that the Xbox is an odd NT based system, it can run win32/UWP apps, but it comes with a strict requirement of x86_64 and therefore has no SysWoW64 to support i386. Naturally, I tried to use the distributed installer, and that's when I found out that the x86_64 installer itself was in fact compiled for i386. I can compile a one-off build for myself and go on with my life, but I also realized it's an oversight because the installer should never assume the target system has backwards compatibility for older architectures and stick to the target architecture throughout the installation phase. I know It's an extreme edge case, but I guess it's valid and make sense. Let me know what you think, and how (or if) I should proceed from here. DanyL.
participants (2)
-
Dany Lisiansky -
Guido van Rossum