On 29/04/2010 5:59 AM, Patrick wrote:
> Is there a plan to migrate the xlrd code to run with Python 3.x?
Here is a restatement of the postion described in a thread about
2009-12-08, with clarifications:
... 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.
The steps (a) and (b) described above were a proof-of-concept exercise
carried out some time ago (when Python 3.0 was newly available) on then
current versions of the source. It didn't go as far as packaging up and
testing a 3.X distribution that would run 2to3 automatically as part of
installation.
As the message indicated, there have been very few inquiries for 3.X
versions, and none of those have been accompanied by offers of moral
support, physical assistance or funding.
So, the short answer is: no plan at the moment.
Do you have a requirement to build an application using Python 3.X?
Cheers,
John