Menu
▾
▴
visualpython-users
|
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: 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 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: 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: 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: 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: 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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X