Hi Titus, one question on the usage of the variable name 'id': since 'id' is also the name of a Python built-in function, for the last year or so I have been trying to eliminate usage of 'id' as a variable name in Pygr, since that usage would block access to the built-in function of the same name. (By contrast, using 'id' as an attribute name seems fine, because that doesn't interfere with access to the built-in function).
I noticed that in seqdb-review you reverted some of my changes, e.g. you changed 'seqID' back to 'id'. I prefer 'seqID', both because it states specifically what the variable is, and because of the concern stated above. I propose that we be consistent throughout Pygr in naming such variables 'someID', i.e. with a meaningful prefix that tells you what kind of identifier it is, and with ID in upper-case. That's the pattern I am now following generally. What do you think? -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
