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 loewis
Recipients loewis, rjs
Date 2011-03-22.20:15:33
SpamBayes Score 1.2332796e-05
Marked as misclassified No
Message-id <4D890364.1050408@v.loewis.de>
In-reply-to <1300785712.91.0.635985427936.issue11626@psf.upfronthosting.co.za>
Content
> I fear I don't understand exactly what is meant here. For me it was enough to get the linker error telling me it is not working.

Suppose 3.2.1 adds this function, which then means that your extension
builds fine. However, it won't run on 3.2.0, so you might complain that
the ABI isn't really "stable". Therefore, I wonder whether you would
have liked to continue receiving compile-time indications that you are
using parts of the ABI which had not been around in 3.2.0.

Now that you know, you *personally* probably don't need this
notification anymore. I just wonder about people in similar situations.
History
Date User Action Args
2011-03-22 20:15:34loewissetrecipients: + loewis, rjs
2011-03-22 20:15:33loewislinkissue11626 messages
2011-03-22 20:15:33loewiscreate