![]() As I mentioned the source code for Python 3.9.5 actually seems to say that at least at one point compiling under 7 was OK. While I do not expect developers to bend over backwards for compatibility, I do sorely object to them apparently going out of their way to sabotage older platforms. Redmond may have decided that Win7 is obsolete, but I and many others have not. Win allows me more freedom in making scripts as I prefer to have 'security' issues as a last concern. I have a Debian Buster install on the same machine, but also like to have my updated scripting languages on the Win platform. Is there a hack, or a FAQ for getting by this nonsensical booby-trap? Someone did a hack of api-ms-win-core-path-l1-1-0.dll for Blender, but did not include the function Python wanted. I tried converting the install exe to msi and used orca to blank out the requirements part, but no luck. The source code seems to say that Win7 is OK for now, but wont compile without api-ms-win-core-path-l1-1-0.dll. V3.9x depends on api-ms-win-core-path-l1-1-0.dll for apparently no good reason other than to prevent Win7 usage. And has never had a problem because of that. This machine has *never* been updated, as I avoid M$ as much as possible. The problem is that some propellorheads decided that because Win7 is no longer 'supported' by M$, is that it is somehow a 'risk'! ![]() I am *not* going to update this macjhine to Win10, and Win8.1 is garbage also. On my Debian Install I loaded v3.9 in /opt and all worked out fne.
0 Comments
Leave a Reply. |