On Oct 26, 6:53 am, David Abrahams <[EMAIL PROTECTED]> wrote:
> > David Abrahams wrote:
> >> I'm seeing highly surprising (and different!) behaviors of
> >> PyImport_ImportModule on Linux and Windows when used in a program with
> >> python embedding.
>
> >> On Linux, ...
>
>
>
> Unfortunately, not
on Sat Mar 24 2007, "Ziga Seilnacht" wrote:
> David Abrahams wrote:
>> I'm seeing highly surprising (and different!) behaviors of
>> PyImport_ImportModule on Linux and Windows when used in a program with
>> python embedding.
>>
>> On Linux, ...
Unfortunately, nothing you have written below or
David Abrahams wrote:
> I'm seeing highly surprising (and different!) behaviors of
> PyImport_ImportModule on Linux and Windows when used in a program with
> python embedding.
>
> On Linux, when attempting to import a module xxx that's in the current
> directory, I get
>
> ImportError: No module
Aahz <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> David Abrahams <[EMAIL PROTECTED]> wrote:
> >
> >I was under the impression that both the current directory *and* the
> >python library directory were already, automatically, in sys.path, so
> >I'm really surprised to see this.
In article <[EMAIL PROTECTED]>,
David Abrahams <[EMAIL PROTECTED]> wrote:
>
>I was under the impression that both the current directory *and* the
>python library directory were already, automatically, in sys.path, so
>I'm really surprised to see this. Am I doing something wrong, or is
>this simpl
I'm seeing highly surprising (and different!) behaviors of
PyImport_ImportModule on Linux and Windows when used in a program with
python embedding.
On Linux, when attempting to import a module xxx that's in the current
directory, I get
ImportError: No module named xxx
I can work around the pr
