[issue40358] pathlib's relative_to should behave like os.path.relpath

C.A.M. Gerlach added the comment: For the record, requested [on Discourse](https://discuss.python.org/t/how-to-go-on-with-a-tiny-improvement-idea-for-pathlib/12472) as well, with a fairly similar proposal. -- nosy: +CAM-Gerlach ___ Python tracker

[issue5993] python produces zombie in webbrowser.open

C.A.M. Gerlach added the comment: I can verify that this still occurs on Linux under an up to date Python 3.9 env (unknown browser; I can inquire), while on my Windows machine running an essentially identical Python 3.9 env, I don't get the warning. The practical problem arises when w

[issue5901] missing meta-info in documentation pdf

Change by C.A.M. Gerlach : -- keywords: +patch nosy: +CAM-Gerlach nosy_count: 5.0 -> 6.0 pull_requests: +30424 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/32386 ___ Python tracker <https://bugs.p

[issue36490] Modernize function signature in Archiving section of shutil doc

C.A.M. Gerlach added the comment: Sorry for the lack of response on this one; it just slipped off my radar. It seems quite clear that my understanding was incomplete as to why the signatures were expressed this way. As such, I presume this can just be closed as NOTABUG? I'll close in a

[issue32592] Drop support of Windows Vista and 7 in Python 3.9

C.A.M. Gerlach added the comment: Sorry I never got around to this, I was planning on it and then life and COVID intervened. I can give it another look now to get it in before the 3.10 feature freeze (since I at least documented in detail what each change should be, so it should be

[issue32592] Drop support of Windows Vista and Windows 7

C.A.M. Gerlach added the comment: In my limited understanding, all PR #15951 does is set a compiler macro to allow use of Win API calls present on >=Win8 instead of >=Win7. If Win8-only calls are not used, then presumably it should still build and run on Windows 7, presumably with th

[issue36490] Modernize function signature in Archiving section of shutil doc

C.A.M. Gerlach added the comment: Closing on grounds of apparently not really being an issue as opposed to a misunderstanding on my part, as mentioned above. -- resolution: -> not a bug stage: needs patch -> resolved status: open -&g

[issue32592] Drop support of Windows Vista and 7 in Python 3.9

C.A.M. Gerlach added the comment: I'd be happy to submit a PR to resolve all the issues that I note here. Just say the word and I'll go right ahead. I presume the Windows installer code [0a] should be updated to refuse to install on Windows <8 and given an informative wa

[issue32592] Drop support of Windows Vista and 7 in Python 3.9

C.A.M. Gerlach added the comment: Here's a further conservative list of low-hanging https://github.com/python/cpython/blob/master/Lib/ntpath.py#L675 * multiprocesing/connection.py | >=Win 8 | Branch can be inlined and outdated comments removed: https://github.com/python/cpython/blo

[issue32592] Drop support of Windows Vista and 7 in Python 3.9

C.A.M. Gerlach added the comment: What Eryk said wrt Windows 8 seems sound, looking at some additional data. Per Statcounter [0], Windows 8 market share has dropped to 1.32% from 2.20% of all Windows users over the past 12 months, or 1.75% -> 1.01% of all desktop users. Extrapolatin

[issue32592] Drop support of Windows Vista and 7 in Python 3.9

C.A.M. Gerlach added the comment: Hey, any update on this? As I mentioned, I'm willing to implement everything I mention here in one or more PRs, but I wanted to wait for a go-ahead in case some of the changes were not desired. Let me know and I'll go ahe

[issue32592] Drop support of Windows Vista and 7 in Python 3.9

C.A.M. Gerlach added the comment: Thanks, will do as requested. I was planning on knocking it out yesterday, but some unexpected things came up so I might have to push it all the way to next weekend, but I'll get it done. -- ___ Python tr

[issue29982] tempfile.TemporaryDirectory fails to delete itself

C.A.M. Gerlach added the comment: In addition to transient failures, this can also occur when, for example, files opened in the temporary directory (perhaps by library or application code not under direct control of the caller) haven't been properly cleaned up and their file handles

[issue25024] Allow passing "delete=False" to TemporaryDirectory

C.A.M. Gerlach added the comment: To note, the proposal on [BPO-29982](https://bugs.python.org/issue29982) should hopefully address one of the two use-cases described by Anthony Sotittle, `ignore_errors=True`, in a cleaner fashion that takes advantage of the existing higher-level

[issue29982] tempfile.TemporaryDirectory fails to delete itself

Change by C.A.M. Gerlach : -- keywords: +patch pull_requests: +23560 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24793 ___ Python tracker <https://bugs.python.org/issu

[issue25024] Allow passing "delete=False" to TemporaryDirectory

Change by C.A.M. Gerlach : -- pull_requests: +23561 pull_request: https://github.com/python/cpython/pull/24793 ___ Python tracker <https://bugs.python.org/issue25

[issue29982] tempfile.TemporaryDirectory fails to delete itself

C.A.M. Gerlach added the comment: Thanks! Submitted as PR #24793 https://github.com/python/cpython/pull/24793 -- ___ Python tracker <https://bugs.python.org/issue29

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

New submission from C.A.M. Gerlach : I propose changing tarfile.DEFAULT_FORMAT to be tarfile.PAX_FORMAT , rather than the legacy tarfile.GNU_FORMAT for Python 3.8. This would offer several benefits: • Removes limitations of the old GNU tar format, including in max UID/GID values and bits in

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

C.A.M. Gerlach added the comment: In general, since pax is a backwards-compatible superset of the standard, portable ustar unlike the vendor-specific GNU format that even GNU tar itself no longer recommends in favor of switching to pax by default, it is to my understanding essentially

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

C.A.M. Gerlach added the comment: Sure, in work now. Its my first contribution to CPython, so bear with me. I presume this is too trivial to go in the What's New in Python article, but does merit a NEWS entry so users are aware of the change? Aside from changing [this line](

[issue30661] Support tarfile.PAX_FORMAT in shutil.make_archive

Change by C.A.M. Gerlach : -- keywords: +patch pull_requests: +12321 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

Change by C.A.M. Gerlach : -- keywords: +patch pull_requests: +12320 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36268> ___ ___ Py

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

C.A.M. Gerlach added the comment: PR is up with CI checks green as [GH-12355](https://github.com/python/cpython/pull/12355). I also had to fix one test which implicitly assumed that DEFAULT_FORMAT == GNU_FORMAT. -- ___ Python tracker <ht

[issue30661] Support tarfile.PAX_FORMAT in shutil.make_archive

C.A.M. Gerlach added the comment: FYI, [GH-12355](https://github.com/python/cpython/pull/12355) will implement pax as default, as discussed in [bpo-36268](https://bugs.python.org/issue36268), which should be equivalent to option 1 here, thus also resolving this issue. Could you confirm that

[issue30661] Support tarfile.PAX_FORMAT in shutil.make_archive

Change by C.A.M. Gerlach : -- versions: +Python 3.8 -Python 3.7 ___ Python tracker <https://bugs.python.org/issue30661> ___ ___ Python-bugs-list mailin

[issue36307] Upgrade Travis CI config to Xenial from near-EoL Trusty and remove obsolete sudo: false key

New submission from C.A.M. Gerlach : Not sure how to categorize this one, or if this should even be a bpo. Currently, the .travis.yml config file still has a sudo: false key, which previously triggered the Container-based environment on Travis. However, that was removed in December 2018, and

[issue36307] Upgrade Travis CI config to Xenial from near-EoL Trusty and remove obsolete sudo: false key

Change by C.A.M. Gerlach : -- keywords: +patch pull_requests: +12323 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36307> ___ ___ Py

[issue36307] Upgrade Travis CI config to Xenial from near-EoL Trusty and remove obsolete sudo: false key

C.A.M. Gerlach added the comment: Sure, thing, sorry—I realized I should have added one but apparently couldn't edit my post to include it. [Here's](https://docs.travis-ci.com/user/reference/overview/#deprecated-virtualization-environments) a description of the removal of the obs

[issue36307] Upgrade Travis CI config to Xenial from near-EoL Trusty and remove obsolete sudo: false key

C.A.M. Gerlach added the comment: Yes, absolutely. While were at it, should we also bump the OpenSSL version up to the latest 1.1.1b, which is the current LTS branch (with 1.0.2 EoL in Dec. 2019 and 1.1.0 EoL in a few months, in September)? -- components: +Build

[issue36307] Upgrade Travis CI config to Xenial from near-EoL Trusty and remove obsolete sudo: false key

C.A.M. Gerlach added the comment: Ah yes, I actually saw that before opening this issue; not sure why I completely forgot about it. Sorry about that and thanks for the reminder. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

C.A.M. Gerlach added the comment: Also, one additional minor note (since I apparently can't edit comments here). Windows 10 (since the April 2018 update a year ago) now includes libarchive-based bsdtar built-in by default and accessible from the standard command prompt, which as ment

[issue30661] Support tarfile.PAX_FORMAT in shutil.make_archive

Change by C.A.M. Gerlach : -- pull_requests: +12566 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issue30661> ___ ___ Python-

[issue36268] Change default tar format to modern POSIX 2001 (pax) for better portability/interop, support and standards conformance

Change by C.A.M. Gerlach : -- pull_requests: +12567 ___ Python tracker <https://bugs.python.org/issue36268> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue30661] Support tarfile.PAX_FORMAT in shutil.make_archive

C.A.M. Gerlach added the comment: I opened a PR to implement both those changes, and also added some minor related clarifications and fixes to the format section of the tarfile docs. > how tarfile.Tarfile behaves if you tell it to open a PAX_FORMAT archive using > GNU_FORMAT or vice

[issue36490] Modernize function signature format in Archiving section of shutil doc

New submission from C.A.M. Gerlach : In the process of updating the documentation for another issue, I noticed that unlike the rest of the shutil doc (and the Python docs in general, not to mention those of virtually every Python package), all the functions in the [Archiving operations

[issue30661] Support tarfile.PAX_FORMAT in shutil.make_archive

C.A.M. Gerlach added the comment: Thanks for the confirmation! -- ___ Python tracker <https://bugs.python.org/issue30661> ___ ___ Python-bugs-list mailin