Starting subshell with Sage environment variables set. Don't forget to exit when you are done. Beware: * Do not do anything with other copies of Sage on your system. * Do not use this for installing Sage packages using "sage -i" or for running "make" at Sage's root directory. These should be done outside the Sage shell.
Bypassing shell configuration files... Note: SAGE_ROOT=/opt/sagemath-8.6 (sage-sh) oth@N122:~$ -python bash: -python: Kommando nicht gefunden. (sage-sh) oth@N122:~$ sage -python Python 2.7.15 (default, Jan 23 2019, 14:07:15) [GCC 7.4.0] on cygwin Type "help", "copyright", "credits" or "license" for more information. >>> Am Di., 23. Apr. 2019 um 08:55 Uhr schrieb Oliver Thiel < [email protected]>: > Sorry, i just dont knew the command "exit", now it closes without problems > > Am Di., 23. Apr. 2019 um 08:53 Uhr schrieb Oliver Thiel < > [email protected]>: > >> It is absolutely possible that i run the sage shell twice. If i start the >> shell, this is what i get: >> >> Starting subshell with Sage environment variables set. Don't forget >> to exit when you are done. Beware: >> * Do not do anything with other copies of Sage on your system. >> * Do not use this for installing Sage packages using "sage -i" or for >> running "make" at Sage's root directory. These should be done >> outside the Sage shell. >> >> Bypassing shell configuration files... >> >> Note: SAGE_ROOT=/opt/sagemath-8.6 >> (sage-sh) oth@N122:~$ >> >> I want to give you everything you need but i dont know exactly what i >> have to do... >> >> Am Do., 18. Apr. 2019 um 17:47 Uhr schrieb E. Madison Bray < >> [email protected]>: >> >>> On Thursday, April 18, 2019 at 12:53:10 PM UTC+2, Oliver Thiel wrote: >>>> >>>> First of all, A was already defined and i realised later that i dont >>>> have to define k=0 too, but, unless i am not a experienced programmer, i >>>> dont think that the problem correlates with my code. >>>> >>> >>> No, it doesn't, rest assured. >>> >>> >>>> The company where i work uses a specific policy software and for the >>>> installation of sage i get a exclusive permission. >>>> >>>> If i type "sage -ipython" in "SageMath 8.6 Shell": >>>> NameError Traceback (most recent call >>>> last) >>>> <ipython-input-1-ac73f397e8f1> in <module>() >>>> ----> 1 sage -ipython >>>> >>>> NameError: name 'sage' is not defined >>>> >>> >>> Sorry, but this is not what I asked you to do, I don't think. The >>> installer should have installed 3 icons in your start menu and/or desktop. >>> The one labeled just "SageMath 8.6" directly launches the Sage command >>> prompt (you get a "sage:" prompt, whereas the one labeled "SageMath 8.6 >>> Shell" starts a UNIX-like bash prompt (containing your username, among >>> other things, and ending with "$"). >>> >>> The command `sage -ipython` is just a problem to start (`sage`) with an >>> argument flag (`-ipython`). In this case it starts the normal IPython >>> interpreter included with the Sage installation *without* loading the Sage >>> library itself. I asked you to do this in order to rule out whether the >>> problem is specific to Sage, or is some deeper problem in the underlying >>> software (since crashing just by typing characters into the console is >>> obviously not normal). >>> >>> You got an exception from *Python* because you tried to enter a shell >>> command (`sage -ipython`) into the *Python* interpreter prompt. If you ran >>> the "SageMath 8.6 Shell" link that should not have happened because you >>> would have gotten a bash prompt instead. Is it possible you accidentally >>> ran it twice in a row? If you ran it once it would have put you in the >>> IPython prompt anyways. >>> >>> I wanted to see if you could run some Python code (like the loop you >>> described above) in the plain IPython interpreter. The full Sage >>> interpreter just runs on IPython with some additional customizations. >>> >>> >>> >>>> After that i had to struggle with closing the shell :-D >>>> >>> >>> Typing `exit` should work. Could you explain more about what you >>> struggled with? >>> >>> >>> >>>> There is the standart windows defender and as far as i know it makes no >>>> updates right know. >>>> >>>> @E. Madisan Bray, what do you mean? Wich build tools? Could i update >>>> them without administration rights? >>>> >>> >>> This was a more general comment about why I haven't release Sage 8.7 for >>> Windows yet. If it doesn't mean anything to you then you can just ignore >>> it. >>> >>> >>> >>>> Am Donnerstag, 18. April 2019 11:29:58 UTC+2 schrieb E. Madison Bray: >>>> >>>>> On Thursday, April 18, 2019 at 11:09:02 AM UTC+2, E. Madison Bray >>>>> wrote: >>>>>> >>>>>> On Thursday, April 18, 2019 at 10:57:11 AM UTC+2, Dima Pasechnik >>>>>> wrote: >>>>>>> >>>>>>> On Thu, Apr 18, 2019 at 7:35 AM Oliver Thiel <[email protected]> >>>>>>> wrote: >>>>>>> > >>>>>>> > More information: >>>>>>> > sage: k=0 >>>>>>> > ....: for k in range(1,j-1,1): >>>>>>> > ....: z=float(A[k][1]) >>>>>>> > ....: s=s+z >>>>>>> > ....: >>>>>>> print(k)------------------------------------------------------------------------ >>>>>>> >>>>>>> > An error occurred during signal handling. >>>>>>> > This probably occurred because a *compiled* module has a bug >>>>>>> > in it and is not properly wrapped with sig_on(), sig_off(). >>>>>>> > Python will now terminate. >>>>>>> > >>>>>>> ------------------------------------------------------------------------ >>>>>>> > this error occurs before i "enter" the command. Do not laugh about >>>>>>> my simple code, i am real new to sage. :-D >>>>>>> > >>>>>>> I assume your A is already defined, right? >>>>>>> As well, I guess this code seems to mean to compute s as a sum of >>>>>>> float(A[k][1]) >>>>>>> but did you set s=0 to begin with? >>>>>>> (you did set k=0, which makes no sense, as you immediately use k as >>>>>>> a >>>>>>> loop variable) >>>>>>> >>>>>>> >>>>>> I don't think that's relevant. Oliver stated earlier that the >>>>>> problem happens simply while typing in code, and without even pressing >>>>>> enter (if I've understood correctly). >>>>>> >>>>>> Oliver, no one here will laugh at your code (I hope! :) and if I >>>>>> understand the problem it's nothing to do with anything specifically you >>>>>> wrote anyways. >>>>>> >>>>>> A couple more questions. You wrote >>>>>> >>>>>> > i used "Sage Mirror" to download the program and installed it with >>>>>> adminstration rights >>>>>> >>>>>> When you installed did you select the "Install for all users" or >>>>>> "Install just for the current user" option? If the latter, you shouldn't >>>>>> need Administrator permissions to install, unless this company machine >>>>>> has >>>>>> additional policies configured restricting your ability to install >>>>>> arbitrary software. It shouldn't matter much here but I'm just curious >>>>>> you >>>>>> say you installed with with Admin rights. >>>>>> >>>>>> Another question: If you run the "SageMath 8.6 Shell" shortcut, and >>>>>> run the command `sage -ipython` (this starts the IPython prompt without >>>>>> any >>>>>> Sage-specific code loaded) do you have any problems? Are you able to >>>>>> enter >>>>>> and run pure Python code like in your example above? >>>>>> >>>>>> Finally, do you know if there are any active virus scanners like >>>>>> McAffee or Symantic. Basically anything on this list: >>>>>> https://cygwin.com/faq/faq.html#faq.using.bloda (note: Windows >>>>>> Defender is normally not actually a problem, but it might be if it's in >>>>>> the >>>>>> middle of performing a scan). >>>>>> >>>>> >>>>> >>>>> It occurs to me that this *might* be an instance of the (very >>>>> technical) bug fixed by https://github.com/sagemath/cysignals/pull/108, >>>>> and included into Sage 8.7 by https://trac.sagemath.org/ticket/27070 >>>>> >>>>> If so, it's occurring in a context that I didn't previously know about >>>>> but it's not impossible, especially if there is BLODA involved. If >>>>> nothing >>>>> else it could be masking a different bug. >>>>> >>>>> I haven't made a Windows release for Sage 8.7 yet, in part because it >>>>> needs some additional patches that were not included in the main 8.7 >>>>> release tarball. I'm not happy about that but it can be dealt with by >>>>> updating the build tools for the Windows release to include additional >>>>> patches; I just need to do it. >>>>> >>>> -- >>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
