-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Debug builds? #73
Comments
@wesm Also take a look at conda-forge/staged-recipes#1593 and conda-forge/staged-recipes#961 |
Just created the pull request #86 about this |
This is a great idea that we should really revive (especially as the tooling has caught up a bit). Raised issue ( conda-forge/conda-forge.github.io#544 ) to discuss how we do split packages and generate things like debug builds as products. |
@msarahan, do you know if any work has been done on this front in |
It's worth noting as of Python 3.8 the interpreter includes all debug symbols. So a separate debug build is no longer needed for 3.8+. ref: https://docs.python.org/3/whatsnew/3.8.html#debug-build-uses-the-same-abi-as-release-build cc @conda-forge/core (for visibility) |
With some of the recent work on PyPy, this seems more doable. Raising issue ( conda-forge/conda-forge.github.io#1017 ) to discuss. |
I did some work for debug builds on Windows on Python 3.8. The ABI is not exactly the same. There is one symbol of difference ("CreateModule2" gets suffixed "Refcounted" or something like that). I used this when I was looking into a Python 3.8 issue on Windows with LIEF. It builds a load of stuff with a huge amount of debug info using a very hacky batch file. To tweak change what gets built, see: https://github.com/AnacondaRecipes/python-feedstock/blob/master/build-locally-debug.bat#L3-L21 If anyone has time, this is how to run it. You need my latest WIP conda-build branch too!
I've only ever run this on my own machines and without I think Unix Python debug builds would be a great idea and should be pretty easy to get going. For Windows, I'd like us to do something different which is to heed the upstream maintainer's advice that we should make a release-with-debug-symbols build as our python 3.8 debug builds, for now at least. Cheers! |
Thanks Ray! 😄
Did this get raised upstream? |
Only in the sense that Steve Dower is the upstream main Windows Python maintainer. |
I guess at Python 3.9 there might be some official debuggable-release build config.. maybe! Or we should put in the work and submit a PR. |
I see. Well at the bare minimum and issue would be useful to aid prioritization/visibility. |
Any idea how much work it would be to have a, say,
3.5-debug
Python version? Maybe this is already available somewhere.The text was updated successfully, but these errors were encountered: