We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This works:
print(getNamespaceVersion("base"))
version "3.5.3"
However getNamespaceVersion on Renjin extensions returns NULL e.g.
> library("assertthat") Loaded org.renjin.cran.assertthat version 0.2.1-b10. > print(getNamespaceVersion("assertthat")) NULL
I have tried with several of my own packages as well with the same (NULL) result (both when specifying the groupId and not, e.g.
> library("se.alipsa:xmlr") Loaded se.alipsa.xmlr version 0.2.1. > print(getNamespaceVersion("xmlr")) NULL > print(getNamespaceVersion("se.alipsa:xmlr")) NULL
The same code in GNU R (3.6.3) results in:
> library("xmlr") > print(getNamespaceVersion("xmlr")) version "0.1.0"
Result is the same on Renjin Console and when running from the Scripting Engine.
Tested on Renjin versions 3.5-beta76 and master branch as of 2022-Jan-12.
The text was updated successfully, but these errors were encountered:
On a similar note:
print(installed.packages(fields = c ("Package", "Version")))
Does not list any Renjin Extensions, only base stuff such as stats, stats4, graphics etc.
Sorry, something went wrong.
This is probably related to issue #483
No branches or pull requests
This works:
print(getNamespaceVersion("base"))
However getNamespaceVersion on Renjin extensions returns NULL e.g.
I have tried with several of my own packages as well with the same (NULL) result (both when specifying the groupId and not, e.g.
The same code in GNU R (3.6.3) results in:
Result is the same on Renjin Console and when running from the Scripting Engine.
Tested on Renjin versions 3.5-beta76 and master branch as of 2022-Jan-12.
The text was updated successfully, but these errors were encountered: