Message296040
| Author | vstinner |
|---|---|
| Recipients | Devin Jeanpierre, benjamin.peterson, josh.r, mark.dickinson, pitrou, serhiy.storchaka, vstinner |
| Date | 2017-06-14.21:30:52 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1497475852.11.0.660890632214.issue17870@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Serhiy Storchaka: "The patch adds too much code, but there is very little need of new feature (...)" I wrote my first patch in 2013, but I still fail to find a very good example where intmax_t would be an obvious choice. So I have to agree and I will now close the issue. If you still want to get a builtin support for intmax_t in CPython, please come with a strong rationale for justify adding "so much code" ;-) I now close the issue and reject my PR. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-06-14 21:30:52 | vstinner | set | recipients: + vstinner, mark.dickinson, pitrou, benjamin.peterson, Devin Jeanpierre, serhiy.storchaka, josh.r |
| 2017-06-14 21:30:52 | vstinner | set | messageid: <1497475852.11.0.660890632214.issue17870@psf.upfronthosting.co.za> |
| 2017-06-14 21:30:52 | vstinner | link | issue17870 messages |
| 2017-06-14 21:30:52 | vstinner | create | |