Where python looks for path

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Philippe Martin

    #1

    Where python looks for path

    Hi,

    I am currently packaging python and a few libraries: PyWin32, PySerial, PIL,
    wxPython, HTML generator, numarray for U3 distribution.

    Basically that means that the complete system initially in $path1\host will
    be moved dynamically to $path2\at execution.


    To take PIL as an example, I notice when I launch Idle in a "relative"
    manner: I am in $path1\host that $path1\host\Lib \site-packages\PIL is in
    the sys.path before I do anything.

    I notice that there is a PIL.pch file in site-packages:

    Q1) is that read by python ?


    On the other hand, even after appending all I can think of in sys.path, I
    still get an error (cannot find module) trying to load win32com.client : it
    fails in the win32api import in win32com.client .

    pywin32.pch is there.

    I think all the .dlls are there also, so I'm a bit confused.

    Q2) what should I be looking for ?


    Also, I seemed to notice in the past that modules (my own) not listed in any
    __init__.py where found under Linux but not Windows for which I had to
    upgrade my __init__.py.


    Q3: is that true ?


    Regards,

    Philippe




  • Philippe Martin

    #2
    Re: Where python looks for path

    PS: I forgot to say that on the win32api import I get a "DLL load failed"

    Philippe


    Philippe Martin wrote:
    [color=blue]
    > Hi,
    >
    > I am currently packaging python and a few libraries: PyWin32, PySerial,
    > PIL, wxPython, HTML generator, numarray for U3 distribution.
    >
    > Basically that means that the complete system initially in $path1\host
    > will be moved dynamically to $path2\at execution.
    >
    >
    > To take PIL as an example, I notice when I launch Idle in a "relative"
    > manner: I am in $path1\host that $path1\host\Lib \site-packages\PIL is in
    > the sys.path before I do anything.
    >
    > I notice that there is a PIL.pch file in site-packages:
    >
    > Q1) is that read by python ?
    >
    >
    > On the other hand, even after appending all I can think of in sys.path, I
    > still get an error (cannot find module) trying to load win32com.client : it
    > fails in the win32api import in win32com.client .
    >
    > pywin32.pch is there.
    >
    > I think all the .dlls are there also, so I'm a bit confused.
    >
    > Q2) what should I be looking for ?
    >
    >
    > Also, I seemed to notice in the past that modules (my own) not listed in
    > any __init__.py where found under Linux but not Windows for which I had to
    > upgrade my __init__.py.
    >
    >
    > Q3: is that true ?
    >
    >
    > Regards,
    >
    > Philippe[/color]

    Comment

    • Philippe Martin

      #3
      Re: Where python looks for path

      Hi,

      I had to move the dlls from pywin32_system3 2 to where python.exe is.

      PS: if someone has a great desire to have another library included in the
      package, let me know.

      Regards,

      Philippe



      Philippe Martin wrote:
      [color=blue]
      > Hi,
      >
      > I am currently packaging python and a few libraries: PyWin32, PySerial,
      > PIL, wxPython, HTML generator, numarray for U3 distribution.
      >
      > Basically that means that the complete system initially in $path1\host
      > will be moved dynamically to $path2\at execution.
      >
      >
      > To take PIL as an example, I notice when I launch Idle in a "relative"
      > manner: I am in $path1\host that $path1\host\Lib \site-packages\PIL is in
      > the sys.path before I do anything.
      >
      > I notice that there is a PIL.pch file in site-packages:
      >
      > Q1) is that read by python ?
      >
      >
      > On the other hand, even after appending all I can think of in sys.path, I
      > still get an error (cannot find module) trying to load win32com.client : it
      > fails in the win32api import in win32com.client .
      >
      > pywin32.pch is there.
      >
      > I think all the .dlls are there also, so I'm a bit confused.
      >
      > Q2) what should I be looking for ?
      >
      >
      > Also, I seemed to notice in the past that modules (my own) not listed in
      > any __init__.py where found under Linux but not Windows for which I had to
      > upgrade my __init__.py.
      >
      >
      > Q3: is that true ?
      >
      >
      > Regards,
      >
      > Philippe[/color]

      Comment

      Working...