[sage-support] Re: Possible error: isogeny classes
Hi John, Thanks a bunch for the pointed reply. Glad to hear we weren't missing something easy and thanks a bunch for filling the bug report! Best, Lance On Sunday, November 26, 2023 at 10:16:53 AM UTC-6 John Cremona wrote: > https://github.com/sagemath/sage/issues/36780 > > On Saturday, 25 November 2023 at 15:11:53 UTC John Cremona wrote: > >> Thanks for this report, which certainly indicates a bug. I will look >> into it as the code here was written by me. I note that the two curves >> have CM (by the order of index 5 and the maximal order in Q(sqrt(-3)) >> respectively), and the code to deal with isogenies is different in this >> case. The relevant function is isogeny_degrees_cm(), imported >> from sage.schemes.elliptic_curves.isogeny_class. And for some reason that >> function is not including the valid isogeny prime 5. >> >> If you do F.isogeny_class(reducible_primes=[3,5]) you get the same as for >> E (but you have to so that in a fresh Sage session becauses of caching of >> previously computed results). >> >> John Cremona >> >> On Friday, 24 November 2023 at 03:50:54 UTC hbetx9 wrote: >> >>> Hi, >>> >>> In some work on isogeny clases, my team ran across the following of two >>> elliptic curves which are isogenous but sage reports different isogeny >>> classes for them. Is there some technicalities (j = 0) leading to >>> incorrect output or is this something that we should flag a bug? >>> >>> sage: L5. = NumberField(x^2-5) >>> >>> sage: E = >>> EllipticCurve(L5,[287275052073119826051072\*r5-642366544675288047943680,-125329261653845158603060848774610944\*r5+280244748627855491701953075326484480]) >>> >>> sage: F = EllipticCurve(L5,[0,-4325477943600\*r5-4195572876000]) >>> >>> sage: E.isogeny_class().matrix() >>> [ 1 25 75 3 5 15] >>> [25 1 3 75 5 15] >>> [75 3 1 25 15 5] >>> [ 3 75 25 1 15 5] >>> [ 5 5 15 15 1 3] >>> [15 15 5 5 3 1] >>> >>> sage: F.isogeny_class().matrix() >>> [1 3] >>> [3 1] >>> >>> sage: E.is_isogenous(F) >>> True >>> >>> Best, >>> Lance >>> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/a9f5672f-407e-4a51-8ee4-fbb5ddad3c35n%40googlegroups.com.
[sage-support] Possible error: isogeny classes
Hi, In some work on isogeny clases, my team ran across the following of two elliptic curves which are isogenous but sage reports different isogeny classes for them. Is there some technicalities (j = 0) leading to incorrect output or is this something that we should flag a bug? sage: L5. = NumberField(x^2-5) sage: E = EllipticCurve(L5,[287275052073119826051072\*r5-642366544675288047943680,-125329261653845158603060848774610944\*r5+280244748627855491701953075326484480]) sage: F = EllipticCurve(L5,[0,-4325477943600\*r5-4195572876000]) sage: E.isogeny_class().matrix() [ 1 25 75 3 5 15] [25 1 3 75 5 15] [75 3 1 25 15 5] [ 3 75 25 1 15 5] [ 5 5 15 15 1 3] [15 15 5 5 3 1] sage: F.isogeny_class().matrix() [1 3] [3 1] sage: E.is_isogenous(F) True Best, Lance -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/a78bba45-9ec5-4df3-8233-b39920d8c28dn%40googlegroups.com.
Re: [sage-support] Sage Crash Report
I can ask this another way. I have the tarball, and I want to end up with a
system wide install. This is not build from source. What is the best way to
do this?
In the referenced instructions the modification is to SAGE_LOCAL and not
SAGE_ROOT. I'm confused as to the difference and effect.
On Wednesday, September 1, 2021 at 2:27:46 PM UTC-5 hbetx9 wrote:
> As the directory is in /opt and ownership is root.root, I can't run this
> as it gets permission denied when writing the log file.
>
> On Wednesday, September 1, 2021 at 2:08:56 PM UTC-5 Matthias Koeppe wrote:
>
>> See
>> https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source
>> point 4 ("./configure --prefix")
>>
>> On Wednesday, September 1, 2021 at 12:00:15 PM UTC-7 hbetx9 wrote:
>>
>>> So I got this working in my home directory but want the SageMath
>>> directory system wide. I moved it to /opt and changed ownership to
>>> root.root, however this causes now a disagreement with the SAGE_ROOT
>>> environment variable. Should I unpack the tarball as root there to install
>>> or is there an easy config/make that I can run on this directory to get it
>>> to work as a system wide install?
>>>
>>> On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:
>>>
>>>> On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote:
>>>>
>>>>> On my system, python2 and python3 is installed, but there is no
>>>>> generic python symlink. Does this need to be created for sage and if so
>>>>> should it be python3? In installed from tarball, so this is not an issue
>>>>> with the Ubuntu package.
>>>>
>>>>
>>>> The latest binary for Linux (https://www.sagemath.org/download.html)
>>>> is Sage 9.3. If you are using this binary tarball, you will have to make
>>>> sure that the symlink python->python3 exists; there is a package that
>>>> provides it. See also
>>>> https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries
>>>>
>>>> The latest version is Sage 9.4. Using the source tarball, there is no
>>>> need to do anything about python/python3. Just follow the instructions in
>>>> the README.
>>>>
>>>>
>>>>
>>>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-support/024ab17b-41e5-4643-a0a7-c7c435b6266en%40googlegroups.com.
Re: [sage-support] Sage Crash Report
As the directory is in /opt and ownership is root.root, I can't run this as
it gets permission denied when writing the log file.
On Wednesday, September 1, 2021 at 2:08:56 PM UTC-5 Matthias Koeppe wrote:
> See
> https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source
> point 4 ("./configure --prefix")
>
> On Wednesday, September 1, 2021 at 12:00:15 PM UTC-7 hbetx9 wrote:
>
>> So I got this working in my home directory but want the SageMath
>> directory system wide. I moved it to /opt and changed ownership to
>> root.root, however this causes now a disagreement with the SAGE_ROOT
>> environment variable. Should I unpack the tarball as root there to install
>> or is there an easy config/make that I can run on this directory to get it
>> to work as a system wide install?
>>
>> On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:
>>
>>> On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote:
>>>
>>>> On my system, python2 and python3 is installed, but there is no generic
>>>> python symlink. Does this need to be created for sage and if so should it
>>>> be python3? In installed from tarball, so this is not an issue with the
>>>> Ubuntu package.
>>>
>>>
>>> The latest binary for Linux (https://www.sagemath.org/download.html) is
>>> Sage 9.3. If you are using this binary tarball, you will have to make sure
>>> that the symlink python->python3 exists; there is a package that provides
>>> it. See also
>>> https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries
>>>
>>> The latest version is Sage 9.4. Using the source tarball, there is no
>>> need to do anything about python/python3. Just follow the instructions in
>>> the README.
>>>
>>>
>>>
>>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-support/3aec31b3-85a5-45f0-af52-1243a1b5b0afn%40googlegroups.com.
Re: [sage-support] Sage Crash Report
So I got this working in my home directory but want the SageMath directory system wide. I moved it to /opt and changed ownership to root.root, however this causes now a disagreement with the SAGE_ROOT environment variable. Should I unpack the tarball as root there to install or is there an easy config/make that I can run on this directory to get it to work as a system wide install? On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote: > On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote: > >> On my system, python2 and python3 is installed, but there is no generic >> python symlink. Does this need to be created for sage and if so should it >> be python3? In installed from tarball, so this is not an issue with the >> Ubuntu package. > > > The latest binary for Linux (https://www.sagemath.org/download.html) is > Sage 9.3. If you are using this binary tarball, you will have to make sure > that the symlink python->python3 exists; there is a package that provides > it. See also > https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries > > The latest version is Sage 9.4. Using the source tarball, there is no need > to do anything about python/python3. Just follow the instructions in the > README. > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/546ebc75-e04c-4587-be1d-760018dab54en%40googlegroups.com.
Re: [sage-support] Sage Crash Report
On my system, python2 and python3 is installed, but there is no generic
python symlink. Does this need to be created for sage and if so should it
be python3? In installed from tarball, so this is not an issue with the
Ubuntu package.
On Monday, August 30, 2021 at 9:13:49 AM UTC-5 hbetx9 wrote:
> I think the issue is a disagreement with python. The package installs fine
> on a clean machine. I know this isn't the wheelhouse, but how can I
> diagnose my python configuration for compatibility with sage. In
> particular, I have python 3.8.10 installed systemwide.
>
> On Sunday, August 29, 2021 at 4:49:52 PM UTC-5 hbetx9 wrote:
>
>> The package log has the following error:
>>
>> /usr/lib/python3/dist-packages/sage/combinat/root_system/branching_rules.py:1753:
>>
>> SyntaxWarning: "is not" with a literal. Did you mean "!="?
>> if len(stypes) is not 2:
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1159:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1168:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1175:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1182:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1189:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1196:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1203:
>> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
>> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>>
>> I think there is something about the way sage is trying to be installed
>> and python, but I'm unsure how to diagnose. Installing from source is an
>> option yes, but I fear it will have the same issue.
>> On Sunday, August 29, 2021 at 2:14:38 AM UTC-5 dim...@gmail.com wrote:
>>
>>> On Sat, Aug 28, 2021 at 10:57 PM Lance Edward Miller
>>> wrote:
>>> >
>>> > To whom it may concern,
>>> >
>>> > I'm installing sage from the synaptic package manager on Linux Mint
>>> 20.1. The package is for Sage 9.0, but the app does not run. Following is
>>> the crash report, any advice on how to best resolve (uninstall and install
>>> from source?) is appreciated:
>>>
>>> This has to be reported to Linux Mint - we don't do packaging for
>>> particular Linux distributions, and it looks like a packaging error,
>>> not anything we can help with.
>>> You can install Sage in several other ways:
>>> https://doc.sagemath.org/html/en/installation/index.html
>>>
>>> >
>>> >
>>> >
>>> ***
>>> >
>>> > IPython post-mortem report
>>> >
>>> > {'commit_hash': '',
>>> > 'commit_source': '(none found)',
>>> > 'default_encoding': 'utf-8',
>>> > 'ipython_path': '/usr/lib/python3/dist-packages/IPython',
>>> > 'ipython_version': '7.13.0',
>>> > 'os_name': 'posix',
>>> > 'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29',
>>> > 'sys_executable': '/usr/bin/python3',
>>> > 'sys_platform': 'linux',
>>> > 'sys_version': '3.8.10 (default, Jun 2 2021, 10:49:15) \n[GCC 9.4.0]'}
>>> >
>>> >
>>> ***
>>> >
>>> >
>>> >
>>> >
>>> ***
>>> >
>>> > Crash traceback:
>>> >
>>> >
>>> -
Re: [sage-support] Sage Crash Report
I think the issue is a disagreement with python. The package installs fine
on a clean machine. I know this isn't the wheelhouse, but how can I
diagnose my python configuration for compatibility with sage. In
particular, I have python 3.8.10 installed systemwide.
On Sunday, August 29, 2021 at 4:49:52 PM UTC-5 hbetx9 wrote:
> The package log has the following error:
>
> /usr/lib/python3/dist-packages/sage/combinat/root_system/branching_rules.py:1753:
>
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> if len(stypes) is not 2:
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1159:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1168:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1175:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1182:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1189:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1196:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
> /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1203:
> SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
> raise TypeError('%s option must be a dictionary, not %s' (name, value))
>
> I think there is something about the way sage is trying to be installed
> and python, but I'm unsure how to diagnose. Installing from source is an
> option yes, but I fear it will have the same issue.
> On Sunday, August 29, 2021 at 2:14:38 AM UTC-5 dim...@gmail.com wrote:
>
>> On Sat, Aug 28, 2021 at 10:57 PM Lance Edward Miller
>> wrote:
>> >
>> > To whom it may concern,
>> >
>> > I'm installing sage from the synaptic package manager on Linux Mint
>> 20.1. The package is for Sage 9.0, but the app does not run. Following is
>> the crash report, any advice on how to best resolve (uninstall and install
>> from source?) is appreciated:
>>
>> This has to be reported to Linux Mint - we don't do packaging for
>> particular Linux distributions, and it looks like a packaging error,
>> not anything we can help with.
>> You can install Sage in several other ways:
>> https://doc.sagemath.org/html/en/installation/index.html
>>
>> >
>> >
>> >
>> ***
>> >
>> > IPython post-mortem report
>> >
>> > {'commit_hash': '',
>> > 'commit_source': '(none found)',
>> > 'default_encoding': 'utf-8',
>> > 'ipython_path': '/usr/lib/python3/dist-packages/IPython',
>> > 'ipython_version': '7.13.0',
>> > 'os_name': 'posix',
>> > 'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29',
>> > 'sys_executable': '/usr/bin/python3',
>> > 'sys_platform': 'linux',
>> > 'sys_version': '3.8.10 (default, Jun 2 2021, 10:49:15) \n[GCC 9.4.0]'}
>> >
>> >
>> ***
>> >
>> >
>> >
>> >
>> ***
>> >
>> > Crash traceback:
>> >
>> >
>> ---
>> >
>> ---
>> > ImportError Python 3.8.10: /usr/bin/python3
>> > Sat Aug 28 16:48:31 2021
>> > A problem occurred executing Python code. Here is the sequence of
>> function
>> > calls leading up to the error, with the most recent (innermost) call
>> last.
>> > /usr/share/sagemath/bin/sage-ipython in
>> > 1 #!/usr/bin/env sage-python
>> > 2 # -*- coding: utf-8 -*-
>> > 3
Re: [sage-support] Sage Crash Report
The package log has the following error:
/usr/lib/python3/dist-packages/sage/combinat/root_system/branching_rules.py:1753:
SyntaxWarning: "is not" with a literal. Did you mean "!="?
if len(stypes) is not 2:
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1159:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1168:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1175:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1182:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1189:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1196:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
/usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1203:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise TypeError('%s option must be a dictionary, not %s' (name, value))
I think there is something about the way sage is trying to be installed and
python, but I'm unsure how to diagnose. Installing from source is an option
yes, but I fear it will have the same issue.
On Sunday, August 29, 2021 at 2:14:38 AM UTC-5 dim...@gmail.com wrote:
> On Sat, Aug 28, 2021 at 10:57 PM Lance Edward Miller
> wrote:
> >
> > To whom it may concern,
> >
> > I'm installing sage from the synaptic package manager on Linux Mint
> 20.1. The package is for Sage 9.0, but the app does not run. Following is
> the crash report, any advice on how to best resolve (uninstall and install
> from source?) is appreciated:
>
> This has to be reported to Linux Mint - we don't do packaging for
> particular Linux distributions, and it looks like a packaging error,
> not anything we can help with.
> You can install Sage in several other ways:
> https://doc.sagemath.org/html/en/installation/index.html
>
> >
> >
> >
> ***
> >
> > IPython post-mortem report
> >
> > {'commit_hash': '',
> > 'commit_source': '(none found)',
> > 'default_encoding': 'utf-8',
> > 'ipython_path': '/usr/lib/python3/dist-packages/IPython',
> > 'ipython_version': '7.13.0',
> > 'os_name': 'posix',
> > 'platform': 'Linux-5.4.0-81-generic-x86_64-with-glibc2.29',
> > 'sys_executable': '/usr/bin/python3',
> > 'sys_platform': 'linux',
> > 'sys_version': '3.8.10 (default, Jun 2 2021, 10:49:15) \n[GCC 9.4.0]'}
> >
> >
> ***
> >
> >
> >
> >
> ***
> >
> > Crash traceback:
> >
> >
> ---
> >
> ---
> > ImportError Python 3.8.10: /usr/bin/python3
> > Sat Aug 28 16:48:31 2021
> > A problem occurred executing Python code. Here is the sequence of
> function
> > calls leading up to the error, with the most recent (innermost) call
> last.
> > /usr/share/sagemath/bin/sage-ipython in
> > 1 #!/usr/bin/env sage-python
> > 2 # -*- coding: utf-8 -*-
> > 3 """
> > 4 Sage IPython startup script.
> > 5 """
> > 6
> > 7 # Display startup banner. Do this before anything else to give the user
> > 8 # early feedback that Sage is starting.
> > 9 from sage.misc.banner import banner
> > 10 banner()
> > 11
> > 12 from sage.repl.interpreter import SageTerminalApp
> > 13
> > 14 app = SageTerminalApp.instance()
> > ---> 15 app.initialize()
> > global app.initialize = >
> > 16 app.start()
> >
> > in
> initialize(self=, argv=None)
> >
> > /usr/lib/python3/dist-packages/traitlets/config/application.py in
> catch_config_error(method=,
> app=, *args=(None,),
> **kwargs={})
> > 72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
> > 73 else:
> > 74 raise ValueError("Unsupported value for environment variable:
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is
> none of {'0', '1', 'false', 'true', ''}."% _envvar )
> > 75
> > 76
> > 77 @decorator
> > 78 def catch_config_error(method, app, *args, **kwargs):
> > 79 """Method decorator for catching invalid config
> (Trait/ArgumentErrors) during init.
> > 80
> > 81 On a
Re: [sage-support] Sage Crash report
I didn't see that option, will use in future, thanks! On Thursday, April 9, 2020 at 2:56:23 PM UTC-5, John H Palmieri wrote: > > Did you look at the file "README.md"? It suggests building in parallel to > speed things up. Have you tried that? > > > On Thursday, April 9, 2020 at 12:35:58 PM UTC-7, hbetx9 wrote: >> >> I htink I know what I did, somehow I change the prefix to a directory >> that didn't exist. I'm recompiling to see if the error is fixed. >> >> Boy does this compile take a LONG time, is that the same for everyone? >> >> >> >> On Thursday, April 9, 2020 at 2:26:48 PM UTC-5, hbetx9 wrote: >>> >>> Okay, I did something apparently odd. >>> >>> For context, I first unpacked in a directory, ran make (took a long >>> time) and would close with an error concerning R as above. Sage would work >>> on command line by running the copy in this directory. However, something I >>> did broke this install, and I'm wondering if I should just erase and start >>> over. >>> >>> Now make finishes with >>> >>> Makefile:31: recipe for target 'base-toolchain' failed >>> make: *** [base-toolchain] Error 1 >>> >>> and when running I get only the following message >>> >>> >>> It seems that you are attempting to run Sage from an unpacked source >>> tarball, but you have not compiled it yet (or maybe the build has not >>> finished). You should run `make` in the Sage root directory first. >>> If you did not intend to build Sage from source, you should download >>> a binary tarball instead. Read README.txt for more information. >>> **** >>> >>> Should I just start over or is there an easy way to repair this issue? >>> >>> On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote: >>>> >>>> On Wednesday, April 8, 2020 at 8:01:38 PM UTC-7, hbetx9 wrote: >>>>> >>>>> No, I just want all users to have this at default. Where should I put >>>>> the SAGE_ROOT directory? /usr/local? >>>>> >>>> >>>> Use "./configure --prefix=/usr/local/opt/sage-9.0" to set the >>>> installation prefix (SAGE_LOCAL). >>>> >>>> >>>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/ec967a81-8172-4ea1-a17e-c7ce16c4ddde%40googlegroups.com.
Re: [sage-support] Sage Crash report
I htink I know what I did, somehow I change the prefix to a directory that didn't exist. I'm recompiling to see if the error is fixed. Boy does this compile take a LONG time, is that the same for everyone? On Thursday, April 9, 2020 at 2:26:48 PM UTC-5, hbetx9 wrote: > > Okay, I did something apparently odd. > > For context, I first unpacked in a directory, ran make (took a long time) > and would close with an error concerning R as above. Sage would work on > command line by running the copy in this directory. However, something I > did broke this install, and I'm wondering if I should just erase and start > over. > > Now make finishes with > > Makefile:31: recipe for target 'base-toolchain' failed > make: *** [base-toolchain] Error 1 > > and when running I get only the following message > > > It seems that you are attempting to run Sage from an unpacked source > tarball, but you have not compiled it yet (or maybe the build has not > finished). You should run `make` in the Sage root directory first. > If you did not intend to build Sage from source, you should download > a binary tarball instead. Read README.txt for more information. > > > Should I just start over or is there an easy way to repair this issue? > > On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote: >> >> On Wednesday, April 8, 2020 at 8:01:38 PM UTC-7, hbetx9 wrote: >>> >>> No, I just want all users to have this at default. Where should I put >>> the SAGE_ROOT directory? /usr/local? >>> >> >> Use "./configure --prefix=/usr/local/opt/sage-9.0" to set the >> installation prefix (SAGE_LOCAL). >> >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/0b78b6ed-3fcf-4820-8bef-8ee59e5a99ab%40googlegroups.com.
Re: [sage-support] Sage Crash report
Okay, I did something apparently odd. For context, I first unpacked in a directory, ran make (took a long time) and would close with an error concerning R as above. Sage would work on command line by running the copy in this directory. However, something I did broke this install, and I'm wondering if I should just erase and start over. Now make finishes with Makefile:31: recipe for target 'base-toolchain' failed make: *** [base-toolchain] Error 1 and when running I get only the following message It seems that you are attempting to run Sage from an unpacked source tarball, but you have not compiled it yet (or maybe the build has not finished). You should run `make` in the Sage root directory first. If you did not intend to build Sage from source, you should download a binary tarball instead. Read README.txt for more information. Should I just start over or is there an easy way to repair this issue? On Wednesday, April 8, 2020 at 11:12:19 PM UTC-5, Matthias Koeppe wrote: > > On Wednesday, April 8, 2020 at 8:01:38 PM UTC-7, hbetx9 wrote: >> >> No, I just want all users to have this at default. Where should I put the >> SAGE_ROOT directory? /usr/local? >> > > Use "./configure --prefix=/usr/local/opt/sage-9.0" to set the installation > prefix (SAGE_LOCAL). > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/211879d7-0157-432f-b390-68658853cc5e%40googlegroups.com.
Re: [sage-support] Sage Crash report
No, I just want all users to have this at default. Where should I put the SAGE_ROOT directory? /usr/local? On Wednesday, April 8, 2020 at 9:36:33 PM UTC-5, Dima Pasechnik wrote: > > On Thu, Apr 9, 2020 at 10:30 AM hbetx9 > > wrote: > > > > Hi Matthias, > > > > Boy what a mess this is. I didn't realize the rabbit hole went down that > far. Do you think I could skip this and after upgrading sage later stable > versions (I see you and others are working on it), this can be resolved? > > > > If I don't resolve this now, then sage works but I'd like to globalize > this install. Its likely a basic question but what is the best way to do > this? > > "globalize" seems to be something from JavaScript world. Do you mean > multi-language support? > > > > > On Wednesday, April 8, 2020 at 6:11:33 PM UTC-5, Matthias Koeppe wrote: > >> > >> Read https://doc.sagemath.org/html/en/developer/ if you wish to make > changes to Sage, and https://trac.sagemath.org/ticket/29379 for the > change ticket that makes the upgrade to R 3.6.3 > >> > >> > >> On Wednesday, April 8, 2020 at 3:02:01 PM UTC-7, hbetx9 wrote: > >>> > >>> I _almost_ got this to work, I have R 3.6.3 but still get the > following error: > >>> > >>> * package: r-3.6.2 > >>> log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log > >>> build directory: > /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2 > >>> > >>> Presumably, there is a flag or configure I can send make to use 3.6.3 > correct? > >>> > >>> > >>> After all this is addressed, how to make this available system wide? > Is there a script in the SAGE_LOCAL that will do it? I know that's a basic > question but I'm curious. I removed Sage 8 so there should be no conflict. > > > > -- > > 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-s...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-support/5fb29a7d-db79-4f13-83bf-4a7b3a904961%40googlegroups.com. > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/912f231f-d2e2-4af6-897f-57da5c27503b%40googlegroups.com.
Re: [sage-support] Sage Crash report
Hi Matthias, Boy what a mess this is. I didn't realize the rabbit hole went down that far. Do you think I could skip this and after upgrading sage later stable versions (I see you and others are working on it), this can be resolved? If I don't resolve this now, then sage works but I'd like to globalize this install. Its likely a basic question but what is the best way to do this? On Wednesday, April 8, 2020 at 6:11:33 PM UTC-5, Matthias Koeppe wrote: > > Read https://doc.sagemath.org/html/en/developer/ if you wish to make > changes to Sage, and https://trac.sagemath.org/ticket/29379 for the > change ticket that makes the upgrade to R 3.6.3 > > > On Wednesday, April 8, 2020 at 3:02:01 PM UTC-7, hbetx9 wrote: >> >> I _almost_ got this to work, I have R 3.6.3 but still get the following >> error: >> >> * package: r-3.6.2 >> log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log >> build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2 >> >> Presumably, there is a flag or configure I can send make to use 3.6.3 >> correct? >> >> >> After all this is addressed, how to make this available system wide? Is >> there a script in the SAGE_LOCAL that will do it? I know that's a basic >> question but I'm curious. I removed Sage 8 so there should be no conflict. >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/5fb29a7d-db79-4f13-83bf-4a7b3a904961%40googlegroups.com.
Re: [sage-support] Sage Crash report
I _almost_ got this to work, I have R 3.6.3 but still get the following
error:
* package: r-3.6.2
log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log
build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
Presumably, there is a flag or configure I can send make to use 3.6.3
correct?
After all this is addressed, how to make this available system wide? Is
there a script in the SAGE_LOCAL that will do it? I know that's a basic
question but I'm curious. I removed Sage 8 so there should be no conflict.
On Wednesday, April 8, 2020 at 12:56:29 PM UTC-5, hbetx9 wrote:
>
> On second thought, I should just fix this now.
>
> Am I correct I need to install package r-3.6.2 and rebuld?
>
> On Wednesday, April 8, 2020 at 11:54:39 AM UTC-5, hbetx9 wrote:
>>
>> Tried from source and got this error:
>>
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: r-3.6.2
>> log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log
>> build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
>>
>> which I'm guessing is only needed if one wants to use integration with R.
>> At this time I don't but in future I might, should I install R and
>> rebuild? Build took a LONG time.
>>
>> Also, version 9 is now in ~/SAGE_ROOT/local but the system version is
>> still 8.1. I guess I need to modify path or create a symlink to get sage
>> available to terminal on boot?
>>
>> Finally, can the color scheme for sage on the terminal be changed? I used
>> a dark background so this is not easy to read.
>>
>> Thanks in advance!
>>
>> On Wednesday, April 8, 2020 at 12:14:48 AM UTC-5, Dima Pasechnik wrote:
>>>
>>> On Wed, Apr 8, 2020 at 11:05 AM hbetx9 wrote:
>>>
>>> > I installed from package on Mint 19.3. I'm happy to run whatever
>>> is needed to help diagnose. For context, I have installed python 2.7.17 and
>>> the package pulled sage 8.1. I'm not sure why the packages didn't pull the
>>> most up to date. Is there a PPA I need to add?
>>> >
>>>
>>> my understanding is that MInt 19 by default follows Ubunu 18.04 (which
>>> indeed has Sage 8.1).
>>> We'd recommend you to build Sage (say, the latest stable version, 9.0)
>>> from source instead.
>>> While latest Ubuntu does have Sage 9.0, I don't know how to get it
>>> installed on your Mint, from PPA or otherwise.
>>> Perhaps you can ask on a Mint forum.
>>>
>>> HTH
>>> Dima
>>>
>>>
>>> > Best,
>>> > Lance
>>> >
>>> > On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote:
>>> >>
>>> >> On Sun, Apr 5, 2020 at 7:44 AM Lance Edward Miller
>>> wrote:
>>> >> >
>>> >> > After install on Linux Mint 19.3, I got the following crash report.
>>> Any help is appreciated.
>>> >>
>>> >> What exactly have you installed?
>>> >> A binary installation, or done a build from sources?
>>> >>
>>> >> >
>>> >> >
>>> ***
>>> >> >
>>> >> > IPython post-mortem report
>>> >> >
>>> >> > {'commit_hash': u'b467d487e',
>>> >> > 'commit_source': 'installation',
>>> >> > 'default_encoding': 'UTF-8',
>>> >> > 'ipython_path': '/usr/lib/python2.7/dist-packages/IPython',
>>> >> > 'ipython_version': '5.5.0',
>>> >> > 'os_name': 'posix',
>>> >> > 'platform':
>>> 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia',
>>> >> > 'sys_executable': '/usr/bin/python',
>>> >> > 'sys_platform': 'linux2',
>>> >> > 'sys_version': '2.7.17 (default, Nov 7 2019, 10:07:09) \n[GCC
>>> 7.4.0]'}
>>> >> >
>>> >> >
>>> ***
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> ***
>>> >> >
>>> >> > Crash traceback:
>>> >> >
>>> >> >
>>> --
Re: [sage-support] Sage Crash report
On second thought, I should just fix this now.
Am I correct I need to install package r-3.6.2 and rebuld?
On Wednesday, April 8, 2020 at 11:54:39 AM UTC-5, hbetx9 wrote:
>
> Tried from source and got this error:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: r-3.6.2
> log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log
> build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
>
> which I'm guessing is only needed if one wants to use integration with R.
> At this time I don't but in future I might, should I install R and
> rebuild? Build took a LONG time.
>
> Also, version 9 is now in ~/SAGE_ROOT/local but the system version is
> still 8.1. I guess I need to modify path or create a symlink to get sage
> available to terminal on boot?
>
> Finally, can the color scheme for sage on the terminal be changed? I used
> a dark background so this is not easy to read.
>
> Thanks in advance!
>
> On Wednesday, April 8, 2020 at 12:14:48 AM UTC-5, Dima Pasechnik wrote:
>>
>> On Wed, Apr 8, 2020 at 11:05 AM hbetx9 wrote:
>>
>> > I installed from package on Mint 19.3. I'm happy to run whatever is
>> needed to help diagnose. For context, I have installed python 2.7.17 and
>> the package pulled sage 8.1. I'm not sure why the packages didn't pull the
>> most up to date. Is there a PPA I need to add?
>> >
>>
>> my understanding is that MInt 19 by default follows Ubunu 18.04 (which
>> indeed has Sage 8.1).
>> We'd recommend you to build Sage (say, the latest stable version, 9.0)
>> from source instead.
>> While latest Ubuntu does have Sage 9.0, I don't know how to get it
>> installed on your Mint, from PPA or otherwise.
>> Perhaps you can ask on a Mint forum.
>>
>> HTH
>> Dima
>>
>>
>> > Best,
>> > Lance
>> >
>> > On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote:
>> >>
>> >> On Sun, Apr 5, 2020 at 7:44 AM Lance Edward Miller
>> wrote:
>> >> >
>> >> > After install on Linux Mint 19.3, I got the following crash report.
>> Any help is appreciated.
>> >>
>> >> What exactly have you installed?
>> >> A binary installation, or done a build from sources?
>> >>
>> >> >
>> >> >
>> ***
>> >> >
>> >> > IPython post-mortem report
>> >> >
>> >> > {'commit_hash': u'b467d487e',
>> >> > 'commit_source': 'installation',
>> >> > 'default_encoding': 'UTF-8',
>> >> > 'ipython_path': '/usr/lib/python2.7/dist-packages/IPython',
>> >> > 'ipython_version': '5.5.0',
>> >> > 'os_name': 'posix',
>> >> > 'platform':
>> 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia',
>> >> > 'sys_executable': '/usr/bin/python',
>> >> > 'sys_platform': 'linux2',
>> >> > 'sys_version': '2.7.17 (default, Nov 7 2019, 10:07:09) \n[GCC
>> 7.4.0]'}
>> >> >
>> >> >
>> ***
>> >> >
>> >> >
>> >> >
>> >> >
>> ***
>> >> >
>> >> > Crash traceback:
>> >> >
>> >> >
>> ---
>> >> >
>> ---
>> >> > ImportError Python 2.7.17:
>> /usr/bin/python
>> >> >Sat Apr 4
>> 18:39:09 2020
>> >> > A problem occurred executing Python code. Here is the sequence of
>> function
>> >> > calls leading up to the error, with the most recent (innermost) call
>> last.
>> >> > /usr/share/sagemath/bin/sage-ipython in ()
>> >> > 1 #!/usr/bin/env python
>> >> > 2 # -*- coding: utf-8 -*-
>> >> > 3 """
>> >> > 4 Sage IPython startup script.
>> >> > 5 """
>> >> > 6
>> >> >
Re: [sage-support] Sage Crash report
Thanks, I'll have to make that adjustment, at the moment I have two versions of sage, so I need to figure out how to make it just version 9 first. Otherwise my home .sage directory won't drive behavior of the things in SAGE_ROOT/local correct? On Wednesday, April 8, 2020 at 12:15:53 PM UTC-5, slelievre wrote: > > > can the color scheme for sage on the terminal be changed? > > I used a dark background so this is not easy to read. > > > If using the Sage REPL on a dark background, > run the command > > sage: %colors Linux > > You can also include that command in a file > called `init.sage` file, located in the `.sage` > folder in hour home, so that it will be run > each time you start Sage. > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/3cb9f550-e43f-4d40-9975-14324daf0693%40googlegroups.com.
Re: [sage-support] Sage Crash report
Tried from source and got this error:
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):
* package: r-3.6.2
log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log
build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
which I'm guessing is only needed if one wants to use integration with R.
At this time I don't but in future I might, should I install R and
rebuild? Build took a LONG time.
Also, version 9 is now in ~/SAGE_ROOT/local but the system version is still
8.1. I guess I need to modify path or create a symlink to get sage
available to terminal on boot?
Finally, can the color scheme for sage on the terminal be changed? I used a
dark background so this is not easy to read.
Thanks in advance!
On Wednesday, April 8, 2020 at 12:14:48 AM UTC-5, Dima Pasechnik wrote:
>
> On Wed, Apr 8, 2020 at 11:05 AM hbetx9 >
> wrote:
>
> > I installed from package on Mint 19.3. I'm happy to run whatever is
> needed to help diagnose. For context, I have installed python 2.7.17 and
> the package pulled sage 8.1. I'm not sure why the packages didn't pull the
> most up to date. Is there a PPA I need to add?
> >
>
> my understanding is that MInt 19 by default follows Ubunu 18.04 (which
> indeed has Sage 8.1).
> We'd recommend you to build Sage (say, the latest stable version, 9.0)
> from source instead.
> While latest Ubuntu does have Sage 9.0, I don't know how to get it
> installed on your Mint, from PPA or otherwise.
> Perhaps you can ask on a Mint forum.
>
> HTH
> Dima
>
>
> > Best,
> > Lance
> >
> > On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote:
> >>
> >> On Sun, Apr 5, 2020 at 7:44 AM Lance Edward Miller
> wrote:
> >> >
> >> > After install on Linux Mint 19.3, I got the following crash report.
> Any help is appreciated.
> >>
> >> What exactly have you installed?
> >> A binary installation, or done a build from sources?
> >>
> >> >
> >> >
> ***
> >> >
> >> > IPython post-mortem report
> >> >
> >> > {'commit_hash': u'b467d487e',
> >> > 'commit_source': 'installation',
> >> > 'default_encoding': 'UTF-8',
> >> > 'ipython_path': '/usr/lib/python2.7/dist-packages/IPython',
> >> > 'ipython_version': '5.5.0',
> >> > 'os_name': 'posix',
> >> > 'platform':
> 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia',
> >> > 'sys_executable': '/usr/bin/python',
> >> > 'sys_platform': 'linux2',
> >> > 'sys_version': '2.7.17 (default, Nov 7 2019, 10:07:09) \n[GCC
> 7.4.0]'}
> >> >
> >> >
> ***
> >> >
> >> >
> >> >
> >> >
> ***
> >> >
> >> > Crash traceback:
> >> >
> >> >
> ---
> >> >
> ---
> >> > ImportError Python 2.7.17:
> /usr/bin/python
> >> >Sat Apr 4
> 18:39:09 2020
> >> > A problem occurred executing Python code. Here is the sequence of
> function
> >> > calls leading up to the error, with the most recent (innermost) call
> last.
> >> > /usr/share/sagemath/bin/sage-ipython in ()
> >> > 1 #!/usr/bin/env python
> >> > 2 # -*- coding: utf-8 -*-
> >> > 3 """
> >> > 4 Sage IPython startup script.
> >> > 5 """
> >> > 6
> >> > 7 from sage.repl.interpreter import SageTerminalApp
> >> > 8
> >> > 9 app = SageTerminalApp.instance()
> >> > ---> 10 app.initialize()
> >> > global app.initialize = SageTerminalApp.initialize of at 0x7f76836e7150>>
> >> > 11 app.start()
> >> >
> >> > in
> initialize(self=, argv=None)
> >> >
> >> > /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in
> catch_config_error(method=,
> app=, *args=(None,),
> **kwargs={})
> &
Re: [sage-support] Sage Crash report
Hi Dima.
I installed from package on Mint 19.3. I'm happy to run whatever is
needed to help diagnose. For context, I have installed python 2.7.17 and
the package pulled sage 8.1. I'm not sure why the packages didn't pull the
most up to date. Is there a PPA I need to add?
Best,
Lance
On Saturday, April 4, 2020 at 9:49:09 PM UTC-5, Dima Pasechnik wrote:
>
> On Sun, Apr 5, 2020 at 7:44 AM Lance Edward Miller > wrote:
> >
> > After install on Linux Mint 19.3, I got the following crash report. Any
> help is appreciated.
>
> What exactly have you installed?
> A binary installation, or done a build from sources?
>
> >
> >
> ***
> >
> > IPython post-mortem report
> >
> > {'commit_hash': u'b467d487e',
> > 'commit_source': 'installation',
> > 'default_encoding': 'UTF-8',
> > 'ipython_path': '/usr/lib/python2.7/dist-packages/IPython',
> > 'ipython_version': '5.5.0',
> > 'os_name': 'posix',
> > 'platform': 'Linux-5.3.0-40-generic-x86_64-with-LinuxMint-19.3-tricia',
> > 'sys_executable': '/usr/bin/python',
> > 'sys_platform': 'linux2',
> > 'sys_version': '2.7.17 (default, Nov 7 2019, 10:07:09) \n[GCC 7.4.0]'}
> >
> >
> ***
> >
> >
> >
> >
> ***
> >
> > Crash traceback:
> >
> >
> ---
> >
> ---
> > ImportError Python 2.7.17:
> /usr/bin/python
> >Sat Apr 4 18:39:09
> 2020
> > A problem occurred executing Python code. Here is the sequence of
> function
> > calls leading up to the error, with the most recent (innermost) call
> last.
> > /usr/share/sagemath/bin/sage-ipython in ()
> > 1 #!/usr/bin/env python
> > 2 # -*- coding: utf-8 -*-
> > 3 """
> > 4 Sage IPython startup script.
> > 5 """
> > 6
> > 7 from sage.repl.interpreter import SageTerminalApp
> > 8
> > 9 app = SageTerminalApp.instance()
> > ---> 10 app.initialize()
> > global app.initialize = of >
> > 11 app.start()
> >
> > in
> initialize(self=, argv=None)
> >
> > /usr/lib/python2.7/dist-packages/traitlets/config/application.pyc in
> catch_config_error(method=,
> app=, *args=(None,),
> **kwargs={})
> > 72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
> > 73 else:
> > 74 raise ValueError("Unsupported value for environment
> variable: 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s'
> which is none of {'0', '1', 'false', 'true', ''}."% _envvar )
> > 75
> > 76
> > 77 @decorator
> > 78 def catch_config_error(method, app, *args, **kwargs):
> > 79 """Method decorator for catching invalid config
> (Trait/ArgumentErrors) during init.
> > 80
> > 81 On a TraitError (generally caused by bad config), this will
> print the trait's
> > 82 message, and exit the app.
> > 83
> > 84 For use on init methods, to prevent invoking excepthook on
> invalid input.
> > 85 """
> > 86 try:
> > ---> 87 return method(app, *args, **kwargs)
> > method =
> > app = 0x7f76836e7150>
> > args = (None,)
> > kwargs = {}
> > 88 except (TraitError, ArgumentError) as e:
> > 89 app.print_help()
> > 90 app.log.fatal("Bad config encountered during
> initialization:")
> > 91 app.log.fatal(str(e))
> > 92 app.log.debug("Config at the time: %s", app.config)
> > 93 app.exit(1)
> > 94
> > 95
> > 96 class ApplicationError(Exception):
> > 97 pass
> > 98
> > 99
> > 100 class LevelFormatter(logging.Formatter):
> > 101 """Formatter with additional `highlevel` record
> > 102
> >
> > /usr/lib/python2.7/dist-packages/IPython/terminal/ipapp.pyc in
> initialize(self=, argv=None)
> > 301
> > 302 return super(TerminalIPythonApp,
> self).parse_command_line(argv)
> > 303
> > 304 @catch_config_error
> > 305 def initialize(self, argv=None):
> > 306 """Do actions after construct, but before starting the
> app."""
> > 307 super(TerminalIPythonApp, self).initialize(argv)
> > 308 if self.subapp is not None:
> > 309 # don't bother initializing further, starting subapp
> > 310 return
> > 311 # print self.extra_args
> > 312 if self.extra_args and not self.something_to_run:
> > 313 self.file_to_run = self.extra_args[0]
> > 314 self.init_path()
[sage-support] symbolic lists
Hi Sage Community, After reviewing this oustanding piece of software, I would like to utilize it to solve some problems I've been working on. However I have one question that the documentation has not provided a solution for. Is there a way have symbolic lists or lists of symbolic variables? Our would I have to construct a new class for this? Best, Lance --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
