search for: numeric_versions

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? > max(numeric_version(c("1.0.1.1000...

? Sat, 27 Apr 2024 13:56:58 -0500 Jonathan Keane <jkeane at gmail.com> ?????: > In devel: > > max(numeric_version(c("1.0.1.100000000", "1.0.3.100000000", > "1.0.2.100000000"))) > [1] ?1.0.1.100000000? > > max(numeric_version(c("1.0.1.10000000", "1.0.3.10000000", > "1.0.2.10000000"))) > [1]

I mean the `numeric_version` object not a numeric (double/int). Basically to protect me from myself I'd prefer not to have to remember to wrap `getNamespaceVersion()` with `as.package_version()`. I suspect a grep of CRAN may highlight others who are erroneously comparing character objects rather than a comparison between a `numeric_version` object and a character. Tim On 17/10/2024

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

On 17/10/2024 13:42, Tim Taylor wrote: > I mean the `numeric_version` object not a numeric (double/int). > Basically to protect me from myself I'd prefer not to have to remember > to wrap `getNamespaceVersion()` with `as.package_version()`. > > I suspect a grep of CRAN may highlight others who are erroneously > comparing character objects rather than a comparison between

On 17 October 2024 at 12:38, Tim Taylor wrote: | Would R-Core be receptive to having getNamespaceVersion() return a | numeric_version object instead of a named character? Is this good enough? What's your actual issue a 'numeric' would address? > as.package_version(getNamespaceVersion("base")) < "4.5.0" [1] TRUE > >

Would R-Core be receptive to having getNamespaceVersion() return a numeric_version object instead of a named character? Tim

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

(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:

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

> is.na(strptime("5/2/1992", format="%m/%d/%Y")) [1] FALSE > is.na(strptime("5/3/1992", format="%m/%d/%Y")) [1] TRUE Any idea what's going on with this? Running strptime against all dates from around 1946, only 5/3/1992 was converted as "NA". Even stranger, it still seems to have a value associated with it (even though is.na thinks

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

In R 3.4.0 RC, argument list of 'c' as S4 generic function has become (x, ...) . However, "S4 methods" section in documentation of 'c' (c.Rd) is not updated yet. Also, in R 3.4.0 RC, 'c' method of class "Date" ('c.Date') is still not explicitly documented.

Hi Everybody, I am having a problem with loading Biobase package. I typed 2 lines below at R prompt > source ("http://boconductor.org/biocLite.R") > biocLite (lib="/usr/local/lib/R/library") which attempted to install a bunch of packages with varying degree of success. Out of 29, 13 failed. Biobase is one of them. As a matter of fact, when I looked at logs, most

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 | >

>>>>> 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 > _R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false but I don't > seem to be able to find any of this mentioned

I am seeing very strange behaviour in R 3.2.0 patched (r68272) and a new build of R-devel. The sessioninfo() from the former is below. Here's what I see: If I set the locale, and trigger a namespace load, a version comparison gives NA, and I get an error. For example, in a new session started with R --vanilla from the terminal: > Sys.setlocale(locale='en_US.UTF-8');grid::gpar()

Full_Name: Christian Brechbuehler Version: 2.7.2, 2.8.1 OS: linux-gnu Submission from: (NULL) (24.128.51.18) Calling [.data.frame on an object that's not a data frame, specifically 1:10, causes segmentation fault. Context ======= We can subscript with a number of different notations: > (1:10)[3] [1] 3 > do.call(get("[",pos="package:base"),list(1:10,3))

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

Hi Kurt, Is it intended that numeric_version() returns an error by default on non-character input in R 4.4.0? It seems that I can turn this into a warning by setting _R_CHECK_STOP_ON_INVALID_NUMERIC_VERSION_INPUTS_=false but I don't seem to be able to find any of this mentioned in the NEWS file. Thanks, H. On 4/1/24 05:28, Kurt Hornik wrote: >>>>>> Andrea Gilardi via