[issue36982] Add support for extended color functions in ncurses 6.1
Ned Deily added the comment: > We really need to get this merged since, without it, Python builds fail with > the newer versions of ncurses now in most distributions. That is a bit of an overstatment on my part. What is true is that test_curses fails on 3.9 and 3.8 when run with ncurses 6.1+. It is also true that the relevant parts of test_curses are often skipped in CI and buildbot runs as described in Issue12669 so a test failure is often not seen. > Łukasz can provide direction about whether and when it should be backported > to 3.9 and/or 3.8. We discussed this and decided that a backport to 3.8 was out-of-scope but a backport in time for 3.9.0 might be OK. Alas, I had forgotten that other changes have gone into master for 3.10 prior to this merge which complicates a backport to 3.9, enough that we shouldn't be trying to throw this in just prior to 3.9.0rc1. Thanks everyone for the work on this! -- resolution: -> fixed stage: commit review -> resolved status: open -> closed versions: -Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue36982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41129] setup.py test for macOS SDK files may incorrectly classify files in other file systems
Ned Deily added the comment: > Why is this share mounted under /System/Volumes/Data and not under /Volumes? See man 5 synthetic_conf for more details. -- ___ Python tracker <https://bugs.python.org/issue41129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41129] setup.py test for macOS SDK files may incorrectly classify files in other file systems
Change by Ned Deily : -- title: Python extension modules fail to build on Mac 10.15.1 (Catalina) -> setup.py test for macOS SDK files may incorrectly classify files in other file systems ___ Python tracker <https://bugs.python.org/issue41129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41129] Python extension modules fail to build on Mac 10.15.1 (Catalina)
Ned Deily added the comment: Thanks for the detailed analysis. That does seem like a reasonable explanation: the code in setup.py was not expecting to find anything other than system files under /System. For Apple to put other fs mount points in the /System hierarchy seems ... odd but there it is. At first glance, rather than singling out /Systems/Volumes/Data, changing the inclusion test from /System to /System/Library is probably sufficient. In the most recent SDKs, there is also /System/iOSSupport which is probably never going to come up in Python build contexts but it does point out that making assumptions here about the SDK contents is fragile. So perhaps an even better solution would be for setup.py to dynamically build a filter based on the contents of the SDK in use, i.e. examine the top level of System and usr in the SDK? As a reminder when implementing: /usr/local is a bit tricky. IIRC, recent versions of the compiler chain include /usr/local/include and /usrlocal/bin in the default search paths only in cases where an SDK was not explicitly named, the idea being that you don't want to include references to /usr/local files if you are building something to distribute to the world but it's fine (and necessary) to include /usr/local if you are just building something to run locally on the build system. I believe /Library works the same way. The tool chains from older version of Xcode and/or CLTs may work differently. So any changes we make here should try to do the right thing on the build tools for all supported versions of macOS. -- components: +macOS nosy: +ronaldoussoren resolution: works for me -> stage: -> needs patch ___ Python tracker <https://bugs.python.org/issue41129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41335] free(): invalid pointer in list_ass_item() in Python 3.7.3
Change by Ned Deily : -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41335> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41460] Translation Error in in Functional Programming HOWTO page
Change by Ned Deily : -- assignee: -> docs@python components: +Documentation nosy: +cocoatomo, docs@python, mdk ___ Python tracker <https://bugs.python.org/issue41460> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36982] Add support for extended color functions in ncurses 6.1
Ned Deily added the comment: New changeset da4e09fff6b483fe858997da5599c25397107ca1 by Hans Petter Jansson in branch 'master': bpo-36982: Add support for extended color functions in ncurses 6.1 (GH-17536) https://github.com/python/cpython/commit/da4e09fff6b483fe858997da5599c25397107ca1 -- ___ Python tracker <https://bugs.python.org/issue36982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26185] zipfile.ZipInfo slots can raise unexpected AttributeError
Ned Deily added the comment: Fixed in 3.9.0 -- nosy: +ned.deily resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 -Python 3.5, Python 3.6 ___ Python tracker <https://bugs.python.org/issue26185> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41451] Cannot subclass typing.Generic with __weakref__ slot in Python 3.6
Ned Deily added the comment: Thank you for the report and for the analysis. As you probably know, Python 3.6 is now in the security phase of its life cycle so generally only fixes for security-related issues are provided at this point. This issue doesn't seem to fall into that category. If you have a workaround for 3.6.x, documenting it is probably the best available option. I'm going to close this as "wont fix". https://www.python.org/downloads/ -- nosy: +ned.deily resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41451> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41447] Resource Tracker in Multiprocessing Shared Memory not working correctly
Change by Ned Deily : -- nosy: +davin, pitrou ___ Python tracker <https://bugs.python.org/issue41447> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37586] macOS: posix_spawn(..., setsid=True)
Ned Deily added the comment: The immediate problem is that the version of Xcode you are using supplies a MacOSX10.15 SDK by default. Since you are running on 10.14, the test passes if you build using a MacOSX10.14 SDK. Either upgrade to 10.15 or grab the 10.14 SDK from a previous version of Xcode or the Command Line Tools (which is all you need to build and test Python) and make that SDK the default. Ronald's patch will eventually fix that but, unless you are building for a newer OS version on an older OS version, it is still safest to use the SDK version that corresponds to the running system. -- ___ Python tracker <https://bugs.python.org/issue37586> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41306] test_tk test_widgets.ScaleTest fails with Tk 8.6.10
Ned Deily added the comment: This issue should be fixed for upcoming releases. Nosying Łukasz for consideration of "release blocker" status. -- nosy: +lukasz.langa priority: normal -> critical ___ Python tracker <https://bugs.python.org/issue41306> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41405] python 3.9.0b5 test
Ned Deily added the comment: As xtreak noted earlier, the test_tk failure is documented in Issue41306. It is a result of changes in Tk 8.6.x itself but the tests need to be fixed to work with older and newer versions of Tk 8.6.x. And the curses issues were originally reported in Issue36630 which has been superseded by Issue36982. If there is further discussion needed on either of these two issues, let's use them, please. -- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> test_tk test_widgets.ScaleTest fails with Tk 8.6.10 ___ Python tracker <https://bugs.python.org/issue41405> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36630] failure of test_colors_funcs in test_curses with ncurses 6.1
Ned Deily added the comment: I believe this is now just a duplicate of Issue36982. If there is anything not already covered there, let's discuss it there. -- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Add support for extended color functions in ncurses 6.1 ___ Python tracker <https://bugs.python.org/issue36630> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36982] Add support for extended color functions in ncurses 6.1
Ned Deily added the comment: PR 17536 was based on the original PR 13534 and has now gone through a couple of rounds of code review. Other than a missing doc change, everything in PR 13534 is covered (and updated) in PR 17536 so I've closed the original PR. Other than adding the doc change and a final core developer review of the last requested changes, this *should* be good to go. We really need to get this merged since, without it, Python builds fail with the newer versions of ncurses now in most distributions. Once it is merged into master for 3.10, Łukasz can provide direction about whether and when it should be backported to 3.9 and/or 3.8. -- nosy: +hpj, lukasz.langa, ned.deily, serhiy.storchaka priority: normal -> critical stage: patch review -> commit review versions: +Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue36982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41413] At prompt for input(), pressing Command q kills IDLE
Ned Deily added the comment: Thanks for the report. Actually this behavior is not specific to running IDLE on macOS, it's also reproducible on Linux and on all current versions of IDLE. -- components: -macOS nosy: -ronaldoussoren versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.7 ___ Python tracker <https://bugs.python.org/issue41413> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38946] IDLE on macOS 10.15 Catalina does not open double-clicked files if app already launched
Ned Deily added the comment: Ramon, I am not sure why you closed this issue. Perhaps it may no longer be a problem for you, but it has not yet been resolved for users of the python.org macOS installers. -- stage: resolved -> status: closed -> open ___ Python tracker <https://bugs.python.org/issue38946> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41358] Unable to uninstall Python launcher using command line
Change by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker <https://bugs.python.org/issue41358> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41363] python 3.8.5 folder not visible in https://www.python.org/ftp/python/ listing
Ned Deily added the comment: Thanks for the report. The python.org website sits behind a content delivery network service and sometimes it takes a little while for pages to be updated in the cache. It should be there now. -- nosy: +ned.deily resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41363> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41349] idle not going full screen when I rotate screen 90° on mac
Change by Ned Deily : -- assignee: -> terry.reedy components: +IDLE nosy: +terry.reedy ___ Python tracker <https://bugs.python.org/issue41349> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40741] Upgrade to SQLite v3.32 in Windows and macOS builds
Ned Deily added the comment: New changeset 7cf1cb36ecafabff363790d245f809d3894fbbaf by Erlend Egeberg Aasland in branch 'master': bpo-40741: Update macOS installer to use SQLite 3.32.3 (GH-20979) https://github.com/python/cpython/commit/7cf1cb36ecafabff363790d245f809d3894fbbaf -- ___ Python tracker <https://bugs.python.org/issue40741> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39073] [security] email module incorrect handling of CR and LF newline characters in Address objects.
Ned Deily added the comment: Merged for release in 3.9.0a6, 3.8.4, 3.7.8, 3.6.11, and 3.5.10. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue39073> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39603] [security] http.client: HTTP Header Injection in the HTTP method
Ned Deily added the comment: Merged for release in 3.9.0b5, 3.8.5, 3.7.9, and 3.6.12. Thanks, everyone! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.10 -Python 2.7 ___ Python tracker <https://bugs.python.org/issue39603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39603] [security] http.client: HTTP Header Injection in the HTTP method
Ned Deily added the comment: New changeset f02de961b9f19a5db0ead56305fe0057a78787ae by Miss Islington (bot) in branch '3.6': bpo-39603: Prevent header injection in http methods (GH-18485) (GH-21539) https://github.com/python/cpython/commit/f02de961b9f19a5db0ead56305fe0057a78787ae -- ___ Python tracker <https://bugs.python.org/issue39603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39603] [security] http.client: HTTP Header Injection in the HTTP method
Ned Deily added the comment: New changeset ca75fec1ed358f7324272608ca952b2d8226d11a by Miss Islington (bot) in branch '3.7': bpo-39603: Prevent header injection in http methods (GH-18485) (GH-21538) https://github.com/python/cpython/commit/ca75fec1ed358f7324272608ca952b2d8226d11a -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue39603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41326] Build failure in blurb-it repo: "Failed building wheel for yarl"
Ned Deily added the comment: blurb-it imports aiohttp which imports yarl. It might be a duplicate of https://github.com/aio-libs/yarl/issues/459 -- nosy: +asvetlov, ned.deily ___ Python tracker <https://bugs.python.org/issue41326> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41304] [CVE-2020-15801] python 38 embed ignore python38._pth file on windows
Ned Deily added the comment: New changeset eb0d255ffe002412bb937e1bde61225e5431da5e by Miss Islington (bot) in branch '3.7': bpo-41304: Update NEWS to include CVE-2020-15801 reference (GH-21521) (GH-21524) https://github.com/python/cpython/commit/eb0d255ffe002412bb937e1bde61225e5431da5e -- ___ Python tracker <https://bugs.python.org/issue41304> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41306] test_tk test_widgets.ScaleTest fails with Tk 8.6.10
Ned Deily added the comment: I can reproduce that test failure with Tk 8.6.10 on macOS, along with a few others. I believe various small things have changed in Tk somewhere between 8.6.8 and 8.6.10 in ways that affect some of the Python Tk gui tests, like test_tk and test_ttk_guionly. Some of our tests are pretty brittle with regard to Tk behavior; they captured how a particular version of Tk worked without necessarily a guarantee on the Tk side that the observed behavior wouldn't change. Someone needs to go through and make the tests work with all recent versions of Tk 8.6.x and someone should also get at least some buildbots running with 8.6.10 and really running the gui tests. -- nosy: +gpolo, serhiy.storchaka stage: -> needs patch title: test_tk failure on Arch Linux -> test_tk test_widgets.ScaleTest fails with Tk 8.6.10 ___ Python tracker <https://bugs.python.org/issue41306> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41306] test_tk failure on Arch Linux
Ned Deily added the comment: What version of Tk is being used? It's in the output from: python3 -m test.pythoninfo or however you invoke python. -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue41306> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41304] python 38 embed ignore python38._pth file on windows
Ned Deily added the comment: New changeset 4bfcffe16e9742c154f54ae96b5b36903500abaa by Steve Dower in branch '3.7': bpo-41304: Ensure python3x._pth is loaded on Windows (GH-21495) (#21499) https://github.com/python/cpython/commit/4bfcffe16e9742c154f54ae96b5b36903500abaa -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue41304> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41291] Race conditions when opening and deleting a file on Mac OS X
Ned Deily added the comment: I was able to easily reproduce it as well. I suppose we all tested on very fast SSD-based APFS file systems. I wonder if the problem might be file system related. I wasn’t able to reproduce it using a HDD-based HFS+ file system but it might just be due to the speed difference. In any case, I agree it’s up to Apple to resolve. Let us know when you hear something back from Apple. -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41291> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41299] Python3 threading.Event().wait time is twice as large as Python27
Ned Deily added the comment: Thanks for the version info. Windows and/or threading experts: any ideas? -- components: +Library (Lib), Windows nosy: +paul.moore, pitrou, steve.dower, tim.golden, zach.ware ___ Python tracker <https://bugs.python.org/issue41299> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41303] perf_counter result does not count system sleep time in Mac OS
Change by Ned Deily : -- nosy: +belopolsky, p-ganssle, vstinner ___ Python tracker <https://bugs.python.org/issue41303> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39017] Infinite loop in the tarfile module
Ned Deily added the comment: Thanks, the PRs for 3.7 and 3.6 are now merged. -- versions: +Python 3.10, Python 3.5, Python 3.6, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue39017> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39017] Infinite loop in the tarfile module
Ned Deily added the comment: New changeset 47a2955589bdb1a114d271496ff803ad73f954b8 by Miss Islington (bot) in branch '3.6': bpo-39017: Avoid infinite loop in the tarfile module (GH-21454) (#21485) https://github.com/python/cpython/commit/47a2955589bdb1a114d271496ff803ad73f954b8 -- ___ Python tracker <https://bugs.python.org/issue39017> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39017] Infinite loop in the tarfile module
Ned Deily added the comment: New changeset 79c6b602efc9a906c8496f3d5f4d54c54b48fa06 by Miss Islington (bot) in branch '3.7': bpo-39017: Avoid infinite loop in the tarfile module (GH-21454) (GH-21484) https://github.com/python/cpython/commit/79c6b602efc9a906c8496f3d5f4d54c54b48fa06 -- ___ Python tracker <https://bugs.python.org/issue39017> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41299] Python3 threading.Event().wait time is twice as large as Python27
Ned Deily added the comment: Please provide the results of running the following with the two pythons you are using: python -m test.pythoninfo For what it's worth, running on macOS 10.15.5, I see a slight difference with more variability in the Python 3 results but nothing as pronounced as what you see. Also the Python 3 results were very similar across recent versions of 3.7.x, 3.8.x, and pre-release 3.9. $ /usr/local/bin/python2.7 ~/test_41299.py | sort 0.017021894455 0.0170249938965 0.017028093338 0.017028093338 0.0170290470123 0.0170290470123 0.0170290470123 0.017036866 0.017030954361 0.0170311927795 [...] 0.0190448760986 0.0190479755402 0.019049882 0.0190510749817 0.0190589427948 0.019061088562 0.0190629959106 0.019079208374 0.0190861225128 0.0190970897675 End reached.0.0158078670502 $ /usr/local/bin/python3.8 ~/test_41299.py | sort 0.009722232818603516 0.017028093338012695 0.017033100128173828 0.017034053802490234 0.017034053802490234 0.017035961151123047 0.017037153244018555 0.017037153244018555 0.01703786849975586 0.017038822174072266 [...] 0.021351099014282227 0.021355152130126953 0.021355152130126953 0.02135610580444336 0.021361112594604492 0.021363258361816406 0.02136397361755371 0.021379947662353516 0.02138543128967285 0.021442890167236328 End reached. -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue41299> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41288] Pickle crashes unpickling invalid NEWOBJ_EX opcode
Change by Ned Deily : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41288> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41288] Pickle crashes unpickling invalid NEWOBJ_EX opcode
Ned Deily added the comment: New changeset 6463cf07fef7a923a743fcaf312150c45fd81b64 by Miss Islington (bot) in branch '3.6': bpo-41288: Fix a crash in unpickling invalid NEWOBJ_EX. (GH-21458) (GH-21462) https://github.com/python/cpython/commit/6463cf07fef7a923a743fcaf312150c45fd81b64 -- ___ Python tracker <https://bugs.python.org/issue41288> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41288] Pickle crashes unpickling invalid NEWOBJ_EX opcode
Ned Deily added the comment: New changeset 620e276a8c1d53332fbf08d369be87f862b6949d by Miss Islington (bot) in branch '3.7': bpo-41288: Fix a crash in unpickling invalid NEWOBJ_EX. (GH-21458) (GH-21461) https://github.com/python/cpython/commit/620e276a8c1d53332fbf08d369be87f862b6949d -- ___ Python tracker <https://bugs.python.org/issue41288> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41288] Pickle crashes unpickling invalid NEWOBJ_EX opcode
Ned Deily added the comment: Sounds like a good idea. -- versions: +Python 3.6, Python 3.7 ___ Python tracker <https://bugs.python.org/issue41288> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41282] Deprecate and remove distutils
Ned Deily added the comment: So what is the plan to continue to support building cpython itself which depends on Distutils? Currently the build bootstraps itself without the aid of an existing Python interpreter instance. There would also be major impacts across the whole cpython development process. For example, there are many open Distutils issues in the bugs.python.org bug tracker. We need a plan on how those are to be handled (and that should take into account the expected transition from b.p.o to GitHub issues). People will continue to submit issues agains Distutils there so triage team members and core developers need to know how to handle such issues. What if an issue applies also or only to a previous release branch (i.e. where Distutils is still in the repo)? What about Distutils documentation in the Python docset? THose are just some off the top of my head. I don't think any of these issues are necessarily blockers but they need to be planned for and reviewed. I think a PEP is definitely in order for a change of this magnitude. -- nosy: +ned.deily, pablogsal ___ Python tracker <https://bugs.python.org/issue41282> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41282] Deprecate and remove distutils
Change by Ned Deily : -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue41282> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41268] 3.9-dev regression? TypeError: exec_module() missing 1 required positional argument: 'module'
Change by Ned Deily : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41268> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41236] "about" button in MacOS caused an error
Ned Deily added the comment: Terry, based on the error message provided, i.e. "About Widget Demo", I assumed that the poster was not using IDLE here. But we can't tell without more input. "when I run 3.9 test.pythoninfo, I am asked to install gcc tools and maybe xcode. Is this expected?" When doing Python development on macOS, you will need to have the Apple-supplied development tools installed and ones appropriate for the macOS release. As the Developer's Guide explains (https://devguide.python.org/setup/#macos-and-os-x), the necessary tools are available if you install the full Xcode development environment from the Mac App Store but that's a big download and most of it is not necessary for just cpython work. If you haven't already downloaded Xcode, then the first time you (or, in this case test.pythoninfo) try to use one of the development tools from the terminal shell command line, macOS offers to download and install a lightweight subset of what's available in Xcode, called the Command Line Tools. You can also force the installation of the CLT by using "xcode-select --install". Once the CLT are installed, they are normally automatically updated as needed by the macOS Software Update process. -- ___ Python tracker <https://bugs.python.org/issue41236> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41236] "about" button in MacOS caused an error
Ned Deily added the comment: Please say exactly how you reproduced this behavior. Please paste the results of running the following command from a terminal window: python3.7 -m test.pythoninfo replacing python3.7 with whatever you use to start the python that fails. -- ___ Python tracker <https://bugs.python.org/issue41236> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath
Ned Deily added the comment: New changeset 46cbf6148a46883110883488d3e9febbe46ba861 by Steve Dower in branch '3.6': [3.6] bpo-29778: Ensure python3.dll is loaded from correct locations when Python is embedded (GH-21298) (#21354) https://github.com/python/cpython/commit/46cbf6148a46883110883488d3e9febbe46ba861 -- ___ Python tracker <https://bugs.python.org/issue29778> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath
Ned Deily added the comment: New changeset 110dd153662a13b8ae1bb06348e5b1f118ab26d7 by Steve Dower in branch '3.7': [3.7] bpo-29778: Ensure python3.dll is loaded from correct locations when Python is embedded (GH-21297) (#21298) https://github.com/python/cpython/commit/110dd153662a13b8ae1bb06348e5b1f118ab26d7 -- ___ Python tracker <https://bugs.python.org/issue29778> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18080] setting CC no longer overrides default linker for extension module builds on OS X
Ned Deily added the comment: > Would you like me to file a separate bug for this issue? Or apply that patch? > Or something else? OK, if I understand correctly, the problem you describe does not affect cPython because cPython's Distutils does not use get_config_vars(), only get_config_var(); but other implementation's ports of Distutils may have diverged to use get_config_vars and so the test may fail when running under those implementations using setuptools with its newly cloned version of cPython Distutils. If that is the case, I think it's fine to backport the fix to cPython tests in the interest of minimizing differences. Since it is minor and not really user visible, if you're willing to do so, I'm OK with a PR under this bpo and I don't think a NEWS blurb is necessary. Thanks for bringing it up. -- ___ Python tracker <https://bugs.python.org/issue18080> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41212] Emoji Unicode failing in standard release of Python 3.8.3 / tkinter 8.6.8
Change by Ned Deily : -- assignee: -> ned.deily ___ Python tracker <https://bugs.python.org/issue41212> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41199] Docstring convention not followed for dataclasses documentation page
Change by Ned Deily : -- pull_requests: -20436 ___ Python tracker <https://bugs.python.org/issue41199> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue896330] pyconfig.h is not placed in --includedir
Change by Ned Deily : -- nosy: -Mario Gonzalez ___ Python tracker <https://bugs.python.org/issue896330> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue896330] pyconfig.h is not placed in --includedir
Change by Ned Deily : -- Removed message: https://bugs.python.org/msg372730 ___ Python tracker <https://bugs.python.org/issue896330> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18080] setting CC no longer overrides default linker for extension module builds on OS X
Ned Deily added the comment: Jason, what action(s) are you expecting with regard to this and by whom? This issue has been long closed. -- ___ Python tracker <https://bugs.python.org/issue18080> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41189] An exploitable segmentation fault in _PyEval_EvalFrameDefault
Ned Deily added the comment: > my only goal was to help Python community (which I love it) to improve the > code quality Thanks for trying to improve things, we do appreciate it! The idea here is that to be able to exploit the crashing pyc file, you need to be able to run an arbitrary pyc file on the web service and to do that the attacker has to have access somehow to the interpreter. If the web service has a hole to allow that, many bad things are possible. That's true for many other languages and tools, too. So it's just not worth worrying about being able to crash with a fuzzed pyc file since, if you can exploit that, you can exploit in much easier ways. -- ___ Python tracker <https://bugs.python.org/issue41189> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41189] An exploitable segmentation fault in _PyEval_EvalFrameDefault
Ned Deily added the comment: If users have unrestricted access to the interpreter, there are easier ways to crash Python than with modified byte code, for example, as is documented with ctypes. As noted on the Python Security Team web page (https://www.python.org/dev/security/): "If you can already execute Python code, there are far worse things you can do than provoke a use-after-free or an interpreter crash." -- ___ Python tracker <https://bugs.python.org/issue41189> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41189] An exploitable segmentation fault in _PyEval_EvalFrameDefault
Ned Deily added the comment: Sorry, if you modified the pyc file, that is undefined behavior. We make no guarantees that you can't crash the interpreter with arbitrary byte code. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41189> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41189] An exploitable segmentation fault in _PyEval_EvalFrameDefault
Ned Deily added the comment: Thank you for the report. Can you please supply the Python code that was translated into the .pyc file you supplied? If there is some reason that you don't want to post it to this issue, you can email it to secur...@python.org. -- ___ Python tracker <https://bugs.python.org/issue41189> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41181] [macOS] Build macOS installer with LTO and PGO optimizations
Ned Deily added the comment: er, "macOS 11.0 Big Sur" :) -- ___ Python tracker <https://bugs.python.org/issue41181> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41181] [macOS] Build macOS installer with LTO and PGO optimizations
Ned Deily added the comment: I should have made it clearer that we expect to release a new installer variant for macOS 11.6 Big Sur that supports both Intel and Apple Silicon architectures later this year (i.e. in several months) when Big Sur releases. It will be much easier to support newer optimizations in that variant. We are in the process right now of getting builds to work on the developer previews and on developer hardware. We will look at optimizations for that variant then. Please drop the idea of trying to change how we build on 10.9 (and, yes, we are perfectly capable of finding newer compilers to run on 10.9 but that's not the point - we *only* support building installers with standard Apple Developer Tool chains and with good reason); hacking on 10.9 is not worth it at this point. -- ___ Python tracker <https://bugs.python.org/issue41181> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41179] find_library on macOS Big Sur
Change by Ned Deily : -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41179> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41181] [macOS] Build macOS installer with LTO and PGO optimizations
Ned Deily added the comment:
> Clang 6.0 doesn't support LTO and PGO?
No, it appears not. And it's not an oversight that we don't use the these
options.
As Łukasz points out, for the current macOS installer variants we supply are
designed to run on all Mac systems from macOS 10.9 on. To accomplish that
safely, we build the Python binaries on macOS 10.9 system to ensure they will
be compatible, in other words, we build on the oldest system support and rely
on upward compatibility when running on newer systems. The other approach is to
build on the newest systems available after adding runtime checks throughout
the C code to test for the presence of newer features (i.e. runtime calls that
have been added in an operating system release newer than the oldest one
support). While this ("weaklinking") can be a viable option, it's a lot more
work to implement initially and then keep updated over each o/s release to
avoid segfaults and other failures when users on older systems try to use newer
features. Eventually we would like to fully support weaklinking so that we
could provide one installer variant for all supported o/s versions that has all
features available at each o/s version, it's not a high priority item at the
moment (for example, supporting the upcoming 11.0 Big Sur with Apple Silicon
is) and the current practices have worked well for many years.
Keep in mind that the main goal of the python.org macOS installers is to
provide a single installable binary that works correctly on a wide-range of
macOS releases and hardware. What we provide today works on all Macs capable
of running macOS 10.9 or later. In particular, it is *not* a goal to provide
the most optimized configuration for a particular system. In general, consider
the range of hardware and operating system releases, that's not easy to do. I
believe that the intended users for the python.org macOS pythons are (1)
beginners (like in a teaching environment where ease of deployment and
uniformity is key) and (2) third-party Mac applications developers who want an
embeddable Python that will allow their applications to work on multiple levels
of macOS. If you are looking for the highest performance for a particular use,
like benchmarking, you should look elsewhere - like one of the third-party
distributors who specialize in numeric Pythons - or build it yourself on your
own system.
So, thanks for the suggestion but we won't be using it now. Sometime in the
future, if and when we support weaklinking and/or use newer toolchains across
the board we will look at adding and other optimizations.
--
resolution: -> not a bug
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue41181>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41004] Hash collisions in IPv4Interface and IPv6Interface
Ned Deily added the comment: New changeset cfc7ff8d05f7a949a88b8a8dd506fb5c1c30d3e9 by Tapas Kundu in branch '3.6': [3.6] bpo-41004: Resolve hash collisions for IPv4Interface and IPv6Interface (GH-21033) (GH-21232) https://github.com/python/cpython/commit/cfc7ff8d05f7a949a88b8a8dd506fb5c1c30d3e9 -- ___ Python tracker <https://bugs.python.org/issue41004> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41004] Hash collisions in IPv4Interface and IPv6Interface
Ned Deily added the comment: New changeset b98e7790c77a4378ec4b1c71b84138cb930b69b7 by Tapas Kundu in branch '3.7': [3.7] bpo-41004: Resolve hash collisions for IPv4Interface and IPv6Interface (GH-21033) (GH-21231) https://github.com/python/cpython/commit/b98e7790c77a4378ec4b1c71b84138cb930b69b7 -- ___ Python tracker <https://bugs.python.org/issue41004> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41004] Hash collisions in IPv4Interface and IPv6Interface
Ned Deily added the comment: A legitimate CVE should certainly be backported to all applicable releases, so, yes. However, I think that it is important for the CVE to be mentioned in the NEWS blurbs for each commit. So please update the NEWS items in each open PR to include the CVE. For master and 3.9 (if you hurry), you can update the original blurb file. For 3.8, the blurb file is in the process of being merged into the blurb for the release; for it, wait until the v3.8.4rc1 has been merged back into the main cpython repo and then update the merged the blob, please. Thanks! -- ___ Python tracker <https://bugs.python.org/issue41004> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding
Ned Deily added the comment: Thanks for the PR! With the backports to 3.9 and 3.8 in place, I am assuming we can now close this issue. -- nosy: +ned.deily resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41048> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding
Change by Ned Deily : -- versions: -Python 3.7 ___ Python tracker <https://bugs.python.org/issue41048> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41100] Build failure on macOS 11 (beta)
Ned Deily added the comment: [Moving the discussion from Issue41164 to here.] The change in PR 21224 may be needed to successfully build but I'm not sure whether that LIBTOOL_CRUFT stuff is still needed. With a squick search, I don't see any references to it anymore. But it won't hurt to add it. -- ___ Python tracker <https://bugs.python.org/issue41100> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41164] allow python to build for macosx-11.0-arm64
Ned Deily added the comment: Lawrence, thanks for the PR. We appreciate any insights from you all. We ahve already started to build using the first seed of Big Sur and have already committed some fixes. Rather than having multiple open issues covering the same topic, I'd like to suggest that we use the existing one Issue41100 to consolidate the PRs; to that end, I've changed the title of your PR (PR 21224) to reference that issue and I'm going to close this one. I'll add you to the other issue and we can continue discussions. BTW, I believe a DTK is in Ronald's future :) -- nosy: +ned.deily resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> Build failure on macOS 11 (beta) ___ Python tracker <https://bugs.python.org/issue41164> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41129] Python extension modules fail to build on Mac 10.15.1 (Catalina)
Ned Deily added the comment: PS. Or try doing an out-of-tree build. Perhaps the problem is just due to trying to do the build under that unconventional location under /. cd ~/build ./path/to/sourcetree/configure ... make ... -- ___ Python tracker <https://bugs.python.org/issue41129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41129] Python extension modules fail to build on Mac 10.15.1 (Catalina)
Ned Deily added the comment: > Do you know of any easy ways to disable mac OS sandboxes from being used in > the python build from the command line? Please show the exact steps you used to build this, in particular, the full ./configure statement and any relevant env variable settings. I don't know how to disable the sandboxes because I've never seen something like this before and I don't know for sure how to reproduce. If I had to take a guess, I suspect it has to do with the location of your source tree which looks like it might be at a unconventional location at the root level: /mathworks/devel. As you may know, macOS 10.15 Catalina has made a lot of under the cover changes to file system structure including the splitting of / into immutable and mutable subvolumes (/System/Volumes/Data). You may want to try moving /mathworks to another location rather than directly under /, perhaps under /opt or under /Users. -- ___ Python tracker <https://bugs.python.org/issue41129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12915] Add inspect.locate and inspect.resolve
Ned Deily added the comment: See bpo-41154 for possible regression introduced by these changes. -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue12915> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41154] test_pkgutil:test_name_resolution fails on some platforms
Ned Deily added the comment: PS, the problem may have been introduced by the changes for bpo-12915. -- ___ Python tracker <https://bugs.python.org/issue41154> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41154] test_pkgutil:test_name_resolution fails on some platforms
Ned Deily added the comment: This same failure is observed with the most recent 3.9beta (3.9.0b3) when running on macOS 10.9 with the binaries from the python.org macOS installer. However, no failure is seen when running the same Python on macOS 10.15. I have not investigated further with other releases. This test failure should be addressed prior t0 3.9.0rc1. -- nosy: +ned.deily, vstinner priority: normal -> deferred blocker title: test_pkgutil:test_name_resolution fails on master -> test_pkgutil:test_name_resolution fails on some platforms versions: +Python 3.9 ___ Python tracker <https://bugs.python.org/issue41154> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37706] IDLE: fix sidebar click-drag bug and macOS test failures
Ned Deily added the comment: Running the GUI test on macOS buildbots is not straightforward, AFAIK. We'd need to have either the console logged in to the username that the tests are running under or, better, the buildbot would need to run in a virtual machine. We have had a chronic shortage of macOS buildbots anyway. Plus the automated tests aren't all that good at finding the nasty problems that pop up in the intersection of the user, IDLE, and macOS Tk; at the moment, there's no substitute for manual testing. -- ___ Python tracker <https://bugs.python.org/issue37706> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41058] pdb reads source files using the locale encoding
Change by Ned Deily : -- versions: -Python 3.7 ___ Python tracker <https://bugs.python.org/issue41058> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41068] zipfile: read after write fails for non-ascii files
Change by Ned Deily : -- versions: -Python 3.7 ___ Python tracker <https://bugs.python.org/issue41068> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41100] Build failure on macOS 11 (beta)
Ned Deily added the comment: New changeset 2f168c6356f92c38ae7751d2faf2b266a9356229 by Ned Deily in branch 'master': bpo-41100: clarify NEWS item about macOS 11 support (GH-21174) https://github.com/python/cpython/commit/2f168c6356f92c38ae7751d2faf2b266a9356229 -- ___ Python tracker <https://bugs.python.org/issue41100> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41100] Build failure on macOS 11 (beta)
Change by Ned Deily : -- pull_requests: +20332 pull_request: https://github.com/python/cpython/pull/21174 ___ Python tracker <https://bugs.python.org/issue41100> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41129] Python extension modules fail to build on Mac 10.15.1 (Catalina)
Ned Deily added the comment: To be honest, I've never seen a failure quite like that before so thanks for that! A couple of observations: you appear to be using an old version of Xcode (11.0.0) that may not be fully supported on 10.15.x. So I would try upgrading to the latest released Xcode for 10.15, which is Xcode 11.5 at the moment or make sure your copy of the Command Like Tools is really up to date (you don't need a full-blown Xcode to build python). xcode-select -p should show which you have selected. You should see one of the following: $ cc --version Apple clang version 11.0.3 (clang-1103.0.32.62) Target: x86_64-apple-darwin19.5.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin or Apple clang version 11.0.3 (clang-1103.0.32.62) Target: x86_64-apple-darwin19.5.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin But that may be a secondary matter. The most interesting things in the snippet you display are the paths to the header files. for example: /System/Volumes/Data/mathworks/devel/sandbox/aflewell/python38_source/Python-3.8.2 which are absolute paths that suggest the build process you are using is somehow using macOS sandboxes. Yet the paths to the actual source file being compiled amd its output file are unprefixed relative paths. So I suggest you figure out why those sandbox paths are in there. A straightforward build from within the source tarball expanded in a non-sandboxed directory, for example under $HOME or /tmp, should work just fine. Keep in mind that in any case you will still run into some missing modules like _ssl and _hashlib unless you supply copies of third-party libraries that macOS does not or no longer provides; the Python Developer's Guide has some suggestions (https://devguide.python.org/setup/#macos-and-os-x). -- resolution: -> works for me status: open -> pending ___ Python tracker <https://bugs.python.org/issue41129> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41093] TCPServer's server_forever() shutdown immediately when calling shutdown()
Change by Ned Deily : -- nosy: -ned.deily versions: +Python 3.10 -Python 3.7 ___ Python tracker <https://bugs.python.org/issue41093> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41116] build on macOS 11 (beta) does not find system-supplied third-party libraries
Ned Deily added the comment: I should have specified that the failures I saw were just with the default intel-64 arch on the beta. After thinking about it a bit and reviewing the code, I think the best approach is to handle this in _osx_support.py as part of the compiler flags customization. What's been happening over the years is that Apple has been deprecating and then removing system header files and system library files on running systems and instead forcing the use of an SDK to build with for both. That's fine but, to continue to support a range of systems, we should be able to handle the various default configurations when the user does not explicitly specify a particular SDK to use. The Apple compiler chain does the right thing under the covers so that C compilations just work. setip.py's macosx_sdk_root() now has initialization code to discover the path to the system header files that the compiler is using; it calls the compiler with -v on a dummy program and then scans the compiler output for the include paths searched until it finds either /usr/include or a path ending in .sdk/usr/include. (It's a bit of a hack but a fairly widely-used hack that works with both clang and gcc, at least, and for the Apple-supplied compilers, takes into account the dynamic specification of SDK via xcrun.) I think the thing to do is move that sdk path detection into _osx_support and then, at the end of other customization steps, if there isn't already a valid -isysroot provided by the user (either through ./configure or CFLAGS et al, add a -isysroot for the discovered default SDK path (or /) into the appropriate customized compiler and linker flags. It would also provide a function to return the SDK path for setup.py (the equivalent of the current macosx_sdk_root()) and others to use. setup.py and Distutils should then do the right things for both header and library file paths on any configuration (whether header files are installed or not and whether lib files are installed or not, Command Line Tools or Xcode) and, with luck, any other Distutils replacements that also use _osx_support will also do the right thing. I had contemplated removing _osx_support at some point in the future but, now with the return of universal files, I'm glad we didn't. -- ___ Python tracker <https://bugs.python.org/issue41116> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41116] build on macOS 11 (beta) does not find system-supplied third-party libraries
New submission from Ned Deily : When building on macOS 11 (beta), a number of modules that should normally build on macOS fail because the system-supplied third-party libraries are not found. The necessary bits to build these optional modules were not found: _bz2 _curses _curses_panel _gdbm _hashlib _lzma _ssl ossaudiodev readline spwd zlib The list should look like this (with no additional third-party libs supplied from another source like Homebrew or MacPorts): The necessary bits to build these optional modules were not found: _gdbm _hashlib _ssl ossaudiodev spwd The problem is due to a change in the 11 beta versus 10.15 or earlier systems: "New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache." This breaks tests in setup.py using find_library_file() to determine if a library is present and in what directory it exists. setup.py depends on Lib/distutils/unixccompiler.py to do the dirty work. A similar problem arose on earlier macOS releases when header files could no longer be installed in the systems /usr/include; setup.py had to be taught to look in the SDK being used implicitly or explicitly by the compiler preprocessor. We could probably do something like that here while trying to avoid changes that might break downstream supplements/replacements to distutils, for example, setuptools. There is a workaround: explicitly specify the SDK location to ./configure (you also need to specify the universal archs setting): ./configure \ --enable-universalsdk=$(xcodebuild -version -sdk macosx Path) \ --with-universal-archs=intel-64 \ ... -- components: macOS messages: 372379 nosy: ned.deily, ronaldoussoren priority: high severity: normal status: open title: build on macOS 11 (beta) does not find system-supplied third-party libraries versions: Python 3.10, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue41116> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41100] Build failure on macOS 11 (beta)
Ned Deily added the comment: New changeset cfbc759f918d646a59acb99251fc10b3900248a6 by Miss Islington (bot) in branch '3.7': BPO-41100: Support macOS 11 when building (GH-21113) (GH-21155) https://github.com/python/cpython/commit/cfbc759f918d646a59acb99251fc10b3900248a6 -- ___ Python tracker <https://bugs.python.org/issue41100> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41100] Build failure on macOS 11 (beta)
Ned Deily added the comment: New changeset 8ea6353f60625c96ce96588c70ff24a77f8c71f9 by Ronald Oussoren in branch 'master': BPO-41100: Support macOS 11 when building (GH-21113) https://github.com/python/cpython/commit/8ea6353f60625c96ce96588c70ff24a77f8c71f9 -- ___ Python tracker <https://bugs.python.org/issue41100> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40939] Remove the old parser
Ned Deily added the comment:
New changeset 8d02f91dc6139a13b6efa9bd5a5b4bdd7ddcc29d by Ned Deily in branch
'master':
bpo-40939: run autoreconf to fix configure{,.ac} disparity (GH-21152)
https://github.com/python/cpython/commit/8d02f91dc6139a13b6efa9bd5a5b4bdd7ddcc29d
--
___
Python tracker
<https://bugs.python.org/issue40939>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40939] Remove the old parser
Change by Ned Deily : -- nosy: +ned.deily nosy_count: 7.0 -> 8.0 pull_requests: +20311 pull_request: https://github.com/python/cpython/pull/21152 ___ Python tracker <https://bugs.python.org/issue40939> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41009] @support.requires_*_version broken for classes
Change by Ned Deily : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue41009> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41009] @support.requires_*_version broken for classes
Ned Deily added the comment: New changeset d3798ed9f1762dcf632369505d517f476eccde13 by Christian Heimes in branch '3.7': [3.7] bpo-41009: fix requires_OS_version() class decorator (GH-20942) (GH-20949) https://github.com/python/cpython/commit/d3798ed9f1762dcf632369505d517f476eccde13 -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue41009> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration
Ned Deily added the comment: New changeset 7318f0ab234e1c60a19eeea4e5968fb5d4fd70af by Ned Deily in branch '3.8': bpo-40204: Pin Sphinx version to 2.3.1 in ``Doc/Makefile``. (GH-21141) (GH-21147) https://github.com/python/cpython/commit/7318f0ab234e1c60a19eeea4e5968fb5d4fd70af -- ___ Python tracker <https://bugs.python.org/issue40204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration
Change by Ned Deily : -- pull_requests: +20306 pull_request: https://github.com/python/cpython/pull/21147 ___ Python tracker <https://bugs.python.org/issue40204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration
Ned Deily added the comment: New changeset 589e8fe07934a8585d6c5c31d12ae5f766b8fec7 by Ned Deily in branch 'master': bpo-40204: Pin Sphinx version to 2.3.1 in ``Doc/Makefile``. (GH-21141) https://github.com/python/cpython/commit/589e8fe07934a8585d6c5c31d12ae5f766b8fec7 -- ___ Python tracker <https://bugs.python.org/issue40204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40400] Mac build-installer.py doesn't support new plist format
Ned Deily added the comment: Thanks for the report. There were several issues, including this one, when trying to run build-installer.py under current versions of Python 3. These have been fixed in the version of build-installer.py to be released with 3.9.0b4, 3.8.4, and 3.7.8. -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.10, Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue40400> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40204] Docs build error with Sphinx 3.0 due to invalid C declaration
Change by Ned Deily : -- pull_requests: +20300 pull_request: https://github.com/python/cpython/pull/21141 ___ Python tracker <https://bugs.python.org/issue40204> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39580] Check for COMMAND_LINE_INSTALL variable in Python_Documentation.pkg
Ned Deily added the comment: Thanks again for the PR. The change will be included in python.org installers for macOS as of 3.9.0b4, 3.8.4, and 3.7.8. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue39580> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23903] Generate PC/python3.def by scraping headers
Change by Ned Deily : -- nosy: -ned.deily versions: -Python 3.7 ___ Python tracker <https://bugs.python.org/issue23903> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39580] Check for COMMAND_LINE_INSTALL variable in Python_Documentation.pkg
Ned Deily added the comment: New changeset 5f190d2cc60cd82a604cbffb58b6ca8f40350a7a by Rick Heil in branch 'master': bpo-39580: add check for CLI installation on macOS (GH-20271) https://github.com/python/cpython/commit/5f190d2cc60cd82a604cbffb58b6ca8f40350a7a -- ___ Python tracker <https://bugs.python.org/issue39580> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40824] Unexpected errors in __iter__ are masked in "in" and the operator module
Change by Ned Deily : -- versions: -Python 3.6, Python 3.7 ___ Python tracker <https://bugs.python.org/issue40824> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40824] Unexpected errors in __iter__ are masked in "in" and the operator module
Ned Deily added the comment: @Serhiy, you have opened PRs for this for 3.7 and 3.6, both of which are now in the security-fix phase of their release cycles. It looks like this behavior has been around for a long time and does not appear to be a security issue. Unless there is some important reason why this behavior should be changed in a security fix release (for 3.6) or as a release critical fix for 3.7.8 final and unless another core developer reviews the changes, I do not think the PRs should be merged to 3.7 or 3.6. -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue40824> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41093] BaseServer's server_forever() shutdown immediately when calling shutdown()
Ned Deily added the comment: > By the way I have to ask, if I want this feature to be merged (this is my > first PR) Thank you for the PR and your contribution! Unless a PR is for a problem specific to a release, simply submit a PR against the master branch. If and when a core developer chooses to merge the PR, a decision will be made about whether to backport it and we have tools to do that semi-automatically. Be aware that, since we are all volunteers here, some areas in the code base do not receive a lot of attention and http.server is one of them. So don't be discouraged if your PR is not reviewed right away. A ping down the road may help. -- nosy: +ned.deily ___ Python tracker <https://bugs.python.org/issue41093> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
