Re: [Rpy] 2.1.0 last call for reporting issues before the release

2010-04-19 Thread Laurent Gautier
On 4/19/10 8:54 AM, Luca Beltrame wrote: > Speaking of "issues" (which I consider minor) in 2.1.x I found at the moment, > it is not possible to pass format parameters when saving a DataFrame object > (i.e. the R equivalents "sep, row.names, quote" and so on). > > Should I file a > bug report (o

Re: [Rpy] 2.1.0 last call for reporting issues before the release

2010-04-19 Thread Luca Beltrame
Speaking of "issues" (which I consider minor) in 2.1.x I found at the moment, it is not possible to pass format parameters when saving a DataFrame object (i.e. the R equivalents "sep, row.names, quote" and so on). Should I file a bug report (on which tracker?) so that it doesn't get lost? sign

Re: [Rpy] 2.1.0 last call for reporting issues before the release

2010-04-18 Thread Laurent Gautier
On 4/12/10 9:31 PM, Yaroslav Halchenko wrote: > I am still experiencing problems (segfault) in pymvpa with rpy2 on 64bit. That's annoying. Let's see what we can do about it. > But > lets start with unittests -- if I try using nosetests to discover/run them > then > I can get a segfault too: > >

Re: [Rpy] 2.1.0 last call for reporting issues before the release

2010-04-12 Thread Yaroslav Halchenko
I am still experiencing problems (segfault) in pymvpa with rpy2 on 64bit. But lets start with unittests -- if I try using nosetests to discover/run them then I can get a segfault too: 1. probably R issue, not RPy2 -- but wanted to check with you: ,--- | $> MVPA_SEED=1 PYTHONPATH=/home/yoh/proj/

[Rpy] 2.1.0 last call for reporting issues before the release

2010-04-11 Thread Laurent
I have a rather limited set of complains, so I am thinking that this is somehow ready for a release. I will have a last check at things, but better if I am not the only one looking at it. Please report: - bugs - missing features (advertised in the documentation, or that should implicitly be pre