=== BasicPRO is now known as BasicOSX === RenatoSilva is now known as a === a is now known as RenatoSilva [17:36] hm, looking at this osutils path manip stuff makes me want to resurrect the old Just van Rossum plan for Path objects. [17:37] if we have to make everyone use the osutils versions already we could at least provide an api that doesn't suck quite so much. [22:30] hi all === Meths_ is now known as Meths === Daviey_ is now known as Daviey [22:44] hi poolie [22:49] is it relatively easy to get the modification time of files that have changed (i.e. would appear in bzr st output) through bzrlib or should I just parse the output of bzr st? [22:53] elmo: getting the mtime from a path is pretty easy [22:53] i think getting the list of files that would appear in st might be a little annoying [22:55] elmo: the_tree.get_file_mtime(file_id) [22:56] hi peitschie, elmo, spiv, mwhudson === poolie changed the topic of #bzr to: Bazaar version control | try https://answers.launchpad.net/bzr for more help | http://irclogs.ubuntu.com/ | Patch pilot: poolie | 2.3b4 is officially out ! (rm vila) [23:47] poolie: if you can get the code out of the error class without regression performance then that would be nice [23:47] i'd much rather regress the feature than the performance [23:47] after all this isn't even something someone specifically asked for [23:47] That's true. [23:48] it was kind of inferred from "they wouldn't have got confused if ..." [23:49] I think maybe it's occasionally come up in user support on IRC too, but only very occasionally. [23:49] oh, seeing that reminded me of the url escaping thing too [23:51] I'm personally pretty relaxed about it now that the open_repository call is confined to str(e). So constructing and repr()ing the exception is simple and safe, and it's only when generating text for display to a user we do the extra work (although I can see an argument for making that be something other than str(e) to be more careful). [23:51] But if you'd rather remove this marginal feature, that's fine with me too. [23:53] i guess it's dropped down my priority list too now [23:53] i would really rather not see code like that come in in future though [23:53] i think exceptions really should be value objects, or very close to it [23:53] (i realize it's a tradeoff) [23:55] Perhaps if we had other exceptions that wanted to provide that sort of hint when displayed to a user we'd find a better a home for the hint-generation/error-formatting.