Thats really a C-level question, the different modules will see the same
value iff the address of MtxLibDir is the same.
On the C level both is possible; The header can declare it e.g. static,
then every compilation unit gets its own copy. Or it can declare it extern,
then it will be shared acr
Hi!
I seek help in the following situation:
The optional package "meataxe" provides a header meataxe.h, defining a
variable
extern char MtxLibDir[];
It is used by some of meataxe's functions to find certain data files.
sage/libs/meataxe.pxd exposes MtxLibDir to Sage, with
cdef extern from "mea
Hi John,
On 2016-08-06, Joseph Hundley wrote:
> I remark that maybe when someone qualified has some time it would be worth
> updating Simon's
> how-to
> at
> http://doc.sagemath.org/html/en/thematic_tutorials/coercion_and_categories.html#base-classes.
>
> This bit appears (to me, anyway) to r
John Cremona wrote:
> None of the worked : sage -b and sage -ba all fail in the same way.
>
> Is this sort of warning normal:
It's not actually a warning but usually rather an error, since this
happens (or may happen) when trying to import from such a folder which
Sage (or Volker ;-) ) refuses to
None of the worked : sage -b and sage -ba all fail in the same way.
Is this sort of warning normal:
make[2]: Entering directory '/home/john/sage/build/make'
if [ -z "$SAGE_INSTALL_FETCH_ONLY" ]; then \
cd /home/john/sage/src && source bin/sage-env && \
sage-logger -p 'time make sage' '/home/john/
On Saturday, August 6, 2016, Volker Braun wrote:
> On Saturday, August 6, 2016 at 5:46:34 PM UTC+2, William wrote:
>>
>> Thanks -- in this case that is perfect, and often that will be all
>> that is needed. Is there any chance we could add a link to provide
>> &id2=develop, since it's a little h
On Saturday, August 6, 2016 at 5:46:34 PM UTC+2, William wrote:
>
> Thanks -- in this case that is perfect, and often that will be all
> that is needed. Is there any chance we could add a link to provide
> &id2=develop, since it's a little hard to remember...?
Whats the problem with clicking
On Sat, Aug 6, 2016 at 12:55 AM, Volker Braun wrote:
> Since cgit doesn't know when you want the diff to start it can't really
> display anything more useful.
>
> You can add e.g. &id2=develop to the URL to specify the starting point, e.g.
>
> https://git.sagemath.org/sage.git/diff/?h=e5fc48064b49
On 6 August 2016 at 16:19, leif wrote:
> John Cremona wrote:
>> On a machine where I had built 7.2 from source and have no branches
>> except master, I did "git pull origin master" to get 7.3 and then
>> "make". Problems:
>
> We already had this; either your working directory isn't clean, or the
John Cremona wrote:
> On a machine where I had built 7.2 from source and have no branches
> except master, I did "git pull origin master" to get 7.3 and then
> "make". Problems:
We already had this; either your working directory isn't clean, or the
*.pyc files haven't been rebuilt.
Try git check
https://libreplanet.org/wiki/Repository_Ethics
They've also ranked GitHub (follow the second link [1] on that page)...
-leif
[1] https://www.gnu.org/software/repo-criteria-evaluation.html
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsu
In sage 7.2 and 7.3, the sequence of commands below produces an error in
sage. It looks like it is calling pari for the computation. Doing the
analogous commands directly in pari works, so the error is in sage dealing
with the pari output (assuming some integer has to be small).
John Jones
p
> 2) When I do git-blame, or other similar commands, I can easily get a
> commit message or commit hash, but I can't get a ticket number. Which is
> usually what I want (to look up e.g. why a change had been done). That's
> user-unfriendly.
I should have added that I don't think we can do much abo
> Because there is no ticket-DAG and there is no immutable history of
> tickets.
I don't see why there couldn't be. Once a ticket is closed, it is
immutable. While a ticket is open, its position in the DAG is mutable:
it will always depend on the tip of develop, as well as tickets that it
explici
On a machine where I had built 7.2 from source and have no branches
except master, I did "git pull origin master" to get 7.3 and then
"make". Problems:
qflllTraceback (most recent call last):
[sagelib-7.3] File "", line 1, in
[sagelib-7.3] File
"/home/john/sage/local/lib/python2.7/site-packa
On Saturday, August 6, 2016 at 2:28:40 PM UTC+2, Johan S. R. Nielsen wrote:
>
> We are informally and without tools abiding by the ticket-DAG.
Because there is no ticket-DAG and there is no immutable history of
tickets. Ticket dependencies are informational but don't change what code
is being a
> You are trying to build a DAG of tickets that is a coarser version of the
> git DAG. You'd need
>
> * Tools to make sure that the two different graphs stay alined.
> * UI to visualize the two different graphs, and to report conflicts
> * Documentation
We are informally and without tools abidin
On Saturday, August 6, 2016 at 1:12:50 PM UTC+2, Johan S. R. Nielsen wrote:
>
> Yes, that's the way Git works. But should it really be the way our
> ticket system should work?
>
You are trying to build a DAG of tickets that is a coarser version of the
git DAG. You'd need
* Tools to make sure
> Changing the branch on A doesn't change the branch on B.
>
> E.g. assume A, B started on the develop branch. Then commit on A, merge A
> in B, commit on B.
>
> Now A contains one commits, and B contains two commits.
>
> Then reset A back to develop. B still contains two commits.
Yes, that's t
On Saturday, August 6, 2016 at 12:37:59 PM UTC+2, Johan S. R. Nielsen wrote:
>
> Say #B is dependent on #A. If #A changes so #B no longer applies on top
> of #A, ...
Changing the branch on A doesn't change the branch on B.
E.g. assume A, B started on the develop branch. Then commit on A, merge
> No, because dependencies are not static. You can e.g. delete the branch
> from a dependency after the dependent ticket has been reviewed...
I don't think I understand what you mean. If that happens, then surely
some action should be taken on the dependent ticket?
Say #B is dependent on #A. If
On Saturday, August 6, 2016 at 11:19:03 AM UTC+2, Johan S. R. Nielsen wrote:
>
> It would be really useful if the dependencies were filtered out as well.
No, because dependencies are not static. You can e.g. delete the branch
from a dependency after the dependent ticket has been reviewed...
--
> Though really you want to know "what would be added if the ticket were
> merged right now" which is, in general, not a single git query (for
> starters merge can fail but git can diff anything). This is what clicking
> on the branch in trac does.
This shows the diff of the current ticket + pl
Since cgit doesn't know when you want the diff to start it can't really
display anything more useful.
You can add e.g. &id2=develop to the URL to specify the starting point, e.g.
https://git.sagemath.org/sage.git/diff/?h=e5fc48064b490ac4e4bdc432885b38c0eaea3e27&id2=develop
Though really you wan
24 matches
Mail list logo
