-
Notifications
You must be signed in to change notification settings - Fork 317
release 2017-01 follow-up #468
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
NumPy 1.12.0 is available at http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy I plan on waiting until affected packages release again before I upgrade to NumPy 1.12.0. By the way, Numexpr 2.6.2 appears to already have updated for compatibility with NumPy 1.12.0. |
The rule-of-thumb on numpy is: don't upgrade until cgohlke upgraded the top of his front page. Currently he is still 1.11: "Many binaries depend on numpy-1.11+mkl " So much things rely on numpy, it's always a dangerous idea to upgrade to a ".0" version. |
WinPython 2017-01 build1 (2017-02-16)Main features (since WinPython 2016-06):
Areas of interest for testers:
Next focus:
History of changes for WinPython 3.6.0.2Qt5b1The following changes were made to WinPython distribution since version 3.6.0.1Qt5. Python packagesNew packages:
Upgraded packages:
Removed packages:
History of changes for WinPython 3.6.0.2Zerob1The following changes were made to WinPython distribution since version 3.6.0.1Zero. Python packagesNew packages:
Upgraded packages:
|
For build 2, please include Python 3.5 so I can test. Also, there is an update at |
If build 2 is more than week in the future, could you add 64-bit Python 3.5 to build 1? |
WinPython 2017-01 build2 (2017-03-0x)Main features (since WinPython 2017-01 build1):
Areas of interest for testers:
Next focus:
History of changes for WinPython 3.5.3.1Qt5b2The following changes were made to WinPython distribution since version 3.5.3.0Qt5. Python packagesNew packages:
Upgraded packages:
|
Did the build for WinPython 3.5.3.1Qt5b2 fail? 10 hours after the post of build 2, all I see is the Zero variants. |
hi, no. Just I wanted to check it, and it was too late yesterday night (coming up in 1 hour) |
WinPython 2017-01 build3 (2017-03-12)Main features (since WinPython 2017-01 build2):
Areas of interest for testers:
Next focus:
History of changes for WinPython 3.5.3.1Qt5 (b3)The following changes were made to WinPython distribution since version 3.5.3.0Qt5. Python packagesNew packages:
Upgraded packages:
|
Does build 3 have PyQt-5.8.1 or PyQt-5.8? There is a disagreement between the audit trail and the build 3 history. Also, the description for sounddevice is for sorted containers instead by mistake. |
hum, that is strange indeed ... checking ... Argh, I didn't place PyQt-5.8.1 in the right directory, we are still PyQt-5.8. shame on me. it's a technical debt I forgot to remove... doing it now. |
To avoid confusion, I suggest naming the new build with PyQt-5.8.1 "build 4". Will build 4 be posted in the next day? I would like to test 64-bit WinPython 3.5.3.1Qt5 with PyQt-5.8.1 since I am seeing a failure with PyQt-5.8. |
sorry hiccup7, next beta is after python-3.6.1 release, around 21rst |
WinPython 2017-01 rc (2017-03-2x)Main features (since WinPython 2017-01 build3):
Areas of interest for testers:
History of changes for WinPython 3.5.3.1Qt5 rcThe following changes were made to WinPython distribution since version 3.5.3.0Qt5. Python packagesNew packages:
Upgraded packages:
Removed packages: (for Win32 bit only) |
I don't see the installer links or hashes for build 4. Did the build fail? I would help test 64-bit WinPython 3.5.3.1Qt5b4. |
no. it may come during week-end.... it is an rc, as I don't wish further change from release. |
If you need to make a change for some other reason, updated lmfit 0.9.6 is available at http://www.lfd.uci.edu/~gohlke/pythonlibs/ |
a rc binary, in my nowodays interpretation, must be a true release candidate, and shall not be re-spin unless:
|
release condition: (python-3.6.1)
expected:
Audit Trail:
build1: 2017-02-16 "statmodels-0.8.0, Tensorflow-1.0, Edward, PyQt-5.8.0, Notebook-5.0.0b1"
build2: 2017-03-06 "notebook-5.0b1, python-3.6.1rc1 was delayed to 2017-03-04"
build3: 2017-03-12 (the last jedi-0.10 , notebook5.0b2, ipywidgets-6.0, scipy-0.19.0, pythonnet-2.3.0)
rc: 2017-03-26
rc is final = same binaries (2017-04-01)
postponed:
The text was updated successfully, but these errors were encountered: