W. eWatson wrote:
I think I understand it, but how does one prevent it from happening, or
know it's the cause? That msg I got?
Yes. The message 'x is not callable', where x is a name of something you
expect to be callable (such as the builtin functions and classes),
signals that x has been r
On Mon, 30 Nov 2009 01:07:53 -0500, Mel wrote:
> In FORTRAN and PL/I words were un-reserved to a degree that's really
> bizarre. A short post can't begin to do it justice -- let's just mention
> that IF and THEN could be variable names, and DO 100 I=1.10 . The syntaxes
> were carefully crafte
"W. eWatson" writes:
> I think I understand it, but how does one prevent it from happening,
> or know it's the cause? That msg I got?
Yes. The line of code was pretty clear: you were attempting to call an
object, and the error message said the object's type doesn't support
being called.
More ge
W. eWatson wrote:
> I think PL/I, FORTRAN, ALGOL, etc. have reserved words.
Algol reserved syntactic tokens that resembled English words, but specified
that they should be written in a different way from programmer-defined
symbols, so no conflict was possible. Published algorithms might have t
On 11/30/2009 4:20 PM, W. eWatson wrote:
John Bokma wrote:
"W. eWatson" wrote:
Yikes. Thanks very much. Python seems to act unlike other language in
which words like float are reserved. I'll use asum.
The problem is that there is a function sum and you creating a float sum:
sum = 0.0
and
John Bokma wrote:
"W. eWatson" wrote:
Yikes. Thanks very much. Python seems to act unlike other language in
which words like float are reserved. I'll use asum.
The problem is that there is a function sum and you creating a float sum:
sum = 0.0
and
mean = sum(hist)
even if both could exis
"W. eWatson" wrote:
> Yikes. Thanks very much. Python seems to act unlike other language in
> which words like float are reserved. I'll use asum.
The problem is that there is a function sum and you creating a float sum:
sum = 0.0
and
mean = sum(hist)
even if both could exist side by side it
On Nov 29, 8:14 pm, "W. eWatson" wrote:
> Ben Finney wrote:
> > "W. eWatson" writes:
>
> >> "C:\Sandia_Meteors\Sentinel_Development\Development_Sentuser+Utilities\sentuser\sentuser_20090103+hist.py",
> >> line 467, in ShowHistogram
> >> mean = sum(hist)
> >> TypeError: 'float' object is not c
Ben Finney wrote:
"W. eWatson" writes:
"C:\Sandia_Meteors\Sentinel_Development\Development_Sentuser+Utilities\sentuser\sentuser_20090103+hist.py",
line 467, in ShowHistogram
mean = sum(hist)
TypeError: 'float' object is not callable
It means you're calling an object of type ‘float’. The
"W. eWatson" writes:
> "C:\Sandia_Meteors\Sentinel_Development\Development_Sentuser+Utilities\sentuser\sentuser_20090103+hist.py",
> line 467, in ShowHistogram
> mean = sum(hist)
> TypeError: 'float' object is not callable
It means you're calling an object of type ‘float’. The line where it
Here's an traceback error msg I get.
Exception in Tkinter callback
Traceback (most recent call last):
File "C:\Python25\lib\lib-tk\Tkinter.py", line 1403, in __call__
return self.func(*args)
File
"C:\Sandia_Meteors\Sentinel_Development\Development_Sentuser+Utilities\sentuser\sentuser_200
11 matches
Mail list logo
