On 25/07/15 22:08, boB Stepp wrote:
4) name_ is used when one is forced to use one of Python's reserved
words as a name.
Various others have commented on the use cases for this. I'd just add
that my solution to using a name that's already used by the language (or
even already used by my
On 25Jul2015 16:08, boB Stepp robertvst...@gmail.com wrote:
After having a long discussion with my wife on her user requirements,
I am convinced that an OO approach is required. Which is just as well
as that has been one of my next areas of learning to do. I am
currently reading Python 3
After having a long discussion with my wife on her user requirements,
I am convinced that an OO approach is required. Which is just as well
as that has been one of my next areas of learning to do. I am
currently reading Python 3 Object Oriented Programming by Dusty
Phillips, which so far seems
In a message of Sat, 25 Jul 2015 16:08:03 -0500, boB Stepp writes:
After having a long discussion with my wife on her user requirements,
I am convinced that an OO approach is required. Which is just as well
as that has been one of my next areas of learning to do. I am
currently reading Python 3
On Saturday, July 25, 2015, boB Stepp robertvst...@gmail.com
javascript:_e(%7B%7D,'cvml','robertvst...@gmail.com'); wrote:
5) __name__ is meant to be used only by the creators of Python for
their special built-in methods, such as __init__, __new__, etc.
Everything up to this point was pretty
On 25/07/2015 22:08, boB Stepp wrote:
After having a long discussion with my wife on her user requirements,
I am convinced that an OO approach is required. Which is just as well
as that has been one of my next areas of learning to do. I am
currently reading Python 3 Object Oriented Programming
boB Stepp robertvst...@gmail.com writes:
From my understandings to date:
1) A single underscore is used conventionally for a throw-away
variable, such as a loop index for which the index value is not
actually used in a subsequent calculation.
That accurately describes common usage. But it's