[Visualpython-users] sockets errors, vpython, and windows xp?

[Pete B. <bo...@ma...>]

Hi:

I'm trying to have students use vpython on their own laptops, and 
several of the newer ones are getting socket errors. The errors are not 
very repeatable, but they seem to go away if ne turns off the firewall. 
Is this a known problem, and ifso, how does one fix it?
                            thanks;
                                    Pete Border

vis...@li... wrote:
> Send Visualpython-users mailing list submissions to
> 	vis...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/visualpython-users
> or, via email, send a message with subject or body 'help' to
> 	vis...@li...
>
> You can reach the person managing the list at
> 	vis...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Visualpython-users digest..."
>
>
> Today's Topics:
>
>    1. Re: Python 2.5 (Arthur Siegel)
>    2. Re: Python 2.5 (Gary Pajer)
>    3. Re: Python 2.5 (Arthur Siegel)
>    4. Python 2.5 version for Windows available (Bruce Sherwood)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 09 Oct 2006 12:52:29 -0400
> From: Arthur Siegel <ajs...@op...>
> Subject: Re: [Visualpython-users] Python 2.5
> To: Jonathan Brandmeyer <jbr...@ea...>
> Cc: vpusers <vis...@li...>
> Message-ID: <1160412749.3105.7.camel@localhost>
> Content-Type: text/plain
>
> On Sat, 2006-10-07 at 20:37 -0400, Arthur Siegel wrote:
>
>   
>> Am I correct that num_util.h and num_util.cpp are those
>> of Phil Austin @ Univ of British Columbia?
>>
>> http://www.eos.ubc.ca/research/clouds/software/pythonlibs/num_util/num_util_release2/
>>
>> If so, there is a new version targeting Numpy, as per the above link.
>>
>> Except that I can't even get it to compile and run the tests correctly.
>>
>> Choking on `intp` types and other places.
>>
>> Grrrr...
>>
>> Numpy is moving fast toward a 1.0 release and I have to wonder whether
>> the num_util code is incompatible with the latest Numpy.
>>
>> Or else I am doing something stupid.
>>     
>
> Turns out my instincts were correct, and I was only stupid to the extent
> that it took be longer than it should have (had I had more background,
> at least) to realize this.
>
> Numpy's include files were in fact changed since Phil released his
> num_util code for numpy.  Following those changes through to the
> num_util code I now get that code to compile.
>
> I guess my strategy is to start from the new num_utils and do a bit of
> monkey-see, monkey-do, following what changes Jonathan had made to the
> orignal, making the analogous on the new, and see if I can follow things
> through from there.
>
> Lot's of moving parts though, as we also have the boost libraries in
> play, and any changes that are happening there to deal with numpy and
> Python2.5.
>
>
> We'll see.
>
> Art
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 09 Oct 2006 13:24:46 -0400
> From: Gary Pajer <gp...@ri...>
> Subject: Re: [Visualpython-users] Python 2.5
> To: vpusers <vis...@li...>
> Message-ID: <452...@ri...>
> Content-Type: text/plain; format=flowed; charset=us-ascii
>
> Arthur Siegel wrote:
>
>   
>> On Sat, 2006-10-07 at 20:37 -0400, Arthur Siegel wrote:
>>
>>  
>>
>>     
>>> Am I correct that num_util.h and num_util.cpp are those
>>> of Phil Austin @ Univ of British Columbia?
>>>    
>>>
>>>       
> [...]
>
>   
>> Numpy's include files were in fact changed since Phil released his
>> num_util code for numpy.  Following those changes through to the
>> num_util code I now get that code to compile.
>>
>>     
> This is the comment that sparked my comment on license issues.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 09 Oct 2006 13:55:04 -0400
> From: Arthur Siegel <ajs...@op...>
> Subject: Re: [Visualpython-users] Python 2.5
> To: Gary Pajer <gp...@ri...>
> Cc: vpusers <vis...@li...>
> Message-ID: <1160416504.5057.3.camel@localhost>
> Content-Type: text/plain
>
> On Mon, 2006-10-09 at 13:24 -0400, Gary Pajer wrote:
>
>   
>>> Numpy's include files were in fact changed since Phil released his
>>> num_util code for numpy.  Following those changes through to the
>>> num_util code I now get that code to compile.
>>>
>>>       
>> This is the comment that sparked my comment on license issues.
>>     
>
> Again, no change from where things are, as current VPython derives from
> its prior release, as is noted by Jonathan in the source file itself.
> The num_utils code is released subject to the Boost license, which is
> short and sweet and unrestrictive in any sense:
>
> http://www.boost.org/LICENSE_1_0.txt
>
> Art
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 09 Oct 2006 12:41:21 -0600
> From: Bruce Sherwood <Bru...@nc...>
> Subject: [Visualpython-users] Python 2.5 version for Windows available
> To: vpusers <vis...@li...>
> Message-ID: <452...@nc...>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Thanks to the suggestion to compile Numeric from source on Windows, I 
> was able to post versions of VPython for Python 2.5, both Visual 3 and 
> Visual 4. This is a stop-gap measure since we all realize the need to 
> move to the new NumPy.
>
> I had to Google to find the following syntax for compiling Numeric on 
> Windows using Msys and MinGW:
>
> /c/python25/python.exe setup.py build ?compiler=mingw32 install
>
> In the process I updated in CVS the install instructions INSTALL.txt, 
> which are now essentially identical for both Visual 3 and Visual 4. I 
> hope this is useful to Arthur and others who may be able to work on 
> Visual. I wouldn't have been able to make these releases at this time 
> had it not been that little effort was required, once it was pointed out 
> how to get around the lack of a binary distribution of Numeric for 
> Python 2.5 on Windows.
>
> FYI, in the process of testing the new releases I found that Python 2.5 
> is more restrictive than previous versions. It's pickier about 
> indentation consistency, and "from __future__ import division" must be 
> the very first line in a program. These new restrictions required minor 
> fixes to a few example programs.
>
> Bruce Sherwood
>
>
>
>
> ------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> ------------------------------
>
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>
> End of Visualpython-users Digest, Vol 5, Issue 6
> ************************************************
>