Message269748
| Author |
ned.deily |
| Recipients |
ned.deily, vstinner, xdegaye, yan12125 |
| Date |
2016年07月03日.00:09:51 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1467504592.19.0.611802688685.issue27442@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Typically, for other sorts of build configuration data, we have relied on extracting that from the ./configure-produced Makefile and making it available via sysconfig.get_config_var(). I think we should be cautious about bloating sys.implementation with platform-specific data unless there is an overriding need for it, for example, if it is needed during interpreter initialization before sysconfig can be initialized. If not, I'd look at adding the needed values as configuration variables in configure.ac. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年07月03日 00:09:52 | ned.deily | set | recipients:
+ ned.deily, vstinner, xdegaye, yan12125 |
| 2016年07月03日 00:09:52 | ned.deily | set | messageid: <1467504592.19.0.611802688685.issue27442@psf.upfronthosting.co.za> |
| 2016年07月03日 00:09:52 | ned.deily | link | issue27442 messages |
| 2016年07月03日 00:09:51 | ned.deily | create |
|