Hi list, I recently tried to do some analysis using rpy2 in a PyQt QThread from within a simple python application. For some reason however, the rpy2 processing ran about 10 times slower (sorry, I didn't actually do any proper timing) in the worker thread than it did in the main application thread. I've seen at least one prior post on rpy2 and threading, but have not seen anything about the issue I'm describing here.
I'm not going to post any code here, as the example is a bit complex, but I was just wondering if others had experienced this, if there was a workaround/fix for it, or if perhaps it's just plain silly to try to run rpy2 functions in a separate thread to being with? If people think it might be useful to include a reproducible example, I will be happy to include one upon request. Cheers, and thanks in advance for any insight you might have, Carson -- Carson J. Q. Farmer ISSP Doctoral Fellow National Centre for Geocomputation (NCG), National University of Ireland, Maynooth, Email: carson.far...@gmail.com Web: http://www.carsonfarmer.com/ ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
