Author apolkosnik
Recipients Jim.Jewett, NewerCookie, amaury.forgeotdarc, apolkosnik, berker.peksag, chuck, ethan.furman, francismb, georg.brandl, gregory.p.smith, ncoghlan, ronaldoussoren, serhiy.storchaka, terry.reedy
Date 2014-05-02.05:14:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

The problems documented here are related to two cases (both apparently arriving from world of windows): 
1. two relative paths with inverted slash in one of them (test\test2.txt vs test/test2.txt)
2. relative path vs absolute path (windows\temp\test.txt vs c:\windows\temp\test.txt)

The extraction part seems to be doing a good job at writing the files into sane locations.

IMHO, there's no point in trying to replace slashes or otherwise "normalize", as this would fix the cases where the presence of an inverted slashes should be noted in debug output. 
By the same token stripping the drive letter from the absolute path part would just deprive  us from noticing such intricacies in these special zip files.
Date User Action Args
2014-05-02 05:14:04apolkosniksetrecipients: + apolkosnik, georg.brandl, terry.reedy, gregory.p.smith, ronaldoussoren, amaury.forgeotdarc, ncoghlan, NewerCookie, chuck, ethan.furman, francismb, berker.peksag, Jim.Jewett, serhiy.storchaka
2014-05-02 05:14:04apolkosniksetmessageid: <>
2014-05-02 05:14:04apolkosniklinkissue6839 messages
2014-05-02 05:14:03apolkosnikcreate