bpo-32101: Add PYTHONDEVMODE environment variable#4624
Conversation
|
Oh, test_sys fails in development mode, but it's unrelated to this PR: bug fixed by PR #4625. Another bug: test_faulthandler and test_asyncio now fail with PYTHONDEVMODE=1. |
Sorry, something went wrong.
Rename also the "Developer mode" to the "Development mode".
Mention it in the development chapiter.
|
I rebased my change to get the memory allocator fixes (commit 5d39e04), and I documented the "Python development mode" in the Development chapiter of the documentation. |
Sorry, something went wrong.
|
Ok, the patch now works properly, and the full Python test suite pass with PYTHONDEVMODE=1. @ncoghlan, @pitrou: What do you think of adding sys.flags.dev_mode? I chose to make sys.flags.dev_mode a boolean, whereas other flags are integer and have a Py_xxx variable in C. |
Sorry, something went wrong.
ncoghlan
left a comment
There was a problem hiding this comment.
Looks good to me. I'm OK with the idea of committing to dev mode being an "all or nothing" toggle - the more fine-grained control already exists in the form of the underlying settings that dev mode groups together.
Sorry, something went wrong.
Add also the sys.flags.dev_mode flag.
https://bugs.python.org/issue32101