Dear Rainer,
It looks like you are using testthat. testthat has a skip_on_cran()
function. This will always skip the subsequent tests in the script unless
the environment variable NOT_CRAN is set.
Best regards,
Thierry
ir. Thierry Onkelinx
Statisticus / Statistician
Vlaamse Overheid / Governm
Correct - I should have thought that there is a Hadley-solution to this problem.
Thanks,
Rainer
> On 6 Sep 2018, at 09:25, Thierry Onkelinx wrote:
>
> Dear Rainer,
>
> It looks like you are using testthat. testthat has a skip_on_cran() function.
> This will always skip the subsequent tests
Dear CRAN
I have made a vignette and followed the instructions for adding a title and
name at the top of the vignette, the title and name appears locally when I
build it from RStudio. However, whenever it gets uploaded to CRAN, it is
not there in the online vignette. The rest of the vignette is fi
On 06/09/2018 6:26 AM, Christopher John wrote:
Dear CRAN
I have made a vignette and followed the instructions for adding a title and
name at the top of the vignette, the title and name appears locally when I
build it from RStudio. However, whenever it gets uploaded to CRAN, it is
not there in th
On Wed, Sep 5, 2018 at 3:03 PM Duncan Murdoch wrote:
>
> On 05/09/2018 2:20 PM, Henrik Bengtsson wrote:
> > I take a complementary approach; I condition on, my home-made,
> > R_TEST_ALL variable. Effectively, I do:
> >
> > if (as.logical(Sys.getenv("R_TEST_ALL", "FALSE"))) {
> > ...
> > }
> >
Hi,
I would like to change the default value of some arguments of some
functions in a package of mine. I don't want to change explicitly the
calls in the many scripts that have been written. For example, I would
to change the delimiter in all write.mytable() without changing any
calls it and
Dear Samuel,
Many may object (for good reasons) that adding options would clash with
functional paradigm, but it is possible.
I don't know about the least worse practice but as far as I would do it,
you could:
1. directly write and then read elements in the (hidden) list .Options that
is present
Hi all,
A simple solution - if indeed you want to go down this route - is to use
options() and getOption(), ensuring all options are namespaced, e.g. by
prefixing them with the package name.
David
On Thu, 6 Sep 2018 at 17:15, Alexandre Courtiol <
alexandre.court...@gmail.com> wrote:
> Dear Samu
{Sorry this is long, just trying to be clear and thorough.}
I'm struggling a bit with some CRAN recommendations; would appreciate
opinions/suggestions about how other people would handle this case.
I'm working on a package (https://github.com/bbolker/broom.mixed) that
processes model fits f
On 09/07/2018 04:15 AM, Alexandre Courtiol wrote:
you could:
1. directly write and then read elements in the (hidden) list .Options that
is present in the global environment:
Point of order Mr. Chairman (and I'm pretty sure it doesn't matter a
damn) but (on my system at least) .Options i
On 06/09/2018 10:32 AM, Hadley Wickham wrote:
On Wed, Sep 5, 2018 at 3:03 PM Duncan Murdoch wrote:
On 05/09/2018 2:20 PM, Henrik Bengtsson wrote:
I take a complementary approach; I condition on, my home-made,
R_TEST_ALL variable. Effectively, I do:
if (as.logical(Sys.getenv("R_TEST_ALL", "F
On Fri, 7 Sep 2018 at 01:16, Duncan Murdoch
wrote:
>
>
> When packages delete tests just for CRAN, the quality of the repository
> suffers. Users should be able to check an install by running the tests
> that passed on CRAN and seeing them pass on their system as well.
In my limited experience
12 matches
Mail list logo