Dear All,
I ran into the following problem when porting my package from Bioc 3.3 to
3.4. When I attach my package interactively (library(package), or via
load_all from devtools) everything works fine on both 3.3 and 3.4. However,
when I install my package (p.arc) and call it using:
Rscript -e 'p.
Dear All,
I ran into the following change in behaviour between the 3.3 and 3.4
Bioconductor releases.
The following code returns TRUE for 3.3 and FALSE for 3.4
library(GenomicRanges)
ir <- IRanges(sample(100),sample(100)+100)
ir2 <- unlist(split(ir, ceiling(1:100 / 10)))
all(ir==ir2)
The reason
not edit by hand
export(att)
import(GenomicFeatures)
3. None of the reasons you listed as causing an implicit attach seems to
apply here.
Thanks,
Marcin
On Mon, Oct 19, 2015 at 5:56 PM, Hervé Pagès wrote:
> Hi Marcin,
>
> On 10/19/2015 05:11 AM, Marcin Cieślik wrote:
>
>> D
Dear Bioc Developers,
I am developing a package that depends on GenomicFeatures which I am adding
to my package using Imports: and import(GenomicFeatures). However, when I
use the "genes" function the "BiocGenerics" package gets attached (I am not
adding BiocGenerics to my Depends:).
Am I missing
Dear All,
I can confirm that the issue is fixed in the latest BioC / R versions.
Thanks a lot.
Yours,
Marcin
On Fri, Oct 16, 2015 at 7:09 AM, Michael Lawrence wrote:
> On Thu, Oct 15, 2015 at 11:04 PM, Hervé Pagès
> wrote:
>
> > Hi Michael,
> >
> > On 10/15/2015 10:08 AM, Michael Lawrenc
Dear Bioconductors,
Somewhere in August S4Vectors stopped installing correctly resulting in a:
Creating a generic function for ‘nchar’ from package ‘base’ in package
‘S4Vectors’
message (that cannot be suppressed) each time the package is loaded. The
issue is not fixed by a fresh reinstall of bi
Hi All,
I am developing a package for Bioconductor 3.0. I "import" on a number of
packages:
methods GenomicRanges rtracklayer BiocParallel GenomicFiles GenomicFeatures
I noticed that depending on the order by which these packages are
library'ed the code
summary(someBigWigFileViewObject, type="m