Message292718
I don't find it helpful to think of it as declaring 3.6.0 broken vs declaring 3.6.1 broken. 3.6.0 is definitely good in the sense that if you build a module on it then it will import on both 3.6.0 and 3.6.1, and 3.6.1 is definitely good in the sense that if you're using it then you can import any module that was built on 3.6.0 or 3.6.1.
I think 3.6.2 should combine the best aspects of 3.6.0 and 3.6.1, in the sense that modules built on 3.6.2 should be importable on any 3.6.x, and 3.6.2 should be able to import modules built on any 3.6.x.
Fortunately this is very easy – it just means that 3.6.2 should continue to export the PySlice_AdjustIndices symbol (because existing 3.6.1 builds will need it to import on 3.6.2), but should remove the #define of PySlice_GetIndicesEx (so code built against 3.6.2 will not *require* PySlice_AdjustIndices to be present).
Removing 3.6.0 and 3.6.1 from circulation is simply not possible; the best 3.6.2 can hope for is to interoperate with them as well as possible. |
|
Date |
User |
Action |
Args |
2017-05-02 06:36:49 | njs | set | recipients:
+ njs, larry, benjamin.peterson, ned.deily, cgohlke, skrah, serhiy.storchaka, steve.dower, cstratak, hroncok |
2017-05-02 06:36:49 | njs | set | messageid: <1493707009.3.0.813257731714.issue29943@psf.upfronthosting.co.za> |
2017-05-02 06:36:49 | njs | link | issue29943 messages |
2017-05-02 06:36:49 | njs | create | |
|