pre-PEP for optional 'pass'
brueckd at tbye.com
brueckd at tbye.com
Wed Apr 17 10:11:28 EDT 2002
More information about the Python-list mailing list
Wed Apr 17 10:11:28 EDT 2002
- Previous message (by thread): pre-PEP for optional 'pass'
- Next message (by thread): pre-PEP for optional 'pass'
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 17 Apr 2002, Duncan Booth wrote: > > We're veering slightly from the original reason for this point, which > > was how to write stub functions/methods which will be implemented > > later. The above certainly doesn't indicate any intent to actually > > implement the methods (in fact, on the contrary, it suggests they > > could be removed). > > I think you trimmed a bit too much when you followed up. I would have > described what the functions were intended to do if I had known that, > but as I said I have no idea what these particular functions do, so all > I could document was the lack of implementation. Since I was being > chastised for failing to produce meaningful docstrings for someone > else's imaginary functions I made them as meaningful as I could in the > circumstances. No, you were being chastised for promoting a horrible standard - that *all* classes and *all* methods should have a docstring. It's just plain wrong.
- Previous message (by thread): pre-PEP for optional 'pass'
- Next message (by thread): pre-PEP for optional 'pass'
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list