When we can expect next release?
jakub-borusewicz opened this issue · 6 comments
Your library seems to be very promising, but in my case I would benefit from it the most, if it would have __getattr__
implemented. When we can expect next release? As I can see, it is already implemented, but I guess there are some problems that stops you from releasing it?
Same here, the __getattr__
is an absolue show-stopper. Where's the catch in "just" proxying the through to the underlying object's __getattr__
?
@sobolevn What do you think??
Yes, I can work on it after the NY. Any help is appreciated!
👍 Looking forward to the mypy plugin being included and __getattr__
support.
How about setattr
?
Maybe
callback(_.setattr("hello", "world"))
or just
callback(_.set("hello", "world"))
?
Something fancy like callback(_(attr="hello", value="world"))
?
Maybe one could even think of using returns à la callback(_.hello.set_value("world"))
, though that might get confusing or interfere with user code.
@jakub-borusewicz @JosXa @virusdave it has been almost three years of waiting but I've just published a new release which has support for _.attr
support 😆