On Sun, 23 May 2021 at 14:35, Chris Angelico <ros...@gmail.com> wrote: > > On Sun, May 23, 2021 at 10:30 PM Marco Sulla > <marco.sulla.pyt...@gmail.com> wrote: > > > > I think the only reason to introduce something like `private` is > > refactoring. If you added a `_variable` and later you decided to > > expose it, you have to change it to `variable`. This is something that > > in languages like Java is not necessary, you have only to change the > > variable from private to public. This sometimes bothered me in Python. > > Since you started with it private, you should be able to solve this > with a simple search-and-replace within the class's own definition. > Nothing outside the class should be affected. If it's that hard to > replace "self._variable" with "self.variable"
And, in non-trivial cases, it is :) > then you can always > create a property to make it available under both names. I use property a lot, but I noticed that the majority of programmers do not use them. Also asyncio, written by Guido himself, uses normal getters and setters. Maybe @property slows down the code? > > 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/L33KIIKBY4ZT7CVJXLGHXMXDCAM7ZQWH/ > Code of Conduct: http://python.org/psf/codeofconduct/ _______________________________________________ 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/ZHWEL7FV7HD2QAHQVXGLE4BTKIPU27VX/ Code of Conduct: http://python.org/psf/codeofconduct/
