[EMAIL PROTECTED] wrote:
> AhhI see. I played around with the sys.path function...and it
> looks like python automatically looks in the same directory as my
> script first. Then is searches to all the other pre-defined paths. So
> it works for me to just keep my main script in the same direc
AhhI see. I played around with the sys.path function...and it
looks like python automatically looks in the same directory as my
script first. Then is searches to all the other pre-defined paths. So
it works for me to just keep my main script in the same directory as
the two modules I'm using
[EMAIL PROTECTED] wrote:
> I know this is wrong syntax, but I think it demonstrates what I'm
> trying to do:
>
> import myModule path = /modules/myModule
> import myModule2 path = /modules/myModule2
>
> Something like that. Is it possible?
I would put your additional modules into a 'modules' di
If it is Windows use py2exe and Inno Installer to create an
installation program that does this for you. If it is another
OS, you need to put your modules into a subdirectory of
site-packages and then Python will be able to see your modules.
If you have a lot of modules you might consider turning
Am Mon, 20 Jun 2005 06:31:38 -0700 schrieb passion_to_be_free:
> Okay, so in my li'l python script I'm importing a few 3rd party modules
> that I have installed on my comp. I need to distribute this script to
> several other people, but I won't have access to install the modules on
> their comp's
Okay, so in my li'l python script I'm importing a few 3rd party modules
that I have installed on my comp. I need to distribute this script to
several other people, but I won't have access to install the modules on
their comp's. I'm thinking I'll include these modules with my script
and deliver th
