xlrd porting effort to Python 3.x

[juno]

Hi everybody,

After a scan of the messages in this group, it seems there is nothing
about Py3k.

My focus is only at xlrd module. I've hacked around it and it helps me
great to manipulate excel file without the Suite of - you know who
- ;)

I first use the 2to3 program to automagically correct basic syntax
changes, and then some hand corrections. I now have a modified module
that I can import with the Py3k interpreter (3.1.1).

It was a short time joy, because I have a traceback somewhere during
the opening process of the workbook.

So :
1/ is there someone else here hacking around xlrd and Py3k in order to
put the efforts together ?
2/ is there someone - apart the author - who is understanding the
deepest parts of xlrd to help me/us when there are issues
understanding the code ?

Thanks in advance. Happy coding !
Juno

[John Machin]

On 8/12/2009 6:05 AM, juno wrote:
> Hi everybody,

Hi juno,

Welcome to the list.

>
> After a scan of the messages in this group, it seems there is nothing
> about Py3k.

This is possibly a symptom that not many people want/need it yet ...

> I first use the 2to3 program to automagically correct basic syntax
> changes, and then some hand corrections. I now have a modified module
> that I can import with the Py3k interpreter (3.1.1).
>
> It was a short time joy, because I have a traceback somewhere during
> the opening process of the workbook.
>
> So :
> 1/ is there someone else here hacking around xlrd and Py3k in order to
> put the efforts together ?

... but there have been 2 or 3 people "hacking around" who have asked
questions off-list. They gave the appearance of wanting a Python
3.x-only port (as opposed to having one codebase that would support both
3.x and 2.x).

My objective: one codebase which "just works" with 2.x (currently 2.1 to
2.6, but thinking of dropping 2.1 and 2.2), and the output of 2to3 "just
works" (no further fiddling with the source) with 3.x.

For each of xlrd and xlwt, I have done (a) an information-gathering
crash-through-or-crash port to a single-codebase-both2&3 kit (b) a
principled port based on knowledge gained in the first step.

> 2/ is there someone - apart the author - who is understanding the
> deepest parts of xlrd to help me/us when there are issues
> understanding the code ?

There's one way to find out: ask your questions in this forum, and
specify a delay period that the author should wait out before replying :-)

What's the perceived problem: the alleged depth of the code, or the author?

Cheers,
John