On windows, glob.glob gives different results if you use a wildcard or not and if you use unix-style paths.

exemple : 
import glob
print glob.glob("c:/tmp/3691674.jpg")
print glob.glob("c:/tmp/3691674.jpg*")
print glob.glob("c:/res.txt")
print glob.glob("c:/res.txt*")

gives :
['c:/tmp/3691674.jpg']
['c:/tmp\\3691674.jpg']
['c:/res.txt']
['c:/res.txt']


the two first calls give the same result but one with a platform specific separator, and not the other.
One can think that if there is no wildcard, this is normal behavior to return the path given to glob.glob but then I have the second inconsitency : in that case the last result should be c:\\res.txt.

Hardly a show stopper. It's actually a problem(?) with ntpath.py.  It could be patched but is it worth it, as this would be yet more work for you guys doing the build/release process?  I'd close this on the grounds that it's not worth the effort.

As no response to msg108627 I'll close this unless there are any objections.

Some bugs take a long time to get fixed. I agree that three years is not a good score, but this really needs a test in order to get closed or fixed, so I’m reopening. Maybe the OP or you could add a test? :)

Here is a test + patch, to preserve the separator. Of course this changes the current behaviour, like:
>>> glob.glob('/tmp/////foo*')
['/tmp/////foo1', '/tmp/////foo2']