Thanks for delineating r-devel vs this list, Ben, and for invitation to start a
fresh convo over there.
I'll do that once I can exhibit a basic proposal functioning within package
'precautionary'.
Best, David
From: R-package-devel on behalf of Ben
Bolker
Date: Friday, July 23, 2021 at 1:29 PM
Patches to parallel could certainly be *considered*, but people will
probably want to argue about the details quite a bit. I would suggest
presenting/discussing your ideas for modification on r-devel before
posting them as a 'wishlist' item to the R bug tracker. (If an R-core
member particip
My understanding about this issue with progressr is that it is nontrivial, and
will take author Henrik Bengtsson some time & thought to resolve.
OTOH if patches to 'parallel' were welcome, I could embed my solution in a
modified version of parallel::mclapply by introducing 1 or 2 new parameters
On 23/07/2021 11:36 a.m., Skye Bender-deMoll wrote:
Dear CRAN devs
I've recently run into some testing issues when attempting to release
fixes for the ndtv package on CRAN.
1) I have examples in documentation that test the ability of the package
to export files, but the creation of these files
Dear CRAN devs
I've recently run into some testing issues when attempting to release
fixes for the ndtv package on CRAN.
1) I have examples in documentation that test the ability of the package
to export files, but the creation of these files then results in a NOTE
from testing.
For exampl
On 23/07/2021 10:59 a.m., Hugh Parsonage wrote:
Happily, package parallel is open-source. If you would like to make
use of the unexported functions, you could copy the source code with
acknowledgement into your package.
There's a good chance that wouldn't work, because parallel is a base
packa
Happily, package parallel is open-source. If you would like to make
use of the unexported functions, you could copy the source code with
acknowledgement into your package. Naturally this might be a lot of
work and risks different behaviour between your package and parallel,
but neither might be tha
I can confirm that getFromNamespace() does indeed circumvent the WARNING.
I might otherwise prefer ':::', however, for making its 'bad intentions' so
clear.
I was very much aware of the cautionary language under `?readChild`, but
wondered whether *in practice* more liberal community policies migh
Am 23.07.21 um 13:19 schrieb David Norris:
Because parallelized progress reporting in the futureverse.org incurs latencies
too great for my application
(https://github.com/HenrikBengtsson/progressr/issues/118), I have found it
necessary to implement my own progress reporting using some of the
AFAIK, you may use getFromNamespace to import non-exported function (e.g.
readChild <- getFromNamespace("readChild", "parallel") )
Although, I never use it myself for a package on CRAN
Concerning the unix only part, I don't know if it is acceptable or not,
If not, maybe it could be a good idea to
Because parallelized progress reporting in the futureverse.org incurs latencies
too great for my application
(https://github.com/HenrikBengtsson/progressr/issues/118), I have found it
necessary to implement my own progress reporting using some of the non-exported
functionality from `parallel`.
11 matches
Mail list logo
