Message157351
| Author |
jeffr@livedata.com |
| Recipients |
amaury.forgeotdarc, benjamin.peterson, georg.brandl, jeffr@livedata.com, kristjan.jonsson, pitrou, python-dev, skrah |
| Date |
2012年04月02日.12:16:58 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<060AD9574BAB473F820DD3F4AEEDDAE7@FamilyPC> |
| In-reply-to |
<1333280888.87.0.587275702453.issue14387@psf.upfronthosting.co.za> |
| Content |
I'm happy to try another build of apsw, but am not up-to-speed with how to
get development copies of Python. As a user, I typically download the
latest Windows .msi file and install it. If you can point me to a document
on how to proceed, I'll give it a try.
I'm Bcc'ing the APSW author in the event he can give it a try.
----- Original Message -----
From: "Stefan Krah" <report@bugs.python.org>
To: <jeffr@livedata.com>
Sent: Sunday, April 01, 2012 7:48 AM
Subject: [issue14387] Include\accu.h incompatible with Windows.h
Stefan Krah <stefan-usenet@bytereef.org> added the comment:
> Should I contact the extension's author(s)/maintainer(s) and tell them
> about this ordering requirement?
FWIW, it is the recommended way in the docs.
The Python build itself has been fixed. Does the
http://code.google.com/p/apsw/ module build now?
----------
_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue14387>
_______________________________________ |
|