search for: loadnamespac

This is an enquiry not so much about what the code for loadNamespace does, but rather about the intent and design of loadNamespace, and how it interacts with the `::` function, which seems to me to follow a slightly different philosophy. It is not an urgent question - the issue that started me wondering has been resolved another way - but I would like to complet...

Hi Duncan The difference is that in your call to loadNamespace, the versionCheck list has 3 components (name, op and version), whereas the documentation only mentions 2 (op and version). loadNamespace 'works' for me provided I add a third component to the list (even a nonsense one). What I haven't yet had the fortitude to do is track down through...

Hi Duncan, Many thanks (yet again). With the hint given by your earlier email (viz that currently loadNamespace expects a 3rd component called name in the list that is used for the versionCheck argument) I had another look at what was going on with my toy examples yesterday evening. I'm still working on my issue, but thus far I have: 1) Confirmed that internal calls to loadNamespace triggered by impor...

...be imported' package1 installed in my .libPath(). It was only when I simulated a user who has and older version of the Imported package1 (by overwriting the later version of package 1 with an earlier version), then trying to load or attach package2 that the (failure of the version checking) at loadNamespace time for package1 became apparent (well apparentish after quite a bit of digging) -----Original Message----- From: Duncan Murdoch [mailto:murdoch.duncan at gmail.com] Sent: Thursday, 27 November 2014 10:57 AM To: Geoff Lee; r-devel at r-project.org Subject: Re: [Rd] Problem understanding behavio...

...e wrong way (e.g. too verbose or lacking in crucial detail or in the wrong format) please let me know I am trying to understand when the version constraints for packages which appear in the Imports field of a DESCRIPTION file are checked. Along the way I've hit a snag understanding what loadNamespace with the versionCheck argument set does. The core of my query is 'am I doing something wrong, or have I stumbled across a bug?'. Probably the former, but after several days I still can't figure it out, so any guidance, hints or outright help would be much appreciated. Thanks in a...

On 26/11/2014, 8:29 PM, Geoff Lee wrote: > Hi Duncan > > The difference is that in your call to loadNamespace, the versionCheck list > has 3 components (name, op and version), whereas the documentation only > mentions 2 (op and version). > loadNamespace 'works' for me provided I add a third component to the list > (even a nonsense one). > > What I haven't yet had the fortitu...

...et of steps to illustrate a bug, then reporting on bugs.r-project.org is the way to get it recorded. Reporting it on this list is really hit and miss. But I think from your previous description, something else is going on. When I try to load a namespace with a bad version number, I get an error: loadNamespace("rgl", versionCheck=list(name="rgl", op=">", version=package_version('3.0'))) Error in loadNamespace("rgl", versionCheck = list(name = "rgl", op = ">", : namespace ?rgl? 0.95.1163 is being loaded, but > 3.0 is required...

...e checked. I would have assumed they are checked when you try to install the package. If you ask for version 3.0, and only have 0.3, the install should fail. But as you've found, the documents say something else... > > > > Along the way I've hit a snag understanding what loadNamespace with the > versionCheck argument set does. The core of my query is 'am I doing > something wrong, or have I stumbled across a bug?'. Probably the former, > but after several days I still can't figure it out, so any guidance, hints > or outright help would be much apprecia...

Dear all, in our current setting we have our packages stored on a (rather slow) network drive and need to invoke short R scripts (using RScript) in a timely manner. Most of the script's runtime is spent with package loading using library() (or loadNamespace to be precise). Is there a way to cache the package namespaces as listed in loadedNamespaces() and load them into memory before the script is executed? My first simplistic attempt was to serialize the environment output from loadNamespace() to a file and load it before the script is started. How...

Hello R Community, I inadvertently updated packages via R Studio when a package was open. Now when R Studio is opened the message below appears in the console panel. Error in loadNamespace(name) : there is no package called ?yaml? Error in loadNamespace(name) : there is no package called ?yaml? When running R code, so far the only function that has not worked is datatable () in the ?DT? package. Removing the ?DT? package and reinstalling it had no effect. A possible fix is to up...

> On Dec 7, 2017, at 10:47 AM, James Henson <jfhenson1 at gmail.com> wrote: > > Hello R Community, > > I inadvertently updated packages via R Studio when a package was open. Now > when R Studio is opened the message below appears in the console panel. > > Error in loadNamespace(name) : there is no package called ?yaml? > > Error in loadNamespace(name) : there is no package called ?yaml? > > When running R code, so far the only function that has not worked is > datatable () in the ?DT? package. Removing the ?DT? package and > reinstalling it had no ef...

...4/10/2016 1:51 PM, Kevin Ushey wrote: >> Hi R-devel, >> >> One of the more common issues that new R users see, and become stumped >> by, is error messages during package load of the form: >> >> > library(ggplot2) >> Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), >> versionCheck = vI[[j]]) : >> there is no package called 'Rcpp' >> Error: package or namespace load failed for 'ggplot2' >> >> Typically, error messages of this form are caused simply by...

Hi R-devel, One of the more common issues that new R users see, and become stumped by, is error messages during package load of the form: > library(ggplot2) Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]) : there is no package called 'Rcpp' Error: package or namespace load failed for 'ggplot2' Typically, error messages of this form are caused simply by one or more dependent packages (in this case, 'Rcpp') n...

Hi I?ve just spend a bit of time debugging an error arising in `loadNamespace`. The bottom line is that the `vI` object is assigned within an `if` block but expected to exist for all of the remaining code. In some cases where the package library has been corrupted or when it resides on a network drive with bad connection this can lead to error messages complaining about `vI...

...17/12/2015 9:06 AM, Michael Felt wrote: > More experimenting with calling commands: > > tools:::foobar() > Error: Line starting 'Package: tools ...' is malformed! > > tools::foobar() > Error: Line starting 'Package: tools ...' is malformed! These both do a loadNamespace("tools"). > > Tools:::foobar() > Error in loadNamespace(name) : there is no package called 'Tools' > > loadNamespace(tools) > Error in loadNamespace(tools) : object 'tools' not found Those are expected, and unrelated. > > loadNamespace(&qu...

...type: openVignette() For details on reading vignettes, see the openVignette help page. > conflicts() [1] "last.warning" "degree" "body<-" "print" "split" [6] "union" > sna::degree() Error in loadNamespace(name) : package 'sna' does not have a name space > graph::degree() Error in loadNamespace(name) : package 'graph' does not have a name space > sna:::degree Error in loadNamespace(name) : package 'sna' does not have a name space > graph:::degree Error in loadNamespa...

>>>>> Thomas Lin Pedersen <thomasp85 at gmail.com> >>>>> on Mon, 22 Jan 2018 14:32:27 +0100 writes: > Hi I?ve just spend a bit of time debugging an error > arising in `loadNamespace`. The bottom line is that the > `vI` object is assigned within an `if` block but expected > to exist for all of the remaining code. In some cases > where the package library has been corrupted or when it > resides on a network drive with bad connection this can >...

...gmail.com> wrote: > Dear all, > > in our current setting we have our packages stored on a (rather slow) > network drive and need to invoke short R scripts (using RScript) in a > timely manner. Most of the script's runtime is spent with package loading > using library() (or loadNamespace to be precise). > > Is there a way to cache the package namespaces as listed in > loadedNamespaces() and load them into memory before the script is executed? > > My first simplistic attempt was to serialize the environment output > from loadNamespace() to a file and load it befor...

...l.com> wrote: > > Dear all, > > in our current setting we have our packages stored on a (rather slow) > network drive and need to invoke short R scripts (using RScript) in a > timely manner. Most of the script's runtime is spent with package loading > using library() (or loadNamespace to be precise). > > Is there a way to cache the package namespaces as listed in > loadedNamespaces() and load them into memory before the script is executed? > > My first simplistic attempt was to serialize the environment output > from loadNamespace() to a file and load it befor...

Dear list, Iget the following error message: > help.search("omit.na") Error in loadNamespace(name) : package 'tools' does not have a name space I do not quite understand what it means in this case. Is something corrupt in the installation? I run R-1.8.1 in Linux RedHat 9 with kernel 2.6.2 on Intel P4. Regards, Ulrich -- __________________________________________________ Ul...