release 2018-01 follow-up #574
Comments
|
audit trail:
build1 (2017-12-24 , jupyterlab-0.30.x: re-booted with react-js+jlpm)
build2 (2018-01-01: Pandas-0.22.0, Spyder-3.2.5+, Jupyterlab bqplot plugin works)
build3 (2018-01-13: Spyder-3.2.6, Jupyterlab-beta1, notebook-5.3.0)
build4 (2018-01-21: Jupyterlab-beta1+, notebook-5.3.1)
build5 (2018-03-0x: Jupyterlab-beta1+, notebook-5.3.1, matplotlib-2.2.0rc2)
build7 (2018-03-25: python-3.6.5rc1, matplotlib-2.2, scipy-1.0.1):
rc (2018-03-3x)
rc2 (2018-04-05) postponed:
|
build1 (2017-12-24 , release with jupyterlab-0.31.0rc1, even if not working yet)main features (since WinPython 2017-03):
Areas of interest for testers:
focus for next build:
History of changes for WinPython-64bit 3.6.4.0Qt5 build1The following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
build2 (2018-01-01 , pandas-0.22, )main features (since WinPython 2017-03):
Areas of interest for testers:
focus for next build:
History of changes for WinPython-64bit 3.6.4.0Qt5b2The following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
|
I tested beta 2, and I get the same problem as spyder-ide/spyder#6091 |
|
hi @hiccup7, Best whishes for 2018, Thanks for the reporting to spyder-ide, |
|
@stonebig - Happy New Year to you too! Thank you too for following the issue and suggesting a safe update for the future. WinPython is still my favorite Python distribution. |
|
I see that beta/build 3 will contain spyder-3.2.6dev20180105. I would like to test this. Could you include your custom spyder wheel in the WinPython root folder? This way, users can revert Spyder to the earlier released versions and then re-install your custom spyder wheel (without having to re-install the whole WinPython). |
build3 (2018-01-07 : jupyterlab-beta, Jupyter notebook-5.3, if they show up jan 6th night)main features hoped (since WinPython 2017-04 b2):
|
|
Spyder v3.2.6 is now at https://www.lfd.uci.edu/%7Egohlke/pythonlibs/ Other users please note that Spyder no longer has a separate section on that page. Instead, it is in the Misc section. Thus, Spyder no longer appears in the "Index by date". |
build3 (2018-01-14 : jupyterlab-beta1, Jupyter notebook-5.3)main features (since WinPython 2018-01 b2 / WinPython 2017-04 b2):
Areas of interest for testers:
focus for next build:
History of changes for WinPython-64bit 3.6.4.0Qt5b3The following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
build3 (2018-01-21 : jupyterlab-beta1 stable, notebook-5.3.1)main features (since WinPython 2018-01 b3):
Areas of interest for testers:
focus for next build:
History of changes for WinPython-64bit 3.6.4.0Qt5b4The following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
|
beta1 of python3.7 only (2018-02-11, rc delayed by a week) in release:
|
|
@stonebig , Is there any option to integrate Conda in WinPython for management of packages? |
|
@RoyiAvital Conda has some technical advantages, but it is not accepted by the Python community. pip is still the official installer. The big advantage for me of WinPython is that its package manager is compatible with pip and all the wheel packages from the whole world community of Python users. If I switch to Anaconda, then I have a limited number of conda packages available. If I use pip to install packages not available in conda, conda doesn't know about them. It causes a big mess having two package managers simultaneously, and each one being unaware of packages installed by the other. If WinPython were to integrate conda, it would have the same problem as Anaconda. |
|
@RoyiAvital you describes the now defunct "pyzo" distribution, which was using the "conda" package manager of Anaconda. Anaconda is the only wise choice if you want to mix "pip" and "conda" installers. |
|
Please put Spyder-3.2.7 final in build 5. This would give me an incentive to test build 5. Also, having separate builds for Spyder and (major) matplotlib updates enables users to better diagnose the cause of a problem. |
|
Spyder-3.2.7 will be in. The problem is to get something big enough out. |
|
build5 (2018-02-26) Main Problem is WinPython exceeded the nsis limit of 2 Go, and has to drop extra-weight. In release:
Removed (to go back below nsis 2Go Limit):
History of changes for WinPython-64bit 3.6.4.0Qt5b5The following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Removed packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
|
Build 5 contains PyQt5 v5.10, which is incompatible with Spyder v3.27 (and earlier). Since the Spyder wheel blocks PyQt5 v5.10, how did the build succeed? Also, are you sure you want to include matplotlib v2.2.0rc1? Why not wait for v2.2.0 final? |
|
hi @hiccup7:
|
|
Want to submit an issue to the Spyder project for the incorrect setup.py? |
|
Spyder specification looks correct, according to this : https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-platform-specific-dependencies so it seems a pip issue. registered it at pypa/pip#5043 |
|
If I want to test build 5, do I replace PyQt5 with this one? |
|
yes, this is were we get them from, nowodays. pip uninstall -y PyQt5 && pip install PyQt5==5.9.2
|
|
I remember that "WinPython Control Panel" doesn't work for changing PyQt versions. |
|
for your offline pc:
"wppm" command line is the remnant of "pre-pip" installer, only used for "pyreadline.exe wheel". We don't want to compete with pip, we want pip to be competitive with conda (or closer to) . |
|
WinPython-3.7.0.0b2 (2017-02-28, with python-3.7.0.0b2) Changes:
WinPython 3.7.0.0ZeroThe following packages are included in WinPython-64bit v3.7.0.0Zero b2. Tools
Python packages
|
|
If the seaborn issue can't be resolved in matplotlib 2.2, will you release new winpython build with matplotlib 2.2 or use matplotlib 2.1.2 instead? |
|
I did propose a stupid patch on seaborn, do you like it ? mwaskom/seaborn#1379 I hope that a simple and better "hack" can be agreed on quickly, so I can implement it. I suppose Matplotlib-2.2.0RCs do exist so that people can raise true issues, and they can be resolved. |
|
The Matplotlib team seems ready to accept a tiny patch solution on their side. Yet, there are other decrepited things in seaborn, like mwaskom/seaborn#1380 So, the no-update situation of seaborn will end-up in a complete breakage with Matplotlib-3.0, if no new release can be done, and no fork shows up. |
|
That is a nice patch! |
|
build6 (2018-03-01) (32 bit only, currently uploading) Main final problem was getting Holoviews working in Jupyterlab. Change from last build 5:
Interesting for testers:
Preparing for release:
History of changes for WinPython-32bit 3.6.4.0Qt5b6The following changes were made to WinPython-32bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Upgraded packages:
Removed packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
|
matplotlib v2.2.0 final is released and available at https://www.lfd.uci.edu/%7Egohlke/pythonlibs/#matplotlib |
|
yes yes. and seaborn merged a compatibility patch of matplotlib-2.2.0 waiting for bokeh/bokeh#7587 (comment) |
|
WinPython needs to keep jupyter_client at v5.2.2 for compatibility with Spyder v3.2.8. |
|
I remember I needed the 5.2.3 for a reason... argh. and no fix in sight ? apparently jupyter_client-5.2.3 is not friendly to scipy either, not sure why |
|
Spyder v3.2.8 is available at https://www.lfd.uci.edu/%7Egohlke/pythonlibs/ |
|
matplotlib v2.2.0 files were updated on 2018-03-15 at https://www.lfd.uci.edu/%7Egohlke/pythonlibs/#matplotlib |
|
build7 (2018-03-25: python-3.6.5rc1, matplotlib-2.2, scipy-1.0.1): Change from last builds:
Interesting for testers:
Hopefully, next build will be the rc, with this change:
History of changes for WinPython-64bit 3.6.5.0Qt5The following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Upgraded packages:
Removed packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
|
rc (2018-03-31: python-3.6.5, spyder-3.2.8, matplotlib-2.2.2, scipy-1.0.1, Jupyterlab-0.31.12, nodejs-8.9.4): Release candidate. Change from last build:
Interesting for testers:
easter-egg:
easter-egg:
History of changes for WinPython-64bit 3.6.5.0Qt5rcThe following changes were made to WinPython-64bit distribution since version 3.6.3.0Qt5. ToolsNew packages:
Upgraded packages:
Removed packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
WinPython 3.7.0.0b3 (from Python-3.7.0b3)The following packages are included in WinPython-64bit v3.7.0.0 b3. Tools
Python packages
|
|
I installed WinPython64-3.6.5.0Qt5rc with a target directory of C:\Program Files\WinPython-3.6.5.0rc. C:\WinP\ is not practical as a target directory because users want to have several WinPython versions installed simultaneously. I don't use nodejs directly. Which packages in WinPython depend on nodejs (where I could expect a problem with my installation)? |
|
I'm not sure if it's of use when "running", but it's mandatory when "updating" the Jupyterlab stack. In next iteration, I'll probably move nodejs from I think you are just 3 characters too long in your current installation path. Maybe default installation path should just be "WinPy" instead of "WinPy64.3.6.1.0Qt5" |
|
PyQt4 is problematic today: spyder-ide/spyder#6889 It is important to me to install WinPython under C:\Program Files\ for good security because programs cannot write to subfolders unless run with administrator privileges. I propose that this problem is big enough to justify an RC2 build. After all, WinPython release 2018-01 will be used for many months by many users, including schools. Security is important to them too, and they too will install multiple versions of WinPython. |
|
"C:\Program Files\WinPy-3.6.5.0rc2" should work, as it's exact same length as build folder path. maybe I'll do an rc2, with the two identified actions on path reduction. |
|
so, I'm preparing an rc2 with this change only :
|
|
I thought Windows 10 solved this path issue already. |
|
That's not what tells me my own Windows 10 copy, so I suppose a lot of users will have the problem if it's not better handled in an rc2. |
|
Have a look at - https://superuser.com/questions/1119883. I like the folder naming you had before as it allows user to have several installations at once under the same folder. |
|
The "expert" user can easily change the default install directory. The "new" user will have much more hard time if he discovers in the middle of installation that his installation path is tool long. |
|
rc2:
==> This changes are intended to reduce path length constraint for included nodejs, so it has a better change to work "without thinking" on users PC. Nodejs may nevertheless work properly only if the root directory of WinPython has a path length of less than 37 characters, for example:
|
|
Any option to detect this? Thank You. |
|
Apps have to be "long paths aware" to take advantage of the new Windows 10 feature. See https://superuser.com/questions/1225845/how-to-allow-long-paths-in-windows-longer-than-260-characters Detecting maybe difficult in the installer. Maybe the solution is to have the installer inform "expert" users about the installation folder character limit for nodejs installation to succeed. |
|
@hiccup7 thanks for the article. |
|
For "expert" users, an easier solution may be to just document the installation folder character limit at https://winpython.github.io/ |
expected (new) date : 2017-04-01
expected features:
sustained effort of this release:
reduced effort:
other:
The text was updated successfully, but these errors were encountered: