|
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
From: John Machin <sjmac...@lexicon.net>
Date: Thu, 25 Jun 2009 12:29:39 +1000
Local: Thurs, Jun 25 2009 12:29 pm
Subject: Re: [pyxl] Status of XLRD reading .xlsx (Excel 2007)
On 25/06/2009 6:51 AM, Darryl Wallace wrote:
Hi Darryl, > I know this has been asked in the past, but is support for The current intention is this: > reading .xlsx (Excel 2007) format closer to being complete? Basic support will be in the next release, whenever that is, unless something happens that causes it not to be. It is intended to support on_demand=True but not formatting_info=True. Support for *any* version of Excel is unlikely ever to be "complete". > The reason I ask is because the included README.html mentions that s/is/was/ > support is scheduled for v0.7.1 which is the current version. I apologise for the slackness of the documentation team :-) > I tried If you have some non-simple XLSX files that you think may test the > to read a simple excel 2007 (under ubuntu linux, python 2.5.4) file > and was greeted with the following error: > --- >>>> book = xlrd.open_workbook("myexcel2007book.xlsx") > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "xlrd/__init__.py", line 429, in open_workbook > biff_version = bk.getbof(XL_WORKBOOK_GLOBALS) > File "xlrd/__init__.py", line 1545, in getbof > bof_error('Expected BOF record; found %r' % self.mem[savpos:savpos > +8]) > File "xlrd/__init__.py", line 1539, in bof_error > raise XLRDError('Unsupported format, or corrupt file: ' + msg) > xlrd.biffh.XLRDError: Unsupported format, or corrupt file: Expected > BOF record; found 'PK\x03\x04\x14\x00\x06\x00' > --- > So my guess is that it's not ready and that's fine. I was just > interested in the status. capabilities of the development team, please send them. Of particular interest would be files created by software other than Excel itself. As with previous Excel versions, Microsoft documentation will say "you must do X" but Excel will support reading non-X. This has already occurred with the docs saying you must use the shared string table; C# code supplied by an MS write-your-own-XLSX workshop doesn't comply but Excel accepts the resultant file silently. Cheers, You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||