Created on 2011-03-09 05:00 by strombrg, last changed 2011-06-01 15:04 by strombrg. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| tar-test | strombrg, 2011-03-09 05:00 | |||
| Messages (4) | |||
|---|---|---|---|
| msg130422 - (view) | Author: Dan Stromberg (strombrg) | Date: 2011-03-09 05:00 | |
The attached file demonstrates the problem in 2.5, 2.5, 2.7, 3.0, 3.1 and 3.2. In short, I believe when you're creating a new tar archive (say, to a pipe), there should be no need for a file_.tell() (which blows up when it's a pipe). I have a workaround, as demonstrated in the file, but probably others shouldn't have to work around this also in the future. Suggested fix: Only do the tell when you're appending or performing other operations that require subsequent seek's. |
|||
| msg130437 - (view) | Author: Lars Gustäbel (lars.gustaebel) *  |
Date: 2011-03-09 09:48 | |
If I understand correctly, the solution to your problem would be to use the stream mode "w|" instead of "w". Could you please try that? |
|||
| msg137421 - (view) | Author: Terry J. Reedy (terry.reedy) * |
Date: 2011-06-01 06:27 | |
2.5 is closed; 2.6 security fix only, 3.1 soon will be |
|||
| msg137434 - (view) | Author: Dan Stromberg (strombrg) | Date: 2011-06-01 15:04 | |
Yes, I just needed to use 'w|' instead of 'w'. Thanks! |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-06-01 15:04:18 | strombrg | set | status: open -> closed resolution: works for me messages: + msg137434 |
| 2011-06-01 06:27:17 | terry.reedy | set | nosy:
+ terry.reedy messages: + msg137421 versions: - Python 2.6, Python 2.5, Python 3.1 |
| 2011-03-09 09:48:20 | lars.gustaebel | set | assignee: lars.gustaebel messages: + msg130437 |
| 2011-03-09 07:40:21 | ned.deily | set | nosy:
+ lars.gustaebel |
| 2011-03-09 05:00:11 | strombrg | create | |