[sage-devel] Re: SPKG Maintainers??

[Marc Mezzarobba]

William Stein wrote:
> If somebody explicitly puts their name in the AUTHORS block when they
> are writing the code in the first place, then we should respect that
> and continue to acknowledge them.

I agree with that part. It would be wrong to remove the AUTHORS blocks 
without putting corresponding acklowledgements in an equally prominent 
place.

-- 
Marc

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: SPKG Maintainers??

[Marc Mezzarobba]

Simon King wrote:
> it is also supposed to say *who* did *what* ("what" meaning the
> purpose/intention of the change)

Commit messages too, and I'd argue they are the right place to do 
that...

(Incidentally, I'm not sure git blame would be the right tool if we did 
want to auto-generate author information for the reference manual. 
Something like git shortlog looks like a better starting point to me. It 
could perhaps combined with some kind of weighting of commits and/or the 
ability to use meta-information extracted from the commit message.)

-- 
Marc

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SPKG Maintainers??

[Jori Mäntysalo]

On Mon, 21 Sep 2015, Marc Mezzarobba wrote:

I agree with that part. It would be wrong to remove the AUTHORS blocks 
without putting corresponding acklowledgements in an equally prominent 
place.


What if I do a small change? Not enought to mention, but something 
potentially stupid. I don't want others to be blamed for something I have 
done.


--
Jori Mäntysalo

[sage-devel] Re: What can we assume about our C compiler

[Ralf Stephan]

On Monday, September 21, 2015 at 6:38:50 PM UTC+2, Volker Braun wrote:
> Afaik we already require C++11 support to compile Pynac 

Yes, Pynac git master requires it but we're still installing backported 
versions (0.3.9.x vs 0.4.x).

The ticket that never got finished was
http://trac.sagemath.org/ticket/18323

Regards,

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What can we assume about our C compiler

[Ralf Stephan]

On Tuesday, September 22, 2015 at 5:47:39 AM UTC+2, François wrote:
>
> The 0.4.x branch of pynac needs c++11 and the “override” keyword. 
>

That is not true. I explicitly held back because without
override gcc 4.6 would suffice.
 

> 1) Do we want to mandate c++11 support 
> Y[X] 
> N[ ]


Because it was requested several times, see also
https://groups.google.com/forum/#!topic/sage-devel/Dk-M5bt-uf8/discussion 
 

> 2) if yes what c++11 features do we want? 
> Feature complete [ ] 
> List of features [ ] (list needed features) 
>  * override 
>

Override not necessary for Pynac

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] access denied on git

[Vincent Delecroix]

How did you configure git? What gives

  $ git remote -v

Vincent

On 21/09/15 21:54, Mike Zabrocki wrote:

I mistakenly installed XCode 7 and so to save myself I started working on a
fresh copy of sage where I don't do too much compiling.

In doing so I seem to have messed up my permissions to access git (or
something).  I can checkout any branch I like, but I can't seem to push.

$ git push

fatal: remote error: access denied or repository not exported: /sage.git

I thought it might be my ssh key, but I can authenticate:

$ ssh g...@trac.sagemath.org info

hello zabrocki, this is git@trac running gitolite3 (unknown) on git 1.7.9.5


  R W sage

Does anyone have an idea about what I am doing wrong?

Thanks.
-Mike



--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: access denied on git

[John H Palmieri]

On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote:
>
> I mistakenly installed XCode 7 and so to save myself I started working on 
> a fresh copy of sage where I don't do too much compiling.
>

Have you tried running Xcode once? It will install some command-line tools, 
and that may be what is necessary.

  John


 

>
> In doing so I seem to have messed up my permissions to access git (or 
> something).  I can checkout any branch I like, but I can't seem to push.
>
> $ git push
>
> fatal: remote error: access denied or repository not exported: /sage.git
>
> I thought it might be my ssh key, but I can authenticate:
>
> $ ssh g...@trac.sagemath.org  info
>
> hello zabrocki, this is git@trac running gitolite3 (unknown) on git 1.7.9.5
>
>
>  R W sage
>
> Does anyone have an idea about what I am doing wrong?
>
> Thanks.
> -Mike
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: access denied on git

[R. Andrew Ohana]

You are using the read only git url, you need to use the ssh url to be able
to push. You can either add a new remote:

git remote add trac g...@trac.sagemath.org:sage.git

or modify your current remote:

git remote set-url origin g...@trac.sagemath.org:sage.git


On Mon, Sep 21, 2015 at 7:16 PM, Mike Zabrocki 
wrote:

> With some further experimenting I find that I can push from my old copy of
> sage (but I can't compile there).
>
> I can edit and compile on one copy of sage and push with another.  This is
> an awkward setup, but at least I can some edits to a ticket done.
> -Mike
>
>
> On Monday, 21 September 2015 21:57:10 UTC-4, Mike Zabrocki wrote:
>>
>> You are right that running Xcode did install the command line tools, but
>> that did not seem to fix the problem.
>> I continue to get the "fatal: remote error: access denied or repository
>> not exported: /sage.git" message.
>> -Mike
>>
>> On Monday, 21 September 2015 21:21:45 UTC-4, John H Palmieri wrote:
>>>
>>>
>>>
>>> On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote:

 I mistakenly installed XCode 7 and so to save myself I started working
 on a fresh copy of sage where I don't do too much compiling.

>>>
>>> Have you tried running Xcode once? It will install some command-line
>>> tools, and that may be what is necessary.
>>>
>>>   John
>>>
>>>
>>>
>>>

 In doing so I seem to have messed up my permissions to access git (or
 something).  I can checkout any branch I like, but I can't seem to push.

 $ git push

 fatal: remote error: access denied or repository not exported: /sage.git

 I thought it might be my ssh key, but I can authenticate:

 $ ssh g...@trac.sagemath.org info

 hello zabrocki, this is git@trac running gitolite3 (unknown) on git
 1.7.9.5


  R W sage

 Does anyone have an idea about what I am doing wrong?

 Thanks.
 -Mike

>>> --
> 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, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SPKG Maintainers??

[William Stein]

On Mon, Sep 21, 2015 at 7:58 PM, Kwankyu Lee  wrote:
> I have written a couple of AUTHORS-blocks, but I think I did it not to have
> a credit but to be responsible for the code.
>
> AUTHORS blocks are rather for developers, not for end users.
These blocks
> are rather hindrance for end users as  they usually appear at the head of a

When I "invented" this idea of AUTHORS blocks, they were definitelynot
only for developers but also for end users.They were partly meant
as an antidote to what happened with Magma when "they" deleted all the
names of many of the contributors to Magma from the beginnings of the
relevant sections of the reference manual, which pissed a lot of
contributors off.

When you read a mathematics paper you don't say "this statement of the
authors of this paper at the top is not for readers and is a
hindrance".

If anything, I think we should systematically do vastly *more* to
clearly acknowledge and appreciate the code contributors to Sage.
They are by far the most important people to the existence of Sage.

 -- William

> documentation but these information, like TODO and TESTS, is not usually
> what the user expects to see in the doc.  These developer-oriented blocks
> are better to be hidden or placed in less prominent place for the end users.
>
> --
> 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, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William (http://wstein.org)

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What can we assume about our C compiler

[Francois Bissey]

We should make a decision on what level of c++ support we want. 
The 0.4.x branch of pynac needs c++11 and the “override” keyword.
I don’t think Nathann  ever mentioned which c++11 feature he wanted,
he probably just assumed that having a c++11 flag was enough.

Another thing to be cautious of: gcc 4.8, 4.9 and 5.x have different c++11
ABI. Which means that if you install sage with one then change compiler
you may be in trouble as soon as you try to re-install or upgrade something
that use c++11.

So I guess there are two questions:
1) Do we want to mandate c++11 support
Y[ ]
N[ ]

2) if yes what c++11 features do we want?
Feature complete [ ]
List of features [ ] (list needed features)
 * override

François
 
> On 22/09/2015, at 15:27, Ralf Stephan  wrote:
> 
> On Monday, September 21, 2015 at 6:38:50 PM UTC+2, Volker Braun wrote:
>> Afaik we already require C++11 support to compile Pynac 
> 
> Yes, Pynac git master requires it but we're still installing backported 
> versions (0.3.9.x vs 0.4.x).
> 
> The ticket that never got finished was
> http://trac.sagemath.org/ticket/18323
> 
> Regards,
> 
> -- 
> 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, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What can we assume about our C compiler

[Francois Bissey]

> On 22/09/2015, at 17:13, Ralf Stephan  wrote:
> 
> On Tuesday, September 22, 2015 at 5:47:39 AM UTC+2, François wrote:
> The 0.4.x branch of pynac needs c++11 and the “override” keyword. 
> 
> That is not true. I explicitly held back because without
> override gcc 4.6 would suffice.

OK but I don’t think you should hold back personally.

François

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SPKG Maintainers??

[Dima Pasechnik]

On Monday, 21 September 2015 21:42:31 UTC-7, William wrote:
>
> On Mon, Sep 21, 2015 at 7:58 PM, Kwankyu Lee  > wrote: 
> > I have written a couple of AUTHORS-blocks, but I think I did it not to 
> have 
> > a credit but to be responsible for the code. 
> > 
> > AUTHORS blocks are rather for developers, not for end users. 
> These blocks 
> > are rather hindrance for end users as  they usually appear at the head 
> of a 
>
> When I "invented" this idea of AUTHORS blocks, they were definitelynot 
> only for developers but also for end users.They were partly meant 
> as an antidote to what happened with Magma when "they" deleted all the 
> names of many of the contributors to Magma from the beginnings of the 
> relevant sections of the reference manual, which pissed a lot of 
> contributors off. 
>
> When you read a mathematics paper you don't say "this statement of the 
> authors of this paper at the top is not for readers and is a 
> hindrance". 
>
> If anything, I think we should systematically do vastly *more* to 
> clearly acknowledge and appreciate the code contributors to Sage. 
> They are by far the most important people to the existence of Sage. g
>

I know at least one prolific Sage contributor who does not add himself to 
AUTHORS block,
and actually is removing these blocks.

IMHO we need an official policy on this. 



>  -- William 
>
> > documentation but these information, like TODO and TESTS, is not usually 
> > what the user expects to see in the doc.  These developer-oriented 
> blocks 
> > are better to be hidden or placed in less prominent place for the end 
> users. 
> > 
> > -- 
> > 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, send 
> an 
> > email to sage-devel+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> William (http://wstein.org) 
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] access denied on git

[Mike Zabrocki]

I mistakenly installed XCode 7 and so to save myself I started working on a 
fresh copy of sage where I don't do too much compiling.

In doing so I seem to have messed up my permissions to access git (or 
something).  I can checkout any branch I like, but I can't seem to push.

$ git push

fatal: remote error: access denied or repository not exported: /sage.git

I thought it might be my ssh key, but I can authenticate:

$ ssh g...@trac.sagemath.org info

hello zabrocki, this is git@trac running gitolite3 (unknown) on git 1.7.9.5


 R W sage

Does anyone have an idea about what I am doing wrong?

Thanks.
-Mike

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage -i annoying

[Simon King]

Hi Jeroen,

On 2015-09-21, Jeroen Demeyer  wrote:
> On 2015-09-21 11:37, Simon King wrote:
>> Hi!
>>
>> It seems that in the latest beta there was a change in "sage -i"
> Certainly, see
> https://groups.google.com/forum/#!topic/sage-devel/nLDOLvjKp3A
>
>> First it does make -j2 configure.
>>
>> Then, it does make -j2 configure!
>>
>> Then, it does make -j2 configure!!
> Three times is surprising, are you sure you counted correctly?

Yes. I started in a new terminal session, and after installing the
package I searched "make -j2 configure". I really find THREE hits.

> I can 
> understand 2 (once for the toolchain, once for the package itself), but 
> 3 is a bug. I've just tried with the latest branch at #12103, and I see 
> "make configure" only twice.

Strange.

>> all what I want to do is to
>> install an optional package that has no dependencies
> Meataxe from #12103 does not have a "dependencies" file, so the default 
> dependencies for optional packages are used: the default is that the 
> package requires all standard packages to be up-to-date, so it has to 
> run cython... If you really want no dependencies, then add a file 
> build/pkgs/meataxe/dependencies saying "# no dependencies". I agree that 
> this isn't documented.

It did help against the cython thingy (so, forget what I said on the
ticket: It did partially help), but three times make -j2 configure
pertains.

Best regards,
Simon

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -i annoying

[Jeroen Demeyer]

On 2015-09-21 15:04, Jori Mäntysalo wrote:

I don't know exactly what has happened, but at least on my systems
compiling is more frequently needed, i.e. sage -b is not enough.


Did you run "make" before (or "make build" if you don't want to wait for 
the doc)?


You can use "./sage -b" if, since the last time you ran make, you made 
only changes to the Sage library. Your workflow should look like:


1) checkout ticket or branch
2) make build (or make doc-clean; make)
3) run ./sage or ./sage -t or similar
4) edit Sage library files
5) ./sage -b
6) goto 3

If you're skipping step 2, it's not surprising that bad things happen.

--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: What can we assume about our C compiler

[Jean-Pierre Flori]

On Monday, September 21, 2015 at 1:47:17 PM UTC+2, Nathann Cohen wrote:
>
> Hello everybody, 
>
> What can we assume on our C compiler? Is it always gcc? Is it always 
> recent? 
>
> I guess the configure script is made to check it is recent enough and 
provides what is needed to build Sage.
Or at least that it can build our GCC.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: What can we assume about our C compiler

[Nathann Cohen]

>
> I guess the configure script is made to check it is recent enough and 
> provides what is needed to build Sage.
> Or at least that it can build our GCC.
>

I want to know if I can compile c++ files with -std=c++11.

Nathann

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage -i annoying

[Simon King]

On 2015-09-21, Jeroen Demeyer  wrote:
> When complaining about a command, could you mention the *exact* command 
> you're talking about. I assume it's not just "sage -i"?

  ./sage -i meataxe
respectively
  ./sage -i -c meataxe
(working on #12103).

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What can we assume about our C compiler

[Jeroen Demeyer]

On 2015-09-21 13:47, Nathann Cohen wrote:

Hello everybody,

What can we assume on our C compiler? Is it always gcc?


First of all, compiler choices can always be overridden using SAGE_PORT 
or SAGE_INSTALL_GCC. But let's assume that those variables are undefined.


In that case, you can assume that the compiler is GCC-compatible, so it 
could be GCC or it could be Clang or possibly a different compiler (ICC 
maybe?). The version is at least version 4.4 (but not 4.6)


That being said, if there is some future which really requires a more 
recent compiler (say, for C++11 support), I wouldn't mind updating the 
prerequisites.


Note that this talks only about the compiler, which is just one piece of 
the toolchain. Many compatibility problems are in fact due to the 
linker, where less assumptions can be made.



Jeroen.

--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: What can we assume about our C compiler

[Nathann Cohen]

> Then why didn't you just ask that right away?

- Because I can deduce my answer from the version of GCC (if we always
compile with GCC).
- Because whoever knows the version of GCC may not know if it supports
C++11, and so may not answer.
- Because knowing the version of GCC is of a wider use than just
knowing if it supports C++11, and could help others if found on our
mailing-list.

> If you're serious about C++11 support, please open a ticket and we can
> continue discussing there.

It seems from your answer that we cannot assume that. If so, what are
the assumptions that we can make on our compiler? Is it always gcc? Do
we know that it will always be more recent than some specific version?

Thanks,

Nathann

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -i annoying

[Jeroen Demeyer]

On 2015-09-21 11:37, Simon King wrote:

Hi!

It seems that in the latest beta there was a change in "sage -i"

Certainly, see
https://groups.google.com/forum/#!topic/sage-devel/nLDOLvjKp3A


First it does make -j2 configure.

Then, it does make -j2 configure!

Then, it does make -j2 configure!!
Three times is surprising, are you sure you counted correctly? I can 
understand 2 (once for the toolchain, once for the package itself), but 
3 is a bug. I've just tried with the latest branch at #12103, and I see 
"make configure" only twice.



all what I want to do is to
install an optional package that has no dependencies
Meataxe from #12103 does not have a "dependencies" file, so the default 
dependencies for optional packages are used: the default is that the 
package requires all standard packages to be up-to-date, so it has to 
run cython... If you really want no dependencies, then add a file 
build/pkgs/meataxe/dependencies saying "# no dependencies". I agree that 
this isn't documented.



Do other people not find it annoying?

In case you do, please review #19043 which fixes this.

--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: What can we assume about our C compiler

[Jeroen Demeyer]

On 2015-09-21 14:12, Nathann Cohen wrote:

I want to know if I can compile c++ files with -std=c++11.


Then why didn't you just ask that right away?

If you're serious about C++11 support, please open a ticket and we can 
continue discussing there.


--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] SageMath foundation

[Samuel Lelievre]

Starting a new thread from a discussion at
https://groups.google.com/d/msg/sage-devel/Jot2ydQjIhk/ZF16lHUzAQAJ


2015-09-17 16:45:53 UTC+2, William:

On Thu, Sep 17, 2015 at 7:34 AM, kcrisman  wrote: 
>
> > it would be useful to revive the discussion of a 
> > true SageMath Foundation, separate from SMCI of course, whether 
> incorporated 
> > in the US or Europe (or elsewhere), but it sounds like there wasn't 
> > currently enough interest in helping with the substantial paperwork 
> involved 
> > in this as of yet.  But if this existed it might help support some of 
> the 
> > other Sage infrastructure needs, beyond the *.math.washington.edu 
> resources 
> > this thread was supposed to be about :) 
>
> Such a foundation isn't going to happen any time soon, at least not 
> with me the one doing it.  I talked extensively with a partner at 
> Fenwick & West, and was advised that it is currently basically 
> impossible for an "Open Source Software Not for profit" to get 501c3 
> status these days in the US.  The IRS used to look favorably on such 
> things a few years ago (e.g., Mozilla!), but now looks very 
> unfavorably on open source as being "not for profit" (things that are 
> political can change dramatically from one point in time to another). 
> I didn't believe this could be the case, but the Fenwick & West partner is 
> a top expert who is very familiar with what is going on, and she 
> repeatedly clarified that it is.  She suggested starting a 501c3 that 
> has nothing to do with Sage, and also doesn't have the word "Sage" in 
> its title 
> would be the only reasonable strategy... and maybe later it would get 
> involved with supporting Sage.  Even doing that, the work 
> involved is more than starting a company, and the rules are tricky 
> involving taxes, so I definitely don't have the time to do that now. 
>
> For all it's cons, University of Washington does at least administer 
> the "Sage Foundation" budget very professionally, they don't charge 
> anything in overhead (absolutely 100% of donations are  spent on sage 
> activities with no cut at all), and they take care of all the 
> dispersement of funds to people (e.g., participants of "Women in Sage" 
> Sage days -- often funded from this, bits of hardware we need for a 
> conference, etc.).One drawback is their stupid "please donate 
> again" mailing list. 
>
>  - William
>

On the USA side of things, the NumFOCUS Foundation

http://numfocus.org/
https://groups.google.com/forum/#!forum/numfocus

seems to support quite a number of open-source science projects

http://numfocus.org/projects/

and it might be worth investigating the possibility for SageMath
to become one of their "fiscally sponsored projects" or of their
"other supported projects".

Samuel

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -i annoying

[Jori Mäntysalo]

On Mon, 21 Sep 2015, Jeroen Demeyer wrote:

Three times is surprising, are you sure you counted correctly? I can 
understand 2 (once for the toolchain, once for the package itself), but 
3 is a bug. I've just tried with the latest branch at #12103, and I see 
"make configure" only twice.


I don't know exactly what has happened, but at least on my systems 
compiling is more frequently needed, i.e. sage -b is not enought. Also 
once I got ImportError from Config and had to do make clean; might be 
related to this, or might not be.


--
Jori Mäntysalo

[sage-devel] What can we assume about our C compiler

[Nathann Cohen]

Hello everybody,

What can we assume on our C compiler? Is it always gcc? Is it always recent?

Nathann

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: access denied on git

[Mike Zabrocki]

You are right that running Xcode did install the command line tools, but 
that did not seem to fix the problem.
I continue to get the "fatal: remote error: access denied or repository not 
exported: /sage.git" message.
-Mike

On Monday, 21 September 2015 21:21:45 UTC-4, John H Palmieri wrote:
>
>
>
> On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote:
>>
>> I mistakenly installed XCode 7 and so to save myself I started working on 
>> a fresh copy of sage where I don't do too much compiling.
>>
>
> Have you tried running Xcode once? It will install some command-line 
> tools, and that may be what is necessary.
>
>   John
>
>
>  
>
>>
>> In doing so I seem to have messed up my permissions to access git (or 
>> something).  I can checkout any branch I like, but I can't seem to push.
>>
>> $ git push
>>
>> fatal: remote error: access denied or repository not exported: /sage.git
>>
>> I thought it might be my ssh key, but I can authenticate:
>>
>> $ ssh g...@trac.sagemath.org info
>>
>> hello zabrocki, this is git@trac running gitolite3 (unknown) on git 
>> 1.7.9.5
>>
>>
>>  R W sage
>>
>> Does anyone have an idea about what I am doing wrong?
>>
>> Thanks.
>> -Mike
>>
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SPKG Maintainers??

[Kwankyu Lee]

I have written a couple of AUTHORS-blocks, but I think I did it not to have 
a credit but to be responsible for the code. 

AUTHORS blocks are rather for developers, not for end users. These blocks 
are rather hindrance for end users as  they usually appear at the head of a 
documentation but these information, like TODO and TESTS, is not usually 
what the user expects to see in the doc.  These developer-oriented blocks 
are better to be hidden or placed in less prominent place for the end users.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] access denied on git

[Mike Zabrocki]

Does it help to see my .gitconfig file?  This hasn't changed though.

[core]

editor = vi

[user]

name = zabrocki

email = zabro...@mathstat.yorku.ca

[alias]

wdiff = diff --color-words

lg = log --graph --pretty=format:'%Cred%h%Creset 
-%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)[%an]%Creset' 
--abbrev-commit --date=relative

rls = ls-remote origin

lscombinat = ls-remote origin '*combinat*'

[push]

default = upstream

[merge]

log = true


On Monday, 21 September 2015 21:10:43 UTC-4, Mike Zabrocki wrote:
>
> $ git remote -v 
>
> origin git://trac.sagemath.org/sage.git (fetch)
>
> origin git://trac.sagemath.org/sage.git (push)
>
>
>
> On Monday, 21 September 2015 21:02:16 UTC-4, vdelecroix wrote:
>>
>> How did you configure git? What gives 
>>
>>$ git remote -v 
>>
>> Vincent 
>>
>> On 21/09/15 21:54, Mike Zabrocki wrote: 
>> > I mistakenly installed XCode 7 and so to save myself I started working 
>> on a 
>> > fresh copy of sage where I don't do too much compiling. 
>> > 
>> > In doing so I seem to have messed up my permissions to access git (or 
>> > something).  I can checkout any branch I like, but I can't seem to 
>> push. 
>> > 
>> > $ git push 
>> > 
>> > fatal: remote error: access denied or repository not exported: 
>> /sage.git 
>> > 
>> > I thought it might be my ssh key, but I can authenticate: 
>> > 
>> > $ ssh g...@trac.sagemath.org info 
>> > 
>> > hello zabrocki, this is git@trac running gitolite3 (unknown) on git 
>> 1.7.9.5 
>> > 
>> > 
>> >   R W sage 
>> > 
>> > Does anyone have an idea about what I am doing wrong? 
>> > 
>> > Thanks. 
>> > -Mike 
>> > 
>>
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: access denied on git

[Mike Zabrocki]

With some further experimenting I find that I can push from my old copy of 
sage (but I can't compile there).

I can edit and compile on one copy of sage and push with another.  This is 
an awkward setup, but at least I can some edits to a ticket done.
-Mike

On Monday, 21 September 2015 21:57:10 UTC-4, Mike Zabrocki wrote:
>
> You are right that running Xcode did install the command line tools, but 
> that did not seem to fix the problem.
> I continue to get the "fatal: remote error: access denied or repository 
> not exported: /sage.git" message.
> -Mike
>
> On Monday, 21 September 2015 21:21:45 UTC-4, John H Palmieri wrote:
>>
>>
>>
>> On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote:
>>>
>>> I mistakenly installed XCode 7 and so to save myself I started working 
>>> on a fresh copy of sage where I don't do too much compiling.
>>>
>>
>> Have you tried running Xcode once? It will install some command-line 
>> tools, and that may be what is necessary.
>>
>>   John
>>
>>
>>  
>>
>>>
>>> In doing so I seem to have messed up my permissions to access git (or 
>>> something).  I can checkout any branch I like, but I can't seem to push.
>>>
>>> $ git push
>>>
>>> fatal: remote error: access denied or repository not exported: /sage.git
>>>
>>> I thought it might be my ssh key, but I can authenticate:
>>>
>>> $ ssh g...@trac.sagemath.org info
>>>
>>> hello zabrocki, this is git@trac running gitolite3 (unknown) on git 
>>> 1.7.9.5
>>>
>>>
>>>  R W sage
>>>
>>> Does anyone have an idea about what I am doing wrong?
>>>
>>> Thanks.
>>> -Mike
>>>
>>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] access denied on git

[Mike Zabrocki]

$ git remote -v 

origin git://trac.sagemath.org/sage.git (fetch)

origin git://trac.sagemath.org/sage.git (push)



On Monday, 21 September 2015 21:02:16 UTC-4, vdelecroix wrote:
>
> How did you configure git? What gives 
>
>$ git remote -v 
>
> Vincent 
>
> On 21/09/15 21:54, Mike Zabrocki wrote: 
> > I mistakenly installed XCode 7 and so to save myself I started working 
> on a 
> > fresh copy of sage where I don't do too much compiling. 
> > 
> > In doing so I seem to have messed up my permissions to access git (or 
> > something).  I can checkout any branch I like, but I can't seem to push. 
> > 
> > $ git push 
> > 
> > fatal: remote error: access denied or repository not exported: /sage.git 
> > 
> > I thought it might be my ssh key, but I can authenticate: 
> > 
> > $ ssh g...@trac.sagemath.org  info 
> > 
> > hello zabrocki, this is git@trac running gitolite3 (unknown) on git 
> 1.7.9.5 
> > 
> > 
> >   R W sage 
> > 
> > Does anyone have an idea about what I am doing wrong? 
> > 
> > Thanks. 
> > -Mike 
> > 
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What can we assume about our C compiler

[Dr. David Kirkby (Kirkby Microwave Ltd)]

On 21 Sep 2015 13:58, "Thierry Dumont"  wrote:
>
> Le 21/09/2015 14:16, Jeroen Demeyer a écrit :
> > On 2015-09-21 13:47, Nathann Cohen wrote:
> >> Hello everybody,
> >>
> >> What can we assume on our C compiler? Is it always gcc?
> >

> Did anybody tried ICC ? I can do it, for fun...

For what it is worth,  I have tried compilers from Sun on Solaris, HP on
HP-UX and IBM on AIX.

I never managed to compile Sage on AIX or HP-UX, although I got much
further with GCC  than with the IBM or HP compilers. Essentially the HP and
IBM reject all the GNUisms.

Although Sage used to build fine on Solaris and pass all doctests, this was
only possible with GCC. Now Sun (now Oracle) did produce a compiler with a
GCC  parser, so it accepted the GNUisms, but used the native back end to
produce faster code than GCC. I never tried building Sage with that.

I think it is fairly safe to say that you can't build Sage with a compiler
that is not in some way based on gcc.

Dave.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Default precision for floats

[rjf]

>
>
>
> > 
> >(Richard)  While it is tempting to add every possible tool to Sage, 
> thinking out of the 
> > box can be productive. 
> > 
> > (one answer:  there is a bootstrapping problem if you have to have a 
> working 
> > Sage in order to build a working Sage.) 
>
> (William)One answer to what?  Huh? 
>

Oh, sorry, I edited out a snarky paragraph there, and should have either 
left
a tendril of it or edited out more.

Here's the question, roughly.  Why not put everything  (make, config, 
compilers etc into python,
and have one huge unified Sage system in which there is a command "make me 
a new Sage system".
(There were/ maybe still are?  some systems of that nature in the Lisp 
world.)

So now you can read the answer.
 
RJF
 

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Default precision for floats

[William Stein]

On Monday, September 21, 2015, rjf  wrote:

>
>
>>
>>
>> >
>> >(Richard)  While it is tempting to add every possible tool to Sage,
>> thinking out of the
>> > box can be productive.
>> >
>> > (one answer:  there is a bootstrapping problem if you have to have a
>> working
>> > Sage in order to build a working Sage.)
>>
>> (William)One answer to what?  Huh?
>>
>
> Oh, sorry, I edited out a snarky paragraph there, and should have either
> left
> a tendril of it or edited out more.
>
> Here's the question, roughly.  Why not put everything  (make, config,
> compilers etc into python,
> and have one huge unified Sage system in which there is a command "make me
> a new Sage system".
> (There were/ maybe still are?  some systems of that nature in the Lisp worl
>

We already have that. Since 2005.  But you wouldn't know since you have
evidently never installed (or used) sage.



>
> So now you can read the answer.
>
> RJF
>
>
> --
> 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, send an
> email to sage-devel+unsubscr...@googlegroups.com
> 
> .
> To post to this group, send email to sage-devel@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my massive iPhone 6 plus.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: What can we assume about our C compiler

[Volker Braun]

Afaik we already require C++11 support to compile Pynac 
(https://groups.google.com/d/msg/sage-devel/DeT2E8IzTGs/Z_GDKbh06X8J). If 
not then we *should* require C++11 because its much better than without...


On Monday, September 21, 2015 at 1:47:17 PM UTC+2, Nathann Cohen wrote:
>
> Hello everybody, 
>
> What can we assume on our C compiler? Is it always gcc? Is it always 
> recent? 
>
> Nathann 
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Help SageMath-Android

[Matematica]

I installed 
SageMath https://play.google.com/store/apps/details?id=org.sagemath.droid 
on my phone Samsung mini2 
http://www.gsmarena.com/samsung_galaxy_mini_2_s6500-3883.php
I get the error from of the attached images. Thanks.


-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install

[Jeroen Demeyer]

On 2015-09-21 19:23, Bill Janssen wrote:

On OS X, The CasADi subsystem now installs its dynamic
libraries in a subdirectory of JModelica, a subdirectory which then has
to be put on the LD_LIBRARY_PATH the Python interpreter is run with
That is clearly an issue with the build system. Instead of requiring 
Sage to change sage-env, it would be better to report this problem 
upstream. Libraries should be installed in the standard places, such 
that no special LD_LIBRARY_PATH hacks are needed.


--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -i annoying

[Jori Mäntysalo]

On Mon, 21 Sep 2015, Jeroen Demeyer wrote:


Your workflow should look like:

1) checkout ticket or branch
2) make build (or make doc-clean; make)

If you're skipping step 2, it's not surprising that bad things happen.


OK. Before it has more often worked with just ./sage -b and I think that 
also make has been much faster. But so I'll run make after checkout from 
not on.


--
Jori Mäntysalo

[sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install

[Bill Janssen]

I'm updating an old-style JModelica spkg to version 1.16, which just came 
out.  On OS X, The CasADi subsystem now installs its dynamic libraries in a 
subdirectory of JModelica, a subdirectory which then has to be put on the 
LD_LIBRARY_PATH the Python interpreter is run with, as CasADi is packaged 
as a Python extension.

There seems to be no standardized way of hacking the LD_LIBRARY_PATH to 
include directories required by a new Python extension.  Am I missing 
something?  Is there a better way to do this than adding a sed script to 
hack sage-env?

Bill

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage -i annoying

[Nathann Cohen]

>
> Do other people not find it annoying? 


I just tried to install a package that was already installed. It takes 
around 10 seconds on my computer (I was lucky, it did not try to compare 
the speed of all mirrors this time - that takes ages) and filled several 
screens with unrelated data. Let's settle for "annoying".

Nathann 

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sagemath-admins] Re: [sage-devel] Re: *.math.washington.edu hardware resources

[Samuel Lelievre]

Le mercredi 16 septembre 2015 19:13:42 UTC+2, William a écrit :

Let's plan to have a page describing the compute resources and 
> acknowledging *everybody* (or organization) that contributes to having 
> bought them, hosting them, and helping to run them. 
>
> William
>

We could use

http://wiki.sagemath.org/Infrastructure

for that purpose. 

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: SPKG Maintainers??

[William Stein]

On Mon, Sep 21, 2015 at 1:17 AM, Jori Mäntysalo  wrote:
> On Mon, 21 Sep 2015, Marc Mezzarobba wrote:
>
>> I agree with that part. It would be wrong to remove the AUTHORS blocks
>> without putting corresponding acklowledgements in an equally prominent
>> place.
>
>
> What if I do a small change? Not enought to mention, but something
> potentially stupid. I don't want others to be blamed for something I have
> done.
>

If it is serious enough that "blame" is involved, then people are
going to use "git blame" to see exactly who did it.  If the person
listed in AUTHORS were contacted, they could also defend themselves by
using "git blame."

William

> --
> Jori Mäntysalo



-- 
William (http://wstein.org)

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] sage -i annoying

[Simon King]

Hi!

It seems that in the latest beta there was a change in "sage -i" that I
find rather annoying: First it does make -j2 configure. Result: Nothing
to (re)build / all up-to-date. Which takes a couple of seconds

Then, it does make -j2 configure! Result: Sage build/upgrade complete!
Which again takes a couple of seconds.

Then, it does make -j2 configure!! This time, it does not immediately
(after printing all environment variables) recognise that the Sage build
is complete, but it does
  python -u setup.py install
  Updating Cython code
  Enabling Cython debugging support
  Finished Cythonizing, time: 11.00 seconds.

What? 11 seconds for nothing (because all what I want to do is to
install an optional package that has no dependencies)??

Furthermore, "of course", we are "running install_data".

And only after all that complete waste of time, which on my laptop in
total takes nearly a minute, Sage finally starts to do what I asked
it to, namely install the package.

Do other people not find it annoying?

Best regards,
Simon


-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Help SageMath-Android

[Andrey Novoseltsev]

Can someone with an Android system take a look at this? Is it device 
specific or the same strange thing happens for everybody?

On Monday, 21 September 2015 11:15:07 UTC-6, Matematica wrote:
>
> I installed SageMath 
> https://play.google.com/store/apps/details?id=org.sagemath.droid on my 
> phone Samsung mini2 
> http://www.gsmarena.com/samsung_galaxy_mini_2_s6500-3883.php
> I get the error from of the attached images. Thanks.
>
>
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -i annoying

[Jeroen Demeyer]

When complaining about a command, could you mention the *exact* command 
you're talking about. I assume it's not just "sage -i"?


--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What can we assume about our C compiler

[Thierry Dumont]

Le 21/09/2015 14:16, Jeroen Demeyer a écrit :
> On 2015-09-21 13:47, Nathann Cohen wrote:
>> Hello everybody,
>>
>> What can we assume on our C compiler? Is it always gcc?
> 
> First of all, compiler choices can always be overridden using SAGE_PORT
> or SAGE_INSTALL_GCC. But let's assume that those variables are undefined.
> 
> In that case, you can assume that the compiler is GCC-compatible, so it
> could be GCC or it could be Clang or possibly a different compiler (ICC
> maybe?). The version is at least version 4.4 (but not 4.6)
> 

Did anybody tried ICC ? I can do it, for fun...

t.d.
> That being said, if there is some future which really requires a more
> recent compiler (say, for C++11 support), I wouldn't mind updating the
> prerequisites.
> 
> Note that this talks only about the compiler, which is just one piece of
> the toolchain. Many compatibility problems are in fact due to the
> linker, where less assumptions can be made.
> 
> 
> Jeroen.
> 

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
<>