similar to: head/tail breaking change

Displaying 20 results from an estimated 7000 matches similar to: "head/tail breaking change"

2019 Dec 19
1
head/tail breaking change
Thank you Gabriel, I agree that new behaviour makes much more sense. Just wanted to confirm before resolving compatibility of my unit tests. Best, Jan On Wed 18 Dec, 2019, 10:46 PM Gabriel Becker, <gabembecker at gmail.com> wrote: > Jan, > > That is an intentional change as you can see in the documentation for > head/tail in R-devel. Last time I discussed it with Martin, this
2019 Dec 18
0
head/tail breaking change
Jan, That is an intentional change as you can see in the documentation for head/tail in R-devel. Last time I discussed it with Martin, this behavior was desired and thus is unlikely to change unless "our" (ie his) mind does. The hope is that the new behavior is actually what people would want (note it already behaves this way for data.frames and for matrices, which are now explicitly
2020 Mar 30
1
is.vector could handle AsIs class better
Thank you Gabriel, Agree, although I think that could be relaxed in this single case and AsIs class could be ignored. Best, Jan On Sun, Mar 29, 2020 at 7:09 PM Gabriel Becker <gabembecker at gmail.com> wrote: > > Jan, > > I believe it's because it has "a non-NULL attribute other than names" as per the documentation. In this case its class of "AsIs". >
2022 Oct 29
1
tools:: extracting pkg dependencies from DCF
Thank you Gabriel, Just for future readers. Below is a base R way to address this common problem, as instructed by you (+stopifnot to suppress print). Rscript -e 'stopifnot(file.copy("DESCRIPTION", file.path(tdir<-tempdir(), "PACKAGES"))); db<-available.packages(paste0("file://", tdir));
2020 Mar 29
2
is.vector could handle AsIs class better
Dear R-devel, AsIs class seems to be well handled by `typeof` and `mode` function. Those two functions are being referred when explaining `is.vector` behaviour in manual. Yet `is.vector` does not seem to be handling AsIs class the same way. is.vector(1L) #[1] TRUE is.vector(I(1L)) #[1] FALSE Is there any reason behind this behaviour? Could we have it supported so AsIs class is ignored when
2016 Nov 17
1
new function to tools/utils package: dependencies based on DESCRIPTION file
Hi Michael, Are you willing to accept patch for this? I'm already using this and few related functions for a while, it plays well. I could wrap it as patch to utils, or tools? Best, Jan On 16 June 2016 at 14:00, Michael Lawrence <lawrence.michael at gene.com> wrote: > I agree that the utils package needs some improvements related to > this, and hope to make them eventually. This
2016 Jun 16
3
new function to tools/utils package: dependencies based on DESCRIPTION file
Dear Joris, So it does looks like the proposed function makes a lot sense then, isn't it? Cheers, Jan On 16 June 2016 at 08:37, Joris Meys <jorismeys at gmail.com> wrote: > Dear Jan, > > It is unavoidable to have OS and R dependencies for devtools. The building > process for packages is both OS and R dependent, so devtools has to be too > according to my understanding.
2020 Jun 29
2
R-devel internal errors during check produce?
>>>>> Jan Gorecki writes: > So the unique.default is from the R tools package during checks. > I don't see those issues on CRAN checks. I cannot reproduce this locally (and have no clues about docker). Perhaps you can try to debug this on your end? And see what env_list is when the error occurs? Best -k > Exact environment where I am reproducing this issue is a
2016 Nov 03
2
Running package tests and not stop on first fail
Hi Martin, Jan, On 11/03/2016 03:45 AM, Martin Maechler wrote: >>>>>> Jan Gorecki <J.Gorecki at wit.edu.pl> >>>>>> on Tue, 1 Nov 2016 22:51:28 +0000 writes: > > > Hello community/devs, Is there an option to run package > > tests during R CMD check and not stop on first error? I > > know that testing frameworks (testhat
2016 Nov 04
4
Running package tests and not stop on first fail
>>>>> Jan Gorecki <J.Gorecki at wit.edu.pl> >>>>> on Fri, 4 Nov 2016 11:20:37 +0000 writes: > Martin, I submitted very simple patch on > https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17176 > Herve, While I like your idea, I prefer to keep my patch > simple, it is now exactly what Martin mentions. I think it > is a
2020 Jun 29
2
R-devel internal errors during check produce?
Thank you both, You are absolutely correct that example should be minimal, so here it is. l = list(a=new.env(), b=new.env()) unique(l) Just for completeness, env_list during check that raises error env_list <- list(baseenv(), as.environment("package:graphics"), as.environment("package:stats"), as.environment("package:utils"),
2020 May 17
2
order function called on a data.frame?
Hi, base::order main input arguments are defined as: a sequence of numeric, complex, character or logical vectors, all of the same length, or a classed R object When passing a list or a data.frame, the resuts seems to be a bit useless. Shouldn't that raise an error, or at least warning? Best Regards, Jan Gorecki
2020 May 18
2
order function called on a data.frame?
I guess we could make it do the equivalent of do.call(order, df). On Mon, May 18, 2020 at 8:32 AM Rui Barradas <ruipbarradas at sapo.pt> wrote: > > Hello, > > There is a result with lists? I am getting > > > order(list(letters, 1:26)) > #Error in order(list(letters, 1:26)) : > # unimplemented type 'list' in 'orderVector1' > >
2016 Nov 01
2
Running package tests and not stop on first fail
Hello community/devs, Is there an option to run package tests during R CMD check and not stop on first error? I know that testing frameworks (testhat and others) can do that but asking about just R and base packages. Currently when package check runs test scripts in ./tests directory it will stop after first fail. Do you think it could be optionally available to continue to run tests after
2020 Jun 26
2
R-devel internal errors during check produce?
Hi R developers, On R-devel (2020-06-24 r78746) I am getting those two new exceptions during R check. I found a change which eventually may be related https://github.com/wch/r-source/commit/69de92b9fb1b7f2a7c8d1394b8d56050881a5465 I think this may be a regression. I grep'ed package manuals and R code for unique.default but don't see any. Usage section of the unique method looks fine as
2023 Nov 24
1
tune "checking installed package size" NOTE
? Fri, 24 Nov 2023 12:15:06 +0100 Jan Gorecki <j.gorecki at wit.edu.pl> ?????: > Recently we got _R_CHECK_CRAN_INCOMING_TARBALL_THRESHOLD_ env var to > tune "Size of tarball" note during R package check. > > Could we get similar one for tuning "checking installed package size" > note? Does _R_CHECK_PKG_SIZES_THRESHOLD_ (in megabytes) work for you? It can
2019 Nov 01
4
[External] R C api for 'inherits' S3 and S4 objects
Thank you Luke. That is why I don't use Rf_inherits but INHERITS which does not allocate, provided in the email body. I cannot do similarly for S4 classes, thus asking for some API for that. On Fri, Nov 1, 2019 at 5:56 PM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > On Fri, 1 Nov 2019, Jan Gorecki wrote: > > > Dear R developers, > > > > Motivated by
2020 May 23
1
base::order breaking change in R-devel
Hi R developers, There seems to be breaking change in base::order on Windows in R-devel. Code below yields different results on R 4.0.0 and R-devel (2020-05-22 r78545). I haven't found any info about that change in NEWS. Was the change intentional? Sys.setlocale("LC_CTYPE","C") Sys.setlocale("LC_COLLATE","C") x1 = "fa\xE7ile" Encoding(x1) =
2016 Jun 14
5
new function to tools/utils package: dependencies based on DESCRIPTION file
Hi all, Packages tools and utils have a lot of useful stuff for R developers. I find one task still not as straightforward as it could. Simply to extract dependencies of a package from DESCRIPTION file (before it is even installed to library). This would be valuable in automation of CI setup in a more meta-data driven way. The simple function below, I know it is short and simple, but having it to
2022 Oct 13
1
tools:: extracting pkg dependencies from DCF
Dear R devs, I would like to raise a request for a simple helper function. Utility function to extract package dependencies from DESCRIPTION file. I do think that tools package is better place, for such a fundamental functionality, than community packages. tools pkg seems perfect fit (having already great function write_PACKAGES). Functionality I am asking for is already in R svn repository