On Sat, 23 May 2009 01:25:09 -0700 Christopher Lee <l...@chem.ucla.edu> wrote:
> > By the way, do you think we will still need > > classutil.default_tmp_path() after this change? > No, better to use Python's standard way of doing things. Fair enough. Bye-bye, default_tmp_path()... http://github.com/mkszuba/pygr/commit/1fe92b15d532566a89aa2af7685831c4ae80ff21 (gettempdir branch) * * * > Correct me if I'm wrong, but this temporary directory change would > affect all threads running within our Python process, right? You are right here, threads (or at least POSIX threads, as I am not familiar with any other threading specifications) share their working directories. And given Windows doesn't support forking... Ugh. > If we really want to handle that case IMHO we should. If we really want to support many different Python versions, > we can do it trivially within the shell command we pass to system() > -- this works on both unix and Windows/cygwin. This should work in the native Windows shell too, as its command separator is "&&" - which works, even if somewhat differently, under both C- and Bourne-compatible shells. Let me know what you think: http://github.com/mkszuba/pygr/commit/80fb47917f3b53e3311a0d1dfb468b0b0d87c647 (filepopen_cwd branch) * * * > Great! We talked about adding a multiseq blast test to check that > the multiseq results match the combined results of running all the > sequences individually. Did you add that? I haven't added that one yet. -- 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 -~----------~----~----~----~------~----~------~--~---
