Re: [sage-support] Re: Snowman

[Samuel Lelièvre]

2022-01-20 03:49 UTC, Kwankyu:
>
> As I wish that the artwork by Samuel Lelièvre is not lost, I posted it here:
>
> https://wiki.sagemath.org/art#Snowman
>
> if the author permits. If not, let me know.

Fine with me. You should add your snow person too!
Then they can keep each other company:

sage: snowies = Graphics()
sage: snowies += P.translate(0, 0,
4).scale(2).rotateZ(-pi/5).translate(0, -4, 0)
sage: snowies += snowie.rotateZ(pi/5).translate(0, 3, 0)
sage: snowies.show(frame=False)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF2aWyZW08cA_-sUgt9i7POVnntxs5q4BH7v9op2hTq4yA%40mail.gmail.com.

Re: [sage-support] Re: LatexExpr

[Samuel Lelièvre]

2021-11-30 17:46 UTC, Cyrille Piatecki:
>
> Thanks John. But LatexExpr(r"\text{there"'"s a way} x_i =")
> generates a mistake.

John's suggestion was that a string that contains
both single-quote and double-quote characters
can be enclosed by tripled delimiters, using
either '''...''' or """...""".

More examples:

LatexExpr(r"\text{there's a way } x_i =")
LatexExpr(r'''\text{there's a way } y' + y" = 0''')
LatexExpr(r"""\text{there's a way } y' + y" = 0""")

See more on strings, also known as "text sequences",
in the Python documentation for built-in types:

https://docs.python.org/3/library/stdtypes.html#textseq

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF2ZmBE66XSAudqt0MOeU82yvt7ctgtoksoFyFX2JuGSZw%40mail.gmail.com.

Re: [sage-support] Re: after upgrade to 9.3, SignalError: Illegal instruction

[Samuel Lelièvre]

Would it help to set `CFLAGS` to `-mno-avx -mno-avx2 -mno-bmi2`
as is done for building the Sage macOS app? --Samuel

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF1s%2BfkpDdjm%2Bygf%3DBofXs%3DZcLhxGvVAq-M8XSAebcF_5A%40mail.gmail.com.

Re: [sage-support] Re: after upgrade to 9.3, SignalError: Illegal instruction

[Samuel Lelièvre]

2021-08-24 05:48 UTC, Dima Pasechnik:
>
> These "illegal instruction" errors are an indication
> that the binary was built for a more advanced CPU
> than yours - which does not support certain CPU
> commands. It's a bug in "fat binary" build process
> we see for some time.
>
> Build Sage yourself, or use Conda.

I opened a ticket at binary-pkg for that:
https://github.com/sagemath/binary-pkg/issues/31

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF0wWB3Lq%2B%2BMuUA6t_hPnzp4axT5G8hUDkYR4yMtG%2Boz8w%40mail.gmail.com.

Re: [sage-support] NumberFieldEmbedding gets confused with relative number fields

[Samuel Lelièvre]

2021-04-28 15:32 UTC+2, Ilia:
> On Saturday, April 24, 2021 at 1:33:36 AM UTC+2 slelievre wrote:
> > Could this have to do with one of the following existing tickets?
> >
> > - Sage Trac ticket 22008
> >  complex_embedding on relative number fields is inconsistent with the base 
> > field
> >   https://trac.sagemath.org/ticket/22008
>
> This is indeed related: it also involves Sage mistaking the extension [L:K]
> for the extension [L:QQ]. But it does not seem to be the exact same
> problem: I am not sure that fixing ticket 17524 would automatically
> fix the problem I am describing here. Well, it *might*; but the only way
> to be sure is to actually pinpoint the problem - and this would involve
> a complex hunt through a lot of different code files that I (being a total
> newbie to Sage development) do not feel like doing right now.
>
> > - Sage Trac ticket 17524
> >   polynomial for relative number field elements
> >   https://trac.sagemath.org/ticket/17524
>
> This one, OTOH, seems a bit different: in this one, there is no confusion
> between [L:K] and [L:QQ], but simply a problem of consistency between
> the chosen embedding of K when taken by itself and the chosen
> embedding of K when seen as a subfield of L.

I agree.

> On Saturday, April 24, 2021 at 9:51:27 PM UTC+2 vdelecroix wrote:
>>
>> At least on 9.3.rc4 it is fixed by using instead
>>
>> sage: K. = QuadraticField(2, embedding=AA(2).sqrt())
>> sage: L. = K.extension(x^3 + (sqrt2/2 + 1/3)*x^2 + (2*sqrt2/5+3/7)*x - 1)
>> sage: phi0 = hom(L, QQbar, roots[0])
>> sage: phi1 = hom(L, QQbar, roots[1])
>> sage: phi2 = hom(L, QQbar, roots[2])
>> sage: phi0(sqrt2)
>> 1.414213562373095?
>> sage: phi1(sqrt2)
>> 1.414213562373095? + 0.?e-17*I
>> sage: phi2(sqrt2)
>> 1.414213562373095? + 0.?e-17*I
>
>
> For what it is worth, in my config (version 9.1), this gives
> a "ValueError: relations do not all (canonically) map to 0
> under map determined by images of generators". So, OK,
> presumably this has been fixed in the meanwhile.

You can try Sage 9.2 at SageCell:

https://sagecell.sagemath.org

> But anyway,
> where can I find documentation for the "hom" method?

sage: hom?
sage: hom??
sage: browse_sage_doc(hom)

sage: Hom?
sage: Hom??
sage: browse_sage_doc(Hom)

https://doc.sagemath.org/html/en/reference/categories/sage/categories/homset.html
https://doc.sagemath.org/html/en/reference/categories/sage/categories/homsets.html

> Assuming it works, OK, thank you, it is a good workaround.
> Still, in the meanwhile, I think that something needs to be
> done about NumberFieldEmbedding: it should either be
> fixed, be deprecated, or at least the documentation should
> be updated to signal that it does not work in relative fields.
> So I guess I will now try to open a ticket.

Sounds good.  --Samuel

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF3EvkUJcoKOAkGaSD5ZRvVARc7_vFAW%2BxgDsGZkh0UWtQ%40mail.gmail.com.

Re: [sage-support] problems again installing Sage9.1 (and 9.2)

[Samuel Lelièvre]

¡Hola Anita!

You could try the new macOS app, currently in beta testing at:

https://github.com/3-manifolds/Sage_macOS/releases/
Let us know if it solves your problems.  --Samuel

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF18DCUC%3DhdL%2Bq%2BXC4nrcV6qhbpPiHD006d4QOxjmpic%3Dg%40mail.gmail.com.

Re: [sage-support] Re: Install of sage on macOS

[Samuel Lelièvre]

Le mer. 23 déc. 2020 à 14:55, Mouse Mousevich:
>>
>> the MacPorts-specific part would be to create a list of packages to install, 
>> and put it into build/pkgs/*/distros/macports
>> and a similar global location.
>
> I'm not sure I understand what that means. If a package is already installed
> by Macports - it does not make sense installing it again. More so, Macports
> keeps a system-wide installation, rather than a copy for each user.

For each package `pkgname` Sage uses, the `build/pkg/pkgname` folder
contains information about building and about not-building this package.
The not-building information is a folder `distros` with a bunch of text files,
one per distro, containing the name of the package in that distro that can
be used if present instead of building it. For an example, see

https://github.com/sagemath/sage/tree/develop/build/pkgs/openssl/distros

The various text files there tell the Sage build system what package
to check for. Depending on the distro, that might be one of:

libressl-openssl
libssl-dev
libssl-devel
openssl
openssl openssl-devel
openssl openssl-solibs
openssl-dev
security/openssl

To support using the packages from MacPorts, we need

- a file build/pkgs/macports.txt with information on core packages,
  see all the text files in

  https://github.com/sagemath/sage/tree/develop/build/pkgs/

- and for each "spkg", a macports.txt file containing the name of
  the equivalent MacPorts package to check for (and to recommend
  installing if not present)

See recent work on adding support for voidlinux

https://trac.sagemath.org/query?order=id=1=~voidlinux=~void%20linux

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF00JbEwFLMPu9-192TzhOhhtaZR2wY1aFAOZD2SutDVbQ%40mail.gmail.com.

Re: [sage-support] Re: factorial

[Samuel Lelièvre]

Le lun. 30 nov. 2020 à 13:37, Dima Pasechnik  a écrit :
>
> On Mon, Nov 30, 2020 at 9:16 AM Vincent Delecroix
> <20100.delecr...@gmail.com> wrote:
> >
> > Le 30/11/2020 à 00:48, slelievre a écrit :
> > > 2020-11-29 21:23:36 UTC, Guillermo:
> > >>
> > >> I wonder what would be wrong with replacing '!' → '.factorial()'
> > >
> > > Interesting idea. Just be careful with `!=` of course.
> > >
> >
> > Indeed the expression "3!=3" is ambiguous... Of course one can choose
> > a priority (3!)=(3) or (3)!=(3) but that would be much more error
> > prone than using .factorial() from the start.
>
> I think .factorial() will do. Perhaps this can be combined with
> looking for deprecation issues vs factorial() and Python 3.9.
>
> From python 3.9 docs:
>
> Currently math.factorial() accepts float instances with non-negative
> integer values (like 5.0).
> It raises a ValueError for non-integral and negative floats. It is now
> deprecated.
> In future Python versions it will raise a TypeError for all floats.
> (Contributed by Serhiy Storchaka in bpo-37315.)
> https://bugs.python.org/issue37315

Dealing with that deprecation is the object of:

- Sage Trac ticket 30764
  Adapt to float factorial deprecation in Python 3.9
  https://trac.sagemath.org/ticket/30764

in case anyone wants to give it a go.

Preparsing `!` to `.factorial()` is orthogonal enough
that I think it deserves its own ticket. I opened

- Sage Trac ticket 30982
  Preparse ! for factorial
  https://trac.sagemath.org/ticket/30982

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF1ZXTbzQb2_scKfO9QyAHh_oXR-QBmXUDL9%2BqG-4__3yA%40mail.gmail.com.

[sage-support] Re: [sage-release] zenodo (DOI) for Sage releases is back!

[Samuel Lelièvre]

Added to the Sage 9.1 Release Tour.


Le mar. 6 oct. 2020 à 22:46, Dima Pasechnik  a écrit :
>
> We've recovered the settings for getting DOI for Sage releases via
> zenodo, something that was broken for years.
> cf https://zenodo.org/record/4066866
> and this is DOI for Sage 9.1: https://doi.org/10.5281/zenodo.4066866
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/CAAWYfq1%2BmY1uULNUsEXwOk8rVyYVJ0%3DxJ9EoRp2naDFz7o99xg%40mail.gmail.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF2wErjoYXFfsvzVWPE4Li2ASVvjJawOJ9k%3DEDEWQyVJ8w%40mail.gmail.com.

Re: [sage-support] Re: Installation fails

[Samuel Lelièvre]

I suggest leaving the anti-virus disabled for SageMath forever.

Should you re-enable it, it might decide to block or remove vital
parts of Sage, making it non-functional, and resulting in crashes.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF0nsJMAeowHSvnai-DgeZ6VWrW17jUg34021d1%2BDrfRgw%40mail.gmail.com.

Re: [sage-support] Apparently Sage lost Python

[Samuel Lelièvre]

Forgot one step. Run this:

sage -i gap_packages
After that, the steps indicated earlier should work.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF18yaZKbDR-W23%2BSn21mZUSf9uB8MWc6sm1c0Wr7EOcDA%40mail.gmail.com.

[sage-support] Lie algebra morphism, mutable matrices, basis not defined

[Samuel Lelièvre]

Dear sage-support,

At Sage Days 106 we are trying to learn some of the
Lie algebra functionality in SageMath and have two
small questions regarding Lie algebra morphisms.

We define the Lie algebra sl_2(QQ) in two ways as follows:

sage: sl2 = lie_algebras.sl(QQ, 2, representation='matrix')
sage: sl2.inject_variables()
Defining e1, f1, h1
sage: sl2bis = LieAlgebra(QQ, {('e', 'h'): {'e': -2}, ('f', 'h'):
{'f': 2}, ('e', 'f'): {'h': 1}}, names='e, f, h')
sage: sl2bis.inject_variables()
Defining e, f, h

Trying to define a Lie algebra morphism between the two
fails with this error:

sage: sl2.morphism({e1: e, f1: f, h1: h})
Traceback (most recent call last)
...
TypeError: mutable matrices are unhashable

and I was wondering why the basis is not made
of immutable matrices.

Trying to define the morphism the other way around,
fails with this error:

sage: sl2bis.morphism({e: e1, f: f1, h: h1})
Traceback (most recent call last)
...
NotImplementedError: the basis is not defined

and I was wondering what is the problem here.

Kind regards,
Samuel Lelièvre

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAEcArF2%2Bh4FtFXGNXo7-aRPeiwzzRAGE%2BzSOsocvU545TFfpag%40mail.gmail.com.

Re: [sage-support] Re: infos

[Samuel Lelièvre]

You may have to install bzip2 and maybe libbz2-dev

sudo apt-get install bzip2 libbz2-dev

Then you should be able to extract with

tar xjf sage*.bz2

or simply

tar xf sage*.bz2

-- 
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: maximal integrals

[Samuel Lelièvre]

Le mar. 19 févr. 2019 à 23:39, Nils Bruin  a écrit :
>
> On Tuesday, February 19, 2019 at 2:04:54 PM UTC-8, slelievre wrote:
>>
>> but how does one get information in a Maxima session about settings
>> such as besselexpand, display2d, domain, keepfloat,
>
> These are just global variables, so "display2d;" will give you the value.
>
>> and loaded
>> modules such as to_poly_solve, simplify_sum, abs_integrate, diag?
>
> I think apropos("");  will usually give different results,
> depending on whether the package has been loaded or not.

Thanks for explaining. But is there a way to get the value of all global
variables, or all that don't have their default values? And to get a list of
all packages that are loaded but are not usually when Maxima starts?
It would be nice if `bug_report();` would include that information.

-- 
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: Weird behavior in sagecell

[Samuel Lelièvre]

Sat 2018-12-01 01:02 UTC, slelievre:
>
> Fri 2018-11-30 23:43 UTC, David Guichard:
>>
>> In this page,
>>
>> http://skink.whitman.edu/~guichard/sage/two_plots_clean.html
>>
>> I have two sagecells, each to do a 3d plot. If I evaluate the first one, it 
>> works as expected. If I then evaluate the second, it graphs correctly, but 
>> it also replaces the first plot with a copy of the second. Neither of them 
>> is "live", that is, I can't rotate either version.
>>
>> If I first evaluate the second cell, it works as expected. If I then 
>> evaluate the first one, it also works as expected: I end up with two 
>> (different) plots, both live.
>>
>> I'd appreciate knowing how to fix this, if it's possible. I have tried a few 
>> things, such as changing the outputLocation, but nothing has worked so far.
>>
>> Thanks,
>> David
>
>
> Not sure how to explain what happens there,
> or how to really fix it if sticking to jsmol is important.
>
> If you do the 3D-plotting with three.js however,
> the problem goes away.
>
> This just amounts to adding viewer='threejs'
> at the end of the plotting commands.

See a similar report on the sage-cell mailing list:
https://groups.google.com/d/topic/sage-cell/BL9h7xLiwG4/discussion

In the discussion there, Andrey Novoseltsev points out
that SageMathCell uses only one jsmol instance, and
if there are several plots using it, they might conflict in
hard to predict ways. He recommends using three.js.

three.js (called "threejs" in Sage) is a javascript 3D-plotting library.
https://threejs.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: Route inspection problem

[Samuel Lelièvre]

Have you tried following the NetworkX tutorial?

https://networkx.github.io/documentation/latest/tutorial.html


2018-04-03 9:52 GMT+02:00 Henri Girard :

> Do you think it's possible to draw fano's plane with networkx ?
>
> I have been looking on internet but no answer yet
>
> Le 03/04/2018 à 08:52, slelievre a écrit :
>
> Or you can turn off the Sage preparser.
>
> preparser(False)
> edgelist.head(10)
>
>
> Le mardi 3 avril 2018 08:44:29 UTC+2, slelievre a écrit :
>>
>> Or you can do edgelist.head(int(10))
>>
>> 2018-04-03 8:00 GMT+02:00 Henri Girard:
>>
>>> Thanks, i must write it to each command but it works well
>>>
>> --
> 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 a topic in the
> Google Groups "sage-support" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-support/E5OW4M4Frlw/unsubscribe.
> To unsubscribe from this group and all its topics, 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: [sage-support] Re: Route inspection problem

[Samuel Lelièvre]

Or you can do edgelist.head(int(10))

2018-04-03 8:00 GMT+02:00 Henri Girard :

> Thanks, i must write it to each command but it works well
>

-- 
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: Error building Sage 8.1 on Ubuntu 16.04 :make: *** [all] Error

[Samuel Lelièvre]

2018-03-13 14:05 GMT+01:00 :
>
> Thanks for the replies. Great help. Now sage is working properly. :)

Good that you managed to get a working Sage installation!

Dima suggests to post copied and pasted input and output of
a terminal session, rather than screenshots. I agree for two
reasons: text material can be copied and pasted again (while
a screenshot is less useful in that respect), and eats less
storage and bandwidth. Keep that in mind for next 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] Importing extra libraries on SageMathCloud such as qutip

[Samuel Lelièvre]

2018-01-25 10:20 GMT-06:00 slelievre :
>
> Le samedi 30 décembre 2017 04:55:27 UTC-6, Manosh Tm a écrit :
>>>
>>> It will be effective if the Qutip package comes with SAGE.
>>
>> Manosh T M
>
> Note: in general, avoid replying to a very old message on a mailing list.
> Instead, open a new thread (and if you wish, you can include a link to
> the old message that you are referencing).


William Stein's 2014 post to this list, that you replied to, had a link to:

https://github.com/sagemath/cloud/wiki/FAQ#wiki--question-i-found-an-awesome-python-package-at-httpspypipythonorgpypi-and-i-want-to-use-it

which is now obsolete. The corresponding up-to-date FAQ item is now at:

https://github.com/sagemathinc/cocalc/wiki/How-to-Install-Python-Packages-into-CoCalc

-- 
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] Importing extra libraries on SageMathCloud such as qutip

[Samuel Lelièvre]

2018-01-25 10:02 GMT-06:00 Ger Tielemans :
>
> .. and what about the library PCRaster?
>  http://pcraster.geo.uu.nl/
>
> Op zaterdag 30 december 2017 18:55:30 UTC+1 schreef slelievre:
>>
>> Note that QuTiP is available system-wide on CoCalc:
>> https://cocalc.com/doc/software-python.html

I opened a ticket to get PCRaster installed on CoCalc:

https://github.com/sagemathinc/cocalc/issues/2661

You can add a comment to give more context and say how this
would be useful to a wide community.

Samuel

-- 
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 for Windows, when?

[Samuel Lelièvre]

Henri, could you say more precisely what you mean by
"Jupyter notebooks run but do no calculation"?

Samuel

2017-04-29 16:01 GMT+02:00 HG :

> I installed it on w10 and w7 works fine in sagenb, jupyper notebook runs
> but do no calculation. It's a bit slow because my pc-s are really old
> stuff, but better that virtualbox and I am unpatient to test sage-8 (linux
> sage-8 beta 4 works fine )
> Le lundi 24 avril 2017 11:54:31 UTC+2, Jim Mooney a écrit :
>>
>> Sage is so painfully slow on win 8.1 since it's run in a virtualbox, I
>> had to fall back to Maxima (which is fine for now, but I'll want Sage
>> eventually). I don't want to partition and dual-boot linux, and running
>> linux from a flash drive only allows a tiny amount of storage for Sage,
>> even with a big flash drive. Is there any progress on Sage for Windows? Or
>> an ETA?
>>
>

-- 
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] recent woes with relocation of SageMath installation directory

[Samuel Lelièvre]

Dear sage-support (cc: sage-release, sage-devel)
(please reply on sage-support only)

I received the following question after announcing
Sage 7.0 on sage-announce.

This is one of many such questions I am reading on
various lists and sites recently.

Something needs to be more clearly documented,
or refactored.

Can someone answer this question by replying to
this post on sage-support?

Thanks!
Samuel

-- Forwarded message --
Date: Mon, 1 Feb 2016 23:32:31 -0600
To: Samuel Lelievre 
Subject: Installing upgraded SageMath

I tried installing sagemath-upstream-binary on my Ubuntu Trusty Tahr
system and saw this:

Rewriting paths for your new installation directory
===

This might take a few minutes but only has to be done once.

patching /usr/lib/sagemath/src/build/cythonized/sage/structure/list_clone.c
Traceback (most recent call last):
  File "/usr/lib/sagemath/relocate-once.py", line 85, in 
p('src/build/cythonized/sage/structure/list_clone.c').substitute().save()
  File "/usr/lib/sagemath/relocate-once.py", line 70, in __call__
return FilePatch(self, filename)
  File "/usr/lib/sagemath/relocate-once.py", line 21, in __init__
self.st = os.stat(filename)
OSError: [Errno 2] No such file or directory:
'/usr/lib/sagemath/src/build/cythonized/sage/structure/list_clone.c'

Any idea what is up?

Dale Amon

-- 
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] ideal in ring of integers: QQ vs number field

[Samuel Lelièvre]

Just to bring atttention to a question at math.stackexchange:

http://math.stackexchange.com/questions/1294942/mathbbq-isnt-a-number-field-for-sage

-- 
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 http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.