[bip] PyGr code review

[Christopher Lee]

Hi Nathan,
thanks for volunteering!  Here are a few ideas on the process for a  
code review:

- finish the 0.7 release
- complete PEP8 re-formating (begun a couple months ago on Titus  
Brown's advice)
- choose an initial module for review.  It would probably be better  
to start with something simpler, that the reviewers have had direct  
experience using, like pygr.seqdb.
- conduct a code review with at least two external reviewers to  
improve code robustness, simplicity and readability.
- each reviewer does an independent review, then we all discuss as a  
group via teleconference or Skype.
- follow up with email
- implement changes

How does this sound to you?  What module(s) have you used  
extensively?  What module would you suggest for the first review?   
What module / aspects of 0.5 gave you trouble?

Yours with thanks,

Chris
On Sep 26, 2007, at 2:35 AM, Nathan Harmston wrote:

> Hi,
>
> I d like to volunteer to do some code reviews for PyGr, I cant  
> pretend that my coding skills are the greatest but I think this  
> would be good for me, and if I ever build a package/code I hope  
> some people volunteer to review the code. I m going to be busy for  
> a couple of weeks as I m just starting a new course but hopefully I  
> ll be able to a have a look after then. I remember there were a few  
> portions of code/ways of doing things in pygr 0.5 that I didnt like  
> so I ll see if they've been changed.
>
> Chris: How are you planning on organising the code review?
>
> Thanks
>
> Nathan