>
> Sure. This list actually deserves a long writeup about that. First,
> there wasn't a "Cython-refactor" of NumPy. There was a Cython-refactor of
> SciPy. I'm not sure of it's current status. I'm still very supportive
> of that sort of thing.
>
>
> I think I missed that - is it on git somewhere?
>
>
> I thought so, but I can't find it either. We should ask Jason McCampbell
> of Enthought where the code is located. Here are the distributed eggs:
> http://www.enthought.com/repo/.iron/
>
> -Travis
>
Hi Travis and everyone, just cleaning up email and saw this question. The
trees had been in my personal GitHub account prior to Enthought switching
over. I forked them now and the paths are:
https://github.com/enthought/numpy-refactor
https://github.com/enthought/scipy-refactor
The numpy code is on the 'refactor' branch. The master branch is dated but
consistent (correct commit IDs) with the master NumPy repository on GitHub
so the refactor branch should be able to be pushed to the main numpy
account if desired.
The scipy code was cloned from the subversion repository and so would
either need to be moved back to svn or sync'd with any git migration.
Jason
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
