> I think it spawned a very helpful discussion. In the end, everybody wants > to be able to "kill off Fortran", but it might be a long road to get there > with contributions from many. > > As you've seen there's probably too many open issues to get something > usable by next week. Do you plan to work more on Cython after that? > (Answer in private if you wish). I'm happy to mentor you over summer if > you have time for something in that direction.
I would definitely like to continue trying to develop cython in an ongoing way, and my intent was to try to use the sage days coding sprint as a way to gain some familiarity with the cython code base. I suggested the previous project in part because there are a lot of aspects that I could do on my own so I don't monopolize other people's time with questions. In general, though, I am still balancing classes, prelims, and research, which is the only reason I haven't got more involved with cython til now, and I don't think things will let up until the fall. > As for an isolated Sage days project, I still think (2) in my initial > email (some form of efficient ndenumerate loop) would make a very good > stepping stone project and is something which would be useful in many > places regardless of how things turn out with Blitz++ etc. (At the very > least, it would mean more efficient copying to and from contiguous memory, > which would be useful everywhere, also in Kurt's GSoC or when using C++ > libraries for vectorization). This definitely seems like something useful, and I'd be happy to do it, but I would need some mentoring to get started. --Hoyt ++++++++++++++++++++++++++++++++++++++++++++++++ + Hoyt Koepke + University of Washington Department of Statistics + http://www.stat.washington.edu/~hoytak/ + [email protected] ++++++++++++++++++++++++++++++++++++++++++ _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
