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
Warnings when reloading packages with S4 classes #141
Comments
Fixed and merged in 9330614. A second part needed fixing, at f57967a. I changed it use importing code from Now the DESCRIPTION file isn't used to actually import packages, although it is still used to check version numbers. |
Winston, What was up here? I'm getting some of the behavior you describe above:
It's spooky that a date is involved, but I'm guessing that it's not a lubridate thing. Also, the warning message does not always appear, and it sometimes appears for |
Oh yeah, I've seen this again recently. The date isn't a lubridate thing - I believe it has something to do with R's handing of |
Garrett - which package are you using when you see this? With Shiny, this warning comes up now when you reload a package. It was introduced in rstudio/shiny@8d8ea53, The problem is |
One more thing I just remembered: John Chambers suggests putting methods into the Depends field instead of importing it. It's the third message in this thread: |
Winston, I was using lubridate, of course :) It's good to know that we can trace the problem to Is there an alternative way to use methods and pass CRAN's check? |
I'm thinking now that you can leave |
Does this still happen? Or is it fixed in recent R? |
The "Created package name" warning seems to be gone on R 3.0.3, and R-devel (from about two weeks ago). @garrettgman A heads up: on R-devel, I see these messages after the tests (but not on R 3.0.3):
|
I get these warnings error when loading lubridate.
I think there are two issues.
unloadNamespace -> cacheMetaData -> .getGenerics -> .removeSuperclassBackRefs
unloadNamespace -> cacheMetaData -> .getGenerics -> .removeSuperclassBackRefs -> findClass
, but I'm not yet sure where.The first type of of warning only happens the second time a package is loaded with
load_all(, TRUE)
. The second type of warning seems to happen every time except the first.The package seems to work, though -- it passes all tests.
The text was updated successfully, but these errors were encountered: