> Leo 4.11 final, build 5020, 2012-02-26 13:18:08 -0600 ...and why is the date from 2012?
Oh. We've been here before (including me!): Version numbers, again - https://groups.google.com/d/topic/leo-editor/bAoFMG-5sY8/discussion It looks like the intent of core/leoVersion.py is to: # First, try to get the version from the .bzr/branch/last-revision. # Next use bzr_version_info. # Finally, fall back to hard-coded values. So on my computer, the 1st test fails (dunno why, I'm running from bzr), so it falls back to reading bzr_version.py, which was last updated 2012 Feb 26, and that's what get's reported in the log pane. The hardcoded final fallback values in leoVersion are: static_version = 6240 static_date = "2013-11-06" version = "4.11 final" and in bzr_version.py: 'build_date': '2012-02-26 13:18:08 -0600', 'clean': None, 'date': '2012-02-26 13:17:52 -0600', 'revision_id': '[email protected]', 'revno': '5020' -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
