Message187971
| Author |
lemburg |
| Recipients |
Joakim.Sernbrant, Marc.Abramowitz, dmalcolm, georg.brandl, lemburg, ned.deily, petri.lehtinen, python-dev, serhiy.storchaka |
| Date |
2013年04月28日.08:44:21 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<517CE163.7090300@egenix.com> |
| In-reply-to |
<1367119253.04.0.752457610441.issue17857@psf.upfronthosting.co.za> |
| Content |
On 28.04.2013 05:20, Ned Deily wrote:
>
> Ned Deily added the comment:
>
> Marc-Andre, can you elaborate on why you think Python 3 is not affected? The changes for Issue17073 also added sqlite3_int64 to 3.2, 3.3, and default and, for me on 10.4, _sqlite3.so currently fails to build in all three. (I don't think 3.2 is worth worrying about but if Georg does spin a brown bag 3.2.5 he could cherry pick it.)
Oh, I just did a grep on the Python 3.3.0 code base and couldn't
find any hits. Was the issue you mentioned applied to the 3.3.1 dot
release ?
If so, then those new mentions will have to be fixed as well,
of course. |
|