-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.4.0 rpy2 issue #38
Comments
FWIW I think both Chris C and I have seen something like this and have been On Friday, October 7, 2016, Nick Harding notifications@github.com wrote:
Alistair Miles |
Will leave this open for now until we see how updated rpy2 behaves in 2.5.0 |
Would be nice to find an automated way to check if rpy2 is behaving, it's
been the problem child so far. I wonder if there is an easy way to run the
rpy2 test suite (assuming it has one) within the travis CI...
…On Tue, Jan 31, 2017 at 3:34 PM, Nick Harding ***@***.***> wrote:
Will leave this open for now until we see how updated rpy2 behaves
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAq8QjW6Tj7ptcy6CwYu4CWUcZTDMKmfks5rX1SNgaJpZM4KRLLN>
.
--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health <http://cggh.org>
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email: alimanfoo@googlemail.com
Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721
|
So I think rpy2 is still broken. I've added a PR to run the rpy2 test suite
(#43), let's see if test suite runs OK on travis (fails on my local
install)...
On Tuesday, January 31, 2017, Alistair Miles <alimanfoo@googlemail.com>
wrote:
… Would be nice to find an automated way to check if rpy2 is behaving, it's
been the problem child so far. I wonder if there is an easy way to run the
rpy2 test suite (assuming it has one) within the travis CI...
On Tue, Jan 31, 2017 at 3:34 PM, Nick Harding ***@***.***
***@***.***');>> wrote:
> Will leave this open for now until we see how updated rpy2 behaves
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#38 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAq8QjW6Tj7ptcy6CwYu4CWUcZTDMKmfks5rX1SNgaJpZM4KRLLN>
> .
>
--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health <http://cggh.org>
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email: ***@***.***
***@***.***');>
Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721
--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health <http://cggh.org>
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email: alimanfoo@googlemail.com
Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721
|
This is what I'm getting locally:
|
get_ipython().magic('reload_ext rpy2.ipython')
Generates an error.
The text was updated successfully, but these errors were encountered: