Odd... doing what action in tortoise causes this? On which version of mercurial? I couldn't replicate it on 1.4 or 1.5, in repos with or without bookmarks. In mercurial 1.4, None is the value that bookmarks.py itself uses to initialize _bookmarks, so that should work fine. On 1.5, it shouldn't be setting _bookmarks to None, but deleting the attribute from the instance instead. If it's happening with 1.5, perhaps it's not detecting this correctly?
- Paul On Wed, Dec 23, 2009 at 11:37 AM, Steve Borho <st...@borho.org> wrote: > On Tue, Dec 22, 2009 at 8:31 PM, Paul Molodowitch > <pa...@luma-pictures.com> wrote: > > mercurial 1.4 needs to use bookmarks.parse/bookmarks.current, as > > repo._bookmarks/repo._bookmarkcurrent won't yield correct > > results after a refresh; whereas 1.5 needs to use > > repo._bookmarks/repo._bookmarkcurrent, as bookmarks.parse/ > > bookmarks.current no longer exist > > > > updated hglib.get_repo_bookmarks to handle this, and added > > hglib.get_repo_bookmarkcurrent > > > > also updated hglib.invalidaterepo to accomodate changes > > This change causes tracebacks in repositories without bookmarks. It's > setting the _bookmarks property to None, and then bookmarks.py tries > to do: if key in None > > -- > Steve Borho >
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
