Hi everyone, sorry if this is not the best place to ask the question, feel free to forward me to a better place for this kind of question :-) I was wondering PyPy 3.6 is supposed to run on WinXP SP3 32bit. Running the pypy3.exe says that it not a valid win32 app (but it runs fine on win7), like if it was a 64bit application only... The vc2015 dependency install fine on WinXP however there is no mention on PyPy website if it supposed to work... WinXP is actually still very common in industrial setups and it would be great if it would work with PyPy as CPython has drop WinXP support after 3.4. Cheers, Denis -- Denis Cardon Tranquil IT 12 avenue Jules Verne (Bat. A) 44230 Saint Sébastien sur Loire (FRANCE) tel : +33 (0) 240 975 755 http://www.tranquil.it Tranquil IT recrute! https://www.tranquil.it/nous-rejoindre/ Samba install wiki for Frenchies : https://dev.tranquil.it WAPT, software deployment made easy : https://wapt.fr
Hi Joseph, Le 05/28/2020 à 10:56 PM, Joseph Jenne via pypy-dev a écrit :
thanks for your answer. I completely agree that WinXP shouldn't be used in office setup anymore. However in industrial setups it is still a very common (perhaps the most common?) operating system. In this kind of industrial setup change of OS is very costly (you may need to change hardware, connectivity card, or even the whole CNC machine). Those system are obviously not connected to the internet... Actually seeing a MSDOS, a QNX or NT4 machine in factory is not that uncommon... With that in perspective WinXP seems modern :-) CPython>3.4 is not compatible with WinXP anymore, and as it is more reliant on C code and on recent VCRedist, I guess there is not much hope on this side. On the other hand PyPy is using vcredist2015 (which is still compatible with XP) and and is less reliant on C Code. So I was wondering if there is any reasons for PyPy3.6 not to work on XP? If you think it is just a compile time issue, I'll be happy try to rebuild it on WinXP. If it has some more tricky issues, I'd be willing to spend some time / money on this. The use case is for WAPT, a Software Deployment solution that use Python as its packaging scripting language. Cheers, Denis [1] https://www.wapt.fr/en/doc/
-- Denis Cardon Tranquil IT 12 avenue Jules Verne (Bat. A) 44230 Saint Sébastien sur Loire (FRANCE) tel : +33 (0) 240 975 755 http://www.tranquil.it Tranquil IT recrute! https://www.tranquil.it/nous-rejoindre/ Samba install wiki for Frenchies : https://dev.tranquil.it WAPT, software deployment made easy : https://wapt.fr
I don't have much experience with the windows side of pypy, especially on XP, but I would suggest trying to compile for your system, as I do not know of any reasons for incompatibility. That said, perhaps using a somewhat older version might be preferable, depending on the specifics of your use case On 5/29/20 1:44 AM, Denis Cardon wrote:
Hi, On Fri, 29 May 2020 at 20:10, Joseph Jenne via pypy-dev <pypy-dev@python.org> wrote:
Joseph, this sounds like very generic advise, of which Denis is likely aware. Denis, my offer to discuss things concretely on pypy-z@python.org still stand. We are not aware of any WinXP-specific issues because we have never tried to build PyPy there. Likely, it doesn't work out of the box. My guess is that we need to remove some WinAPI calls along with the corresponding Python-level functions, and we'd end up with a separate build that misses some functions (likely obscure and specific ones from the 'os' module, for example). Ideally we wouldn't rebuild ourselves every release but let you do it. Whatever the result, we wouldn't do it for free, but if it's only a matter of carefully removing a bit of functionality then it can probably be done at a reasonable price. If you want to give it a go yourself, you're welcome too, and we'd be happy to merge a branch which adds a translation flag to remove dependencies on non-WinXP functionality, for example. A bientôt, Armin.
Hi Denis, On Thu, 28 May 2020 at 18:05, Denis Cardon <dcardon@tranquil.it> wrote:
I see the point. If some parts of the industry want a modern version of Python but are otherwise stuck on WinXP, then it can be problematic for them. I am rather sure that no-one among the core developers will do it for free. I suppose that a contract job could be arranged if there is enough money, though. The correct place to discuss this is probably pypy-z@python.org . A bientôt, Armin.
Hi Joseph, Le 05/28/2020 à 10:56 PM, Joseph Jenne via pypy-dev a écrit :
thanks for your answer. I completely agree that WinXP shouldn't be used in office setup anymore. However in industrial setups it is still a very common (perhaps the most common?) operating system. In this kind of industrial setup change of OS is very costly (you may need to change hardware, connectivity card, or even the whole CNC machine). Those system are obviously not connected to the internet... Actually seeing a MSDOS, a QNX or NT4 machine in factory is not that uncommon... With that in perspective WinXP seems modern :-) CPython>3.4 is not compatible with WinXP anymore, and as it is more reliant on C code and on recent VCRedist, I guess there is not much hope on this side. On the other hand PyPy is using vcredist2015 (which is still compatible with XP) and and is less reliant on C Code. So I was wondering if there is any reasons for PyPy3.6 not to work on XP? If you think it is just a compile time issue, I'll be happy try to rebuild it on WinXP. If it has some more tricky issues, I'd be willing to spend some time / money on this. The use case is for WAPT, a Software Deployment solution that use Python as its packaging scripting language. Cheers, Denis [1] https://www.wapt.fr/en/doc/
-- Denis Cardon Tranquil IT 12 avenue Jules Verne (Bat. A) 44230 Saint Sébastien sur Loire (FRANCE) tel : +33 (0) 240 975 755 http://www.tranquil.it Tranquil IT recrute! https://www.tranquil.it/nous-rejoindre/ Samba install wiki for Frenchies : https://dev.tranquil.it WAPT, software deployment made easy : https://wapt.fr
I don't have much experience with the windows side of pypy, especially on XP, but I would suggest trying to compile for your system, as I do not know of any reasons for incompatibility. That said, perhaps using a somewhat older version might be preferable, depending on the specifics of your use case On 5/29/20 1:44 AM, Denis Cardon wrote:
Hi, On Fri, 29 May 2020 at 20:10, Joseph Jenne via pypy-dev <pypy-dev@python.org> wrote:
Joseph, this sounds like very generic advise, of which Denis is likely aware. Denis, my offer to discuss things concretely on pypy-z@python.org still stand. We are not aware of any WinXP-specific issues because we have never tried to build PyPy there. Likely, it doesn't work out of the box. My guess is that we need to remove some WinAPI calls along with the corresponding Python-level functions, and we'd end up with a separate build that misses some functions (likely obscure and specific ones from the 'os' module, for example). Ideally we wouldn't rebuild ourselves every release but let you do it. Whatever the result, we wouldn't do it for free, but if it's only a matter of carefully removing a bit of functionality then it can probably be done at a reasonable price. If you want to give it a go yourself, you're welcome too, and we'd be happy to merge a branch which adds a translation flag to remove dependencies on non-WinXP functionality, for example. A bientôt, Armin.
Hi Denis, On Thu, 28 May 2020 at 18:05, Denis Cardon <dcardon@tranquil.it> wrote:
I see the point. If some parts of the industry want a modern version of Python but are otherwise stuck on WinXP, then it can be problematic for them. I am rather sure that no-one among the core developers will do it for free. I suppose that a contract job could be arranged if there is enough money, though. The correct place to discuss this is probably pypy-z@python.org . A bientôt, Armin.
participants (3)
-
Armin Rigo -
Denis Cardon -
Joseph Jenne