On Apr 29, Amit Belani <[EMAIL PROTECTED]> wrote:

> IMDbPY 3.4 installs fine on Python 2.5 x86 on Windows. It's just 3.5 that
> doesn't. How and why is this difference?

Fortunately, I've kept the working files created building both 3.5
and 3.4.  From what I can tell, I think that the cutils C module
wasn't compiled for 3.4, probably because I've called the wrong
Python interpreter (I've many versions installed), building
the package.

Repeat with me: WOOOPS!  WOOOPS!  WOOOPS! ;-)

That made the 3.4 a "pure python" release, while 3.5 - containing
a C module - is specific for a given Python release (2.4, in this
case).

I'll try to learn what I've to do to compile C modules with cygwin
for Python 2.5, but don't hold your breath in the wait... ;-)

As usual, any help is appreciated.


-- 
Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47]
http://erlug.linux.it/~da/

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Imdbpy-devel mailing list
Imdbpy-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/imdbpy-devel

Reply via email to