From: Arthur S. <ajs...@op...> - 2006-10-08 22:45:03
|
On Sun, 2006-10-08 at 15:45 -0600, Bruce Sherwood wrote: > I agree that it is a priority to be able to run Visual 3 on Python 2.5. > > I'm guessing that the quickest way to do that would be to comment out > references in Visual to Numeric (which isn't available for Python 2.5 I'm confused why it is you have that impression. Numeric's C can compile against Python2.5, and its Python code is fully compatible with Python2.5. I have compiled it successfully today on Linux. In fact, in my mind it is more stable and mature than numarray. It is my understanding that numarray was developed to optimize enormous arrays confronted in analyzing astronomical data - astronomical arrays ;) - and is sub-optimum for the earthbound arrays I think is more typical in the use of vpython. It is also my impression that numarray never fully matured, i.e. development was cut short when it was agreed that numpy would become the standard. So that it is my opinion that we should be concentrating on a Numeric based distribution against Python2.5. Though it is also true I am not understanding what the problem you see in keeping things as they are, and using either/or. To me this is rather straight forward - I see no reason why the existing vpython 3.xxx should have any problems with Python2.5 other than the one I had mentioned on 64 bit machines - which I am assuming is not a practical problem for most. Python is generally conservative in its development philosophy. A new release generally means new features. Great attention is paid to not breaking backward compatibility. The change in the C API to accommodate 64 bit machines is a rare exception, except that it was done in such a way that other than possibly a warning message that wasn't there before, things whould continue to run fine as they were on your standard PC. With my general "unless I am missing something" disclaimer, I think we are making this more of an issue than it should be. My problem is that I don't have the commercial tools necessary to do a Windows compilation to try to understand what you are running into. But frankly I suspect it is something other than what you think it is. Art > but is required to be present for Visual to build, at least on Windows) > and go with NumArray (which should work with Visual, even though I just > discovered that it doesn't seem to). However, this is a less desirable > path than replacing both Numeric and NumArray with the new NumPy. > > This assumes that the amount of work required to make a stable Visual 4 > with NumPy will take significantly more time than making a stable Visual > 3 with NumPy. > > For the information of those interested in working on Visual, using > source code from sourceforge.net: The files HACKING.txt and INSTALL.txt > contain instructions on what tools you need to have on your computer in > order to be able to build from source, and instructions on how to use > those tools. If you have questions, feel free to ask. > > Individual files in the project typically have pretty good commentary, > but there isn't an overview document that explains how the pieces go > together, which together with the complexity of Visual does make it > difficult to get started. > > Bruce > > Arthur Siegel wrote: > > >On Sun, 2006-10-08 at 10:05 -0400, Arthur Siegel wrote: > > > > > > > >>So that maybe the short-term focus should > >>be shifted there. I am concerned about the perception regarding VPython > >>should there be a significant delay in making Python2.5 binaries > >>available, now that Python2.5 is itself final. > >> > >> > > > >to add - > > > >IMO, binaries for Python2.5 against the stable 3.xxx branch should be > >maintained and made available until such time as the known bugs against > >the 4.xxx branch get sorted out. > > > >Among other reasons, it is my perception that the Debian folks are quite > >conservative about what they package/support so that an official Debian > >distro against 3.xxx and Python2.5 is a more feasible request than one > >against 4.xxx. > > > > > >Art > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |