Skip to content
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

November + December 2014 Release follow-up #7

Closed
20 of 41 tasks
stonebig opened this issue Oct 20, 2014 · 8 comments
Closed
20 of 41 tasks

November + December 2014 Release follow-up #7

stonebig opened this issue Oct 20, 2014 · 8 comments

Comments

@stonebig
Copy link
Contributor

I proposed to follow-up here the plan for next release.

An intermediate release is planned in November, to fix annoying defaults.

Top comment (this one), would be updated from progress, links and inputs below.

Next Winpython 'distribution' intermediate release :

  • target date : mid-november 2014 (with Pandas0.15.1)
  • fix problems in sphinx/sqlite_bro/pep8/pyflakes packaging
  • fix links to winpython.github.io in Winpython itself
  • winpython package (to create a release) doesn't depend on guidata
  • simplify current download site
  • better Ipython Notebook default opening (inclusion of docs directoy)
  • feedback on docs (between Prelease and Release)
  • New packages : oct2py Octave interface, baresql, db.py
  • Removal of TortoiseHG from default winpython
  • update of existing packages (up to the time of the release)
  • numpy1.9.1
  • rebase pyjulia 'custom' from Pyjulia git2014-11-04 (still needs the fix)
  • pandoc included (used by nbconvert, sufficient to do the .html version of a Notebook)

Next Winpython 'distribution' intermediate release (IPython 3.0 being late) :

  • target date : mid-december 2014
  • python 2.7.9 (december 6th)
  • integrate auto-cleanup in winpython builder of AppData\Local\Temp\wppm_* directories
  • spyder 2.3.2 (unicode fix + improvements), pandas 0.15.2
  • switch to mingw64 static toolchain also for 32 bit
  • support OpenBLAS
  • Do_It_Yourself procedure improvement (wiki move)
  • better winpython.github.io
  • better winpython_afterdocs
  • New packages : pulp
  • considered packages : skll, xlwings, pandas-ply, bokeh 0.7
  • maybe time for an Ijulia flavor experiment ?

for another release:

  • numba 0.16.0, cython 0.22
  • Ipython 2.4 / Ipython3.0,
  • New interface packages (if ipython3.0) : scilab_kernel, octave_kernel
  • Flavors of the month : flavorR (if rpy2 in good shape for Windows)

Domains of Explorations (for enthusiast users)

  • Ipython3.0 pre-beta (a beta from Ipython team may be released end december)
  • comparison of the (3+ ?) Matlab interface packages (matlab_wrapper, pymatlab and mlab)
  • what if Spyder switch to PyQt5 ? (problems to solve)
  • PEP 405 (venv) and/or virtualenv effect on winpython
  • on board Clang compiler flavor
  • on board VC2010 (or more?) compiler flavor
  • New bigger data packages : Blaze, Dynd, Datashape, impyla
  • what if we try to mix with conda packages ? (Yuxang Wang experimenting)
  • Wall of Flavors (now in the wiki) : discussing what flavors should exists :
    • semi-officials (big group of specific needs),
    • exploration of next next release
    • typical user-made for their own need examples,
    • current Flavor ideas :
  • ...
@ankostis
Copy link

Would be nice to add support for Kivy:http://kivy.org/
An Open source Python library for rapid development of applications
that make use of innovative user interfaces, such as multi-touch apps.

@stonebig
Copy link
Contributor Author

a python 3.4 32 bit will do ? .. let me know (I choose the 32 bit supposing it would be used on windows tablets, sometimes limited to 32 bit)

@stonebig stonebig changed the title December 2014 Release follow-up November + December 2014 Release follow-up Oct 31, 2014
@stonebig
Copy link
Contributor Author

2014-11 release is brewing this week-end. I hope the 'docs' will please users, I did receive no feedback at the moment.

@ankostis
Copy link

My favorite doc-improvements:

  1. Make the old site (Pierre Raybaut@sourceforge) redirect to github.
  2. Make more obvious to the end-users what they have to do to modify their PATH after installation.

These 2 points still consume most of my support time, since there is no central point where i can guide them once and for all.
Lets hope that this time the release comes out "clean"

Well done in any case!

@stonebig
Copy link
Contributor Author

It's for this milestone. what means "clean" in your mind ?

@ankostis
Copy link

A "clean" installation experience would be:

  1. Google: winpython, [Click 1st choice at github.io],
  2. Select WinPython version (64/32bit, python2,3) & Download,
  3. Execute & wait to unpack...
  4. blah-blah,
    • [check-box] "Do you want to register after install?",
    • [checkbox] "Do you want to add/replace in PATH?",
      5 [Click install] and wait...Done!

@stonebig
Copy link
Contributor Author

Ah, ok. Thanks for the clarification.
Is it better now ? (still some work)

@stonebig
Copy link
Contributor Author

Apparently today nov. 21rst, winpython.github.io is second choice.

I intend to place the 3.4.2 release also on the old website this week-end, so any google "1rst choice" will 'also' suggest a recent winpython.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants