-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
more complete version info #1351
Comments
Is there any use in providing not only |
What would be great is if every library or module can register a version number, so that versions can be managed in a uniform way. |
This seems like it should be integrated into require functionality, since that keeps track of what has and hasn't been loaded it should also keep track of what version was loaded. |
Now that packages have taken the Julia ecosystem by storm, let's revisit this and possibly scope it down a little. I suggest setting this pull request to track the creation of a To that end, the list that Jeff started with seems pretty good, with Julia's commit hash, BLAS name/version, cpu and platform identifies. I can't think of anything else that might be interesting, can anyone else? |
also potentially useful (in verbose mode):
|
As @vtjnash suggests:
Something like ver(), that provides more complete information, would probably be nice to add. I currently can think of the following to include:
uname -mprsv
The text was updated successfully, but these errors were encountered: