Re: [sage-support] Writing 'n' variables in Sagemath linux ubuntu

[Jori Mäntysalo]

If I understood this, isn't

var(['a'+str(i) for i in range(1,4)])

what is wanted? It will make a1, a2 and a3 to variables.

--
Jori Mäntysalo

[sage-support] Re: Getting a Symbolic version of a Sum

[saad khalid]

I asked the list and here was the response I got. Personally, I think that 
it would be a good idea, but I don't know how to implement it myself.

"The besselexpand is an option variable in maxima core (part of the bessel 
function package) and simplify_sum is a share package. In general I think 
that share packages should not modify core options when it is not 
necessary. And I think functions in general should not change option 
variables so that the user can't control them. So the reason why 
simplify_sum doesn't change besselexpand to true is not because I know of 
some problems with it, but because I try to avoid such behaviour of 
functions (I knew that simplify_sum would return nicer results with 
besselexpand:true when I wrote that part of simplify_sum).

But maybe this is a situation in which changing global option variables 
should be allowed from a function.

HTH,
Andrej"


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage 7.0 crashes

[Juan Luis Varona]

I have been able to compile Sage 7.0 from the source code in my MacBook Air 
(late 2010).

Now, it works in Terminal, and if I use notebook() I obtain the traditional 
notebook interface.

But I do not know how to obtain the SageMath.app. There is a simple 
description of how to do it in any place? (I'm not a prgramming expert)

Moreover, how is possible to use the jupiter interface?

Thanks,

Juan Luis

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] console prompt color

[Volker Braun]

On Tuesday, January 26, 2016 at 5:09:52 PM UTC-5, Michael Orlitzky wrote:
>
> You're just using "reasonable" to mean "has the color scheme I like." 
>

That black text on white background is the most legible color scheme is an 
empirical fact.

Also, IPython alone also defaults to using colors. Changing colors is also 
exacly the same as in plain IPython.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] console prompt color

[Michael Orlitzky]

On 01/26/2016 03:30 PM, Volker Braun wrote:
> On Tuesday, January 26, 2016 at 12:16:01 PM UTC-5, Michael Orlitzky wrote:
> 
> The default should be NoColor, since whatever color scheme we choose is
> going to be awful for a large number of users.
> 
> 
> I disagree, the default should be good on white background. Every
> reasonable terminal uses that by default as UX research time again
> proved that this is the most readable color scheme. 
> 

You're just using "reasonable" to mean "has the color scheme I like."
We're not talking about a major improvement for the people who use a
light background. It's eye candy, at the cost of catastrophic failure on
terminals with dark backgrounds. Most people who start sage and see
dark-blue-on-black aren't going to go find a mailing list, sign up, and
ask for the secret commands to make it work the way it should already.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Volker Braun]

I created http://trac.sagemath.org/ticket/19967 for dealing with cliquer


On Tuesday, January 26, 2016 at 3:36:24 PM UTC-5, Volker Braun wrote:
>
> For the record, the OSX binaries are broken because cliquer fails to 
> install; the log contains:
>
> error: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool:
>  
> changing install names or rpaths can't be redone for: 
> /Users/vbraun/Code/binary-pkg/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidmas391yaj24ng0bmdu/local/lib/libcliquer.dylib
>  
> (for architecture x86_64) because larger updated load commands do not fit 
> (the program must be relinked, and you may need to use -headerpad or 
> -headerpad_max_install_names)
>
> Of course errors are not caught in cliquer's spkg-install so the 
> compilation continues from there. The binary then doesn't work, of course.
>
>
> On Tuesday, January 26, 2016 at 1:36:45 PM UTC-5, Nathann Cohen wrote:
>>
>> > Nathann: 
>>
>> William, 
>>
>> I'm sorry to say that the situation is not as simple as "You suggest, 
>> and you are happy to see people doing it for you". 
>>
>> Sometimes, people do stuff because nobody would do it otherwise. They 
>> feel responsible as members of the community, and so give it a try. I 
>> swear: trust me. And by merely "suggesting stuff and waiting for 
>> others to (happily) do it" the truth is that you sometimes *use* those 
>> people. 
>>
>> Once, on a trac ticket, I saw something like that: "Of course this 
>> implementation is unnecessarily slow, but someday somebody will see it 
>> and improve it". For somebody like me, it comes very close to forcing 
>> me to improve it: because I do not accept to see a very obviously slow 
>> algorithm in Sage when I see a clear way to improve it: we deserve 
>> better (*). 
>>
>> I can only pray that not too many people will grow this "much bigger 
>> picture longterm strategic view of things" that you mentionned. 
>> Because each time it happens (you cite Nicolas Thierry as an example) 
>> we lose a developer and those they take with them. 
>>
>> And there is work to be done. Work which will only be done by those 
>> who remain. Some key people who, like you, are hardly repleacable: how 
>> many persons do you think have what it takes to change Sage's build 
>> system? 
>>
>> I'd say three: Volker, Jeroen and you. Perhaps there are others: I 
>> don't even know enough to give the full list. 
>>
>> But you cannot expect this to be done by one person, it takes a *lot* 
>> of time and skill, and we are not enough. 
>>
>> So please, now that you have seen the "much bigger picture longterm 
>> strategic view of things", come down here and get your hands dirty. We 
>> can't do the job if those who know how to do it think that they are 
>> above it. 
>>
>> Nathann 
>>
>> (*) On this ticket, they *knew* what was wrong. They just did not care 
>> enough to spend the time. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Volker Braun]

For the record, the OSX binaries are broken because cliquer fails to 
install; the log contains:

error: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool:
 
changing install names or rpaths can't be redone for: 
/Users/vbraun/Code/binary-pkg/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidmas391yaj24ng0bmdu/local/lib/libcliquer.dylib
 
(for architecture x86_64) because larger updated load commands do not fit 
(the program must be relinked, and you may need to use -headerpad or 
-headerpad_max_install_names)

Of course errors are not caught in cliquer's spkg-install so the 
compilation continues from there. The binary then doesn't work, of course.


On Tuesday, January 26, 2016 at 1:36:45 PM UTC-5, Nathann Cohen wrote:
>
> > Nathann: 
>
> William, 
>
> I'm sorry to say that the situation is not as simple as "You suggest, 
> and you are happy to see people doing it for you". 
>
> Sometimes, people do stuff because nobody would do it otherwise. They 
> feel responsible as members of the community, and so give it a try. I 
> swear: trust me. And by merely "suggesting stuff and waiting for 
> others to (happily) do it" the truth is that you sometimes *use* those 
> people. 
>
> Once, on a trac ticket, I saw something like that: "Of course this 
> implementation is unnecessarily slow, but someday somebody will see it 
> and improve it". For somebody like me, it comes very close to forcing 
> me to improve it: because I do not accept to see a very obviously slow 
> algorithm in Sage when I see a clear way to improve it: we deserve 
> better (*). 
>
> I can only pray that not too many people will grow this "much bigger 
> picture longterm strategic view of things" that you mentionned. 
> Because each time it happens (you cite Nicolas Thierry as an example) 
> we lose a developer and those they take with them. 
>
> And there is work to be done. Work which will only be done by those 
> who remain. Some key people who, like you, are hardly repleacable: how 
> many persons do you think have what it takes to change Sage's build 
> system? 
>
> I'd say three: Volker, Jeroen and you. Perhaps there are others: I 
> don't even know enough to give the full list. 
>
> But you cannot expect this to be done by one person, it takes a *lot* 
> of time and skill, and we are not enough. 
>
> So please, now that you have seen the "much bigger picture longterm 
> strategic view of things", come down here and get your hands dirty. We 
> can't do the job if those who know how to do it think that they are 
> above it. 
>
> Nathann 
>
> (*) On this ticket, they *knew* what was wrong. They just did not care 
> enough to spend the time. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] console prompt color

[Volker Braun]

On Tuesday, January 26, 2016 at 12:16:01 PM UTC-5, Michael Orlitzky wrote:
>
> The default should be NoColor, since whatever color scheme we choose is 
> going to be awful for a large number of users.


I disagree, the default should be good on white background. Every 
reasonable terminal uses that by default as UX research time again proved 
that this is the most readable color scheme. 

People are of course free to customize their terminal but then they can 
also customize their applications.


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: sage development (was Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes))

[William Stein]

On Tue, Jan 26, 2016 at 10:36 AM, Nathann Cohen  wrote:
>> Nathann:
>
> William,
>
> I'm sorry to say that the situation  [...]

I have over the years seen dozens of incredible Sage developers who
could do what we are talking about, but have to instead work fulltime
industry jobs now since open source math software development is so
horribly underfunded (and the love programming more than teaching).
For me it makes way more sense to do what it takes to try to get
better funding for open source math software now.  I'm good at
programming, but nowhere near as good as the dozens of people who I
could hire if I had any resources with which to hire them.

William

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Nathann Cohen]

> Nathann:

William,

I'm sorry to say that the situation is not as simple as "You suggest,
and you are happy to see people doing it for you".

Sometimes, people do stuff because nobody would do it otherwise. They
feel responsible as members of the community, and so give it a try. I
swear: trust me. And by merely "suggesting stuff and waiting for
others to (happily) do it" the truth is that you sometimes *use* those
people.

Once, on a trac ticket, I saw something like that: "Of course this
implementation is unnecessarily slow, but someday somebody will see it
and improve it". For somebody like me, it comes very close to forcing
me to improve it: because I do not accept to see a very obviously slow
algorithm in Sage when I see a clear way to improve it: we deserve
better (*).

I can only pray that not too many people will grow this "much bigger
picture longterm strategic view of things" that you mentionned.
Because each time it happens (you cite Nicolas Thierry as an example)
we lose a developer and those they take with them.

And there is work to be done. Work which will only be done by those
who remain. Some key people who, like you, are hardly repleacable: how
many persons do you think have what it takes to change Sage's build
system?

I'd say three: Volker, Jeroen and you. Perhaps there are others: I
don't even know enough to give the full list.

But you cannot expect this to be done by one person, it takes a *lot*
of time and skill, and we are not enough.

So please, now that you have seen the "much bigger picture longterm
strategic view of things", come down here and get your hands dirty. We
can't do the job if those who know how to do it think that they are
above it.

Nathann

(*) On this ticket, they *knew* what was wrong. They just did not care
enough to spend the time.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[William Stein]

Nathann:

> I can't help but notice that you say "we" when you say what should be
done, and you say "you" when there is actual work ahead.Will you
help? Or will you wait for Sage developers to do it?

It occurred to me that another reason I've been doing this is because
it gives me a sense for what I *have* to do versus what other people
will do.   There's no point in me doing something if I suggest it,and
other people are more than competent and willing to do it.As an
example, I've suggested numerous times that we should massively
refactor the sage library to be a bunch of smaller Python libraries,
develop them say on github (?), use Pypi and pip. If people would
realize how important it is that we revamp how Sage development is
done in a much less monolithic way, and better using existing tools,
then I would be happy and enjoy watching as people do the revamp
(e.g., like happened with switching from Mercurial to Git, which I
didn't do much on, but definitely supported).  As it is, I sadly see
that nobody seems to "get it" regarding how broken our development
process is right now.  So, I figure I'll have to do something.
Unfortunately, I can't do anything now, due to lack of time.   I hope
that either I'm totally wrong, or that I do have time before Sage gets
into deeper trouble.

William


On Tue, Jan 26, 2016 at 10:05 AM, Henri Girard  wrote:
> Wouldn't be possible to make a cliquer package ?

Cliquer has already been a standard Sage package since at least 2009.



>
>
>
> Le 26/01/2016 18:20, William Stein a écrit :
>>
>> On Tue, Jan 26, 2016 at 9:02 AM, Nathann Cohen 
>> wrote:

 contributions.  E.g., they won't even consider a new component be
 added to Python unless somebody clearly commits to supporting the
 contribution for "five years".  And of course the people making that
 commitment have to be reputable.We should do the same for Sage --
>>>
>>>
>>> 
>>> Don't you think we should start by doing the same for Sage's own source
>>> code? Anybody who proposes a patch should agree to do the
>>> debugging/maintenance of what (s)he added for the next 5 years? Looks
>>> weird
>>> to only have this high level of expectation for third-party code only,
>>> and
>>> not for our own.
>>> 
>>
>> Hey I was just reporting on a conversation with Guido about what they
>> *already* do with Python.
>>
>>> In Sage, we are at a level where some files don't have a clear "regular
>>> maintainer". We would need to be 10x more developpers to enforce such
>>> rules.
>>>
>> Indeed -- Python probably has 10x more developers...  maybe someday we
>> will have way more developer time too.  We don't now, as we are
>> massively under-resourced.
>>
>>> For 'cliquer' in particular, maybe we could propose upstream a
>>> autotoolized
>>> build system, and see how it goes? We did it for 'planarity' not so long
>>> ago
>>> (and perhaps with others?). Our spkg-install file indeed contains several
>>> platform-specific instructions.
>>
>> Huge +1.  I'm all for Sage devs contributing upstream :-)
>>
>>> Nathann
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to sage-support+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-support@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-support.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> 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-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Nathann Cohen]

> Wouldn't be possible to make a cliquer package ?

There is one already, installed in Sage by default.

This package is a copy of the cliquer tarball that you can download
from its official website. It contains a 'minimal' build system, which
does not work on all platforms that Sage supports. For this reason,
Sage adds a few instructions in order to make it work, but that's not
the 'clean way of doing things' for us.

The "clean way of doing things" would be for the original tarball to
compile properly on all platforms, without a need for additional
instructions.

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Henri Girard]

Wouldn't be possible to make a cliquer package ?


Le 26/01/2016 18:20, William Stein a écrit :

On Tue, Jan 26, 2016 at 9:02 AM, Nathann Cohen  wrote:

contributions.  E.g., they won't even consider a new component be
added to Python unless somebody clearly commits to supporting the
contribution for "five years".  And of course the people making that
commitment have to be reputable.We should do the same for Sage --



Don't you think we should start by doing the same for Sage's own source
code? Anybody who proposes a patch should agree to do the
debugging/maintenance of what (s)he added for the next 5 years? Looks weird
to only have this high level of expectation for third-party code only, and
not for our own.


Hey I was just reporting on a conversation with Guido about what they
*already* do with Python.


In Sage, we are at a level where some files don't have a clear "regular
maintainer". We would need to be 10x more developpers to enforce such rules.


Indeed -- Python probably has 10x more developers...  maybe someday we
will have way more developer time too.  We don't now, as we are
massively under-resourced.


For 'cliquer' in particular, maybe we could propose upstream a autotoolized
build system, and see how it goes? We did it for 'planarity' not so long ago
(and perhaps with others?). Our spkg-install file indeed contains several
platform-specific instructions.

Huge +1.  I'm all for Sage devs contributing upstream :-)


Nathann

--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.





--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[William Stein]

On Tue, Jan 26, 2016 at 9:42 AM, Nathann Cohen  wrote:
>>> Are you one of them?
>>
>> Rolls eyes...
>
> I can't help but notice that you say "we" when you say what should be
> done, and you say "you" when there is actual work ahead.

I am too busy to work on core Sage development right now.   If what
I'm doing right now pays off, there will be far more resources for
Sage development in the long run than anything I could ever personally
do.  I have also already done a lot -- according to this, I've done
some work on Sage:

   https://github.com/sagemath/sage/graphs/contributors

> You reported this problem concerning cliquer, and you are "all for
> Sage developpers contributing upstream". Will you help?

Nope, not on that. My time is better spent elsewhere.

> Or will you wait for Sage developpers to do it?

For now, yes.

I don't know how to say this, but I'm older than you have and have a
much bigger picture longterm strategic view of things.   There is much
more to helping the Sage project than diving into the trenches and
writing code (though that is very valuable too). For example, Nicholas
Thierry's work on getting the DREAMKIT funding and managing that is an
extremely valuable contribution.

That said, it's not like I don't write code -- I've evidently made
over 3000 commits to open source code in the last year:

   https://github.com/williamstein

I think I've done more programing in the last two years than at any
point in my life before.  And it has been at times much more difficult
than any work I did on Sage.

I'm sorry if you feel like I'm "flame baiting" you with the above
off-topic message.

Back to work.

William

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

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: problem with nfs or... what ? (7.0)

[Thierry Dumont]

Le 25/01/2016 15:37, Volker Braun a écrit :

The directory path has to match, if its different on server and client
then you have to compile it on the client (or mount on the server in the
same path first).



Ok it's working. But is it something new ?

For binary distributions, we can install it at any place we want, no?
What is the difference?

Yours (thanks).
t.


On Monday, January 25, 2016 at 9:20:17 AM UTC-5, tdumont wrote:

Hello,

I have tried to switch from 6.10 to 7.0, but... I have some problems.

1) Let me fist explain the architecture of our client/server
installation:

-We have a nfs server (Debian + Zfs) which export a directory
(/srv/local64) to a large number of clients (all Ubuntu 14.O4-LTS) but
with different generations of Intel CPUs.

So, on the server I compiled sage from the 7.0 source with
export SAGE_FAT_BINARY="yes"
make distclean
make

On the server, I can launch this compiled sage 7.0 without any
problem..

2) On the clients, I have a problem:
./sage

   File

"/usr/local/sage/local/lib/python2.7/site-packages/sage/misc/temporary_file.py",

line 51, in delete_tmpfiles
  from sage.misc.misc import SAGE_TMP
File
"/usr/local/sage/local/lib/python2.7/site-packages/sage/misc/misc.py",
line 57, in 
  import sage.misc.prandom as random
File
"/usr/local/sage/local/lib/python2.7/site-packages/sage/misc/prandom.py",
line
58, in 
  from sage.misc.randstate import current_randstate
ImportError: libgmp.so.16: cannot open shared object file: No such file
or directory

Permissions seems ok... So, no idea for me.


This is new: I have kept a tree with a 6.10 version and everything
is ok.

???
Yours

t.d.

--
You received this message because you are subscribed to the Google
Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage-support+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-support@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
<>

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Nathann Cohen]

>> Are you one of them?
>
> Rolls eyes...

I can't help but notice that you say "we" when you say what should be
done, and you say "you" when there is actual work ahead.

You reported this problem concerning cliquer, and you are "all for
Sage developpers contributing upstream". Will you help?

Or will you wait for Sage developpers to do it?

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[William Stein]

On Tue, Jan 26, 2016 at 9:35 AM, Nathann Cohen  wrote:
>> Hey I was just reporting on a conversation with Guido about what they
>> *already* do with Python.
>
> It ended with "we should do the same in Sage"

I was talking about packages not code.

>> Huge +1.  I'm all for Sage devs contributing upstream :-)
>
> Are you one of them?

Rolls eyes...

>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> 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-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Nathann Cohen]

> Hey I was just reporting on a conversation with Guido about what they
> *already* do with Python.

It ended with "we should do the same in Sage"

> Huge +1.  I'm all for Sage devs contributing upstream :-)

Are you one of them?

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: [sage-edu] Writing 'n' variables in Sagemath linux ubuntu

[Michael Orlitzky]

> On Tue, Jan 26, 2016 at 3:01 AM, Usman Afzal  wrote:
>> If I want to write one variable, the command is
>> x=var('x')
>>
>> But I want to write "n" variables namely x1, x2, . . . , x(n). How can I
>> write this?

This is http://trac.sagemath.org/ticket/11576, but it's dead in the
water. I still maintain and use my SymbolSequence implementation. I'm
attaching symbol_sequence.py; to use it, load it in your sage session:

  sage: load('symbol_sequence.py')

Then to declare a list of variables "x1", "x2", and so on, write,

  sage: x = SymbolSequence('x')

Now you can use array indexes to get as many variables as you need:

  sage: x[0]
  x_0
  sage: x[1]
  x_1
  sage: x[10]
  x_10

Multiple subscripts and slices work the way you'd want them to:

  sage: [ a[i,j] for i in range(0,2) for j in range(0,2) ]
  [a_0_0, a_0_1, a_1_0, a_1_1]

And you can use that (for example) to construct matrices:

  sage: d = 5
  sage: X = matrix(SR, d, d, x[0:d,0:d])
  sage: X
  [x_0_0 x_0_1 x_0_2 x_0_3 x_0_4]
  [x_1_0 x_1_1 x_1_2 x_1_3 x_1_4]
  [x_2_0 x_2_1 x_2_2 x_2_3 x_2_4]
  [x_3_0 x_3_1 x_3_2 x_3_3 x_3_4]
  [x_4_0 x_4_1 x_4_2 x_4_3 x_4_4]


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
from sage.all import *

class SymbolSequence:
"""
An iterable object which acts like a sequence of symbolic
expressions (variables).

INPUT:

  - ``name`` -- The sequence name. For example, if you name the
sequence `x`, the variables will be called `x_0`, `x_1`,...

  - ``latex_name`` -- An optional latex expression (string) to
use instead of `name` when converting the symbols to latex.

  - ``domain`` -- A string representing the domain of the symbol,
either 'real', 'complex', or 'positive'.

OUTPUT:

An iterable object containing symbolic expressions.

EXAMPLES:

The simplest use case::

sage: a = SymbolSequence('a')
sage: a[0]
a_0
sage: a[1]
a_1

Create polynomials with symbolic coefficients of arbitrary
degree::

sage: a = SymbolSequence('a')
sage: p = sum([ a[i]*x^i for i in range(0,5)])
sage: p
a_4*x^4 + a_3*x^3 + a_2*x^2 + a_1*x + a_0

Using a different latex name since 'lambda' is reserved::

sage: l = SymbolSequence('l', '\lambda')
sage: l[0]
l_0
sage: latex(l[0])
\lambda_{0}

Using multiple indices::

sage: a = SymbolSequence('a')
sage: a[0,1,2]
a_0_1_2
sage: latex(a[0,1,2])
a_{0}_{1}_{2}
sage: [ a[i,j] for i in range(0,2) for j in range(0,2) ]
[a_0_0, a_0_1, a_1_0, a_1_1]

You can pass slices instead of integers to obtain a list of
symbols::

sage: a = SymbolSequence('a')
sage: a[5:7]
[a_5, a_6]

This even works for the second, third, etc. indices::

sage: a = SymbolSequence('a')
sage: a[0:2, 0:2]
[a_0_0, a_0_1, a_1_0, a_1_1]

TESTS:

We shouldn't overwrite variables in the global namespace::

sage: a = SymbolSequence('a')
sage: a_0 = 4
sage: a[0]
a_0
sage: a_0
4

The symbol at a given index should always be the same, even when
the symbols themselves are unnamed. We store the string
representation and compare because the output is unpredictable::

sage: a = SymbolSequence()
sage: a0str = str(a[0])
sage: str(a[0]) == a0str
True

Slices and single indices work when combined::

sage: a = SymbolSequence('a')
sage: a[3, 0:2]
[a_3_0, a_3_1]
sage: a[0:2, 3]
[a_0_3, a_1_3]

"""

def __init__(self, name=None, latex_name=None, domain=None):
# We store a dict of already-created symbols so that we don't
# recreate a symbol which already exists. This is especially
# helpful when using unnamed variables, if you want e.g. a[0]
# to return the same variable each time.
self._symbols = {}

self._name = name
self._latex_name = latex_name
self._domain = domain


def _create_symbol_(self, subscript):
"""
Return a symbol with the given subscript. Creates the
appropriate name and latex_name before delegating to
SR.symbol().

EXAMPLES::

sage: a = SymbolSequence('a', 'alpha', 'real')
sage: a_1 = a._create_symbol_(1)
sage: a_1
a_1
sage: latex(a_1)
alpha_{1}

"""
# Allow creating unnamed symbols, for consistency with
# SR.symbol().

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[William Stein]

On Tue, Jan 26, 2016 at 9:02 AM, Nathann Cohen  wrote:
>> contributions.  E.g., they won't even consider a new component be
>> added to Python unless somebody clearly commits to supporting the
>> contribution for "five years".  And of course the people making that
>> commitment have to be reputable.We should do the same for Sage --
>
>
> 
> Don't you think we should start by doing the same for Sage's own source
> code? Anybody who proposes a patch should agree to do the
> debugging/maintenance of what (s)he added for the next 5 years? Looks weird
> to only have this high level of expectation for third-party code only, and
> not for our own.
> 

Hey I was just reporting on a conversation with Guido about what they
*already* do with Python.

> In Sage, we are at a level where some files don't have a clear "regular
> maintainer". We would need to be 10x more developpers to enforce such rules.
>

Indeed -- Python probably has 10x more developers...  maybe someday we
will have way more developer time too.  We don't now, as we are
massively under-resourced.

> For 'cliquer' in particular, maybe we could propose upstream a autotoolized
> build system, and see how it goes? We did it for 'planarity' not so long ago
> (and perhaps with others?). Our spkg-install file indeed contains several
> platform-specific instructions.

Huge +1.  I'm all for Sage devs contributing upstream :-)

>
> Nathann
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> 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-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] console prompt color

[Michael Orlitzky]

On 01/24/2016 03:03 PM, Jagdpanther wrote:
> I just compiled  SageMath 7.0.  Both the console and notebook interface
> seem to work well.  I use a dark gray background in my xterm (uxterm)
> window where I run sage (console)  and the dark blue "sage:" prompt is
> hard to see.  How do I change the color of the console "sage:" prompt?

Rather annoying isn't it =)

The default should be NoColor, since whatever color scheme we choose is
going to be awful for a large number of users. To change it once, run

  sage: %colors NoColor

To change it permanently, add that command to your init.sage file:

  $ echo '%colors NoColor' >> ~/.sage/init.sage

If it works for you, you may prefer the color scheme designed for
light-on-dark terminals, obtained with "%colors Linux".

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] compile sage from source to link to existing applications

[Michael Orlitzky]

On 01/26/2016 01:13 AM, bernard ck Wong wrote:
> Hi, I am wondering if it is possible to compile Sage from source and
> configure it in such a way that it will use software that is already
> installed in my system instead of building the bundled ones? For
> example, I have R, Singular and Maxima already installed in their latest
> versions and I have already built atlas optimised to my machine. It
> seems that there is no point for sage to create duplicates which are
> either older or not as well tuned to my setup.

The only way to do this right now is with sage-on-gentoo [0], which
works easily only if you happen to use Gentoo Linux. Otherwise you would
have to get a Gentoo Prefix [1] up and running, and then add
sage-on-gentoo to that.

Installing Prefix can be pretty hairy -- most Prefix users switch to
Gentoo eventually so demand is always low. But still, it's faster to
build an entire prefix system from scratch and then build sage-on-gentoo
twice than it is to build sage twice using the official process.

[0] https://github.com/cschwan/sage-on-gentoo
[1] https://wiki.gentoo.org/wiki/Project:Prefix

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[Nathann Cohen]

>
> contributions.  E.g., they won't even consider a new component be 
> added to Python unless somebody clearly commits to supporting the 
> contribution for "five years".  And of course the people making that 
> commitment have to be reputable.We should do the same for Sage -- 
>


Don't you think we should start by doing the same for Sage's own source 
code? Anybody who proposes a patch should agree to do the 
debugging/maintenance of what (s)he added for the next 5 years? Looks weird 
to only have this high level of expectation for third-party code only, and 
not for our own.


In Sage, we are at a level where some files don't have a clear "regular 
maintainer". We would need to be 10x more developpers to enforce such rules.

For 'cliquer' in particular, maybe we could propose upstream a autotoolized 
build system, and see how it goes? We did it for 'planarity' not so long 
ago (and perhaps with others?). Our spkg-install file indeed contains 
several platform-specific instructions.

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: sage console prompt color

[slelievre]

Le mardi 26 janvier 2016 16:17:41 UTC, Jagdpanther a écrit :
>
>
>
> I just compiled and tested sage 7.0. Everything (both console and 
> notebook) seems to work.  I use a dark grey xterm (uxterm) console and the 
> dark blue "sage:" prompt is hard to see.  I do I change the color of the 
> console "sage:" prompt?
>
> Thanks.
>

This may help:
http://linuxwisdom.blogspot.co.uk/2009/05/sage-prompt-in-color.html 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] compile sage from source to link to existing applications

[William Stein]

On Mon, Jan 25, 2016 at 10:13 PM, bernard ck Wong
 wrote:
> Hi, I am wondering if it is possible to compile Sage from source and
> configure it in such a way that it will use software that is already
> installed in my system instead of building the bundled ones? For example, I
> have R, Singular and Maxima already installed in their latest versions and I
> have already built atlas optimised to my machine. It seems that there is no
> point for sage to create duplicates which are either older or not as well
> tuned to my setup.
>

No, it's not possible.

William

> Thanks/
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> 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-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage 7.0 crashes

[Volker Braun]

That doesn't work on linux so it'll only make it more difficult by 
introducing yet another special snowflake... 

Really I'm surprised that cliquer ever worked on OSX.




On Tuesday, January 26, 2016 at 11:06:45 AM UTC-5, Dima Pasechnik wrote:
>
> How about we create an OSX installer that does not rewrite anything at 
> all, but must be installed in
> /Applications/SageMath/
> quicker and less error-prone...
>
>
> On Tuesday, 26 January 2016 15:59:15 UTC, Volker Braun wrote:
>>
>> The cliquer "buildsystem" is a steaming pile of s**t, it clearly should 
>> not be a standard package. For starters, it shouldn't install a .so on 
>> darwin...
>>
>>
>>
>>
>>
>>
>> On Tuesday, January 26, 2016 at 10:53:27 AM UTC-5, Dima Pasechnik wrote:
>>>
>>> however, notice no path in front of 
>>>
>>> libcliquer.dylib (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> in these outputs.
>>> On a working copy of Sage I have
>>>
>>>
>>> /Applications/SageMath/local/lib/libcliquer.dylib (compatibility version 
>>> 0.0.0, current version 0.0.0)
>>>
>>>
>>> On Tuesday, 26 January 2016 15:46:17 UTC, Dima Pasechnik wrote:

 that is before the 1st Sage start attempt; and after it crashed, I get 
 seemingly normal looking


 $ otool -L 
 /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so


 /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:

 libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1226.10.1)

 /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility 
 version 1.0.0, current version 1.0.0)


 $ otool -L /Applications/SageMath/local/lib/libcliquer.so

 /Applications/SageMath/local/lib/libcliquer.so:

 libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1226.10.1)

 /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility 
 version 1.0.0, current version 1.0.0)


 $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib 

 /Applications/SageMath/local/lib/libcliquer.dylib:

 libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1226.10.1)

 /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility 
 version 1.0.0, current version 1.0.0)


 thus, my guess about the wrong arch seems to be right.

 On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote:
>
>
>
> On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:
>>
>> Output of "otool -L" for cliquer.so and libcliquer.so?
>>
>
> here you are, there is some buildslave crap (how can it work on ANY 
> system?)
>
> $ otool -L 
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>
>
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 1226.10.1)
>
> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>  
> (compatibility version 1.0.0, current version 1.0.0)
>
>
> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib
>
> /Applications/SageMath/local/lib/libcliquer.dylib:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 1226.10.1)
> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>  
> (compatibility version 1.0.0, current version 1.0.0)
>
> $ otool -L /Applications/SageMath/local/lib/libcliquer.so   
>
> /Applications/SageMath/local/lib/libcliquer.so:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 1226.10.1)
> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>  
> (compatibility version 1.0.0, current version 1.0.0) 
>
> --
> and libgcc_s.1.dylib should be
>
>
> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility 
> version 1.0.0, current version 1.0.0)
>
>
>
>>
>>
>> On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik 
>> wrote:
>>>
>>> I can reproduce this. I downloaded t

[sage-support] console prompt color

[Jagdpanther]

I just compiled  SageMath 7.0.  Both the console and notebook interface 
seem to work well.  I use a dark gray background in my xterm (uxterm) 
window where I run sage (console)  and the dark blue "sage:" prompt is hard 
to see.  How do I change the color of the console "sage:" prompt?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] compile sage from source to link to existing applications

[bernard ck Wong]

Hi, I am wondering if it is possible to compile Sage from source and 
configure it in such a way that it will use software that is already 
installed in my system instead of building the bundled ones? For example, I 
have R, Singular and Maxima already installed in their latest versions and 
I have already built atlas optimised to my machine. It seems that there is 
no point for sage to create duplicates which are either older or not as 
well tuned to my setup.

Thanks/

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] sage console prompt color

[Jagdpanther]

I just compiled and tested sage 7.0. Everything (both console and notebook) 
seems to work.  I use a dark grey xterm (uxterm) console and the dark blue 
"sage:" prompt is hard to see.  I do I change the color of the console 
"sage:" prompt?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Cliquer (was Re: [sage-support] Re: Sage 7.0 crashes)

[William Stein]

On Tue, Jan 26, 2016 at 7:59 AM, Volker Braun  wrote:
> The cliquer "buildsystem" is a steaming pile of s**t, it clearly should not
> be a standard package. For starters, it shouldn't install a .so on darwin...

Agreed. In fact, here's a (was private) email I wrote in 2009 after
having lunch with Guido van Rossum; it's about Cython, Sage packaging
and how cliquer is a prime example of something that shouldn't be in
Sage: "I asked Guido about Cython going into core Python and he gave
me a general speech discouraging me from getting *anything* into core
Python.  (I might use some of it when people try to propose packages
for Sage.)   He said that only dead code in maintenance only mode
should be added, etc., etc.  He didn't really answer specifically
about Cython though, except to say that modern software distribution
tools are getting so good (alluding to Distribute?) that being in the
core of Python isn't such a big deal anymore.

He also mentioned they have an official PEP or something for all new
contributions.  E.g., they won't even consider a new component be
added to Python unless somebody clearly commits to supporting the
contribution for "five years".  And of course the people making that
commitment have to be reputable.We should do the same for Sage --
e.g., when PIL got considered, we should have made sure somebody
*volunteers* to maintain it for some amount of time, before even
considering it.  Same for cliquer, which got voted in, then sucked in
a million ways, and almost feels disowned already.I will bring
this up next time a package is considered for inclusion in Sage.   I'm
actually really shocked that in all the discussion about getting
packages into Sage, we fixed on voting procedures and other stuff, but
totally missed by far the most important point -- getting somebody to
solidly commit to maintaining the package on all platforms for a given
amount of time.   We missed the most important thing and instead got
caught up in stupid bureaucracy that doesn't solve anything."

William

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage 7.0 crashes

[Dima Pasechnik]

How about we create an OSX installer that does not rewrite anything at all, 
but must be installed in
/Applications/SageMath/
quicker and less error-prone...


On Tuesday, 26 January 2016 15:59:15 UTC, Volker Braun wrote:
>
> The cliquer "buildsystem" is a steaming pile of s**t, it clearly should 
> not be a standard package. For starters, it shouldn't install a .so on 
> darwin...
>
>
>
>
>
>
> On Tuesday, January 26, 2016 at 10:53:27 AM UTC-5, Dima Pasechnik wrote:
>>
>> however, notice no path in front of 
>>
>> libcliquer.dylib (compatibility version 0.0.0, current version 0.0.0)
>>
>> in these outputs.
>> On a working copy of Sage I have
>>
>>
>> /Applications/SageMath/local/lib/libcliquer.dylib (compatibility version 
>> 0.0.0, current version 0.0.0)
>>
>>
>> On Tuesday, 26 January 2016 15:46:17 UTC, Dima Pasechnik wrote:
>>>
>>> that is before the 1st Sage start attempt; and after it crashed, I get 
>>> seemingly normal looking
>>>
>>>
>>> $ otool -L 
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>>
>>>
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>>
>>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>>> 1.0.0, current version 1.0.0)
>>>
>>>
>>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so
>>>
>>> /Applications/SageMath/local/lib/libcliquer.so:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>>
>>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>>> 1.0.0, current version 1.0.0)
>>>
>>>
>>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib 
>>>
>>> /Applications/SageMath/local/lib/libcliquer.dylib:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>>
>>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>>> 1.0.0, current version 1.0.0)
>>>
>>>
>>> thus, my guess about the wrong arch seems to be right.
>>>
>>> On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote:



 On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:
>
> Output of "otool -L" for cliquer.so and libcliquer.so?
>

 here you are, there is some buildslave crap (how can it work on ANY 
 system?)

 $ otool -L 
 /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so


 /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:

 libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1226.10.1)

 /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
  
 (compatibility version 1.0.0, current version 1.0.0)


 $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib

 /Applications/SageMath/local/lib/libcliquer.dylib:

 libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1226.10.1)
 /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
  
 (compatibility version 1.0.0, current version 1.0.0)

 $ otool -L /Applications/SageMath/local/lib/libcliquer.so   

 /Applications/SageMath/local/lib/libcliquer.so:

 libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
 version 1226.10.1)
 /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
  
 (compatibility version 1.0.0, current version 1.0.0) 

 --
 and libgcc_s.1.dylib should be


 /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility 
 version 1.0.0, current version 1.0.0)



>
>
> On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:
>>
>> I can reproduce this. I downloaded the 
>> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
>> unpacked and copied in /Applications/
>> and started /Applications/Sage/sage in the terminal. And ended up 
>> with the same crash on clique.so load.
>>
>> It could be due to old hardware:
>>
>> MacBook Air (13-inch, Late 2010)
>>
>>   Model Name: MacBook Air
>>
>>   M

[sage-support] Re: Sage 7.0 crashes

[Volker Braun]

The cliquer "buildsystem" is a steaming pile of s**t, it clearly should not 
be a standard package. For starters, it shouldn't install a .so on darwin...






On Tuesday, January 26, 2016 at 10:53:27 AM UTC-5, Dima Pasechnik wrote:
>
> however, notice no path in front of 
>
> libcliquer.dylib (compatibility version 0.0.0, current version 0.0.0)
>
> in these outputs.
> On a working copy of Sage I have
>
>
> /Applications/SageMath/local/lib/libcliquer.dylib (compatibility version 
> 0.0.0, current version 0.0.0)
>
>
> On Tuesday, 26 January 2016 15:46:17 UTC, Dima Pasechnik wrote:
>>
>> that is before the 1st Sage start attempt; and after it crashed, I get 
>> seemingly normal looking
>>
>>
>> $ otool -L 
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>
>>
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so
>>
>> /Applications/SageMath/local/lib/libcliquer.so:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib 
>>
>> /Applications/SageMath/local/lib/libcliquer.dylib:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>> thus, my guess about the wrong arch seems to be right.
>>
>> On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote:
>>>
>>>
>>>
>>> On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:

 Output of "otool -L" for cliquer.so and libcliquer.so?

>>>
>>> here you are, there is some buildslave crap (how can it work on ANY 
>>> system?)
>>>
>>> $ otool -L 
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>>
>>>
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>>
>>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>>  
>>> (compatibility version 1.0.0, current version 1.0.0)
>>>
>>>
>>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib
>>>
>>> /Applications/SageMath/local/lib/libcliquer.dylib:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>>  
>>> (compatibility version 1.0.0, current version 1.0.0)
>>>
>>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so   
>>>
>>> /Applications/SageMath/local/lib/libcliquer.so:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>>  
>>> (compatibility version 1.0.0, current version 1.0.0) 
>>>
>>> --
>>> and libgcc_s.1.dylib should be
>>>
>>>
>>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>>> 1.0.0, current version 1.0.0)
>>>
>>>
>>>


 On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:
>
> I can reproduce this. I downloaded the 
> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
> unpacked and copied in /Applications/
> and started /Applications/Sage/sage in the terminal. And ended up with 
> the same crash on clique.so load.
>
> It could be due to old hardware:
>
> MacBook Air (13-inch, Late 2010)
>
>   Model Name: MacBook Air
>
>   Model Identifier: MacBookAir3,2
>
>   Processor Name: Intel Core 2 Duo
>
>   Processor Speed: 1.86 GHz
>
>   Number of Processors: 1
>
>   Total Number of Cores: 2
>
>   L2 Cache: 6 MB
>
>   Memory: 4 GB
>
>   Bus Speed: 1.07 GHz
>
>   Boot ROM Version: MBA31.0061.B01
>
>   SMC Version (system): 1.66f61
>>>

[sage-support] Re: Sage 7.0 crashes

[Dima Pasechnik]

 Tuesday, 26 January 2016 15:53:27 UTC, Dima Pasechnik wrote:
>
> however, notice no path in front of 
>
> libcliquer.dylib (compatibility version 0.0.0, current version 0.0.0)
>
argh, sorry, typo:

On a non-working copy I have 
 
libcliquer.so (compatibility version 0.0.0, current version 0.0.0)


> in these outputs.
> On a working copy of Sage I have
>
>
> /Applications/SageMath/local/lib/libcliquer.dylib (compatibility version 
> 0.0.0, current version 0.0.0)
>
>
> On Tuesday, 26 January 2016 15:46:17 UTC, Dima Pasechnik wrote:
>>
>> that is before the 1st Sage start attempt; and after it crashed, I get 
>> seemingly normal looking
>>
>>
>> $ otool -L 
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>
>>
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so
>>
>> /Applications/SageMath/local/lib/libcliquer.so:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib 
>>
>> /Applications/SageMath/local/lib/libcliquer.dylib:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>> thus, my guess about the wrong arch seems to be right.
>>
>> On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote:
>>>
>>>
>>>
>>> On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:

 Output of "otool -L" for cliquer.so and libcliquer.so?

>>>
>>> here you are, there is some buildslave crap (how can it work on ANY 
>>> system?)
>>>
>>> $ otool -L 
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>>
>>>
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>>
>>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>>  
>>> (compatibility version 1.0.0, current version 1.0.0)
>>>
>>>
>>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib
>>>
>>> /Applications/SageMath/local/lib/libcliquer.dylib:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>>  
>>> (compatibility version 1.0.0, current version 1.0.0)
>>>
>>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so   
>>>
>>> /Applications/SageMath/local/lib/libcliquer.so:
>>>
>>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>>
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>>> 1226.10.1)
>>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>>  
>>> (compatibility version 1.0.0, current version 1.0.0) 
>>>
>>> --
>>> and libgcc_s.1.dylib should be
>>>
>>>
>>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>>> 1.0.0, current version 1.0.0)
>>>
>>>
>>>


 On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:
>
> I can reproduce this. I downloaded the 
> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
> unpacked and copied in /Applications/
> and started /Applications/Sage/sage in the terminal. And ended up with 
> the same crash on clique.so load.
>
> It could be due to old hardware:
>
> MacBook Air (13-inch, Late 2010)
>
>   Model Name: MacBook Air
>
>   Model Identifier: MacBookAir3,2
>
>   Processor Name: Intel Core 2 Duo
>
>   Processor Speed: 1.86 GHz
>
>   Number of Processors: 1
>
>   Total Number of Cores: 2
>
>   L2 Cache: 6 MB
>
>   Memory: 4 GB
>
>   Bus Speed: 1.07 GHz
>
>   Boot ROM Version: MBA31.0061.B01
>
>   SMC Version (system): 1.66f61
>
> I don't know on which hardware the binar

[sage-support] Re: Sage 7.0 crashes

[Dima Pasechnik]

that is before the 1st Sage start attempt; and after it crashed, I get 
seemingly normal looking


$ otool -L 
/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so

/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:

libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)

/Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
1.0.0, current version 1.0.0)


$ otool -L /Applications/SageMath/local/lib/libcliquer.so

/Applications/SageMath/local/lib/libcliquer.so:

libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)

/Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
1.0.0, current version 1.0.0)


$ otool -L /Applications/SageMath/local/lib/libcliquer.dylib 

/Applications/SageMath/local/lib/libcliquer.dylib:

libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)

/Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
1.0.0, current version 1.0.0)


thus, my guess about the wrong arch seems to be right.

On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote:
>
>
>
> On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:
>>
>> Output of "otool -L" for cliquer.so and libcliquer.so?
>>
>
> here you are, there is some buildslave crap (how can it work on ANY 
> system?)
>
> $ otool -L 
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>
>
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1226.10.1)
>
> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>  
> (compatibility version 1.0.0, current version 1.0.0)
>
>
> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib
>
> /Applications/SageMath/local/lib/libcliquer.dylib:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1226.10.1)
> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>  
> (compatibility version 1.0.0, current version 1.0.0)
>
> $ otool -L /Applications/SageMath/local/lib/libcliquer.so   
>
> /Applications/SageMath/local/lib/libcliquer.so:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1226.10.1)
> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>  
> (compatibility version 1.0.0, current version 1.0.0) 
>
> --
> and libgcc_s.1.dylib should be
>
>
> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
> 1.0.0, current version 1.0.0)
>
>
>
>>
>>
>> On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:
>>>
>>> I can reproduce this. I downloaded the 
>>> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
>>> unpacked and copied in /Applications/
>>> and started /Applications/Sage/sage in the terminal. And ended up with 
>>> the same crash on clique.so load.
>>>
>>> It could be due to old hardware:
>>>
>>> MacBook Air (13-inch, Late 2010)
>>>
>>>   Model Name: MacBook Air
>>>
>>>   Model Identifier: MacBookAir3,2
>>>
>>>   Processor Name: Intel Core 2 Duo
>>>
>>>   Processor Speed: 1.86 GHz
>>>
>>>   Number of Processors: 1
>>>
>>>   Total Number of Cores: 2
>>>
>>>   L2 Cache: 6 MB
>>>
>>>   Memory: 4 GB
>>>
>>>   Bus Speed: 1.07 GHz
>>>
>>>   Boot ROM Version: MBA31.0061.B01
>>>
>>>   SMC Version (system): 1.66f61
>>>
>>> I don't know on which hardware the binary distro was built, I suspect on 
>>> something newer (Core2 Duo is really old and a bit weird).
>>> It might be missing some processor commands which are used in the 
>>> binary...
>>>
>>>
>>> Solution: rebuild Sage from source.
>>>
>>> Dima
>>>
>>>
>>> On Tuesday, 26 January 2016 02:15:38 UTC, Volker Braun wrote:

 Does the file exist? From the log:

 ImportError: 
 dlopen(/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so,
  
 2): Library not loaded: libcliquer.so
   Referenced from: 
 /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
   Reason: image not found




 On Monday, January 25, 2016 at 7:52:42 PM UTC-5, Juan Luis Varona wrote:
>
> I have tried to install sage 7.0 in a mac with osx-10-11-2 and it 
> crash

[sage-support] Re: Sage 7.0 crashes

[Dima Pasechnik]

however, notice no path in front of 

libcliquer.dylib (compatibility version 0.0.0, current version 0.0.0)

in these outputs.
On a working copy of Sage I have


/Applications/SageMath/local/lib/libcliquer.dylib (compatibility version 
0.0.0, current version 0.0.0)


On Tuesday, 26 January 2016 15:46:17 UTC, Dima Pasechnik wrote:
>
> that is before the 1st Sage start attempt; and after it crashed, I get 
> seemingly normal looking
>
>
> $ otool -L 
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>
>
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1226.10.1)
>
> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
> 1.0.0, current version 1.0.0)
>
>
> $ otool -L /Applications/SageMath/local/lib/libcliquer.so
>
> /Applications/SageMath/local/lib/libcliquer.so:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1226.10.1)
>
> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
> 1.0.0, current version 1.0.0)
>
>
> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib 
>
> /Applications/SageMath/local/lib/libcliquer.dylib:
>
> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 1226.10.1)
>
> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
> 1.0.0, current version 1.0.0)
>
>
> thus, my guess about the wrong arch seems to be right.
>
> On Tuesday, 26 January 2016 15:31:19 UTC, Dima Pasechnik wrote:
>>
>>
>>
>> On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:
>>>
>>> Output of "otool -L" for cliquer.so and libcliquer.so?
>>>
>>
>> here you are, there is some buildslave crap (how can it work on ANY 
>> system?)
>>
>> $ otool -L 
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>
>>
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>>
>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>  
>> (compatibility version 1.0.0, current version 1.0.0)
>>
>>
>> $ otool -L /Applications/SageMath/local/lib/libcliquer.dylib
>>
>> /Applications/SageMath/local/lib/libcliquer.dylib:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>  
>> (compatibility version 1.0.0, current version 1.0.0)
>>
>> $ otool -L /Applications/SageMath/local/lib/libcliquer.so   
>>
>> /Applications/SageMath/local/lib/libcliquer.so:
>>
>> libcliquer.so (compatibility version 0.0.0, current version 0.0.0)
>>
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
>> 1226.10.1)
>> /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
>>  
>> (compatibility version 1.0.0, current version 1.0.0) 
>>
>> --
>> and libgcc_s.1.dylib should be
>>
>>
>> /Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
>> 1.0.0, current version 1.0.0)
>>
>>
>>
>>>
>>>
>>> On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:

 I can reproduce this. I downloaded the 
 ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
 unpacked and copied in /Applications/
 and started /Applications/Sage/sage in the terminal. And ended up with 
 the same crash on clique.so load.

 It could be due to old hardware:

 MacBook Air (13-inch, Late 2010)

   Model Name: MacBook Air

   Model Identifier: MacBookAir3,2

   Processor Name: Intel Core 2 Duo

   Processor Speed: 1.86 GHz

   Number of Processors: 1

   Total Number of Cores: 2

   L2 Cache: 6 MB

   Memory: 4 GB

   Bus Speed: 1.07 GHz

   Boot ROM Version: MBA31.0061.B01

   SMC Version (system): 1.66f61

 I don't know on which hardware the binary distro was built, I suspect 
 on something newer (Core2 Duo is really old and a bit weird).
 It might be missing some processor commands which are used in the 
 binary...


 Solution: rebuild Sage from source.

 Dima


 On Tuesday, 26 January 2016 02:15:38 UTC, Volker Braun wrote:
>
> Does the fil

[sage-support] Re: Sage 7.0 crashes

[Volker Braun]

On Tuesday, January 26, 2016 at 10:31:19 AM UTC-5, Dima Pasechnik wrote:
>
> here you are, there is some buildslave crap (how can it work on ANY 
> system?)
>

The relocate-once.py script was not run for some reason...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage 7.0 crashes

[Dima Pasechnik]

On Tuesday, 26 January 2016 14:38:41 UTC, Volker Braun wrote:
>
> Output of "otool -L" for cliquer.so and libcliquer.so?
>

here you are, there is some buildslave crap (how can it work on ANY system?)

$ otool -L 
/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so

/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so:

libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)

/Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
 
(compatibility version 1.0.0, current version 1.0.0)


$ otool -L /Applications/SageMath/local/lib/libcliquer.dylib

/Applications/SageMath/local/lib/libcliquer.dylib:

libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)
/Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
 
(compatibility version 1.0.0, current version 1.0.0)

$ otool -L /Applications/SageMath/local/lib/libcliquer.so   

/Applications/SageMath/local/lib/libcliquer.so:

libcliquer.so (compatibility version 0.0.0, current version 0.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)
/Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libgcc_s.1.dylib
 
(compatibility version 1.0.0, current version 1.0.0) 

--
and libgcc_s.1.dylib should be


/Applications/SageMath/local/lib/libgcc_s.1.dylib (compatibility version 
1.0.0, current version 1.0.0)



>
>
> On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:
>>
>> I can reproduce this. I downloaded the 
>> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
>> unpacked and copied in /Applications/
>> and started /Applications/Sage/sage in the terminal. And ended up with 
>> the same crash on clique.so load.
>>
>> It could be due to old hardware:
>>
>> MacBook Air (13-inch, Late 2010)
>>
>>   Model Name: MacBook Air
>>
>>   Model Identifier: MacBookAir3,2
>>
>>   Processor Name: Intel Core 2 Duo
>>
>>   Processor Speed: 1.86 GHz
>>
>>   Number of Processors: 1
>>
>>   Total Number of Cores: 2
>>
>>   L2 Cache: 6 MB
>>
>>   Memory: 4 GB
>>
>>   Bus Speed: 1.07 GHz
>>
>>   Boot ROM Version: MBA31.0061.B01
>>
>>   SMC Version (system): 1.66f61
>>
>> I don't know on which hardware the binary distro was built, I suspect on 
>> something newer (Core2 Duo is really old and a bit weird).
>> It might be missing some processor commands which are used in the 
>> binary...
>>
>>
>> Solution: rebuild Sage from source.
>>
>> Dima
>>
>>
>> On Tuesday, 26 January 2016 02:15:38 UTC, Volker Braun wrote:
>>>
>>> Does the file exist? From the log:
>>>
>>> ImportError: 
>>> dlopen(/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so,
>>>  
>>> 2): Library not loaded: libcliquer.so
>>>   Referenced from: 
>>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>>   Reason: image not found
>>>
>>>
>>>
>>>
>>> On Monday, January 25, 2016 at 7:52:42 PM UTC-5, Juan Luis Varona wrote:

 I have tried to install sage 7.0 in a mac with osx-10-11-2 and it 
 crashes.

 ┌┐

 │ SageMath Version 7.0, Release Date: 2016-01-19 │

 │ Type "notebook()" for the browser-based notebook interface.│

 │ Type "help()" for help.│

 └┘

 This looks like the first time you are running Sage.

 Updating various hardcoded paths...

 (Please wait at most a few minutes.)

 DO NOT INTERRUPT THIS.

 Done updating paths.


 **


 Oops, Sage crashed. We do our best to make it stable, but...

 [...]

 I have tried both with
 *sage-7.0-OSX_10.11.2-x86_64.dmg 
 *
 and with
 *sage-7.0-OSX_10.11.2-x86_64.app.dmg 
 *

 I include Sage_crash_report.txt

 Yours,

 Juan Luis Varona



-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/gro

[sage-support] Re: Sage 7.0 crashes

[Volker Braun]

Output of "otool -L" for cliquer.so and libcliquer.so?



On Tuesday, January 26, 2016 at 8:04:33 AM UTC-5, Dima Pasechnik wrote:
>
> I can reproduce this. I downloaded the 
> ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
> unpacked and copied in /Applications/
> and started /Applications/Sage/sage in the terminal. And ended up with the 
> same crash on clique.so load.
>
> It could be due to old hardware:
>
> MacBook Air (13-inch, Late 2010)
>
>   Model Name: MacBook Air
>
>   Model Identifier: MacBookAir3,2
>
>   Processor Name: Intel Core 2 Duo
>
>   Processor Speed: 1.86 GHz
>
>   Number of Processors: 1
>
>   Total Number of Cores: 2
>
>   L2 Cache: 6 MB
>
>   Memory: 4 GB
>
>   Bus Speed: 1.07 GHz
>
>   Boot ROM Version: MBA31.0061.B01
>
>   SMC Version (system): 1.66f61
>
> I don't know on which hardware the binary distro was built, I suspect on 
> something newer (Core2 Duo is really old and a bit weird).
> It might be missing some processor commands which are used in the binary...
>
>
> Solution: rebuild Sage from source.
>
> Dima
>
>
> On Tuesday, 26 January 2016 02:15:38 UTC, Volker Braun wrote:
>>
>> Does the file exist? From the log:
>>
>> ImportError: 
>> dlopen(/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so,
>>  
>> 2): Library not loaded: libcliquer.so
>>   Referenced from: 
>> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>>   Reason: image not found
>>
>>
>>
>>
>> On Monday, January 25, 2016 at 7:52:42 PM UTC-5, Juan Luis Varona wrote:
>>>
>>> I have tried to install sage 7.0 in a mac with osx-10-11-2 and it 
>>> crashes.
>>>
>>> ┌┐
>>>
>>> │ SageMath Version 7.0, Release Date: 2016-01-19 │
>>>
>>> │ Type "notebook()" for the browser-based notebook interface.│
>>>
>>> │ Type "help()" for help.│
>>>
>>> └┘
>>>
>>> This looks like the first time you are running Sage.
>>>
>>> Updating various hardcoded paths...
>>>
>>> (Please wait at most a few minutes.)
>>>
>>> DO NOT INTERRUPT THIS.
>>>
>>> Done updating paths.
>>>
>>>
>>> **
>>>
>>>
>>> Oops, Sage crashed. We do our best to make it stable, but...
>>>
>>> [...]
>>>
>>> I have tried both with
>>> *sage-7.0-OSX_10.11.2-x86_64.dmg 
>>> *
>>> and with
>>> *sage-7.0-OSX_10.11.2-x86_64.app.dmg 
>>> *
>>>
>>> I include Sage_crash_report.txt
>>>
>>> Yours,
>>>
>>> Juan Luis Varona
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage 7.0 crashes

[Juan Luis Varona]

My mac is similar:

  Nombre del modelo: MacBook Air

  Identificador del modelo: MacBookAir3,1

  Nombre del procesador: Intel Core 2 Duo

  Velocidad del procesador: 1.4 GHz

  Cantidad de procesadores: 1

  Cantidad total de núcleos: 2

  Caché de nivel 2: 3 MB

  Memoria: 4 GB

  Velocidad del bus: 800 MHz

  Versión de la ROM de arranque: MBA31.0061.B07

  Versión SMC (sistema): 1.67f10


I will try to compile from the source code.


Thanks,


Juan Luis

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage 7.0 crashes

[Dima Pasechnik]

I can reproduce this. I downloaded 
the 
ftp://ftp.fu-berlin.de/unix/misc/sage/osx/intel/sage-7.0-OSX_10.11.2-x86_64.dmg
unpacked and copied in /Applications/
and started /Applications/Sage/sage in the terminal. And ended up with the 
same crash on clique.so load.

It could be due to old hardware:

MacBook Air (13-inch, Late 2010)

  Model Name: MacBook Air

  Model Identifier: MacBookAir3,2

  Processor Name: Intel Core 2 Duo

  Processor Speed: 1.86 GHz

  Number of Processors: 1

  Total Number of Cores: 2

  L2 Cache: 6 MB

  Memory: 4 GB

  Bus Speed: 1.07 GHz

  Boot ROM Version: MBA31.0061.B01

  SMC Version (system): 1.66f61

I don't know on which hardware the binary distro was built, I suspect on 
something newer (Core2 Duo is really old and a bit weird).
It might be missing some processor commands which are used in the binary...


Solution: rebuild Sage from source.

Dima


On Tuesday, 26 January 2016 02:15:38 UTC, Volker Braun wrote:
>
> Does the file exist? From the log:
>
> ImportError: 
> dlopen(/Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so,
>  
> 2): Library not loaded: libcliquer.so
>   Referenced from: 
> /Applications/SageMath/local/lib/python2.7/site-packages/sage/graphs/cliquer.so
>   Reason: image not found
>
>
>
>
> On Monday, January 25, 2016 at 7:52:42 PM UTC-5, Juan Luis Varona wrote:
>>
>> I have tried to install sage 7.0 in a mac with osx-10-11-2 and it crashes.
>>
>> ┌┐
>>
>> │ SageMath Version 7.0, Release Date: 2016-01-19 │
>>
>> │ Type "notebook()" for the browser-based notebook interface.│
>>
>> │ Type "help()" for help.│
>>
>> └┘
>>
>> This looks like the first time you are running Sage.
>>
>> Updating various hardcoded paths...
>>
>> (Please wait at most a few minutes.)
>>
>> DO NOT INTERRUPT THIS.
>>
>> Done updating paths.
>>
>>
>> **
>>
>>
>> Oops, Sage crashed. We do our best to make it stable, but...
>>
>> [...]
>>
>> I have tried both with
>> *sage-7.0-OSX_10.11.2-x86_64.dmg 
>> *
>> and with
>> *sage-7.0-OSX_10.11.2-x86_64.app.dmg 
>> *
>>
>> I include Sage_crash_report.txt
>>
>> Yours,
>>
>> Juan Luis Varona
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: [sage-edu] Writing 'n' variables in Sagemath linux ubuntu

[David Joyner]

This is the wrong email list for this sort of question. I'm cc'ing
sage-support. If you have a topic or question about teaching with
Sagemath, please post that here.

BTW, I googled your question and came up with this:
http://ask.sagemath.org/question/7925/a-list-of-symbolic-variables/
I'm not sure if that is what you want.


On Tue, Jan 26, 2016 at 3:01 AM, Usman Afzal  wrote:
> If I want to write one variable, the command is
> x=var('x')
>
> But I want to write "n" variables namely x1, x2, . . . , x(n). How can I
> write this?
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-edu+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-edu.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.