P
Philippe C. Martin
Hi,
*** QUICK BACKGROUND ***
-)I have been working with pycsc.c in which I made a few modifications.
-)When I had it working un linux - I attempted to port it to Windows
-) I read a lot, downloaded mingwin and had pexports crash when I attempted to
get the .def out of winscard.dll
-) I then attempted to create the .def by hand with no luck
-) I read some more and decided I would have ess problems with Visual
Studio .NET (sigh) - so I broked down and invested
-) the setup.py failed on python 2.3 because V6 was required
-) I read there was a patch but also that the laster 2.4B was compiled with VS
7.1 (which I assumed meant .NET)
-) Downloaded it, everyting compiled and linked fine - had to copy the files
by hand to the right locations and everyting worked great.
***************************************
Now for the question:
Since pycsc does not use any brand new Python functionality, are the binaries
be compatible with earlier versions of Python ? down to which ?
Regards,
Philippe
*** QUICK BACKGROUND ***
-)I have been working with pycsc.c in which I made a few modifications.
-)When I had it working un linux - I attempted to port it to Windows
-) I read a lot, downloaded mingwin and had pexports crash when I attempted to
get the .def out of winscard.dll
-) I then attempted to create the .def by hand with no luck
-) I read some more and decided I would have ess problems with Visual
Studio .NET (sigh) - so I broked down and invested
-) the setup.py failed on python 2.3 because V6 was required
-) I read there was a patch but also that the laster 2.4B was compiled with VS
7.1 (which I assumed meant .NET)
-) Downloaded it, everyting compiled and linked fine - had to copy the files
by hand to the right locations and everyting worked great.
***************************************
Now for the question:
Since pycsc does not use any brand new Python functionality, are the binaries
be compatible with earlier versions of Python ? down to which ?
Regards,
Philippe