-
Notifications
You must be signed in to change notification settings - Fork 0
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
Move all packages from Depends to Imports #22
Comments
As an update, my recent PR reduces this to two packages in Depends: dplyr and tidyselect. I intentionally left tidyselect as-is because we currently have another PR that I think is related to it, and I wanted to reduce the chance of have any conflicts there. I also intentionally left dplyr as-is because R CMD check triggers a lot of "no visible global function definition" NOTEs. I think (but am not sure) that some of those are dplyr functions. |
Let's see:
... can we close this? |
My personal preference is to keep this open, and have it be the next thing I address in this repo. If you look at the DESCRIPTION file you'll see that there are still two packages listed in I know that you mentioned that you sometimes like to put packages in Also, when I run
These are related to this issue. In that I think we can really only safely move packages from Depends to Imports when R knows exactly which package we want it to use for a particular function call. And here |
This is a good question. A few years ago, IIRC, the team wanted folks to have a clean-ish session by default, such that you'd always need to invoke So I'm not yet persuaded that adding Let's pose the question "What should the team's default R environment look like?" to the current core team. We've had some new hires, some training, and some retirements in the past few years. So there may be some new perspectives and/or preferences. |
When you run R CMD CHECK you get this NOTE:
Depends is somewhat dangerous, because forces the package to be loaded. This means that if someone is working locally, they might have their existing function / data names overridden when they load your package. Even worse, we don't control the packages we are loading. So after a call to
update.packages()
, people might get different results when they reload the package.Fixing this, I believe, requires us to first fix #21. The reason is that if we move something from Depends to Imports now, and our namespace does not declare a specific
importFrom
call in the NAMESPACE file, R CMD CHECK will create a fatal error and crash. So we must first ensure that we are explicitly importing all necessary functions from each package. Then we can move the packages to Imports.The text was updated successfully, but these errors were encountered: