Hello Davide,

Thanks for the answer, but the question is about getting a clue on the IMP version I am running in my python environment. Which can be useful, for instance, to keep a trace of the IMP version with which an experiment was made, or simply to verify that I am really working with the latest version I compiled, and not with the old one :)

--Ben

> I don't know of that's what you mean, but have you tried with "svn info" from the imp root dir? > > Davide > > > Il giorno Oct 5, 2012, alle ore 9:24 AM, Benjamin SCHWARZ ha scritto: > >> In [2]: IMP.get_module_version() >> Out[2]: 'develop with Boost.FileSystem' >> >> I remember the good old times, when I could see the svn revision number for free. >> Is it hidden somewhere else nowadays ? >> >> --Ben (S.)

On Oct 5, 2012, at 8:06 AM, Ben Webb ben@salilab.org wrote:

> On 10/5/12 12:24 AM, Benjamin SCHWARZ wrote: >> I remember the good old times, when I could see the svn revision number for free. >> Is it hidden somewhere else nowadays ? > > The SVN revision number didn't really tell you anything useful, since it doesn't reflect any changes you've made to your checkout. Well, it did (since it would have an M appended if you had changed anything, which was pretty nice).

> If you want to keep track of your own checkouts, just put some suitable string in the VERSION file before you compile.

We dropped displaying the SVN revision because - there was a bug with it that needed to be fixed - it wasn't going to be useful once we shifted to git (planned to occur in the not to distant future) - the first operation after seeing the svn version number was always to look up what date that corresponded to.

As a result, we had shifted to displaying the date that the copy was checked out (by storing the current date in the repository). For some reason that isn't working right now.

So as a question for people, what info would you find useful to show? - checkout date - nearest nightly test version - presence or absence of changes - git/svn version

Thanks.

On 10/5/12 8:36 AM, Daniel Russel wrote: > On Oct 5, 2012, at 8:06 AM, Ben Webb ben@salilab.org wrote: >> The SVN revision number didn't really tell you anything useful, >> since it doesn't reflect any changes you've made to your checkout. > Well, it did (since it would have an M appended if you had changed > anything, which was pretty nice).

Perhaps I should have been more clear: it doesn't tell you anything about the nature of the change.

> So as a question for people, what info would you find useful to > show? - checkout date - nearest nightly test version - presence or > absence of changes - git/svn version

I doubt there's one answer that everybody would be happy with, which is why I suggested 'write a string you're happy with to VERSION'. It can be as simple as "svnversion > VERSION" if people like the revision number.

IIRC you already set up nightly branches for git, so when we switch to git it would make sense to encourage people to use those, which would also address this issue.

Ben