This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | koobs |
|---|---|
| Recipients | Arfrever, Danya.Alexeyevsky, benjamin.peterson, berker.peksag, davin, koobs, larry, lemburg, pitrou |
| Date | 2015年03月21日.13:56:04 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1426946164.94.0.723037039966.issue23042@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
@marc I took a look at the code upstream and it does indeed appear to be the same. It was introduced in 3.1 [1]. I cant explain however how or why our Python ports work with libffi 3.2.1. See msg238767 for a link to another similar (same?) issue, with failure of OSX on 3.2.1 (building libffi, not python) [1] https://github.com/atgreen/libffi/commit/e1911f78df113ca58738b66089a070d4cf747de7 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015年03月21日 13:56:04 | koobs | set | recipients: + koobs, lemburg, pitrou, larry, benjamin.peterson, Arfrever, Danya.Alexeyevsky, berker.peksag, davin |
| 2015年03月21日 13:56:04 | koobs | set | messageid: <1426946164.94.0.723037039966.issue23042@psf.upfronthosting.co.za> |
| 2015年03月21日 13:56:04 | koobs | link | issue23042 messages |
| 2015年03月21日 13:56:04 | koobs | create | |