Ok, I'll carify: move csnd.dll out of your
PYTHONPATH, which means wherever python looks for
modules to load. If it finds csnd.dll when you do
import csnd, then it will fail. But put it somewhere
else in your PATH, exec path, so that windows can
find it (when python loads _csnd.pyd which is linked
to csnd.dll).

 I think this does actually happen
in 2.5, because it only looks for .pyd and will
not try to load a .dll, as 2.4 does.

Victor
>
> Thanks for the explanations for the different files, I
> feel wiser now ;-) Only one thing remains unclear as of
> now:
>
> 2007/11/2, Victor Lazzarini :
> > csnd.dll is all the interfaces code that the
> > python module uses. I suppose it can go where
> > you keep your csound binary or anywhere else
> > in your path that is not in the way.
> >
> but you said earlier (2007/10/30):
> """
> > The problem is that there is a file called csnd.dll in
> > the directory, which is not a python module, import csnd
> > tries to import it, when it should be importing csnd.py
> instead. >
> > Solution: move csnd.dll out of there.
> """
> And out of "there" refered to the csound/bin folder (where
> I keep the csound binary.
> Your previous advise (of 10/30) worked well, I'm just
> confused that you now seem to say it's allright to keep
> csnd.dll in the /bin folder (as this caused problems
> loading csnd in python).
>
> best
> Oeyvind

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net