Title: ignores custom bufsize value when creating a new archive
Type: Stage:
Components: Library (Lib) Versions: Python 3.7, Python 3.6, Python 2.7
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: cstratak, lars.gustaebel, nitishch
Priority: normal Keywords:

Created on 2017-10-12 14:17 by cstratak, last changed 2017-10-16 07:50 by nitishch.

File name Uploaded Description Edit cstratak, 2017-10-12 14:17
Messages (3)
msg304241 - (view) Author: Charalampos Stratakis (cstratak) * Date: 2017-10-12 14:17
Trying to create an archive with the tarfile module, by specifying a different blocking factor, doesn't seem to work as only the default value is being used. The issue is reproducible on all the active python branches.

Attaching a script to reproduce it.

Original bug report:
msg304457 - (view) Author: Nitish (nitishch) * Date: 2017-10-16 07:49
Seems like bufsize is used only in streaming modes. Even in the documentation bufsize is described only in the context of streaming modes. 

Even TarFile constructor doesn't take bufsize as an argument. Why is it so?
msg304458 - (view) Author: Nitish (nitishch) * Date: 2017-10-16 07:50
Sorry. My bad. There *is* an argument 'copybufsize' in TarFile.
Date User Action Args
2017-10-16 07:50:32nitishchsetmessages: + msg304458
2017-10-16 07:49:20nitishchsetmessages: + msg304457
2017-10-16 07:29:33nitishchsetnosy: + nitishch
2017-10-12 14:17:19cstratakcreate