On Fri, 21 Nov 2014 08:59:36 -0800 (PST)
Davy Cottet <cottet.d...@gmail.com> wrote:
> Is there many part of the code using folder and file structure to
> store information ?
> If it is only the case for leoVersion.py maybe an alternative would
> be to store last commit and git information as a module or pickle ?
so instead of leo/core/commit_timestamp.json
{
"asctime": "Fri Nov 21 08:48:19 CST 2014",
"timestamp": "20141121084819"
}
we could have leo/core/commit_timestamp.py
LEO_VERSION = {
"asctime": "Fri Nov 21 08:48:19 CST 2014",
"timestamp": "20141121084819",
"release": "Leo 5.2"
}
although that would be a bit more putzy because the bash code which
updates (even on windows) the commit_timestamp.json would have to get
the release info. from somewhere.
Maybe this would be The Simplest Thing That Can Possibly Work(TM)
:-) -
Switch from commit_timestamp.json to commit_timestamp.py but put only
LEO_COMMIT = {
"asctime": "Fri Nov 21 08:48:19 CST 2014",
"timestamp": "20141121084819"
}
in there and continue getting the release info. from where ever it's
coming from now, presumably a .py file.
Cheers -Terry
--
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
