[sage-devel] On (di)graph generation
1) list(graphs.nauty_geng(0)) gives empty list, whereas Sage knows a graph of 0 vertices. Can someone ask McKay to handle this special case too? 2) Is there an example of graph property that holds after deleting any vertex but not necessarily after deleting an edge? Or the converse? 3) Currently graphs(...) has parameters vertices and augment. With graphs(n, augment='edges') it generates all n-vertex graphs, whereas graphs(n, augment='vertices') generates all graphs of 0, 1, ..., n vertices. Would it be more logical to have parameters max_vertices and min_vertices? 4) When is augment='edges' usefull? Is sum(sum(1 for _ in graphs(i, augment='edges')) for i in range(9)) faster in someone's computer than sum(1 for _ in graphs(8, augment='vertices')) ? -- Jori Mäntysalo
[sage-devel] Issues installing the optional "libhomfly" package
although the linking error you got seems to be not related to GC. -- 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] Issues installing the optional "libhomfly" package
to install Boehm GC Sage package, do sage -i gc -- 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] Issues installing the optional "libhomfly" package
Greetings,
I have been trying to use the function "homfly_polynomial()" from the Link
package in Sage, but it requires an optional package "libhomfly":
http://files.sagemath.org/spkg/upstream/libhomfly/index.html.
Unfortunately, when I try to install libhomfly ("sage -i libhomfly") the
build always fails (see attached log file).
One of the dependencies for libhomfly is Boehm GC, but when I try to
install this package ("sage -i boehm_gc"), it is not even found on Sage's
list of optional packages (even though it's displayed on the
website:http://mirrors-usa.go-parts.com/sage/sagemath/spkg/upstream/boehm_gc/index.html).
I'm not sure if this is indeed the issue, but it's just something I came
across.
For what it's worth, I'm running SageMath 8.0 and MacOS 10.12.6 on a mid
2012 MacBook Pro with a 2.3 GHz i7 processor and 8GB RAM.
Any help is much appreciated.
JH
--
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.
Found local metadata for libhomfly-1.0r2
Attempting to download package libhomfly-1.0r2.tar.gz from mirrors
http://files.sagemath.org/spkg/upstream/libhomfly/libhomfly-1.0r2.tar.gz
[..]
libhomfly-1.0r2
Setting up build directory for libhomfly-1.0r2
Finished extraction
No patch files found in ../patches
Host system:
Darwin Jesses-MacBook-Pro.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15
17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/Applications/SageMath-8.0.app/Contents/Resources/sage/local/libexec/gcc/x86_64-apple-darwin15.6.0/5.4.0/lto-wrapper
Target: x86_64-apple-darwin15.6.0
Configured with: ../src/configure
--prefix=/Applications/SageMath-8.0.app/Contents/Resources/sage/local
--with-local-prefix=/Applications/SageMath-8.0.app/Contents/Resources/sage/local
--with-gmp=/Applications/SageMath-8.0.app/Contents/Resources/sage/local
--with-mpfr=/Applications/SageMath-8.0.app/Contents/Resources/sage/local
--with-mpc=/Applications/SageMath-8.0.app/Contents/Resources/sage/local
--with-system-zlib --disable-multilib --disable-nls
--enable-languages=c,c++,fortran --disable-libitm
--with-build-config=bootstrap-debug --without-isl --without-cloog
Thread model: posix
gcc version 5.4.0 (GCC)
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... build-aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking the archiver (ar) interface... ar
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking build system type... x86_64-apple-darwin16.7.0
checking host system type... x86_64-apple-darwin16.7.0
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... ld
checking if the linker (ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking how to convert x86_64-apple-darwin16.7.0 file names to
x86_64-apple-darwin16.7.0 format... func_convert_file_
Re: [sage-devel] proposal: remove libogg and libtheora completely from sage
On Tuesday, October 10, 2017 at 5:10:35 PM UTC+2, Erik Bray wrote: > > It raises the question: Who added these packages to > Sage in the first place, and what for? > Weren't they added because of earlier giac versions? If so they are no longer needed now I believe. -- 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] proposal: remove libogg and libtheora completely from sage
On Wed, Sep 20, 2017 at 1:55 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > On 19/09/2017 20:29, Maarten Derickx wrote: >> >> Since the people in the thread "proposal: downgrade libtheora to >> experimental package" >> at https://groups.google.com/forum/#!topic/sage-devel/olOxh1f6-cc were >> quite in favour of going even further then just downgrading it here a >> concrete proposal: >> >> remove the optional libogg and libtheora packages completely from sage. >> >> for motivation one can see the other thread. Short summary, they don't >> seem >> to add anything a lot of value to sage the library and shipping video and >> audio codecs is not really a goal of sage the distribution, so we should >> not include them even as optional package. Furthermore installing >> libtheora >> is currently broken. >> >> The main reason why I start this new thread is that I think it should be >> clear from just the subject title what the proposed change is, so that the >> sage developers not reading all the details of a long discussion don't >> feel >> surprised if these packages are suddenly gone. >> >> If people have any objections to this please let me know. > > > -1. It is safer to first downgrade to experimental and then remove because > not supported anymore. Some users (not knowing the existence of sage-devel) > might be playing with it (who knows). > > I will upvote in a year or so. I think downgrading to experimental seems reasonable (and perhaps deprecating, though I suppose one could consider that a form of deprecation...?) It raises the question: Who added these packages to Sage in the first place, and what for? -- 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: recipe for target 'ecl-16.1.2.p4' fail
On Tuesday, October 10, 2017 at 3:07:57 PM UTC+2, Johannes Martin wrote: > > Actually, setting SAGE_GCC_INSTALL=yes didn't help. > Apology, it should have read SAGE_INSTALL_GCC. -- 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: changelogs missing in http://www.sagemath.org/changelogs/index.html
This would indeed be fantastic as I am writing an application for funding for a future SageDays and it would be great to have an order of magnitude of how many active contributors there are to the latest Sage releases! Le jeudi 28 septembre 2017 14:59:50 UTC+2, kcrisman a écrit : > > > > > I'll try to have a look today. >> > > That would be fantastic if this could be back up, granted the definitely > nontrivial work involved getting it going again. > -- 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: 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] Re: Graphs: Hamiltonian path vs. cycle
On Tue, 10 Oct 2017, Dima Pasechnik wrote: I cannot think of a reason other than different authors/reviewers, different weather, different amount of coffee... :-) Haha. I opened #24003 for this, but will wait some days to see if there will be more comments. -- Jori Mäntysalo
[sage-devel] optional package mpfrcx not on the mirror
This is probably because it is still in beta. The tarbal can be found at https://trac.sagemath.org/ticket/11806 -- 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: Graphs: Hamiltonian path vs. cycle
On Tuesday, October 10, 2017 at 8:21:56 AM UTC+1, Jori Mäntysalo wrote: > > Try > > g = graphs.StarGraph(3) > print(g.hamiltonian_path()) > print(g.hamiltonian_cycle()) > > Is there a reason for this? I cannot think of a reason other than different authors/reviewers, different weather, different amount of coffee... :-) > If not, which way we should correct it? > IMHO returning an empty is OK, not sure about the overall consistency though. > > (#23994 is waiting for a review, will also depend on this.) > > -- > Jori Mäntysalo > -- 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] Graphs: Hamiltonian path vs. cycle
Try g = graphs.StarGraph(3) print(g.hamiltonian_path()) print(g.hamiltonian_cycle()) Is there a reason for this? If not, which way we should correct it? (#23994 is waiting for a review, will also depend on this.) -- Jori Mäntysalo
[sage-devel] optional package mpfrcx not on the mirror
Hello, [mpfrcx-0.4.2] sage_bootstrap.tarball.FileNotMirroredError: tarball does not exist on mirror network Vincent -- 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.
