[sage-support] Error compiling : patch-2-7-5
Dear all, I already have a sage installed from binaries (from the debian package) and I'm trying to compile a dev version from source. I'm getting this error (log attached) after less than 1 minute. Does someone know why? I have a Ubuntu 16.04. My default python is 3.6.1 (is this the problem?). It looks like some conflicts with some local stuff. Best Viviane -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout. Found local metadata for patch-2.7.5 Attempting to download package patch-2.7.5.tar.gz from mirrors http://www-ftp.lip6.fr/pub/math/sagemath/spkg/upstream/patch/patch-2.7.5.tar.gz [..] patch-2.7.5 Setting up build directory for patch-2.7.5 Traceback (most recent call last): File "/home/viviane/sage/build/bin/sage-uncompress-spkg", line 23, in run() File "/home/viviane/sage/build/bin/../sage_bootstrap/uncompress/cmdline.py", line 72, in run unpack_archive(archive, dirname) File "/home/viviane/sage/build/bin/../sage_bootstrap/uncompress/action.py", line 68, in unpack_archive archive.extractall(members=archive.names) File "/home/viviane/sage/build/bin/../sage_bootstrap/uncompress/tar_file.py", line 90, in extractall members=members) File "/home/viviane/miniconda3/lib/python3.6/tarfile.py", line 2007, in extractall numeric_owner=numeric_owner) File "/home/viviane/miniconda3/lib/python3.6/tarfile.py", line 2049, in extract numeric_owner=numeric_owner) TypeError: _extract_member() got an unexpected keyword argument 'set_attrs' Error: failed to extract /home/viviane/sage/upstream/patch-2.7.5.tar.gz Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the log file /home/viviane/sage/logs/pkgs/patch-2.7.5.log Describe your computer, operating system, etc. Found local metadata for patch-2.7.5 Using cached file /home/viviane/sage/upstream/patch-2.7.5.tar.gz patch-2.7.5 Setting up build directory for patch-2.7.5 Traceback (most recent call last): File "/home/viviane/sage/build/bin/sage-uncompress-spkg", line 23, in run() File "/home/viviane/sage/build/bin/../sage_bootstrap/uncompress/cmdline.py", line 72, in run unpack_archive(archive, dirname) File "/home/viviane/sage/build/bin/../sage_bootstrap/uncompress/action.py", line 68, in unpack_archive archive.extractall(members=archive.names) File "/home/viviane/sage/build/bin/../sage_bootstrap/uncompress/tar_file.py", line 90, in extractall members=members) File "/home/viviane/miniconda3/lib/python3.6/tarfile.py", line 2007, in extractall numeric_owner=numeric_owner) File "/home/viviane/miniconda3/lib/python3.6/tarfile.py", line 2049, in extract numeric_owner=numeric_owner) TypeError: _extract_member() got an unexpected keyword argument 'set_attrs' Error: failed to extract /home/viviane/sage/upstream/patch-2.7.5.tar.gz Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the log file /home/viviane/sage/logs/pkgs/patch-2.7.5.log Describe your computer, operating system, etc.
[sage-support] Question about Free algebra
Hi everyone, I'm doing this: sage: FreeA.a,b,c,d,e,f = FreeAlgebra(QQ,implementation=letterplace) sage: P = a*b*a*c*c*b + a*b*a*d*d*b + a*c*a*d*d*c + b*c*b*d*d*c sage: X = P.lm() sage: X a*b*a*c*c*b And now I would like a way to cut my element X into two factors of a given size. Something like sage: u,v = X[:2],X[2:] with then u=a*b and v = a*c*c*d except this doesn't work (no __getitem__ on X). I have looked a bit, but I cannot find how to do this even though it seems quite a natural operation. I must say, I don't even understand the datastructure of X, list(X) doesn't give me something I can easily read or transform into a word or anything... If someone knows about this, I would appreciate the help. Thank you Best Viviane -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
Re: [sage-support] Re: Make doc error
The problem was indeed the accent, we tried John's fix with # -*- coding: utf-8 -*- and it worked! Thank you for your help, it was kind of tricky. Best Viviane 2015-06-04 3:03 GMT-05:00 Volker Braun vbraun.n...@gmail.com: The docstring might have to be declared unicode (haven't actually looked at it): def foo(): u unicode string On Thursday, June 4, 2015 at 2:24:47 AM UTC+2, John H Palmieri wrote: Earlier in the docbuilding, I see this: [combinat ] building [inventory]: targets for 2 source files that are out of date [combinat ] updating environment: 0 added, 2 changed, 0 removed [combinat ] reading sources... [ 50%] sage/combinat/cluster_algebra_quiver/cluster_seed [combinat ] Encoding error: [combinat ] 'ascii' codec can't decode byte 0xc3 in position 414: ordinal not in range(128) [combinat ] The full traceback has been saved in /var/folders/cp/n8wtqs490tq5psknff1hv9qrgn/T/sphinx-err-jeDhGW.log, if you want to report the issue to the developers. which is caused by the accents on line 18 of cluster_seed.py. Does the problem go away if you remove those accents or add something like # -*- coding: utf-8 -*- to the top of the file? John On Wednesday, June 3, 2015 at 4:24:37 PM UTC-7, Viviane Pons wrote: This I did already... 2015-06-03 18:21 GMT-05:00 Volker Braun vbrau...@gmail.com: Try make doc-clean make On Thursday, June 4, 2015 at 1:06:03 AM UTC+2, Viviane Pons wrote: Hi everyone, I get this doc build error on a branch ( http://trac.sagemath.org/ticket/18594) and I have no idea why. I just know the error comes from the branch (I can build the doc fine on develop) but I don't know which commit caused it. I'm going to look into it but if someone has the slightest idea of what is causing it, it would help! The error: [reference] WARNING: Unable to fetch /media/ubuntudata/Programming/sage/src/doc/output/doctrees/en/reference/combinat/environment.pickle Error building the documentation. Note: incremental documentation builds sometimes cause spurious error messages. To be certain that these are real errors, run make doc-clean first and try again. Traceback (most recent call last): File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 1626, in module getattr(get_builder(name), type)() File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 292, in _wrapper getattr(get_builder(document), 'inventory')(*args, **kwds) File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 516, in _wrapper getattr(DocBuilder(self.name, lang), format)(*args, **kwds) File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 110, in f eval(compile(open(sys.argv[0]).read(), sys.argv[0], 'exec')) File /media/ubuntudata/Programming/sage/src/doc/common/custom-sphinx-build.py, line 219, in module raise OSError(ERROR_MESSAGE) OSError: [reference] WARNING: Unable to fetch /media/ubuntudata/Programming/sage/src/doc/output/doctrees/en/reference/combinat/environment.pickle Best Viviane -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com. To post to this group, send email to sage-s...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
Re: [sage-support] Re: Make doc error
This I did already... 2015-06-03 18:21 GMT-05:00 Volker Braun vbraun.n...@gmail.com: Try make doc-clean make On Thursday, June 4, 2015 at 1:06:03 AM UTC+2, Viviane Pons wrote: Hi everyone, I get this doc build error on a branch ( http://trac.sagemath.org/ticket/18594) and I have no idea why. I just know the error comes from the branch (I can build the doc fine on develop) but I don't know which commit caused it. I'm going to look into it but if someone has the slightest idea of what is causing it, it would help! The error: [reference] WARNING: Unable to fetch /media/ubuntudata/Programming/sage/src/doc/output/doctrees/en/reference/combinat/environment.pickle Error building the documentation. Note: incremental documentation builds sometimes cause spurious error messages. To be certain that these are real errors, run make doc-clean first and try again. Traceback (most recent call last): File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 1626, in module getattr(get_builder(name), type)() File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 292, in _wrapper getattr(get_builder(document), 'inventory')(*args, **kwds) File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 516, in _wrapper getattr(DocBuilder(self.name, lang), format)(*args, **kwds) File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 110, in f eval(compile(open(sys.argv[0]).read(), sys.argv[0], 'exec')) File /media/ubuntudata/Programming/sage/src/doc/common/custom-sphinx-build.py, line 219, in module raise OSError(ERROR_MESSAGE) OSError: [reference] WARNING: Unable to fetch /media/ubuntudata/Programming/sage/src/doc/output/doctrees/en/reference/combinat/environment.pickle Best Viviane -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
[sage-support] Make doc error
Hi everyone, I get this doc build error on a branch ( http://trac.sagemath.org/ticket/18594) and I have no idea why. I just know the error comes from the branch (I can build the doc fine on develop) but I don't know which commit caused it. I'm going to look into it but if someone has the slightest idea of what is causing it, it would help! The error: [reference] WARNING: Unable to fetch /media/ubuntudata/Programming/sage/src/doc/output/doctrees/en/reference/combinat/environment.pickle Error building the documentation. Note: incremental documentation builds sometimes cause spurious error messages. To be certain that these are real errors, run make doc-clean first and try again. Traceback (most recent call last): File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 1626, in module getattr(get_builder(name), type)() File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 292, in _wrapper getattr(get_builder(document), 'inventory')(*args, **kwds) File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 516, in _wrapper getattr(DocBuilder(self.name, lang), format)(*args, **kwds) File /media/ubuntudata/Programming/sage/src/doc/common/builder.py, line 110, in f eval(compile(open(sys.argv[0]).read(), sys.argv[0], 'exec')) File /media/ubuntudata/Programming/sage/src/doc/common/custom-sphinx-build.py, line 219, in module raise OSError(ERROR_MESSAGE) OSError: [reference] WARNING: Unable to fetch /media/ubuntudata/Programming/sage/src/doc/output/doctrees/en/reference/combinat/environment.pickle Best Viviane -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
Re: [sage-support] segfault when plotting gamma function
Will do 2015-04-15 14:30 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com: I would send a message to sage-devel with the ticket number... and you could also specify it for the readers of this thread. On 15/04/15 20:28, Viviane Pons wrote: Ok, just did it. I'm not sure who to CC on this. Best Viviane 2015-04-15 14:12 GMT-04:00 Viviane Pons vivianep...@gmail.com: I'll do it, but I was hopping to get more context about it, also checking if it wasn't known somewhere. 2015-04-15 14:09 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com : Do you know how to open a ticket? On 15/04/15 20:08, Viviane Pons wrote: More context about this: I'm here with Buck at PyCon and he said he actually had this line running a few years ago. I don't know anything about this stuff so it's difficult to track what's wrong now. But it's really bad, as you can see, it's not just a usual exception, it's actually crashing Sage... (also, this is on Sage 6.6 and I believe it was there before. Buck had the error on the previous version and updated it to see if was fixed on 6.6) Best Viviane 2015-04-15 14:04 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com : Already the following fails sage: integrated = -(gamma(1/2*k, 1/2*R*k) - gamma(1/2*k))/gamma(1/2*k) sage: plot(integrated.subs(k=41), (R,0,6)) /home/vincent/bin/sage: line 134: 13683 Segmentation fault $SAGE_ROOT/src/bin/sage $@ On 15/04/15 18:55, Buck Evan wrote: I'm trying to plot a function involving the gamma function. It's this one: -(gamma(1/2*k, 1/2*R*k) - gamma(1/2*k))/gamma(1/2*k) If I try to plot the function with a k value any greater than 40, I get a segfault: sum( plot( integrated(k=k), (x, 0, 2.5), ymax=1.6, color=color, legend_label='k=%i' % k, figsize=6, aspect_ratio=1.0, ) for k, color in zip( [21, 22, 23, 26, 31, 41], ['blue', 'brown', 'red', 'green', 'black', 'yellow', 'orange'], ) ) /Users/buck/trees/mine/sage/sage: line 134: 12283 Segmentation fault: 11 $SAGE_ROOT/src/bin/sage $@ [I 12:15:10.735 NotebookApp] KernelRestarter: restarting kernel (1/5) This is extremely similar to the behavior I was getting with the pre-built 6.5 sage, so I think it's an old bug rather than a problem with my build. In 6.5 there was no output (I suspect the Segmentation Fault message was gobbled somehow), so I never tried to enable / debug a core dump in 6.5. Inspecting the 6.6 core dump, I see that it used 27528, mostly calling back and forth between two functions. Smells like stack overflow to me. (lldb) bt [27503/47384] * thread #1: tid = 0x, 0x000103588007 libpython2.7.dylib`vgetargskeywords + 23, stop reason = signal SIGSTOP * frame #0: 0x000103588007 libpython2.7.dylib` vgetargskeywords + 23 frame #1: 0x00010358890e libpython2.7.dylib`PyArg_ParseTupleAndKeywords + 174 frame #2: 0x00010356c40e libpython2.7.dylib`builtin___ import__ + 94 frame #3: 0x0001034a377f libpython2.7.dylib`PyObject_CallFunctionObjArgs + 367 frame #4: 0x00010774c1c4 coerce.so`__Pyx_Import(name= unavailable, from_list=0x000117da7560, level=unavailable) + 180 at coerce.c: 20339 frame #5: 0x00010774d08e coerce.so`__pyx_f_4sage_9structure_6coerce_py_scalar_ parent(__pyx_v_py_type=unavailable, __pyx_skip_dispatch= unavailable) + 510 at coerce.c:2938 frame #6: 0x000107760318 coerce.so`__pyx_f_4sage_9structure_6coerce_ 24CoercionModel_cache_maps_ canonical_coercion(__pyx_v_self=0x0001 07648d50, __pyx_v_x=0x7f8fbfc37238, __pyx_v_y=0x000118c5f390, __pyx_skip_dispatch=unavailable) + 3128 at coerce.c:9585 frame #7: 0x000107763cfe coerce.so`__pyx_pw_4sage_9structure_6coerce_ 24CoercionModel_cache_maps_ 25canonical_coercion + 13 at coerce.c:105 64 frame #8: 0x000107763cf1 coerce.so`__pyx_pw_4sage_9structure_6coerce_ 24CoercionModel_cache_maps_ 25canonical_coercion(__pyx_v_self=0x0 00107648d50, __pyx_args=0x000117e5f248, __pyx_kwds=0x) + 65 frame #9: 0x000103574f10 libpython2.7.dylib`PyEval_ EvalFrameEx + 26208 frame #10: 0x000103575fb0 libpython2.7.dylib`PyEval_ EvalCodeEx + 2144 frame #11: 0x0001034dae0c libpython2.7.dylib`function_ call + 124 frame #12: 0x00010d680381 pynac.so`__Pyx_PyObject_Call(func=0x000108f0c410, arg=unavailable, kw=PyObject * at scalar) + 65 at pynac .cpp:26785 frame #13: 0x00010d6a76e9 pynac.so`py_gcd(__pyx_v_n=0x7f8fbfc37238, __pyx_v_k=0x000118c5f390) + 521 at pynac.cpp:8416 frame #14: 0x00010d7d0f28 libpynac.1.dylib`GiNaC::gcd(GiNaC::numeric const, GiNaC::numeric const) + 56 frame #15: 0x00010d7ad100 libpynac.1.dylib`GiNaC::add
Re: [sage-support] segfault when plotting gamma function
I'll do it, but I was hopping to get more context about it, also checking if it wasn't known somewhere. 2015-04-15 14:09 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com: Do you know how to open a ticket? On 15/04/15 20:08, Viviane Pons wrote: More context about this: I'm here with Buck at PyCon and he said he actually had this line running a few years ago. I don't know anything about this stuff so it's difficult to track what's wrong now. But it's really bad, as you can see, it's not just a usual exception, it's actually crashing Sage... (also, this is on Sage 6.6 and I believe it was there before. Buck had the error on the previous version and updated it to see if was fixed on 6.6) Best Viviane 2015-04-15 14:04 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com: Already the following fails sage: integrated = -(gamma(1/2*k, 1/2*R*k) - gamma(1/2*k))/gamma(1/2*k) sage: plot(integrated.subs(k=41), (R,0,6)) /home/vincent/bin/sage: line 134: 13683 Segmentation fault $SAGE_ROOT/src/bin/sage $@ On 15/04/15 18:55, Buck Evan wrote: I'm trying to plot a function involving the gamma function. It's this one: -(gamma(1/2*k, 1/2*R*k) - gamma(1/2*k))/gamma(1/2*k) If I try to plot the function with a k value any greater than 40, I get a segfault: sum( plot( integrated(k=k), (x, 0, 2.5), ymax=1.6, color=color, legend_label='k=%i' % k, figsize=6, aspect_ratio=1.0, ) for k, color in zip( [21, 22, 23, 26, 31, 41], ['blue', 'brown', 'red', 'green', 'black', 'yellow', 'orange'], ) ) /Users/buck/trees/mine/sage/sage: line 134: 12283 Segmentation fault: 11 $SAGE_ROOT/src/bin/sage $@ [I 12:15:10.735 NotebookApp] KernelRestarter: restarting kernel (1/5) This is extremely similar to the behavior I was getting with the pre-built 6.5 sage, so I think it's an old bug rather than a problem with my build. In 6.5 there was no output (I suspect the Segmentation Fault message was gobbled somehow), so I never tried to enable / debug a core dump in 6.5. Inspecting the 6.6 core dump, I see that it used 27528, mostly calling back and forth between two functions. Smells like stack overflow to me. (lldb) bt [27503/47384] * thread #1: tid = 0x, 0x000103588007 libpython2.7.dylib`vgetargskeywords + 23, stop reason = signal SIGSTOP * frame #0: 0x000103588007 libpython2.7.dylib`vgetargskeywords + 23 frame #1: 0x00010358890e libpython2.7.dylib`PyArg_ParseTupleAndKeywords + 174 frame #2: 0x00010356c40e libpython2.7.dylib`builtin___ import__ + 94 frame #3: 0x0001034a377f libpython2.7.dylib`PyObject_CallFunctionObjArgs + 367 frame #4: 0x00010774c1c4 coerce.so`__Pyx_Import(name= unavailable, from_list=0x000117da7560, level=unavailable) + 180 at coerce.c: 20339 frame #5: 0x00010774d08e coerce.so`__pyx_f_4sage_9structure_6coerce_py_scalar_ parent(__pyx_v_py_type=unavailable, __pyx_skip_dispatch= unavailable) + 510 at coerce.c:2938 frame #6: 0x000107760318 coerce.so`__pyx_f_4sage_9structure_6coerce_24CoercionModel_cache_maps_ canonical_coercion(__pyx_v_self=0x0001 07648d50, __pyx_v_x=0x7f8fbfc37238, __pyx_v_y=0x000118c5f390, __pyx_skip_dispatch=unavailable) + 3128 at coerce.c:9585 frame #7: 0x000107763cfe coerce.so`__pyx_pw_4sage_9structure_6coerce_24CoercionModel_cache_maps_ 25canonical_coercion + 13 at coerce.c:105 64 frame #8: 0x000107763cf1 coerce.so`__pyx_pw_4sage_9structure_6coerce_24CoercionModel_cache_maps_ 25canonical_coercion(__pyx_v_self=0x0 00107648d50, __pyx_args=0x000117e5f248, __pyx_kwds=0x) + 65 frame #9: 0x000103574f10 libpython2.7.dylib`PyEval_EvalFrameEx + 26208 frame #10: 0x000103575fb0 libpython2.7.dylib`PyEval_EvalCodeEx + 2144 frame #11: 0x0001034dae0c libpython2.7.dylib`function_call + 124 frame #12: 0x00010d680381 pynac.so`__Pyx_PyObject_Call(func=0x000108f0c410, arg=unavailable, kw=PyObject * at scalar) + 65 at pynac .cpp:26785 frame #13: 0x00010d6a76e9 pynac.so`py_gcd(__pyx_v_n=0x7f8fbfc37238, __pyx_v_k=0x000118c5f390) + 521 at pynac.cpp:8416 frame #14: 0x00010d7d0f28 libpynac.1.dylib`GiNaC::gcd(GiNaC::numeric const, GiNaC::numeric const) + 56 frame #15: 0x00010d7ad100 libpynac.1.dylib`GiNaC::add::integer_content() const + 496 frame #16: 0x00010d7acef0 libpynac.1.dylib`GiNaC::ex::integer_content() const + 16 frame #17: 0x00010d79fe01 libpynac.1.dylib`GiNaC::mul:: eval(int) const + 1377 frame #18: 0x00010d71ba91 libpynac.1.dylib`GiNaC::ex::construct_from_basic(GiNaC::basic const) + 113 frame #19: 0x00010d7a026b libpynac.1.dylib`GiNaC::mul:: eval
Re: [sage-support] segfault when plotting gamma function
Ok, just did it. I'm not sure who to CC on this. Best Viviane 2015-04-15 14:12 GMT-04:00 Viviane Pons vivianep...@gmail.com: I'll do it, but I was hopping to get more context about it, also checking if it wasn't known somewhere. 2015-04-15 14:09 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com: Do you know how to open a ticket? On 15/04/15 20:08, Viviane Pons wrote: More context about this: I'm here with Buck at PyCon and he said he actually had this line running a few years ago. I don't know anything about this stuff so it's difficult to track what's wrong now. But it's really bad, as you can see, it's not just a usual exception, it's actually crashing Sage... (also, this is on Sage 6.6 and I believe it was there before. Buck had the error on the previous version and updated it to see if was fixed on 6.6) Best Viviane 2015-04-15 14:04 GMT-04:00 Vincent Delecroix 20100.delecr...@gmail.com : Already the following fails sage: integrated = -(gamma(1/2*k, 1/2*R*k) - gamma(1/2*k))/gamma(1/2*k) sage: plot(integrated.subs(k=41), (R,0,6)) /home/vincent/bin/sage: line 134: 13683 Segmentation fault $SAGE_ROOT/src/bin/sage $@ On 15/04/15 18:55, Buck Evan wrote: I'm trying to plot a function involving the gamma function. It's this one: -(gamma(1/2*k, 1/2*R*k) - gamma(1/2*k))/gamma(1/2*k) If I try to plot the function with a k value any greater than 40, I get a segfault: sum( plot( integrated(k=k), (x, 0, 2.5), ymax=1.6, color=color, legend_label='k=%i' % k, figsize=6, aspect_ratio=1.0, ) for k, color in zip( [21, 22, 23, 26, 31, 41], ['blue', 'brown', 'red', 'green', 'black', 'yellow', 'orange'], ) ) /Users/buck/trees/mine/sage/sage: line 134: 12283 Segmentation fault: 11 $SAGE_ROOT/src/bin/sage $@ [I 12:15:10.735 NotebookApp] KernelRestarter: restarting kernel (1/5) This is extremely similar to the behavior I was getting with the pre-built 6.5 sage, so I think it's an old bug rather than a problem with my build. In 6.5 there was no output (I suspect the Segmentation Fault message was gobbled somehow), so I never tried to enable / debug a core dump in 6.5. Inspecting the 6.6 core dump, I see that it used 27528, mostly calling back and forth between two functions. Smells like stack overflow to me. (lldb) bt [27503/47384] * thread #1: tid = 0x, 0x000103588007 libpython2.7.dylib`vgetargskeywords + 23, stop reason = signal SIGSTOP * frame #0: 0x000103588007 libpython2.7.dylib`vgetargskeywords + 23 frame #1: 0x00010358890e libpython2.7.dylib`PyArg_ParseTupleAndKeywords + 174 frame #2: 0x00010356c40e libpython2.7.dylib`builtin___ import__ + 94 frame #3: 0x0001034a377f libpython2.7.dylib`PyObject_CallFunctionObjArgs + 367 frame #4: 0x00010774c1c4 coerce.so`__Pyx_Import(name= unavailable, from_list=0x000117da7560, level=unavailable) + 180 at coerce.c: 20339 frame #5: 0x00010774d08e coerce.so`__pyx_f_4sage_9structure_6coerce_py_scalar_ parent(__pyx_v_py_type=unavailable, __pyx_skip_dispatch= unavailable) + 510 at coerce.c:2938 frame #6: 0x000107760318 coerce.so`__pyx_f_4sage_9structure_6coerce_24CoercionModel_cache_maps_ canonical_coercion(__pyx_v_self=0x0001 07648d50, __pyx_v_x=0x7f8fbfc37238, __pyx_v_y=0x000118c5f390, __pyx_skip_dispatch=unavailable) + 3128 at coerce.c:9585 frame #7: 0x000107763cfe coerce.so`__pyx_pw_4sage_9structure_6coerce_ 24CoercionModel_cache_maps_ 25canonical_coercion + 13 at coerce.c:105 64 frame #8: 0x000107763cf1 coerce.so`__pyx_pw_4sage_9structure_6coerce_ 24CoercionModel_cache_maps_ 25canonical_coercion(__pyx_v_self=0x0 00107648d50, __pyx_args=0x000117e5f248, __pyx_kwds=0x) + 65 frame #9: 0x000103574f10 libpython2.7.dylib`PyEval_EvalFrameEx + 26208 frame #10: 0x000103575fb0 libpython2.7.dylib`PyEval_EvalCodeEx + 2144 frame #11: 0x0001034dae0c libpython2.7.dylib`function_call + 124 frame #12: 0x00010d680381 pynac.so`__Pyx_PyObject_Call(func=0x000108f0c410, arg=unavailable, kw=PyObject * at scalar) + 65 at pynac .cpp:26785 frame #13: 0x00010d6a76e9 pynac.so`py_gcd(__pyx_v_n=0x7f8fbfc37238, __pyx_v_k=0x000118c5f390) + 521 at pynac.cpp:8416 frame #14: 0x00010d7d0f28 libpynac.1.dylib`GiNaC::gcd(GiNaC::numeric const, GiNaC::numeric const) + 56 frame #15: 0x00010d7ad100 libpynac.1.dylib`GiNaC::add::integer_content() const + 496 frame #16: 0x00010d7acef0 libpynac.1.dylib`GiNaC::ex::integer_content() const + 16 frame #17: 0x00010d79fe01 libpynac.1.dylib`GiNaC::mul:: eval(int) const + 1377 frame #18: 0x00010d71ba91
Re: [sage-support] Re: left right subtrees
Hi,
do you specifically need to use a graph? Because there is a special object
for binary trees.
Anyway, here is the code for the labelled binary tree corresponding to what
you want:
sage: LBT = LabelledBinaryTree
sage: a = LBT([], label='a')
sage: b = LBT([], label='b')
sage: c = LBT([], label='c')
sage: d = LBT([], label='d')
sage: tree = LBT([LBT([a,b], '+'), LBT([c,d],'-')],'*')
sage: tree
*[+[a[., .], b[., .]], -[c[., .], d[., .]]]
sage: view(tree)
Sadly, there is no graph syntax like to create the tree. And in general,
labelled binary trees are not that well handled. But anyway, if you have
some specific use cases or suggestions, they could be implemented!
Best,
Viviane
2014-11-25 14:33 GMT+01:00 kcrisman kcris...@gmail.com:
Hi! I don't think this is necessarily a notebook question, so I'm
forwarding this to sage-support where it is morel likely to get some
responses. Good luck!
Hi,
I would like to get a left and right subtree from a vertice.
First i used Graph abd option layout. The graph don't respect the order
of suns.
g=DiGraph({*:[+,-],-:[d,c],+:[a,b]})
g.order(), g.size()
g.vertices()
g.edges()
g.show(layout='tree')
Does someone have an idea? How to plot the tree in order abd get right
and left subtrees?
Dominique
--
You received this message because you are subscribed to the Google Groups
sage-support group.
To unsubscribe from this group and stop receiving emails from it, send an
email to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
sage-support group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-support] Re: Trouble with easy_install
Thank's, indeed I went thought the all thing and now it works! 2013/7/17 P Purkayastha ppu...@gmail.com On 07/16/2013 05:35 PM, Viviane Pons wrote: Hi everyone, I have installed sage-5.11-beta3 and for some reason, I cannot use use easy_install anymore on the sage shell. It seems to be a problem with https. When I do sage -sh and then easy_install -U mysql-python (for example), I get this: Reading http://pypi.python.org/simple/**mysql-python/http://pypi.python.org/simple/mysql-python/ Download error: unknown url type: https -- Some packages may not be found! I don't remember if I had this error before. But I'm sure I was able to install this package with easy_install on previous sage versions. Did anyone have some similar issues? Thank's a lot Viviane Make sure you have support for SSL installed. The details are present in the SSL section of the README.txt file in the Sage directory. -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscribe@**googlegroups.comsage-support%2bunsubscr...@googlegroups.com . To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/**group/sage-supporthttp://groups.google.com/group/sage-support . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
[sage-support] Trouble with easy_install
Hi everyone, I have installed sage-5.11-beta3 and for some reason, I cannot use use easy_install anymore on the sage shell. It seems to be a problem with https. When I do sage -sh and then easy_install -U mysql-python (for example), I get this: Reading http://pypi.python.org/simple/mysql-python/ Download error: unknown url type: https -- Some packages may not be found! I don't remember if I had this error before. But I'm sure I was able to install this package with easy_install on previous sage versions. Did anyone have some similar issues? Thank's a lot Viviane -- You received this message because you are subscribed to the Google Groups sage-support group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
