kekx's profile - activity

If anyone knows a better way that would allow me to continue working in the shared folder directly I'd be happy to hear about it!

Alright, so I have managed to pin down the problem and also found a workaround. I am getting this warning, because I am working in a shared folder of a virtual box linux. In order to enable the automatic sharing with the host machine, virtual box gives the ownership (and write permission) of these shared folders to a group called 'vboxsf', which in turn upsets sage. Since I cannot remove the write permission without messing with the functionality of the shared folders, I created a copy of the shared folders in my home directory and set up a cron job to sync the two periodically.

Alright, it turned out that the problem was/is actually related to this other problem that I am also having. In short, for security reasons sage is stripping os.sys.path of the first entry which is usually the empty string and tells python to look in the current directory.

Thanks! This was very helpful for figuring out the problem.

I have 'installed' sage following these instructions, by just extracting the latests binary tarball and then adding a symbolic link like so: ln -s ~/sage/sage /usr/local/bin/sage

Now every time I execute a file with sage path/to/file I get the following warning:

sys:1: RuntimeWarning: not adding directory '' to sys.path since it's writable by an untrusted group.
Untrusted users could put fi les in this directory which might then be imported by your Python code. As a general precaution from similar exploits, you should not execute Python code from this directory

Especially during debugging sessions the additional output tends to clutter up my screen a lot and pushes away the meaningful output. Is there any way I can fix this?

I have a project that is primarily written in python but uses sage for some specific operations. In order to facilitate this I have only .py files and use from sage.all import * at the top of all modules that make use of sage functionalities. To execute I always used sage -python path/to/file.py.

This approach worked fine until it became necessary to split my project into multiple sub-packages. I now want to execute my modules with python -m package.subpackage.module for modules that do not use sage (which works) and correspondingly sage -python -m package.subpackage.module for modules that do. Unfortunately the latter only returns an error message of the form ~/sage/local/bin/python: No module named package.subpackage

In order to be able to use package relative imports I am kind of dependent on the -m syntax, so I would like to get it to work. Any ideas what I am doing wrong? Or is this simply not possible with the python that is bundled with sage for internal reasons? Any help is apreciated!

I am trying to perform a polynomial modulus between elements in a QuotientRing, more or less like so:

sage: R = QuotientRing(ZZ[x], x**8+1)
sage: t = R.gen()
sage: g = 3*t^5 + 3*t^4 + 2*t^3 + 3*t^2 + t + 2
sage: a = -14*t^7 - t^6 + t^4 - 9*t^2 + 5*t + 1
sage: a.mod(g)
-14*xbar^7 - xbar^6 + xbar^4 - 9*xbar^2 + 5*xbar + 1

As you can see the modulus is not doing anything. I am not very well versed in this kind of maths, but I still believe that it should be possible to compute that modulus. Thus my question is, if it is possible to compute that modulus in sage, possibly via some kind of workaround.

I would be glad about any hints!