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. _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/ZDBM554BX5VRIMIQ7WIOY64FQA2NRVH3/ Code of Conduct: http://python.org/psf/codeofconduct/
