leif wrote:
leif wrote:
leif wrote:
Looks like reinstalling the Sage library spkg would meanwhile also
trigger the rebuild of *all* extension modules; not sure since when
though... (seen with Sage 5.10.beta5 at least)
Yep. This is because #14570, merged into Sage 5.10.beta4, completely
brea
leif wrote:
leif wrote:
Looks like reinstalling the Sage library spkg would meanwhile also
trigger the rebuild of *all* extension modules; not sure since when
though... (seen with Sage 5.10.beta5 at least)
Yep. This is because #14570, merged into Sage 5.10.beta4, completely
breaks sage-sync-
Hey,
Could we at least get the hacked sage-sync-build into 5.10? The combinat
queue has a few patch which create new cython files that replace python
files (i.e. cythonizes them) which requires the sync-build to be run when
people are moving ahead of those patches. Rebuilding all cython files
leif wrote:
leif wrote:
4) Minimally adapt sage-sync-build.py to reflect the (hard-coded) change
by #14570. [May be easy as well, but potentially unsafe.]
Even that turns out to be non-trivial, AFAICS, i.e., the whole strategy
would have to get changed, as opposed to just some file / director
On Sat, Jun 1, 2013 at 3:55 AM, leif wrote:
> John H Palmieri wrote:
>>
>> On Thursday, May 30, 2013 9:57:07 PM UTC-7, leif wrote:
>>
>> leif wrote:
>> > Looks like reinstalling the Sage library spkg would meanwhile also
>> > trigger the rebuild of *all* extension modules; not sure s
leif wrote:
leif wrote:
John H Palmieri wrote:
Is there a ticket for the sage-sync-build problem?
Not yet. There are a couple of ways to (quickly or temporarily) "fix"
this:
1) Unmerge #14570, which doesn't fix a bug, but only introduces a new
(btw. non-configurable) feature. [A bit odd, e
leif wrote:
John H Palmieri wrote:
Is there a ticket for the sage-sync-build problem?
Not yet. There are a couple of ways to (quickly or temporarily) "fix"
this:
1) Unmerge #14570, which doesn't fix a bug, but only introduces a new
(btw. non-configurable) feature. [A bit odd, especially sin
John H Palmieri wrote:
On Thursday, May 30, 2013 9:57:07 PM UTC-7, leif wrote:
leif wrote:
> Looks like reinstalling the Sage library spkg would meanwhile also
> trigger the rebuild of *all* extension modules; not sure since when
> though... (seen with Sage 5.10.beta5 at leas
Hey,
I noticed that after running sync-build that it was always taking a very
long time. I'm moving through a couple of patches which create new cython
files and having to watch sage rebuild because I need to run sync-build
slows me down significantly. This definitely should be a blocker.
Be
On Thursday, May 30, 2013 9:57:07 PM UTC-7, leif wrote:
>
> leif wrote:
> > Looks like reinstalling the Sage library spkg would meanwhile also
> > trigger the rebuild of *all* extension modules; not sure since when
> > though... (seen with Sage 5.10.beta5 at least)
>
> Yep. This is because
On 2013-05-31, leif wrote:
> IMHO both issues (complete rebuild upon cloning and after
> sage-sync-build) should be resolved before the final 5.10 gets out.
+1
It should be a blocker, IMHO.
Cheers, Simon
--
You received this message because you are subscribed to the Google Groups
"sage-deve
leif wrote:
Looks like reinstalling the Sage library spkg would meanwhile also
trigger the rebuild of *all* extension modules; not sure since when
though... (seen with Sage 5.10.beta5 at least)
Yep. This is because #14570, merged into Sage 5.10.beta4, completely
breaks sage-sync-build, which
Eric Gourgoulhon wrote:
I confirm this behavior on a fresh install of version 5.9 from the
sources: sage -clone triggers the recompilation of the Cython sources.
In version 5.8, it did not. Don't know the reason for this...
Looks like reinstalling the Sage library spkg would meanwhile also
tr
>> For the impatient, the following at least avoids rebuilding of (most of
>> the) Cython-generated files:
Thanks leif, it works quite well on sage-5.9. Do you have an idea for
avoiding documentation regeneration (see [1]) ?
Best,
Vincent
[1]
http://groups.google.com/group/sage-devel/browse_t
leif wrote:
leif wrote:
Eric Gourgoulhon wrote:
I confirm this behavior on a fresh install of version 5.9 from the
sources: sage -clone triggers the recompilation of the Cython sources.
In version 5.8, it did not. Don't know the reason for this...
For the impatient, the following at least avo
leif wrote:
Eric Gourgoulhon wrote:
I confirm this behavior on a fresh install of version 5.9 from the
sources: sage -clone triggers the recompilation of the Cython sources.
In version 5.8, it did not. Don't know the reason for this...
FWIW, it did still work in 5.9.beta2.
Probably #13031 [1]
Eric Gourgoulhon wrote:
I confirm this behavior on a fresh install of version 5.9 from the
sources: sage -clone triggers the recompilation of the Cython sources.
In version 5.8, it did not. Don't know the reason for this...
FWIW, it did still work in 5.9.beta2.
Probably #13031 [1] (merged into
I confirm this behavior on a fresh install of version 5.9 from the sources:
sage -clone triggers the recompilation of the Cython sources. In version
5.8, it did not. Don't know the reason for this...
Eric.
Le vendredi 10 mai 2013 14:53:27 UTC+2, vdelecroix a écrit :
>
> Hi,
>
> It seems that th
18 matches
Mail list logo
