-
Notifications
You must be signed in to change notification settings - Fork 315
release 2017-02 follow-up #516
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:
build1 (2017-04-23: ipython-6.0, holoviews-1.7, matplotlib-2.0.1, droping python 2.7/3.4 as we look for C++11 packages)
build2 (2017-05-07: vitables, matplotlib-2.0.1)
build3 (2017-06-18, delayed by a busy week-end: ipython-6.1, pandas-0.20.2, jupyterlab-0.23.1, spyder-3.2dev )
b4 (2017-07-08, may slip by 7 days more)
b5 (2017-07-16, for the failed b4 attempt on python-3.6.2rc2 32bit)
b6 (2017-07-30, nodejs, spyder-terminal)
rc (2017-08-13) : (ffmpeg) may drop it (unless we slip again of 7 days) :
next time:
experiments:
|
Would it be possible to add GPflow too? |
@unoe : not at the moment. |
llvmlite updated to v0.17.1 http://www.lfd.uci.edu/~gohlke/pythonlibs/#llvmlite |
@hiccup7 thanks. now struggling with fastparquet |
build1 (2017-04-2x): numpy-0.11.2, pandas-0.19.0, bokeh-0.12.5main features (since WinPython 2017-01 ):
Areas of interest for testers:
Next Focus:
History of changes for WinPython-64bit 3.6.1.1ZeroThe following changes were made to WinPython-64bit distribution since version 3.6.1.0Zero. Python packagesNew packages:
Upgraded packages:
History of changes for WinPython-64bit 3.6.1.1Qt5The following changes were made to WinPython-64bit distribution since version 3.6.1.0Qt5. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
matplotlib v2.0.1 is available today. See http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib |
Please include Python 3.5 for future test builds. |
llvmlite‑0.18.0 is available. May be required for numba-0.33.0. |
build2 (2017-05-07): pandas-0.20.1, matplotlib-2.0.1, spyder-3.1.4main features (since WinPython 2017-02 build1):
Areas of interest for testers: (to contribute bug examples and patches)
Next Focus:
History of changes for WinPython-64bit 3.5.3.2Qt5The following changes were made to WinPython-64bit distribution since version 3.5.3.1Qt5. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
I have been testing WinPython-64bit-3.5.3.2Qt5b2, with matplotlib upgraded to v2.0.2. Spyder crashed while using the editor. If I figure out how to reproduce the bug, I will post a PR to the Spyder team. Otherwise, build 2 is working fine for me. |
thank you @hiccup7 for your time to test, debug, and propose a PR for spyder team. |
here says TensorFlow only supports version 3.5.x of Python on Windows, so does it worthwhile to include in 3.6.x build ? |
Yes:
|
Bottleneck‑1.2.1 is now available at http://www.lfd.uci.edu/~gohlke/pythonlibs/#bottleneck |
Hi, |
hi @joesoap99 , post rather on stackoverflow for this kind of questions |
Any progress with making it really portable? You're doing amazing work, really! |
build3 (2017-06-18/19): pandas-0.20.1, matplotlib-2.0.1, spyder-3.1.4main features (since WinPython 2017-02 build2):
Areas of interest for testers: (to contribute bug examples and patches)
Next Focus:
History of changes for WinPython-64bit 3.6.2.0Qt5b3The following changes were made to WinPython-64bit distribution since version 3.6.1.0Qt5. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
The build3 title says matplotlib-2.0.1, but the change log says matplotlib-2.0.2. Was it a mistake to include numpy 1.13.0+mkl? Previously, you recommended using the version of numpy listed at the top of http://www.lfd.uci.edu/%7Egohlke/pythonlibs/ |
build4 (2017-07-09/10): PyQt-5.9, pandas-0.20.3, spyder-3.2.0ev20170709)It could have been an rc, but:
main features (since WinPython 2017-02 build3):
Areas of interest for testers: (to contribute bug examples and patches)
Next Focus:
History of changes for WinPython-64bit 3.5.3.2Zero b4The following changes were made to WinPython-64bit distribution since version 3.5.3.1Zero. Python packagesNew packages:
Upgraded packages:
Removed packages:
History of changes for WinPython-64bit 3.5.3.2Qt5 b4The following changes were made to WinPython-64bit distribution since version 3.5.3.1Qt5. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
build5 (2017-07-17): spyder-notebook, numpy-1.13.1, spyder-3.2.0dev20170715Just for python-3.6.2 32 bit , who didn't have a build4. main features (since WinPython 2017-02 build4):
Areas of interest for testers: (to contribute bug examples and patches)
Next Focus:
|
build6 in the works (nodejs, spyder-3.2.1dev, jupyterlab-0.26.4) main issue: (turns around this ? jupyter-widgets/ipywidgets#1551 (comment) )
interesting part to check:
reverting to previous ipywidgets for release candidate is an option
History of changes for WinPython-64bit 3.6.2.0Qt5 b6The following changes were made to WinPython-64bit distribution since version 3.6.1.0Qt5. ToolsNew packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
Build 6 has been working well for me. Spyder v3.2.1 has no open issues: https://github.com/spyder-ide/spyder/milestones |
rc (ffmpeg) : 2018-08-12/13 main change since last betas:
main change since last beta:
Interesting part to check:
History of changes for WinPython-64bit 3.5.4.0Qt5The following changes were made to WinPython-64bit distribution since version 3.5.3.1Qt5. ToolsNew packages:
Python packagesNew packages:
Upgraded packages:
Removed packages:
|
@hiccup7 , spyder-3.2.1dev is not moving since a few days, so I took it as it is now, with last minute Qtpy-1.3 |
@stonebig , How come you take development builds of Spyder? |
procedure:
also, this may be simplified, if you don't bother the wheel:
there may be simpler steps. for pre-releases of bokeh, that doesn't work and the method to use is:
|
I didn't mean how you do it. |
The Spyder stable build is perfect for Anaconda stable-release, but sometimes lacks some bug-fixes for WinPython. So I use the dev build of Spyder stable branch 3.x, when it contains bug-fixes I want. |
I see. They have a great progress there with Spyder, really great team. |
pytorch is certainly great, trading blows with tensorflow for the benefit of Python stack. Yet I probably can't ship "CuDNN 7 + CUDA 8 / 9" with it.... But I see on the front page a "Facebook and Microsoft introduce ONNX" Let me know when it comes to Windows, and I'll have a check |
I'm not sure how it works but I think it has CuDNN built in. I'm not sure about CUDA (Does it use the system library or its own). I will surely let you know once it is available. Thank You. |
There is also the japan "Cupy/chainer" outsider that Travis Oliphant (numpy father) noticed https://twitter.com/teoliphant/status/941758883554619392 I think Tensorflow/cuda have the marketshare for this round, but things evolve quickly and cuda must loose dominance, as it's vendor-tied. |
@stonebig , As you can see in ContinuumIO/anaconda-issues#7410 PyTorch is a package by itself. Coming with CuDNN + CUDA on its own. It is a native Python Deep Learning package. |
By the way, it seems Windows support will be official in version 0.4 of PyTorch. |
Good news: having all leading DeepLearning packages under Python makes Python sucessfull. Unfortunately, Tensorflow is already getting too big for WinPython 2go limit, and Pytorch shall be bigger. |
release estimate: mid-august
expected:
new packages:
package updates:
infrastructure:
WinPython-201701 final is out, and is identical to rc.
The text was updated successfully, but these errors were encountered: