➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2003-12-10 02:22 by aggression, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| tarfile-test.tar.gz | aggression, 2003-12-10 02:22 | Tarfile Test | ||
| Messages (4) | |||
|---|---|---|---|
| msg19351 - (view) | Author: Ricardo Martins (aggression) | Date: 2003-12-10 02:22 | |
The attachment has a tar.gz file which contains a file and an hard-link to that file. The Python script unpacks the tar file to 3 locations: the current directory, the current directory specified by absolute path and /tmp). In the machines I've tested it, when unpacking to /tmp (or any other directory that does not belongs to the same branch as the current) the hard-link is not created. Am I missing something ? I have tested it with the tarfile module that ships with Python 2.3.2, and with the CVS tarfile module, the behavior is the same. Regards Ricardo Martins |
|||
| msg19352 - (view) | Author: Lars Gustäbel (lars.gustaebel) *  |
Date: 2004-03-15 20:54 | |
Logged In: YES user_id=642936 I submitted a patch (#916874) that fixes this. |
|||
| msg19353 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2004-07-20 22:10 | |
Logged In: YES user_id=33168 Checked in as: * Lib/tarfile.py; 1.13 * Lib/test/test_tarfile.py; 1.13 * Misc/NEWS; 1.1048 Perhaps this should be backported to 2.3? |
|||
| msg19354 - (view) | Author: Lars Gustäbel (lars.gustaebel) * |
Date: 2004-07-21 07:15 | |
Logged In: YES user_id=642936 Yes, it should be backported. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:01 | admin | set | github: 39687 |
| 2003-12-10 02:22:46 | aggression | create | |