On Fri, Jul 2, 2010 at 4:45 AM, Stefan Sperling <s...@elego.de> wrote: > On Fri, Jul 02, 2010 at 11:42:58AM +0100, Julian Foad wrote: >> Any objection to this step? The only down side I can think of is the >> slight inconvenience for us developers of having to quote the path on >> the command line when debugging the tests, and that's not something that >> should put us off. > > -1 > > I tend to find spaces in filenames I work with on the command line quite > annoying. So I'd prefer explicit unit tests which check for whitespace > within local paths and within URLs, much like what you listed below.
+1. For example, seeing the mu character in all of our tests would drive me bonkers. I don't see a reason why we can't have some explicit tests which focus on ensuring the crazy paths are handled correctly, but all of them? Ugh. -- justin
