Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-23 Thread Oliver Thiel
Know i was able to follow your instructions, such a silly mistake of mine... and until now, there is no error while typing or something else. Am Di., 23. Apr. 2019 um 13:22 Uhr schrieb E. Madison Bray < erik.m.b...@gmail.com>: > On Tuesday, April 23, 2019 at 12:48:31 PM UTC+2, Oliver Thiel

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-23 Thread E. Madison Bray
On Tuesday, April 23, 2019 at 12:48:31 PM UTC+2, Oliver Thiel wrote: > > 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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-23 Thread Oliver Thiel
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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-23 Thread Oliver Thiel
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 < oliver.e.th...@gmail.com>: > 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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-23 Thread Oliver Thiel
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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-18 Thread E. Madison Bray
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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-18 Thread Oliver Thiel
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. The company where i work uses a specific policy software and for the installation of sage i get a

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-18 Thread 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 >> wrote: >> > >> > More information: >> > sage: k=0 >> > : for k in range(1,j-1,1): >>

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-18 Thread E. Madison Bray
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 > wrote: > > > > More information: > > sage: k=0 > > : for k in range(1,j-1,1): > > : z=float(A[k][1]) > > : s=s+z > > : >

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-18 Thread Dima Pasechnik
On Thu, Apr 18, 2019 at 7:35 AM Oliver Thiel 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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-17 Thread Oliver Thiel
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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-17 Thread Oliver Thiel
Sage runs on win 10, i used "Sage Mirror" to download the program and installed it with adminstration rights. I dont know if it is nessecary to say but the computer i am using is located in a company and i dont have permanent administration rights. The next time the failure will occure i show

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-17 Thread slelievre
Can you say what operating system this is on, and how Sage was installed? -- 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

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-17 Thread Oliver Thiel
That is the biggest problem, i've done nothing but typing some letters in the console and than the error occurs. For me there is no connection between my actions and the failure unless i am typing but without sending a command to the programm... for example i am typing: A=example.command(A,B,

Re: [sage-support] I absolutely dont know why but i am getting an error.

2019-04-17 Thread Jeroen Demeyer
On 2019-04-17 09:32, Oliver Thiel wrote: Hello, I absolutely dont know why but i am getting an error. What did you do? What happened *exactly*? See also https://www.chiark.greenend.org.uk/~sgtatham/bugs.html -- You received this message because you are subscribed to the Google Groups

[sage-support] I absolutely dont know why but i am getting an error.

2019-04-17 Thread Oliver Thiel
Hello, I absolutely dont know why but i am getting an error. "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." The program chrashes suddenly while i want