On 2015-11-27 09:06, Jori Mäntysalo wrote:
And server_pool makes it impossible to have %cython cells.
By the way, this is https://github.com/sagemath/sagenb/issues/260
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gro
On 2015-11-27 11:16, Jori Mäntysalo wrote:
On Fri, 27 Nov 2015, Jeroen Demeyer wrote:
And server_pool makes it impossible to have %cython cells.
As a workaround, doing
cython("""
# Cython code here
""")
does work.
Great!
Somebody please document this.
Or somebody fix %cython (one can w
On Fri, 27 Nov 2015, Jeroen Demeyer wrote:
And server_pool makes it impossible to have %cython cells.
As a workaround, doing
cython("""
# Cython code here
""")
does work.
Great!
Somebody please document this. That could be part of "Sagemath perfomance
tips" with Nathann Cohen's suggestio
On 2015-11-27 09:06, Jori Mäntysalo wrote:
And server_pool makes it impossible to have %cython cells.
As a workaround, doing
cython("""
# Cython code here
""")
does work.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from thi
On Thu, 26 Nov 2015, Volker Braun wrote:
The question was about the default notebook; We aren't going to remove
SageNB any time soon but for most users its not a good match. Also, jupyter
also has multiuser stuff (though not packaged in Sage), and a better
implementation thereof thats not totall
The question was about the default notebook; We aren't going to remove
SageNB any time soon but for most users its not a good match. Also, jupyter
also has multiuser stuff (though not packaged in Sage), and a better
implementation thereof thats not totally oblivious to security.
On Wednesday,
On Wednesday, November 25, 2015 at 8:50:15 PM UTC+1, Nils Bruin wrote:
>
> On Wednesday, November 25, 2015 at 2:23:27 AM UTC-8, Volker Braun wrote:
>>
>> LD_LIBRARY_PATH strikes again...
>>
> What can we do about it, though?
>
Simple: Do not use it. Use rpaths for libraries that you can't / don't
On Wednesday, November 25, 2015 at 2:23:27 AM UTC-8, Volker Braun wrote:
>
> LD_LIBRARY_PATH strikes again...
>
What can we do about it, though? I think the relevant module is
"webbrowser". It has rather complicated logic and is therefore rather hard
to convince to run a command through "sage-na
On Wed, 25 Nov 2015, Jeroen Demeyer wrote:
Code that needs some package should raise an error if the package is
not installed. And the interface should catch it and give consistent
and friendly error message. Either "Do this" or "Ask you system
administrator".
Do you have an example where t
On 2015-11-25 06:22, Jori Mäntysalo wrote:
Code that needs some
package should raise an error if the package is not installed. And the
interface should catch it and give consistent and friendly error
message. Either "Do this" or "Ask you system administrator".
Do you have an example where this i
LD_LIBRARY_PATH strikes again...
On Wednesday, November 25, 2015 at 4:47:59 AM UTC+1, Nils Bruin wrote:
>
> 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
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
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
>
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
>
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
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
16 matches
Mail list logo
