You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_ _ _(_)_ | A fresh approach to technical computing
(_) | (_) (_) | Documentation: http://docs.julialang.org
_ _ _| |_ __ _ | Type "help()" to list help topics
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 0.2.0-1194.r608185cf
_/ |\__'_|_|_|\__'_| | Commit 608185cf39 2013-04-25 02:18:30
|__/ |
It would be nice if VERSION includes something that says that this is the development version.
It would also be nice to have some query functions like isreleased() that can say whether one is running a released version of julia or a development version.
The text was updated successfully, but these errors were encountered:
Not exactly, but I think the current situation is better than it was. We have Base.BUILD_INFO.tagged_commit which will be changed to Base.GIT_VERSION_INFO.tagged_commit in #5095
The line specifying the commit is also removed in tagged versions, so that it is not obvious, but possible to see. I also think we have a better policy for updating the /VERSION file so that it says prerelease between releases.
Currently, the banner prints:
It would be nice if
VERSION
includes something that says that this is the development version.It would also be nice to have some query functions like
isreleased()
that can say whether one is running a released version of julia or a development version.The text was updated successfully, but these errors were encountered: