"is" and ==

[BlueJ774]

Can someone please explain to me the difference between the "is"
keyword and the == boolean operator. I can't figure it out on my own
and I can't find any documentation on it.

I can't understand why this works:

if text is None:

and why this always returns false:

if message is 'PING':

even when message = 'PING'.

What's the deal with that?

[Erik Max Francis]

BlueJ774 wrote:

Can someone please explain to me the difference between the "is"
keyword and the == boolean operator. I can't figure it out on my own
and I can't find any documentation on it.

I can't understand why this works:

if text is None:

and why this always returns false:

if message is 'PING':

even when message = 'PING'.

What's the deal with that?

`x is y` means the same thing as:

id(x) == id(y)

You use the `is` operator for when you're testing for _object identity_,
not value. `None` is a special object sentinel that is not only a value
but a special _object_, and so if you're testing whether or not an
object is `None`, you do so with the `is` operator.

If you're testing whether an object is equal to the string "PING" then
you do not want to do so by identity, but rather value, so you use the
`==` operator, not `is`.

--
Erik Max Francis && ma*@alcyone.com && http://www.alcyone.com/max/
San Jose, CA, USA && 37 20 N 121 53 W && AIM, Y!M erikmaxfrancis
You could have another fate / You could be in another place
-- Anggun

[BlueJ774]

On May 30, 12:57 am, Erik Max Francis <m...@alcyone.c omwrote:

BlueJ774 wrote:

Can someone please explain to me the difference between the "is"
keyword and the == boolean operator. I can't figure it out on my own
and I can't find any documentation on it.

I can't understand why this works:

if text is None:

and why this always returns false:

if message is 'PING':

even when message = 'PING'.

What's the deal with that?

`x is y` means the same thing as:

id(x) == id(y)

You use the `is` operator for when you're testing for _object identity_,
not value. `None` is a special object sentinel that is not only a value
but a special _object_, and so if you're testing whether or not an
object is `None`, you do so with the `is` operator.

If you're testing whether an object is equal to the string "PING" then
you do not want to do so by identity, but rather value, so you use the
`==` operator, not `is`.

--
Erik Max Francis && [e-mail] m &&http://www.alcyone.com/max/
San Jose, CA, USA && 37 20 N 121 53 W && AIM, Y!M erikmaxfrancis
You could have another fate / You could be in another place
-- Anggun

Thanks. That's exactly what I was looking for.

[Warren Stringer]

I want to call every object in a tupple, like so:

#------------------------------------------
def a: print 'a'
def b: print 'b'
c = (a,b)

>>>c[:]() # i wanna

TypeError: 'tupple' object is not callable

>>>c[0]() # expected

a

>>>c[:][0] # huh?

a

>>[i() for i in c] # too long and ...huh?

a
b
[None,None]
#------------------------------------------

Why? Because I want to make Python calls from a cell phone.
Every keystroke is precious; even list comprehension is too much.

Is there something obvious that I'm missing?

Warren

Today's quote: "HELLO PARROT! wakey wakey!"

[Carsten Haese]

On Wed, 2007-05-30 at 11:48 -0700, Warren Stringer wrote:

I want to call every object in a tupple, like so:

#------------------------------------------
def a: print 'a'
def b: print 'b'
c = (a,b)

>>c[:]() # i wanna

[...]
Is there something obvious that I'm missing?

Yes: Python is not Perl.

Python is based on the principle that programmers don't write computer
code for the benefit of the computer, but for the benefit of any
programmer who has to read their code in the future. Terseness is not a
virtue. To call every function in a tuple, do the obvious:

for func in funcs: func()

HTH,

--
Carsten Haese
http://informixdb.sourceforge.net

[Warren Stringer]

Hmmm, this is for neither programmer nor computer; this is for a user. If I
wanted to write code for the benefit for the computer, I'd still be flipping
switches on a PDP-8. ;-)

This is inconsistent:

why does c[:][0]() work but c[:]() does not?
Why does c[0]() has exactly the same results as c[:][0]() ?
Moreover, c[:][0]() implies that a slice was invoked

So, tell me, for scheduling a lot of asynchronous events, what would be more
readable than this:

bidders = [local_members] + [callin_members]
bidders[:].sign_in(roster )
...

\~/

-----Original Message-----
From: py************* *************** *****@python.or g [mailto:python-list-
bo************* ********@python .org] On Behalf Of Carsten Haese
Sent: Wednesday, May 30, 2007 12:55 PM
To: py*********@pyt hon.org
Subject: Re: c[:]()

On Wed, 2007-05-30 at 11:48 -0700, Warren Stringer wrote:

I want to call every object in a tupple, like so:

#------------------------------------------
def a: print 'a'
def b: print 'b'
c = (a,b)

>>>c[:]() # i wanna

[...]
Is there something obvious that I'm missing?

Yes: Python is not Perl.

Python is based on the principle that programmers don't write computer
code for the benefit of the computer, but for the benefit of any
programmer who has to read their code in the future. Terseness is not a
virtue. To call every function in a tuple, do the obvious:

for func in funcs: func()

HTH,

--
Carsten Haese
http://informixdb.sourceforge.net
--
http://mail.python.org/mailman/listinfo/python-list

[irstas]

On May 31, 12:31 am, "Warren Stringer" <[e-mail] mwrote:

This is inconsistent:

why does c[:][0]() work but c[:]() does not?
Why does c[0]() has exactly the same results as c[:][0]() ?
Moreover, c[:][0]() implies that a slice was invoked

It's not inconsistent, but [:] probably does something different than
you think it does. All it does is create a copy (not in general, but
at least if c is a list or a tuple). Since in your example c is a
tuple and tuples are immutable, making a copy of it is essentially
useless. Why not just use the original? I.e. instead of c[:] you could
just write c. That's why c[:][0]() has exactly the same effect as c[0]
(), although the former is likely to be slightly slower.

c[:]() tries to call the copied tuple. Tuples aren't callable.
c[:][0]() calls the first element in the copied tuple, and that
element happens to be callable.

[Brian van den Broek]

Warren Stringer said unto the world upon 05/30/2007 05:31 PM:

Hmmm, this is for neither programmer nor computer; this is for a user. If I
wanted to write code for the benefit for the computer, I'd still be flipping
switches on a PDP-8. ;-)

This is inconsistent:

why does c[:][0]() work but c[:]() does not?

c[:][0]() says take a copy of the list c, find its first element, and
call it. Since c is a list of functions, that calls a function.

c[:]() says take a copy of the list c and call it. Since lists are not
callable, that doesn't work.

Why does c[0]() has exactly the same results as c[:][0]() ?

Because c[0] is equal to c[:][0].

Moreover, c[:][0]() implies that a slice was invoked

Yes, but the complete slice.

So, tell me, for scheduling a lot of asynchronous events, what would be more
readable than this:

bidders = [local_members] + [callin_members]
bidders[:].sign_in(roster )
...

for bidder in [local_members] + [callin_members]:
bidder.sign_in( roster)

Best,

Brian vdB

\~/

>-----Original Message-----
From: py************* *************** *****@python.or g [mailto:python-list-
bo************ *********@pytho n.org] On Behalf Of Carsten Haese
Sent: Wednesday, May 30, 2007 12:55 PM
To: py*********@pyt hon.org
Subject: Re: c[:]()

On Wed, 2007-05-30 at 11:48 -0700, Warren Stringer wrote:

>>I want to call every object in a tupple, like so:

#------------------------------------------
def a: print 'a'
def b: print 'b'
c = (a,b)

>c[:]() # i wanna
[...]
Is there something obvious that I'm missing?

Yes: Python is not Perl.

Python is based on the principle that programmers don't write computer
code for the benefit of the computer, but for the benefit of any
programmer who has to read their code in the future. Terseness is not a
virtue. To call every function in a tuple, do the obvious:

for func in funcs: func()

HTH,

--
Carsten Haese
http://informixdb.sourceforge.net
--
http://mail.python.org/mailman/listinfo/python-list

[Warren Stringer]

Hey many thanks for the replies!

Ah, so is seems that c[:][:][:][:][:][:][:][:][:][:][:][0]()
also work ...

Ah well, can't have everything. Guess I was inspired by the alphabetically
adjacent message "Call for Ruby Champion". Would have been nice for it work
- a more elegant iterator would be hard to come by. A PEP, perhaps? Maybe
not; am still a bit new - am probably missing something obvious why this
isn't an easy fix.

Pretty cool that I can override the list class.

Cheers,

\~/

-----Original Message-----
From: py************* *************** *****@python.or g [mailto:python-list-
bo************* ********@python .org] On Behalf Of Brian van den Broek
Sent: Wednesday, May 30, 2007 3:00 PM
To: py*********@pyt hon.org
Subject: Re: c[:]()

Warren Stringer said unto the world upon 05/30/2007 05:31 PM:

Hmmm, this is for neither programmer nor computer; this is for a user.

If I

wanted to write code for the benefit for the computer, I'd still be

flipping

switches on a PDP-8. ;-)

This is inconsistent:

why does c[:][0]() work but c[:]() does not?

c[:][0]() says take a copy of the list c, find its first element, and
call it. Since c is a list of functions, that calls a function.

c[:]() says take a copy of the list c and call it. Since lists are not
callable, that doesn't work.

Why does c[0]() has exactly the same results as c[:][0]() ?

Because c[0] is equal to c[:][0].

Moreover, c[:][0]() implies that a slice was invoked

Yes, but the complete slice.

So, tell me, for scheduling a lot of asynchronous events, what would be

more

readable than this:

bidders = [local_members] + [callin_members]
bidders[:].sign_in(roster )
...

for bidder in [local_members] + [callin_members]:
bidder.sign_in( roster)

Best,

Brian vdB

\~/

-----Original Message-----
From: py************* *************** *****@python.or g [mailto:python-

list-

bo************* ********@python .org] On Behalf Of Carsten Haese
Sent: Wednesday, May 30, 2007 12:55 PM
To: py*********@pyt hon.org
Subject: Re: c[:]()

On Wed, 2007-05-30 at 11:48 -0700, Warren Stringer wrote:
I want to call every object in a tupple, like so:

#------------------------------------------
def a: print 'a'
def b: print 'b'
c = (a,b)

c[:]() # i wanna
[...]
Is there something obvious that I'm missing?
Yes: Python is not Perl.

Python is based on the principle that programmers don't write computer
code for the benefit of the computer, but for the benefit of any
programmer who has to read their code in the future. Terseness is not a
virtue. To call every function in a tuple, do the obvious:

for func in funcs: func()

HTH,

--
Carsten Haese
http://informixdb.sourceforge.net
--
http://mail.python.org/mailman/listinfo/python-list

--
http://mail.python.org/mailman/listinfo/python-list

[Dustan]

On May 30, 5:37 pm, "Warren Stringer" <[e-mail] mwrote:

Hey many thanks for the replies!

Ah, so is seems that c[:][:][:][:][:][:][:][:][:][:][:][0]()
also work ...

Ah well, can't have everything. Guess I was inspired by the alphabetically
adjacent message "Call for Ruby Champion". Would have been nice for it work
- a more elegant iterator would be hard to come by. A PEP, perhaps? Maybe
not; am still a bit new - am probably missing something obvious why this
isn't an easy fix.

Pretty cool that I can override the list class.

Cheers,

Do a search on "python is not java" (words to live by). You can also
plug in another language you know (like Ruby), but you won't get as
many results.