: object does not provide __dir__
--
components: Interpreter Core
messages: 143349
nosy: amaury.forgeotdarc, benjamin.peterson, pitrou
priority: normal
severity: normal
status: open
title: method-wrapper objects are difficult to inspect
type: behavior
versions: Python 3.2, Python 3.3
Benjamin Peterson benja...@python.org added the comment:
51e27f42beda and friends.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12879
___
Bengt Richter wrote:
On Thu, 28 Apr 2005 11:33:04 +0200, Dr. Peer Griebel [EMAIL PROTECTED]
wrote:
Peer Dr. Griebel wrote:
[..]
Why has [].__str__ a different type than object.__str__?
Why is object.__str__ a routine while object().__str__ not?
Why wouldn't you expect different
On Thu, 28 Apr 2005 11:33:04 +0200, Dr. Peer Griebel [EMAIL PROTECTED]
wrote:
Peer Dr. Griebel wrote:
[..]
Why has [].__str__ a different type than object.__str__?
Why is object.__str__ a routine while object().__str__ not?
Why wouldn't you expect different types? Those are different
Peer Dr. Griebel wrote:
I think I was a little bit unspecific in my last mail.
I would like to see some description about method-wrapper and
wrapper_descriptor objects. I dont' understand the following behaviour:
type([].__str__)
type 'method-wrapper'
type(object.__str__)
type
Dr. Peer Griebel wrote:
Why has [].__str__ a different type than object.__str__?
Why is object.__str__ a routine while object().__str__ not?
Well, I don't know why inspect.isroutine does what it does, but if you
really need to detect these, can you do something like:
py MethodWrapperType =
I think I was a little bit unspecific in my last mail.
I would like to see some description about method-wrapper and
wrapper_descriptor objects. I dont' understand the following behaviour:
type([].__str__)
type 'method-wrapper'
type(object.__str__)
type 'wrapper_descriptor'
Hi,
I'm currently working on a Python Management Console.
During inspection of my objects I stumbled over method-wrapper objects.
Such an object may be obtained e.g. as
method_wrapper = [].__str__
My problem is: This object is not a method, not a function, not a
method descriptor
On 10 Dec 2004 15:03:01 -0800, [EMAIL PROTECTED] wrote:
Well, that could be a feature, depending on what your use case is.
Or you could make a method for adding methods, I suppose.
A perfectly transparent wrap of obj would be to do nothing ;-)
What do you actually want to do?
Actually, the very
Simon Brunning wrote:
On 9 Dec 2004 06:11:41 -0800, Egil M?ller [EMAIL PROTECTED] wrote:
Is there any way to create transparent wrapper objects in Python?
This work - http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52295?
Only for old-style classes, though. If you inherit from object
):
File stdin, line 1, in ?
TypeError: cannot concatenate 'str' and 'Wrapper' objects
=
So close! What's going wrong here? Well, it has to do with the fact that, when
developing new types, the onus is on the author of the type to play well with
others (e.g. accepting builtin types
Bengt Richter wrote:
On 9 Dec 2004 06:11:41 -0800, [EMAIL PROTECTED] (Egil M?ller) wrote:
Is there any way to create transparent wrapper objects in Python?
I thought implementing __getattribute__ on either the wrapper class
or
its metaclass would do the trick, but it does not work
Nick Coghlan wrote:
Simon Brunning wrote:
This work -
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52295?
Only for old-style classes, though. If you inherit from object or
another builtin, that recipe fails.
Could you explain, please? I thought __getattr__ worked the same with new-
Well, that could be a feature, depending on what your use case is.
Or you could make a method for adding methods, I suppose.
A perfectly transparent wrap of obj would be to do nothing ;-)
What do you actually want to do?
Actually, the very best would if only type(), isinstance() and the
[EMAIL PROTECTED] wrote:
The wrapper objects needs to work as dictionary keys, to support
printing, concatenation/addition, getitem/setitem and such things...
In that case, identifying exactly which operations you want to support, and
using a metaclass based approach like mine or Bengt's should
Is there any way to create transparent wrapper objects in Python?
I thought implementing __getattribute__ on either the wrapper class or
its metaclass would do the trick, but it does not work for the built
in operators:
class Foo(object):
class __metaclass__(type):
def
16 matches
Mail list logo
