My apologies -- that was an oversight on my part.  Now that I look at the issue again, it's plain that it most likely won't be an issue.  Problems only arise when you allow '#' to occur before '?' and then treat portion of the url between the '#' and '?' as a fragment. In this scenario, when the url is rejoined, the order of the fragment and query is switched by urlunsplit().  

However, since the portion of the url with a hashtag would be treated as a the netloc, this isn't any cause for concern. We only need to ensure that the order of the components is maintained.

Thanks for the heads up, Dmi.