This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author uranusjr
Recipients asvetlov, rhettinger, serhiy.storchaka, uranusjr, yselivanov
Date 2022-02-14.11:30:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644838200.18.0.991000957314.issue46622@roundup.psfhosted.org>
In-reply-to
Content
I agree that `print(await a.hello)` does look awkward, although I know some would disagree. (Context: I submitted this BPO after a colleague of mine at $WORK pointed out the behavioural difference between `functools` and `cached_property to me.)

Personally I’d feel this more natural:

class Foo:
    @functools.cache
    async def go(self):
        print(1)

async def main():
    foo = Foo()
    await foo.go()
    await foo.go()

Although now I just noticed this actually does not work either.

Perhaps we should fix this instead and add a line in the documentation under cached_property to point people to the correct path?
History
Date User Action Args
2022-02-14 11:30:00uranusjrsetrecipients: + uranusjr, rhettinger, asvetlov, serhiy.storchaka, yselivanov
2022-02-14 11:30:00uranusjrsetmessageid: <1644838200.18.0.991000957314.issue46622@roundup.psfhosted.org>
2022-02-14 11:30:00uranusjrlinkissue46622 messages
2022-02-14 11:30:00uranusjrcreate