News for hackers. Stuff that matters.
Re:A bite of Python by masklinn on Thursday September 08, 2016 @08:02AM (#12452178)
It's not an implementation detail, it is a deliberate, specified and documented feature of the language dedicated to namespace conflict resolutions in the context of inheritance.

ref: https://docs.python.org/2/reference/expressions.html#atom-id...

ref: https://docs.python.org/2/faq/programming.html#i-try-to-use-...

Re:A bite of Python by marklgr on Thursday September 08, 2016 @08:21AM (#12452286)
It's so crude that, again, it looks like implementation details having been promoted to specs. Field visibility and name mangling done with very magic underscores just doesn't look right, to me.
Re:A bite of Python by masklinn on Thursday September 08, 2016 @08:30AM (#12452342)
> Field visibility

It has nothing whatsoever to do with field visibility.

Re:A bite of Python by marklgr on Thursday September 08, 2016 @08:44AM (#12452414)
The single leading underscore?
Re:A bite of Python by masklinn on Thursday September 08, 2016 @09:32AM (#12452790)
Is conventional, it doesn't do anything at the language level.
Re:A bite of Python by marklgr on Thursday September 08, 2016 @10:17AM (#12453199)
Which is my point, it's still roll-your-own, with some magic when necessary. I don't want to make a fuss about it, I mean, it's great for tinkering or small projects, but I prefer when my compiler works harder for me and actually enforces what is intended (bar some runtime reflection for very special cases).
Re:A bite of Python by ubernostrum on Thursday September 08, 2016 @03:51PM (#12456666)
Or it's just a philosophy that you happen not to like, which doesn't make it objectively bad or wrong. There's room for people to have different tastes and preferences.
Re:A bite of Python by guyzmo on Thursday September 08, 2016 @08:06AM (#12452197)
Yes! Exactly! I added the py3 links of those in my big lengthy parent comment, so people get twice the chance to RTFM !