Embedding vs Configuring Python build

Discussion in 'Python' started by hvendelbo.dev@googlemail.com, Mar 5, 2008.

  1. Guest

    I am using Python in an application that cannot depend on an existing
    Python installation or require Python to
    be installed. The application itself should not have an install
    procedure, but rather should be runnable from any
    location in the file system.

    Ideally I would prefer not to embed at all, but would rather prefer to
    configure. I found a couple of discussions on the
    default sys.path in the archive and am currently reading through the
    Py_GetPath. The path logic seems pretty specific to the platform,
    whereas I would want it to be relative regardless of platform. I
    figure that if I can just get to
    my own site.py/sitecustomize.py then I'm in business.

    This is what I wan't to achieve:

    * The python executable location should be used to determine dynamic
    libraries
    * The python exe location should be used to determine standard library
    scripts
    * site.py should be executed rather than the shell if no parameters
    are specified

    Is it possible to change the build configuration of Python to support
    this.
    , Mar 5, 2008
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Nicolas Lehuen
    Replies:
    3
    Views:
    699
    Nicolas Lehuen
    Jan 28, 2004
  2. Phil Frost
    Replies:
    3
    Views:
    509
    Donn Cave
    May 26, 2004
  3. Phil Frost
    Replies:
    1
    Views:
    304
    Ryan Paul
    May 27, 2004
  4. Toon Knapen
    Replies:
    2
    Views:
    350
    Toon Knapen
    May 17, 2006
  5. Wong Wah Meng-R32813
    Replies:
    0
    Views:
    689
    Wong Wah Meng-R32813
    Sep 18, 2011
Loading...

Share This Page