Tempo wrote:
> It worked. Those two functions (usefulness_of_cells &
> number_of_good_rows) seem to work flawlessly...knock on wood. I have
> run a number of different Excel spreadsheets through the functions, and
> so far the functions have a 100% acuracy rating. The acuracy rating is
> based on
It worked. Those two functions (usefulness_of_cells &
number_of_good_rows) seem to work flawlessly...knock on wood. I have
run a number of different Excel spreadsheets through the functions, and
so far the functions have a 100% acuracy rating. The acuracy rating is
based on the functions' returned
On 16/09/2006 2:55 AM, Tempo wrote:
> John Machin thanks for all of your help, and I take responsibility for
> the way I worded my sentences in my last reply to this topic. So in an
> effort to say sorry, I want to make it clear to everybody that it seems
> as though errors in my code and use of e
John Machin wrote:
[...]
>
> [1] There's a possibility that the package's author reads this
> newsgroup, and I've heard tell that he's a cranky old so-and-so; you
> wouldn't want him to take umbrage, would you?
>
Cranks doesn't even *begin* to describe it ...
regards
Steve
--
Steve Holden
John Machin thanks for all of your help, and I take responsibility for
the way I worded my sentences in my last reply to this topic. So in an
effort to say sorry, I want to make it clear to everybody that it seems
as though errors in my code and use of external programs (Excel in
particular) are m
Tempo wrote:
> Thanks for all of the help. It all has been very useful to an new
> python programmer. I agree that I should fix the error/bug instead of
> handeling it with a try/etc. However, I do not know why
> "range(sh.nrows)" never gets the right amount of rows right. For
> example, if the Exc
> if the Excel sheet has 10 rows with data in them, the
> statement "range(sh.nrows)" should build the list of numbers [0,
> 1,...9]. It should, but it doesn't do that. What it does is buld a list
> from [0, 1...20] or more or a little less, but the point is that it
> always grabs empy rows after t
Thanks for all of the help. It all has been very useful to an new
python programmer. I agree that I should fix the error/bug instead of
handeling it with a try/etc. However, I do not know why
"range(sh.nrows)" never gets the right amount of rows right. For
example, if the Excel sheet has 10 rows wi
Tempo wrote:
> Hello. I am getting the error that is displayed below, and I know
> exactly why it occurs. I posted some of my program's code below, and if
> you look at it you will see that the error terminates the program
> pre-maturely. Becasue of this pre-mature termination, the program is
> not
At Thursday 14/9/2006 23:40, Tempo wrote:
Hello. I am getting the error that is displayed below, and I know
exactly why it occurs. I posted some of my program's code below, and if
you look at it you will see that the error terminates the program
pre-maturely. Becasue of this pre-mature terminati
On Thu, 14 Sep 2006 19:40:35 -0700, Tempo wrote:
> Hello. I am getting the error that is displayed below, and I know
> exactly why it occurs. I posted some of my program's code below, and if
> you look at it you will see that the error terminates the program
> pre-maturely. Becasue of this pre-mat
11 matches
Mail list logo
