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: colet-KCgK2vT7wad/90uGnh1m2w at public.gmane.org (Cole Tuininga)
Date: Wed, 01 Aug 2007 13:24:32 -0400
In-reply-to: <46B0B985.1010202-Dp9fwfP21SfQT0dZR+AlfA@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> <46B0B985.1010202@ropine.com>

On Wed, 2007-08-01 at 12:49 -0400, Seth Gordon wrote:
> When I changed the code to take out the ` marks, I still got
> "<WriteOnly.WriteOnly object ...>" in the last line of output.

Hmmm - grab the code from http://www.code-energy.com/code/test.py - what
do you get for output from that?

-- 
Cole Tuininga <colet-KCgK2vT7wad/90uGnh1m2w at public.gmane.org>
http://www.code-energy.com/


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

Follow-Ups:
- Python descriptors are not transparent when they're first used
  - From: sethg-Dp9fwfP21SfQT0dZR+AlfA at public.gmane.org (Seth Gordon)

References:
- Python descriptors are not transparent when they're first used
  - From: sethg-Dp9fwfP21SfQT0dZR+AlfA at public.gmane.org (Seth Gordon)

Prev by Date: Python descriptors are not transparent when they're first used
Next by Date: SQL 2000 to MySQL
Previous by thread: Python descriptors are not transparent when they're first used
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