You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(15) |
Oct
(32) |
Nov
(35) |
Dec
(48) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(46) |
Feb
(22) |
Mar
(65) |
Apr
(49) |
May
(22) |
Jun
(29) |
Jul
(51) |
Aug
(34) |
Sep
(32) |
Oct
(46) |
Nov
(30) |
Dec
(32) |
2002 |
Jan
(48) |
Feb
(4) |
Mar
(20) |
Apr
(28) |
May
(13) |
Jun
(34) |
Jul
(51) |
Aug
(15) |
Sep
(15) |
Oct
(35) |
Nov
(15) |
Dec
(20) |
2003 |
Jan
(31) |
Feb
(111) |
Mar
(41) |
Apr
(28) |
May
(36) |
Jun
(29) |
Jul
(27) |
Aug
(29) |
Sep
(47) |
Oct
(28) |
Nov
(7) |
Dec
(26) |
2004 |
Jan
(44) |
Feb
(9) |
Mar
(17) |
Apr
(26) |
May
(58) |
Jun
(13) |
Jul
(44) |
Aug
(64) |
Sep
(30) |
Oct
(11) |
Nov
(21) |
Dec
(28) |
2005 |
Jan
(29) |
Feb
(11) |
Mar
(11) |
Apr
(22) |
May
(85) |
Jun
(46) |
Jul
(17) |
Aug
(18) |
Sep
(14) |
Oct
(22) |
Nov
(1) |
Dec
(45) |
2006 |
Jan
(20) |
Feb
(36) |
Mar
(18) |
Apr
(24) |
May
(21) |
Jun
(48) |
Jul
(23) |
Aug
(20) |
Sep
(10) |
Oct
(41) |
Nov
(46) |
Dec
(40) |
2007 |
Jan
(40) |
Feb
(20) |
Mar
(13) |
Apr
(6) |
May
(24) |
Jun
(31) |
Jul
(30) |
Aug
(11) |
Sep
(11) |
Oct
(10) |
Nov
(56) |
Dec
(64) |
2008 |
Jan
(64) |
Feb
(22) |
Mar
(63) |
Apr
(28) |
May
(25) |
Jun
(36) |
Jul
(11) |
Aug
(9) |
Sep
(14) |
Oct
(41) |
Nov
(46) |
Dec
(130) |
2009 |
Jan
(95) |
Feb
(41) |
Mar
(24) |
Apr
(35) |
May
(53) |
Jun
(67) |
Jul
(48) |
Aug
(48) |
Sep
(86) |
Oct
(75) |
Nov
(64) |
Dec
(52) |
2010 |
Jan
(57) |
Feb
(31) |
Mar
(28) |
Apr
(40) |
May
(25) |
Jun
(42) |
Jul
(79) |
Aug
(31) |
Sep
(49) |
Oct
(66) |
Nov
(38) |
Dec
(25) |
2011 |
Jan
(29) |
Feb
(18) |
Mar
(44) |
Apr
(6) |
May
(28) |
Jun
(31) |
Jul
(36) |
Aug
(24) |
Sep
(30) |
Oct
(23) |
Nov
(21) |
Dec
(27) |
2012 |
Jan
(14) |
Feb
(11) |
Mar
(2) |
Apr
(48) |
May
(7) |
Jun
(32) |
Jul
(22) |
Aug
(25) |
Sep
(31) |
Oct
(32) |
Nov
(21) |
Dec
(17) |
2013 |
Jan
(44) |
Feb
(27) |
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(4) |
Sep
(1) |
Oct
(7) |
Nov
(5) |
Dec
(5) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(2) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bruce S. <Bru...@nc...> - 2009-10-18 17:58:50
|
And there is PIL, the Python Imaging Library, which can do lots of image conversions. But the fundamental problem is that you'll have a low-resolution bitmap image, which isn't good for many applications. Bruce Sherwood Stanley Sokolow wrote: > Bruce is correct that there are screenshot functions in the operating > systems, including LInux. In Ubuntu Linux and probably most > distributions, there's a widget that can be added to the desktop panel > for taking a screenshot. On Windows, I use the Shift-PrintScrn key > combination, then open the accessory program called Paint and paste > (Ctrl-V) the clipboard onto the canvas. Using Paint you can crop and > make other changes, then save as jpeg or other formats. I've used this > to make step-by-step instruction manuals for using software, with a > screenshot of each important step. > > Another useful program is the ImageMagick library, which is available > for many programming languages, including Python: > http://www.imagemagick.org/script/index.php. It can do lots of image > conversions. > > Stan > > ------------------------------------ > On Sun, Oct 18, 2009 at 8:00 AM, Bruce Sherwood <Bru...@nc... > <mailto:Bru...@nc...>> wrote: > > That could be useful; perhaps the reason it's not there is that > there hasn't > been much need expressed for such a facility. Note that on Windows > and Mac (and > maybe on Linux?) there are facilities built-in to get screen shots. > For example, > Alt-Print Screen on Windows captures a bitmap image of the active > window, which > can then be pasted into various applications, including Word. > > Converting to jpeg is NOT a small job. A jpeg is extremely different > from a > bitmap image. Any easily-implemented screen capture will necessarily > be a bitmap > image, and therefore necessarily low-resolution for print purposes. > > For many purposes one wants something much better than a bitmap > image. In the > contributed section of vpython.org <http://vpython.org> the > povexport utility generates a file that > can be read by the freeware POV-ray application to generate a > high-resolution > ray-traced image of a VPython scene. > > A separate issue is that it would be very useful, and probably not very > difficult, to generate a PostScript file from a (two-dimensional) > graph in order > to produce high-resolution prints of graphs. > > Bruce Sherwood > > Anders Wallin wrote: > > Hi all, > > > > Why is there no screenshot function in visual? > > > > I've looked a bit at SDL/OpenGL in C++ under Ubuntu, and it's about a > > 5 min job to google for the correct screenshot code and get it > > working. It saves a 24-bit TGA-file, but I imagine changing that to > > bmp or jpeg or similar is not a big job either. I must be missing > > something? > > > > thanks, > > > > Anders > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > <mailto:Vis...@li...> > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
From: Stanley S. <ove...@ea...> - 2009-10-18 17:55:35
|
Bruce is correct that there are screenshot functions in the operating systems, including LInux. In Ubuntu Linux and probably most distributions, there's a widget that can be added to the desktop panel for taking a screenshot. On Windows, I use the Shift-PrintScrn key combination, then open the accessory program called Paint and paste (Ctrl-V) the clipboard onto the canvas. Using Paint you can crop and make other changes, then save as jpeg or other formats. I've used this to make step-by-step instruction manuals for using software, with a screenshot of each important step. Another useful program is the ImageMagick library, which is available for many programming languages, including Python: http://www.imagemagick.org/script/index.php. It can do lots of image conversions. Stan ------------------------------------ On Sun, Oct 18, 2009 at 8:00 AM, Bruce Sherwood <Bru...@nc...>wrote: > That could be useful; perhaps the reason it's not there is that there > hasn't > been much need expressed for such a facility. Note that on Windows and Mac > (and > maybe on Linux?) there are facilities built-in to get screen shots. For > example, > Alt-Print Screen on Windows captures a bitmap image of the active window, > which > can then be pasted into various applications, including Word. > > Converting to jpeg is NOT a small job. A jpeg is extremely different from a > bitmap image. Any easily-implemented screen capture will necessarily be a > bitmap > image, and therefore necessarily low-resolution for print purposes. > > For many purposes one wants something much better than a bitmap image. In > the > contributed section of vpython.org the povexport utility generates a file > that > can be read by the freeware POV-ray application to generate a > high-resolution > ray-traced image of a VPython scene. > > A separate issue is that it would be very useful, and probably not very > difficult, to generate a PostScript file from a (two-dimensional) graph in > order > to produce high-resolution prints of graphs. > > Bruce Sherwood > > Anders Wallin wrote: > > Hi all, > > > > Why is there no screenshot function in visual? > > > > I've looked a bit at SDL/OpenGL in C++ under Ubuntu, and it's about a > > 5 min job to google for the correct screenshot code and get it > > working. It saves a 24-bit TGA-file, but I imagine changing that to > > bmp or jpeg or similar is not a big job either. I must be missing > > something? > > > > thanks, > > > > Anders > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Bruce S. <Bru...@nc...> - 2009-10-18 15:01:01
|
That could be useful; perhaps the reason it's not there is that there hasn't been much need expressed for such a facility. Note that on Windows and Mac (and maybe on Linux?) there are facilities built-in to get screen shots. For example, Alt-Print Screen on Windows captures a bitmap image of the active window, which can then be pasted into various applications, including Word. Converting to jpeg is NOT a small job. A jpeg is extremely different from a bitmap image. Any easily-implemented screen capture will necessarily be a bitmap image, and therefore necessarily low-resolution for print purposes. For many purposes one wants something much better than a bitmap image. In the contributed section of vpython.org the povexport utility generates a file that can be read by the freeware POV-ray application to generate a high-resolution ray-traced image of a VPython scene. A separate issue is that it would be very useful, and probably not very difficult, to generate a PostScript file from a (two-dimensional) graph in order to produce high-resolution prints of graphs. Bruce Sherwood Anders Wallin wrote: > Hi all, > > Why is there no screenshot function in visual? > > I've looked a bit at SDL/OpenGL in C++ under Ubuntu, and it's about a > 5 min job to google for the correct screenshot code and get it > working. It saves a 24-bit TGA-file, but I imagine changing that to > bmp or jpeg or similar is not a big job either. I must be missing > something? > > thanks, > > Anders |
From: Guy K. K. <g....@ma...> - 2009-10-17 23:58:32
|
Trying to track down the problem further I've hit some leads that seem to indicate that there seem to be quite some problems on Ubuntu Karmic with Boost.Python (version 1.38.0-6ubuntu6). The PySide team has had also some similar problems, as well as someone else. Here's a thread on the Py++ mailing list on this http://www.nabble.com/-py%2B%2B-- AttributeError:-%27Boost.Python.StaticProperty%27-object- attribute-%27__doc__%27-is-read-only-td25058627.html or short http://ur1.ca/du0m It seems like Visual is not using .def_readonly(...), but I guess then that this is only one of the ways to trigger this bug/behaviour. Maybe some Boost specialist knows an approach to tackle this problem? Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Anders W. <and...@gm...> - 2009-10-17 20:45:18
|
Hi all, Why is there no screenshot function in visual? I've looked a bit at SDL/OpenGL in C++ under Ubuntu, and it's about a 5 min job to google for the correct screenshot code and get it working. It saves a 24-bit TGA-file, but I imagine changing that to bmp or jpeg or similar is not a big job either. I must be missing something? thanks, Anders |
From: Guy K. K. <g....@ma...> - 2009-10-16 02:04:51
|
Just tried a port of the python-visual 5.12 package from Debian Sid to Ubuntu Karmic, but the effect was unfortunately the same: https://bugs.launchpad.net/ubuntu/+source/python-visual/+bug/408663 I'm assuming it has got something to do with the Boost(.Python) version used in Karmic (1.38) that may be the reason of the trouble. Any indicators from somewhere on that particular Boost version towards compiling/solving the problem? Has anybody successfully compiled abainst Boost 1.38 libraries? Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Guy K. K. <g....@ma...> - 2009-10-14 20:53:38
|
I'm now leaping due to other concerns on my laptop ahead to Karmic already. And I'm also experiencing problems with the provided python-visual 5.11 packages, as well as with the build resulting from dpkg-buildpackage from the source package. However the problem seems to be somewhat different from the one stated in the Karmic bug report here: https://bugs.launchpad.net/ubuntu/+source/python-visual/+bug/408663 The symptoms are different from Tony/Guenter's filing/reporting. I'm getting an attribute error on executing a sample: guy@mountpaku:/usr/share/doc/python-visual/examples$ python orbit.py Traceback (most recent call last): File "orbit.py", line 1, in <module> from visual import * File "/usr/lib/python2.6/dist-packages/visual/__init__.py", line 59, in <module> import cvisual AttributeError: 'Boost.Python.StaticProperty' object attribute '__doc__' is read-only Any ideas? This seems to be much more low level, so I'm actually in doubt that 5.12 or later would have this problem solved, as I think that they mostly targeted the API and internal implementation rather than the wrapping as it is. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |
From: Bruce S. <Bru...@nc...> - 2009-10-13 19:23:03
|
Visual 5.13 released for Windows (Python 2.6), Mac (Python 2.6, Intel, OSX 10.4 and above), and Linux. Bugs fixed on Linux concerned with making windows visible and invisible, and with reporting correct values of scene.x, scene.y, scene.width, and scene.height. Bugs fixed on all platforms: vector.mag now is ordinary number instead of numpy.ndarray; helix.color is (red,green,blue) instead of an array (the array of colors in the helical curve is helix.helix.color); corrected documentation error which erroneously claimed that that you couldn't specify a list of points for gcurve, gvbars, or ghbars; error in VIDLE corrected by Guilherme Polo -- sometimes initially scrolled so that the first line was not visible. Bruce Sherwood |
From: Bruce S. <Bru...@nc...> - 2009-10-13 17:31:09
|
Currently the way to get high-quality images is to use the povexport module available in the contributed section of vpython.org: "A module by Ruth Chabay to export a VPython scene to POV-Ray, which can create a high-resolution ray-traced image as a targa file, which can then be further manipulated in image-processing applications such as Photoshop. Markus Gritsch, Bruce Sherwood, Scott David Daniels, and Guy Kloss also contributed." Ruth Chabay and I have made extensive use of this machinery to prepare high-resolution images for a physics textbook. Bruce Sherwood Rob Salgado wrote: > I've been dreaming about getting Postscript vector graphics from a > VPython scene. > > (I've also been dreaming about options for rendering as wireframe or > as solid with enhanced edges and with dashed or invisible hidden-edges.) > > Apart from having VPython render Postscript in addition to OpenGL, > I wonder if these projects for getting Postscript from OpenGL might be useful > http://www.opengl.org/resources/code/samples/mjktips/Feedback.html > http://www.geuz.org/gl2ps/ > http://www.codeproject.com/KB/openGL/glexport.aspx > > For now, if I need a high-quality image, I screen-capture a VPython window > that I have maximized to a multiple (i.e. 2x2) monitor setup. > If necessary, one can try to vectorize the raster image with > http://autotrace.sourceforge.net/ > > Rob Salgado > > > Michele Mattioni wrote (Re: Exporting visual image in svg): >> Hi list, >> >> I was wondering if somebody ever thought about it. >> >> It would be really nice to export the image in svg, so they can be >> scaled without losing resolution. >> >> Cheers, >> Michele. > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Rob S. <rsa...@mt...> - 2009-10-13 17:14:16
|
I've been dreaming about getting Postscript vector graphics from a VPython scene. (I've also been dreaming about options for rendering as wireframe or as solid with enhanced edges and with dashed or invisible hidden-edges.) Apart from having VPython render Postscript in addition to OpenGL, I wonder if these projects for getting Postscript from OpenGL might be useful http://www.opengl.org/resources/code/samples/mjktips/Feedback.html http://www.geuz.org/gl2ps/ http://www.codeproject.com/KB/openGL/glexport.aspx For now, if I need a high-quality image, I screen-capture a VPython window that I have maximized to a multiple (i.e. 2x2) monitor setup. If necessary, one can try to vectorize the raster image with http://autotrace.sourceforge.net/ Rob Salgado Michele Mattioni wrote (Re: Exporting visual image in svg): > > Hi list, > > I was wondering if somebody ever thought about it. > > It would be really nice to export the image in svg, so they can be > scaled without losing resolution. > > Cheers, > Michele. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Michele M. <mat...@gm...> - 2009-10-13 12:48:22
|
Hi list, I was wondering if somebody ever thought about it. It would be really nice to export the image in svg, so they can be scaled without losing resolution. Cheers, Michele. |
From: Bruce S. <Bru...@nc...> - 2009-09-29 15:00:33
|
Works for me on Windows, though it's a little complicated, because you have to click on the shell window in order to enter the command (to be accepted by the "input" routine), and then after entering the command you have to click on the VPython graphics window for VPython to pick up inputs using scene.kb.getkey(). Bruce Sherwood Kadir Haldenbilen wrote: > Hello All, > > I am trying to write a little routine, which will enable intreacting > with the program while it is looping. > It is basically intended for debugging, butit may also be useful for > changing some attributes (and hence the logic) in flight. > > I am using the keyboard events to break-into the loop. I am using the > "@" character as a special character, > then, once detected I input my command from the shell (with > preceeding/following quote signs). > > It works OK for the first time. > > But, after the first one, "scene.kb.keys" does not sense the input key. > > Most probably, with the input() command I am breaking some stack, etc., > so that visual can not detect the keyboard input. > > You can find the sample code below. > > Any ideas will be appreciated. > > Thanks, > > Kadir > > ====================================== > > from visual import * > > bb = box() > > while 1: > > if scene.kb.keys: # event waiting to be processed? > s = scene.kb.getkey() # get keyboard info > print "s ", s # this is the key pressed > if s == "@": # see if it is the break character "@" > df = input("Enter Command: ") # If True, then > wait for command input > print df # This is the command entered > try: # it may be an invalid command, be > prepared > print eval(df) # execute the command > and print the result > except: > pass # if invalid command do nothing > > s = "" # reset the input key > print scene.kb.keys # check if there are any > other keyboard events > > bb.rotate(axis=(0,1,0), angle=0.01) # set something going on in > the loop > rate(25) > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > > > ------------------------------------------------------------------------ > > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Chris C. <scc...@gm...> - 2009-09-28 09:58:19
|
You should look into the threading module: http://docs.python.org/library/threading.html On Sun, Sep 27, 2009 at 9:05 PM, Kadir Haldenbilen <kha...@ya...> wrote: > Hello All, > > I am trying to write a little routine, which will enable intreacting with > the program while it is looping. > It is basically intended for debugging, butit may also be useful for > changing some attributes (and hence the logic) in flight. > > I am using the keyboard events to break-into the loop. I am using the "@" > character as a special character, > then, once detected I input my command from the shell (with > preceeding/following quote signs). > > It works OK for the first time. > > But, after the first one, "scene.kb.keys" does not sense the input key. > > Most probably, with the input() command I am breaking some stack, etc., so > that visual can not detect the keyboard input. > > You can find the sample code below. > > Any ideas will be appreciated. > > Thanks, > > Kadir > > ====================================== > > from visual import * > > bb = box() > > while 1: > > if scene.kb.keys: # event waiting to be processed? > s = scene.kb.getkey() # get keyboard info > print "s ", s # this is the key pressed > if s == "@": # see if it is the break character "@" > df = input("Enter Command: ") # If True, then wait > for command input > print df # This is the command entered > try: # it may be an invalid command, be > prepared > print eval(df) # execute the command and > print the result > except: > pass # if invalid command do nothing > > s = "" # reset the input key > print scene.kb.keys # check if there are any other > keyboard events > > bb.rotate(axis=(0,1,0), angle=0.01) # set something going on in the > loop > rate(25) > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
From: Kadir H. <kha...@ya...> - 2009-09-27 19:05:40
|
Hello All, I am trying to write a little routine, which will enable intreacting with the program while it is looping. It is basically intended for debugging, butit may also be useful for changing some attributes (and hence the logic) in flight. I am using the keyboard events to break-into the loop. I am using the "@" character as a special character, then, once detected I input my command from the shell (with preceeding/following quote signs). It works OK for the first time. But, after the first one, "scene.kb.keys" does not sense the input key. Most probably, with the input() command I am breaking some stack, etc., so that visual can not detect the keyboard input. You can find the sample code below. Any ideas will be appreciated. Thanks, Kadir ====================================== from visual import * bb = box() while 1: if scene.kb.keys: # event waiting to be processed? s = scene.kb.getkey() # get keyboard info print "s ", s # this is the key pressed if s == "@": # see if it is the break character "@" df = input("Enter Command: ") # If True, then wait for command input print df # This is the command entered try: # it may be an invalid command, be prepared print eval(df) # execute the command and print the result except: pass # if invalid command do nothing s = "" # reset the input key print scene.kb.keys # check if there are any other keyboard events bb.rotate(axis=(0,1,0), angle=0.01) # set something going on in the loop rate(25) |
From: Aaron M. <ajm...@al...> - 2009-09-22 16:41:43
|
Hello All, Try this little big of code: from visual import * a=helix() print a.color I notice that the color for each segment is returned as a numpy array. This is actually quite fun, since you can individually set the color along the helix, but leads to problems matching colors between objects, for instance: a=helix() b=sphere() b.color=a.color This gives the error: Traceback (most recent call last): File "<pyshell#17>", line 1, in <module> b.color=a.color ArgumentError: Python argument types in None.None(sphere, numpy.ndarray) did not match C++ signature: None(class cvisual::primitive {lvalue}, class cvisual::rgb) So, I would propose that somehow we preserve the ability to access the color array, say through an attribute "helix.colorarray" or something, but that a single color gets returned with the helix.color attribute. Aaron ------------------------------------------------------ Aaron J. Miller, Ph.D. Department of Physics 328 Palenske Hall Albion College, Albion, MI 49224 |
From: Guenter S. <Gue...@ph...> - 2009-09-17 19:49:01
|
Another workaround: This works in a simple python shell (on a computer with ATI graphics): ~ $python Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import wx >>> from visual import * >>> v = vector('x') Traceback (most recent call last): File "<stdin>", line 1, in <module> Boost.Python.ArgumentError: Python argument types in vector.__init__(vector, str) did not match C++ signature: __init__(_object*, cvisual::vector) __init__(_object*) __init__(_object*, double) __init__(_object*, double, double) __init__(_object*, double, double, double) >>> v = vector(1,2,3) >>> for i in v: ... print i ... 1.0 2.0 3.0 >>> quit() ~ $ My guess is that wxpython does something right during initialization which vpython is not doing by itself. Probably an accident that it works for nvidia cards. gs Guenter Schneider wrote: > Thank you for pointing me to pycrust. I can confirm the correct behavior > on my 'ATI' computer using it. It is very strange indeed. I wouldn't > call it a fix but it is a workaround. > > Guenter > > Jim Thomas wrote: >> When I run python on the command line I get segfaults like so: >> >> jim@jtws:~$ python >> Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) >> [GCC 4.3.3] on linux2 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> from visual import * >> >>> v = vector('x') >> Segmentation fault >> jim@jtws:~$ >> >> jim@jtws:~$ python >> Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) >> [GCC 4.3.3] on linux2 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> from visual import * >> >>> v = vector(1,2,3) >> >>> for i in v: >> ... print i >> ... >> 1.0 >> 2.0 >> 3.0 >> Segmentation fault >> jim@jtws:~$ >> >> However, this is interesting. When I run in PyCrust (distributed as >> part of wxPython) I get this instead: >> >> PyCrust 0.9.5 - The Flakiest Python Shell >> Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) >> [GCC 4.3.3] on linux2 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> from visual import * >> >>> v = vector('x') >> Traceback (most recent call last): >> File "<input>", line 1, in <module> >> ArgumentError: Python argument types in >> vector.__init__(vector, str) >> did not match C++ signature: >> __init__(_object*, cvisual::vector) >> __init__(_object*) >> __init__(_object*, double) >> __init__(_object*, double, double) >> __init__(_object*, double, double, double) >> >>> >> >>> v = vector(1,2,3) >> >>> for i in v: >> ... print i >> ... 1.0 >> 2.0 >> 3.0 >> >>> >> >> So basically it works fine so long as I'm using PyCrust. This would >> explain why I have not seen this as a problem since I rarely use the >> command line Python. I'm not quite sure what type of exception visual >> is throwing in the first test but I can catch it: >> >>> try: >> ... v = vector('x') >> ... except Exception as inst: >> ... print 'Exception Caught' >> ... print inst >> ... Exception Caught >> Python argument types in >> vector.__init__(vector, str) >> did not match C++ signature: >> __init__(_object*, cvisual::vector) >> __init__(_object*) >> __init__(_object*, double) >> __init__(_object*, double, double) >> __init__(_object*, double, double, double) >> >>> >> >> Hopefully this helps. it seems to me the simplest fix for you might >> just be to install wxPython and your students use >> PyShell/PyCrust/PyAlamode for code development. >> >> JT >> >> Guenter Schneider wrote: >>> What happens on your system if you run the 2 tests below? I agree it >>> is not a show shopper if you are an experienced programmer. The only >>> thing I can't do is iterate over vector elements (which is what caught >>> my attention). The matter is not so nice in a computational lab with >>> novice programmers who get a seg.fault instead of an error message. It >>> is also very annoying if you use vpython interactively. >>> >>> Guenter >>> >>> Jim Thomas wrote: >>>> Gee, I thought I had VPython working just fine on Ubuntu 9.04 AMD64 >>>> on ATI proprietary until I ran your tests. However since I was able >>>> to develop my VisualPyODE library and demos without problems on this >>>> platform, maybe it is not such a show stopper. I hadn't even noticed... >>>> >>>> JT >>>> >>>> Guenter Schneider wrote: >>>>> I have struggled to get vpython fully working on ubuntu for a while >>>>> now. Here is my summary what I learned. Let me say right away, as >>>>> far as I can tell it's not a vpython problem. >>>>> >>>>> First, unlike others on this list, I have no problems compiling >>>>> vpython 5.12. It works using debian Lenny on any computer I have >>>>> tried. By >>>>> 'it works' I mean these simple tests do not result in seg. faults: >>>>> >>>>> TEST 1: >>>>> >>> from visual import * >>>>> >>> v = vector('x') >>>>> Traceback (most recent call last): >>>>> File "<stdin>", line 1, in <module> >>>>> ValueError: Vectors must be constructed from sequences of 2 or 3 >>>>> float members. >>>>> >>> >>>>> >>>>> TEST 2: >>>>> >>> from visual import * >>>>> >>> v=vector(1,2,3) >>>>> >>> for i in v: >>>>> ... print i >>>>> ... >>>>> 1.0 >>>>> 2.0 >>>>> 3.0 >>>>> >>> >>>>> >>>>> On ubuntu 9.04 it works on some computers but not on others. It >>>>> doesn't matter if I use 32 bit or 64 bit ubuntu 9.04. >>>>> >>>>> In fact the same pattern holds true in my tests for the >>>>> python-visual package that is distributed with ubuntu 9.04 (which is >>>>> vpython 3.2.9). It fails on all computers if a proprietary graphics >>>>> driver is not installed. Activating an nvidia proprietary graphics >>>>> driver results in a working vpython (as defined above), on system >>>>> with ati graphics cards I was not so lucky. I tried 6 different >>>>> computers, 2 with nvidia graphics and 4 with ati graphics. >>>>> >>>>> I got the same result for ubuntu 8.10. It always works with ubuntu >>>>> 8.04.3. >>>>> >>>>> I filed a bug report with ubuntu against vpython since I have no >>>>> idea what is causing this problem. >>>>> >>>>> I could not try python-visual on karmic alpha (which 5.11) since >>>>> that leads to a seg fault like this >>>>> >>>>> >>> from visual import * >>>>> Segmentation fault >>>>> >>>>> There is already a bug report for this. >>>>> >>>>> Guenter >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> Come build with us! The BlackBerry® Developer Conference in SF, CA >>>>> is the only developer event you need to attend this year. Jumpstart >>>>> your >>>>> developing skills, take BlackBerry mobile applications to market and >>>>> stay ahead of the curve. Join us from November 9-12, 2009. >>>>> Register now! >>>>> http://p.sf.net/sfu/devconf >>>>> _______________________________________________ >>>>> Visualpython-users mailing list >>>>> Vis...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users >>>>> > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Guenter S. <Gue...@ph...> - 2009-09-17 19:18:56
|
Thank you for pointing me to pycrust. I can confirm the correct behavior on my 'ATI' computer using it. It is very strange indeed. I wouldn't call it a fix but it is a workaround. Guenter Jim Thomas wrote: > When I run python on the command line I get segfaults like so: > > jim@jtws:~$ python > Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) > [GCC 4.3.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from visual import * > >>> v = vector('x') > Segmentation fault > jim@jtws:~$ > > jim@jtws:~$ python > Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) > [GCC 4.3.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from visual import * > >>> v = vector(1,2,3) > >>> for i in v: > ... print i > ... > 1.0 > 2.0 > 3.0 > Segmentation fault > jim@jtws:~$ > > However, this is interesting. When I run in PyCrust (distributed as > part of wxPython) I get this instead: > > PyCrust 0.9.5 - The Flakiest Python Shell > Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) > [GCC 4.3.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from visual import * > >>> v = vector('x') > Traceback (most recent call last): > File "<input>", line 1, in <module> > ArgumentError: Python argument types in > vector.__init__(vector, str) > did not match C++ signature: > __init__(_object*, cvisual::vector) > __init__(_object*) > __init__(_object*, double) > __init__(_object*, double, double) > __init__(_object*, double, double, double) > >>> > >>> v = vector(1,2,3) > >>> for i in v: > ... print i > ... 1.0 > 2.0 > 3.0 > >>> > > So basically it works fine so long as I'm using PyCrust. This would > explain why I have not seen this as a problem since I rarely use the > command line Python. I'm not quite sure what type of exception visual > is throwing in the first test but I can catch it: > >>> try: > ... v = vector('x') > ... except Exception as inst: > ... print 'Exception Caught' > ... print inst > ... Exception Caught > Python argument types in > vector.__init__(vector, str) > did not match C++ signature: > __init__(_object*, cvisual::vector) > __init__(_object*) > __init__(_object*, double) > __init__(_object*, double, double) > __init__(_object*, double, double, double) > >>> > > Hopefully this helps. it seems to me the simplest fix for you might > just be to install wxPython and your students use > PyShell/PyCrust/PyAlamode for code development. > > JT > > Guenter Schneider wrote: >> What happens on your system if you run the 2 tests below? I agree it >> is not a show shopper if you are an experienced programmer. The only >> thing I can't do is iterate over vector elements (which is what caught >> my attention). The matter is not so nice in a computational lab with >> novice programmers who get a seg.fault instead of an error message. It >> is also very annoying if you use vpython interactively. >> >> Guenter >> >> Jim Thomas wrote: >>> Gee, I thought I had VPython working just fine on Ubuntu 9.04 AMD64 >>> on ATI proprietary until I ran your tests. However since I was able >>> to develop my VisualPyODE library and demos without problems on this >>> platform, maybe it is not such a show stopper. I hadn't even noticed... >>> >>> JT >>> >>> Guenter Schneider wrote: >>>> I have struggled to get vpython fully working on ubuntu for a while >>>> now. Here is my summary what I learned. Let me say right away, as >>>> far as I can tell it's not a vpython problem. >>>> >>>> First, unlike others on this list, I have no problems compiling >>>> vpython 5.12. It works using debian Lenny on any computer I have >>>> tried. By >>>> 'it works' I mean these simple tests do not result in seg. faults: >>>> >>>> TEST 1: >>>> >>> from visual import * >>>> >>> v = vector('x') >>>> Traceback (most recent call last): >>>> File "<stdin>", line 1, in <module> >>>> ValueError: Vectors must be constructed from sequences of 2 or 3 >>>> float members. >>>> >>> >>>> >>>> TEST 2: >>>> >>> from visual import * >>>> >>> v=vector(1,2,3) >>>> >>> for i in v: >>>> ... print i >>>> ... >>>> 1.0 >>>> 2.0 >>>> 3.0 >>>> >>> >>>> >>>> On ubuntu 9.04 it works on some computers but not on others. It >>>> doesn't matter if I use 32 bit or 64 bit ubuntu 9.04. >>>> >>>> In fact the same pattern holds true in my tests for the >>>> python-visual package that is distributed with ubuntu 9.04 (which is >>>> vpython 3.2.9). It fails on all computers if a proprietary graphics >>>> driver is not installed. Activating an nvidia proprietary graphics >>>> driver results in a working vpython (as defined above), on system >>>> with ati graphics cards I was not so lucky. I tried 6 different >>>> computers, 2 with nvidia graphics and 4 with ati graphics. >>>> >>>> I got the same result for ubuntu 8.10. It always works with ubuntu >>>> 8.04.3. >>>> >>>> I filed a bug report with ubuntu against vpython since I have no >>>> idea what is causing this problem. >>>> >>>> I could not try python-visual on karmic alpha (which 5.11) since >>>> that leads to a seg fault like this >>>> >>>> >>> from visual import * >>>> Segmentation fault >>>> >>>> There is already a bug report for this. >>>> >>>> Guenter >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> Come build with us! The BlackBerry® Developer Conference in SF, CA >>>> is the only developer event you need to attend this year. Jumpstart >>>> your >>>> developing skills, take BlackBerry mobile applications to market and >>>> stay ahead of the curve. Join us from November 9-12, 2009. >>>> Register now! >>>> http://p.sf.net/sfu/devconf >>>> _______________________________________________ >>>> Visualpython-users mailing list >>>> Vis...@li... >>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users >>>> >>> > |
From: Jim T. <jt...@mi...> - 2009-09-17 14:14:20
|
Gee, I thought I had VPython working just fine on Ubuntu 9.04 AMD64 on ATI proprietary until I ran your tests. However since I was able to develop my VisualPyODE library and demos without problems on this platform, maybe it is not such a show stopper. I hadn't even noticed... JT Guenter Schneider wrote: > I have struggled to get vpython fully working on ubuntu for a while now. > Here is my summary what I learned. Let me say right away, as far as I > can tell it's not a vpython problem. > > First, unlike others on this list, I have no problems compiling vpython > 5.12. It works using debian Lenny on any computer I have tried. By > 'it works' I mean these simple tests do not result in seg. faults: > > TEST 1: > >>> from visual import * > >>> v = vector('x') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ValueError: Vectors must be constructed from sequences of 2 or 3 float > members. > >>> > > TEST 2: > >>> from visual import * > >>> v=vector(1,2,3) > >>> for i in v: > ... print i > ... > 1.0 > 2.0 > 3.0 > >>> > > On ubuntu 9.04 it works on some computers but not on others. It doesn't > matter if I use 32 bit or 64 bit ubuntu 9.04. > > In fact the same pattern holds true in my tests for the python-visual > package that is distributed with ubuntu 9.04 (which is vpython 3.2.9). > It fails on all computers if a proprietary graphics driver is not > installed. Activating an nvidia proprietary graphics driver results in a > working vpython (as defined above), on system with ati graphics cards I > was not so lucky. I tried 6 different computers, 2 with nvidia graphics > and 4 with ati graphics. > > I got the same result for ubuntu 8.10. It always works with ubuntu 8.04.3. > > I filed a bug report with ubuntu against vpython since I have no idea > what is causing this problem. > > I could not try python-visual on karmic alpha (which 5.11) since that > leads to a seg fault like this > > >>> from visual import * > Segmentation fault > > There is already a bug report for this. > > Guenter > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Bruce S. <Bru...@nc...> - 2009-09-16 15:02:30
|
Thanks for keeping at this. For what it's worth (not much) I've not seen any of these problems on my dual-boot Dell XPS M1330 laptop with NVIDIA graphics. I'm using the proprietary graphics driver on Ubuntu 9.04. Bruce Sherwood |
From: Bruce S. <Bru...@nc...> - 2009-09-16 14:57:45
|
Thanks for reporting this mismatch. It seems like it really should be a list rather than a tuple, but if that's not feasible for some reason the documentation should be corrected. Bruce Sherwood Guenter Schneider wrote: > The online documentation at > http://vpython.org/contents/docs/visual/lights.html > says scene.lights is a list, however > > >>> from visual import * > >>> scene = display() > >>> print isinstance(scene.lights,list) > False > >>> print isinstance(scene.lights,tuple) > True > >>> > > Guenter |
From: Guenter S. <Gue...@ph...> - 2009-09-16 12:08:24
|
The online documentation at http://vpython.org/contents/docs/visual/lights.html says scene.lights is a list, however >>> from visual import * >>> scene = display() >>> print isinstance(scene.lights,list) False >>> print isinstance(scene.lights,tuple) True >>> Guenter |
From: Guenter S. <Gue...@ph...> - 2009-09-16 06:48:18
|
Tony Risinger wrote: > Yeah I opened that report but I haven't got any feedback yet. I am not surprised. Bug fixes in packages which are not essential to the facebook crowd proceed with glacial pace in ubuntu. > > I'm not sure what it means, but I took the python-visual 5.11 package from sid, tweaked the package slightly (python version was set to less than 2.6, I changed that to 2.7 so it would install, that's the only change I made) and tried it on ubuntu jaunty and karmic. > > Segfaults under python 2.6, but oddly works fine when ran under python 2.5. 32 and 64 bit both fail under 2.6, not sure off the top of my head if I was using the nvidia binary graphics driver or not, I don't think I was. > If you can clarify what exactly you did I am willing to try again. I built and installed a deb package from the sid source files like this: dpkg-source -x python-visual_5.11-1.dsc cd python-visual-5.11 dpkg-buildpackage -rfakeroot -b cd .. dpkg -i python-visual_5.11-1_amd64.deb I did not see a place where I could change 2.6 to 2.7 and it was not needed. In my case (using my laptop with ati graphics) it seg faults under python 2.5, runs under 2.6 but fails my little tests. Pretty much the opposite of what you found and no different from what I found by installing 5.12 from source. > As stated by another in that bug report: > > "Please consider raising the importance from medium to high. Not having this package working is a deal breaker in many educational environments." Just trying to move things along. See above. Guenter > > But now that I've typed this whole message, I now see that person's name was "gs", and is probably you :-) > > -----Original Message----- > From: Guenter Schneider [mailto:Gue...@ph...] > Sent: Tuesday, September 15, 2009 8:13 PM > To: vis...@li... > Subject: [Visualpython-users] vpython on ubuntu > > I have struggled to get vpython fully working on ubuntu for a while now. > Here is my summary what I learned. Let me say right away, as far as I > can tell it's not a vpython problem. > > First, unlike others on this list, I have no problems compiling vpython > 5.12. It works using debian Lenny on any computer I have tried. By > 'it works' I mean these simple tests do not result in seg. faults: > > TEST 1: > >>> from visual import * > >>> v = vector('x') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ValueError: Vectors must be constructed from sequences of 2 or 3 float > members. > >>> > > TEST 2: > >>> from visual import * > >>> v=vector(1,2,3) > >>> for i in v: > ... print i > ... > 1.0 > 2.0 > 3.0 > >>> > > On ubuntu 9.04 it works on some computers but not on others. It doesn't > matter if I use 32 bit or 64 bit ubuntu 9.04. > > In fact the same pattern holds true in my tests for the python-visual > package that is distributed with ubuntu 9.04 (which is vpython 3.2.9). > It fails on all computers if a proprietary graphics driver is not > installed. Activating an nvidia proprietary graphics driver results in a > working vpython (as defined above), on system with ati graphics cards I > was not so lucky. I tried 6 different computers, 2 with nvidia graphics > and 4 with ati graphics. > > I got the same result for ubuntu 8.10. It always works with ubuntu 8.04.3. > > I filed a bug report with ubuntu against vpython since I have no idea > what is causing this problem. > > I could not try python-visual on karmic alpha (which 5.11) since that > leads to a seg fault like this > > >>> from visual import * > Segmentation fault > > There is already a bug report for this. > > Guenter > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > > > Tony Risinger > Application Development Specialist > Tel: 507-535-7563 | Fax: 507-292-5747 | Toll Free: 866-241-0639 > > To...@Br... > > http://www.brokerbin.com/ > > CONFIDENTIAL INFORMATION: This electronic mail message and any attached files contain information intended for the exclusive use of the specific individual(s) or entity(s) to whom it is addressed and may contain information that is propriety, privileged or confidential or otherwise exempt from disclosure. If you are not the intended recipient, please notify the sender immediately, by reply electronic mail or by telephone, of any unintended recipients so we may correct our records. Also, delete the original electronic mail and any attachments without making any copies of the electronic mail message or attachments. |
From: Tony R. <To...@br...> - 2009-09-16 04:35:53
|
Yeah I opened that report but I haven't got any feedback yet. I'm not sure what it means, but I took the python-visual 5.11 package from sid, tweaked the package slightly (python version was set to less than 2.6, I changed that to 2.7 so it would install, that's the only change I made) and tried it on ubuntu jaunty and karmic. Segfaults under python 2.6, but oddly works fine when ran under python 2.5. 32 and 64 bit both fail under 2.6, not sure off the top of my head if I was using the nvidia binary graphics driver or not, I don't think I was. As stated by another in that bug report: "Please consider raising the importance from medium to high. Not having this package working is a deal breaker in many educational environments." But now that I've typed this whole message, I now see that person's name was "gs", and is probably you :-) -----Original Message----- From: Guenter Schneider [mailto:Gue...@ph...] Sent: Tuesday, September 15, 2009 8:13 PM To: vis...@li... Subject: [Visualpython-users] vpython on ubuntu I have struggled to get vpython fully working on ubuntu for a while now. Here is my summary what I learned. Let me say right away, as far as I can tell it's not a vpython problem. First, unlike others on this list, I have no problems compiling vpython 5.12. It works using debian Lenny on any computer I have tried. By 'it works' I mean these simple tests do not result in seg. faults: TEST 1: >>> from visual import * >>> v = vector('x') Traceback (most recent call last): File "<stdin>", line 1, in <module> ValueError: Vectors must be constructed from sequences of 2 or 3 float members. >>> TEST 2: >>> from visual import * >>> v=vector(1,2,3) >>> for i in v: ... print i ... 1.0 2.0 3.0 >>> On ubuntu 9.04 it works on some computers but not on others. It doesn't matter if I use 32 bit or 64 bit ubuntu 9.04. In fact the same pattern holds true in my tests for the python-visual package that is distributed with ubuntu 9.04 (which is vpython 3.2.9). It fails on all computers if a proprietary graphics driver is not installed. Activating an nvidia proprietary graphics driver results in a working vpython (as defined above), on system with ati graphics cards I was not so lucky. I tried 6 different computers, 2 with nvidia graphics and 4 with ati graphics. I got the same result for ubuntu 8.10. It always works with ubuntu 8.04.3. I filed a bug report with ubuntu against vpython since I have no idea what is causing this problem. I could not try python-visual on karmic alpha (which 5.11) since that leads to a seg fault like this >>> from visual import * Segmentation fault There is already a bug report for this. Guenter ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Visualpython-users mailing list Vis...@li... https://lists.sourceforge.net/lists/listinfo/visualpython-users Tony Risinger Application Development Specialist Tel: 507-535-7563 | Fax: 507-292-5747 | Toll Free: 866-241-0639 To...@Br... http://www.brokerbin.com/ CONFIDENTIAL INFORMATION: This electronic mail message and any attached files contain information intended for the exclusive use of the specific individual(s) or entity(s) to whom it is addressed and may contain information that is propriety, privileged or confidential or otherwise exempt from disclosure. If you are not the intended recipient, please notify the sender immediately, by reply electronic mail or by telephone, of any unintended recipients so we may correct our records. Also, delete the original electronic mail and any attachments without making any copies of the electronic mail message or attachments. |
From: Guenter S. <Gue...@ph...> - 2009-09-16 02:31:21
|
I have struggled to get vpython fully working on ubuntu for a while now. Here is my summary what I learned. Let me say right away, as far as I can tell it's not a vpython problem. First, unlike others on this list, I have no problems compiling vpython 5.12. It works using debian Lenny on any computer I have tried. By 'it works' I mean these simple tests do not result in seg. faults: TEST 1: >>> from visual import * >>> v = vector('x') Traceback (most recent call last): File "<stdin>", line 1, in <module> ValueError: Vectors must be constructed from sequences of 2 or 3 float members. >>> TEST 2: >>> from visual import * >>> v=vector(1,2,3) >>> for i in v: ... print i ... 1.0 2.0 3.0 >>> On ubuntu 9.04 it works on some computers but not on others. It doesn't matter if I use 32 bit or 64 bit ubuntu 9.04. In fact the same pattern holds true in my tests for the python-visual package that is distributed with ubuntu 9.04 (which is vpython 3.2.9). It fails on all computers if a proprietary graphics driver is not installed. Activating an nvidia proprietary graphics driver results in a working vpython (as defined above), on system with ati graphics cards I was not so lucky. I tried 6 different computers, 2 with nvidia graphics and 4 with ati graphics. I got the same result for ubuntu 8.10. It always works with ubuntu 8.04.3. I filed a bug report with ubuntu against vpython since I have no idea what is causing this problem. I could not try python-visual on karmic alpha (which 5.11) since that leads to a seg fault like this >>> from visual import * Segmentation fault There is already a bug report for this. Guenter |
From: Guenter S. <Gue...@ph...> - 2009-09-16 02:20:29
|
I'll summarize what I learned about installing vpython on ubuntu in a new thread. As for why I believe that exceptions are common to all the examples I presented, a python loop 1 for item in sequence: 2 body is internally equivalent to 1 iter = sequence.__iter__() 2 try: 3 while True: 4 item = iter.next() 5 body 6 except StopIteration: 7 pass Guenter Bruce Sherwood wrote: > I don't understand enough about building on Linux to be sure that it would help, > but it might be worth building according to the instructions in INSTALL.txt, > since that's how I've built Visual and it works. Moreover, the configure stage > will tell you if you're missing certain dependencies. On the other hand, it > seems possible that there's some incompatibility between Visual and 64bit Ubuntu > (I only have access to 32bit Ubuntu). > > You suspect that "whenever vpython raises an exception, python seg. faults", but > in your Example 1 there's no reason why VPython would raise an exception. > > Bruce Sherwood > > Guenter Schneider wrote: >> Thank you for the prompt answers and I am glad it's my setup because >> that should be easy to fix. >> >> There is no typo in the examples. All is cut and paste out of ipython >> sessions. >> >> I should have mentioned I use 64bit Ubuntu. >> I use boost 1.35 (libboost1.35-dev) and python 2.6.2 >> >> I use this script to build and install vpython >> >> #!/bin/bash >> >> SOFTWARE=visual-5.12_release >> ARCHIVE=$SOFTWARE.tar.bz2 >> ARCHIVEDIR="$SOFTWARE" >> BUILDDIR=$SOFTWARE-install >> tar jxvf $ARCHIVE >> mkdir -p $BUILDDIR >> cd $BUILDDIR >> aptitude -y install libboost1.35-dev >> aptitude -y install libsigc++-2.0-dev libgtkmm-2.4-dev libgtkglext1-dev >> libgtkglext1 libgtkglextmm-x11-1.2-0 libgtkglextmm-x11-1.2-dev >> libglademm-2.4-1c2a libglademm-2.4-dev >> ../$ARCHIVEDIR/configure --prefix /usr >> make >> >> #as root >> cd $BUILDDIR >> make install >> echo /usr/lib/python2.6/site-packages >> >> /usr/lib/python2.6/dist-packages/site-packages.pth >> >> If necessary I will setup a clean system from scratch and install >> vpython there, but I'd rather fix it without going this route. >> >> Guenter Schneider >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |