On Sun, Jan 6, 2013 at 2:25 PM, Nick Hall <nick__hall@hotmail.com> wrote:
On 05/01/13 18:19, Doug Blank wrote:
Perhaps we should check the timestamp on const.py and compare to const.py.in and if newer, at least give a warning? I know I have forgotten too.

This is quite a good idea.  The const.py.in file doesn't change much under normal development, but when it does it is easy to miss.

Perhaps I should have emailed the list?  We might be making quite a few changes to it though for the alpha releases.

Perhaps we can just start a new philosophy: if there is something that we can easily write code to check for and notify the user, let's do that. But if we can't, we'll email the list. I suspect that database upgrades are one set of changes that we haven't written code to check for proper version in the past and need to be more careful about notifications. (But I wouldn't complain if we had more fine-grained versioning on database changes, then checked for appropriate version, and then gave notifications/warnings/errors.)

The other option is to put const.py into version control. But, it seems that setup.py does a few things now that are necessary for running, and so the checks sound like a better idea.




Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
Gramps-devel mailing list