Message306288
I wrote a new "_PyInitError" type to report more information when something goes wrong:
* indicate if it's an user error: don't abort() in that case
* function name where the error was raised
* error message
Example:
---
$ PYTHONHASHSEED=x ./python
Fatal Python error: _Py_HashRandomization_Init: PYTHONHASHSEED must be "random" or an integer in range [0; 4294967295]
---
=> Python doesn't fail with abort() anymore
=> notice the new "_Py_HashRandomization_Init" function name which gives context to the error message
Previously, Python called abort() and so might dump a core file:
---
$ PYTHONHASHSEED=x python3
Fatal Python error: PYTHONHASHSEED must be "random" or an integer in range [0; 4294967295]
Aborted (core dumped)
--- |
|
Date |
User |
Action |
Args |
2017-11-15 17:27:04 | vstinner | set | recipients:
+ vstinner, barry, ncoghlan, eric.snow |
2017-11-15 17:27:04 | vstinner | set | messageid: <1510766824.54.0.213398074469.issue32030@psf.upfronthosting.co.za> |
2017-11-15 17:27:04 | vstinner | link | issue32030 messages |
2017-11-15 17:27:04 | vstinner | create | |
|