From: Travis O. <oli...@ie...> - 2006-05-31 02:53:32
|
Please help the developers by responding to a few questions. 1) Have you transitioned or started to transition to NumPy (i.e. import numpy)? 2) Will you transition within the next 6 months? (if you answered No to #1) 3) Please, explain your reason(s) for not making the switch. (if you answered No to #2) 4) Please provide any suggestions for improving NumPy. Thanks for your answers. NumPy Developers |
From: Bill B. <wb...@gm...> - 2006-05-31 03:43:52
|
pyOpenGL is one project that hasn't upgraded to numpy yet. http://pyopengl.sourceforge.net/ I think the issue is just that noone is really maintaining it, rather than any difficulty in porting to numpy. Since he's probably not reading this list, might be a good idea to send the project admin a copy of the survey: mcfletch at users.sourceforge.net --bb On 5/31/06, Travis Oliphant <oli...@ie...> wrote: > > > Please help the developers by responding to a few questions. > > > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? > > > > > 2) Will you transition within the next 6 months? (if you answered No to > #1) > > > > > 3) Please, explain your reason(s) for not making the switch. (if you > answered No to #2) > > > > > > 4) Please provide any suggestions for improving NumPy. > > > > > > Thanks for your answers. > > > NumPy Developers > > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > -- William V. Baxter III OLM Digital Kono Dens Building Rm 302 1-8-8 Wakabayashi Setagaya-ku Tokyo, Japan 154-0023 +81 (3) 3422-3380 |
From: Sasha <nd...@ma...> - 2006-05-31 03:56:41
|
I am a Numeric user. On 5/30/06, Travis Oliphant <oli...@ie...> wrote: > > Please help the developers by responding to a few questions. > > > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? > Started transition. Most applications were easily ported to Numpy. I am still deciding whether or not support both Numpy and Numeric during the transition period. > > 2) Will you transition within the next 6 months? (if you answered No to #1) > Yes, as soon as numpy 1.0 is released. > 4) Please provide any suggestions for improving NumPy. > That's a big topic! Without expanding on anything: - optimized array of interned strings (compatible with char** at the C level) - optimized array of arrays (a restriction of dtype=object array) - use BLAS in umath |
From: Andrew M. <an...@ob...> - 2006-05-31 04:31:13
|
We use Numeric in NetEpi Analysis (www.netepi.org). >Please help the developers by responding to a few questions. > >1) Have you transitioned or started to transition to NumPy (i.e. import >numpy)? No. >2) Will you transition within the next 6 months? (if you answered No to #1) Unknown - someone will have to fund the work. >3) Please, explain your reason(s) for not making the switch. (if you >answered No to #2) NetEpi Analysis implements C extensions to do fast set options on integer Numeric arrays, as well as to support mmap'ed Numeric arrays. I haven't looked at what is required to port these to Numpy (or replace with native Numpy features). NetEpi Analysis also uses rpy, which will potentially need to be updated to support Numpy. We're also concerned about speed - but I haven't done any testing against the latest Numpy. -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ |
From: Rob H. <ro...@ho...> - 2006-05-31 04:47:56
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Travis Oliphant wrote: Numeric user since 1998. Writing commercial application software for control of machines. The machine is sold with the application software, closed source. | 1) Have you transitioned or started to transition to NumPy (i.e. import | numpy)? No | 2) Will you transition within the next 6 months? (if you answered No to #1) Maybe. | 3) Please, explain your reason(s) for not making the switch. (if you | answered No to #2) We are by now late adopters of everything. Everything else we use (we use about 30 non-GPL opensource packages in our development environment, some of which are using Numeric themselves) will need to migrate as well. Our own code is interspersed with Numeric calls, and amounts to about 200k lines... Rob - -- Rob W.W. Hooft || ro...@ho... || http://www.hooft.net/people/rob/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEfR/fH7J/Cv8rb3QRAvbjAKCCMLpbBbWSBDsRZZzL0+p4HTqcLACbBwiB YLFwX1oEULCH068j2I7ZoDg= =0gj8 -----END PGP SIGNATURE----- |
From: Jens <je...@fy...> - 2006-05-31 06:14:07
|
We use Numeric for our "Atomic Simulation Environment" and for a Density Functional Theory code: http://wiki.fysik.dtu.dk/ASE http://wiki.fysik.dtu.dk/gridcode > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? No. > 2) Will you transition within the next 6 months? (if you answered No to > #1) Yes. Only problem is that ASE relies on Konrad Hinsen's Scientific.IO.NetCDF module which is still a Numeric thing. I saw recently that this module has been converted to numpy and put in SciPy/sandbox. What is the future of this module? > 4) Please provide any suggestions for improving NumPy. Can't think of anything! Jens J=F8rgen Mortensen |
From: Konrad H. <kh...@ce...> - 2006-06-06 16:27:48
|
On May 31, 2006, at 8:13, Jens J=F8rgen Mortensen wrote: > Yes. Only problem is that ASE relies on Konrad Hinsen's > Scientific.IO.NetCDF module which is still a Numeric thing. I saw > recently that this module has been converted to numpy and put in > SciPy/sandbox. What is the future of this module? Martin Wiechert recently sent me his adaptation to Numpy. I =20 integrated his patches checking for nothing else but that it doesn't =20 break the Numeric interface. I then checked that it compiles and runs =20= the demo script correctly. I am happy to send this version to anyone =20 who wants to test-drive it. Personally I cannot really test it as all =20= my application code that is based on it requires Numeric. Konrad. -- --------------------------------------------------------------------- Konrad Hinsen Laboratoire L=E9on Brillouin, CEA Saclay, 91191 Gif-sur-Yvette Cedex, France Tel.: +33-1 69 08 79 25 Fax: +33-1 69 08 82 61 E-Mail: kon...@ce... --------------------------------------------------------------------- |
From: <rba...@fr...> - 2006-05-31 07:53:39
|
Le Mercredi 31 Mai 2006 04:53, Travis Oliphant a =E9crit : > Please help the developers by responding to a few questions. > > I am a numarray user > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? no I tried to install numpy but the installation failed. > > 2) Will you transition within the next 6 months? (if you answered No to= #1) > no,=20 (hm, but if numarray will be prohibited, ...) > > 3) Please, explain your reason(s) for not making the switch. (if you > answered No to #2) > numarray works and works fine (from version number 0.8 to 1.5) > > > > 4) Please provide any suggestions for improving NumPy. > > > > > > Thanks for your answers. > > > NumPy Developers > > --=20 Ren=E9 Bastian http://www.musiques-rb.org http://pythoneon.musiques-rb.org |
From: Pujo A. <aj...@gm...> - 2006-05-31 08:45:16
|
On 5/31/06, Travis Oliphant <oli...@ie...> wrote: > > > Please help the developers by responding to a few questions. > > I'm a Numeric user. > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? > No > > > 2) Will you transition within the next 6 months? (if you answered No to > #1) > No > > > > 3) Please, explain your reason(s) for not making the switch. (if you > answered No to #2) > Numeric is ok and the conversion somehow make my unittest fail..... 4) Please provide any suggestions for improving NumPy. > I think the conversion between Numpy and numeric should be > compatible...... > > > > > Thanks for your answers. > > > NumPy Developers > > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |
From: Francesc A. <fa...@ca...> - 2006-05-31 11:51:59
|
Hi Travis, Here you have the answers for PyTables project (www.pytables.org). A Dimecres 31 Maig 2006 04:53, Travis Oliphant va escriure: > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? Not yet, although suport for it is in-place through the use of the array=20 protocol. > 2) Will you transition within the next 6 months? (if you answered No to #= 1) We don't know, but other projects in our radar make us to think that we wil= l=20 not be able to do that in this timeframe. > 3) Please, explain your reason(s) for not making the switch. (if you > answered No to #2) As I said before, it is mainly a matter of priorities. Also, numarray works= =20 very well for PyTables usage, and besides, NumPy 1.0 is not yet there. > 4) Please provide any suggestions for improving NumPy. You are already doing a *great* work. Perhaps pushing numexpr in NumPy woul= d=20 be nice. Also working in introducing a simple array class in Python core an= d=20 using the array protocol to access the data would be very good. Cheers, =2D-=20 >0,0< Francesc Altet =A0 =A0 http://www.carabos.com/ V V C=E1rabos Coop. V. =A0=A0Enjoy Data "-" |
From: Ed S. <sch...@ft...> - 2006-05-31 13:16:18
|
On 31/05/2006, at 4:53 AM, Travis Oliphant wrote: > Please help the developers by responding to a few questions. I've ported my code to NumPy. But I have some suggestions for improving NumPy. I've now entered them as these tickets: Improvements for NumPy's web presence: http://projects.scipy.org/scipy/numpy/ticket/132 Squeeze behaviour for 1d and 0d arrays: http://projects.scipy.org/scipy/numpy/ticket/133 Array creation from sequences: http://projects.scipy.org/scipy/numpy/ticket/134 -- Ed |
From: Gary S. <st...@nm...> - 2006-05-31 14:00:25
|
Numeric user since somewhere near "the beginning" (~1996-7?). > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? No. Just dabbling so far. > 2) Will you transition within the next 6 months? (if you answered No to #1) Depends. > 3) Please, explain your reason(s) for not making the switch. (if you answered > No to #2) (i) Numpy out-of-the-box build failed on my linux boxes, and I will need to upgrade linux and Windoze simultaneously. (ii) So far, Numeric is still working for me. (iii) Time ... I also have ~200k lines of code to convert. (iv) Like others, I guess I'm waiting for NumPy 1.0 to take a stab. > 4) Please provide any suggestions for improving NumPy. From what I've tried/tested so far on Windoze, Numpy looks awesome. Thanks Travis! And the rest of the development team! (Now, if I could only truly understand and remember all the new indexing options ... esp. a[tuple] vs. a[array] .....) Gary |
From: eric <er...@en...> - 2006-05-31 16:57:51
|
> > Please help the developers by responding to a few questions. > > > > 1) Have you transitioned or started to transition to NumPy (i.e. > import numpy)? We (Enthought) have started. > > > 2) Will you transition within the next 6 months? (if you answered No > to #1) We have a number of deployed applications that use Numeric heavily. Much of our code is now NumPy/Numeric compatible, but it is not well tested on NumPy. That said, a recent large project will be delivered on NumPy this summer, and we are releasing an update to a legacy app using NumPy in the next month or so. Pearu, Travis, and the Numeric->NumPy conversion scripts have been very helpful in this respect. It has been (and remains) a big effort to get the ship turned in the direction of NumPy, but we're committed to it. We are very much looking forward to using its new features. > > > 3) Please, explain your reason(s) for not making the switch. (if you > answered No to #2) Just time right now. We have noticed one major slow down in code, but it is a known issue (scalar math). This was easily fixed with a little weave code in the time being (so now we're actually 2-3 times faster than the old Numeric code. :-) > > 4) Please provide any suggestions for improving NumPy. No strong opinions here yet as I (sadly) haven't gotten to use it much yet. The scalar math speed hit us once, so others will probably hit it as well. Thanks again for all the amazing work on this stuff. It has already had an amazing impact on the community involvement and growth. From my own experience, I understand why others are slow to convert. Enthought has wanted to be an early adopter from the beginning, and we are still not there because of the effort involved in conversion and testing along with time pressures from other projects. Still, there is a nice feed back loop that happens here. As scipy/numpy continue to improve (more functionality, 64-bit stability, etc.) and more projects convert over, there are more reasons for people to update their code to the latest and greatest. My bet is it'll take 2-3 more years for the transition to run its course. see ya, eric > > > > > > Thanks for your answers. > > > NumPy Developers > > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat > certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |
From: Christopher B. <Chr...@no...> - 2006-05-31 17:08:22
|
Ed Schofield wrote: > Improvements for NumPy's web presence: > http://projects.scipy.org/scipy/numpy/ticket/132 From that page: NumPy's web presence could be improved by: 2. Pointing www.numpy.org to numeric.scipy.org instead of the SF page I don't like this. *numpy is not scipy*. It should have it's own page (which would refer to scipy). That page should be something better than the raw sourceforge page, however. A lot of us use numpy without anything else from the scipy project, and scipy is still a major pain in the *&&^* to build. Can you even build it with gcc 4 yet? I like the other ideas. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Fernando P. <fpe...@gm...> - 2006-05-31 21:35:23
|
On 5/31/06, Christopher Barker <Chr...@no...> wrote: > > Ed Schofield wrote: > > Improvements for NumPy's web presence: > > http://projects.scipy.org/scipy/numpy/ticket/132 > > From that page: > > NumPy's web presence could be improved by: > > 2. Pointing www.numpy.org to numeric.scipy.org instead of the SF page > > I don't like this. *numpy is not scipy*. It should have it's own page > (which would refer to scipy). That page should be something better than > the raw sourceforge page, however. Well, ipython is not scipy either, and yet its homepage is ipython.scipy.org. I think it's simply a matter of convenience that the Enthought hosting infrastructure is so much more pleasant to use than SF, that other projects use scipy.org as an umbrella. In that sense, I think it's fair to say that numpy is part of the 'scipy family'. I don't know, at least this doesn't particularly bother me. > A lot of us use numpy without anything else from the scipy project, and > scipy is still a major pain in the *&&^* to build. Can you even build it > with gcc 4 yet? I built it on a recent ubuntu not too long ago, without any glitches. I can check again tonitght on a fresh Dapper with up-to-date SVN if you want. Cheers, f |
From: Bruce S. <bso...@gm...> - 2006-05-31 18:47:55
|
Hi, On 5/30/06, Travis Oliphant <oli...@ie...> wrote: > > Please help the developers by responding to a few questions. > > > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? Yes and No > 2) Will you transition within the next 6 months? (if you answered No to #1) Probably for new code only. Having ported numarray code to NumPy there are too many quirks that need to be found. > 3) Please, explain your reason(s) for not making the switch. (if you > answered No to #2) Hopefully 1.0 will be out by then :-). Also bugs and performance will at a similar level to numeric and numarray. > 4) Please provide any suggestions for improving NumPy. The main one at present is to provide a stable release that can serve as a reference point for users. This is more a reflection of having a stable version of numpy for reference rather than having to check the svn for an appropriate version. Bruce > Thanks for your answers. > > > NumPy Developers > > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |
From: Russell E. O. <ro...@ce...> - 2006-05-31 21:48:26
|
In article <447...@ie...>, Travis Oliphant <oli...@ie...> wrote: > Please help the developers by responding to a few questions. > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? No, not beyond installing it to see if it works. > 2) Will you transition within the next 6 months? (if you answered No to #1) I expect to start to transition within a few months of both numpy and pyfits-with-numpy being released and being reported as stable and fast. > 4) Please provide any suggestions for improving NumPy. Please improve notification of documentation updates. I keep seeing complaints from folks who've bought the numpy documentation that they get no notification of updates. That makes me very reluctant to buy the documentation myself. I wish that full support for masked arrays had made it in (i.e. masked arrays are first class citizens that are accepted by all functions). The inability in numeric to apply 2d filters on masked image arrays is the main thing missing for me in numarray. -- Russell |
From: Alan G I. <ai...@am...> - 2006-06-01 02:57:29
|
On Wed, 31 May 2006, "Russell E. Owen" apparently wrote: > Please improve notification of documentation updates. > I keep seeing complaints from folks who've bought the > numpy documentation that they get no notification of > updates. That makes me very reluctant to buy the > documentation myself. The documentation is excellent, and I've been completely satisfied with Travis's handling of the updates. It is also a minimal investment in an excellent project. fwiw, Alan Isaac |
From: Fernando P. <fpe...@gm...> - 2006-06-01 04:19:28
|
On 5/31/06, Alan G Isaac <ai...@am...> wrote: > On Wed, 31 May 2006, "Russell E. Owen" apparently wrote: > > Please improve notification of documentation updates. > > I keep seeing complaints from folks who've bought the > > numpy documentation that they get no notification of > > updates. That makes me very reluctant to buy the > > documentation myself. > > The documentation is excellent, and I've been completely > satisfied with Travis's handling of the updates. I'll add my voice on this front. When I've needed a special update (for a workshop, where I needed to print out hardcopies as up-to-date as possible), Travis was very forthcoming and gave me quickly his most recent copy. So while a few weeks ago a couple of emails may not have been replied quite on the spot, overall I don't feel in any way slighted by his handling of the doc system, quite the opposite. And he also indicated he was in the process of setting up a more automated system. To be honest, I'd rather wait for a manual upate than see Travis devote one or two evenings to configuring something of this nature when he could be coding for numpy :) Cheers, f |
From: Christopher B. <Chr...@no...> - 2006-06-01 16:54:30
|
Fernando Perez wrote: >> 2. Pointing www.numpy.org to numeric.scipy.org instead of the SF page > Well, ipython is not scipy either, and yet its homepage is > ipython.scipy.org. I think it's simply a matter of convenience that > the Enthought hosting infrastructure is so much more pleasant to use > than SF Pardon me for being a lazy idiot. numeric.scipy.org is a fine place for it. I was reacting to a post a while back that suggested pointing people searching for numpy to the main scipy page, which I did not think was a good idea. Objection withdrawn. >> Can you even build it with gcc 4 yet? > I built it on a recent ubuntu not too long ago, without any glitches. > I can check again tonitght on a fresh Dapper with up-to-date SVN if > you want. Well, I need FC4 (and soon 5) as well as OS-X, so I'll try again when I get the chance. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Travis O. <oli...@ie...> - 2006-06-01 20:20:44
|
Berthold Höllmann wrote: > Travis Oliphant <oli...@ie...> writes: > > >> 2) Will you transition within the next 6 months? (if you answered No to #1) >> > > Unlikely > > >> 3) Please, explain your reason(s) for not making the switch. (if you >> answered No to #2) >> > > Lack of resources (Numeric is used in hand coded extensions; are > arrays of type PyObject supported in NumPy, they were not in numarray) > Yes, NumPy is actually quite similar to Numeric. Most C-extensions are easily ported simply by replacing #include Numeric/arrayobject.h with #include numpy/arrayobject.h (and making sure you get the right location for the headers). -Travis |
From: Perry G. <pe...@st...> - 2006-06-01 20:42:42
|
Just to clarify the issue with regard to numarray since one person brought it up. When we (STScI) are finished getting all our software running under numpy--and we are well more than halfway there--we will start drawing down support for numarray. It won't suddenly stop, but less and less effort will go into it and eventually none. That transition time (starts when we can run all our software on numpy and stops when we no longer support numarray at all) will probably be on the order of 6 months, but note that for much of that time, the support will likely be limited to dealing with major bugs only or support for new versions of major platforms. We will note the start and stop points of this transition on the numpy and scipy lists of course. After that, any support for it will have to come from elsewhere. (Message: if you use numarray, you should be planning now to make the transition if 6 months isn't enough time) Perry |
From: Joris De R. <jo...@st...> - 2006-06-02 11:07:03
|
[CB]: I was reacting to a post a while back that suggested pointing people [CB]: searching for numpy to the main scipy page, which I did not think was a [CB]: good idea. That would be my post :o) The reasons why I suggested this are 1) www.scipy.org is at the moment the most informative site on numpy 2) of all sites www.scipy.org looks currently most professional 3) a wiki-style site where everyone can contribute is really great 4) I like information to be centralized. Having to check pointers, docs and cookbooks on two different sites is inefficient 5) Two different sites inevitably implies some duplication of the work Just as you, I am not (yet) a scipy user, I only have numpy installed at the moment. The principal reason is the same as the one you mentioned. But for me this is an extra motivation to merge scipy.org and numpy.org: 6) merging scipy.org and numpy.org will hopefully lead to a larger SciPy community and this in turn hopefully leads to user-friendly installation procedures. Cheers, Joris Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm |
From: David M. C. <co...@ph...> - 2006-06-02 19:47:03
|
On Fri, 2 Jun 2006 10:27:45 +0200 Joris De Ridder <jo...@st...> wrote: > [CB]: I was reacting to a post a while back that suggested > pointing people [CB]: searching for numpy to the main scipy page, > which I did not think was a [CB]: good idea. > > That would be my post :o) > > The reasons why I suggested this are > > 1) www.scipy.org is at the moment the most informative site on numpy > 2) of all sites www.scipy.org looks currently most professional > 3) a wiki-style site where everyone can contribute is really great > 4) I like information to be centralized. Having to check pointers, > docs and cookbooks on two different sites is inefficient > 5) Two different sites inevitably implies some duplication of the work > > Just as you, I am not (yet) a scipy user, I only have numpy installed > at the moment. The principal reason is the same as the one you > mentioned. But for me this is an extra motivation to merge scipy.org > and numpy.org: > > 6) merging scipy.org and numpy.org will hopefully lead to a larger > SciPy community and this in turn hopefully leads to user-friendly > installation procedures. My only concern with this is numpy is positioned for a wider audience: everybody who needs arrays, and the extra speed that numpy gives, but doesn't need what scipy gives. So merging the two could lead to confusion on what provides what, and what you need to do which. For instance, I don't want potential numpy users to be directed to scipy.org, and be turned off with all the extra stuff it seems to have (that scipy, not numpy, provides). But I think this can be handled if we approach scipy.org as serving both purposes. But I think is this the best option, considering how much crossover there is. -- |>|\/|< /--------------------------------------------------------------------------\ |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ |co...@ph... |
From: Jonathan T. <jon...@ut...> - 2006-06-03 12:04:23
|
My suggestion would be to have both numpy.org and scipy.org be the exact same page, but make it extremely clear that there are two different projects on the front page. Cheers. Jon. On 6/2/06, David M. Cooke <co...@ph...> wrote: > On Fri, 2 Jun 2006 10:27:45 +0200 > Joris De Ridder <jo...@st...> wrote: > > [CB]: I was reacting to a post a while back that suggested > > pointing people [CB]: searching for numpy to the main scipy page, > > which I did not think was a [CB]: good idea. > > > > That would be my post :o) > > > > The reasons why I suggested this are > > > > 1) www.scipy.org is at the moment the most informative site on numpy > > 2) of all sites www.scipy.org looks currently most professional > > 3) a wiki-style site where everyone can contribute is really great > > 4) I like information to be centralized. Having to check pointers, > > docs and cookbooks on two different sites is inefficient > > 5) Two different sites inevitably implies some duplication of the work > > > > Just as you, I am not (yet) a scipy user, I only have numpy installed > > at the moment. The principal reason is the same as the one you > > mentioned. But for me this is an extra motivation to merge scipy.org > > and numpy.org: > > > > 6) merging scipy.org and numpy.org will hopefully lead to a larger > > SciPy community and this in turn hopefully leads to user-friendly > > installation procedures. > > My only concern with this is numpy is positioned for a wider audience: > everybody who needs arrays, and the extra speed that numpy gives, but > doesn't need what scipy gives. So merging the two could lead to > confusion on what provides what, and what you need to do which. > For instance, I don't want potential numpy users to be directed to > scipy.org, and be turned off with all the extra stuff it seems to have > (that scipy, not numpy, provides). But I think this can be handled if > we approach scipy.org as serving both purposes. > > But I think is this the best option, considering how much crossover > there is. > > -- > |>|\/|< > /--------------------------------------------------------------------------\ > |David M. Cooke > http://arbutus.physics.mcmaster.ca/dmc/ |co...@ph... > > > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |