-
Notifications
You must be signed in to change notification settings - Fork 317
release 2015-08 Follow-up (early december 2015) #190
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
comments:
|
Hi Carl, Thanks for the update. pipwin looks interesting indeed |
May I suggest adding the |
PyMC3 beta seems indeed interesting, but we shall wait that Christoph Gohlke gives its blessing wheels to this project, |
There is also the problem that Theano last official release is becoming more and more irrelevant: pymc-devs/pymc#850 (comment) |
so, it just a matter of shifting to Theano master. Pymc3 seems much smaller in size than pymc2 (and compiles directly in winpython via a nice |
Today, Anaconda has released python 3.5 version, but without PyQt5 (https://www.continuum.io/downloads) Will next version winpython support python 3.5 ? |
Probably not, unless:
All these events should happen around february 2016, according to my cristal ball and marketing understandings. |
@yw5aj which pymc are you talking (using) about ? pymc2 or pymc3 ? |
@stonebig First of all, sorry for the slow response! I was thinking about pymc2 because
But Christoph might be building it soon, so holding it until he builds it would be a terrific idea too. Shawn |
and does pymc2 works to your convenience with today WinPython ? |
@stonebig Yes - |
pipwin 0.2.2 with Python 3 support just landed. |
trying to wake-up a pymc3 beta2, as pymc3 looks way more active, and it doesn't seem so far from rc. |
build1 (2015-11-08: scikit-learn 0.17, matplotlib 1.5.0, pyzmq 15, PythonQwt/guiqwt/guidata refresh)main features (since previous release):
next build effort:
History of changes for WinPython 3.4.3.7Qt5Build1The following changes were made to WinPython distribution since version 3.4.3.6Qt5. Python packagesNew packages:
Upgraded packages:
|
build2 (2015-11-10: experimenting a Slim version of Winpython)main features (since previous 'Qt5' build1):
Feedback on this experiment is welcomed next build effort:
History of changes for WinPython 3.4.3.7Slim (build2)The following changes were made to WinPython distribution since version 3.4.3.7Qt5 (build1) Python packagesNew packages:
Upgraded packages:
Removed packages:
|
build3 (2015-11-11: experimenting a Slim version of Winpython for Python3.5 64bit)main features (since previous build2):
Feedback on this early Python3.5 experiment is welcomed:
WinPython 3.5.0.1SlimThe following packages are included in WinPython v3.5.0.1Slim build3. Tools
Python packages
|
build4 (2015-11-14: experimenting a full Qt4 version of Winpython for Python3.5 64bit)main features (since previous build3Slim):
Feedback on this last Python3.5 dedicated build experiment is welcomed:
Next builds:
WinPython 3.5.0.1The following packages are included in WinPython v3.5.0.1 build4. Tools
Python packages
|
Here is a link for the Universal C Runtime for an OS-specific, smaller download: |
Since WinPython Release 2015-07 is the end of Python 2 support, I suggest offering "still" and "fresh" variants of Python 3.4. This is similar to LibreOffice, where "still" implies stability and bug fixes, while "fresh" implies bleeding-edge, new features and high risk for bugs. Very important to me is stability in Spyder. The Spyder team is very busy making changes to support Qt5 and Python 3.5, but they haven't yet made a release supporting these. I also saw a Spyder commit saying that pylint doesn't yet support Python 3.5. I would rather stay with Qt4 and Python 3.4 for a few months until Spyder stabilizes. I am not clear on whether the latest numba, which requires the new Universal C Runtime, is too risky for the "still" variant. |
My own whish is to maintain WinPython 3.4 until July 2016. That said, we can't really see further than next release, like most open-source projects. |
build5 (2015-11-21: pandas 0.17.1, MKL update, formlayout for Qt5)Main features (since previous build4):
Feedback welcome on:
Next builds:
WinPython 3.4.3.7ZeroThe following packages are included in WinPython v3.4.3.7Zero build5. Tools
Python packages
|
build6 (2015-11-21/22/23: pandas 0.17.1, MKL update, formlayout for Qt5)Main features (since previous build4):
Feedback welcome on:
Next builds:
WinPython 3.4.3.7ZeroThe following packages are included in WinPython v3.4.3.7Zero build6. Tools
Python packages
History of changes for WinPython 3.4.3.7Qt5The following changes were made to WinPython distribution since version 3.4.3.6Qt5. Python packagesNew packages:
Upgraded packages:
|
build7 (2015-11-24+: Python3.5.1rc1)Main features (since previous build6):
History of changes for WinPython 3.5.1.1The following changes were made to WinPython distribution since version 3.5.0.1. Python packagesNew packages:
Upgraded packages:
Removed packages:
|
Spyder v2.3.8 has been released, which includes a fix for compatibility with matplotlib v1.5. |
Don't Panic ! Spyder is chasing a (too) wide range of targets: Python2/3, Linux/Windows/Apple. the fix/bug was for Python 2 / 'linux' combination. |
Thanks for the clarification. I notice that NumPy v1.10.x has been removed from here: |
Upgrading numpy too early caused me issues (work) last year. |
pylint v1.5.1 is now available, which is especially important for Python 3.5: |
ok |
Because Wiki is not practical to me to post changelogs and package index, I will jus post them as .md on the source. It shows result as if it was in The Wiki, with much less efforts. |
WinPython 2015-08 (2015-12-12), in 'Panda-color'
Features:
Many thanks to Steve Dower, Christoph Gohlke, Carl Kleffner, and Pierre Raybaut for their critical help in the cooking of WinPython 3.5.1 .
Binaries (currently uploading on sourceforge then github):
History of changes for WinPython 3.4.3.7Qt5
The following changes were made to WinPython distribution since version 3.4.3.6Qt5.
Python packages
New packages:
Upgraded packages:
Removed packages:
The text was updated successfully, but these errors were encountered: