Which source files/functions/line numbers should I take a look at, as specifically as possible?<br><br><div class="gmail_quote">On Tue, Jul 31, 2012 at 9:55 AM, Maciej Fijalkowski <span dir="ltr"><<a href="mailto:fijall@gmail.com" target="_blank">fijall@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Jul 31, 2012 at 3:41 PM, Steven Jackson<br>
<<a href="mailto:stevenjackson121@gmail.com">stevenjackson121@gmail.com</a>> wrote:<br>
> I am definitely open to working on Numpy first, my only hesitation was that<br>
> it might be hard to get spun up, and scipy seemed like something I could<br>
> slice off and do (some of) by myself without accidentally conflicting with<br>
> ongoing development efforts.<br>
><br>
> If, as your replies have indicated, Numpy isn't being very actively<br>
> developed, and it would be easy to get caught up and avoid conflicting with<br>
> other developers, then I'd be glad to help there instead of independently<br>
> trying to get scipy going.<br>
<br>
</div>That sounds very good to me. The thing I started (and I'm not actively<br>
working on it for at least a week or two more) is to clean up stuff<br>
and try to reuse pure-python numpy part without changes<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
><br>
> On Tue, Jul 31, 2012 at 9:24 AM, Daπid <<a href="mailto:davidmenhur@gmail.com">davidmenhur@gmail.com</a>> wrote:<br>
>><br>
>> I believe the reason is that they prefer to focus the development<br>
>> effort into the more "basic" Numpy and from that go on. Numpy is not<br>
>> fully implemented<br>
>><br>
>> I am working (actually, right now I am only in the "thinking" state)<br>
>> on some modules of NumPy, maybe we could coordinate and give this a<br>
>> boost.<br>
>><br>
>> On Tue, Jul 31, 2012 at 12:25 PM, Steven Jackson<br>
>> <<a href="mailto:stevenjackson121@gmail.com">stevenjackson121@gmail.com</a>> wrote:<br>
>> > I know there is no current plan to implement scipy in pypy, but<br>
>> > searching<br>
>> > the PyPy website, I was not able to find the reason.<br>
>> ><br>
>> > If it is not to be included as a feature due to lack of interest or<br>
>> > developer time, I am offering to begin rewriting scipy in pure python (I<br>
>> > have quite a bit of free time to do this).<br>
>> > If it has been discussed and actively excluded from pypy, I would like<br>
>> > to<br>
>> > know that before I waste too much time rewriting it.<br>
>> ><br>
>> > I have an active interest in being able to use some modules which depend<br>
>> > on<br>
>> > scipy while using the PyPy interpreter (especially pyBrain). I have seen<br>
>> > the<br>
>> > hack on the pypy blog:<br>
>> ><br>
>> ><br>
>> > <a href="http://morepypy.blogspot.com/2011/12/plotting-using-matplotlib-from-pypy.html" target="_blank">http://morepypy.blogspot.com/2011/12/plotting-using-matplotlib-from-pypy.html</a><br>
>> ><br>
>> > I could simply use the hack myself, but unless there's a reason not too,<br>
>> > I<br>
>> > think it'd be nice to have scipy available as a pure python module<br>
>> > (perhaps<br>
>> > called scipypy in the same manner as numpy).<br>
>> ><br>
>> > --<br>
>> > Steven Jackson<br>
>> ><br>
>> > _______________________________________________<br>
>> > pypy-dev mailing list<br>
>> > <a href="mailto:pypy-dev@python.org">pypy-dev@python.org</a><br>
>> > <a href="http://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">http://mail.python.org/mailman/listinfo/pypy-dev</a><br>
>> ><br>
><br>
><br>
><br>
><br>
> --<br>
> Steven Jackson<br>
><br>
> _______________________________________________<br>
> pypy-dev mailing list<br>
> <a href="mailto:pypy-dev@python.org">pypy-dev@python.org</a><br>
> <a href="http://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">http://mail.python.org/mailman/listinfo/pypy-dev</a><br>
><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Steven Jackson<br>