Aha.
I think I've just learned something interesting. It took me a while to
figure out although everyone else may already know - pysqlite returns
unicode strings from queries, which is not generally a problem - however,
passing these directly as strings for titles and axes for plots in rpy is
very bad for your sanity as it (at least in my hands) leads to (otherwise
mysterious) segfaults - eg
RHOME= /usr/local/lib64/R
RVERSION= 2.4.1
RVER= 2041
RUSER= /home/rerla
Loading Rpy version 2041 .. Done.
Creating the R object 'r' .. Done
Error: segfault from C stack overflow
Segmentation fault
For my setup, a liberal dash of ascii re-encoding such as:
rslist = [x.encode('ascii') for x in rslist]
seems to make the nasty segfaults go away and pretty R graphs appear in
their place.
Anyone know how to handle this in a general way?
Lots of people probably want unicode in their R plot headers. But, I wonder
how many people have been burned by this? Could be useful in the docs
somewhere?
--
python -c "foo = map(None,'[EMAIL PROTECTED]'); foo.reverse(); print
''.join(foo)"
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
