GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — [3.14] gh-135427: Fix DeprecationWarning for os.fork when run in threads with -Werror (GH-136796) by gpshead · Pull Request #140191 · python/cpython Conversation
|
|
🤖 New build scheduled with the buildbot fleet by @gpshead for commit b02aefc 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F140191%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Should we backport this? Warnings changes in patch releases make it harder to update, and from comments like #135427 (comment) it sounds like it's important to fix this now. But, if you think it should get a backport, let's do it :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I don't think this one is actually urgent to backport. I'll close this, the PR is ready and can be resurrected if deemed important. So -Werror doesn't turn it into an error in 3.14 but we've fixed that in 3.15? good enough. This is an odd warning - it'll probably never become an error because our detection can only ever be best effort (it cannot be guaranteed to detect if other threads exist), it's more of the best way to surface an application design flaw to users. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
^^; one reference point is that I ran into this new error on a test suite on 3.15, and the issue was that the test suite had |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.