MINUTES, 2009.02.10Present: Alex, Istvan, Jenny, Marek, Titus 1. Testing and building a. Megatests MS still working on generalisation. No deployments yet other than Namshin's at UCLA. Istvan suggests creating a separate directory for megatest scripts in the source tree; will add appropriate issue to the tracker. b. Building and standard tests Titus: a buildbot exists (created by Alex) which checks the sources out from the git repository, builds Pygr and tests it, on a number of different platforms. Suffered from local stability issues before, a new student is working on it now. He is still learning the ropes but will likely be done soon. Final expected form: Linux, OS X and Windows machines with Python 2.2 to 2.6. Estimated time of completion: 1-2 weeks. Istvan: major problems under Windows caused by having to explicitly specify 'b' flag to open files as binary rather than text. He has been trying to address this (see e.g. issue 60) but it would be much easier for someone familiar with Pygr core, who knows which files are which. Obvious candidate: Chris; MS will bring this up with him after he's come back from conference. c. New testing framework etc. - all tests converted but Istvan would like more testing and feedback. Titus will take care of this; - simplification of setup.py: ditto; - doctests: incorporated in the new framework. Istvan has converted some existing code examples; he will post a status report about this to pygr-dev. Also, other developers are encouraged to begin adopting this approach; - non-doctest code snippets: there appear to be quite a few, e.g. in the Cookbook. Idea: convert all these documents into the RST format and submit them to git, then periodically convert RSTs to Wiki format and push them to Google Code via Subversion. A local machine needed for this to happen - the upcoming new UCLA Pygr server? MS will bring this up with Chris after he's come back from conference. 2. Code review The first pass will be the new testing framework (see above), Titus will take care of this in a week. He will then go back to SequenceDB, which will take another week. 3. Human resources Not much chance of getting new developers any time soon... Titus will have some people begin using Pygr for their projects in a month or so, they will however work *with* it rather than *on* it; he believes the Pygr learning curve is too steep to get students involved here within existing time constraints. Jenny: doctests and more recipes, especially ones comparing Pygr to BioPython, MAQ and other genomic mining tools, will likely help here (Istvan has been working on comparing some such tools for a while, hopes to be able to make his findings into Wiki recipes within a few weeks). Istvan: some bits of code are too convoluted as a result of trying to produce very detailed error messages, thinks simply throwing exceptions would be good enough in many such places. Titus believes the latter will be addressed by the code review. 4. Open tracker issues close to resolving: - 10: almost done, just take care of the README.current problem (Chris?); - 33: unfortunately Jenny hasn't worked on this since the previous meeting; - 14, 37: done as soon as patches are accepted by Chris; - 36: continue discussion on the mailing list. 5. EVO We will have a short test meeting in two weeks. 6. Next meeting Unless Chris decides after his return that we need one earlier, the next full meeting will take place in four weeks - 2009.03.03 (Tuesday), 17:00 PST. Cheers! -- MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
