Nick

Show:

What's happening?

  • Comment: python crash on "from pylab import *"

    For those who are using MingW and want to embed Python with Matplotlib, I added some directions to the Scons wiki: http://www.scons.org/wiki/EmbedManifestIntoTarget.

    2009-10-31 19:12:37 UTC in matplotlib

  • Nsound

    weegreenblobbie committed revision 411 to the Nsound SVN repository, changing 2 files.

    2009-10-31 17:46:43 UTC in Nsound

  • Comment: python crash on "from pylab import *"

    Okay, so embedding Python & Matplotlib will take some extra work. The only thing to do, if possible, would be to error out more gracefully. To the non-experts, the failure appears to be a problem with matplotlib, not necessarily a windows runtime link problem.

    2009-10-29 07:04:23 UTC in matplotlib

  • Comment: python crash on "from pylab import *"

    What has changed from 0.99.0? All that work with msvc*.dll and manifests is troublesome. Does this mean I must burden my end users with installing vc90 runtime? In the end, would I have to detect which C Runtime is installed and somehow inject the correct manifest file into the executables? I have a Unix development background, I am not familiar with manifests.

    2009-10-29 02:34:36 UTC in matplotlib

  • Comment: python crash on "from pylab import *"

    I guess sourceforge won't allow additional attachments. Here's the full error text: Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\cygwin\home\nhilton\nsound-0.7.3\.sconf_temp\a.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.

    2009-10-28 22:06:18 UTC in matplotlib

  • Comment: python crash on "from pylab import *"

    Copying the DLLs to the local directory satisfies the dependency check, but now I get a C++ runtime error: R6034. I will upload a screenshot. This may be my setup here on my work machine. I will try again tonight on my dev box at home.

    2009-10-28 21:55:24 UTC in matplotlib

  • Comment: python crash on "from pylab import *"

    May be it's my C API program that is causing the issue since it's compiled with MingGW. Trying it out....

    2009-10-28 20:12:09 UTC in matplotlib

  • Comment: python crash on "from pylab import *"

    I am using Python2.6.4 and the problem still exists. To clarify, from a DOS box using an interactive session, I can import pylab and create plots as expected. Only my C API program has a problem. Searching my whole hard disk I find MSVCR90.dll only lives here: C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_d08d0375...

    2009-10-28 20:06:18 UTC in matplotlib

  • Comment: python crash on "from pylab import *"

    Found this information which may be related: The Python 2.6 binary from python.org has been built with a version of MS Visual Studio that causes problems when extensions are compiled with Mingw32. The reason is an errenous file libmsvcr90.a coming with Mingw32. To fix it, you can recreate the file from the DLL msvcr90.dll that comes with Python 2.6 with pexports and dlltool (the latter is part...

    2009-10-28 05:44:00 UTC in matplotlib

  • Nsound

    weegreenblobbie committed revision 410 to the Nsound SVN repository, changing 4 files.

    2009-10-28 05:05:57 UTC in Nsound

About Me

  • 2004-07-09 (5 years ago)
  • 1080014
  • weegreenblobbie (My Site)
  • Nick

Send me a message