OK, I'll jump in here. (After all, I've been the lead complainer about the 
Windows Python popup.)

Yes, the problem popup still lives - at least on Windows XP with the 5.10 
float installer.

I've just done a thorough test, uninstalling all versions of Csound and 
clearing out all Csound-related environment variables. (I also searched for 
any other files with "python" in their names. Nothing. I can vouch that 
Python is *not* installed.)

I did a clean install of the float installer, specifying to continue without 
Python2.5.

Running a realtime .csd from the commandline:

1) I get the "can't find Python2.5.dll" popup window. Clicking OK allows me 
to continue normally.
2) There is an additional warning message inline only: "could not open 
library Csound\plugins\csnd.dll. (I really wish this message would disappear 
as well.)
3) The .csd performs normally except for one problem:
4) CTRL-C does not exit cleanly; CTRL-ALT-DEL is required (which returns to 
Windows, in turn requiring a return to the appropriate commandline 
directory).

Mike, IMO it would be really helpful if you had a Windows system without 
Csound on which you could try out new installs (at least float versions) 
with a simple realtime csd. (I'd be happy to come up with the latter: no 
MIDI, just an ASCII key to turn a note on and off for testing purposes.) I 
think this could save us all a portion of grief.

And - thanks for all your wonderful, tireless work.

Art Hunkins

----- Original Message ----- 
From: "Rory Walsh" 
To: 
Sent: Monday, June 29, 2009 7:43 AM
Subject: [Csnd] Re: Re: Re: Csound's viability on Windows for non-technical 
users...


> Sorry Mike but the last time I installed the latest version of Csound
> on a fresh machine Csound still complained about python2.whatever
> missing. I guess this is because the python opcodes are still in the
> opcode and bin directory even if users wish not to install python
> first.
>
> Rory.
>
>
> 2009/6/29  :
>> I responded to most of these questions in my previous email.
>>
>> About Python and the Windows Csound installer, as far as I know the 
>> problem
>> has been solved... but this email may result on my finding out that it 
>> has
>> not been solved after all!
>>
>> Regards,
>> Mike
>>
>> ----- Original Message ----- From: 
>> To: 
>> Sent: Monday, June 29, 2009 3:47 AM
>> Subject: [Csnd] Re: Csound's viability on Windows for non-technical 
>> users...
>>
>>
>>
>>>
>>> 1) How difficult would it be to build Csound without Python (i.e. no
>>> Scons/Python needed from build to end-use)?
>>
>>
>> You will need to write a new Makefile for each platform. Or, worse, write 
>> an
>> autoconf script etc.
>>
>>>
>>> 2) Can I build Csound with the standard version of mingw (not the setjmp
>>> longjmp version -- or whatever it's called). If not, then how hard would 
>>> it
>>> be to recode the "jumps" so it can be built on the normal version of 
>>> mingw
>>> (I haven't delved into the code deeply but as far as I can tell the 
>>> "jumps"
>>> are error and return related so it would seem that they could be 
>>> removed).
>>
>> I'm not sure about this. I have installed the standard version of MinGW 
>> (as
>> far as I can remember) a
>> couple of months ago in this vista computer I have at home and it builds
>> Csound for me alright.
>> Not sure about this requirement now. Mike Gogins will tell you more...
>>
>>>
>>> 3) How many "core" dependencies does Csound really have? It seems like
>>> most of the dependencies are gui and binding related and that the basic
>>> table, opcode, and soundfile code use a small set of libraries that are 
>>> easy
>>> to build.
>>
>> The only core dependency is libsndfile. Everything else is optional. With
>> libsndfile only you
>> get a functional system on all platforms. However on Windows RT IO is bad
>> because it
>> will use the MME IO module. So in this platform I would recommend at 
>> least
>> adding portaudio
>> to the list for ASIO.
>>
>>>
>>> 4) My main user-group will be on Windows and I'd like to make the use of
>>> Csound as transparent as possible but I'm concerned about Csound's 
>>> installer
>>> for it. Last I knew it was leaving users with an unresolved Python 
>>> library
>>> message box issue during Csound startup. Is this still the case?
>>
>> Mike Gogins is your man on this one.
>>
>>
>> Victor
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

Thanks for the information. I will make every effort to fix this, I
know it is annoying.

For your information,  to test this, I remove Csound and Python from
my computer, and then I install Csound. There were no annoying popups
for me last time I tried this.

I'd be interested to hear if anyone has installed and not had the
popup appear AND they didn't have Python....

In theory you should not see the popup if Csound can't find any plugin
opcode that is linked to the Python library and if Csound can't find
_csnd or _CsoundAC.

Regards,
Mike

On 6/30/09, Art Hunkins  wrote:
> OK, I'll jump in here. (After all, I've been the lead complainer about the
> Windows Python popup.)
>
> Yes, the problem popup still lives - at least on Windows XP with the 5.10
> float installer.
>
> I've just done a thorough test, uninstalling all versions of Csound and
> clearing out all Csound-related environment variables. (I also searched for
> any other files with "python" in their names. Nothing. I can vouch that
> Python is *not* installed.)
>
> I did a clean install of the float installer, specifying to continue without
> Python2.5.
>
> Running a realtime .csd from the commandline:
>
> 1) I get the "can't find Python2.5.dll" popup window. Clicking OK allows me
> to continue normally.
> 2) There is an additional warning message inline only: "could not open
> library Csound\plugins\csnd.dll. (I really wish this message would disappear
> as well.)
> 3) The .csd performs normally except for one problem:
> 4) CTRL-C does not exit cleanly; CTRL-ALT-DEL is required (which returns to
> Windows, in turn requiring a return to the appropriate commandline
> directory).
>
> Mike, IMO it would be really helpful if you had a Windows system without
> Csound on which you could try out new installs (at least float versions)
> with a simple realtime csd. (I'd be happy to come up with the latter: no
> MIDI, just an ASCII key to turn a note on and off for testing purposes.) I
> think this could save us all a portion of grief.
>
> And - thanks for all your wonderful, tireless work.
>
> Art Hunkins
>
> ----- Original Message -----
> From: "Rory Walsh" 
> To: 
> Sent: Monday, June 29, 2009 7:43 AM
> Subject: [Csnd] Re: Re: Re: Csound's viability on Windows for non-technical
> users...
>
>
>> Sorry Mike but the last time I installed the latest version of Csound
>> on a fresh machine Csound still complained about python2.whatever
>> missing. I guess this is because the python opcodes are still in the
>> opcode and bin directory even if users wish not to install python
>> first.
>>
>> Rory.
>>
>>
>> 2009/6/29  :
>>> I responded to most of these questions in my previous email.
>>>
>>> About Python and the Windows Csound installer, as far as I know the
>>> problem
>>> has been solved... but this email may result on my finding out that it
>>> has
>>> not been solved after all!
>>>
>>> Regards,
>>> Mike
>>>
>>> ----- Original Message ----- From: 
>>> To: 
>>> Sent: Monday, June 29, 2009 3:47 AM
>>> Subject: [Csnd] Re: Csound's viability on Windows for non-technical
>>> users...
>>>
>>>
>>>
>>>>
>>>> 1) How difficult would it be to build Csound without Python (i.e. no
>>>> Scons/Python needed from build to end-use)?
>>>
>>>
>>> You will need to write a new Makefile for each platform. Or, worse, write
>>>
>>> an
>>> autoconf script etc.
>>>
>>>>
>>>> 2) Can I build Csound with the standard version of mingw (not the setjmp
>>>> longjmp version -- or whatever it's called). If not, then how hard would
>>>>
>>>> it
>>>> be to recode the "jumps" so it can be built on the normal version of
>>>> mingw
>>>> (I haven't delved into the code deeply but as far as I can tell the
>>>> "jumps"
>>>> are error and return related so it would seem that they could be
>>>> removed).
>>>
>>> I'm not sure about this. I have installed the standard version of MinGW
>>> (as
>>> far as I can remember) a
>>> couple of months ago in this vista computer I have at home and it builds
>>> Csound for me alright.
>>> Not sure about this requirement now. Mike Gogins will tell you more...
>>>
>>>>
>>>> 3) How many "core" dependencies does Csound really have? It seems like
>>>> most of the dependencies are gui and binding related and that the basic
>>>> table, opcode, and soundfile code use a small set of libraries that are
>>>> easy
>>>> to build.
>>>
>>> The only core dependency is libsndfile. Everything else is optional. With
>>> libsndfile only you
>>> get a functional system on all platforms. However on Windows RT IO is bad
>>> because it
>>> will use the MME IO module. So in this platform I would recommend at
>>> least
>>> adding portaudio
>>> to the list for ASIO.
>>>
>>>>
>>>> 4) My main user-group will be on Windows and I'd like to make the use of
>>>> Csound as transparent as possible but I'm concerned about Csound's
>>>> installer
>>>> for it. Last I knew it was leaving users with an unresolved Python
>>>> library
>>>> message box issue during Csound startup. Is this still the case?
>>>
>>> Mike Gogins is your man on this one.
>>>
>>>
>>> Victor
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com