A few minutes ago, I wrote: > I can verify that #593 is fixed. I wrote too quickly, sorry. #593 is *not* fixed; it behaves exactly as it did before. Personally, this isn't a show-stopper for me for a 2.0.2 release (though it may be for others), as long as it can be addressed within the next few weeks. -- Erik