On Mon, 5 Oct 2015, Dima Pasechnik wrote:
In docstrings we have \leq converted to <=, can't we use unicode, and
get ≤? More importantly, can we do similar things to \cap (∩) and \cup
(∪), and perhaps even more of this?
What we assume the user to have on command line?
I just read your email i
Followup: I just solved my own problem, so I can share my story in case it
helps...
My system (a big shared cluster) has a modular system for loading/unloading
standard packages, including Python. The standard python2 provided by the
system is somewhat older (2.7.3, as you can see from the path
The same thing just happened to me! Here's the traceback I got:
gcc -pthread -L/gpfs_home/kedlaya/sage-6.8/local/lib -Xlinker
-export-dynamic -o python \
Modules/python.o \
-L. -lpython2.7 -lpthread -ldl -lutil -lm
LD_LIBRARY_PATH=/gpfs_home/kedlaya/sage-6.8/local/var/tmp/sage/build/python2
>
>
> Also this does not work with all (longer?) functions in the notebook. Try
>
> g = Graph()
> g.plot??
>
> for an example of one kind of a bug.
>
>
In the notebook sometimes if there is something with
Traceback...
then it cuts off there, see https://github.com/sagemath/sagenb/issues/34
"
>
> The source code of Python built-ins can not be obtained by the "??". But
> if you have an object (a function, a type, and instance, ...) that is
> defined in the SageMath library, then "??" should give you the source code
> and "?" should give you the doc string. If it doesn't then it is a
src/sage/misc/sagedoc.py
On Monday, October 5, 2015 at 9:37:49 PM UTC+2, Dima Pasechnik wrote:
>
>
>
> On Monday, 5 October 2015 12:20:45 UTC-7, Volker Braun wrote:
>>
>> +1: write a patch
>>
>
> do you know where to look for the code doing the replacement '\leq' ->
> '<=' ?
>
>
>>
>> On Monday
On Monday, 5 October 2015 12:20:45 UTC-7, Volker Braun wrote:
>
> +1: write a patch
>
do you know where to look for the code doing the replacement '\leq' -> '<='
?
>
> On Monday, October 5, 2015 at 9:10:30 PM UTC+2, Dima Pasechnik wrote:
>>
>> In docstrings we have \leq converted to <=, can'
+1: write a patch
On Monday, October 5, 2015 at 9:10:30 PM UTC+2, Dima Pasechnik wrote:
>
> In docstrings we have \leq converted to <=, can't we use unicode, and get
> ≤? More importantly, can we do similar
> things to \cap (∩) and \cup (∪), and perhaps even more of this?
>
> Dima
>
--
You rece
In docstrings we have \leq converted to <=, can't we use unicode, and get ≤?
More importantly, can we do similar
things to \cap (∩) and \cup (∪), and perhaps even more of this?
Dima
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscrib
On Mon, 5 Oct 2015, kcrisman wrote:
sage: lagrange_polynomial?? # should be code
Note that the latter doesn't always work (for instance Python built-ins,
or some (all?) Cythonized functions) or so it seems to me.
Also this does not work with all (longer?) functions in the notebook. Try
g =
Hi Karl-Dieter,
On 2015-10-05, kcrisman wrote:
>> Hi everyone, where it is possible to find the code of each command or
>> maybe documentation? For example lagrange_polynomial. How can one see the
>> function code, but documention would be better. Thank you in advance.
>>
>
> sage: lagrange_pol
On 10/05/2015 10:05 AM, Dmitrij Moreinis wrote:
> Hi everyone, where it is possible to find the code of each command or
> maybe documentation? For example lagrange_polynomial. How can one see
> the function code, but documention would be better. Thank you in advance.
>
Type the function name foll
> Hi everyone, where it is possible to find the code of each command or
> maybe documentation? For example lagrange_polynomial. How can one see the
> function code, but documention would be better. Thank you in advance.
>
sage: lagrange_polynomial? # should be doc
sage: lagrange_polynomial?? #
Hi everyone, where it is possible to find the code of each command or maybe
documentation? For example lagrange_polynomial. How can one see the
function code, but documention would be better. Thank you in advance.
--
You received this message because you are subscribed to the Google Groups
"sa
Hi, thanks you very much, it works for me atm. I hope an official fix in
the future.
El lunes, 5 de octubre de 2015, 6:48:50 (UTC+2), Dima Pasechnik escribió:
>
> it seems that you will need to disable SIP:
> https://groups.google.com/d/msg/sage-devel/OBv5x1v3_6M/sOunnE-7BQAJ
>
>
> On Sunday, 4 O
15 matches
Mail list logo