[issue10403] Use "member" consistently

Changes by Senthil Kumaran : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue10403] Use "member" consistently

Roundup Robot added the comment: New changeset 3935a1fb1db2 by Senthil Kumaran in branch '2.7': merge from 3.2 - Issue10403 - datetime module documentation changes based on review. http://hg.python.org/cpython/rev/3935a1fb1db2 -- ___ Python tracker

[issue10403] Use "member" consistently

Roundup Robot added the comment: New changeset 05f0ffe4e0b3 by Senthil Kumaran in branch '3.2': Fix Issue10403 - datetime documentation clarification based on review in the reitveld by Alexendar belopolsky. http://hg.python.org/cpython/rev/05f0ffe4e0b3 -- _

[issue10403] Use "member" consistently

Senthil Kumaran added the comment: Hello Eric, I missed noticing Alexander's comments in the reitveld, I looked only at tracker then. I see that some of them can be addressed. Like using members (components) of the field, instead of attributes when it is not an attribute. Shall correct it. Th

[issue10403] Use "member" consistently

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10403] Use "member" consistently

Changes by Éric Araujo : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10403] Use "member" consistently

Changes by Eric Snow : -- nosy: +ericsnow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue10403] Use "member" consistently

Éric Araujo added the comment: Senthil, I’m not sure you read Alexander’s reply on Rietveld before committing. -- ___ Python tracker ___

[issue10403] Use "member" consistently

Roundup Robot added the comment: New changeset b8f5da066782 by Senthil Kumaran in branch '2.7': Fix closes issue10403 - Let's not use members anymore. http://hg.python.org/cpython/rev/b8f5da066782 -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed

[issue10403] Use "member" consistently

Roundup Robot added the comment: New changeset d442c313536b by Senthil Kumaran in branch '3.2': issue10403 - Let's not use members anymore. Use 'attribute' where it denotes attribute and 'methods' where it denotes methods. Context should clarify usage. http://hg.python.org/cpython/rev/d442c3135

[issue10403] Use "member" consistently

Roundup Robot added the comment: New changeset d442c313536b by Senthil Kumaran in branch '3.2': issue10403 - Let's not use members anymore. Use 'attribute' where it denotes attribute and 'methods' where it denotes methods. Context should clarify usage. http://hg.python.org/cpython/rev/d442c3135

[issue10403] Use "member" consistently

Éric Araujo added the comment: I’m not -1 on using “attributes” to denote methods, since they *are* and it’s not difficult to understand, and I’m not opposed either to using “attributes” to replace “members” (i.e. attributes that are not methods.) For those wanting to see the raging debate:

[issue10403] Use "member" consistently

Senthil Kumaran added the comment: Yes, I agree with you. Good Suggestion. Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue10403] Use "member" consistently

Antoine Pitrou added the comment: So I'm -1 on using "attributes" to denote methods. It will actively confuse non-expert users. If you want to ditch "members", please consider using the more explicit phrase "attributes and methods". -- nosy: +pitrou __

[issue10403] Use "member" consistently

Éric Araujo added the comment: Alexander, could you comment on the review page about datetime.rst changes? -- nosy: +belopolsky ___ Python tracker ___ __

[issue10403] Use "member" consistently

Changes by Adam Woodbeck : Added file: http://bugs.python.org/file22438/issue10403_v3.patch ___ Python tracker ___ ___ Python-bugs-list mailin

[issue10403] Use "member" consistently

Adam Woodbeck added the comment: I was always under the impression attributes and methods were mutually exclusive. I've corrected the patch as requested. -- Added file: http://bugs.python.org/file22436/issue10403_v2.patch ___ Python tracker

[issue10403] Use "member" consistently

Éric Araujo added the comment: > I used "methods and attribute" in io.rst because BufferedIOBase > included one attribute and several methods. My terminology may be > off, but I felt this was the correct replacement of "members." Nearly :) See in the first message: > "Members and methods" sho

[issue10403] Use "member" consistently

Adam Woodbeck added the comment: I grepped the documentation in the cpython repository and replaced all mentions of "member(s)" with "attribute(s)" where I felt appropriate. I left mentions of "members" related to structs or any C documentation alone as I'm less confident of their terminolog

[issue10403] Use "member" consistently

Changes by Adam Woodbeck : -- nosy: +adam.woodbeck ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10403] Use "member" consistently

Changes by Senthil Kumaran : -- stage: -> needs patch type: -> behavior versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___

[issue10403] Use "member" consistently

Senthil Kumaran added the comment: It is 'attributes' instead of term 'members'. The term 'method' when it denotes methods can be left as such. -- assignee: d...@python -> orsenthil nosy: +orsenthil ___ Python tracker

[issue10403] Use "member" consistently

Raymond Hettinger added the comment: > "Members and methods" should just be "attributes". +1 That substitution should be made almost everywhere. Individual slot variable are still called members though and their type is a member_descriptor. And the C API still has a tp_members entry. Other

[issue10403] Use "member" consistently

Changes by Fred L. Drake, Jr. : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10403] Use "member" consistently

New submission from Fred L. Drake, Jr. : Some portions of the documentation are using the term "member" to mean "data attribute". This appears to be an aberration at this time, but occurrences should be identified and corrected, and "Documenting Python" updated to note correct usage. Example