python 3.0, pywin32 and scipy
Diez B. Roggisch
deets at nospam.web.de
Thu Aug 2 21:16:04 CEST 2007
> I am trying to promote python in my job, my collegue only see matlab
> and microsoft scripting language.
> I understood that there willl be no backward compatibility between
> python 2.x and 3.0, does it means that:
> - my script using pywin32 for the COM layer and scipy for the maths
> won't work under 3.0
If the win32-extensions are made available (which I think is to be
expected - they are too important to not being ported), I fail to see
what COM-dependend code you expect to fail - after all, it's the
COM-based APIs that are to be questioned there.
> - will we have the equivalent of pywin32 and scipy in python ?
Again, I think so - but of course I don't know for sure. But they both
are to important.
> I will be incharge of designing a python module which will be a
> 'matrix calculator' in our current software. Will it be compatible
> with python 3.0 ? I guess no.
Even if not - why do you care? Is your C# 1 code being ported to C# 2
immediately? Are you preparing for C# three?
> What can I answer to my collegue who will say 'Python is changing and
> the stuff you are doing now is useless'?
> how can I argue against matlab and c# ?
You mean C#, the language that has seen 3 major revisions in the last 6
years of existence, with C# 3 being announced already? And the .NET SDK,
that happily strode along with that? Compared to python, that has been
started in 1991 and now approaches it's third incarnation, I'd say
python has a record of steadiness that surpasses that of MS-based tools
by any means.
More information about the Python-list