similar to: all.equal(data.frame(package_version()), ...) infinite recursion

Displaying 20 results from an estimated 6000 matches similar to: "all.equal(data.frame(package_version()), ...) infinite recursion"

2008 Feb 13
0
RFC for package PopCon: a popularity contest for R and packages
Hello all, I've developed a prototype package called PopCon (short for popularity contest), a package for tracking the popularity of R and its packages. I'd like this work to be similar in spirit to the Debian package popularity-contest: http://popcon.debian.org/. Once Popcon is loaded, it captures two kinds of information from the user and stores it into a cache: the names of the
2008 Feb 14
0
RFC for package PopCon: a popularity contest for R and packages
(I posted this to the R-devel list yesterday, but I thought others on this list would be interested, so sorry for those who get it twice.) Hello all, I've developed a prototype package called PopCon (short for popularity contest), a package for tracking the popularity of R and its packages. I'd like this work to be similar in spirit to the Debian package popularity-contest:
2013 Oct 03
1
version comparison puzzle
Can anyone explain what I'm missing here? max(pp1 <- package_version(c("0.99999911.3","1.0.4","1.0.5"))) ## [1] ?1.0.4? max(pp2 <- package_version(c("1.0.3","1.0.4","1.0.5"))) ## [1] ?1.0.5? I've looked at ?package_version , to no avail. Since max() goes to .Primitive("max") I'm having trouble figuring out
2013 Apr 16
1
testInstalledBasic / testInstalledPackages
Hi, I installed R 3.0.0 on a Windows 2008 Server. When I submitted the following code in R64, library(tools) testInstalledBasic(scope="devel") I get the following message in the R Console: > library(tools) > testInstalledBasic(scope="devel") running tests of consistency of as/is.* creating ?isas-tests.R? running code in ?isas-tests.R? comparing ?isas-tests.Rout? to
2024 Apr 25
1
Question regarding .make_numeric_version with non-character input
Hi Kurt, On 25 April 2024 at 08:07, Kurt Hornik wrote: | >>>>> Herv? Pag?s writes: | | > Hi Kurt, | > Is it intended that numeric_version() returns an error by default on | > non-character input in R 4.4.0? | | Dear Herve, yes, that's the intention. | | > It seems that I can turn this into a warning by setting | >
2014 Nov 26
0
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
Summary: I think you've found a bug. On 26/11/2014, 5:39 PM, Geoff Lee wrote: > Hi > > > > I'm still exploring the R programming universe, so if this is being asked in > the wrong place, or in the 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
2014 Nov 27
0
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
On 26/11/2014, 7:38 PM, Geoff Lee wrote: > Many thanks Duncan for the quick response. A little too quick, it seems... > > A bug is a relief in a way. I've been digging my way deeper into this (and > learning more as I go) for several days now - but it is a diversion from (a > diversion from) my main goal :-( > > Is there somewhere specific I should report or log the
2023 Jul 06
1
numeric_version doesn't like numeric versions anymore?
Dear R devs, I installed the recent devel R to test a package error when I intercept this warning when loading packages: ``` Warning in .make_numeric_version(x, strict, .standard_regexps()$valid_numeric_version) : invalid non-character version specification 'x' (type: double) ``` After a long debugging, I realize that `numeric_version` in base does not support numerical input x by
2014 Nov 26
3
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
Hi I'm still exploring the R programming universe, so if this is being asked in the wrong place, or in the 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
2014 Nov 27
0
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
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
2023 Apr 08
0
Time to add is.formula() to 'stats'?
I know that it has been discussed in the past, but I wanted to ask to revisit the idea of exporting is.formula <- function(x) inherits(x, "formula") from 'stats', parallel to is.data.frame() in 'base', given how widely formulae are used these days in conjunction with data frames, even outside of model fitting functions (e.g., for split-apply). One could argue
2014 Nov 27
2
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
Many thanks Duncan for the quick response. A bug is a relief in a way. I've been digging my way deeper into this (and learning more as I go) for several days now - but it is a diversion from (a diversion from) my main goal :-( Is there somewhere specific I should report or log the bug or will that happen from this mailing-list automatically? (I have seen the Bug Tracking link on the
2016 Feb 10
0
Method from package dependency is not updated due to lazy load?
Hi, not sure this is a bug or just an unavoidable undesirable side-effect -- or just me that does not do the right thing. Consider the code and output below. It creates 2 packages: * pkgA * pkgB that creates a method for a generic defined in pkgA Changes in a method for the generic in pkgA (after re-installing pkgA) are not reflected in pkgB, unless pkgB is re-installed against the new
2014 Nov 27
2
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
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 the code to see what the arguments
2010 Sep 07
0
Sexpr in package.Rd fails
If I f = function() {} package.skeleton("PkgA", "f", path="/tmp") and then edit man/PkgA-pacakge.Rd to read in part \description{ More about what it does (maybe more than one line) \Sexpr{1} } and then R CMD build PkgA I end up with Saving output to ?/tmp/PkgA/build/PkgA.pdf? ... Warning in file.create(to[okay]) : cannot create file
2015 Jul 03
1
Are downstream dependencies rebuilt when a package is updated on CRAN?
I was wondering: are the downstream dependencies of a package rebuilt when a package is updated on CRAN? (I'm referring to the binary packages, of course.) The reason I ask is because there are cases where this can cause problems. Suppose that when pkgB is built, it calls pkgA::makeClosure(), which returns a closure that refers to a function in pkgA. Suppose this code is in pkgA 1.0:
2014 Nov 27
1
Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
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
2024 Apr 27
1
max on numeric_version with long components
I've noticed something in R devel which seems a little off and not the behavior I see in 4.4.0 or earlier versions. With numeric_versions that have long (>8 digit) final components max and min return the first element and not the max or min: In devel: > max(numeric_version(c("1.0.1.100000000", "1.0.3.100000000", "1.0.2.100000000"))) [1] ?1.0.1.100000000?
2013 Aug 30
2
"False" warning on "replacing previous import" when re-exporting identical object
Hi, SETUP: Consider three packages PkgA, PkgB and PkgC. PkgA defines a generic function foo() and exports it; export(foo) PkgB imports PkgA::foo() and re-exports it; importFrom(PkgA, foo) export(foo) PkgC imports everything from PkgA and PkgB: imports(PkgA, PkgB) PROBLEM: Loading or attaching the namespace of PkgC will generate a warning: replacing previous import by
2014 Feb 21
0
instantiating a reference class with an initialize() method from .onLoad fails
PkgA has a single R/binding.R file containing .A <- setRefClass("A", methods=list(initialize=function(...) {})) .onLoad <- function(...) .A() A NAMESPACE with import(methods) exportClasses("A") and DESCRIPTION Package: PkgA Type: Package Title: Documenting reference classes Version: 0.0.1 Date: 2012-08-05 Author: Martin