Hynek Schlawack
Hynek Schlawack
There's nothing we can do her – let's pray to the Kanban gods.
Hmmm. So the thing is that I was kinda planning to expose class settings as a class _internally_ anyway, because the amount of arguments is getting out of control. However...
Sorry for the late answer. Would you mind showing/elaborating some use cases for this?
We have a volunteer! ✨
I think if you can do it backward compatible, there's no need for a new function?
Unfortunately we had to revert the changes due to #804. I think we'll have to write a new function to make stuff unequivocal. Sorry everyone! :(
I've been thinking about how to add first-class property support in attrs before, because I keep running into this limitation myself. Haven't come up with anything useful so far though...
Can’t we implement something ourselves? Technically it shouldn’t be a big of a deal: private var + property in front of it?
Absolutely. I think we can simulate that using a simple placeholder class that does almost the same. It might make sense to have a blessed way for that that would...
Yeah, the problem is that it doesn't work with slotted classes: ```python from functools import cached_property import time import attr @attr.define class A: @cached_property def x(self): return 42 a =...