[Biopython-dev] Compiling Biopython on 64 bit Windows, was: Volunteer buildslave machines?

[Manlio Calvi]

I'm running the tests against a WinPython x64 3.3.3.3 at the moment
(so a non-Python.org distro) and will see if that happens there too,
I'm planning to install a native one(if the time permits).

Manlio

On Mon, Apr 21, 2014 at 6:33 PM, Peter Cock <p.j.a.cock at googlemail.com> wrote:
> On Mon, Apr 21, 2014 at 5:25 PM, Manlio Calvi <manlio.calvi at gmail.com> wrote:
>> Works as expected because I have Numpy modules running in other
>> scripts (dumps the path to __init__.py)
>>
>> In C:\Python34\Lib\site-packages\Bio the non-py files are two:
>> cpairwise2.pyd
>> trie.pyd
>>
>> The same are in the folder I used to build them, and by the extension
>> should be callable/importable.
>> I tried to import cpairwise2 but (don't) work the same way, same error
>> raised as before.
>>
>
> So, if you've done an install & can't import the C modules, that
> tells me this isn't a simply problem in our test harness (run_tests.py
> does some magic with the Python path to try to test using the just
> built files rather than any installed files).
>
> This is a deeper problem with building/installing under Python 3.4
> on your setup. I have for the moment run out of ideas :(
>
> (Other than trying Python 3.3 which may behave differently - and
> will be useful anyway for checking the other test failures and if they
> are in part due to the new Python version).
>
> Thanks,
>
> Peter