BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Python descriptors are not transparent when they're first used

Subject: Python descriptors are not transparent when they're first used
From: sethg-Dp9fwfP21SfQT0dZR+AlfA at public.gmane.org (Seth Gordon)
Date: Wed, 01 Aug 2007 12:49:09 -0400
In-reply-to: <1185923972.19530.3.camel-3d271U21k4+RUznp8rcpbkB+6BGkLq7r@public.gmane.org>
References: <46AE4001.3080105@ropine.com> <1185843995.21902.22.camel@martha.tuininga.org> <46AF7015.6040000@ropine.com> <1185923972.19530.3.camel@martha.tuininga.org>

Cole Tuininga wrote:
> 
> If you were to instead have done:
> print foo.quux   # Note the lack of ` marks
> 
> It would have displayed None

When I changed the code to take out the ` marks, I still got
"<WriteOnly.WriteOnly object ...>" in the last line of output.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Prev by Date: SQL 2000 to MySQL
Next by Date: Python descriptors are not transparent when they're first used
Previous by thread: SQL 2000 to MySQL
Next by thread: Python descriptors are not transparent when they're first used
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org