Iguananaut's profile - activity

You're not trying to run sage in cmd.exe are you?

Could you please break this up into two separate questions? At first I thought it was about setting the terminal colors

V 9.3 Installation Problems on Windows 10 I ran the installation without admin privileges, and the Sage Console seemed t

What do you mean "it looks like the installation process will never stop"? What is it doing? It could be there is a bug in the dependency resolution causing it to rebuild dependencies that it shouldn't. But even if that's the case just let it run its course.

It could also be a CPU incompatibility. Sage for Windows is compiled with the current maximum level of CPU compatibility but there could be some outliers, or if it's a very new CPU it might break MPIR or something.

This might be a Windows-specific quirk

It's not. They probably have BLODA

Chances are good you have BLODA. In particular some antivirus software is known to interfere with, or even delete files from Sage's installation since it's full of false-positives.

Possible duplicate of https://ask.sagemath.org/question/461...

When signing into ask.sagemath.org using Google I get

Authorization Error

Error 400: redirect_uri_mismatch The redirect URI in the request, https://ask.sagemath.org/account/sign..., does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com...

Out of curiosity why do you want to do this? Sage is a UNIX-based program and not really designed to work well in the Windows cmd shell, as you can tell from the ugly colors alone. I also can't promise that various things like keyboard commands will work well. Is there some other underlying goal? If so, perhaps there is a better way to achieve that goal.

See the documentation for the %edit magic. It's a little confusing, but it does not work exactly the same as entering the code directly in the interactive prompt. If you just write a bare expression like 1 + 1, although it will be evaluated, its results are not displayed. Instead you have to write something like print(1 + 1) if you want the results displayed when executing the code. The %edit command outputs the code entered as a string allowing you to do things like %edit _ to re-edit the previous code.

Sage 9.1 for Windows was released last week: https://github.com/sagemath/sage-wind... Sorry for the long delay on this one.

@Emmanual Charpentier: The information in your last comment is a bit inaccurate. There have been SageMath for Windows releases for some time now: https://wiki.sagemath.org/SageWindows I know you know this because you directly referred to it. But it is what is meant by "SageMath for Windows". The fact that it uses Cygwin is a technical detail not relevant to most users (although sometimes good to be aware of for more intermediate users, especially when it comes to understanding how it maps UNIX paths to Windows paths and vice-versa).

@Masacroso: It shouldn't usually take several months, but right now I'm the only one building the Windows installer releases and I had some setbacks in my ability to build the 9.1 release. Usually it should be out within a week or so of the source release

Try Plotting Fermat' s Spiral, which requires polar coordinates, r=2theta?

Find the root of Tan(x)?

You can find instructions for configuring PyCharm with sage here: https://ask.sagemath.org/question/397...

... I was able to run the interpreter. But I think there should be a better way. And it doesn't seem to work for commands like "Python: Start REPL". I need to reverse engineer how the Python extension searches for activate scripts, such as when it activates virtualenvs and conda envs, and see if the same mechanism can be used to load a sage-env. This issue also seems to be a problem: https://github.com/microsoft/vscode-p... It might be best for a Sage environment to change the default shell to the bash that comes with Sage, but I don't know how to do that yet. Still figuring out how to configure VSCode and some of it is very confusing...

I don't think that's really the problem. I was able to set up a workspace where I set "python.pythonPath" to the windows path to Sage's Python interpreter. To get the Windows path, from the Sage shell you can run cygpath -m -a $(which python3), which in my case returns C:/Users/Erik M. Bray/AppData/Local/SageMath 9.0/runtime/opt/sagemath-9.0/local/bin/python3.7.exe. Putting this in "python.pythonPath" almost works, except the additional trick is that at the very least you also need to have the $PATH environment variable set properly. I was able to do this by creating a sage.env file like echo "$(cygpath -p -m "$PATH")" > sage.env, and then in my workspace settings set "python.envFile" to the path to that sage.env. This partly works....

I'm not exactly sure what you mean here: "it's not able to detect Sage's Python executable because VSCode uses import sys; print(sys.executable) to get the actual path". In order to run some code in a specific Python interpreter, doesn't it need to already know the path to that Python interpreter in the first case? In what context does VSCode do this? I think I actually have VSCode installed but I never use it, or if not I'll go ahead and install it and see what I can find out...

Could you please post a piece of sample code which reproduces the problem for you? I can reproduce the problem with 8.9, but not with 9.0.

Hi, I'm not sure what you intended exactly by this answer but it appears to be misleading. Sage on Windows uses Cygwin. MinTTY is just a terminal emulator that is included in Cygwin, and is also the terminal emulator used by default when running Sage for Windows.

I forgot about this question, but just as a quick follow-up Jesus and I met last week at the University of Essex and I walked him through building Sage on Windows/Cygwin using the instructions at: https://trac.sagemath.org/wiki/Cygwin...

As we noted at the time, one bit of information currently missing from those instructions is to set:

export FFLAS_FFPACK_CONFIGURE=--disable-openmp

This is just to work around a slight defect in the build system that should get fixed at some point...

I tried it on 9.0 and it does appear to be fixed. Compiling the spyx module is a little slow--slower than it should be for some reason--but it works.

Have you tried 9.0? I believe this problem may be fixed in 9.0.

Where did you look? When you go to the download page and select a mirror and OS, each page lists old versions.

I need to download SageMath8.9 for a class, but online, the only version I can find for download is 9.0. Where can I download 8.9?

Thanks.

I need version 8.9 for a class, but I can only find links to download 9.0 online. Where can I find a download for 8.9?

Thanks.

Well done. Shame about the patch to tornado; I don't see another way around it until/unless it's fixed upstream.

One thing I'm a bit confused by: You seem to mention that VSCode comes with its own Python into which you can install Jupyter Notebook, and indeed you mention pip installing Jupyter. But then you say you're running the Jupyter Notebook that comes with Sage, so the previous copy of notebook is never actually used as far as I can tell...unless you're just using Sage Notebook to start the kernel?

It would be easier if you copied the sage/kernel.json to somewhere else (not modifying the Sage installation, which is a bit dangerous), and instead installed a copy of that kernel directly into the jupyter notebook you installed on your system kernel. Should work.

This is basically correct, and passing an arbitrary **kwargs to a subclass's constructor is a fairly common idiom. A couple (very minor) nitpicks where your code is non-idiomatic:

• Python has a style guide called PEP-8, which is also used by Sage (see Sage Coding Conventions. Most of your code is already PEP-8 except the self._edgePairs. camelCase is not used for local variables or attributes; instead you could call this self._edge_pairs (like I said, very minor)
• The line assert edge in self.edges() is unnecessary; if it isn't true the following line will raise a KeyError, which is more explicit than an AssertionError anyways.

astropy also has a very powerful units and quantities package which took much of its original inspiration from Pint. Actually, lately they've been converging more and more again on shared functionality (thanks in part to recent updates to Numpy making propagation of units easier)--I wonder if one day it will be possible for them to converge, rather than maintaining separate projects. Though astropy.units does have some more advanced functionality specific to the astronomy community (though also useful for most any science).