gh-130819: Update tarfile.py#_create_gnu_long_header to align with GNU Tar#130820
gh-130819: Update tarfile.py#_create_gnu_long_header to align with GNU Tar#130820gdh1995 wants to merge 1 commit into
tarfile.py#_create_gnu_long_header to align with GNU Tar#130820Conversation
|
All commit authors signed the Contributor License Agreement. |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
ce2e670 to
24b90cf
Compare
24b90cf to
283b34e
Compare
There was a problem hiding this comment.
Can you motivate the choice for this? namely is there a real benefit between having an explicit user+mode rather than letting the "defaults"? And more importantly, can you cite the relevant manpage / specs where we can find this?
Note: whether this is accpeted or not, this should be treated as a feature request and not a bug IMO. As such, a What's New entry will need to be created, unless the motivation behind this change is not sufficient (in which case we would close the issue as "not planned")
| info["mode"] = 0o100644 | ||
| info["uname"] = "root" | ||
| info["gname"] = "root" |
There was a problem hiding this comment.
Where in the specs are these decided?
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
Oh btw, please reply on the issue instead of the PR (I'll repost my comment above) |
80b8591 to
5282dd6
Compare
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @picnixz: please review the changes made to this pull request. |
| _unames = {} # Cached mappings of uid=0 -> uname | ||
| _gnames = {} # Cached mappings of gid=0 -> gname |
There was a problem hiding this comment.
I prefer that we keep per-instance caches instead of per-class caches, even for 0.
There was a problem hiding this comment.
Hello, sorry but there seems no available TarFile object for _create_gnu_long_header to cache the querying result:
- a
TarFileinstance does have cache members ofself._unames: Dict[uid, uname] - however, across the calling stack of
TarInfo.tobuf() -> TarInfo.create_gnu_header() -> TarInfo._create_gnu_long_header(), there's noTarFileargument.
If we add a TarFile into TarInfo.tobuf(...), then this PR may break existing subclasses of TarInfo. Is it indeed necessary?
There was a problem hiding this comment.
Um, to make this cache safe for the free-threading version of CPython, I've replaced the _unames = {} with _name_uid0 = None (and _gnames = {} with _name_gid0 = None).
Do you developers have any suggestions?
There was a problem hiding this comment.
@picnixz Any idea about where to put the cache object?
47861a1 to
ca20885
Compare
ca20885 to
02bbde5
Compare
|
I have made the requested changes; please review again. |
|
Thanks for making the requested changes! @picnixz: please review the changes made to this pull request. |
| (Contributed by Xuehai Pan in :gh:`131799`.) | ||
|
|
||
|
|
||
| tarfile |
There was a problem hiding this comment.
This will need to be moved in whatsnew/3.15.rst now
| _name_uid0 = None # Cached uname of uid=0 | ||
| _name_gid0 = None # Cached gname of gid=0 |
There was a problem hiding this comment.
What I meant before is: why using a class variable? the issue is that once we deduce uid=0, we're stuck with it for the entire Python process.
EDIT: I didn't see you comment, my bad. Then we need to think of another solution because storing them in TarFile feels wrong. What we can do is to add a private attribute in TarInfo and populate it from TarFile. When writing, if the attribute is not set, we populate it eagerly (and thus subclasses of TarInfo will be slower but they won't be broken). Or instead, we can even just dump them with the legacy way (namely without aligning with GNU Tar). Only default TarFile and TarInfo objects will be having this new feature.
More generally, we should be able to set cached contextual information on TarInfo objects coming from a TarFile.
|
This PR is stale because it has been open for 30 days with no activity. |
3 participants
The latest
tarfilemay still generate a file slightly different with the one made by GNU Tar, whenever a path name is longer than 100 bytes. So this PR tries to avoid the difference.More details are in #130819 .