New submission from Elijah Merkin :
time.clock () has very poor time resolution on Linux (tested on Ubuntu 11.04).
The result of call to clock () changes once per several seconds. On the other
side, on Windows it provides very good resolution.
Here is a doctest that fails on Linux
Elijah Merkin added the comment:
Sorry for not explaining properly, I was distracted.
1. The absolute path really exists in the .tar.gz file when I view it in
a hex editor.
2. Windows archive managers I tried see that absolute path.
3. Linux tar utility, however, somehow manages to extract the
Elijah Merkin added the comment:
Tested again under Python 2.6.1 on Windows XP (added Python 2.6 to
versions).
An archive I attached to the issue contains a .py file that reproduces
the bug and an archive created by it.
In my case I just put the .py file to C:\testtarfile\ directory and run
New submission from Elijah Merkin :
Tested on Python 2.5.4.
1. Use tarfile.open("fname", "w|gz") to create an archive.
2. Add a file using TarFile.add(name, arcname=None, recursive=True,
exclude=None) by specifying 2 params: absolute path to a source file as
'name'
