Message 396461 - Python tracker
Message396461
| Author | jakirkham |
|---|---|
| Recipients | amacd31, christian.heimes, jakirkham, jan-xyz, matan1008, methane, ronaldoussoren |
| Date | 2021-06-24.08:34:13 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1624523653.14.0.674031322838.issue42853@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Right with this change ( https://github.com/python/cpython/pull/25468 ). Thanks for adding that Christian :) I guess what I'm wondering is if in older Python versions we could do an `#ifdef` check to try and use `SSL_read_ex` & `SSL_write_ex` if the symbols are found at build time? This would allow package maintainers the option to build with a newer OpenSSL to fix this issue (even on older Pythons) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-06-24 08:34:13 | jakirkham | set | recipients: + jakirkham, ronaldoussoren, christian.heimes, methane, matan1008, amacd31, jan-xyz |
| 2021-06-24 08:34:13 | jakirkham | set | messageid: <1624523653.14.0.674031322838.issue42853@roundup.psfhosted.org> |
| 2021-06-24 08:34:13 | jakirkham | link | issue42853 messages |
| 2021-06-24 08:34:13 | jakirkham | create | |