-
Notifications
You must be signed in to change notification settings - Fork 317
release 2018-03 follow-up #649
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:
beta1 (2018-07-31: python-3.7.0 fixes, take the Jupyterlab-0.33.x plunge, go back to Tensorflow, holoviews not working well in Jupyterlab ... a true beta )
beta2 (2018-08-12: stabilized Jupyterlab-beta3, brings back IDLEX)
beta3 (2018-08-20: updated javascript stack)
rc (2018-08-28: idlex, Spyder-3.3.1, Jupyterlab-0.34 beta4) rc2 (2018-09-02: idlex was missing in the big wheels, re-spinning with IDLEX added)
|
build1 2018-07-31 (Jupyterlab-0.33.4 beta3, Python-3.7 fixes, pythonnet for Python-3.7) Changes from WinPython 2018-02:
Areas of particular interest for testers:
focus for next build:
History of changes for WinPython-64bit 3.7.0.2 build1The following changes were made to WinPython-64bit distribution since version 3.7.0.1. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
Please leave PyTorch + TorchVision inside. I think once you have PyTorch you can remove Keras, Theano, etc... |
build2 2018-08-11 (Jupyterlab-0.33.4 beta8, Python-3.7 fixes, IDLEX) Changes from WinPython 2018-03 build 1:
Areas of particular interest for testers:
focus for next build:
History of changes for WinPython-64bit 3.7.0.2 b2The following changes were made to WinPython-64bit distribution since version 3.7.0.1. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
@stonebig , This is a truly Python based Deep Learning framework as opposed to TensorFlow. |
Tensorflow and Pytorch have both some advantages, see https://medium.com/@UdacityINDIA/tensorflow-or-pytorch-the-force-is-strong-with-which-one-68226bb7dab4 , but at the moment:
So for This iteration, I'm trying back the Tensorflow way, but maybe none of them will be able to remain in the Size Limit of WinPython. |
build3 2018-08-20 (Jupyterlab-0.34.0 beta4) Changes from WinPython 2018-03 build2:
focus for next build:
History of changes for WinPython-64bit 3.6.6.2Qt5 b3The following changes were made to WinPython-64bit distribution since version 3.6.6.1Qt5. ToolsUpgraded packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
@RoyiAvital from Pybay you can get the last Travis Oliphant talk "State of AI/ML in Python": https://speakerdeck.com/teoliphant/ml-in-python We shall hope a nice convergence of currently conflicting framework within 2 years time, as nobody wants to be trapped in a specific and incompatible framework. |
@stonebig , By the way, I'd prefer Chainer + CuPy instead of TensorFlow. |
@RoyiAvital Cupy is currently 100% tied to cuda/nvidia: 0% of PCs you can find in schools. |
But Chainer isn't. In case you have nVidia, Chainer will have the same features as PyTorch. Just like you don't say - The GPU framework of TensorFlow / PyTorch is 100% CUDA hence 0% support on schools and remove it it is OK to include CuPy with Chainer. |
Hi, By the way, could you add RISE to the packages? |
ok, will remove pymc3 to make room. |
@stonebig , Are you referring to the RISE request or PyTorch / Chainer? Update |
rc (2018-08-27) Change from WinPython 2018-03 build3
History of changes for WinPython-64bit 3.6.6.2Qt5 rcThe following changes were made to WinPython-64bit distribution since version 3.6.6.1Qt5. ToolsUpgraded packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
uploading rc as final. |
Congrats! What about Chainer and CuPy? |
at the moment:
|
Hi, The GPU features of TensorFlow only works on nVidia GPU's as well yet it is included. If you add Chainer + CuPy you'll have Dynamic Graph DNN which is written in Python with Numpy acceleration for those with nVidia GPU. Just like TensorFlow / PyTorch or any other DNN library. I'm coming from education (Student). |
rc3 (2018-09-02) for the non-zero wheels: change from rc1:
|
@stonebig , |
@RoyiAvital you may:
I'm strugling to make Jupyterlab build again, so you may anyway not have a new version until a few days. |
What I don't get is why would you prefer a library you can't see how it works and learn form it (TensorFlow) over options which are pure Python and people can look at the code, debug it and learn from it. Isn't it better for your audience (Education)? |
@RoyiAvital the choice is made of Tensorflow for this release. We'll see For next one:
|
I don't remember Pytorch was on Christoph Gohlke "reference" list before |
rc3 is the final version... updating website soon |
estimated release date: 2018-09-04
expected:
effort of the release:
non-effort of the release:
drop of the release:
The text was updated successfully, but these errors were encountered: