The easiest way to debug such import problems is by telling
Python to be verbose:
python -vv -c "import some_module"
The generated output will then list all the locations where
Python looks for the module and is often handy to track
down reasons for Python not being able to load a module.
--
Ma
On Nov 6, 3:21 am, BL <[EMAIL PROTECTED]> wrote:
> On Nov 4, 7:11 pm, John Machin <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Nov 5, 9:18 am, BL <[EMAIL PROTECTED]> wrote:
>
> > > I am very new to python. I am installing it as part of a bazzar
> > > version control installation.
> > > I have installed
On Nov 4, 7:11 pm, John Machin <[EMAIL PROTECTED]> wrote:
> On Nov 5, 9:18 am, BL <[EMAIL PROTECTED]> wrote:
>
> > I am very new to python. I am installing it as part of a bazzar
> > version control installation.
> > I have installed the Crypto, paramiko and cElementTree modules. I am
> > running
On Nov 5, 9:18 am, BL <[EMAIL PROTECTED]> wrote:
> I am very new to python. I am installing it as part of a bazzar
> version control installation.
> I have installed the Crypto, paramiko and cElementTree modules. I am
> running Solaris10x86.
> When testing the modules I get the following results.
I am very new to python. I am installing it as part of a bazzar
version control installation.
I have installed the Crypto, paramiko and cElementTree modules. I am
running Solaris10x86.
When testing the modules I get the following results.
python -c "import Crypto"
Traceback (most recent call la
