[sage-devel] Re: How about automatic install of all possible optional packages by a patchbot?
Jeroen Demeyer wrote: > I think it is far more important to do that on the release buildbot. The > patchbot is still an optional thing, which reviewers are free to ignore. Yes, but patch- and buildbots essentially do the same, with different configurations though. To me it seems this is not well-organized at the moment; as klee mentioned, it's not obvious which bot tests with which optional packages, and AFAIK the buildbots aren't integrated into trac at all -- they IMHO should (i.e., their results should at least be accessible from trac tickets in the same way the patchbots' are). -leif -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: How about automatic install of all possible optional packages by a patchbot?
Simon King wrote: > Hi! > > On 2016-09-12, Kwankyu Lee wrote: >> This happened to me. My patch for a ticket passed the doctesting by a >> patchbot A but afterward failed by another patchbot B. The reason was that >> the patchbot B has an optional package installed, and hence ran the >> optional doctests for the installed package, and my patch failed some of >> the optional doctests. >> >> If it were not for the patchbot B, my patch might have been merged into >> Sage, and make those optional doctests potential failures. I was fortunate. > > It could have been the other way around as well: Your patch works *with* > some optional package that you happen to have and forgot for some > reason, but it doesn't work without. Yes, that's exactly what I /tried to/ say as well... -leif > Hence, it can not be the solution that *all* patchbot install *all* > optional packages. In an ideal world, all possible combinations of > optional packages would be tested, but I doubt that that would be > feasible. > > Best regards, > Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Compilation error with linbox-1.4.2 during compilation of sage 7.4.beta4
this is now #21482 On Monday, September 12, 2016 at 5:50:11 PM UTC, leif wrote: > > Volker Braun wrote: > > The error is in an optional part that isn't compiled by default; I guess > > its the maple interface? The config contains > > > > checking for MAPLE >= 9.0... ./configure: line 18187: > > /bin/maple.system.type: No such file or directory > > found > > > > We should probably configure linbox with --with-maple=no > > ... or fix the build error. > > I'll post to #17635... > > > -leif > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: jupyter and python incompatibility in Sage 7.3?
On 2016-09-13 12:40, Stan wrote: Would it be a possible workaround to just pip install entrypoints and configparser? Just entrypoints would be sufficient. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: jupyter and python incompatibility in Sage 7.3?
OK, just to confirm, an easy workaround is, in a terminal: sage --sh pip install entrypoints pip install configparser Thanks a lot for your help!!! Stan On Tuesday, September 13, 2016 at 12:40:49 PM UTC+2, Stan wrote: > > Awesome, thanks! I should have looked for a ticket involving nbconvert > directly in sage-trac instead of the www. > Would it be a possible workaround to just pip install entrypoints and > configparser? > > I also didn't relaise that the %%sh magic takes me to the sage shell, not > the shell of my os. Thanks for letting me know. > > Cheers > Stan > > On Tuesday, September 13, 2016 at 11:46:05 AM UTC+2, Jeroen Demeyer wrote: >> >> On 2016-09-13 11:34, Stan wrote: >> > Actually, I am a bit confused here. For some reason|||jupyter| is not >> > found when I call it at the prompt, using Debian Jessy. Why is it found >> > when I call it from within a jupyter notebook using %%sh or os.system? >> >> Because Jupyter is installed within Sage. You need to run jupyter from a >> Sage shell: >> >> $ sage --sh >> >> (sage-sh) $ jupyter nbconvert --help >> This application is used to convert notebook files (*.ipynb) to various >> other formats. >> [...] >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: jupyter and python incompatibility in Sage 7.3?
Awesome, thanks! I should have looked for a ticket involving nbconvert directly in sage-trac instead of the www. Would it be a possible workaround to just pip install entrypoints and configparser? I also didn't relaise that the %%sh magic takes me to the sage shell, not the shell of my os. Thanks for letting me know. Cheers Stan On Tuesday, September 13, 2016 at 11:46:05 AM UTC+2, Jeroen Demeyer wrote: > > On 2016-09-13 11:34, Stan wrote: > > Actually, I am a bit confused here. For some reason|||jupyter| is not > > found when I call it at the prompt, using Debian Jessy. Why is it found > > when I call it from within a jupyter notebook using %%sh or os.system? > > Because Jupyter is installed within Sage. You need to run jupyter from a > Sage shell: > > $ sage --sh > > (sage-sh) $ jupyter nbconvert --help > This application is used to convert notebook files (*.ipynb) to various > other formats. > [...] > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: jupyter and python incompatibility in Sage 7.3?
On 2016-09-13 11:34, Stan wrote: Actually, I am a bit confused here. For some reason|||jupyter| is not found when I call it at the prompt, using Debian Jessy. Why is it found when I call it from within a jupyter notebook using %%sh or os.system? Because Jupyter is installed within Sage. You need to run jupyter from a Sage shell: $ sage --sh (sage-sh) $ jupyter nbconvert --help This application is used to convert notebook files (*.ipynb) to various other formats. [...] -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] jupyter and python incompatibility in Sage 7.3?
On 2016-09-13 11:10, Stan wrote: Every time I run either jupyter nbconvert or ipython nbconvert, I get the following error message: ImportError: No module named entrypoints This might have been fixed by https://trac.sagemath.org/ticket/21261 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] How about automatic install of all possible optional packages by a patchbot?
I think it is far more important to do that on the release buildbot. The patchbot is still an optional thing, which reviewers are free to ignore. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: jupyter and python incompatibility in Sage 7.3?
Actually, I am a bit confused here. For some reason jupyter is not found when I call it at the prompt, using Debian Jessy. Why is it found when I call it from within a jupyter notebook using %%sh or os.system? When I run ipython from the command line on one of my ipynb files, I get the following error message: NBFormatError: Unsupported nbformat version 4 On Tuesday, September 13, 2016 at 11:10:15 AM UTC+2, Stan wrote: > > Dear all, > I keep running into problems in Sage 7.3 that I did not have in 6.8. > Example: https://groups.google.com/forum/#!topic/sage-devel/nbV2VGIhD1s > The newest one seems to be explained here: > https://trac.macports.org/ticket/51167 > > Every time I run either jupyter nbconvert or ipython nbconvert, I get the > following error message: > > ImportError: No module named entrypoints > > The explanation in the above ticket was that "entrypoints has been added, but > does not work with python2.7". > Is there a way to fix this? > > Cheers > Stan > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] jupyter and python incompatibility in Sage 7.3?
Dear all, I keep running into problems in Sage 7.3 that I did not have in 6.8. Example: https://groups.google.com/forum/#!topic/sage-devel/nbV2VGIhD1s The newest one seems to be explained here: https://trac.macports.org/ticket/51167 Every time I run either jupyter nbconvert or ipython nbconvert, I get the following error message: ImportError: No module named entrypoints The explanation in the above ticket was that "entrypoints has been added, but does not work with python2.7". Is there a way to fix this? Cheers Stan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Sending the signal SIGHUP to a Sage 7.4.beta4 process doesn't kill the process
Reported upstream at https://github.com/ipython/ipython/issues/9944 https://github.com/jonathanslenders/python-prompt-toolkit/issues/392 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: How about automatic install of all possible optional packages by a patchbot?
> > Note that we'd have to do both, testing with *and* without (each) > optional package. Obviously we cannot test for all possible combinations of packages. But I think that every patch must be tested against at least one vanilla Sage and one full-featured Sage with "all" optional package installed. Even better "--optional=sage,optional,external" should be the norm. Perhaps the report by a patchbot should explicitly show the list of optional(and external) packages against which the patch passes doctesting, and coverage summary. This information is in the log but buried deep somewhere. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: How about automatic install of all possible optional packages by a patchbot?
Hi! On 2016-09-12, Kwankyu Lee wrote: > This happened to me. My patch for a ticket passed the doctesting by a > patchbot A but afterward failed by another patchbot B. The reason was that > the patchbot B has an optional package installed, and hence ran the > optional doctests for the installed package, and my patch failed some of > the optional doctests. > > If it were not for the patchbot B, my patch might have been merged into > Sage, and make those optional doctests potential failures. I was fortunate. It could have been the other way around as well: Your patch works *with* some optional package that you happen to have and forgot for some reason, but it doesn't work without. Hence, it can not be the solution that *all* patchbot install *all* optional packages. In an ideal world, all possible combinations of optional packages would be tested, but I doubt that that would be feasible. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Sending the signal SIGHUP to a Sage 7.4.beta4 process doesn't kill the process
Hi,
I use Sage 7.4.beta4 on Ubuntu 16.04. The Sage process used to exit if it
received SIGHUP, but Sage7.4.beta4 doesn't.
Step to reproduce:
1. Run Sage 7.4.beta4 in terminal
2. Try to kill the Sage process by "kill -HUP pid_of_the_process"
3. The Sage process crashes with the following message but it doesn't exit.
Attached file is ~/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt.
Best regards,
Sho Takemori
**
Oops, Sage crashed. We do our best to make it stable, but...
A crash report was automatically generated with the following information:
- A verbatim copy of the crash traceback.
- A copy of your input history during this session.
- Data on your current Sage configuration.
It was left in the file named:
'/home/sho/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will
help
them in understanding and correcting the problem.
You can mail it to: sage-support at sage-supp...@googlegroups.com
with the subject 'Sage Crash Report'.
If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-supp...@googlegroups.com <
/home/sho/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt
To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org
Hit to quit (your terminal may close):Error in sys.excepthook:
Traceback (most recent call last):
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/core/application.py",
line 254, in excepthook
return self.crash_handler(etype, evalue, tb)
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/core/crashhandler.py",
line 180, in __call__
input("Hit to quit (your terminal may close):")
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/utils/py3compat.py",
line 219, in input
return builtin_mod.raw_input(prompt)
EOFError: EOF when reading a line
Original exception was:
Traceback (most recent call last):
File "/home/sho/app/sage-7.4.beta4/SageMath/src/bin/sage-ipython", line
14, in
app.start()
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/terminal/ipapp.py",
line 348, in start
self.shell.mainloop()
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/terminal/interactiveshell.py",
line 402, in mainloop
self.interact()
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/terminal/interactiveshell.py",
line 385, in interact
code = self.prompt_for_code()
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython/terminal/interactiveshell.py",
line 321, in prompt_for_code
pre_run=self.pre_prompt, reset_current_buffer=True)
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/prompt_toolkit/interface.py",
line 389, in run
self.eventloop.run(self.input, self.create_eventloop_callbacks())
File
"/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/prompt_toolkit/terminal/vt100_input.py",
line 424, in __exit__
termios.tcsetattr(self.fileno, termios.TCSANOW, self.attrs_before)
termios.error: (25, 'Inappropriate ioctl for device')
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
***
IPython post-mortem report
{'commit_hash': u'1ba246d',
'commit_source': 'installation',
'default_encoding': 'UTF-8',
'ipython_path':
'/home/sho/app/sage-7.4.beta4/SageMath/local/lib/python2.7/site-packages/IPython',
'ipython_version': '5.0.0',
'os_name': 'posix',
'platform': 'Linux-4.4.0-36-generic-x86_64-with-debian-stretch-sid',
'sys_executable': '/home/sho/app/sage-7.4.beta4/SageMath/local/bin/python',
'sys_platform': 'linux2',
'sys_version': '2.7.10 (default, Sep 11 2016, 05:27:27) \n[GCC 4.9.3]'}
***
***
Crash traceback:
---
---
error Python 2.7.10: /home/sho/app/sage-7.4.beta4/SageMath/local/bin/python
Tue Sep 13 15:44:47 2016
A problem occurred executing Python code. Here is the sequence of function
calls leading up t
