> Would you mind changing it to
> os.environ.get('GTIMELOG_HOME') or '~/.gtimelog'
> ? I think setting $GTIMELOG_HOME to an empty value should be equivalent to not setting it at all, instead of using the current
> working directory.
Good idea, done.
> I'm going to grant you write access to gtimelog trunk, so you can push this yourself -- assuming I figure out how to do that in
> Launchpad. I did it once for zodbbrowser, I should be able to figure the confusing UI again...
Done, and thanks! This branch pushed to trunk in r155.
What do you think about doing a release soon? I'd like to get updated versions into Debian and Ubuntu eventually. Both are in feature freeze, but I'd be happy to update the packaging and throw it into a PPA. Either mine or ~gtimelog-dev if we create one. If you give me upload rights to the cheeseshop project, I'm happy to take care of it all.
> Would you mind changing it to get('GTIMELOG_ HOME') or '~/.gtimelog'
> os.environ.
> ? I think setting $GTIMELOG_HOME to an empty value should be equivalent to not setting it at all, instead of using the current
> working directory.
Good idea, done.
> I'm going to grant you write access to gtimelog trunk, so you can push this yourself -- assuming I figure out how to do that in
> Launchpad. I did it once for zodbbrowser, I should be able to figure the confusing UI again...
Done, and thanks! This branch pushed to trunk in r155.
What do you think about doing a release soon? I'd like to get updated versions into Debian and Ubuntu eventually. Both are in feature freeze, but I'd be happy to update the packaging and throw it into a PPA. Either mine or ~gtimelog-dev if we create one. If you give me upload rights to the cheeseshop project, I'm happy to take care of it all.