-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-46968: Add os.sysconf_names['SC_MINSIGSTKSZ'] #31824
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
Conversation
@oleksandr-pavlyk: Would you mind to review my change? |
See also #31789 |
I am not sure I understand how this preprocessor variable gets populated and with what value. Is the intent to expose the value of |
After building with
|
The intent is to provide the constant if present at compile time so that one could write |
Thank you for the explanation. This would be the way for Python user using pre-built distribution to infer the value of preprocessor variable What confuses me is that the key It would also be useful to expose the actual value of |
Maybe your OS (glibc version) doesn't have the constant yet. I'm using Fedora 35 which provides glibc 2.34:
|
The intented usage is just:
But it also works to pass directly the constant
|
Thanks for the review @gpshead. I merged my PR. |
I would prefer to not expose such low-level value. In Python, we try to provide high-level API like "implement a signal handler": Outside faulthandler, I'm not aware of any stdlib module which needs to run a signal handler with its own dedicated stack. |
On Linux, glibc It doesn't seem like a hardcoded constant, but a value sent to userspace by the kernel. Or maybe I misunderstood your commeent. Are you talking about the |
Yes indeed, my bits/confname.h does not have that constant. I tried reviewing it, learned something new :) |
For future reference about |
https://bugs.python.org/issue46968