[issue14156] argparse.FileType for '-' doesn't work for a mode of 'rb'
William Woodruff added the comment: Nosying myself; this affects 3.9 and 3.10 as well. -- nosy: +yossarian versions: +Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue14156> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38794] Setup: support linking openssl statically
William Woodruff added the comment: Not to butt in too much, but I have a related use case that would benefit from being able to statically link to OpenSSL: I have an environment in which dynamic modules are acceptable, but where the entire Python install benefits from being relocatable and used on different hosts with the same *basic* state (same glibc, etc). OpenSSL isn't one of those pieces of basic state (for bad reasons, but ones that I can't control), so having a Python distribution that links it statically would save me some amount of complexity. I realize this introduces a significant support burden, and that dealing with myraid OpenSSL configurations is already a pain. So I'm content to shoulder this as my own local build patch -- I'm only following up to note another use case that might benefit from a full-fledged `configure` option, should this ever get re-visited. -- nosy: +yossarian ___ Python tracker <https://bugs.python.org/issue38794> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38794] Setup: support linking openssl statically
William Woodruff added the comment: Cheers! No promises about not using the hack, but I *will* promise not to complain if it doesn't work for me :-) -- ___ Python tracker <https://bugs.python.org/issue38794> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38794] Setup: support linking openssl statically
William Woodruff added the comment: I don't think this is a productive or polite response. If you read the issue linked, you'll note that the other flag added (--with-openssl-rpath) is in furtherance of any *already* supported linking scenario (dynamic, with a non-system-default OpenSSL). The proposed change here is for an *new* linking scenario, i.e. statically linking OpenSSL. I don't blame the maintainers for not wanting to add another build configuration to their plate, especially for something like OpenSSL. It's up to us as end users to make those accommodations on our own, knowing that what we're doing isn't tested or directly supported. The resolution above is, in my book, the ideal one. Best, William On Sat, Apr 03, 2021 at 04:45:34PM +, Lukas Vacek wrote: > > Lukas Vacek added the comment: > > For the record, this would have been solved more than a year ago already. > > When this change was proposed more than a year ago it was rejected with > "There is no need to add more configure flags to build Python with a custom > OpenSSL installation. " yet now it's ok to add a new option > --with-openssl-rpath https://bugs.python.org/issue43466 ? > > And the first comment there, from python core dev nonetheless, is suggesting > static linking as well. Emm... this would have been solved year and half ago. > I would be happy to completely drop my proposed (and approved on gihub) > changes and implement it in a different way. > > The maintainer's attitude as demonstrated here can be really harmful in > open-source projects (many of us still remember eglibc fork back in the day) > but fortunately this is the first time I noticed such attitude among python > developers. > > Importantly the issue is resolved now (did it take a request from IBM's > customer to get this implemented ;-) ?) and hopefully a lesson learnt and > Christian will be more welcoming and less judgemental of outsiders' > contributions. > > -- > > ___ > Python tracker > <https://bugs.python.org/issue38794> > ___ -- ___ Python tracker <https://bugs.python.org/issue38794> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15795] Zipfile.extractall does not preserve file permissions
Change by William Woodruff : -- nosy: +yossarian ___ Python tracker <https://bugs.python.org/issue15795> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29435] Allow to pass fileobj to is_tarfile
William Woodruff added the comment: I'll take a stab at this. It looks like `Tarfile.open` takes an optional keyword that should make this straightforward. -- nosy: +yossarian ___ Python tracker <https://bugs.python.org/issue29435> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29435] Allow to pass fileobj to is_tarfile
Change by William Woodruff : -- keywords: +patch pull_requests: +17482 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18090 ___ Python tracker <https://bugs.python.org/issue29435> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29435] Allow to pass fileobj to is_tarfile
William Woodruff added the comment: Thanks to you to! -- ___ Python tracker <https://bugs.python.org/issue29435> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com