[sage-devel] Re: Sage bdist changes (OSX El Capitan)

2015-11-24 Thread Dima Pasechnik
On Monday, 23 November 2015 21:42:17 UTC, Volker Braun wrote: > > On Monday, November 23, 2015 at 10:40:11 PM UTC+1, Dima Pasechnik wrote: >> >> And, does it need that Apple's new security thing off, or not? >> > > Not required. > great, I can confirm that this gives seemingly working Sage in

[sage-devel] Re: Sage bdist changes (OSX El Capitan)

2015-11-24 Thread Volker Braun
I'm pretty sure its IO bound, so parallelization won't help. You have to run it only once anyways... On Tuesday, November 24, 2015 at 3:27:49 PM UTC+1, Dima Pasechnik wrote: > > great, I can confirm that this gives seemingly working Sage in such a > settings (SIP on, i.e. as 99% of users will ha

[sage-devel] install_package('whatever')

2015-11-24 Thread Nathann Cohen
Hello everybody, I just read a question on AskSage [1] from a user who attempted to install an optional package. As you can read from his message he did not understand what 'typing sage -i' in a terminal exactly meant, and was apparently stuck, unable to install this package. Is there a technical

Re: [sage-devel] Re: A new book on Sage, for high school students in Poland

2015-11-24 Thread Andrzej Giniewicz
Thank you! On Tue, Nov 24, 2015 at 8:52 AM, slelievre wrote: > Fixed. > > 2015-11-17 09:45:23 UTC+1, Andrzej Giniewicz: > >> I noticed book is already there, but Author names were copy-pasted >> from position above. This should be "Andrzej Giniewicz and Katarzyna >> Zajączkowska" - not "Thorsten

[sage-devel] Re: install_package('whatever')

2015-11-24 Thread Volker Braun
How does install_package work? a) run os.system('sage -i') which may or may not modify shared libraries currently in use in Sage. Possibly crashes Sage, corrupts worksheets, etc. Aka "I'm feeling lucky" b) Close the Python interpreter, then run sage -i from a shell script, then restart sage T

[sage-devel] Re: install_package('whatever')

2015-11-24 Thread Nils Bruin
On Tuesday, November 24, 2015 at 1:43:03 PM UTC-8, Volker Braun wrote: > > The real question is: Why are we still shipping the old SageNB as default > notebook? It does have usability issues, in particular no way to extend it > with non-Sage stuff. E.g. the IPython notebook has a built-in termina

[sage-devel] Re: install_package('whatever')

2015-11-24 Thread Andrey Novoseltsev
On Tuesday, 24 November 2015 17:49:53 UTC-7, Nils Bruin wrote: > > On Tuesday, November 24, 2015 at 1:43:03 PM UTC-8, Volker Braun wrote: >> >> The real question is: Why are we still shipping the old SageNB as default >> notebook? It does have usability issues, in particular no way to extend it >

[sage-devel] Re: install_package('whatever')

2015-11-24 Thread Nils Bruin
On Tuesday, November 24, 2015 at 4:49:53 PM UTC-8, Nils Bruin wrote: > > On another computer I got something different (and that's an up-to-date > fedora 22!): > > XPCOMGlueLoad error for file /usr/lib64/firefox/libxul.so: > /usr/lib64/firefox/libxul.so: undefined symbol: sqlite3_unlock_notify >

Re: [sage-devel] Re: install_package('whatever')

2015-11-24 Thread Jori Mäntysalo
On Tue, 24 Nov 2015, Andrey Novoseltsev wrote: The real question is: Why are we still shipping the old SageNB as default notebook? Note also that it supports multiple accounts - I am not sure how many of "personal" Sage installs are for teaching purposes, but there it is crucial. So actual