wxPython is a GUI toolkit for the Python programming language. It
allows Python programmers to create programs with a robust, highly
functional graphical user interface, simply and easily. It is
implemented as a Python extension module that wraps the GUI components
of the popular wxWidgets cross platform library, which is written in
C++.
wxPython is a cross-platform toolkit. This means that the same program
will usually run on multiple platforms without modifications.
Currently supported platforms are 32-bit and 64-bit Microsoft Windows,
most Linux or other Unix-like systems using GTK2, and Mac OS X 10.4+.
In most cases the native widgets are used on each platform to provide
a 100% native look and feel for the application.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
On Wed, Oct 8, 2008 at 23:01, Robin Dunn <robin@alldunn.com> wrote:
Hi All,
A set of wxPython binaries for Python 2.6 on Win32, Win64 and Mac OS X are
now available at Redirecting...
I see that wxPython for 2.6 on Win32 is still shipping msvcr71.dll and
msvcp71.dll. Shouldn't it ship msvcr90.dll and msvcp90.dll instead?
Are you sure they were not left over from a previous install? The latest installer for py26 doesn't install any CRT DLLs at all because since Python 2.6 is using the standard CRT assembly then it is guaranteed to be there already, (as long as Python is installed anyway, but wxPython wouldn't be very useful without it.)
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I've just checked, and yes, it installs C:\Python26\msvcr71.dll and
C:\Python26\Lib\site-packages\wx-2.8-msw-unicode\wx\msvcp71.dll.
I agree that there is no need to install msvcr71.dll, but I think
msvcp71.dll is not installed by Python itself.
Conrado
···
On Thu, Oct 9, 2008 at 01:48, Robin Dunn <robin@alldunn.com> wrote:
Are you sure they were not left over from a previous install? The latest
installer for py26 doesn't install any CRT DLLs at all because since Python
2.6 is using the standard CRT assembly then it is guaranteed to be there
already, (as long as Python is installed anyway, but wxPython wouldn't be
very useful without it.)
On Wed, Oct 8, 2008 at 23:01, Robin Dunn <robin@alldunn.com> wrote:
Hi All,
A set of wxPython binaries for Python 2.6 on Win32, Win64 and Mac OS X are
now available at Redirecting...
I see that wxPython for 2.6 on Win32 is still shipping msvcr71.dll and
msvcp71.dll. Shouldn't it ship msvcr90.dll and msvcp90.dll instead?
Only if the underlying wxWidgets DLLs were built with Visual Studio
2008. I don't know that they were. The DLLs in 2.8.6.0 were still
built with VS 2003, which needs the 71 runtimes. Since this release was
not caused by a new release of wxWidgets, I'm guessing the DLLs didn't
change.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
Are you sure they were not left over from a previous install? The latest
installer for py26 doesn't install any CRT DLLs at all because since Python
2.6 is using the standard CRT assembly then it is guaranteed to be there
already, (as long as Python is installed anyway, but wxPython wouldn't be
very useful without it.)
I've just checked, and yes, it installs C:\Python26\msvcr71.dll and
C:\Python26\Lib\site-packages\wx-2.8-msw-unicode\wx\msvcp71.dll.
Ah, I see the problem now. The change I made to exclude the MS DLLs in the py26 installers was in a branch of code that only executes for AMD64. I've moved it up to be checked before it gets that far, and it will be fixed in the next release.
I agree that there is no need to install msvcr71.dll, but I think
msvcp71.dll is not installed by Python itself.
It shouldn't need either anymore because Python, wxWidgets and wxPython will all have been built with VS 2008, and so none of them will be linking with any of the MS*71*.DLL's
···
On Thu, Oct 9, 2008 at 01:48, Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
A set of wxPython binaries for Python 2.6 on Win32, Win64 and Mac OS X are
now available at Redirecting...
I see that wxPython for 2.6 on Win32 is still shipping msvcr71.dll and
msvcp71.dll. Shouldn't it ship msvcr90.dll and msvcp90.dll instead?
Only if the underlying wxWidgets DLLs were built with Visual Studio
2008. I don't know that they were. The DLLs in 2.8.6.0 were still
built with VS 2003, which needs the 71 runtimes. Since this release was
not caused by a new release of wxWidgets, I'm guessing the DLLs didn't
change.
They did. My build system switches which compiler is used for both the wxWidgets and the wxPython builds based on which version of Python it is building for. Here is how that breaks down:
A set of wxPython binaries for Python 2.6 on Win32, Win64 and Mac OS X are
now available at Redirecting...
I see that wxPython for 2.6 on Win32 is still shipping msvcr71.dll and
msvcp71.dll. Shouldn't it ship msvcr90.dll and msvcp90.dll instead?
Only if the underlying wxWidgets DLLs were built with Visual Studio
2008. I don't know that they were. The DLLs in 2.8.6.0 were still
built with VS 2003, which needs the 71 runtimes. Since this release was
not caused by a new release of wxWidgets, I'm guessing the DLLs didn't
change.
They did. My build system switches which compiler is used for both the wxWidgets and the wxPython builds based on which version of Python it is building for. Here is how that breaks down:
I should add another to the list. 2.5 for Win64 uses the compiler and libs included with the 2003 Platform SDK which is something between 7.1 and 8.0, which can result in a slightly sticky mess.
···
On Wed, Oct 8, 2008 at 23:01, Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!