New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python windows version installation #721
Comments
By the way we tried it in two different PCs with the same result. |
Hi @ZeusMarti : the answer is in the error message: you C compiler is too old. Unlike Matlab, python does not clearly states which are the compatible compilers for a given python version, it just says "You will still need the C compiler that was used to build Python; typically Microsoft Visual C++.", which depends on where your binary distribution of python was generated. I found some compatibility table here. Personally, I have no problem with Microsoft Visual Studio Community 2019 (including Microsoft Visual C++ 2019). Now this only concerns building from source. Installing from PyPI should not require a C compiler, so I would like to see the error you got using |
Thanks @lfarv , The Visual C++ version seems to be older than 14, I'm a bit confused, I just asked help to our IT section, will see. Indeed finally the remote installation |
What you highlight there is not the Visual C++ compiler itself, but the "Visual C++ Redistributable", which is (I think…) a set of libraries which need to be distributed for running apps compiled with Visual C++.
Good ! I have no way to experiment with binary distribution on Windows, but apparently you confirm that it works without needing a C++ compiler.
Excellent. Concerning the future development on AT, I expect a lot from the future meeting(s) of the "board", as advertised by Simon, to identify and prioritise the next evolutions. |
Hi all,
We have encountered problems installing AT in windows 10 for python versions above 3.9 (for equal or below works). We have tried both "pip install accelerator-toolbox" and locally "pip install .". You will find an screenshot below. Is it a known issue and we should stick to 3.9?
The text was updated successfully, but these errors were encountered: