Tim Churches wrote:
> Yes, except that we have quite a lot of code in fielded applications
> which is written with Numeric, and which also uses RPy. We currently
> have no funds to do the Numeric to NumPy port in our code. If RPy
> dropped support for Numeric, we would be forced to use increasing o
Tim Churches wrote:
> Robert Kern wrote:
>> I don't see why. RPy will use numpy internally to communicate with R. Your
>> code
>> will use Numeric internally to do whatever you do. As of Numeric 24.2, each
>> can
>> consume the other's arrays seamlessly.
>
> OK, if that is the case, then it migh
Robert Kern wrote:
> I don't see why. RPy will use numpy internally to communicate with R. Your
> code
> will use Numeric internally to do whatever you do. As of Numeric 24.2, each
> can
> consume the other's arrays seamlessly.
OK, if that is the case, then it might be OK for us if RPy dropped
N
Tim Churches wrote:
> Travis Oliphant wrote:
>> I've added a patch to the Porting to NumPy page so that RPy uses NumPy
>> instead of Numeric. It would be very helpful for unification if these
>> package authors would accept these patches. NumPy is far enough along
>> in development that I don'
Travis Oliphant wrote:
> I've added a patch to the Porting to NumPy page so that RPy uses NumPy
> instead of Numeric. It would be very helpful for unification if these
> package authors would accept these patches. NumPy is far enough along
> in development that I don't think there is any reaso
I've added a patch to the Porting to NumPy page so that RPy uses NumPy
instead of Numeric. It would be very helpful for unification if these
package authors would accept these patches. NumPy is far enough along
in development that I don't think there is any reason for new releases
of package
