Message265109
| Author | martin.panter |
|---|---|
| Recipients | Arfrever, Keith.Dart, Michael.Felt, christian.heimes, eric.araujo, hynek, kdart, knny-myer, martin.panter, nailor, nvetoshkin, orsenthil, pitrou, r.david.murray, serhiy.storchaka |
| Date | 2016-05-08.03:24:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1462677894.34.0.849473945862.issue11063@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The versioning problem with libFOO.so.N already occurs with compiled programs. A C program compiled against libuuid.so.1 will fail to load if you only have libuuid.so.2. On the other hand, a Python program using find_library() will find either version. My point about robustness is that if a version 2 is invented, it might have different semantics or function signatures, and Python would then be assuming the wrong semantics. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-05-08 03:24:54 | martin.panter | set | recipients: + martin.panter, orsenthil, kdart, pitrou, christian.heimes, eric.araujo, Arfrever, r.david.murray, nvetoshkin, knny-myer, nailor, Keith.Dart, hynek, serhiy.storchaka, Michael.Felt |
| 2016-05-08 03:24:54 | martin.panter | set | messageid: <1462677894.34.0.849473945862.issue11063@psf.upfronthosting.co.za> |
| 2016-05-08 03:24:54 | martin.panter | link | issue11063 messages |
| 2016-05-08 03:24:53 | martin.panter | create | |