MacPython 2.2 on Mac OS X 10.3.8 - configurePython error

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Paul Miller

    #1

    MacPython 2.2 on Mac OS X 10.3.8 - configurePython error

    I have a user who is is having trouble getting MacPython on his OS X
    10.3.8 system.

    When he runs ConfigurePython Carbon, he gets this error:

    [terminated]
    'import site' failed; use -v for traceback
    traceback )most recent call last):
    File "Moes:SWdev:Jac k:Python2.2:Mac :script:configu rePython.py", line 11
    , in ?
    Import error: No module named os


    I have had no trouble on my system (same version).

    What can cause this?

    -Paul

  • Robert Kern

    #2
    Re: MacPython 2.2 on Mac OS X 10.3.8 - configurePython error

    Paul Miller wrote:[color=blue]
    > I have a user who is is having trouble getting MacPython on his OS X
    > 10.3.8 system.
    >
    > When he runs ConfigurePython Carbon, he gets this error:
    >
    > [terminated]
    > 'import site' failed; use -v for traceback
    > traceback )most recent call last):
    > File "Moes:SWdev:Jac k:Python2.2:Mac :script:configu rePython.py", line 11
    > , in ?
    > Import error: No module named os
    >
    >
    > I have had no trouble on my system (same version).
    >
    > What can cause this?[/color]

    os.py got deleted from its home, probably. I doubt anyone is going to
    help fix the problem though. MacPython 2.2 has been long abandoned. The
    official OS X binary for Python 2.4.1 can be found here:



    --
    Robert Kern
    rkern@ucsd.edu

    "In the fields of hell where the grass grows high
    Are the graves of dreams allowed to die."
    -- Richard Harter

    Comment

    • Paul Miller

      #3
      Re: MacPython 2.2 on Mac OS X 10.3.8 - configurePython error

      Robert Kern wrote:[color=blue]
      > Paul Miller wrote:
      >[color=green]
      >>I have a user who is is having trouble getting MacPython on his OS X
      >>10.3.8 system.
      >>
      >>When he runs ConfigurePython Carbon, he gets this error:
      >>
      >>[terminated]
      >>'import site' failed; use -v for traceback
      >>traceback )most recent call last):
      >>File "Moes:SWdev:Jac k:Python2.2:Mac :script:configu rePython.py", line 11
      >>, in ?
      >>Import error: No module named os
      >>
      >>
      >>I have had no trouble on my system (same version).
      >>
      >>What can cause this?[/color]
      >
      >
      > os.py got deleted from its home, probably. I doubt anyone is going to
      > help fix the problem though. MacPython 2.2 has been long abandoned. The
      > official OS X binary for Python 2.4.1 can be found here:
      >
      > http://www.python.org/ftp/python/2.4...SX-2.4.1-1.dmg[/color]

      I realize that, but I have an application that is linked with MacPython
      2.2. I can't just drop 2.4 in.

      He claims the only thing that has changed is his preferences were wiped
      out. There must be some solution for what is probably a not too uncommon
      problem.
      [color=blue]
      >[/color]

      Comment

      • Robert Kern

        #4
        Re: MacPython 2.2 on Mac OS X 10.3.8 - configurePython error

        Paul Miller wrote:[color=blue]
        > Robert Kern wrote:[/color]
        [color=blue][color=green]
        >> MacPython 2.2 has been long abandoned. The
        >>official OS X binary for Python 2.4.1 can be found here:
        >>
        >>http://www.python.org/ftp/python/2.4...SX-2.4.1-1.dmg[/color]
        >
        > I realize that, but I have an application that is linked with MacPython
        > 2.2. I can't just drop 2.4 in.[/color]

        Is this an application that you've written? If so, then I realize that
        you can't just drop 2.4 in painlessly, but you really should consider
        upgrading your software to use a newer Python. No one is going to
        support MacPython 2.2.
        [color=blue]
        > He claims the only thing that has changed is his preferences were wiped
        > out. There must be some solution for what is probably a not too uncommon
        > problem.[/color]

        It *is* uncommon. Judging from the traffic on the Pythonmac-SIG,
        virtually no one is using MacPython 2.2 anymore. You can ask for help on
        there, but I don't think you'll fare any better.



        --
        Robert Kern
        rkern@ucsd.edu

        "In the fields of hell where the grass grows high
        Are the graves of dreams allowed to die."
        -- Richard Harter

        Comment

        • Paul Miller

          #5
          Re: MacPython 2.2 on Mac OS X 10.3.8 - configurePython error

          Robert Kern wrote:[color=blue]
          > Paul Miller wrote:
          >[color=green]
          >>Robert Kern wrote:[/color]
          >
          >[color=green][color=darkred]
          >>>MacPython 2.2 has been long abandoned. The
          >>>official OS X binary for Python 2.4.1 can be found here:
          >>>
          >>>http://www.python.org/ftp/python/2.4...SX-2.4.1-1.dmg[/color]
          >>
          >>I realize that, but I have an application that is linked with MacPython
          >>2.2. I can't just drop 2.4 in.[/color]
          >
          >
          > Is this an application that you've written? If so, then I realize that
          > you can't just drop 2.4 in painlessly, but you really should consider
          > upgrading your software to use a newer Python. No one is going to
          > support MacPython 2.2.[/color]

          Yes, this is an app I have written. I could take the time to rebuild it
          with the latest Python, yes.

          However, the simpler solution seemed to be to try to figure out why it
          won't reconfigure itself. I have OS X 10.3.8 and a clean install works
          perfectly fine. Surely someone somewhere has used MacPython 2.2 on OS X
          10.3.8 and heard of a similar issue, with ConfigurePython Carbon not
          working after preferences were destroyed.

          This is why I asked here.
          [color=blue][color=green]
          >>He claims the only thing that has changed is his preferences were wiped
          >>out. There must be some solution for what is probably a not too uncommon
          >>problem.[/color]
          >
          > It *is* uncommon. Judging from the traffic on the Pythonmac-SIG,
          > virtually no one is using MacPython 2.2 anymore. You can ask for help on
          > there, but I don't think you'll fare any better.[/color]

          Perhaps I am the only developer with a legacy application he's trying to
          support. But I doubt it.

          Comment

          Working...