Hello, 1. A while ago Chris spotted a few more hardcoded Unix-style paths in Pygr code. The commit
http://github.com/mkszuba/pygr/commit/690dac43b65d6ee8f66f0d1a22ce4ee7b97d616b in the "gettempdir" branch replaces these with calls to tempfile.gettempdir(). By the way, do you think we will still need classutil.default_tmp_path() after this change? 2. The commit http://github.com/mkszuba/pygr/commit/3782a57431cf26751aeb90848393bd2c10aac686 in the "filepopen_cwd" branch attempts to make it possible for called processes to use a different working directory than the current one even if the subprocess module (whose Popen() method has got a dedicated keyword for this) is not present. This will be needed if, as Titus suggested, we are to make formatdb run in the same directory as its data files. 3. The "blast_test" branch has been extended with more parser-only tests. Now every existing BLAST test which parses blastall output has its canned-output counterpart. Comments are welcome! -- MS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
