Closed GoogleCodeExporter closed 9 years ago
For compatibility with Python 2.6 and Python 3.0, PyScripter version 1.9.9.3
requires
the latest C++ Redistributable Package.
http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D
-3802B2AF5FC2&displaylang=en
This is automatically installed by Python 2.6 and Python 3.0. If you do not
have any
of these versions installed, then you need to download and install it manually.
Does this help? Are you working on Vista?
Original comment by pyscripter
on 31 Dec 2008 at 12:50
Many Thanks for responding.
I wanted to use the new PyScripter with Python 2.5.4 (not Python 2.6 or 3.0).
Do I
still require to manually install the latest C++ Redistributable Package?
I am also running MS Visual Studio 2005 on my computer and do not want to
disturb
this environment overwriting the existing redistributables.
I am running on Windows XP and not Vista.
Hope the above info helps resolve the reported issue.
Wishing you a Very Happy and Prosperous New Year
Original comment by Vishal.Mukkamala@gmail.com
on 31 Dec 2008 at 3:05
I am afraid you need to install it.
This requires some explanation (note: this is quite technical).
Python 2.6 and Python 3.0 are built using the Visual Studio 2008 and
link against version 9.0.21022.8 of the Microsoft C++ Redistributable
Package, This package is installed by the Python installers, so if
you install either Python 2.6 or Python 3.0 you do not need to do
anything. The Python installer installs this package on systems
supporting Side-by-Side installation (Vista and XP) in c:\Windows
\winsxs and not in C:\Windows\system32. I had to add a dependency to
this package in the PyScripter manifest resource file for PyScripter
to work properly with Python 2.6. Without this dependency, it would
appear to work well but import of extension modules would fail.
Given that this package is installed in a side-by-side mode it should not upset
your
Visual Studio environment.
Original comment by pyscripter
on 31 Dec 2008 at 5:04
I am using XP PRO and have
http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D
-3802B2AF5FC2&displaylang=en
installed. When moving to 1.9.9.3, I experience the problem Vishal reported.
I retreated to 1.9.9.2 and all is well.
Colin W.
Original comment by cjwillia...@gmail.com
on 10 Jan 2009 at 10:33
I think the resolution is to include the MS VC++ runtimes in the same directory
as
the pyscripter exe. I also ran into the same problems with a install of Python
2.5
on Windows Server 2003. If you run depends.exe on the pyscripter.exe it will
show
it's dependencies, and you can simply include those in the same directory as
the exe
and no one will have these issues.
Original comment by tony.cad...@gmail.com
on 13 Jan 2009 at 10:33
As Recommended by PyScripter, the issue got resolved after installing the
redistributables from Microsoft.
But I feel that since PyScripter depends on these libraries, these should have
been
included in the Setup package itself. The user typicaly should not be required
to do
any extra step after the installation to get the application launched
successfully.
Or atleast the setup should check for the pre-requisites and advise the user to
install the necessary libraries before proceding with the installation.
Original comment by Vishal.Mukkamala@gmail.com
on 15 Jan 2009 at 7:07
Tony,
Unlike Vishal, I was not able to fly: XP PRO, Python 2.5.4.
It would help if you could identify the specific files or directories from VS
that
should be copied into the PyScripter executable directory.
Is it all the files from the bin directory?
Thanks,
Colin W.
Original comment by cjwillia...@gmail.com
on 16 Jan 2009 at 12:22
I guess
msvcm90.dll
msvcp90.dll
msvcr90.dll
In a side by side installation these are installed under
C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86
ed6ac711f91
on my Windows Vista machine. The directory should be different under XP but
still
under the C:\Windows\winsxs directory.
Original comment by pyscripter
on 20 Jan 2009 at 2:07
I am closing this bug. The issue Colin has has been filed separately.
Regarding the
dependency I am still debating whether I would produce a version of PyScripter
without it for working with versions of Python 2.5 or earlier.
Original comment by pyscripter
on 13 Feb 2009 at 10:45
Original issue reported on code.google.com by
Vishal.Mukkamala@gmail.com
on 31 Dec 2008 at 12:26Attachments: