visualpython-users

[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
> ************************************************
>   

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

[Bruce S. <Bru...@nc...>]

The issue is with IDLE, a component of Python, not with VPython itself 
(though the basic architecture was originally developed by David Scherer 
when he was first building VPython), so you might want to bring this to 
the attention of the Python people.

Basically, the way IDLE works is that it spawns a separate copy of 
Python, which among other things keeps the running of your program at 
arm's length from the editing of your program, and so provides more 
security in terms of not losing your editing work. A socket is created 
to permit communication between IDLE and your running program. This 
socket is purely internal and makes no connection to the outside world, 
as you see in the boiler plate shown in the shell window when you first 
run from IDLE:

Personal firewall software may warn about the connection IDLE
makes to its subprocess using this computer's internal loopback
interface.  This connection is not visible on any external
interface and no data is sent to or received from the Internet.

Some firewalls ask you whether to continue blocking access or not for 
this program, and of course you should unblock.

A possibly separate issue is that occasionally one gets a socket error 
with no firewall issue in sight. The only way I know to clear this (at 
least on Windows, where most of my experience lies) is to log out and 
log back in (if the machine is configured that way) or to reboot.

Are these Windows laptops, Mac? Linux?

Bruce Sherwood

Pete Border wrote:

>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
>
>  
>

[Visualpython-users] Mac 10.4: _tkinter.TclError: this isn't a Tk application couldn't connect to display ":0.0"

[Jon S. <js...@gm...>]

Vpython has stopped working.  What to do?

I'm suddenly having problems I remember from 3 years ago and gather it has
something to do with the upgrade of x11.  But I can't figure out how to get
it going again.

When I run vpython I get

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Traceback (most recent call last):
  File "/sw/bin/idle2.4", line 5, in ?
    main()
  File "/sw/lib/python2.4/idlelib/PyShell.py", line 1350, in main
    root = Tk(className="Idle")
  File "/sw/lib/python2.4/lib-tk/Tkinter.py", line 1569, in __init__
    self.tk = _tkinter.create(screenName, baseName, className, interactive,
wantobjects, useTk, sync, use)
_tkinter.TclError: this isn't a Tk applicationcouldn't connect to display
":0.0"
[apples-powerbook-g4-99:/] apple%

   
x11 is running
But if I try running startX from a non-x11 terminal I get this:

/usr/X11R6/bin/startx: line 33: [: /Users/apple: binary operator expected
/usr/X11R6/bin/startx: line 42: [: /Users/apple: binary operator expected


XFree86 Version 4.4.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
[DRI] screen 0 installation complete
 

Re: [Visualpython-users] Mac 10.4: _tkinter.TclError: this isn't a Tk application couldn't connect to display ":0.0"

[Martin C. <cos...@wa...>]

Jon Schull wrote:
> Vpython has stopped working.  What to do?

What you show has nothing to do with vpython nor with tkinter. You need 
to run X11 which you don't seem to be able to.

> I'm suddenly having problems I remember from 3 years ago and gather it has
> something to do with the upgrade of x11.  But I can't figure out how to get
> it going again.
> 
> When I run vpython I get
> 
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified

The X server is not starting up completely.

> Traceback (most recent call last):
>   File "/sw/bin/idle2.4", line 5, in ?
>     main()
>   File "/sw/lib/python2.4/idlelib/PyShell.py", line 1350, in main
>     root = Tk(className="Idle")
>   File "/sw/lib/python2.4/lib-tk/Tkinter.py", line 1569, in __init__
>     self.tk = _tkinter.create(screenName, baseName, className, interactive,
> wantobjects, useTk, sync, use)
> _tkinter.TclError: this isn't a Tk applicationcouldn't connect to display
> ":0.0"
> [apples-powerbook-g4-99:/] apple%

You get this when you try to run vpython without running X11.

> x11 is running

Actually no. It tries to start, but doesn't manage.

> But if I try running startX from a non-x11 terminal I get this:

Using startx on MacOSX is always a bad idea. Why don't you just 
double-click on X11.app?

> /usr/X11R6/bin/startx: line 33: [: /Users/apple: binary operator expected
> /usr/X11R6/bin/startx: line 42: [: /Users/apple: binary operator expected

This looks like you have a user name with a space inside, like "apple 
user". Dont't do this, it will break all kinds of things.

-- 
Martin

Re: [Visualpython-users] Mac 10.4: _tkinter.TclError: this isn't a Tk application couldn't connect to display ":0.0"

[Jon S. <js...@gm...>]

Thanks

I did determine that the problem was an X11 problem, and after repairing
permissions, reinstalling python, and vpython, and resinstalling x11
1.1.3...I'm happy to say that back in business.

Happy Thanksgiving to all


On 11/22/06 4:19 PM, "Martin Costabel" <cos...@wa...> wrote:

> Jon Schull wrote:
>> Vpython has stopped working.  What to do?
> 
> What you show has nothing to do with vpython nor with tkinter. You need
> to run X11 which you don't seem to be able to.
> 
>> I'm suddenly having problems I remember from 3 years ago and gather it has
>> something to do with the upgrade of x11.  But I can't figure out how to get
>> it going again.
>> 
>> When I run vpython I get
>> 
>> Xlib: connection to ":0.0" refused by server
>> Xlib: No protocol specified
> 
> The X server is not starting up completely.
> 
>> Traceback (most recent call last):
>>   File "/sw/bin/idle2.4", line 5, in ?
>>     main()
>>   File "/sw/lib/python2.4/idlelib/PyShell.py", line 1350, in main
>>     root = Tk(className="Idle")
>>   File "/sw/lib/python2.4/lib-tk/Tkinter.py", line 1569, in __init__
>>     self.tk = _tkinter.create(screenName, baseName, className, interactive,
>> wantobjects, useTk, sync, use)
>> _tkinter.TclError: this isn't a Tk applicationcouldn't connect to display
>> ":0.0"
>> [apples-powerbook-g4-99:/] apple%
> 
> You get this when you try to run vpython without running X11.
> 
>> x11 is running
> 
> Actually no. It tries to start, but doesn't manage.
> 
>> But if I try running startX from a non-x11 terminal I get this:
> 
> Using startx on MacOSX is always a bad idea. Why don't you just
> double-click on X11.app?
> 
>> /usr/X11R6/bin/startx: line 33: [: /Users/apple: binary operator expected
>> /usr/X11R6/bin/startx: line 42: [: /Users/apple: binary operator expected
> 
> This looks like you have a user name with a space inside, like "apple
> user". Dont't do this, it will break all kinds of things.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Schull, Ph.D.
Associate Professor
Information Technology
Rochester Institute of Technology
102 Lomb Memorial Drive
Rochester, New York 14623
sc...@di...
fax: 978-246-0487
cell: 585-738-6696