Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #85376 > unrolled thread
| Started by | Rustom Mody <rustompmody@gmail.com> |
|---|---|
| First post | 2015-02-09 03:28 -0800 |
| Last post | 2015-02-10 03:40 -0800 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.lang.python
doc buglets? Rustom Mody <rustompmody@gmail.com> - 2015-02-09 03:28 -0800
Re: doc buglets? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-02-09 15:55 +0000
Re: doc buglets? Rustom Mody <rustompmody@gmail.com> - 2015-02-10 03:40 -0800
| From | Rustom Mody <rustompmody@gmail.com> |
|---|---|
| Date | 2015-02-09 03:28 -0800 |
| Subject | doc buglets? |
| Message-ID | <cf5d6342-810a-4b7f-b644-aefbc7254b3f@googlegroups.com> |
Poking around in help() (python 3.4.2) I find * PACKAGES does not seem to have anything on packages * DYNAMICFEATURES seems to be some kind of footnote * SPECIALATTRIBUTES has 'bases' and 'subclasses'. It seems to me a more consistent naming for OOP would be in order. These are the OOP-metaphors I am familiar with - superclass ↔ subclass - base class ↔ derived class - parent class ↔ child class [Yeah if this is a bug its more than a docbug. So no, I am not suggesting changing the actual attribute names which would be a breaking change, just the stuff in help() ]
[toc] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2015-02-09 15:55 +0000 |
| Message-ID | <mailman.18562.1423497333.18130.python-list@python.org> |
| In reply to | #85376 |
On 09/02/2015 11:28, Rustom Mody wrote: > Poking around in help() (python 3.4.2) I find > > * PACKAGES > does not seem to have anything on packages > * DYNAMICFEATURES > seems to be some kind of footnote > * SPECIALATTRIBUTES > has 'bases' and 'subclasses'. It seems to me a more consistent naming > for OOP would be in order. These are the OOP-metaphors I am familiar with > - superclass ↔ subclass > - base class ↔ derived class > - parent class ↔ child class > > [Yeah if this is a bug its more than a docbug. > So no, I am not suggesting changing the actual attribute names which would be a > breaking change, just the stuff in help() > ] > So raise an issue and attach a patch. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence
[toc] | [prev] | [next] | [standalone]
| From | Rustom Mody <rustompmody@gmail.com> |
|---|---|
| Date | 2015-02-10 03:40 -0800 |
| Message-ID | <6054f695-3528-49d0-9633-66c33472c660@googlegroups.com> |
| In reply to | #85379 |
On Monday, February 9, 2015 at 9:25:45 PM UTC+5:30, Mark Lawrence wrote: > On 09/02/2015 11:28, Rustom Mody wrote: > > Poking around in help() (python 3.4.2) I find > > > > * PACKAGES > > does not seem to have anything on packages > > * DYNAMICFEATURES > > seems to be some kind of footnote > > * SPECIALATTRIBUTES > > has 'bases' and 'subclasses'. It seems to me a more consistent naming > > for OOP would be in order. These are the OOP-metaphors I am familiar with > > - superclass ↔ subclass > > - base class ↔ derived class > > - parent class ↔ child class > > > > [Yeah if this is a bug its more than a docbug. > > So no, I am not suggesting changing the actual attribute names which would be a > > breaking change, just the stuff in help() > > ] > > > > So raise an issue and attach a patch. Sure – can do. However for the first two I am not sure what the intentions of those entries are And for the third, I am not clear that anyone other than me finds the mismatching metaphors galling.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web