similar to: Programming Tools CTV

On Thu, Jan 22, 2015 at 12:45 PM, Achim Zeileis <Achim.Zeileis at uibk.ac.at> wrote: > On Thu, 22 Jan 2015, Max Kuhn wrote: > >> I've had a lot of requests for additions to the reproducible research >> task view that fall into a grey area (to me at least). >> >> For example, roxygen2 is a tool that broadly enable reproducibility >> but I see it more as

On Thu, Jan 22, 2015 at 1:05 PM, Achim Zeileis <Achim.Zeileis at uibk.ac.at> wrote: > On Thu, 22 Jan 2015, Max Kuhn wrote: > >> On Thu, Jan 22, 2015 at 12:45 PM, Achim Zeileis >> <Achim.Zeileis at uibk.ac.at> wrote: >>> >>> On Thu, 22 Jan 2015, Max Kuhn wrote: >>> >>>> I've had a lot of requests for additions to the

On Thu, 22 Jan 2015, Max Kuhn wrote: > I've had a lot of requests for additions to the reproducible research > task view that fall into a grey area (to me at least). > > For example, roxygen2 is a tool that broadly enable reproducibility > but I see it more as a tool for better programming. I'm about to check > in a new version of the task view that includes packrat and

On Thu, 22 Jan 2015, Max Kuhn wrote: > On Thu, Jan 22, 2015 at 12:45 PM, Achim Zeileis > <Achim.Zeileis at uibk.ac.at> wrote: >> On Thu, 22 Jan 2015, Max Kuhn wrote: >> >>> I've had a lot of requests for additions to the reproducible research >>> task view that fall into a grey area (to me at least). >>> >>> For example, roxygen2 is

I second the motion for a Programming Tools CRAN Task View. I would also think it could contain things like Rcpp, R6, etc. -Greg > On Jan 22, 2015, at 10:20 AM, Max Kuhn <mxkuhn at gmail.com> wrote: > > I've had a lot of requests for additions to the reproducible research > task view that fall into a grey area (to me at least). > > For example, roxygen2 is a tool

Changing the vapply() behavior makes sense in principle. I analyzed the CRAN code base using the R parser and found 143 instances of calling vapply with USE.NAMES=FALSE. These would need to be inspected to understand the consequences of the change. For reference: /AzureML/R/datasets.R:226 /BBmisc/R/toRangeStr.R:33 /DBI/R/DBDriver.R:205 /Kmisc/R/str_rev.R:37 /Matrix/R/diagMatrix.R:98

Hi, Both vapply() and sapply() support the 'USE.NAMES' argument. According to the man page: USE.NAMES: logical; if ?TRUE? and if ?X? is character, use ?X? as ?names? for the result unless it had names already. But if 'X' has names already and 'USE.NAMES' is FALSE, it's not clear what will happen to the names. Are they going to propagate to the result

Hi all, Sorry if this doesn't end up in the thread. Tobias Verbeke forwarded that e-mail to me, because he thought I would be interested in maintaining the Programming Tools CTV. I wasn't subscribed to R-devel yet, but I would indeed like to volunteer to maintain the Programming Tools CTV. It will be my first time creating a CTV, so some guidance on getting it setup will be appreciated.

Dear Willem, Personally, I use the R-forge project for the distribution CTV : https://r-forge.r-project.org/projects/ctv/ It?s an alternative option to github. Regards, Christophe --------------------------------------- Christophe Dutang LMM, UdM, Le Mans, France web: http://dutangc.free.fr Le 23 janv. 2015 ? 12:49, Luca Braglia <lbraglia at gmail.com> a ?crit : > Hi Willem >

Hello everybody, as a young/unexperienced R package developer (only a few, mainly for personal use) i was thinking it could be very useful having a "meta" task view for all package-development related packages and/or function. Something like ... Creation - utils::package.skeleton, pkgKitten, Rcpp::Rcpp.package.skeleton Foreign languages interfaces: - Rcpp Documentation - roxygen2

I'd strongly second the notion of using github. The biggest advantage is that others can easily contribute changes through pull requests which lifts much of the burden from your shoulders. Hadley On Fri, Jan 23, 2015 at 3:49 AM, Luca Braglia <lbraglia at gmail.com> wrote: > Hi Willem > > thanks for volounteering. > > To the best of my knowledge (regarding the machinery

Hi Willem thanks for volounteering. To the best of my knowledge (regarding the machinery side), if you're planning to use github (and maybe even if you don't) you can "stole" ideas from https://github.com/ropensci/webservices https://github.com/lbraglia/PackageDevelopmentTaskView (minor modifications from webservices) https://github.com/eddelbuettel/ctv-finance or

Dear R-devs, Scenario: When checking a package via `R CMD check package_tar.ball`, required / suggested packages may be missing. R subsequently returns a list of packages that are missing (delimited by spaces). Example: ``` R CMD check glmSparseNet_0.99.13.tar.gz * using log directory '/home/ubuntu/Bioconductor/glmSparseNet.Rcheck' * using R Under development (unstable) (2018-06-06

Hi, Which is the best way to use unit tests as examples for documentation? I use testthat, but if there is a good way to do this, for example, only with RUnit, it'd still be good to know. Unit-tests are usually simple and concise, so they are good candidates for example code, but I don't want to copy them into documentation and maintain by hands. I tried to google how people handle this,

Dear R experts--- after many years, I am planning to give in and write my first R package. I want to combine my collection of collected useful utility routines. as my guide, I am planning to use Friedrich Leisch's "Creating R Packages: A Tutorial" from Sep 2009. Is there a newer or better tutorial? this one is 4 years old. I also plan on one change---given that the

On Friday, 26 June 2020 10.47.13 WEST I?aki Ucar wrote: > I used bcond locally and wrongly assumed that fedpkg build would > support --with BCOND and --without BCOND. Instead, the way to activate > it is to change to "%bcond_with check" and then revert to > "%bcond_without check". The only difference with bootstrap is that > "bootstrap" is recognized

Hi the reference to R Internals https://cran.r-project.org/doc/manuals/r-release/R-ints.html#Tools in ?check (PkgUtils.Rd in utils package) is stale. Here is my proposed patch (use named reference rather than numeric reference to avoid any similar broken links in the future). Index: src/library/utils/man/PkgUtils.Rd =================================================================== ---

library("lintr") Error: package or namespace load failed for 'lintr' in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]): there is no package called 'magrittr' library("magrittr") Error in library("magrittr") : there is no package called 'magrittr' session.Info(): R version 3.4.4 (2018-03-15) Platform:

>>>>> Jeroen Ooms <jeroenooms at gmail.com> >>>>> on Wed, 20 Jul 2016 10:26:19 +0200 writes: > On Tue, Jul 19, 2016 at 6:46 PM, Kevin Ushey <kevinushey at gmail.com> wrote: >> R fails to install a package from source over a pre-existing package >> when the path to that package is a symlink, rather than a directory.

I've inherited a large R codebase which has grown over a few years and a few different developers. It contains many things I'd like to delete: - Unused functions - Variable definitions that are never called - Unreachable code I'd write that myself, it would even be fun, but I don't want to reinvent the wheel. Is there an R package that can find these things? I've heard of