Josiah Kaviani
Josiah Kaviani
Good evening, Could you provide full code example which cause en error with library you mention? I would try to figure out how to fix it. Best regards, Artem.
Good morning, I did some initial testing for `lazy_object_proxy` library. Generally, I'm interested in support of such libraries. What I have at that time: ```pycon >>> from dependencies import Injector...
Speaking about early instantiation, I could confirm it :cry: ```pycon >>> from lazy_object_proxy import Proxy >>> from dependencies import Injector >>> class Inner: ... def __init__(self, x): ... print('x', x)...
Indeed, `Proxy(Injector())` could be used only to wrap main injector. This solution does not work with nested Injectors. I just tried to reproduce example you provide: ```python from dependencies import...
Quick suggestion: try both `ipython` and `python -i` consoles. It could introduce additional magic.
That's because I'm an idiot. My system has python 3.10 by default, most recent dependencies release specified 3.9 as supported, so `pip` decided to install `3.0.0` version as most compatible.
Sorry it takes me too long to get back to this issue. I could confirm `Proxy` object does eager initialization in the example I post previously. ```pycon >>> from dependencies...
I found the way to workaround `isinstance` check you mention it the very first message. ```python from dependencies import Injector, value from lazy_object_proxy import Proxy as _Proxy class Inner: def...
API above was heavily influenced by [immer javascript library](https://github.com/immerjs/immer). As alternative I would like to suggest a "deep merge" operator for two Injector subclasses. It should be close to existed...
Positional-only arguments were added in python 3.8. At the moment we support Python 3.7 and PyPy 3.6. I don't want to introduce additional complexity to the build system to deal...