-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Update info about versioninfo
in devdocs
#28810
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since?
doc/src/devdocs/backtraces.md
Outdated
@@ -16,9 +16,10 @@ and follow the instructions to generate the debugging information requested. Ta | |||
|
|||
No matter the error, we will always need to know what version of Julia you are running. When Julia | |||
first starts up, a header is printed out with a version number and date. Please also include the | |||
output of `versioninfo()` in any report you create: | |||
output of `versioninfo()` in any report you create (sinсe version 0.7.0 this function moved into [`InteractiveUtils`](@ref InteractiveUtils.versioninfo) module, so maybe you need import the module): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it really needed to describe the history of how this function has moved.
Something like
Please also include the output of
versioninfo()
(exported from theInteractiveUtils
standard library) in any report you create:
seems enough to me. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, history of versioninfo()
function is not necesarry.
Should I update message to your variant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, drop the historical comment. Someone using an old version can read the old docs.
(cherry picked from commit b411a58)
(cherry picked from commit b411a58)
(cherry picked from commit b411a58)
(cherry picked from commit b411a58)
Related: #28803