Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | gh-107811: tarfile: treat overflow in UID/GID as failure to set it (#108369) | Petr Viktorin | 2023-08-23 | 1 | -1/+2 |
| | |||||
* | gh-107396: tarfiles: set self.exception before _init_read_gz() (GH-107485) | balmeida-nokia | 2023-08-21 | 1 | -1/+1 |
| | | | | | | | | | | | In the stack call of: _init_read_gz() ``` _read, tarfile.py:548 read, tarfile.py:526 _init_read_gz, tarfile.py:491 ``` a try;except exists that uses `self.exception`, so it needs to be set before calling _init_read_gz(). | ||||
* | gh-107845: Fix symlink handling for tarfile.data_filter (GH-107846) | Petr Viktorin | 2023-08-21 | 1 | -2/+9 |
| | | | | Co-authored-by: Victor Stinner <vstinner@python.org> Co-authored-by: Lumír 'Frenzy' Balhar <frenzy.madness@gmail.com> | ||||
* | gh-102120: [TarFile] Add an iter function that doesn't cache (GH-102128) | Robert O'Shea | 2023-05-23 | 1 | -6/+11 |
| | |||||
* | gh-102950: Implement PEP 706 – Filter for tarfile.extractall (#102953) | Petr Viktorin | 2023-04-24 | 1 | -41/+320 |
| | |||||
* | gh-74468: [tarfile] Fix incorrect name attribute of ExFileObject (GH-102424) | Oleg Iarygin | 2023-03-27 | 1 | -3/+3 |
| | | | Co-authored-by: Simeon Visser <svisser@users.noreply.github.com> | ||||
* | bpo-45975: Simplify some while-loops with walrus operator (GH-29347) | Nick Drozd | 2022-11-26 | 1 | -9/+3 |
| | |||||
* | gh-91078: Return None from TarFile.next when the tarfile is empty (GH-91850) | Sam Ezeh | 2022-11-26 | 1 | -0/+2 |
| | | | Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com> | ||||
* | gh-99325: Remove unused `NameError` handling (#99326) | Nikita Sobolev | 2022-11-11 | 1 | -7/+3 |
| | |||||
* | bpo-26253: Add compressionlevel to tarfile stream (GH-2962) | Yaron de Leeuw | 2022-06-25 | 1 | -9/+13 |
| | | | | | | `tarfile` already accepts a compressionlevel argument for creating files. This patch adds the same for stream-based tarfile usage. The default is 9, the value that was previously hard-coded. | ||||
* | gh-91387: Strip trailing slash from tarfile longname directories (GH-32423) | Chris Fernald | 2022-06-17 | 1 | -0/+10 |
| | | | Co-authored-by: Brett Cannon <brett@python.org> | ||||
* | bpo-45863: tarfile: don't zero out header fields unnecessarily (GH-29693) | Joshua Root | 2022-02-09 | 1 | -6/+15 |
| | | | | | | | | | | Numeric fields of type float, notably mtime, can't be represented exactly in the ustar header, so the pax header is used. But it is helpful to set them to the nearest int (i.e. second rather than nanosecond precision mtimes) in the ustar header as well, for the benefit of unarchivers that don't understand the pax header. Add test for tarfile.TarInfo.create_pax_header to confirm correct behaviour. | ||||
* | bpo-44289: Keep argument file object's current position in ↵ | Andrzej Mateja | 2022-02-09 | 1 | -0/+2 |
| | | | | tarfile.is_tarfile (GH-26488) | ||||
* | bpo-21987: Fix TarFile.getmember getting a dir with a trailing slash (GH-30283) | andrei kulakov | 2022-01-21 | 1 | -1/+1 |
| | |||||
* | bpo-39039: tarfile raises descriptive exception from zlib.error (GH-27766) | Jack DeVries | 2021-09-29 | 1 | -0/+9 |
| | | | | | | | * during tarfile parsing, a zlib error indicates invalid data * tarfile.open now raises a descriptive exception from the zlib error * this makes it clear to the user that they may be trying to open a corrupted tar file | ||||
* | bpo-8978: improve tarfile.open error message when lzma / bz2 are missing ↵ | Anthony Sottile | 2021-04-27 | 1 | -2/+5 |
| | | | | | (GH-24850) Automerge-Triggered-By: GH:pablogsal | ||||
* | bpo-39717: [tarfile] update nested exception raising (GH-23739) | Ethan Furman | 2020-12-12 | 1 | -32/+33 |
| | | | | - `from None` if the new exception uses, or doesn't need, the previous one - `from e` if the previous exception is still relevant | ||||
* | bpo-12800: tarfile: Restore fix from 011525ee9 (GH-21409) | Julien Palard | 2020-11-25 | 1 | -0/+3 |
| | | | Restore fix from 011525ee92eb1c13ad1a62d28725a840e28f8160. | ||||
* | bpo-39693: mention KeyError in tarfile extractfile documentation (GH-18639) | Andrey Doroschenko | 2020-10-20 | 1 | -3/+4 |
| | | | Co-authored-by: Andrey Darascheka <andrei.daraschenka@leverx.com> | ||||
* | bpo-41316: Make tarfile follow specs for FNAME (GH-21511) | Artem Bulgakov | 2020-09-07 | 1 | -0/+2 |
| | | | | | | | | | | tarfile writes full path to FNAME field of GZIP format instead of just basename if user specified absolute path. Some archive viewers may process file incorrectly. Also it creates security issue because anyone can know structure of directories on system and know username or other personal information. RFC1952 says about FNAME: This is the original name of the file being compressed, with any directory components removed. So tarfile must remove directory names from FNAME and write only basename of file. Automerge-Triggered-By: @jaraco | ||||
* | bpo-39017: Avoid infinite loop in the tarfile module (GH-21454) | Rishi | 2020-07-15 | 1 | -0/+2 |
| | | | | | Avoid infinite loop when reading specially crafted TAR files using the tarfile module (CVE-2019-20907). | ||||
* | bpo-18819: tarfile: only set device fields for device files (GH-18080) | William Chargin | 2020-02-12 | 1 | -2/+10 |
| | | | | | | The GNU docs describe the `devmajor` and `devminor` fields of the tar header struct only in the context of character and block special files, suggesting that in other cases they are not populated. Typical utilities behave accordingly; this patch teaches `tarfile` to do the same. | ||||
* | bpo-39430: Fix race condition in lazy imports in tarfile. (GH-18161) | Serhiy Storchaka | 2020-01-24 | 1 | -10/+8 |
| | | | Use `from ... import ...` to ensure module is fully loaded before accessing its attributes. | ||||
* | bpo-29435: Allow is_tarfile to take a filelike obj (GH-18090) | William Woodruff | 2020-01-23 | 1 | -1/+6 |
| | | | `is_tarfile()` now supports `name` being a file or file-like object. | ||||
* | Add missing docstrings for TarInfo objects (#12555) | Raymond Hettinger | 2019-03-27 | 1 | -7/+46 |
| | |||||
* | bpo-36268: Change default tar format to pax from GNU. (GH-12355) | CAM Gerlach | 2019-03-21 | 1 | -1/+1 |
| | |||||
* | Clean up code which checked presence of os.{stat,lstat,chmod} (#11643) | Anthony Sottile | 2019-02-25 | 1 | -8/+6 |
| | |||||
* | bpo-34043: Optimize tarfile uncompress performance (GH-8089) | INADA Naoki | 2018-07-06 | 1 | -18/+12 |
| | | | | | | | | | | | tarfile._Stream has two buffer for compressed and uncompressed data. Those buffers are not aligned so unnecessary bytes slicing happens for every reading chunks. This commit bypass compressed buffering. In this benchmark [1], user time become 250ms from 300ms. [1]: https://bugs.python.org/msg320763 | ||||
* | bpo-34010: Fix tarfile read performance regression (GH-8020) | hajoscher | 2018-07-04 | 1 | -9/+11 |
| | | | | During buffered read, use a list followed by join instead of extending a bytes object. This is how it was done before but changed in commit b506dc32c1a. | ||||
* | bpo-33842: Remove tarfile.filemode (GH-7661) | INADA Naoki | 2018-06-28 | 1 | -7/+0 |
| | |||||
* | bpo-32713: Fix tarfile.itn for large/negative float values. (GH-5434) | Joffrey F | 2018-02-27 | 1 | -1/+2 |
| | |||||
* | bpo-30693: zip+tarfile: sort directory listing (#2263) | Bernhard M. Wiedemann | 2018-01-31 | 1 | -1/+1 |
| | | | | | | tarfile and zipfile now sort directory listing to generate tar and zip archives in a more reproducible way. See also https://reproducible-builds.org/docs/stable-inputs/ on that topic. | ||||
* | bpo-32297: Few misspellings found in Python source code comments. (#4803) | Mike | 2017-12-14 | 1 | -1/+1 |
| | | | | | | | | * Fix multiple typos in code comments * Add spacing in comments (test_logging.py, test_math.py) * Fix spaces at the beginning of comments in test_logging.py | ||||
* | Remove two legacy constants which hopefully have no consumers (#1087) | Alex Gaynor | 2017-04-12 | 1 | -2/+0 |
| | | | The data contained in them is nonsensical | ||||
* | bpo-29958: Minor improvements to zipfile and tarfile CLI. (#944) | Serhiy Storchaka | 2017-04-07 | 1 | -9/+6 |
| | |||||
* | bpo-29776: Use decorator syntax for properties. (#585) | Serhiy Storchaka | 2017-03-19 | 1 | -6/+10 |
| | |||||
* | Issue #29210: Removed support of deprecated argument "exclude" in | Serhiy Storchaka | 2017-01-13 | 1 | -13/+3 |
| | | | | tarfile.TarFile.add(). | ||||
* | Issue #26937: The chown() method of the tarfile.TarFile class does not fail now | Xavier de Gaye | 2016-12-09 | 1 | -12/+19 |
| | | | | when the grp module cannot be imported, as for example on Android platforms. | ||||
* | Issue #28449: tarfile.open() with mode "r" or "r:" now tries to open a tar | Serhiy Storchaka | 2016-10-30 | 1 | -1/+3 |
|\ | | | | | | | | | file with compression before trying to open it without compression. Otherwise it had 50% chance failed with ignore_zeros=True. | ||||
| * | Issue #28449: tarfile.open() with mode "r" or "r:" now tries to open a tar | Serhiy Storchaka | 2016-10-30 | 1 | -1/+3 |
| | | | | | | | | | | file with compression before trying to open it without compression. Otherwise it had 50% chance failed with ignore_zeros=True. | ||||
* | | Issue #27199: TarFile expose copyfileobj bufsize to improve throughput | Łukasz Langa | 2016-09-10 | 1 | -15/+18 |
| | | | | | | | | Patch by Jason Fried. | ||||
* | | Issue #27355: Removed support for Windows CE. It was never finished, | Larry Hastings | 2016-09-05 | 1 | -1/+1 |
| | | | | | | | | and Windows CE is no longer a relevant platform for Python. | ||||
* | | Merge 3.5, issue #27194 | Łukasz Langa | 2016-06-11 | 1 | -2/+2 |
|\ \ | |/ | |||||
| * | Issue #27194: superfluous truncate calls in tarfile.py slow down extraction | Łukasz Langa | 2016-06-11 | 1 | -2/+2 |
| | | | | | | | | Patch by Jason Fried. | ||||
* | | Issue #24838: Merge tarfile fix from 3.5. | Lars Gustäbel | 2016-04-19 | 1 | -14/+15 |
|\ \ | |/ | |||||
| * | Issue #24838: tarfile's ustar and gnu formats now correctly calculate name and | Lars Gustäbel | 2016-04-19 | 1 | -14/+15 |
| | | | | | | | | link field limits for multibyte character encodings like utf-8. | ||||
* | | Issue #26778: Fixed "a/an/and" typos in code comment, documentation and error | Serhiy Storchaka | 2016-04-17 | 1 | -2/+2 |
|\ \ | |/ | | | | | messages. | ||||
| * | Issue #26778: Fixed "a/an/and" typos in code comment and documentation. | Serhiy Storchaka | 2016-04-17 | 1 | -2/+2 |
| | | |||||
* | | Issue #22468: Merge gettarinfo() doc from 3.5 | Martin Panter | 2016-02-19 | 1 | -10/+11 |
|\ \ | |/ | |||||
| * | Issues #22468, #21996, #22208: Clarify gettarinfo() and TarInfo usage | Martin Panter | 2016-02-19 | 1 | -10/+11 |
| | | | | | | | | | | | | | | | | * The Windows-specific binary notice was probably a Python 2 thing * Make it more obvious gettarinfo() is based on stat(), and that non-ordinary files may need special care * The file name must be text; suggest dummy arcname as a workaround * Indicate TarInfo may be used directly, not just via gettarinfo() |