The first release of Visual 5 will be for Python 2.5, though of course
we will try to track upgrades in Python.
I tried building Visual 5 for Python 2.6, which is an attractive target
because it provides support for identifying possible incompatibilities
with Py3K. Unfortunately there are various problems. Here is what I
posted on the VPython wiki in response to a question about 2.6:
The Boost libraries, which enhance C++, have to be built for a specific
version of Python, and since there aren't yet available these binaries
for 2.6, I built them from source. Similarly for numpy. Turns out that
something has changed in these components, because there's now a type
mismatch between numpy integers and Python integers (this is a
simplified description). Moreover, for the new Visual about to be
released, there's a problem with a native-mode version for the Mac
because the Mac Python 2.6 has an IDLE that won't run!
Summary: There are various problems in the Python 2.6 world. But we'll
be tracking them and looking for solutions. We would prefer to release
the new Visual for Python 2.6, because Python 2.6 builds a bridge
between Python 2.5 and the coming Python 3.0, a version of Python that
will actually break some existing programs. Python 2.6 offers tools to
check on possible incompatibilities.
Bruce Sherwood
Roberto Aguirre Maturana wrote:
> Is Visual 5 going to be compatible with Py3K?
>
|
