[sage-devel] Re: Error when installing from source code on Windows 11
I had very similar problems when trying to install the current development version on cygwin (the package python3-3.10.2 failed to build). I was able to fix this by manually specifying in the configuration that the system python3.8 should be used (python3.9 failed for separate reasons), but then I encountered a separate bug with building e_antic-0.1.9. I could post the corresponding log files, though I should say that I have since given up on making it run on cygwin. What I can recommend to the original poster is to set up sage locally on Windows using the Windows Subsystem for Linux, as described here: https://doc.sagemath.org/html/en/installation/source.html#ubuntu-on-windows-subsystem-for-linux-wsl-prerequisite-installation For me neither the BIOS modification nor the upgrade to Ubuntu 20.10 was necessary, and all steps were much faster than the steps I got to work on cygwin, too. After following the instructions above, I continued with the Ubuntu instructions on https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation followed by the instructions in https://github.com/sagemath/sage/#readme as recommended. Matthias Koeppe schrieb am Freitag, 25. März 2022 um 17:26:06 UTC+1: > Your screenshot contains the instructions what files to send with this > report. > > On Friday, March 25, 2022 at 8:15:13 AM UTC-7 bea...@gmail.com wrote: > >> Hello everyone, >> >> I am currently trying to install the latest version of sage locally on my >> laptop (Windows 11 OS) from the source code and encountered an error >> related to building a python package. I did the installation using cygwin. >> The error seems to be related to building python3-3.9.9. >> I attach hereby a screenshot of the cygwin command prompt. I would >> appreciate any help towards solving this issue. >> >> Best regards, >> Andry >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/41f3a6dc-4d79-4a35-be05-b76075be87ban%40googlegroups.com.
[sage-devel] Bug in __hash__ for PermutationGroupElement
Dear all,
the current implementation of __hash__ for PermutationGroupElement returns
a hash that not only depends on the given permutation, but also on the
group the permutation lives in.
Thus the "same" permutation (when compared with __eq__) may have different
hash values, which is not in line with the Python documentation (
https://docs.python.org/3.5/reference/datamodel.html#object.__hash__) and
leads to unexpected situations as the following.
sage: G = SymmetricGroup(2)
sage: H = SymmetricGroup(1)
sage: d = {G.one() : "FooBaa"}
sage: H.one() in list(d.keys())
True
sage: H.one() in d
False
Best,
Johannes Schwab
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/66a4796f-19da-42aa-b530-4f7f70402979n%40googlegroups.com.
[sage-devel] Re: recipe for target 'ecl-16.1.2.p4' fail
Actually, setting SAGE_GCC_INSTALL=yes didn't help. Also, installing the recommended rpms libffi libffi-devel-3.2.1.git259-11.1.x86_64 didn't help initially. However, in order to install the rpms, I had to remove libffi-devel-gcc5, which broke some dependencies. I also was supposed to install som libffi7. Which I did. Now I have installed: libffi-devel-3.2.1.git259-11.1.x86_64 libffi4-32bit-5.3.1+r233831-10.1.x86_64 libffi4-5.3.1+r233831-10.1.x86_64 and ecl compiles, miraculously! I'm not sure, whether this is of any help. I'm also not sure, what the consequences of this broken dependency will be. gcc5 doesn't show up in my rpm-list any longer. But at least for now I'm happy. Thanks a lot for your help, Johannes. Am Montag, 9. Oktober 2017 20:57:23 UTC+2 schrieb Johannes Martin: > > I tried to install sage-8.0 from source on opensuse linux 42.3 > following the standard procedure > configure > make > > Any help will be appreciated, > Johannes Martin. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] recipe for target 'ecl-16.1.2.p4' fail
There are no older versions offered for downgrade or newer versions for update. It is the regular version installed by the operating system. Am Montag, 9. Oktober 2017 22:14:17 UTC+2 schrieb François Bissey: > > Strange version number. Can you install something called just libffi > version 3.x? > > > On 10/10/2017, at 08:58, Johannes Martin <physik...@gmail.com > > wrote: > > > > libffi4 5.3.1+r233831-10.1 > > > > Am Montag, 9. Oktober 2017 21:09:54 UTC+2 schrieb François Bissey: > > What version of ffi (possibly libffi) is one the system? > > > > François > > > > > On 10/10/2017, at 07:57, Johannes Martin <physik...@gmail.com> wrote: > > > > > > I tried to install sage-8.0 from source on opensuse linux 42.3 > > > following the standard procedure > > > configure > > > make > > > > > > Any help will be appreciated, > > > Johannes Martin. > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "sage-devel" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-devel+...@googlegroups.com. > > > To post to this group, send email to sage-...@googlegroups.com. > > > Visit this group at https://groups.google.com/group/sage-devel. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-devel+...@googlegroups.com . > > To post to this group, send email to sage-...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] recipe for target 'ecl-16.1.2.p4' fail
libffi4 5.3.1+r233831-10.1 Am Montag, 9. Oktober 2017 21:09:54 UTC+2 schrieb François Bissey: > > What version of ffi (possibly libffi) is one the system? > > François > > > On 10/10/2017, at 07:57, Johannes Martin <physik...@gmail.com > > wrote: > > > > I tried to install sage-8.0 from source on opensuse linux 42.3 > > following the standard procedure > > configure > > make > > > > Any help will be appreciated, > > Johannes Martin. > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-devel+...@googlegroups.com . > > To post to this group, send email to sage-...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Bug in groebner_basis()?
Oh, thank you! Sometimes it's a good idea to have a look at the documentation of ALL used functions... Sorry for the trouble. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Bug in groebner_basis()?
Hello, I think I stumbled across a bug in groebner_basis(). The example below doesn't generate the unique reduced Groebner basis of the ideal generated by f and g, but instead the set [y^3 + 2*y^2 - x - y, x^2 + 2*y, x*y - y^2 + 1] is returned. This set isn't a Groebner basis at all. The correct basis should be [1 - 2*y^2 + 2*y^3 + y^4, x + y - 2*y^2 - y^3] . Here is the code: R.<x,y> = PolynomialRing(QQ, 'lex') f = x^2 + 2*y g = x*y - y^2 + 1 I = ideal([f,g]) print I.groebner_basis() I tested it with version 6.7, 8.0.rc1 and on sagecell.sagemath.org and with different algorithms as argument to groebner_basis(), the result is always the same. Is this a bug, or do I have some stupid error in my code? Regards, Johannes -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Error installing package ecl-15.3.7p0
Hi,
I cannot compile the source files of sage on
openSuse Leap 42
Linux linux-noh5 4.1.20-11-default #1 SMP PREEMPT Fri Mar 18 14:42:07 UTC
2016 (0a392b2) x86_
64 x86_64 x86_64 GNU/Linux
The corresponding log-file shows the following information
gcc -DECLDIR="\"/home/jmartin/Downloads/sage-7.1/local/lib/ecl-15.3.7\""
-I. -I/home/jmartin/
Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/build
-I/home/jmartin/Downloads/
sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c -I../ecl/gc
-DECL_API -DECL_NO_LEGAC
Y -I/home/jmartin/Downloads/sage-7.1/local/include
-I/home/jmartin/Downloads/sage-7.1/local
/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -Dlinux -c -o
ffi.o ffi.o.c
/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c/ffi.d:146:27
: error: 'FFI_SYSV' undeclared here (not in a function)
{@':cdecl', FFI_SYSV},
^
Makefile:81: recipe for target 'ffi.o' failed
make[5]: *** [ffi.o] Error 1
make[5]: Leaving directory
'/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
3.7p0/src/build/c'
Makefile:109: recipe for target 'libeclmin.a' failed
make[4]: *** [libeclmin.a] Error 2
make[4]: Leaving directory
'/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
3.7p0/src/build'
Makefile:70: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory
'/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
3.7p0/src'
Error - Failed to build ECL ... exiting
real0m22.295s
user0m17.176s
sys 0m1.792s
Error installing package ecl-15.3.7p0
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Pythonics
On 31.03.2016 23:08, Justin C. Walker wrote: Hi, all, I have couple of questions regarding "attributes" in Python/Sage: 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not blow up? this means X.foo is defined. 2. Is there a way to tell, when hasattr(X, "foo") returns True, whether "X.foo" can be called? X.foo and x.foo.__call__ is None 3. If "X.foo" is callable, is it expected that "X.foo()" will *not* blow up with "Not Implemented"? No. For example you can have class x(object): def foo(self): raise NotImplemented() x = new X() x.foo() # this will raise a not implemented exception. but x.foo is well defined. bg, Jo I'm hoping that makes sense... Thanks! Justin -- Justin C. Walker, Curmudgeon-At-Large, Director Institute for the Enhancement of the Director's Income The path of least resistance: it's not just for electricity any more. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: max(sin(x),cos(x)) = sin(x)
On 12.05.2015 09:28, Nathann Cohen wrote: Okay, so what do we do with this bug? 1) make Sage's default 'max' be 'max_symbolic' (yes/no) +1 imho the only reason not to do is performance, and it seems to be ok like pointed Nils pointed out. 2) Return Unknown instead of False in the __bool__ function od symbolic comparisons (yes/no) as pointed out by Jakob, an additional value will cause some trouble (which can be fixed) and some confusion for the enduser (which was one reason for this thread) Maybe a third option would be to raise an exception and somehow mention symbolic_min/symbolic_max. bg, Johannes Vincent: I am asking you especially, since you were initially opposed to it. I only want something (anything) to be done about it. Nathann On Saturday, May 9, 2015 at 7:11:42 PM UTC+2, Nils Bruin wrote: On Saturday, May 9, 2015 at 6:25:49 AM UTC-7, Volker Braun wrote: Arguably it should raise, though that is possibly only legal in Python 3 Where does the myth come from that comparison is not allowed to raise errors in python 2? Python 2.7.5 (default, Nov 3 2014, 14:33:39) [GCC 4.8.3 20140911 (Red Hat 4.8.3-7)] on linux2 Type help, copyright, credits or license for more information. complex(1,2)complex(3,4) TypeError: no ordering relation is defined for complex numbers -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com mailto:sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com mailto:sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Sage's changelog
On 13.05.2015 21:36, Harald Schilly wrote: I'm happy if there were a few more helping hands for the website. There are several technical and financial constraints (besides the time I'm spending with it), which might shed some light on the reasons why some things do happen. What kind of issues? And what kind of help? Maybe Ican spend some time on it too. bg, Johannes -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Products of permutations use nonstandard order of operation
Hi there, I'm new to sage-devel. So I apologize in advance if I say things that make no sense. The order of the product of two permutations in sage struck me as well, as many others, no doubt. As has been said, it does not really matter which order has been chosen, as soon as the other order is available as well. It appears to me that the opposite of a group, or more generally of a magma, is currently not implemented in sage. Wouldn't that be a nice feauture and a solution to the problem? SymmetricGroup(n).opposite() would then give the symmetric group in which (1,2) * (1,3) equals (1,3,2), whereas (1,2) * (1,3) = (1,2,3) in SymmetricGroup(n). Johan -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Sage 5.9 Fails to build in conway_polynomials
Hi List,
I tried to upgrade sage via sage -upgrade but it fails in
conway_polynomials.
For more Details see attachment.
On:
Linux neo 3.2.0-41-generic #65-Ubuntu SMP Wed Apr 10 18:23:37 UTC 2013
i686 i686 i386 GNU/Linux
Ubuntu 12.04
bg
Johannes
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Testing mirrors...
[15] sage.mirror.garr.it 140 [ms]
[8 ] mirror.switch.ch 162 [ms]
[4 ] ftp.sh.cvut.cz 174 [ms]
[19] www.mirrorservice.org187 [ms]
[17] sunsite.rediris.es 205 [ms]
[18] www-ftp.lip6.fr 209 [ms]
[10] mirror.yandex.ru 242 [ms]
[16] servingzone.com 252 [ms]
[12] mirrors.fe.up.pt 260 [ms]
[7 ] mirror.clibre.uqam.ca367 [ms]
[6 ] jambu.spms.ntu.edu.sg539 [ms]
[3 ] ftp.riken.jp 678 [ms]
[11] mirror.yongbok.net 803 [ms]
[2 ] ftp.kaist.ac.kr 818 [ms]
[9 ] mirror.unej.ac.id878 [ms]
[5 ] ftp.tsukuba.wide.ad.jp 1162 [ms]
[13] mirrors.tuna.tsinghua.edu.cn1411 [ms]
[14] sage.Igor.onlineDirect.bg 5175 [ms]
[1 ] boxen.math.washington.edu 5612 [ms]
Automatically selected server mirror.switch.ch
(http://mirror.switch.ch/mirror/sagemath/).
Downloading packages from 'http://mirror.switch.ch/mirror/sagemath//spkg'.
Reading package lists... Done!
The following packages will be upgraded:
extcode-5.9 r-2.15.2.p2 sagetex-2.3.4
** WARNING: This is a source-based upgrade, which could take hours,
** fail, and render your Sage install useless!!
Do you want to continue [y/N]?
http://mirror.switch.ch/mirror/sagemath//spkg/standard/extcode-5.9.spkg --
extcode-5.9.spkg 'extcode-5.9.spkg' is already present.
http://mirror.switch.ch/mirror/sagemath//spkg/standard/r-2.15.2.p2.spkg --
r-2.15.2.p2.spkg 'r-2.15.2.p2.spkg' is already present.
http://mirror.switch.ch/mirror/sagemath//spkg/standard/sagetex-2.3.4.spkg --
sagetex-2.3.4.spkg 'sagetex-2.3.4.spkg' is already present.
http://mirror.switch.ch/mirror/sagemath//spkg/standard/VERSION.txt --
VERSION.txt [.]
http://mirror.switch.ch/mirror/sagemath//spkg/install -- install [...]
http://mirror.switch.ch/mirror/sagemath//spkg/standard/deps -- deps
[...nothing changed
nothing changed
]
make base
env SAGE_BUILD_TOOLCHAIN=yes make toolchain
make toolchain-deps
make[1]: Betrete Verzeichnis '/usr/lib/sagemath/spkg'
make /usr/lib/sagemath/spkg/installed/zlib-1.2.6.p0
make /usr/lib/sagemath/spkg/installed/mpir-2.6.0.p2
make /usr/lib/sagemath/spkg/installed/mpfr-3.1.0.p2
make /usr/lib/sagemath/spkg/installed/mpc-1.0.p0
make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/spkg'
make all-sage
make[1]: Betrete Verzeichnis '/usr/lib/sagemath/spkg'
/usr/lib/sagemath/spkg/pipestatus sage-spkg ${SAGE_SPKG_OPTS}
conway_polynomials-0.4 21 tee -a
/usr/lib/sagemath/logs/pkgs/conway_polynomials-0.4.log
make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/spkg'
*** ALL ENVIRONMENT VARIABLES BEFORE BUILD: ***
AR=ar
AS=as
CCACHE_BASEDIR=/usr/lib/sagemath
CC=gcc
CHMOD=chmod
CPATH=/usr/lib/sagemath/local/include:/usr/include/i386-linux-gnu
CP=cp
CPP=cpp
CXXFLAGS=
CXX=g++
DISPLAY=:0.0
DOT_SAGE=/home/j_schn14/.sage/
ECLDIR=/usr/lib/sagemath/local/lib/ecl/
EDITOR=emacs
F77=gfortran
F90=gfortran
F95=gfortran
GP_DATA_DIR=/usr/lib/sagemath/local/share/pari
GPDOCDIR=/usr/lib/sagemath/local/share/pari/doc
GPHELP=/usr/lib/sagemath/local/bin/gphelp
HGENCODING=utf8
HGPLAIN=yes
HOME=/home/j_schn14
IPYTHONDIR=/home/j_schn14/.sage//ipython-0.12
LANG=de_DE@euro
LANGUAGE=de_DE:de:en_GB:en
LC_ALL=de_DE.UTF-8
LDFLAGS=
LD=ld
LD_LIBRARY_PATH=/usr/lib/sagemath/local/lib:/usr/lib/sagemath/local/lib/R/lib
LESSOPEN=| /usr/share/source-highlight/src-hilite-lesspipe.sh %s
LESS= -R
LIBRARY_PATH=/usr/lib/sagemath/local/lib:/usr/lib/i386-linux-gnu
LN=ln
LOGNAME=root
MAIL=/var/mail/root
MAKE=make
MAXIMA_PREFIX=/usr/lib/sagemath/local
MKDIR=mkdir
MPLCONFIGDIR=/home/j_schn14/.sage//matplotlib-1.1.0
MV=mv
PATH=/usr/lib/sagemath/spkg/bin:/usr/lib/sagemath/local/bin:/usr/lib/sagemath/spkg/bin:/usr/lib/sagemath/local/bin:/home/j_schn14/studium/ss11/infoPruefung/tanagra/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/android-sdk/tools:/opt/android-sdk/platform-tools/
PKG_CONFIG_PATH=/usr/lib/sagemath/local/lib/pkgconfig
PREREQ_OPTIONS=--disable-compiler-checks
PWD=/usr/lib/sagemath/spkg
PYTHONHOME=/usr/lib/sagemath/local
PYTHONPATH=/usr/lib/sagemath/local
RANLIB=ranlib
__sage__=
SAGE64=no
SAGE_BROWSER=firefox
Re: [sage-devel] Blocker tickets
Hi,
Tickt 14433 fails on my system:
sage:len(search_doc('tree', interact=False).splitlines()
3956
sage: version()
'Sage Version 5.8, Release Date: 2013-03-15'
bg,
Johannes
On 12.04.2013 16:01, Jeroen Demeyer wrote:
There are 2 blocker tickets remaining for Sage 5.9, both of them need
review:
#14371: Race condition in singular doctest
http://trac.sagemath.org/sage_trac/ticket/14371
#14426: Runaway/Segfaulting ECL processes
http://trac.sagemath.org/sage_trac/ticket/14426
There is already 1 blocker for Sage 5.10, which also needs review:
#14433: Increase number of matches to tree in sagedoc.py doctest
http://trac.sagemath.org/sage_trac/ticket/14433
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Signal handling
maybe another (untested) suggestion is, to start a sage instance in
background, separated from django and communicate over a network
protocol with each other.
this has the further advantage, that you can separate the web-server
from the sage installation for security of performance reasons.
bg,
Johannes
On 29.03.2013 08:02, Jeroen Demeyer wrote:
On 03/28/2013 11:44 PM, tom d wrote:
The problem seems to be at:
from sage.ext.c_lib import _init_csage, sig_on_count
_init_csage()
which is explicitly using the signal library and doing signal handling
stuff for Sage. Any idea how deep this goes? Some of the online
suggestions are about using some different libraries for signal
handling, which might be a bit more sensitive about whether Sage is the
main process or not.
You could completely disable the Sage signal handler, I guess the
following patch would do it (NOT TESTED!)
diff --git a/c_lib/src/stdsage.c b/c_lib/src/stdsage.c
--- a/c_lib/src/stdsage.c
+++ b/c_lib/src/stdsage.c
@@ -48,7 +48,6 @@
void init_csage() {
init_global_empty_tuple();
init_memory_functions();
-setup_sage_signal_handler();
setup_NTL_error_callback(global_NTL_error_callback, NULL);
}
diff --git a/sage/ext/c_lib.pyx b/sage/ext/c_lib.pyx
--- a/sage/ext/c_lib.pyx
+++ b/sage/ext/c_lib.pyx
@@ -37,8 +37,6 @@
# call its interrupt handler (which is the one we set now). This
# handler issues a sig_check() which finally raises the
# KeyboardInterrupt exception.
-import signal
-signal.signal(signal.SIGINT, sage_python_check_interrupt)
init_csage()
But seriously: why are you trying to run Django and Sage in the same
process? That seems like asking for trouble. Couldn't you run a Sage
subprocess?
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Python 3 formatting
some of those errors should be fixable by a little sed script like most
of the whitespace warnings and ''.
greatz Johannes
On 31.01.2013 12:17, Jeroen Demeyer wrote:
$ pep8 -qq --statistics sage
869 E111 indentation is not a multiple of four
189 E121 continuation line indentation is not a multiple of four
28 E122 continuation line missing indentation or outdented
66 E123 closing bracket does not match indentation of opening
bracket's line
33 E124 closing bracket does not match visual indentation
145 E125 continuation line does not distinguish itself from next
logical line
281 E126 continuation line over-indented for hanging indent
774 E127 continuation line over-indented for visual indent
1134E128 continuation line under-indented for visual indent
2942E201 whitespace after '['
2629E202 whitespace before ']'
1104E203 whitespace before ':'
45 E211 whitespace before '('
586 E221 multiple spaces before operator
657 E222 multiple spaces after operator
8741E225 missing whitespace around operator
23360 E231 missing whitespace after ','
5992E251 no spaces around keyword / parameter equals
1261E261 at least two spaces before inline comment
564 E262 inline comment should start with '# '
156 E271 multiple spaces after keyword
564 E272 multiple spaces before keyword
192 E301 expected 1 blank line, found 0
4050E302 expected 2 blank lines, found 1
2200E303 too many blank lines (3)
1 E304 blank lines found after function decorator
72 E401 multiple imports on one line
37135 E501 line too long (163 79 characters)
775 E502 the backslash is redundant between brackets
1078E701 multiple statements on one line (colon)
163 E702 multiple statements on one line (semicolon)
158 E703 statement ends with a semicolon
338 E711 comparison to None should be 'if cond is None:'
150 E712 comparison to True should be 'if cond is True:' or 'if cond:'
11 E721 do not compare types, use 'isinstance()'
10811 W291 trailing whitespace
3 W292 no newline at end of file
38415 W293 blank line contains whitespace
440 W391 blank line at end of file
322 W601 .has_key() is deprecated, use 'in'
3822W602 deprecated form of raising exception
33 W603 '' is deprecated, use '!='
8 W604 backticks are deprecated, use 'repr()'
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review
Hi,
I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a
test all?)
and a get a bunch of errors. Most of them coming from undefined
variables in the tests. I don't think that all these test are broken
(400+), because some of the errors look like the following one:
File
/usr/lib/sagemath/devel/sage-dev/sage/combinat/rigged_configurations/kleber_tree.py,
line 630:
sage: KT.plot()
Exception raised:
Traceback (most recent call last):
File /usr/lib/sagemath/local/bin/ncadoctest.py, line 1231, in
run_one_test
self.run_one_example(test, example, filename, compileflags)
File /usr/lib/sagemath/local/bin/sagedoctest.py, line 38, in
run_one_example
OrigDocTestRunner.run_one_example(self, test, example, filename,
compileflags)
File /usr/lib/sagemath/local/bin/ncadoctest.py, line 1172, in
run_one_example
compileflags, 1) in test.globs
File doctest __main__.example_18[4], line 1, in module
KT.plot()###line 630:
sage: KT.plot()
File
/usr/lib/sagemath/local/lib/python/site-packages/sage/combinat/rigged_configurations/kleber_tree.py,
line 633, in plot
return self.digraph().plot(edge_labels=True, vertex_size=0, **options)
File
/usr/lib/sagemath/local/lib/python/site-packages/sage/combinat/rigged_configurations/kleber_tree.py,
line 617, in digraph
if have_dot2tex():
File
/usr/lib/sagemath/local/lib/python/site-packages/sage/graphs/dot2tex_utils.py,
line 29, in have_dot2tex
return dot2tex.dot2tex(graph {}, format = positions) == {}
File
/usr/lib/sagemath/local/lib/python/site-packages/dot2tex/__init__.py, line
49, in dot2tex
return d2t.convert_graph(dotsource,**kwargs)
File
/usr/lib/sagemath/local/lib/python/site-packages/dot2tex/dot2tex.py, line
2966, in convert_graph
tex = main(True, dotsource,options)
File
/usr/lib/sagemath/local/lib/python/site-packages/dot2tex/dot2tex.py, line
2928, in main
s = conv.convert(dotdata)
File
/usr/lib/sagemath/local/lib/python/site-packages/dot2tex/dot2tex.py, line
774, in convert
sys.exit(1)
SystemExit: 1
attached the list of failed tests.
bg,
Johannes
On 12.01.2013 16:38, Jeroen Demeyer wrote:
Please review #13946, it does some misc cleanup of the signal handling
code without changing its functionality. It is mainly meant to provide
a more solid base for future enhancements to the signal code:
http://trac.sagemath.org/sage_trac/ticket/13946
Thanks,
Jeroen.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
sage -t -long src/sage/src/misc/benchmark.py # 2 doctests failed
sage -t -long src/sage/src/tests/benchmark.py # 1 doctests failed
sage -t -long src/sage/src/misc/functional.py # 1 doctests failed
sage -t -long src/sage/src/tests/book_stein_ent.py # 4 doctests failed
sage -t -long src/sage/src/databases/cremona.py # 57 doctests failed
sage -t -long src/sage/src/tests/cmdline.py # 2 doctests failed
sage -t -long src/sage/src/combinat/root_system/cartan_type.py # 6
doctests failed
sage -t -long src/sage/src/combinat/tutorial.py # 1 doctests failed
sage -t -long src/sage/src/combinat/posets/hasse_diagram.py # 3
doctests failed
sage -t -long src/sage/src/combinat/posets/linear_extensions.py # 10
doctests failed
sage -t -long src/sage/src/combinat/posets/posets.py # 13 doctests
failed
sage -t -long src/sage/src/combinat/crystals/spins.py # 64 doctests
failed
sage -t -long src/sage/src/combinat/crystals/crystals.py # 20 doctests
failed
sage -t -long src/sage/src/combinat/crystals/direct_sum.py # 40
doctests failed
sage -t -long src/sage/src/combinat/crystals/affine.py # 131 doctests
failed
sage -t -long src/sage/src/combinat/crystals/fast_crystals.py # 76
doctests failed
sage -t -long src/sage/src/combinat/crystals/littelmann_path.py # 3
doctests failed
sage -t -long src/sage/src/combinat/crystals/letters.py # 157 doctests
failed
sage -t -long src/sage/src/combinat/crystals/tensor_product.py # 210
doctests failed
sage -t -long src/sage/src/combinat/crystals/highest_weight_crystals.py
# 63 doctests failed
sage -t -long src/sage/src/combinat/crystals/kirillov_reshetikhin.py #
524 doctests failed
sage -t -long src/sage/src/combinat/crystals/alcove_path.py # 62
doctests failed
sage -t -long
src/sage/src/combinat/rigged_configurations/rigged_configuration_element.py # 2
doctests failed
sage -t -long src/sage/src/combinat/rigged_configurations/bijection.py
# 4
Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review
yea, I have and I never had problems with it. It's a big surprise for me, that so much tests failed, even because I never recognized any problems. bg, Johannes On 13.01.2013 12:44, Volker Braun wrote: On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote: I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a test all?) Yes, make ptest / make ptestlong and a get a bunch of errors. Most of them coming from undefined variables in the tests Do you have LaTeX installed? Some plot commands use it. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review
I think something with my installation is broken, I removed the patch and still get the same errors. I try to track down the reasons for this. bg, Johannes On 13.01.2013 19:49, Johannes wrote: yea, I have and I never had problems with it. It's a big surprise for me, that so much tests failed, even because I never recognized any problems. bg, Johannes On 13.01.2013 12:44, Volker Braun wrote: On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote: I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a test all?) Yes, make ptest / make ptestlong and a get a bunch of errors. Most of them coming from undefined variables in the tests Do you have LaTeX installed? Some plot commands use it. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Problems with Mercurial / importing new patches
Hi list, I cant import new patches to my sage installation without committing changes I've done to the code. But I don't want to commit them. What is the mistake I'm doing? my setup is the following: - created a new branch - imported to patches by hg_sage.import_patch() - added two new files - changed one file on my own. now I want to import to more patches, what am I doing wrong? bg, Johannes -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: Weird issue with matrix mutability
I agree, the best is to speed up matrices at all, instead of creating a dangerous hack, just to speed up 2x2 Matrices. Further I think it's natural to inherit (most) matrix classes from Matrix, so this should not be changed. bg, Johannes On 11.01.2013 21:47, Nils Bruin wrote: sage/matrix$ grep _mutability *.pxd matrix0.pxd:cdef sage.structure.mutability.Mutability _mutability matrix0.pxd:cdef check_mutability(self) matrix0.pxd:cdef check_bounds_and_mutability(self, Py_ssize_t i, Py_ssize_t j) matrix0.pxd:cdef check_row_bounds_and_mutability(self, Py_ssize_t r1, Py_ssize_t r2) matrix0.pxd:cdef check_column_bounds_and_mutability(self, Py_ssize_t c1, Py_ssize_t c2) so if you change that to cdef bint _mutability you probably only have to amend those 4 routines. Further attribute access: sage/matrix$ grep \\._mutability *.pyx | wc 20 691235 in matrix0.pyx these are just the lines in the functions above and the remaining 9 lines are in a handful of special matrix implementations and of the form if self._mutability._is_immutable: which aren't really adhering to protocol (accessing private attributes! twice!), but are easily rewritten (to faster code anyway!) I thinks it's entirely doable to just make _mutability a straight boolean flag. Does anyone have reasons why this is not a good idea? -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Weird issue with matrix mutability
hey list, If you look at the code, there is a function called _new_c() which is used in the multiplication algorithm. In there, the following line is called: x = Matrix_integer_2x2 Matrix_integer_2x2.__new__(Matrix_integer_2x2, self._parent, None, False, False) this returns a Matrix_integer_2x2, but is different from the one you get, if you call: Matrix_integer_2x2(M2Z,None,false,false) sage: from sage.matrix.matrix_integer_2x2 import Matrix_integer_2x2 as mi2x2 sage: M2Z = MatrixSpace(ZZ,2) sage: null = mi2x2(M2Z,None,false,false);null [0 0] [0 0] sage: some_other_null = mi2x2.__new__(mi2x2, M2Z , None, False, False);some_other_null [] sage: some_other_null.set_immutable() --- AttributeError Traceback (most recent call last): [..] AttributeError: 'NoneType' object has no attribute 'set_immutable' even, if in _new_c the number of cols and rows is set, I think there is some internal object, which still has no value greatz Johannes On 10.01.2013 10:10, David Loeffler wrote: The following curious bug came up during work on ticket #12233. For some reason, if one creates a 2x2 integer matrix directly using the constructor then it is possible to tell it to be immutable; but if one creates one via arithmetic operations then calling set_immutable on it fails. Here's an example: sage: from sage.matrix.matrix_integer_2x2 import Matrix_integer_2x2 as mi2x2 sage: M2Z = MatrixSpace(ZZ,2) sage: mi2x2(M2Z, [1,0,0,1]) sage: x=mi2x2(M2Z, [1,0,0,1], false, false) sage: y=mi2x2(M2Z, [1,0,0,1], false, false) sage: type(x) type 'sage.matrix.matrix_integer_2x2.Matrix_integer_2x2' sage: z = x*y sage: type(z) type 'sage.matrix.matrix_integer_2x2.Matrix_integer_2x2' sage: x.set_immutable()# ok sage: z.set_immutable()# error [...] AttributeError: 'NoneType' object has no attribute 'set_immutable' (Many thanks to Timo Kluck for clarifying the problem and finding this example.) Does anyone have any idea what's going on here, and if so how to fix it? Regards, David -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: Weird issue with matrix mutability
But in the _copy_() method _mutability is set to a value. Even if I think this should be done in _new_c(). By the way, this bug also appears for x + y and x - y. greatz Johannes On 10.01.2013 23:34, Nils Bruin wrote: On Jan 10, 12:55 pm, Johannes dajo.m...@web.de wrote: hey list, If you look at the code, there is a function called _new_c() which is used in the multiplication algorithm. See http://trac.sagemath.org/sage_trac/ticket/8294 Looks like a little more is broken than just __copy__. Normally, _mutability gets set in matrix0's Matrix.__init__. Matrix_integer_dense gets that by explicitly calling a superclass __init__ in its __cinit__. I guess 2x2 tries to avoid that for efficiency reasons, but it suggests that its __cinit__ (or at least its _new_c) should then set the _mutability attribute. Is this class intentionally producing maimed instances for efficiency reasons perhaps? -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: Weird issue with matrix mutability
I think it would be enough to move the _mutability = Mutability(False) statement from the _copy_() method to the _new_c() method. On 11.01.2013 00:20, Johannes wrote: But in the _copy_() method _mutability is set to a value. Even if I think this should be done in _new_c(). By the way, this bug also appears for x + y and x - y. greatz Johannes On 10.01.2013 23:34, Nils Bruin wrote: On Jan 10, 12:55 pm, Johannes dajo.m...@web.de wrote: hey list, If you look at the code, there is a function called _new_c() which is used in the multiplication algorithm. See http://trac.sagemath.org/sage_trac/ticket/8294 Looks like a little more is broken than just __copy__. Normally, _mutability gets set in matrix0's Matrix.__init__. Matrix_integer_dense gets that by explicitly calling a superclass __init__ in its __cinit__. I guess 2x2 tries to avoid that for efficiency reasons, but it suggests that its __cinit__ (or at least its _new_c) should then set the _mutability attribute. Is this class intentionally producing maimed instances for efficiency reasons perhaps? -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-combinat-devel] Inconsistent behavior of LatticePolytopes and Polyhedrons
Hi List, I recognized some differences between polyhedron and lattice polytopes. let p be a polyhedron, and l a lattice polytop. then: first one: p.vertices() gives a list of lists, i.e. a list of vertices l.vertices() gives a matrix, where the columns define the vertices. second: let l be given, then p = Polyhedron(l.vertices().columns()) p.lattice_polytope() == l evaluates to false because the order of the vertices in p.lattice_polytope() is different then the one of the vertices in l third: for lattice polytopes we have nvertices, npoints and nfacets but for polyhedrons we have n_facets, n_vertices and more, which are not needed for lattice polytopes: n_rays, n_Hrepresentation, n_Vrepresentation, n_equations, n_inequalities, n_lines greatz Johannes -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-devel] High level architectural design document of Sage
Something like the information provided at http://www.sagemath.org/doc/thematic_tutorials/tutorial-objects-and-classes.html#sage-specifics-about-classes would be nice to have for an mathematical object in general. A good start would be the blog post at sagemath.blogspot.com from William, explaining the coercion model: http://sagemath.blogspot.de/2010/11/brief-history-and-motivation-behind.html I think it is the wrong way, that somebody who wants to start coding for sage must have to look at the source code to get a to learn something about the design and structure of sage. greatz Johannes On 04.12.2012 05:18, Michael Orlitzky wrote: On 12/03/2012 04:45 PM, William Stein wrote: Yes, it was kind of frustrating. Basically, David advertised it a lot, but at the end of the day, basically few people were available to come to a Sage Days on improving the documentation, even with all expenses paid... If anybody reading this has any experience with how to dramatically improve reference documentation of a big open source software project, please share. One difficulty with Sage is that there is probably no human alive who can really understand all of what Sage does, due to how many areas of advanced mathematics Sage touches, so whatever we do simply can't be a one-person project. In this regard, the scope of Magma is actually much smaller than that of Sage, since, e.g., Magma includes nothing in symbolic calculus and almost nothing in numerical analysis, which are two massive areas. Somebody asserted above that the Sage reference manual is supposed to cover all the functionality of Sage. However, this is not what it does, and I'm not sure it should. The reference manual covers most of the functionality of the core Sage library, which -- depending on your perspective -- may or may not be a big part of what Sage does (for you). For example, an undergrad recently asked me how to find out about what Sage can do in signal processing, and I definitely didn't suggest that he read the Sage reference manual; instead, I suggested the scipy website. Another example: Cython is a big part of Sage, but it isn't documented in the reference manual. The existing thematic tutorials sort-of address this problem: http://www.sagemath.org/doc/thematic_tutorials/ but there are far too few of them. I would suggest creating a magma-like hierarchy of thematic tutorials, one for each branch that Sage supports. The tutorials could link to individual pages of the reference manual, and should go through most common tasks that people might want to do. It should also have brief translations for users of other CAS software. See Rosetta Code http://rosettacode.org/ for an example of this done well. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Ubuntu 12.04: Sage fails to install from PPA - Error installing package gap_packages-4.4.12.p
Hi Am Mo 19 Nov 2012 04:47:19 CET schrieb Jan Groenewald: dpkg-reconfigure sagemath-optional that does not work: /usr/sbin/dpkg-reconfigure: sagemath-optional ist kaputt oder nicht komplett installiert (package is defect or not completely installed) if I try dpkg-reconfigure --force sagemath-optional I get get exactly the same error as before. greatz Johannes Until you do this your package manager will stay in a broken state. When you run dpkg -l sagemath-optional, it should also say ii next to it, once you are finished. Regards, Jan On 18 November 2012 21:42, Johannes dajo.m...@web.de mailto:dajo.m...@web.de wrote: Hey, On 18.11.2012 20:23, Jan Groenewald wrote: Dear Johannes, How did you install? From the PPA? Is this the sagemath-optional trying to build? I once installed Sage by `apt-get install sagemath-optional sagemath-upstream-binary` Johannes, please list the installed PPA packages: dpkg -l |grep sagemath dpkg -l |grep sagemath iF sagemath-optional 5.4 ii sagemath-upstream-binary5.4ubuntu1 sudo apt-get update sudo apt-get dist-upgrade sudo sage -f /usr/lib/sagemath/spkg/optional/gap_packages-4.4.12.p1.spkg Installing the package by `sage -f ..` as above seems to work fine. greatz Johannes Regards, Jan On 18 November 2012 21:04, Johannes dajo.m...@web.de mailto:dajo.m...@web.de mailto:dajo.m...@web.de mailto:dajo.m...@web.de wrote: Hi list, I tried to upgrade my sage installation, but it fails to build: make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/nauty22' gcc -c -O4 -march=i686 -DBIGNAUTY -o naututilB.o naututil.c gcc -c -O4 -march=i686 -DBIGNAUTY -o nautyB.o nauty.c gcc -c -O4 -march=i686 -DBIGNAUTY -o nautilB.o nautil.c gcc -c -O4 -march=i686 -DBIGNAUTY -o nautinvB.o nautinv.c gcc -c -O4 -march=i686 -DBIGNAUTY -o naugraphB.o naugraph.c gcc -c -O4 -march=i686 rng.c gcc -o dreadnautB -O4 -march=i686 -DBIGNAUTY dreadnaut.c naututilB.o \ nautyB.o nautilB.o nautinvB.o naugraphB.o rng.o make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/nauty22' ( cd src; make BINDIR= ) make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/src' gcc -O -o ../bin//drcanon4 drcanon4.c gcc -O -o ../bin//drtogap4 drtogap4.c gcc -O -o ../bin//gap4todr gap4todr.c make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/src' cat: ../..//sysinfo.gap: Datei oder Verzeichnis nicht gefunden ( test -d bin || mkdir bin; \ test -d bin/ || mkdir bin/; cd bin/; \ make -f ../../Makefile all2 CC=gcc CFLAGS=-O2; \ cd ../../src/leon/src/../; ./configure; make; mkdir ../../bin/leon; \ cp cent ../../bin/leon; cp cjrndper ../../bin/leon; \ cp commut ../../bin/leon; cp compgrp ../../bin/leon; \ cp desauto ../../bin/leon; cp fndelt ../../bin/leon; \ cp generate ../../bin/leon; cp inter ../../bin/leon; \ cp orbdes ../../bin/leon; cp orblist ../../bin/leon; \ cp randobj ../../bin/leon; cp setstab ../../bin/leon; \ cp wtdist ../../bin/leon; cp src/*.sh ../../bin/leon; \ cp wtdist ../../bin; cp desauto ../../bin; \ cp wtdist ../../bin/; cp desauto ../../bin/ \ ) make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' make[1]: ../../Makefile: Datei oder Verzeichnis nicht gefunden make[1]: *** Keine Regel, um »../../Makefile« zu erstellen. Schluss. make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' /bin/sh: 4: cd: can't cd to ../../src/leon/src/../ /bin/sh: 4: ./configure: not found make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' make[1]: *** Keine Targets angegeben und keine »make«-Steuerdatei gefunden. Schluss. make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' mkdir: kann Verzeichnis »../../bin/leon“ nicht anlegen: Datei oder Verzeichnis nicht gefunden my setup: Ubuntu 12.04 Linux neo 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:17:36 UTC 2012 i686 i686 i386 GNU/Linux if you need any more information, just ask, and I'll tell you. greatz and thnx, Johannes -- You received this message because you
Re: [sage-devel] Sage testing
Hey Jernej, take a look here: http://www.sagemath.org/doc/developer/walk_through.html#reviewing-a-patch greatz Johannes On 21.11.2012 17:20, Jernej Azarija wrote: Hello! I was wondering how is testing of Sage currently performed. What I was wondering is if there is a policy that for every new addition to sage there is also a suitable test case that is prepared to test the specific addition. For example if I add the function foo() to the graph class is there a test file or something in which I can add some test cases to test if the return value of foo() is as expected? I believe it would be nice to have a test script for each part of sage (for example Graphs) such that it would test all functions and methods of the given part. In this way one could always keep track if some local change in a library/sage broke a specific functionality of sage and it would also allow us to time if a global change in sage made any speed improvements to the running time of the tests. As far as I've noticed there is a policy to add the respective documentation for each addition to sage but no policy related to such tests. Am I correct? Is there any reason why this is not encouraged? Best, Jernej -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Ubuntu 12.04: Sage fails to install from PPA - Error installing package gap_packages-4.4.12.p
Hey, On 18.11.2012 20:23, Jan Groenewald wrote: Dear Johannes, How did you install? From the PPA? Is this the sagemath-optional trying to build? I once installed Sage by `apt-get install sagemath-optional sagemath-upstream-binary` Johannes, please list the installed PPA packages: dpkg -l |grep sagemath dpkg -l |grep sagemath iF sagemath-optional 5.4 ii sagemath-upstream-binary5.4ubuntu1 sudo apt-get update sudo apt-get dist-upgrade sudo sage -f /usr/lib/sagemath/spkg/optional/gap_packages-4.4.12.p1.spkg Installing the package by `sage -f ..` as above seems to work fine. greatz Johannes Regards, Jan On 18 November 2012 21:04, Johannes dajo.m...@web.de mailto:dajo.m...@web.de wrote: Hi list, I tried to upgrade my sage installation, but it fails to build: make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/nauty22' gcc -c -O4 -march=i686 -DBIGNAUTY -o naututilB.o naututil.c gcc -c -O4 -march=i686 -DBIGNAUTY -o nautyB.o nauty.c gcc -c -O4 -march=i686 -DBIGNAUTY -o nautilB.o nautil.c gcc -c -O4 -march=i686 -DBIGNAUTY -o nautinvB.o nautinv.c gcc -c -O4 -march=i686 -DBIGNAUTY -o naugraphB.o naugraph.c gcc -c -O4 -march=i686 rng.c gcc -o dreadnautB -O4 -march=i686 -DBIGNAUTY dreadnaut.c naututilB.o \ nautyB.o nautilB.o nautinvB.o naugraphB.o rng.o make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/nauty22' ( cd src; make BINDIR= ) make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/src' gcc -O -o ../bin//drcanon4 drcanon4.c gcc -O -o ../bin//drtogap4 drtogap4.c gcc -O -o ../bin//gap4todr gap4todr.c make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/grape/src' cat: ../..//sysinfo.gap: Datei oder Verzeichnis nicht gefunden ( test -d bin || mkdir bin; \ test -d bin/ || mkdir bin/; cd bin/; \ make -f ../../Makefile all2 CC=gcc CFLAGS=-O2; \ cd ../../src/leon/src/../; ./configure; make; mkdir ../../bin/leon; \ cp cent ../../bin/leon; cp cjrndper ../../bin/leon; \ cp commut ../../bin/leon; cp compgrp ../../bin/leon; \ cp desauto ../../bin/leon; cp fndelt ../../bin/leon; \ cp generate ../../bin/leon; cp inter ../../bin/leon; \ cp orbdes ../../bin/leon; cp orblist ../../bin/leon; \ cp randobj ../../bin/leon; cp setstab ../../bin/leon; \ cp wtdist ../../bin/leon; cp src/*.sh ../../bin/leon; \ cp wtdist ../../bin; cp desauto ../../bin; \ cp wtdist ../../bin/; cp desauto ../../bin/ \ ) make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' make[1]: ../../Makefile: Datei oder Verzeichnis nicht gefunden make[1]: *** Keine Regel, um »../../Makefile« zu erstellen. Schluss. make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' /bin/sh: 4: cd: can't cd to ../../src/leon/src/../ /bin/sh: 4: ./configure: not found make[1]: Betrete Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' make[1]: *** Keine Targets angegeben und keine »make«-Steuerdatei gefunden. Schluss. make[1]: Verlasse Verzeichnis '/usr/lib/sagemath/local/lib/pkg/guava/bin' mkdir: kann Verzeichnis »../../bin/leon“ nicht anlegen: Datei oder Verzeichnis nicht gefunden my setup: Ubuntu 12.04 Linux neo 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:17:36 UTC 2012 i686 i686 i386 GNU/Linux if you need any more information, just ask, and I'll tell you. greatz and thnx, Johannes -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com mailto:sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com mailto:sage-devel%2bunsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za http://www.aims.ac.za ^^-^^ -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] bug in groups.prod?
/site-packages/sage/structure/sage_object.so in sage.structure.sage_object.SageObject._gap_ (sage/structure/sage_object.c:3909)() /opt/sage-4.6/local/lib/python2.6/site-packages/sage/structure/sage_object.so in sage.structure.sage_object.SageObject._interface_ (sage/structure/sage_object.c:3554)() /opt/sage-4.6/local/lib/python2.6/site-packages/sage/interfaces/expect.pyc in __call__(self, x, name) 1097 1098 if isinstance(x, basestring): - 1099 return cls(self, x, name=name) 1100 try: 1101 return self._coerce_from_special_method(x) /opt/sage-4.6/local/lib/python2.6/site-packages/sage/interfaces/expect.pyc in __init__(self, parent, value, is_name, name) 1524 except (TypeError, KeyboardInterrupt, RuntimeError, ValueError), x: 1525 self._session_number = -1 - 1526 raise TypeError, x 1527 self._session_number = parent._session_number 1528 TypeError: Gap produced error output Variable: 'Complex' must have a value Syntax error: ; expected $sage8:=Complex Field with 53 bits of precision;; ^ Variable: 'with' must have a value Variable: 'bits' must have a value Variable: 'precision' must have a value executing $sage8:=Complex Field with 53 bits of precision;; greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] bug in groups.prod?
I got my error, i mixed prod and cartesian_product.
Am 14.08.2011 16:50, schrieb Johannes:
Hi list,
i tried to compute the product of two matrix groups and run in a gap
parsing error.
Miniexample:
g1 = MatrixGroup([Matrix(CC,[[1, 0, 0, 0], [0, 1, 0, 0], [0, 0, -1, 0],
[0, 0, 0, 1]])])
g2 = MatrixGroup([Matrix(CC,[[1, 0, 0, 0], [0, 1, 0, 0], [0, 0, 1, 0],
[0, 0, 0, I]])])
g1.prod(g2)
this leads to the following output:
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (146, 0))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (396, 0))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (29, 0))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (5, 0))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (29, 0))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (5, 0))
---
TypeError Traceback (most recent call last)
/home/j_schn14/studium/diplarbeit/tex/ipython console in module()
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/categories/monoids.pyc
in prod(self, args)
145 'ab'
146
-- 147 return prod(args, self.one())
148
149 def _test_prod(self, **options):
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/misc/cachefunc.pyc
in __call__(self, *args, **kwds)
553 return self.cache[k]
554 except KeyError:
-- 555 w =
self._cachedmethod._instance_call(self._instance, *args, **kwds)
556 self.cache[k] = w
557 return w
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/misc/cachefunc.pyc
in _instance_call(self, inst, *args, **kwds)
776
777
-- 778 return self._cachedfunc.f(inst, *args, **kwds)
779
780 def _get_instance_cache(self, inst):
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/categories/monoids.pyc
in one(self)
81 ''
82
--- 83 return self(1)
84
85 def one_element(self):
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/groups/matrix_gps/matrix_group.pyc
in __call__(self, x)
249 M = self.matrix_space()(x)
250 g = self.element_class(M, self)
-- 251 if not gap(g) in gap(self):
252 raise TypeError, no way to coerce element to self.
253 return g
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/interfaces/expect.pyc
in __call__(self, x, name)
1099 return cls(self, x, name=name)
1100 try:
- 1101 return self._coerce_from_special_method(x)
1102 except TypeError:
1103 raise
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/interfaces/expect.pyc
in _coerce_from_special_method(self, x)
1123 s = '_gp_'
1124 try:
- 1125 return (x.__getattribute__(s))(self)
1126 except AttributeError:
1127 return self(x._interface_init_())
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/structure/sage_object.so
in sage.structure.sage_object.SageObject._gap_
(sage/structure/sage_object.c:3909)()
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/structure/sage_object.so
in sage.structure.sage_object.SageObject._interface_
(sage/structure/sage_object.c:3428)()
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/groups/matrix_gps/matrix_group_element.py
in _gap_init_(self)
166 true
167
-- 168 return self.__mat._gap_init_()
169
170 def _gap_latex_(self):
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/matrix/matrix1.so
in sage.matrix.matrix1.Matrix._gap_init_ (sage/matrix/matrix1.c:2277)()
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/interfaces/expect.pyc
in __call__(self, x, name)
1099 return cls(self, x, name=name)
1100 try:
- 1101 return self._coerce_from_special_method(x)
1102 except TypeError:
1103 raise
/opt/sage-4.6/local/lib/python2.6/site-packages/sage/interfaces/expect.pyc
in _coerce_from_special_method(self, x)
1123
Re: [sage-devel] Shall / can we reduce the number of Sage related Google groups?
Am 03.08.2011 16:13, schrieb Simon King: Having a combined list for sage-nt, sage-algebra and sage-combinat- devel would (according to figures from the past 6 months) result in a list with little more than 7 posts per day. That should be small enough so that all people interested in abstract nonsense could easily follow - actually more easily than with three lists. In particular when interested people are only subscribed to two of them. +1 III. Moving sage-solaris, sage-flame, sage-marketing and sage-edu to sage- devel would yield an increment of (in average) less than one post per day on sage-devel. I believe nobody can reasonably say that such a little increment is a flood with tons of technical details. A single additional post per day could easily be filtered manually (i.e., ignored), if necessary. -1 I don't see a common ground for sage-develop and sage-maketing. Looks like list should get mixed just to reduce the number of lists. IV. sage-marketing and sage-edu concern topics which are perhaps not in the centre of everybody's research interests. However, most are at a university and could occasionally contribute to sage-edu, and I guess that most people would at least have an opinion on marketing and could occasionally contribute to sage-marketing (ok, that could be painting a bike shed). Hence, why hiding these two topics from a larger audience, putting them into a small list? V. sage-windows discusses a topic that is said to be a major goal of Sage. Hence, why not underlining its importance? Why not raising alertness by exposing it to the big audience? maybe it would be a better idea to create a new list like sage-porting where all discussions about ports to diferent OSs take place. greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: building sage took more then 24h now
i stopped it after 3 days. took to long just for some experiments. greatz Am 22.11.2010 15:48, schrieb RegB: I have a similarly modest system and my experience with UBUNTU 10.10 has been that the standard set of packages takes about 8 hours, maybe 6 1/2 of build and 1 1/2 of testing and document building. Anecdotal ? Yes, but 24h + to build some unknown package(s) is no surprise to me (-: You could monitor the log(s) as this build progresses. You MIGHT see some re-curing error that is causing numerous re-tries, etc. Same comment on the scripts, they may retry without limit on (partial)failure. It might be worth editing to limit the re-tries, example Atlas gives up after 5. Disclaimer; I am a newbie, regard my input as NOT advice (-: On Nov 16, 3:21 am, Johannes dajo.m...@web.de wrote: hi list, On Sunday started to install all experimental packages by sage -experimental | grep --color -vE 'INSTALLED|NOT|Type' | xargs sage -i and it's still building. Is this normal, or did i run into a endless loop? my configuration: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz 2GB Ram Linux neo 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Severe slowness of singular interface on some machines partially caused by _synchronize
24618 1290349603.215559 write(3, aaa, 3) = 3 24619 1290349603.219923 ... read resumed aaa, 256) = 3 in the first case: Wall time: 16.0200681686 Total CPU: 0.862045 in the second one: Wall time: 0.0230610370636 Total CPU: 0.042001 in the third one: Wall time: 8.00897812843 Total CPU: 0.300014 and my config: Linux neo 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 i686 GNU/Linux j_sch...@neo:~$ sage -version | Sage Version 4.6, Release Date: 2010-10-30 hope this helps. greatz Johannes Am 19.11.2010 15:12, schrieb Willem Jan Palenstijn: On Thu, Nov 18, 2010 at 11:47:38PM -0800, Simon King wrote: On 19 Nov., 07:28, Simon King simon.k...@uni-jena.de wrote: So, now the question is what all the machines have in common. I notice that it is Ubuntu in many (or all?) cases. One of the machines at my university used to *not* show the big overhead when it was running Scientific Linux. Now it is (if I understood correctly what the sysadminn said) Ubuntu. Small correction: One of the problematic machines runs Debian 6.0, not Ubuntu. But according to our sysadmin, Ubuntu is based on Debian, so that one might conjecture that the problem occurs on machines that in some way are based on Debian. Could you try to download, compile and run a small test program on a problematic machine? It times how fast a pseudo-terminal responds, which might be the problem judging by a few quick tests I ran. wget http://www.usecode.org/misc/timeptmx.c gcc -o timeptmx timeptmx.c strace -o timeptmx.log -f -ttt ./timeptmx grep aaa timeptmx.log That should output something like this: 16095 1290175675.065705 write(3, aaa, 3) = 3 16096 1290175675.065749 ... read resumed aaa, 256) = 3 The difference between these two timestamps seems to determine how fast pexpect responds. In this case it's fast (1290175675.065705 to 1290175675.065749 is only 44 microseconds), but I've seen 1.8ms on other machines with newer kernels. Something similar to this is run twice for every singular.eval() call, and seems to be the major factor in execution (wall) time. -Willem Jan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] building sage took more then 24h now
hi list, On Sunday started to install all experimental packages by sage -experimental | grep --color -vE 'INSTALLED|NOT|Type' | xargs sage -i and it's still building. Is this normal, or did i run into a endless loop? my configuration: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz 2GB Ram Linux neo 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Error building sage 4.6 on ubuntu 10.04
those hints helped me: http://ask.sagemath.org/question/107/building-atlas greatz Am 17.11.2010 00:42, schrieb Johannes: Hi list, today I tried to build the newset sage Version on my system from the sources and it fails. this seems to be the imporant part of the install log for me: gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/sage-4.6/local/include/python2.6 -c C/base.c -o build/temp.linux-i686-2.6/C/base.o gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/sage-4.6/local/include/python2.6 -c C/dense.c -o build/temp.linux-i686-2.6/C/dense.o gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/tmp/sage-4.6/local/include/python2.6 -c C/sparse.c -o build/temp.linux-i686-2.6/C/sparse.o In file included from /usr/include/string.h:640, from /tmp/sage-4.6/local/include/python2.6/Python.h:38, from C/sparse.c:22: In function ‘strncat’, inlined from ‘spmatrix_str’ at C/sparse.c:2473: /usr/include/bits/string3.h:154: warning: call to __builtin___strncat_chk might overflow destination buffer In function ‘strncat’, inlined from ‘spmatrix_str’ at C/sparse.c:2479: /usr/include/bits/string3.h:154: warning: call to __builtin___strncat_chk might overflow destination busffer gcc -pthread -shared build/temp.linux-i686-2.6/C/base.o build/temp.linux-i686-2.6/C/dense.o build/temp.linux-i686-2.6/C/sparse.o -L/tmp/sage-4.6/local/lib -L/tmp/sage-4.6/local/lib -lm -llapack -lcblas -lf77blas -latlas -lgfortran -lpython2.6 -o build/lib.linux-i686-2.6/cvxopt/base.so /usr/bin/ld: cannot find -lcblas collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 my system: Linux neo 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux Using Ubuntu 10.04. greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Error building sage 4.6 on ubuntu 10.04
No, building ATLAS failed. Am 17.11.2010 04:16, schrieb François Bissey: those hints helped me: http://ask.sagemath.org/question/107/building-atlas Was the issue that ATLAS had not finished building yet? Francois -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] bug in show/latex?
hi list
I have this simple code:
latex(matrix([[-(a + 1)/b]]))
and i get:
\left(\begin{array}{r}
\frac{-a + 1}{b}
\end{array}\right)
but it should be
\left(\begin{array}{r}
\frac{-a - 1}{b}
\end{array}\right)
or
\left(\begin{array}{r}
\frac{-(a + 1)}{b}
\end{array}\right)
greatz Johannes
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
Re: [sage-devel] Re: sage crashes on calculating roots of a polynom
that's the only test wich fails:
The following tests failed:
sage -t devel/sage/sage/graphs/schnyder.py
I dont think that there is any connection to my problem.
greatz Johannes
Am 07.10.2010 20:06, schrieb mhampton:
Those commands work for me on linux (ubuntu 9.10, intel i7 860) and OS
X 10.6. Maybe you could run all the standard tests for sage (sage -t
$SAGE_ROOT/devel/sage/sage), that might help narrow the problem down.
-M. Hampton
On 7 Okt., 17:31, Johannes dajo.m...@web.de wrote:
Hi list,
i got my sage crashed once again:
sage: a,b,c= var('a,b,c')
sage: mprime = matrix([[01,b+1,2],[a+1,2,1],[2,1,c+1]])
sage: cp = mprime.charpoly()
sage: cp.real_roots()
*** glibc detected *** python: free(): invalid pointer: 0x00541bfc ***
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
[sage-devel] sage crashes on calculating roots of a polynom
.1.0(PyEval_EvalFrameEx+0x4370)[0x1fb130] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x59e1)[0x1fc7a1] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x1fcfa1] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x1fb130] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x1fcfa1] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x1fb130] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x1fcfa1] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x1fb130] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x1fcfa1] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCode+0x63)[0x1fd0c3] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyRun_FileExFlags+0xb1)[0x21cf91] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyRun_SimpleFileExFlags+0xdc)[0x21d1cc] /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(Py_Main+0xc3b)[0x229c0b] /opt/sage-4.5.1/local/bin/python(main+0x27)[0x80486577] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x2f8bd6] /opt/sage-4.5.1/local/bin/python[0x8048591] === Memory map: 0011-0012b000 r-xp 08:05 580890 /lib/ld-2.11.1.so 0012b000-0012c000 r--p 0001a000 08:05 580890 /lib/ld-2.11.1.so 0012c000-0012d000 rw-p 0001b000 08:05 580890 /lib/ld-2.11.1.so 0012d000-0012e000 r-xp 00:00 0 [vdso] 0012e000-00265000 r-xp 08:05 948912 /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0 00265000-00266000 r--p 00136000 08:05 948912 /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0 00266000-00292000 rw-p 00137000 08:05 948912 /opt/sage-4.5.1/local/lib/libpython2.6.so.1.0 00292000-0029b000 rw-p 00:00 0 0029b000-002b r-xp 08:05 1659854 /lib/tls/i686/cmov/libpthread-2.11.1.so 002b-002b1000 r--p 00014000 08:05 1659854 /lib/tls/i686/cmov/libpthread-2.11.1.so 002b1000-002b2000 rw-p 00015000 08:05 1659854 /lib/tls/i686/cmov/libpthread-2.11.1.so 002b2000-002b4000 rw-p 00:00 0 002b4000-002b6000 r-xp 08:05 1659843 /lib/tls/i686/cmov/libdl-2.11.1.so 002b6000-002b7000 r--p 1000 08:05 1659843 /lib/tls/i686/cmov/libdl-2.11.1.so 002b7000-002b8000 rw-p 2000 08:05 1659843 /lib/tls/i686/cmov/libdl-2.11.1.so 002b8000-002ba000 r-xp 08:05 1659859 /lib/tls/i686/cmov/libutil-2.11.1.so 002ba000-002bb000 r--p 1000 08:05 1659859 /lib/tls/i686/cmov/libutil-2.11.1.so 002bb000-002bc000 rw-p 2000 08:05 1659859 /lib/tls/i686/cmov/libutil-2.11.1.so 002bc000-002e r-xp 08:05 1659844 /lib/tls/i686/cmov/libm-2.11.1.so 002e-002e1000 r--p 00023000 08:05 1659844 /lib/tls/i686/cmov/libm-2.11.1.so 002e1000-002e2000 rw-p 00024000 08:05 1659844 /lib/tls/i686/cmov/libm-2.11.1.so 002e2000-00435000 r-xp 08:05 1659789 /lib/tls/i686/cmov/libc-2.11.1.so 00435000-00436000 ---p 00153000 08:05 1659789 /lib/tls/i686/cmov/libc-2.11.1.so 00436000-00438000 r--p 00153000 08:05 1659789 /lib/tls/i686/cmov/libc-2.11.1.so 00438000-00439000 rw-p 00155000 08:05 1659789 /lib/tls/i686/cmov/libc-2.11.1.so 00439000-0043c000 rw-p 00:00 0 0043c000-0044 r-xp 08:05 164265 /opt/sage-4.5.1/local/lib/python2.6/lib-dynload/readline.so 0044-00441000 r--p 3000 08:05 164265 /opt/sage-4.5.1/local/lib/python2.6/lib-dynload/readline.so 00441000-00442000 rw-p 4000 08:05 164265 /opt/sage-4.5.1/local/lib/python2.6/lib-dynload/readline.so 00442000-00472000 r-xp 08:05 949057 /opt/sage-4.5.1/local/lib/libreadline.so.6.0 00472000-00473000 r--p 0002f000 08:05 949057 /opt/sage-4.5.1/local/lib/libreadline.so.6.0 00473000-00476000 rw-p 0003 08:05 949057 /opt/sage-4.5.1/local/lib/libreadline.so.6.0 00476000-00478000 rw-p 00:00 0 00478000-004ac000 r-xp 08:05 580533 /lib/libncurses.so.5.7 Program received signal SIGABRT, Aborted. 0x0012d422 in __kernel_vsyscall () wich looks like the one i get running just sage. greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] sage crashes on calculating roots of a polynom
uname -a Linux neo 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux sage --version | Sage Version 4.5.3, Release Date: 2010-09-04 -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: sage crashes on calculating roots of a polynom
im sorry, but I cant install valgrind because it does not compile with
my glibc version.
Ubuntu 10.4 is comming with glib 2.10 and valgrind builds just with
glibc 2.2 up to 2.7
greatz
Am 07.10.2010 19:38, schrieb maldun:
I would suggest to run sage with valgrind to get more information out
of your error messages.
On 7 Okt., 17:31, Johannes dajo.m...@web.de wrote:
Hi list,
i got my sage crashed once again:
sage: a,b,c= var('a,b,c')
sage: mprime = matrix([[01,b+1,2],[a+1,2,1],[2,1,c+1]])
sage: cp = mprime.charpoly()
sage: cp.real_roots()
*** glibc detected *** python: free(): invalid pointer: 0x00541bfc ***
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6(+0x6b591)[0xc57591]
/lib/tls/i686/cmov/libc.so.6(+0x6cde8)[0xc58de8]
/lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0xc5becd]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/rings/memory.so(+0x121d)[0x16c21d]
/opt/sage-4.5.1/local/lib/libmpfr.so.1(mpfr_clear+0x58)[0x8e3778]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/rings/polynomial/polynomial_real_mpfr_dense.so(+0x5dd5)[0x68fcdd5]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(+0x86c43)[0x724c43]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x3535)[0x76a2f5]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(+0x57ed7)[0x6f5ed7]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(+0x3bfb4)[0x6d9fb4]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/structure/coerce_maps.so(+0xffb2)[0xb4ffb2]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/structure/parent.so(+0x1f4df)[0x5214df]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyCFunction_Call+0x128)[0x70bc48]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(+0x90cad)[0x72ecad]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/rings/polynomial/polynomial_element.so(+0x7511)[0x1327511]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyCFunction_Call+0xa5)[0x70bbc5]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/rings/polynomial/polynomial_element.so(+0xb33d3)[0x13d33d3]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyCFunction_Call+0x128)[0x70bc48]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyObject_Call+0x5c)[0x6c873c]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_CallObjectWithKeywords+0x54)[0x765f84]
/opt/sage-4.5.1/local/lib/python2.6/site-packages/sage/rings/polynomial/polynomial_element.so(+0x39aea)[0x1359aea]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x482e)[0x76b5ee]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCode+0x63)[0x76d0c3]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x50c9)[0x76be89]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x76b130]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x76b130]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x59e1)[0x76c7a1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x76b130]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x76b130]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4370)[0x76b130]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7d1)[0x76cfa1]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyEval_EvalCode+0x63)[0x76d0c3]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyRun_FileExFlags+0xb1)[0x78cf91]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyRun_SimpleFileExFlags+0xdc)[0x78d1cc]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(PyRun_AnyFileExFlags+0x7a)[0x78d5fa]
/opt/sage-4.5.1/local/lib/libpython2.6.so.1.0(Py_Main+0xc7d)[0x799c4d]
python(main+0x27)[0x8048657]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xc02bd6]
python[0x8048591]
=== Memory map:
0011-00117000 r-xp 08:05 164238
/opt/sage-4.5.1/local/lib/python2.6/lib-dynload/itertools.so
00117000-00118000 r--p 6000 08:05 164238
/opt/sage-4.5.1/local/lib
[sage-devel] segfault while running sage
Hi, i just got my sage crashed with theis following command sage: filter(lambda x: all([item.denominator()._cmp_(1) for item in x]), [[coordinate.subs(c=0).subs(b=0) for coordinate in item] for item in wi ]) Unhandled SIGSEGV: A segmentation fault occurred in Sage. This probably occurred because a *compiled* component of Sage has a bug in it (typically accessing invalid memory) or is not properly wrapped with _sig_on, _sig_off. You might want to run Sage under gdb with 'sage -gdb' to debug this. Sage will now terminate (sorry). Process SAGE exited abnormally with code 1 using Sage Version 4.5.3, Release Date: 2010-09-04 running sage -gdb leads to this: sage: filter(lambda x: all([item.denominator()._cmp_(1) for item in x]), [[coordinate.subs(c=0).subs(b=0) for coordinate in item] for item in wi ]) Program received signal SIGSEGV, Segmentation fault. GiNaC::basic::compare (this=0x8416bb0, other=...) at basic.cpp:838 838 basic.cpp: No such file or directory. in basic.cpp it seems to be a bug in the _cmp_ function. greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Error while building libfplll in sage -upgrade
Hi list, i just tried to update sage by sage -upgrade errormessage after sage -upgrade g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.4.3/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.4.3/crtbeginS.o .libs/dummy.o -Wl,--rpath -Wl,/opt/sage-4.5.1/local/lib -Wl,--rpath -Wl,/opt/sage-4.5.1/local/lib -L/opt/sage-4.5.1/local/lib /opt/sage-4.5.1/local/lib/libmpfr.so /opt/sage-4.5.1/local/lib/libgmp.so -L/opt/sage-4.5.1/local/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.4.3 -L/usr/lib/gcc/i486-linux-gnu/4.4.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.4.3/../../.. -L/usr/lib/i486-linux-gnu -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.4.3/crtendS.o /usr/lib/gcc/i486-linux-gnu/4.4.3/../../../../lib/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.1.0 (cd .libs rm -f libfplll.so.0 ln -s libfplll.so.0.1.0 libfplll.so.0) (cd .libs rm -f libfplll.so ln -s libfplll.so.0.1.0 libfplll.so) ar cru .libs/libfplll.a dummy.o ranlib .libs/libfplll.a creating libfplll.la /bin/sed: can't read /tmp/sage-4.5.1/local/lib/libgmp.la: No such file or directory libtool: link: `/tmp/sage-4.5.1/local/lib/libgmp.la' is not a valid libtool archive make[2]: *** [libfplll.la] Fehler 1 make[2]: Verlasse Verzeichnis '/opt/sage-4.5.1/spkg/build/libfplll-3.0.12.p1/src' make[1]: *** [all-recursive] Fehler 1 make[1]: Verlasse Verzeichnis '/opt/sage-4.5.1/spkg/build/libfplll-3.0.12.p1/src' Error building libfplll [...] install.log: checking for the kernel version... 2.6 family (2.6.32-22-generic) checking for a supported CPU/OS combination... ok (i686-linux) checking for egrep... grep -E checking the libc version... unsupported version configure: error: Valgrind requires glibc version 2.2 - 2.7 error configuring valgrind 3.3.1 real0m2.661s user0m0.604s sys 0m0.768s [...] Warning: Attempted to overwrite SAGE_ROOT environment variable p_group_cohomology-2.0 Machine: Linux neo 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux sage: /opt/sage-4.5.1/p_group_cohomology-2.0 is already installed SAGE_ROOT=/opt/sage-4.5.1 it seems that im using the wrong version of glibc, i'm using the default ubuntu version 2.11.1 which is too high. is there any way to build it against this higher version? greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] domains for variables
Hi list, i try to solve a linear equation in ZZ in the variables w_i: sage: variables = [var(w + str(i),domain=ZZ)for i in range(s.nvertices())] sage: eq (w0 + w1 + w2 - 14*w3, w1 + 2*w2 - 8*w3, 2*w2 - 3*w3) sage: result [w0 == 15/2*r548, w1 == 5*r548, w2 == 3/2*r548, w3 == r548] up to here it's ok, but now im lookin for the smalest integer r548 0 solving this equatoins. in other words, the smalest r548 such that every wi is in ZZ. How can i do this? Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] domains for variables
sorry, wrong list. Am 30.07.2010 00:01, schrieb Johannes: Hi list, i try to solve a linear equation in ZZ in the variables w_i: sage: variables = [var(w + str(i),domain=ZZ)for i in range(s.nvertices())] sage: eq (w0 + w1 + w2 - 14*w3, w1 + 2*w2 - 8*w3, 2*w2 - 3*w3) sage: result [w0 == 15/2*r548, w1 == 5*r548, w2 == 3/2*r548, w3 == r548] up to here it's ok, but now im lookin for the smalest integer r548 0 solving this equatoins. in other words, the smalest r548 such that every wi is in ZZ. How can i do this? Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: new keywords for limit()
2. I wanted to avoid confusion about whether left meant moving leftward as opposed to from the left. +1 here seems to be more presice than just left or right. greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] bug in solve?
i just tried something with solving a equation, i think i did it the
wrong way, but still it should not result in this:
def calc_wights_by_sum(s)
variables = var([w + str(i) for i in range(s.nvertices())])
equation = reduce(lambda f1,f2: f1 + f2, [variables[i] * s.vertex(i)
for i in range(s.nvertices())]) == 0
print equation
return solve(equation,variables)
sage: calc_wights_by_sum(s)
False
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.RuntimeError' ignored
Exception RuntimeError: RuntimeError('maximum recursion depth exceeded
in cmp',) in Exception RuntimeError: 'maximum recursion depth exceeded
in __subclasscheck__' in type 'exceptions.RuntimeError' ignored
ignored
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.RuntimeError' ignored
Exception RuntimeError: RuntimeError('maximum recursion depth exceeded
in cmp',) in Exception RuntimeError: 'maximum recursion depth exceeded
in __subclasscheck__' in type 'exceptions.RuntimeError' ignored
[...]
i just helped to kill python by killall -9 python.
greatz Johannes
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
Re: [sage-devel] bug in solve?
ok, i got my first mistake,
the first line in the functoin schould be this:
variables = [var(w + str(i))for i in range(s.nvertices())]
but anyway, no reason for such a big problem.
Am 29.07.2010 01:15, schrieb Johannes:
i just tried something with solving a equation, i think i did it the
wrong way, but still it should not result in this:
def calc_wights_by_sum(s)
variables = var([w + str(i) for i in range(s.nvertices())])
equation = reduce(lambda f1,f2: f1 + f2, [variables[i] * s.vertex(i)
for i in range(s.nvertices())]) == 0
print equation
return solve(equation,variables)
sage: calc_wights_by_sum(s)
False
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.RuntimeError' ignored
Exception RuntimeError: RuntimeError('maximum recursion depth exceeded
in cmp',) in Exception RuntimeError: 'maximum recursion depth exceeded
in __subclasscheck__' in type 'exceptions.RuntimeError' ignored
ignored
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.RuntimeError' ignored
Exception RuntimeError: RuntimeError('maximum recursion depth exceeded
in cmp',) in Exception RuntimeError: 'maximum recursion depth exceeded
in __subclasscheck__' in type 'exceptions.RuntimeError' ignored
[...]
i just helped to kill python by killall -9 python.
greatz Johannes
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
[sage-devel] global options for python
Hi list, i want to check which part of the sagecode makes problems when trying to port it to python 3.x. For that, I want want to build it with the '-3' option, but i dont want to edit every single makefile. is the a special place to put something like a global python build parameter? greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] global options for python
many thanks guys, i'll test it soon and give some feedback about the
results.
greatz Johannes
Am 14.07.2010 23:55, schrieb Carl Witty:
On Wed, Jul 14, 2010 at 2:43 PM, Mike Hansen mhan...@gmail.com wrote:
On Wed, Jul 14, 2010 at 2:31 PM, Johannes dajo.m...@web.de wrote:
i want to check which part of the sagecode makes problems when trying to
port it to python 3.x. For that, I want want to build it with the '-3'
option, but i dont want to edit every single makefile. is the a special
place to put something like a global python build parameter?
This is a runtime option you pass to python rather than a build
option. To make use of it , you can make the following change in
$SAGE_ROOT/local/bin/sage-sage
--- a/sage-sage
+++ b/sage-sage
@@ -205,7 +205,7 @@
sage() {
sage_setup
-sage-ipython $@ -i
+python -3 sage-ipython $@ -i
}
if [ $# -eq 0 ]; then
Then, you'll see a lot of deprecation warnings when Sage starts.
Also, you can change this line in sage-doctest:
--- a/sage-doctestTue Jul 13 18:13:17 2010 -0700
+++ b/sage-doctestWed Jul 14 14:56:40 2010 -0700
@@ -125,7 +125,7 @@
##
# The Python binary
##
-PYTHON = python
+PYTHON = python -3
def pad_zeros(s, size):
and any doctests will be run in -3 mode. (Which means that huge
numbers of doctests will fail, because the expected outputs don't
have the deprecation warnings.)
Carl
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
Re: [sage-combinat-devel] Re: Question about LatticePolytopeClass
hey Andrey, thnx for your information about __eq__ on latticepolytopes - i think every coder understands ;). is there a patch with the new version, even if it's not working? I'd like to have a look at it and maybe to do some work there (if i find free time somehow) Am 09.07.2010 19:35, schrieb Andrey Novoseltsev: [..] I don't agree that elements of LatticePolytope are its integer points. As a set it is a subset of some real space, so usually it is infinite. i don't agree here. the Points of the polytope depend on the space, where it's defined in and a latticepolytope is always defined in on a lattice, so the points of the polytope just can be latticepoints. But I dont see any connection to a real space, maybe, ca connection to the quotientfield of the lattice or to the algebraic clousure of it. greatz Johannes -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-de...@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
[sage-devel] Bug or feature - questoin about databindings
Hi list, i just tried the following pice of code and returned an unexcepted, but explainable behavior: sage: p = los[0][1] A lattice polytope: 3-dimensional, 4 vertices. sage: list(set([ p for p in reduce (lambda x,y : x + y,[ f.points() for f in p.facets() ])])) [0, ... some list of points ] sage: p 34 my old variable p = los[0][1] is overwritten by the one i used in the list comprehension. Is this the default sage or python behavior? or is this an bug in sage/python? In my eyes, every a variable created in a listcomprehension should overwrite an existing one (i think in my case this happens, because the in every step i have to access my orginal p) and after that should be destroyed again. greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Bug or feature - questoin about databindings
Am 10.07.2010 15:04, schrieb William Stein [...] This is standard Python behaviour. A list comprehension doesn't have its own scope, so the p used in the list comprehension overwrites the other p previously declared in the same scope. I agree that this can be annoying, but it's a fact of life in Python programming. ... albiet, a temporary one (!): wst...@redhawk:~$ python3.1 Python 3.1.2 (r312:79147, Apr 15 2010, 15:35:48) [GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. [i*i for i in range(10)] [0, 1, 4, 9, 16, 25, 36, 49, 64, 81] i Traceback (most recent call last): File stdin, line 1, in module NameError: name 'i' is not defined The point being that in Python 3.x this fact of life is change. Eventually, Sage will switch to Python 3.x. William is there a way to build sage testwise with python 3.x? For example by setting a special path/variable or replace some files? greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-combinat-devel] Question about LatticePolytopeClass
Hi list, im just playing around with sage and LatticePolytopes and im wondering why theres no __eq__ implementet for them. if i have this code: s1 = LatteciPolytope(matrix([[1,0,-1],[0,1,-1]]) s2 = LatteciPolytope(matrix([[1,0,-1],[0,1,-1]]) then s1 == s2 evals to false. thats right in the sentence of ref-equality but in my eyes two polytopes are equal, if they live in the same space (in this case, on the same Lattice) and have the same edges. Is there any reason, why its not implemented that way? greatz Johannes -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-de...@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
[sage-devel] Re: SciTools in Sage
Nothing new on this issue? Regards, Johannes On Tue, Sep 9, 2008 at 10:41 AM, Johannes Ring [EMAIL PROTECTED] wrote: Hi Michael, On Thu, Sep 4, 2008 at 4:59 AM, mabshoff [EMAIL PROTECTED] wrote: On Sep 3, 2:37 am, Johannes Ring [EMAIL PROTECTED] wrote: Hello Sage developers, Hi Johannes, I am one of the developers of the Python package SciTools (http://scitools.googlecode.com) and for some time I have seen that there is a package for SciTools in the experimental section in Sage. The package is called scitools++ and it includes not only SciTools, but also packages like doconce, epydoc, Gnuplot, IPython, Pmw, preprocess.py, and Scientific Python. For a couple of days ago I decided to try it out, however, it didn't work very well. I think there was a problem with IPython. I'm not sure who created the package, but I think there should be a separate package for SciTools that doesn't install all the other packages. I have therefore created a new SciTools package for Sage, called scitools-0.4.spkg. The package depends on Gnuplot.py 1.8 and I have created a Sage package for this as well. Both packages can be downloaded fromhttp://folk.uio.no/johannr/tmp/. It would be very nice if SciTools was included into Sage, perhaps in the experimental section for now. I think the scitools++ package can be removed. I will check out the spkgs and get them reviewed. It might take a day or two, so please ping us if nothing happens. So, how is it going with the review? In general we have moved away from gnuplot due to its non-GPL compatible license. We have discussed creating a non-free section for spkgs due to code like gnuplot. Okay, I see. Thanks for considering including SciTools into Sage, Johannes Thanks, Johannes Ring Cheers, Michael P.S. For those that don't know about SciTools, it's a Python package with lots of useful tools for scientific computing and it is built on top of other Python packages like NumPy, SciPy, and Scientific Python. SciTools also includes a plotting interface called Easyviz (http://code.google.com/p/scitools/wiki/EasyvizDocumentation), which is a unified interface to other plotting packages like Gnuplot, Matplotlib, VTK, and several others. It can do both curve plots and more advanced 2D/3D visualization of scalar and vector fields and it has simple, Matlab-like syntax. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: SciTools in Sage
On Thu, Sep 25, 2008 at 9:23 AM, mabshoff [EMAIL PROTECTED] wrote: On Sep 25, 12:01 am, Johannes Ring [EMAIL PROTECTED] wrote: Nothing new on this issue? Regards, Johannes I took a look a week ago and besides some small issues everything looked good. But I am buried under work and have some deadlines until the end of the months, so if somebody else wants to do formal review it is fine by me. Sorry for the delay, No problem, take your time. There is no rush. Johannes Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: SciTools in Sage
Hi Michael, On Thu, Sep 4, 2008 at 4:59 AM, mabshoff [EMAIL PROTECTED] wrote: On Sep 3, 2:37 am, Johannes Ring [EMAIL PROTECTED] wrote: Hello Sage developers, Hi Johannes, I am one of the developers of the Python package SciTools (http://scitools.googlecode.com) and for some time I have seen that there is a package for SciTools in the experimental section in Sage. The package is called scitools++ and it includes not only SciTools, but also packages like doconce, epydoc, Gnuplot, IPython, Pmw, preprocess.py, and Scientific Python. For a couple of days ago I decided to try it out, however, it didn't work very well. I think there was a problem with IPython. I'm not sure who created the package, but I think there should be a separate package for SciTools that doesn't install all the other packages. I have therefore created a new SciTools package for Sage, called scitools-0.4.spkg. The package depends on Gnuplot.py 1.8 and I have created a Sage package for this as well. Both packages can be downloaded fromhttp://folk.uio.no/johannr/tmp/. It would be very nice if SciTools was included into Sage, perhaps in the experimental section for now. I think the scitools++ package can be removed. I will check out the spkgs and get them reviewed. It might take a day or two, so please ping us if nothing happens. So, how is it going with the review? In general we have moved away from gnuplot due to its non-GPL compatible license. We have discussed creating a non-free section for spkgs due to code like gnuplot. Okay, I see. Thanks for considering including SciTools into Sage, Johannes Thanks, Johannes Ring Cheers, Michael P.S. For those that don't know about SciTools, it's a Python package with lots of useful tools for scientific computing and it is built on top of other Python packages like NumPy, SciPy, and Scientific Python. SciTools also includes a plotting interface called Easyviz (http://code.google.com/p/scitools/wiki/EasyvizDocumentation), which is a unified interface to other plotting packages like Gnuplot, Matplotlib, VTK, and several others. It can do both curve plots and more advanced 2D/3D visualization of scalar and vector fields and it has simple, Matlab-like syntax. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] SciTools in Sage
Hello Sage developers, I am one of the developers of the Python package SciTools (http://scitools.googlecode.com) and for some time I have seen that there is a package for SciTools in the experimental section in Sage. The package is called scitools++ and it includes not only SciTools, but also packages like doconce, epydoc, Gnuplot, IPython, Pmw, preprocess.py, and Scientific Python. For a couple of days ago I decided to try it out, however, it didn't work very well. I think there was a problem with IPython. I'm not sure who created the package, but I think there should be a separate package for SciTools that doesn't install all the other packages. I have therefore created a new SciTools package for Sage, called scitools-0.4.spkg. The package depends on Gnuplot.py 1.8 and I have created a Sage package for this as well. Both packages can be downloaded from http://folk.uio.no/johannr/tmp/ . It would be very nice if SciTools was included into Sage, perhaps in the experimental section for now. I think the scitools++ package can be removed. Thanks, Johannes Ring P.S. For those that don't know about SciTools, it's a Python package with lots of useful tools for scientific computing and it is built on top of other Python packages like NumPy, SciPy, and Scientific Python. SciTools also includes a plotting interface called Easyviz (http://code.google.com/p/scitools/wiki/EasyvizDocumentation), which is a unified interface to other plotting packages like Gnuplot, Matplotlib, VTK, and several others. It can do both curve plots and more advanced 2D/3D visualization of scalar and vector fields and it has simple, Matlab-like syntax. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
