and for purposes of continuity TableParse should be replaced with My_Module
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
hey guys, thanks a lot for your insight (or lack thereof) which convinced me
to try further investigation on what I might have left out. One significant
point of correction: for purposes of simplification, I neglected to include
for your review the fact that when I attempted to add my path to Pyth
On Sun, Nov 25, 2007 at 11:14:47PM -0800, Jeff Younker wrote:
>
> > so when I run my script from the command line, the folder does seem
> > to be added to Python's importable modules search path. When I
> > attempt to import my_module I get the error:
> >
> > ImportError: No module named my_m
> so when I run my script from the command line, the folder does seem
> to be added to Python's importable modules search path. When I
> attempt to import my_module I get the error:
>
> ImportError: No module named my_module
Do your module directories have an __init__.py file
in them?
- Jef
On 11/25/07, Kent Johnson <[EMAIL PROTECTED]> wrote:
>
>
>
> Should be sys.path.append(...)
>
> Kent
yes, I'm sorry, in my posting I did have a typographical error, but my code
has the following seemingly correct lines:
sys.path.append(PATH_TO_MODULE)
print "Path added:
[EMAIL PROTECTED] wrote:
> Dear fellow Python enthusiasts,
>
> I trust your Thanksgiving holiday has been a relaxing one. A quick
> question for you: I have a script that attempts to import my_module from
> a folder that is not in Python's importable modules search path. In my
> script, that
Dear fellow Python enthusiasts,
I trust your Thanksgiving holiday has been a relaxing one. A quick question
for you: I have a script that attempts to import my_module from a folder
that is not in Python's importable modules search path. In my script, that
I run from the command line, I have the
