© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
My personal impression (take this with a grain of salt, I don't know too much about testresources yet) is that teaching the decorator to pass through unknown attribute lookups will fix this particular issue, but make the ultimate failure condition much more painful; especially given the proclivity of test-infrastructure code to make liberal use of potentially conflicting names like "name", "id", "count", etc.
The idea of somehow making the decorator less intrusive is a good one, though. If passing through attribute lookups could be combined with some mechanism for namespacing of additional attributes that might eliminate my concern...?