On Thu, May 15, 2014 at 12:53 AM, Ralf Stephan wrote:
> It may be possible to test newer package versions in patchbot without
> official ticket by forking Sage on github, installing the package in the
> local
> Sage, publish the changed branch on github, and use that branch as
> base_repo with pat
I didn't put it there. I agree that its silly, but so is much of the
bureaucratic process behind these grants. Afaik we don't have a policy
formulated.
On Saturday, May 17, 2014 11:40:25 PM UTC+1, Nathann Cohen wrote:
>
> Hm... Could we not cite grants in source code ? :-/
>
> +This modul
Hm... Could we not cite grants in source code ? :-/
+This module has, in part, received funding from the European Union's
+Seventh Framework Programme (FP7/2007-2013) under grant agreement
+FP7-ICT-247914.
--
You received this message because you are subscribed to the Google Groups
"sage-de
R. Andrew Ohana wrote:
Well it is a bit different than other changes, since nothing actually
changes in the ticket itself (which would prompt a notification). Rather
the plugin is just a special render for the branch field, so the merge
is not actually checked until someone actually loads the pag
Well it is a bit different than other changes, since nothing actually
changes in the ticket itself (which would prompt a notification). Rather
the plugin is just a special render for the branch field, so the merge is
not actually checked until someone actually loads the page for the first
time (res
bump
On Monday, May 12, 2014 1:09:20 PM UTC+1, Volker Braun wrote:
>
> This fixes some critical bugs in comparison with infinities
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it,
Ralf Stephan wrote:
On Friday, May 16, 2014 1:19:08 PM UTC+2, Wilfried Lübbe wrote:
> Would it be possible to reveive an email notification when the color changes
to red (like for other changes of the ticket)?
And set the ticket to needs-work, *beg*...
Alternatively, introduce another trac tic
It is possible that the /tmp installation is broken anyway. With
setuptools-3.6
I get 4 out of 4 failures because some paths point back to the original
sage/
directory, but some not and the underlying files are not there (numpy for
example).
Moreover, none of the 6.2 TestsPassed runs (n=47) is a
