-
Notifications
You must be signed in to change notification settings - Fork 317
Release 2022-03 follow-up #1085
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
Comments
audit trail:
b1 (2022-08-07)
interlude Python-3.11.0rc1 (2022-08-09)
b2 (2022-08-16)
b3 (2022-09-18)
b4 (2022-10-16)
b5 (2022-10-23)
rc (2022-10-31) postponed:
|
While the UC Irvine LFD site hasn't been taken down yet, the site has already been archived and it seems like Gohlke has stopped compiling new wheels. For example, MKL wheels are not available for Numpy 1.23, which was released 3 days before the last update of the LFD site, or for Numpy 1.23.1. I suppose even he didn't build every release of Numpy against MKL though. Intel's own builds are obviously even further behind (wheels for CPython 3.10 aren't even available yet). |
Could you add binaries for Python 3.9.13? |
There is no resources nor interest nor environmental benefit to maintain & update old cpython-3.x versions. |
Has anyone tried to contact @cgohlke to know the status? |
He announced on that site a month or two ago that UC Irvine LFD lost funding, so the site would be shutting down before July. |
I see. Too bad. I hope he shares his building scripts so it might be replicated. |
Hummm, looking at an Intel site, it seems that "pip install mkl" may offer a path forward: "pip install mkl numpy" |
Counting MKL casualties ... at first look, it seems that:
So:
|
b1 (2022-08-06/0x) Changes from WinPython 2022-02:
Areas of particular interest for testers: Next build effort:
|
@stonebig , Does it mean you were able to overcome the MKL issues? |
Winpython64-3.10.6.1b1.exe of today is made with intel MKL standard wheel. |
@stonebig , I will test it. |
on "current" cpython, it shall remain timely. The problem is for PyPy or un-final-released cpython-3.11 |
interlude (2022-08-09): Python-3.11.0rc1 (following python-3.11.0rc1 development cycle) The Winpython-3.11.0.0 versions follows the cycle of Python-3.11.0 (alphas, betas, release_candidates). Apparently:
The 3.11.0.1 will actually be "for true release" and follow the normal scheme Changes from Python-3.11.0b4 :
Areas of particular interest for testers:
Next build effort:
download is at: WinPython 3.11.0.0The following packages are included in WinPython-64bit v3.11.0.0 rc1. Tools
Python packages
|
b2 (2022-08-15: infrastructure modernization) Changes from WinPython 2022-03 b1:
Areas of particular interest for testers:
Next build effort:
WinPython 3.10.6.1The following packages are included in WinPython-64bit v3.10.6.1 b2.
### Tools
Python packages
|
@stonebig , When you say Could you share the links to those wheels? |
No, the hope is that the standard wheel of numpy see and choose the mkl. The mkl itself is a shared dll |
@stonebig , I think it won't. I think one must build NumPy / SciPy in a way that utilize MKL. |
Humm, maybe you're right, https://www.intel.com/content/www/us/en/developer/articles/tool/oneapi-standalone-components.html#python or I don't know how to check mkl is used per numpy |
so the possible link is this one, https://pypi.org/project/intel-numpy/#files If the mkl is unusable in current python without cgohlke , mkl will go away to make room for alternatives. winpython 2022-03b1 python 3.10 winpython 2022-03b1 python 3.11 (so we notice cgohlke was recompiling intel_numpy) |
This is Intel NumPy, They recompile it with MKL. It seems your path is just add the MKL DLL's not a recompiled NumPy? What I'm saying is that I'm not sure just adding the DLL is enough without recompilation. What do you think? |
interesting thread here scipy/scipy#11812 and so mkl/numpy/scipy shall come from the same nest.... like cgohlke's lost one. |
Yea, This is similar to LibTrampoline project at Julia. The question if this was implemented. It doesn't seem so. |
As I see numpy contributors in 'PyPy' and 'https://data-apis.org/array-api/latest/", I suppose:
These people are very busy making their Mac M1 & M2 working at maximum speed, so the 'MKL' thing can be percieved as 'passé'. The constant move to 'latest' remains the strategy to:
'MKL' is becoming a numpy's legacy, otherwise it would be simpler to use it in official python-3.10/numpy |
Where did you get the notion it becomes a legacy? There is no alternative, yet at least, to MKL on the What about replicating @cgohlke recipes to build NumPy and SciPy? |
'pip intel-numpy' is not available for python-3.10, from the company which shall be the most motivated to feed it to you. |
It is because their distribution isn't popular. So maybe using the package from Conda is the solution here? |
Maybe in the long run, this might help: https://www.nsf.gov/awardsearch/showAward?AWD_ID=2209877. |
Will be done by july 2025, not exactly tomorrow..... |
I wrote in the long run :-). |
No There is no fun nor interest nor strategy that would motivate such a move/burden. It can only be done and sustained per a way bigger organization. |
I don't need to recreate all the recipes he created, Only NumPy and SciPy. |
There is a new contender lfortran that smells interesting, to replace intel fortran: |
It is a compiler, It won't make OpenBLAS faster than MKL. In MKL the kernels are written in assembly. The magic isn't the Intel compiler, it is the kernels. |
That is something only Christoph Gohlke, or Intel or Microsoft, can carry on with the required care, and forward-looking care in case of Christoph. |
What about out of the box idea? It is a single file to start with, so all the scripts will be much easier around it. |
it's indeed a possible path. Even if it's done per frenchies, I'm a bit unsettled per the server domain https://micro.mamba.pm |
What do you mean by:
|
pm = St Pierre & Miquelon |
the demise of https://www.lfd.uci.edu/~gohlke/pythonlibs/ and also indirectly the fall-of-the-tree of intel are problems. |
b3 (2022-09-18: Python updates) Changes from WinPython 2022-03 b1:
Areas of particular interest for testers:
Next build effort: rc
WinPython 3.10.7.0The following packages are included in WinPython-64bit v3.10.7.0 b3. Tools
Python packages
WinPython 3.11.0.0The following packages are included in WinPython-64bit v3.11.0.0 rc2. Tools
Python packages
|
Do I understand correctly that WinPython-64bit v3.10.7.0 b3 uses pip to install numpy and scipy from the following links? If so, why does WinPython-64bit v3.10.7.0 b3 contain scipy v1.9.0? scipy v1.9.1 was released 2022-August-26. |
well, it's a miss |
b4 (2022-10-16: Python updates) Changes from WinPython 2022-03 b3
Areas of particular interest for testers:
Next build effort: rc
WinPython 3.10.8.0 b4The following packages are included in WinPython-64bit v3.10.8.0 b4.
### Tools
Python packages
|
I don't see why you add |
I had a doubt. Did you experiment a bit with mamba ? |
Yes. It worked like It seems you'll be able to create a portable distribution around it much easier. |
b5 (2022-10-23: python-3.10.8 IDLE fix, python-3.11 preparation) Changes from WinPython 2022-03 b4
Areas of particular interest for testers:
Next build effort: rc
WinPython 3.10.8.0The following packages are included in WinPython-64bit v3.10.8.0 b5. Tools
Python packages
WinPython 3.11.0.1The following packages are included in WinPython-64bit v3.11.0.1 b5. Tools
Python packages
|
Hello, it is possible to upgrade the python version of WinPython or do I have to reinstall it again? Sorry, if it not the right space, but I couldn't find any information about this topic. |
Installing/unzipping a new version is the suggested method. |
rc (2022-10-30: ) Changes from WinPython 2022-03 b5
Areas of particular interest for testers:
rc binaries will be re-tagged as final in a few days if no major issue is discovered. Next build effort:
WinPython 3.10.8.0The following packages are included in WinPython-64bit v3.10.8.0 . Tools
Python packages
History of changes for WinPython-64bit 3.10.8.0The following changes were made to WinPython-64bit distribution since version 3.10.5.0. Python packagesNew packages:
Upgraded packages:
Removed packages:
WinPython 3.11.0.1The following packages are included in WinPython-64bit v3.11.0.1 . Tools
Python packages
|
post-rc remarks:
|
Maybe a good strategy would be waiting to Python 3.11.1. It will give time to the eco system to mature and have better compatibility. |
hummm, dask-jupyterlab-bug is not related to the message, so rc is final
WinPython 3.10.8.0The following packages are included in WinPython-64bit v3.10.8.0 . Tools
Python packages
History of changes for WinPython-64bit 3.10.8.0The following changes were made to WinPython-64bit distribution since version 3.10.5.0. Python packagesNew packages:
Upgraded packages:
Removed packages:
WinPython 3.11.0.1The following packages are included in WinPython-64bit v3.11.0.1 . Tools
Python packages
|
In the particular case of Winpython:
|
release: october 2022
Wanted:
Focus:
Postpone:
Hopes/Wishes for 2022/2023:
The text was updated successfully, but these errors were encountered: