Python 2.3.2 spawn problem

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jim Tanner

    Python 2.3.2 spawn problem

    I am trying to start the 2.3.3 IDL and getting an error. I think I might
    have a dll conflict, but the 2.2.3 IDL works fine. The 2.3.3 IDL used to
    work just fine.

    The following are the Traceback error messages:

    bash-2.05b$ python.exe Lib/idlelib/idle.pyw
    C:\cygwin\bin\p ython2.3.exe: *** unable to remap
    C:\cygwin\bin\c ygssl-0.9.7.dll
    to same address as parent(0x720000 ) != 0x730000
    407 [main] python 2496 sync_with_child : child 3112(0x180) died before
    initia
    lization with status code 0x1
    903 [main] python 2496 sync_with_child : *** child state child loading
    dlls
    Traceback (most recent call last):
    File "Lib/idlelib/idle.pyw", line 4, in ?
    main()
    File "/cygdrive/c/Python23/Lib/idlelib/PyShell.py", line 1282, in main
    flist.pyshell = PyShell(flist)
    File "/cygdrive/c/Python23/Lib/idlelib/PyShell.py", line 764, in __init__
    self.interp.sta rt_subprocess()
    File "/cygdrive/c/Python23/Lib/idlelib/PyShell.py", line 355, in
    start_subproc
    ess
    self.spawn_subp rocess()
    File "/cygdrive/c/Python23/Lib/idlelib/PyShell.py", line 321, in
    spawn_subproc
    ess
    self.rpcpid = os.spawnv(os.P_ NOWAIT, sys.executable, args)
    File "/usr/lib/python2.3/os.py", line 521, in spawnv
    return _spawnvef(mode, file, args, None, execv)
    File "/usr/lib/python2.3/os.py", line 489, in _spawnvef
    pid = fork()
    OSError: [Errno 11] Resource temporarily unavailable

    Thanks for your assistance,
    Jim Tanner


  • Jim Tanner

    #2
    Re: Python 2.3.2 spawn problem


    "Jim Tanner" <james.g.tanner @boeing.com> wrote in message
    news:HuDnKL.HAz @news.boeing.co m...[color=blue]
    > I am trying to start the 2.3.3 IDL and getting an error. I think I might
    > have a dll conflict, but the 2.2.3 IDL works fine. The 2.3.3 IDL used to
    > work just fine.
    >[/color]
    I finally tracked this error to a conflict with the TCL/TK library version
    installed by Ruby having previously installed Python 2.3.2. Python 2.3.2 is
    dependent on a TCL/TK version that is one release older than that required
    by Ruby.

    Uninstalling Ruby and Python 2.3.2 and reinstalling Python 2.3.2 seems to
    have done the trick.

    I will have to run some controlled experiments to see if Ruby can run with
    the same TCL/TK version as Python 2.3.2.

    Thanks again for those of you who responded with suggestions.

    Jim Tanner


    Comment

    Working...