On Thursday, 28 January 2016 20:20:27 UTC, Juan Luis Varona wrote:
>
>
>>
>> run the following commands in the Terminal
>> ./sage -i openssl
>> ./sage -f python2
>>
>>>
>>>
>
> Thanks again! I have done it but, later, when using
> ./sage --notebook='jupyter'ed to run
>
hmm, you probably also ne
Intelligent students use any valuable software... And poor students
like open source... Look in india, in china where studying is reserved
to rich people, but not always the most intelligent ones
Le 28/01/2016 21:54, Juan Luis Varona a écrit :
>
> But let me a reflexion, not for you
True... These days I am discovering so many python ipython jupyter good
things that I am very astonished. How much would we pay if we had to buy
sage sagemanifold ipython and many others, visit ... The list is long !
But the problem is how to get money to found this.
Regards
Henri
Le 28/01/2016
Hi
I don't agree with what you are saying...
There are so many examples : google search I do... sagemath /pub/sws
And most of all sagenb server in the world will show to you !
With ubuntu it was quiete easy (I compiled it now, on ubuntu it's very
easy), I just discovered jr Johanson ipython noteb
>
> > But let me a reflexion, not for you but for the sage community (sorry
> for my
> > bad English): I'm s university math professor in Spain, and I explain
> > sagemath to my students. How is possible to promote sagemath between the
> > students if only to install it is so complicate, al
On Thu, Jan 28, 2016 at 12:20 PM, Juan Luis Varona
wrote:
>>
>>
>> run the following commands in the Terminal
>> ./sage -i openssl
>> ./sage -f python2
>>>
>>>
>
>
> Thanks again! I have done it but, later, when using
> ./sage --notebook='jupyter'
> I get the same error message.
>
> Do not worry,
>
>
>
> run the following commands in the Terminal
> ./sage -i openssl
> ./sage -f python2
>
>>
>>
Thanks again! I have done it but, later, when using
./sage --notebook='jupyter'
I get the same error message.
Do not worry, I will try again when new binaries for mac of sage 7-0 appear
in the dow
On Thursday, 28 January 2016 01:30:56 UTC, Juan Luis Varona wrote:
>
>
>
> El miércoles, 27 de enero de 2016, 15:58:01 (UTC+1), Dima Pasechnik
> escribió:
>>
>>
>>
>> On Wednesday, 27 January 2016 04:10:42 UTC, Juan Luis Varona wrote:
>>>
>>> I have been able to compile Sage 7.0 from the source
It means your sage hasn't openssl you probably can use pip ?
sudo pip install ssl (or something else on mac)
I am on linux not on mac.
./sage -n=ipython is the command I use...
Time being I am not sure it is so clear with "notebook, jupyter, ipython"
I had to slightly hack to get everything workin
El miércoles, 27 de enero de 2016, 15:58:01 (UTC+1), Dima Pasechnik
escribió:
>
>
>
> On Wednesday, 27 January 2016 04:10:42 UTC, Juan Luis Varona wrote:
>>
>> 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 u
On Wednesday, 27 January 2016 04:10:42 UTC, Juan Luis Varona wrote:
>
> 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 o
On Wednesday, 27 January 2016 14:58:01 UTC, Dima Pasechnik wrote:
>
>
>
> On Wednesday, 27 January 2016 04:10:42 UTC, Juan Luis Varona wrote:
>>
>> 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()
On Wednesday, 27 January 2016 04:10:42 UTC, Juan Luis Varona wrote:
>
> 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 o
On Tuesday, 26 January 2016 20:40:07 UTC, Volker Braun wrote:
>
> I created http://trac.sagemath.org/ticket/19967 for dealing with cliquer
>
ready for review, by the way...
>
>
> On Tuesday, January 26, 2016 at 3:36:24 PM UTC-5, Volker Braun wrote:
>>
>> For the record, the OSX binaries are br
On Wed, Jan 27, 2016 at 12:55 AM, Jeroen Demeyer wrote:
> On 2016-01-26 17:08, William Stein wrote:
>>
>> He said that only dead code in maintenance only mode
>> should be added, etc., etc.
>
>
> So we can never add new features to Python? That's depressing...
Heh, I'm just reporting what he said
On 2016-01-26 17:08, William Stein wrote:
He said that only dead code in maintenance only mode
should be added, etc., etc.
So we can never add new features to Python? That's depressing...
I'm
actually really shocked that in all the discussion about getting
packages into Sage, we fixed on voti
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 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/Deve
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/
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 sou
> 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
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
> 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
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
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 wh
>> 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 w
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 ups
> 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
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
>
> 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
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 no
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 G
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
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 (com
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)
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 (compatibil
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:
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
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
/A
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/
> a
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
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:
El martes, 26 de enero de 2016, 3:15:38 (UTC+1), Volker Braun escribió:
>
> 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:
> /Applicati
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 f
44 matches
Mail list logo
