Hi Malcolm,
On 11/12/2012 08:48 AM, Cook, Malcolm wrote:
Hi Herve,
Perfect. I understand the issue, and confirm the fix works for me.
Yes it's related to the discussion we had in the long "parallel package
generics" thread. By doing setGeneric("union") graph was claiming
ownership on this ge
Hi Herve,
Perfect. I understand the issue, and confirm the fix works for me.
Thanks!
Malcolm
> Hi Malcolm,
>
> The graph package was explicitly creating its own union() generic
> instead of importing it from BiocGenerics. This is fixed in versions
> 1.36.1 (release) and 1.37.1 (devel).
>
>
Excellent news. Thanks for the sleuthing and fix.
~Malcolm
> -Original Message-
> From: Hervé Pagès [mailto:hpa...@fhcrc.org]
> Sent: Friday, November 09, 2012 12:10 AM
> To: Cook, Malcolm
> Cc: bioc-devel@r-project.org
> Subject: Re: graph package conflict with GenomicRanges
>
> Hi Ma
Hi Malcolm,
The graph package was explicitly creating its own union() generic
instead of importing it from BiocGenerics. This is fixed in versions
1.36.1 (release) and 1.37.1 (devel).
Thanks for reporting this.
H.
On 11/08/2012 09:40 AM, Cook, Malcolm wrote:
Hi,
I find there is some form of
Hi,
I find there is some form of namespace conflict between the GenomicRanges
package and 'graph'
A session showing reproducible issue, and workaround, follows.
Thanks for your help and attention.
Malcolm Cook
Computational Biology - Stowers Institute for Medical Research
PS: The issue appea
