Thanks for the review. I think it will be safe as well. Ondrej is traveling
to Prague at the moment. When he arrives, let's here what he has to say and
then move forward.
-Travis
On Jul 12, 2012, at 12:42 AM, Charles R Harris wrote:
>
>
> On Wed, Jul 11, 2012 at 11:21 PM, Thouis (Ray) J
On Wed, Jul 11, 2012 at 11:21 PM, Thouis (Ray) Jones wrote:
> On Thu, Jul 12, 2012 at 1:28 AM, Charles R Harris
> wrote:
> > Hi All,
> >
> > Travis and I agree that it would be appropriate to remove the current
> 1.7.x
> > branch and branch again after a code freeze. That way we can avoid the
> p
On Thu, Jul 12, 2012 at 1:28 AM, Charles R Harris
wrote:
> Hi All,
>
> Travis and I agree that it would be appropriate to remove the current 1.7.x
> branch and branch again after a code freeze. That way we can avoid the pain
> and potential errors of backports. It is considered bad form to mess wi
Hi All,
Travis and I agree that it would be appropriate to remove the current 1.7.x
branch and branch again after a code freeze. That way we can avoid the pain
and potential errors of backports. It is considered bad form to mess with
public repositories that way, so another option would be to rena
On Sun, Jul 8, 2012 at 11:47 AM, Matthew Brett wrote:
> Hi,
>
> On Sun, Jul 8, 2012 at 2:36 AM, Ralf Gommers
> wrote:
> >
> >
> > On Fri, Jul 6, 2012 at 1:30 PM, McCully, Dwayne (NIH/NLM/LHC) [C]
> > wrote:
> >>
> >> Hope this is the right list to post this problem! I’m getting two
> errors
> >
On Thu, Jul 12, 2012 at 12:06 AM, Fode wrote:
> Should build_ext regenerate the cython files? It is not doing so for me.
No, Cython is not a build requirement for numpy. Therefore Cython is run
either by hand, or in the case of numpy.random by running
generate_mtrand_c.py. Then we check in the
Should build_ext regenerate the cython files? It is not doing so for me.
Fode
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
