-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a new -X dev option: "developer mode" #76224
Comments
I propose to add a new "developer mode": a new "-X dev" command line option. In short: For the rationale, please see: |
Antoine Pitrou asked me to document the performance and memory overhead of -X dev: https://mail.python.org/pipermail/python-dev/2017-November/150578.html For example, I measured an increase of +50% on the peak memory usage (measured by tracemalloc) when running test_os. Antoine proposed: """Currently, developer mode adds negligible CPU time overhead, but can https://mail.python.org/pipermail/python-dev/2017-November/150579.html |
I created bpo-32101: Add PYTHONDEVMODE=1 to enable the developer mode. |
While the discussion is not done, I close this issue to focus on other more specific issues. I completed the documentation and fixed warnings filters (bpo-32089). The option now also enables asyncio debug mode (bpo-32047). It was proposed to add an environment variable to enable the developer mode: see bpo-32101 ("Add PYTHONDEVMODE=1 to enable the developer mode"). Note: I also fixed subprocess._args_from_interpreter_flags: bpo-32094. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: