visualpython-users

Re: [Visualpython-users] Errors with new Visual

[Jonathan B. <jbr...@ea...>]

On Tue, 2004-07-27 at 13:44, Jonathan Brandmeyer wrote:
> On Tue, 2004-07-27 at 13:25, Bruce Peterson wrote:
> 
> > Interestingly -- the Remove Programs in the Control panel doesn't remove 
> > Visual.py
> > After cleaning out the Visual directory, I installed Visual 2004-07-22 
> > again (which doesn't have a visual.py) and ran my test program.
> > This time the error message was:
> >   << snip additional trace back into my code>>
> >    File "C:\Python23\TSWork\DDV_GS005.py", line 1510, in show_axis
> >      text=timetext,height=self.seldict['tlabelsize'],box=0,line=0,opacity=0.0)
> >    File "C:\Python23\Lib\site-packages\visual\primitives.py", line 230, in 
> > __init__
> >      process_init_args_from_keyword_dictionary(self, keywords)
> >    File "C:\Python23\Lib\site-packages\visual\primitives.py", line 37, in 
> > process_init_args_from_keyword_dictionary
> >      displayobject.color =  keywords['color']
> > ArgumentError: Python argument types in
> >      None.None(label, vector)
> > did not match C++ signature:
> >      None(visual::Label {lvalue}, boost::python::tuple)
> > 
> 
> 
> This error was generated because you assigned the color of a label
> object to be a vector, when it wants a 3-tuple.
> 
> If this is a serious problem for you, then I can implement a workaround
> that would accept any 3-element sequence to be a color, but I don't
> think it is appropriate to use vectors for specifying a color.  
> 
> In the meantime, you can use the built-in function tuple(sequence) to
> construct a tuple from any sequence (Visual's vectors are sequences), or
> you can use the special member function vector.as_tuple() for a faster

That would be vector.astuple(), with no '_'.

> conversion in performance-sensitive code.

-Jonathan

Re: [Visualpython-users] Errors with new Visual

[Jonathan B. <jbr...@ea...>]

On Tue, 2004-07-27 at 13:25, Bruce Peterson wrote:

> Interestingly -- the Remove Programs in the Control panel doesn't remove 
> Visual.py
> After cleaning out the Visual directory, I installed Visual 2004-07-22 
> again (which doesn't have a visual.py) and ran my test program.
> This time the error message was:
>   << snip additional trace back into my code>>
>    File "C:\Python23\TSWork\DDV_GS005.py", line 1510, in show_axis
>      text=timetext,height=self.seldict['tlabelsize'],box=0,line=0,opacity=0.0)
>    File "C:\Python23\Lib\site-packages\visual\primitives.py", line 230, in 
> __init__
>      process_init_args_from_keyword_dictionary(self, keywords)
>    File "C:\Python23\Lib\site-packages\visual\primitives.py", line 37, in 
> process_init_args_from_keyword_dictionary
>      displayobject.color =  keywords['color']
> ArgumentError: Python argument types in
>      None.None(label, vector)
> did not match C++ signature:
>      None(visual::Label {lvalue}, boost::python::tuple)
> 


This error was generated because you assigned the color of a label
object to be a vector, when it wants a 3-tuple.

If this is a serious problem for you, then I can implement a workaround
that would accept any 3-element sequence to be a color, but I don't
think it is appropriate to use vectors for specifying a color.  

In the meantime, you can use the built-in function tuple(sequence) to
construct a tuple from any sequence (Visual's vectors are sequences), or
you can use the special member function vector.as_tuple() for a faster
conversion in performance-sensitive code.

HTH,
-Jonathan

[Visualpython-users] Errors with new Visual

[Bruce P. <bap...@te...>]

<< snip >>
At 08:37 PM 7/26/2004, you wrote:


>Make sure you remove any existing installations of Visual before
>upgrading.  It appears you have some cruft from an old install.  (note:
>simply removing C:\Python23\Lib\site-packages\visual\visual.py might be
>enough, or there could be other conflicts).
>
>-Jonathan

Interestingly -- the Remove Programs in the Control panel doesn't remove 
Visual.py
After cleaning out the Visual directory, I installed Visual 2004-07-22 
again (which doesn't have a visual.py) and ran my test program.
This time the error message was:
  << snip additional trace back into my code>>
   File "C:\Python23\TSWork\DDV_GS005.py", line 1510, in show_axis
     text=timetext,height=self.seldict['tlabelsize'],box=0,line=0,opacity=0.0)
   File "C:\Python23\Lib\site-packages\visual\primitives.py", line 230, in 
__init__
     process_init_args_from_keyword_dictionary(self, keywords)
   File "C:\Python23\Lib\site-packages\visual\primitives.py", line 37, in 
process_init_args_from_keyword_dictionary
     displayobject.color =  keywords['color']
ArgumentError: Python argument types in
     None.None(label, vector)
did not match C++ signature:
     None(visual::Label {lvalue}, boost::python::tuple)



Bruce Peterson
425 466 7344 

Re: [Visualpython-users] Problem with windows Vpython update

[Jonathan B. <jbr...@ea...>]

On Mon, 2004-07-26 at 15:07, Bruce Peterson wrote:
> >I installed the 2004_07-22 update of VPython. When attempting to run with 
> >Activestate python 2.3.2 (Windows XP) I got the following error:
> 
>      from visual import *
>    File "C:\Python23\Lib\site-packages\visual\__init__.py", line 21, in ?
>      from visual.primitives import arrow, cylinder, cone, sphere, box, 
> ring, label
>    File "C:\Python23\Lib\site-packages\visual\visual.py", line 21, in ?
>      copy_reg.pickle(cvisual.VectorType, lambda v: (vector, tuple(v)), vector)
> AttributeError: 'module' object has no attribute 'VectorType'
> 
> Updating Python to 2.3.4 didn't help.  It looks like declaration is missing 
> from the pickle library.
> 
> 
> Bruce Peterson
> 425 466 7344

Make sure you remove any existing installations of Visual before
upgrading.  It appears you have some cruft from an old install.  (note:
simply removing C:\Python23\Lib\site-packages\visual\visual.py might be
enough, or there could be other conflicts).

-Jonathan

[Visualpython-users] Problem with windows Vpython update

[Bruce P. <bap...@te...>]

>I installed the 2004_07-22 update of VPython. When attempting to run with 
>Activestate python 2.3.2 (Windows XP) I got the following error:

     from visual import *
   File "C:\Python23\Lib\site-packages\visual\__init__.py", line 21, in ?
     from visual.primitives import arrow, cylinder, cone, sphere, box, 
ring, label
   File "C:\Python23\Lib\site-packages\visual\visual.py", line 21, in ?
     copy_reg.pickle(cvisual.VectorType, lambda v: (vector, tuple(v)), vector)
AttributeError: 'module' object has no attribute 'VectorType'

Updating Python to 2.3.4 didn't help.  It looks like declaration is missing 
from the pickle library.


Bruce Peterson
425 466 7344

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Martin G. <mar...@co...>]

I've upgraded the nvidia drivers/libs to the version in unstable,
and recompiled visual with the patched gldevice.cpp (I didn't
try going back to the original version), and am happy to report
that all seems well so far.  Many thanks!  Perhaps a note
to the effect that the linux nvidia drivers version 1.0.5336 do
not work with visual, upgrade to 1.0.6106, should be added
to the linux download page.

Love the new helix!   --Marty

On Friday 23 July 2004 08:49 pm, Jonathan Brandmeyer wrote:
> On Fri, 2004-07-23 at 18:42, Martin Gelfand wrote:
> > In answer to the questions from J.B. ...
> > * I am using an nvidia card with the nvidia drivers
> > * The output of everything after import stars...
>
> [snipped]
>
> Thanks for the info.
>
> First, apply the attached patch to cvisual/gldevice.cpp [1], rebuild
> vpython, and see if that fixes the problem.
> If it does, please upgrade to the latest nvidia-glx and nvidia-kernel
> packages in unstable, and rebuild vpython from the unpatched source, to
> see if upgrading the nvidia drivers fixes the problem.
>
> If applying the patch corrects the crash and upgrading the driver does
> not, please run glxinfo and send me the output.
>
> Thanks,
> -Jonathan
>

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Jonathan B. <jbr...@ea...>]

On Sun, 2004-07-25 at 15:12, Martin Gelfand wrote:
> I've resolved the problem with the old visual.  On rebuilding, there
> was an error that libGL.so did not exist.  It did, but it was a link
> to libGL.so.1.2, which did not exist.  However, libGL.so.1 did exist,
> as a link to libGL.so.1.0.5336.  Pointing libGL.so to libGL.so.1 allowed
> visual to build, and it runs fine again.
> 
> Does that constitute a bug in xlibmesa-gl-dev (the package which
> appears to own /usr/lib/libGL.so)?

I think that the symlink from libGL.so to the correct file is provided
by nvidia-glx-dev.

> Onward to visual-3.0...  And thanks, Jonathan, for your assistance.

You're welcome,
-Jonathan

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Martin G. <mar...@co...>]

I've resolved the problem with the old visual.  On rebuilding, there
was an error that libGL.so did not exist.  It did, but it was a link
to libGL.so.1.2, which did not exist.  However, libGL.so.1 did exist,
as a link to libGL.so.1.0.5336.  Pointing libGL.so to libGL.so.1 allowed
visual to build, and it runs fine again.

Does that constitute a bug in xlibmesa-gl-dev (the package which
appears to own /usr/lib/libGL.so)?

Onward to visual-3.0...  And thanks, Jonathan, for your assistance.


> On Friday 23 July 2004 03:23 pm, Jonathan Brandmeyer wrote:
> > On Fri, 2004-07-23 at 15:49, Martin Gelfand wrote:
> > > What's worse, my old visual setup (python2.2, visual-2.1.9) no longer
> > > works:
> > > Python 2.2.3+ (#1, Jun 20 2004, 13:32:48)
> > > [GCC 3.3.4 (Debian)] on linux2
> > > Type "help", "copyright", "credits" or "license" for more information.
> > >
> > > >>> import visual
> > >
> > > Visual-2003-10-05
> > > Traceback (most recent call last):
> > >   File "<stdin>", line 1, in ?
> > >   File "/usr/local/lib/python2.2/site-packages/visual/__init__.py",
> > > line 17, in ?
> > >     import cvisual
> > > ImportError: /usr/local/lib/python2.2/site-packages/cvisualmodule.so:
> > > undefined symbol: __pure_virtual
> > >
> > > I don't see how this could be the fault of installing the new
> > > visual--could it have come about due to an upgrade of python2.2 since I
> > > built that version of visual?
> >
> > I don't know for certain what this could be.  The only place that I can
> > find this symbol on my system is in libgcc.a from GCC 2.95.  Try
> > rebuilding VPython 2.1.9 with the current compiler.  (you will have to
> > specify PYTHON=python2.2 to build against Python 2.2 since `python` is
> > 2.3).
> >

Re: [Visualpython-users] vpython update problems on linux

[Jonathan B. <jbr...@ea...>]

On Sat, 2004-07-24 at 15:20, francois schnell wrote:
> Hello all,
> 
> I had the linux version (http://vpython.org/linux_download.html)  It
> worked nicely since 2 weeks ago on my suse 9.0.

SUSE 9.0 - Uh, oh.  (see below)


> Then I saw  that the updated files were available there  :-) :
> http://vpython.org/all_download.html :
> 
> Doc-2004-07-22.zip Documentation for Visual
> Demos-2004-07-22.zip VPython demo programs
> Visual-2004-07-22.zip Visual module (*.py files needed by VPython)
> 
> I unziped them and crushed the old ones (without doing a full install
> again):
> 

That doesn't work for the Visual-2004-07-22.zip package, and is the
source of the ImportError below.  Part of VPython is written in C++, and
part of it in Python.  The two must come from the same release of
VPython, ie, you must perform a full install.

> Now, when I run vpython I have the following problems:
> 
> 
> 
> >>> 
> Visual 2004-07-22
> 
> Traceback (most recent call last):
>   File "/usr/lib/python2.3/site-packages/visual/demos/gyro2.py", line
> 1, in -toplevel-
>     from visual import *
>   File "/usr/lib/python2.3/site-packages/visual/__init__.py", line 19,
> in -toplevel-
>     from cvisual import vector, mag, mag2, norm, cross, rotate, comp,
> proj, diff_angle, rate
> ImportError: cannot import name comp
> 
> Do you know what I did wrong again this time ....   :-(

You have version mismatch between the old cvisualmodule.so and the new
visual/*.py files.


> I tried the new full install but when I do "make" I have this:
> Making all in cvisual
> 
> make[1]: Entering directory
> `/home/schnell/Desktop/vpython/visual-3.0/cvisual'
> 
> Compiling arrow.cpp ...
> 
> make[1]: *** [arrow.lo] Erreur 1
> 


Suse 9.0 is known to have shipped with a broken compiler.  You must
install GCC and Boost from source to correct the problems with your
broken compiler. 
http://www.vpython.org/Building%20VPython%20on%20SuSE.html

Also, since SUSE installs GNOME into /opt/gnome, you will need to set
the CPPFLAGS environment variable to include "-I/opt/gnome/include" when
running Visual's configure script.

-Jonathan

[Visualpython-users] vpython update problems on linux

[francois s. <fra...@fr...>]

Hello all,

I had the linux version (http://vpython.org/linux_download.html)  It=20
worked nicely since 2 weeks ago on my suse 9.0.

Then I saw  that the updated files were available there  :-) :
http://vpython.org/all_download.html :

Doc-2004-07-22.zip <http://vpython.org/download/Doc-2004-07-22.zip>=20
Documentation for Visual
Demos-2004-07-22.zip <http://vpython.org/download/Demos-2004-07-22.zip>=20
VPython demo programs
Visual-2004-07-22.zip=20
<http://vpython.org/download/Visual-2004-07-22.zip> Visual module (*.py=20
files needed by VPython)

I unziped them and crushed the old ones (without doing a full install=20
again):

linux:/usr/lib/python2.3/site-packages/visual # ls -l
total 509

drwxrwxrwx 5 root root 992 2004-07-24 20:28 .
drwxr-xr-x 18 root root 3360 2004-07-18 12:57 ..
-rwxrwxrwx 1 root root 18029 2004-07-24 20:28 controls.py
-rwxrwxrwx 1 root root 21256 2004-07-24 20:28 controls.pyc
-rwxrwxrwx 1 root root 21455 2004-07-18 12:57 controls.pyo
-rwxrwxrwx 1 root root 283 2004-07-24 20:28 crayola.py
-rwxrwxrwx 1 schnell users 1009 2004-07-24 20:28 crayola.pyc
-rwxrwxrwx 1 root root 1009 2004-07-18 12:57 crayola.pyo
drwxrwxrwx 2 root root 1064 2004-07-24 19:49 demos
-rwxrwxrwx 1 root root 42972 2004-07-24 19:40 Demos-2004-07-22.zip
-rwxrwxrwx 1 root root 123328 2004-07-24 19:40 Doc-2004-07-22.zip
drwxrwxrwx 4 root root 168 2004-07-24 19:55 docs
-rwxrwxrwx 1 root root 856 2004-07-24 20:28 factorial.py
-rwxrwxrwx 1 root root 1234 2004-07-18 12:57 factorial.pyc
-rwxrwxrwx 1 root root 1234 2004-07-18 12:57 factorial.pyo
-rwxrwxrwx 1 root root 26322 2004-07-24 20:28 graph.py
-rwxrwxrwx 1 root root 24411 2004-07-18 12:57 graph.pyc
-rwxrwxrwx 1 root root 24411 2004-07-18 12:57 graph.pyo
-rwxrwxrwx 1 root root 1540 2004-07-24 20:28 __init__.py
-rwxrwxrwx 1 schnell users 2174 2004-07-24 20:28 __init__.pyc
-rwxrwxrwx 1 root root 4287 2004-07-18 12:57 __init__.pyo
drwxrwxrwx 3 root root 80 2004-07-24 19:41 Lib
-rwxrwxrwx 1 root root 399 2004-07-24 20:28 macevent.py
-rwxrwxrwx 1 root root 830 2004-07-18 12:57 macevent.pyc
-rwxrwxrwx 1 root root 830 2004-07-18 12:57 macevent.pyo
-rwxrwxrwx 1 schnell users 12080 2004-07-24 20:28 primitives.py
-rwxrwxrwx 1 schnell users 21219 2004-07-24 20:28 primitives.pyc
-rwxrwxrwx 1 root root 19101 2004-07-24 20:28 text.py
-rwxrwxrwx 1 root root 16816 2004-07-24 20:28 text.pyc
-rwxrwxrwx 1 root root 16867 2004-07-18 12:57 text.pyo
-rwxrwxrwx 1 schnell users 815 2004-07-24 20:28 ui.py
-rwxrwxrwx 1 schnell users 1162 2004-07-24 20:28 ui.pyc
-rwxrwxrwx 1 root root 36502 2004-07-24 19:40 Visual-2004-07-22.zip




Now, when I run vpython I have the following problems:



> >>
Visual 2004-07-22

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/visual/demos/gyro2.py", line 1,=20
in -toplevel-
    from visual import *
  File "/usr/lib/python2.3/site-packages/visual/__init__.py", line 19,=20
in -toplevel-
    from cvisual import vector, mag, mag2, norm, cross, rotate, comp,=20
proj, diff_angle, rate
ImportError: cannot import name comp

Do you know what I did wrong again this time ....   :-(

I tried the new full install but when I do "make" I have this:

schnell@linux:~/Desktop/vpython/visual-3.0> make

Making all in visual

make[1]: Entering directory=20
`/home/schnell/Desktop/vpython/visual-3.0/visual'

make[1]: Rien =E0 faire pour =AB all =BB.

make[1]: Leaving directory `/home/schnell/Desktop/vpython/visual-3.0/visu=
al'

Making all in cvisual

make[1]: Entering directory=20
`/home/schnell/Desktop/vpython/visual-3.0/cvisual'

Compiling arrow.cpp ...

make[1]: *** [arrow.lo] Erreur 1

make[1]: Leaving directory=20
`/home/schnell/Desktop/vpython/visual-3.0/cvisual'

make: *** [all-recursive] Erreur 1

schnell@linux:~/Desktop/vpython/visual-3.0> PYTHON=3D/usr/bin/python make

Making all in visual

make[1]: Entering directory=20
`/home/schnell/Desktop/vpython/visual-3.0/visual'

make[1]: Rien =E0 faire pour =AB all =BB.

make[1]: Leaving directory `/home/schnell/Desktop/vpython/visual-3.0/visu=
al'

Making all in cvisual

make[1]: Entering directory=20
`/home/schnell/Desktop/vpython/visual-3.0/cvisual'

Compiling arrow.cpp ...

make[1]: *** [arrow.lo] Erreur 1

make[1]: Leaving directory=20
`/home/schnell/Desktop/vpython/visual-3.0/cvisual'

make: *** [all-recursive] Erreur 1



Thhank's for any help  :-)

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Jonathan B. <jbr...@ea...>]

On Fri, 2004-07-23 at 22:49, Jonathan Brandmeyer wrote:
> On Fri, 2004-07-23 at 18:42, Martin Gelfand wrote:
> > In answer to the questions from J.B. ...
> > * I am using an nvidia card with the nvidia drivers
> > * The output of everything after import stars...
> 
> [snipped]
> 
> Thanks for the info.
> 
> First, apply the attached patch to cvisual/gldevice.cpp [1], rebuild
> vpython, and see if that fixes the problem.
> If it does, please upgrade to the latest nvidia-glx and nvidia-kernel

Make that nvidia-glx-dev rather than nvidia-glx.

> packages in unstable, and rebuild vpython from the unpatched source, to
> see if upgrading the nvidia drivers fixes the problem.
> 

-Jonathan

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Jonathan B. <jbr...@ea...>]

On Fri, 2004-07-23 at 18:42, Martin Gelfand wrote:
> In answer to the questions from J.B. ...
> * I am using an nvidia card with the nvidia drivers
> * The output of everything after import stars...

[snipped]

Thanks for the info.

First, apply the attached patch to cvisual/gldevice.cpp [1], rebuild
vpython, and see if that fixes the problem.
If it does, please upgrade to the latest nvidia-glx and nvidia-kernel
packages in unstable, and rebuild vpython from the unpatched source, to
see if upgrading the nvidia drivers fixes the problem.

If applying the patch corrects the crash and upgrading the driver does
not, please run glxinfo and send me the output.

Thanks,
-Jonathan


[1] Save the attached file as cvisual/gldevice.cpp.diff (in the visual
source tree)
cd into cvisual
run `patch < gldevice.cpp.diff`

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Martin G. <mar...@co...>]

In answer to the questions from J.B. ...
* I am using an nvidia card with the nvidia drivers
* The output of everything after import stars...

>>> import stars

Right button drag to rotate view.
Left button drag up or down to move in or out.

[New Thread 32769 (LWP 10189)]
[New Thread 16386 (LWP 10190)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16386 (LWP 10190)]
0x40118c0f in strlen () from /lib/libc.so.6
(gdb) bt
#0  0x40118c0f in strlen () from /lib/libc.so.6
#1  0x40a90464 in visual::GLDevice::render_control ()
   from /usr/local/lib/python2.3/site-packages/cvisualmodule.so
#2  0x40a9187b in visual::GLDevice::callback ()
   from /usr/local/lib/python2.3/site-packages/cvisualmodule.so
#3  0x40e98ec4 in g_main_set_poll_func () from /usr/lib/libglib-1.2.so.0
#4  0x40e9803d in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#5  0x40e984f4 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#6  0x40e98724 in g_main_run () from /usr/lib/libglib-1.2.so.0
#7  0x40c4c25f in gtk_main () from /usr/lib/libgtk-1.2.so.0
#8  0x40aca12b in visual::mainloop ()
   from /usr/local/lib/python2.3/site-packages/cvisualmodule.so
#9  0x4002ee51 in pthread_start_thread () from /lib/libpthread.so.0
#10 0x4002eecf in pthread_start_thread_event () from /lib/libpthread.so.0
#11 0x4017a69a in clone () from /lib/libc.so.6

On Friday 23 July 2004 03:23 pm, Jonathan Brandmeyer wrote:
> On Fri, 2004-07-23 at 15:49, Martin Gelfand wrote:
> > I am running Debian testing, but got boost-python-dev and dependencies
> > from unstable (since only unstable has boost 1.31 at this time).
> >
> > Compilation of visual-3.0 seemed to go fine.  I used
> > PYTHON=/usr/bin/python ./configure --prefix=/usr/local
> > (/usr/bin/python is a link to python2.3, and I want all locally built
> > software in /usr/local)
>
> /usr/local is configure's default prefix, and so long as /usr/bin/python
> is the first Python named 'python' in your PATH, that is the default as
> well.
>
> > Importing visual in a python2.3 shell goes OK, but I get a segfault on
> > trying to do anything that generates a display on-screen.  I see a
> > display window appear, then immediately close.  Simply instantiating a
> > display (e.g. firstdisplay=visual.display()) does not throw a segfault.
>
> visual.display has "initialize on first use" semantics, and merely
> instantiating one isn't enough to constitute 'use'; you have to also
> instantiate a rendered object.
>
> I'm using visual 3.0 on Debian Sid right now, without any problems.  Can
> you please run the following to get a backtrace?:
>
> gdb python
> [displays some stuff and gives you the (gdb) prompt]
> (gdb) run
> [displays more stuff and gives you the python prompt]
>
> >>> from visual import *
> >>> import sys
> >>> sys.path.append(
>
> ...   "/usr/local/lib/python2.3/site-packages/visual/demos")
> ...
>
> >>> import stars
>
> [ This will attempt to run the stock "stars" demo program ]
> [ When (if) it crashes, control will return to gdb with the (gdb)
> prompt.]
> (gdb) bt
>
> Please send me the output of the last command.
>
> Also, to partially rule out general OpenGL problems, please see if
> glxgears runs.
>
> Are you by chance using the R200 DRI driver?
>
> > What's worse, my old visual setup (python2.2, visual-2.1.9) no longer
> > works:
> > Python 2.2.3+ (#1, Jun 20 2004, 13:32:48)
> > [GCC 3.3.4 (Debian)] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> >
> > >>> import visual
> >
> > Visual-2003-10-05
> > Traceback (most recent call last):
> >   File "<stdin>", line 1, in ?
> >   File "/usr/local/lib/python2.2/site-packages/visual/__init__.py", line
> > 17, in ?
> >     import cvisual
> > ImportError: /usr/local/lib/python2.2/site-packages/cvisualmodule.so:
> > undefined symbol: __pure_virtual
> >
> > I don't see how this could be the fault of installing the new
> > visual--could it have come about due to an upgrade of python2.2 since I
> > built that version of visual?
>
> I don't know for certain what this could be.  The only place that I can
> find this symbol on my system is in libgcc.a from GCC 2.95.  Try
> rebuilding VPython 2.1.9 with the current compiler.  (you will have to
> specify PYTHON=python2.2 to build against Python 2.2 since `python` is
> 2.3).
>
> -Jonathan
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

-- 
Martin Gelfand

Associate Professor.............Phone: 970 491 5263
Department of Physics.............Fax: 970 491 7947
Colorado State University.......Email: ge...@la...
Fort Collins CO 80523-1875

[Visualpython-users] active stereo

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

The latest VPython on Windows has an intermittent problem with 'active' 
stereo (shutter glasses). Sometimes you get a black window, then 
rerunning the program often makes the display work properly. The only 
workaround at the moment is to revert to an earlier version.

Bruce Sherwood

Re: [Visualpython-users] Release: VPython 2.9.7

[Joe H. <hea...@ct...>]

On Jul 23, 2004, at 4:42 PM, Jonathan Brandmeyer wrote:

> I used several options to GCC's configure program to ensure that the 
> one
> being built would not interfere with the stock compiler.
> - It is installed into /usr/local.
> - All of the generated programs have the full GCC version number
> appended to their name (eg, gcc-3.3.4 rather than gcc).
> - The compiler's libraries are installed into version-specific
> directories, so the system compiler will not pick up the new GCC's libs
> by accident.

Great work!

>> The build process seemed to bring my
>> entire system to a grinding halt (quite literally) during compilation
>> of the vector array stuff. I've no idea why.
>
> How much memory do you have?  The system might have started swapping 
> out
> to disk.  Actually, now that I think about it, I probably should remove
> '-j2' from the make commands in that script.  That option causes make 
> to
> run two jobs at once, and a few of the source files require ~200 MB of
> RAM to compile - my development machine is a dualie.

I used my iBook G4 with 256MB RAM. I was running some other things in 
the background, including a real time Earth illumination program that 
uses the entire desktop (EarthDesk...<http://www.timepalette.com>) and 
Mail. Window moves took like 15 seconds or longer. Things got a little 
faster after shutting down everything except the build process, but it 
still just sat there forever so I just restarted and all was fine. I 
will attempt to do all this on my iMac this weekend.

I've now got a problem with Fink. It seems that some of the packages in 
unstable don't want to update even though I've enabled the unstable 
tree and there are more recent versions available. I'll deal with that 
on the fink-users list though.

> Is there a way to determine how many processors are installed on a
> PowerMac from the command line?

No idea. I've not played with a PowerMac. I have my heart set on one of 
the upcoming iMacs, provided I survive this current onslaught of 
medical bills.

Thank you for your hard work!

Cheers,
Joe Heafner -- Astronomy/Physics Instructor (by some definitions)

Re: [Visualpython-users] no-go with new (and old!) visual on linux

[Jonathan B. <jbr...@ea...>]

On Fri, 2004-07-23 at 15:49, Martin Gelfand wrote:
> I am running Debian testing, but got boost-python-dev and dependencies
> from unstable (since only unstable has boost 1.31 at this time).
> 
> Compilation of visual-3.0 seemed to go fine.  I used
> PYTHON=/usr/bin/python ./configure --prefix=/usr/local
> (/usr/bin/python is a link to python2.3, and I want all locally built
> software in /usr/local)

/usr/local is configure's default prefix, and so long as /usr/bin/python
is the first Python named 'python' in your PATH, that is the default as
well.

> Importing visual in a python2.3 shell goes OK, but I get a segfault on
> trying to do anything that generates a display on-screen.  I see a display 
> window appear, then immediately close.  Simply instantiating a display
> (e.g. firstdisplay=visual.display()) does not throw a segfault.

visual.display has "initialize on first use" semantics, and merely
instantiating one isn't enough to constitute 'use'; you have to also
instantiate a rendered object.

I'm using visual 3.0 on Debian Sid right now, without any problems.  Can
you please run the following to get a backtrace?:

gdb python
[displays some stuff and gives you the (gdb) prompt]
(gdb) run
[displays more stuff and gives you the python prompt]
>>> from visual import *
>>> import sys
>>> sys.path.append( 
...   "/usr/local/lib/python2.3/site-packages/visual/demos")
... 
>>> import stars
[ This will attempt to run the stock "stars" demo program ]
[ When (if) it crashes, control will return to gdb with the (gdb)
prompt.]
(gdb) bt

Please send me the output of the last command.

Also, to partially rule out general OpenGL problems, please see if
glxgears runs.

Are you by chance using the R200 DRI driver?

> What's worse, my old visual setup (python2.2, visual-2.1.9) no longer
> works:  
> Python 2.2.3+ (#1, Jun 20 2004, 13:32:48)
> [GCC 3.3.4 (Debian)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import visual
> Visual-2003-10-05
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/local/lib/python2.2/site-packages/visual/__init__.py", line 17, 
> in ?
>     import cvisual
> ImportError: /usr/local/lib/python2.2/site-packages/cvisualmodule.so: 
> undefined symbol: __pure_virtual
> 
> I don't see how this could be the fault of installing the new visual--could
> it have come about due to an upgrade of python2.2 since I built that
> version of visual?

I don't know for certain what this could be.  The only place that I can
find this symbol on my system is in libgcc.a from GCC 2.95.  Try
rebuilding VPython 2.1.9 with the current compiler.  (you will have to
specify PYTHON=python2.2 to build against Python 2.2 since `python` is
2.3).

-Jonathan

Re: [Visualpython-users] Release: VPython 2.9.7

[Jonathan B. <jbr...@ea...>]

On Fri, 2004-07-23 at 16:08, Joe Heafner wrote:
> I am very pleased to report that I was able to build Visual and VPython 
> from the latest source on Mac OS 10.3.4 with no major problems. 

Excellent!

> I used 
> the mkdist_osx.sh script for the entire process. I now have an extra 
> copy of gcc on my system, but it doesn't seem to interfere with 
> anything as far as I can tell. 

I used several options to GCC's configure program to ensure that the one
being built would not interfere with the stock compiler.
- It is installed into /usr/local.
- All of the generated programs have the full GCC version number
appended to their name (eg, gcc-3.3.4 rather than gcc).
- The compiler's libraries are installed into version-specific
directories, so the system compiler will not pick up the new GCC's libs
by accident.

> The build process seemed to bring my 
> entire system to a grinding halt (quite literally) during compilation 
> of the vector array stuff. I've no idea why. 

How much memory do you have?  The system might have started swapping out
to disk.  Actually, now that I think about it, I probably should remove
'-j2' from the make commands in that script.  That option causes make to
run two jobs at once, and a few of the source files require ~200 MB of
RAM to compile - my development machine is a dualie.

Is there a way to determine how many processors are installed on a
PowerMac from the command line?

> I shut down and restarted 
> and reran the script and all worked just fine. It appears that my 
> previous VPython installation was completely overwritten, which is what 
> I would have expected.
> 
> The help facility doesn't work within IDLE, but I think I have an old 
> email somewhere explaining how to fix that. I note that VPython windows 
> seem "snappier" and more responsive than in the version I was using. 
> The new crystal.py demo is simply amazing. I've not yet tried a program 
> with a graph to see if those issues have been cleared up, but I'll try 
> tonight or tomorrow.

The only visible issue with graphs may be a bit of a stutter on startup.

Thanks for the feedback,
-Jonathan

Re: [Visualpython-users] Release: VPython 2.9.7

[Joe H. <hea...@ct...>]

I am very pleased to report that I was able to build Visual and VPython 
from the latest source on Mac OS 10.3.4 with no major problems. I used 
the mkdist_osx.sh script for the entire process. I now have an extra 
copy of gcc on my system, but it doesn't seem to interfere with 
anything as far as I can tell. The build process seemed to bring my 
entire system to a grinding halt (quite literally) during compilation 
of the vector array stuff. I've no idea why. I shut down and restarted 
and reran the script and all worked just fine. It appears that my 
previous VPython installation was completely overwritten, which is what 
I would have expected.

The help facility doesn't work within IDLE, but I think I have an old 
email somewhere explaining how to fix that. I note that VPython windows 
seem "snappier" and more responsive than in the version I was using. 
The new crystal.py demo is simply amazing. I've not yet tried a program 
with a graph to see if those issues have been cleared up, but I'll try 
tonight or tomorrow.

Cheers,
Joe Heafner -- Astronomy/Physics Instructor (by some definitions)

[Visualpython-users] no-go with new (and old!) visual on linux

[Martin G. <mar...@co...>]

I am running Debian testing, but got boost-python-dev and dependencies
from unstable (since only unstable has boost 1.31 at this time).

Compilation of visual-3.0 seemed to go fine.  I used
PYTHON=/usr/bin/python ./configure --prefix=/usr/local
(/usr/bin/python is a link to python2.3, and I want all locally built
software in /usr/local)

Importing visual in a python2.3 shell goes OK, but I get a segfault on
trying to do anything that generates a display on-screen.  I see a display 
window appear, then immediately close.  Simply instantiating a display
(e.g. firstdisplay=visual.display()) does not throw a segfault.

What's worse, my old visual setup (python2.2, visual-2.1.9) no longer
works:  
Python 2.2.3+ (#1, Jun 20 2004, 13:32:48)
[GCC 3.3.4 (Debian)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import visual
Visual-2003-10-05
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/local/lib/python2.2/site-packages/visual/__init__.py", line 17, 
in ?
    import cvisual
ImportError: /usr/local/lib/python2.2/site-packages/cvisualmodule.so: 
undefined symbol: __pure_virtual

I don't see how this could be the fault of installing the new visual--could
it have come about due to an upgrade of python2.2 since I built that
version of visual?

Thanks for your attention.

-- 
Martin Gelfand

Associate Professor.............Phone: 970 491 5263
Department of Physics.............Fax: 970 491 7947
Colorado State University.......Email: ge...@la...
Fort Collins CO 80523-1875

[Visualpython-users] new vector functions

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

I forgot to mention two new vector functions that Jonathan Brandmeyer 
introduced into the new Boost-based VPython:

There are two new functions to use with vectors: vec1.diff_angle(vec2) 
returns the angle (in radians) between vectors vec1 and vec2. You can 
convert a vector to a tuple by tuple(vec1) or by the much faster option 
vec1.as_tuple().

Bruce

P.S. The "Recent developments" section of http://vpython.org contains a 
log of changes, so you can always look there to see what's new.

[Visualpython-users] update

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

At http://vpython.org the Windows and Linux installer downloads have 
been updated to contain the new Boost-based VPython created by Jonathan 
Brandmeyer. Some minor corrections were made to the installers found at 
sourceforge.net.

Congratulations, Jonathan! This is a major step forward. There is a new 
built-in object, helix, and it is used in a new, very fast version of 
the demo program crystal.py. There is a new __copy()__ routine for 
copying objects; it replaces the old __members__ attribute.

And wait till you see what Jonathan has in store for you next....

Bruce Sherwood

[Visualpython-users] New __copy__() function for displayable objects

[Jonathan B. <jbr...@ea...>]

For all displayable objects in visual, object.__copy__() returns an
identical copy of that object, which is displayed immediately.  Without
any arguments, this results in creating a second object in the exact
same position as the first and may not be quite what you want.  So, the
__copy__() member function also takes a list of keyword=value argument
pairs which are applied to the new object before making it visible.  So,
for example, to clone an object from one display to another, you would
execute:
new_object = old_object.__copy__( display=new_display)

Restriction:  If the original object is within a frame, and the new
object is on a different display, you must supply both a new display and
a new frame for the new object (the new frame may be None).  This is due
to the restriction that an object may not be located within a reference
frame on a separate display.

Cloning the 'universe' within one display to another, in the case when
some objects are within frames can be done with the following algorithm
(sent as attachment to keep formatting):

-Jonathan

Re: [Visualpython-users] demos ERROR "TypeError: Expecting an object of type NDArray"

[Jonathan B. <jbr...@ea...>]

On Thu, 2004-07-22 at 12:03, Jonathan Brandmeyer wrote:
> On Thu, 2004-07-22 at 10:32, Kazuhiko Uebayashi wrote:
> > Hi,
> > 
> > I'm trying to use "visual-2.9.6.tar.gz"
> >  on Debian i686 GNU/Linux (testing+part of unstable)
> > 
> > Almost all demos(python2.3/site-packages/visual/demos) says
> >     "TypeError: Expecting an object of type NDArray; \
> >                    got an object of type array instead"
> 
> You can work around this bug by removing the python2.3-numarray package.
> 
> A fix for visual will be out shortly.
> 

In case it wasn't clear in the release notes, fixing this problem is
what I meant about "cooperates with numarray".

-Jonathan

[Visualpython-users] Release: VPython 2.9.7

[Jonathan B. <jbr...@ea...>]

This release is expected to be the last beta before releasing VPython
3.0 from this series.

All renderable objects contain a new member function, __copy__(), which
produces a duplicate of the old object after applying a user-defined set
of keyword=value argument pairs.

Some internal changes have been made to produce a smaller extension
module.

Visual cooperates with numarray when it is installed.  Numeric is still
required, but both Numeric and numarray may be installed at the same
time.

The build scripts for OSX have been updated.  The source tree contains a
file, mkdist_osx.sh, that will download, build, and install GCC and
Boost.Python from source.  Run the script from its own directory.  You
must have fink and the fink packages python23, numeric-py23, gtkglarea,
pkgconfig, and wget installed to use the script.


Enjoy,
Jonathan Brandmeyer

Re: [Visualpython-users] demos ERROR "TypeError: Expecting an object of type NDArray"

[Jonathan B. <jbr...@ea...>]

On Thu, 2004-07-22 at 10:32, Kazuhiko Uebayashi wrote:
> Hi,
> 
> I'm trying to use "visual-2.9.6.tar.gz"
>  on Debian i686 GNU/Linux (testing+part of unstable)
> 
> Almost all demos(python2.3/site-packages/visual/demos) says
>     "TypeError: Expecting an object of type NDArray; \
>                    got an object of type array instead"

You can work around this bug by removing the python2.3-numarray package.

A fix for visual will be out shortly.

HTH,
-Jonathan