On Fri, May 7, 2021 at 4:04 AM Shreyan Avigyan <pythonshreya...@gmail.com> wrote: > > Chris: > > > That would require some definition of what's "within" and what's > > "outside" the class, and whatever definition you use, it won't work > > with all forms of dynamic code. > > Yes, implementing that will be hard. But the question is I can't quite > understand why this is not acceptable by the Python community? Private > members may be a disaster but I don't think readonly attributes is. In fact > that's what have been implemented for years using @property. >
I'm not sure about other people, but I have never, not once, used @property as a means of controlling access. So giving me another way to do something that I am not, and don't want to, do... isn't much of an argument. :) ChrisA _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/XDTYC7RAXP4KPKBPX24VTCYGSRDJGABX/ Code of Conduct: http://python.org/psf/codeofconduct/
