Jun 9, 2016, 1:54:55 AM6/9/16
to python...@googlegroups.com, John Machin
So, I wanted to be somewhat more official about this...
With the recent work I've done sprinting at Pycon 2016 in Portland, and
the week following, I believe all three of the packages I've maintained,
two of them along with John Machin, are now in a sensible state; they
have docs on Read The Docs, they are all Python 3 compatible and they
all have continuous integration running under Travis CI, including
releasing to PyPI when tags are pushed.
The packages in question are xlrd, xlwt and xlutils. I will be upfront
and say you should no longer be using these unless you have a particular
need to work with .xls files. If you only work with .xlsx files, and
that's the only Excel format you should look to create nowadays, then
you should be using openpyxl instead.
This is open source, so none of xlrd, xlwt or xlutils are going away,
just be aware that if you have problems, you'll likely need to be the
one to do the work, read the specs, read the code, and propose fixes.
Until someone better comes forward, I'll still be gatekeeper for merging
pull requests along with John Machin, and I'll be looking for tests and
descriptive code changes before doing so. Stability is of utmost
importance in these now mature packages.
If you have a passion to maintain any of these libraries, please make
yourself known, and prove you're serious about it.
In the meantime, I'd like to take the time to thank John Machin. He's
been the brains behind the three packages and knows more about Excel
files than I will ever want to or be capable of! I'd also like to wish
Charlie Clark the best of luck with openpyxl; you're a braver man than I ;-)
cheers, and thanks for all the fish,