Menu
▾
▴
visualpython-users
|
From: Gary P. <gar...@gm...> - 2010-02-15 16:45:10
|
I installed VPython on a new WinXP machine. First I installed python, then visual, and all was good. Then I went about and installed the other stuff I use ... numpy, scipy, matplotlib ... And VPython crashed python at "import visual" Then I discovered that the VPython installer installs numpy 1.4, but the latest version on numpy.scipy.org is numpy 1.3. So I had unknowingly downgraded numpy. So I uninstalled numpy and visual (and python for good measure) and reinstalled, and it works again. Is it possible (or already known) that visual does not work with numpy 1.3, the current release? I'm hesitant to try it myself. Everything is working now, but I was surprised, and I thought I might document this potential gotcha. -gary |
|
From: Bruce S. <Bru...@nc...> - 2010-02-15 17:05:17
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> I would guess (without actually trying it) that yes, Visual would surely work with numpy 1.3 if (but only if) Visual had been compiled with numpy 1.3 present. You make me realize that I've been too casual in what numpy I install before building on Windows. I've always just used the most up to date version of numpy, without checking to see what version of numpy is being used by scipy. Of course there may be yet another major application that wants even a different numpy, but surely scipy is the most likely accompaniment to Visual.<br> <br> Should I rebuild the Windows installer using numpy 1.3?<br> <br> Bruce Sherwood<br> <br> Gary Pajer wrote: <blockquote cite="mid:88f...@ma..." type="cite">I installed VPython on a new WinXP machine. First I installed python, then visual, and all was good.<br> <br> Then I went about and installed the other stuff I use ... numpy, scipy, matplotlib ...<br> <br> And VPython crashed python at "import visual"<br> <br> Then I discovered that the VPython installer installs numpy 1.4, but the latest version on <a moz-do-not-send="true" href="http://numpy.scipy.org">numpy.scipy.org</a> is numpy 1.3. So I had unknowingly downgraded numpy. So I uninstalled numpy and visual (and python for good measure) and reinstalled, and it works again. <br> <br> Is it possible (or already known) that visual does not work with numpy 1.3, the current release? I'm hesitant to try it myself. Everything is working now, but I was surprised, and I thought I might document this potential gotcha.<br> <br> -gary<br> <pre wrap=""> <hr size="4" width="90%"> ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/solaris-dev2dev">http://p.sf.net/sfu/solaris-dev2dev</a></pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ Visualpython-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Vis...@li...">Vis...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/visualpython-users">https://lists.sourceforge.net/lists/listinfo/visualpython-users</a> </pre> </blockquote> </body> </html> |
|
From: Gary P. <gar...@gm...> - 2010-02-15 20:13:51
|
We should probably confirm that 1.3 does break visual before proceeding. I'm surprised that a change from 1.3 -> 1.4 would cause breakage... the API is supposed to be the same. But wait ... I now recall that there is a discussion going on about numpy 1.4 ... evidently it actually breaks the ABI, the application binary interface. There have been over 200 posts on the subject on the numpy discussion list. The break comes in date/time support, so I wouldn't think it would affect visual. I glanced at some of the posts, and they talk as if 1.4 has been released, but I can't find it. Maybe they've withdrawn it. On the one hand, this will bite only people who install the current numpy after installing the current visual *and* are on Windows *and* are novice enough not to figure out how to fix their problem. Most people who install numpy independently from visual will probably be able to figure things out as I did. On the other hand, you eliminate even that small set of people by recompiling. That set might have zero people in it. But to be entirely neat and clean, one would not want visual to break if one installs the current numpy. By the way, AFAICT, the current version of numpy is 1.3. ... if anyone sees something I've missed, and the current version is indeed 1.4, please let me know. Overall, I'd say it's not critical, but some day when you have time it would be better to recompile. But someone in addition to me should try to install the latest numpy 1.3 on top of the latest visual on WinXP and see if it breaks. Just in case the problem is idiosyncratic to me. -g On Mon, Feb 15, 2010 at 12:04 PM, Bruce Sherwood <Bru...@nc...>wrote: > I would guess (without actually trying it) that yes, Visual would surely > work with numpy 1.3 if (but only if) Visual had been compiled with numpy 1.3 > present. You make me realize that I've been too casual in what numpy I > install before building on Windows. I've always just used the most up to > date version of numpy, without checking to see what version of numpy is > being used by scipy. Of course there may be yet another major application > that wants even a different numpy, but surely scipy is the most likely > accompaniment to Visual. > > Should I rebuild the Windows installer using numpy 1.3? > > Bruce Sherwood > > Gary Pajer wrote: > > I installed VPython on a new WinXP machine. First I installed python, then > visual, and all was good. > > Then I went about and installed the other stuff I use ... numpy, scipy, > matplotlib ... > > And VPython crashed python at "import visual" > > Then I discovered that the VPython installer installs numpy 1.4, but the > latest version on numpy.scipy.org is numpy 1.3. So I had unknowingly > downgraded numpy. So I uninstalled numpy and visual (and python for good > measure) and reinstalled, and it works again. > > Is it possible (or already known) that visual does not work with numpy 1.3, > the current release? I'm hesitant to try it myself. Everything is working > now, but I was surprised, and I thought I might document this potential > gotcha. > > -gary > > ------------------------------ > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOWhttp://p.sf.net/sfu/solaris-dev2dev > > ------------------------------ > > _______________________________________________ > Visualpython-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
|
From: Gary P. <gar...@gm...> - 2010-02-16 14:07:26
|
On Mon, Feb 15, 2010 at 3:13 PM, Gary Pajer <gar...@gm...> wrote: > We should probably confirm that 1.3 does break visual before proceeding. > I'm surprised that a change from 1.3 -> 1.4 would cause breakage... the API > is supposed to be the same. > > But wait ... I now recall that there is a discussion going on about numpy > 1.4 ... evidently it actually breaks the ABI, the application binary > interface. There have been over 200 posts on the subject on the numpy > discussion list. The break comes in date/time support, so I wouldn't think > it would affect visual. I glanced at some of the posts, and they talk as if > 1.4 has been released, but I can't find it. Maybe they've withdrawn it. Someone just asked about this on the numpy mailing list. Evidently it is true that numpy 1.4 has been withdrawn due to the ABI breakage. |
|
From: Bruce S. <Bru...@nc...> - 2010-02-16 14:42:49
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Gary, thanks for tracking this down. I'll rebuild the Windows version.
I think the Mac version may also need to be redone.<br>
<br>
Bruce Sherwood<br>
<br>
Gary Pajer wrote:
<blockquote
cite="mid:88f...@ma..."
type="cite">
<div class="gmail_quote">On Mon, Feb 15, 2010 at 3:13 PM, Gary Pajer <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:gar...@gm...">gar...@gm...</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We
should probably confirm that 1.3 does break visual before proceeding.
I'm surprised that a change from 1.3 -> 1.4 would cause breakage...
the API is supposed to be the same. <br>
<br>
But wait ... I now recall that there is a discussion going on about
numpy 1.4 ... evidently it actually breaks the ABI, the application
binary interface. There have been over 200 posts on the subject on the
numpy discussion list. The break comes in date/time support, so I
wouldn't think it would affect visual. I glanced at some of the posts,
and they talk as if 1.4 has been released, but I can't find it. Maybe
they've withdrawn it.</blockquote>
<div><br>
</div>
<div>Someone just asked about this on the numpy mailing list. <br>
Evidently it is true that numpy 1.4 has been withdrawn due to the ABI
breakage. </div>
</div>
<pre wrap="">
<hr size="4" width="90%">
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/solaris-dev2dev">http://p.sf.net/sfu/solaris-dev2dev</a></pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Visualpython-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Vis...@li...">Vis...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/visualpython-users">https://lists.sourceforge.net/lists/listinfo/visualpython-users</a>
</pre>
</blockquote>
</body>
</html>
|
×
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