-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NOTICE: plan(multiprocess) of future is deprecated #13
Comments
@esnitkin914 could you assign this to whoever is going to maintain the package now? I think the best option is to delete the deprecated code and include documentation of how the user can call any sort of parallelization plan they want in their own script prior to running functions that can be parallelized. Here's an example explanation: http://www.schlosslab.org/mikropml/articles/parallel.html Once it's updated, the package will also have to be re-submitted to CRAN. |
Hello, just a friendly bump on this. It looks like this was fixed in the git repo (0bf01d3). What's missing is a CRAN release. |
Friendly reminder; 'multiprocess' has been deprecated since 2020-10-30. |
Last reminder. Very soon, your package will break and fall of CRAN when I release the updated version of future;
|
FYI, future 1.32.0 is now on CRAN making |
Thanks for letting us know! We're on it |
Hi.
This is a friendly reminder that
plan(multiprocess)
of the future package is deprecated since future 1.20.0 (2020-11-03). It will eventually become defunct and removed. The background for this can be found in futureverse/future#420.Your prewas package relies on
multiprocess
, cf. https://github.com/Snitkin-Lab-Umich/prewas/search?q=multiprocess.Please migrate your code to the platform-independent
plan(multisession)
or the Linux/macOS-specificplan(multicore)
. If you want to emulate whatmultiprocess
does, you can do something like:BTW, if you don't already do so, please make sure to undo any
plan()
you set in your code, as illustrated by the above example. This is needed to guarantee that calling your code won't override settings that the user has set previously. You can read about this in https://future.futureverse.org/reference/plan.html#for-package-developers.Thank you,
Henrik
(maintainer of the future package)
The text was updated successfully, but these errors were encountered: