[sage-devel] Testing Sage's packages

[John H Palmieri]

I just set SAGE_CHECK=yes and tried to build Sage on several platforms: OS 
X and a virtual machine running Ubuntu. Summary:

Failed on both:

- gap: looks like some sort of string-vs-bytes problem 
(https://trac.sagemath.org/ticket/28728)
- cvxopt: fails with a Python 3 build, hangs (at least on OS X) with a 
Python 2 build (https://trac.sagemath.org/ticket/28730)
- cysignals: fails with a Python 3 build because the testsuite uses the 
wrong "python" in testing, not Sage's python3 
(https://trac.sagemath.org/ticket/28726)
- nose: fails with a Python 3 build, passes with a Python 2 build 
(https://trac.sagemath.org/ticket/28727)

Failed on OS X:

- openblas: I see "ld: file too small (length=0)ld :file  file too small 
(length='0). file 
'./../libopenblas_skylakexplibopenblas_skylakexp--r0.3.6.a' r0.3.6.afor'  
architecturefor  x86_64architecture x86_64". I'm not sure why it's looking 
for libopenblas_skylake... instead of libopenblas_haswellp..., which looks 
like the appropriate file on this machine.

- cython (https://trac.sagemath.org/ticket/28729)

I think that all of the Cython failures look like

Failed example:
long_long_abs(-max_long_long-1) #doctest: +ELLIPSIS
Expected:
Traceback (most recent call last):
...
OverflowError: ...
Got:
-9223372036854775808


Failed on ubuntu virtual machine:

- linbox
- r

Notes: 
- these failures may be specific to some sort of misconfiguration of the 
virtual machine, so I haven't opened tickets for them.
- the Ubuntu virtual machine routinely has doctest failures due to 
numerical noise. Could these be related to the linbox failures?

---

What failures do others see?

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b46f882b-6267-4d31-99ef-7f10dcc1240a%40googlegroups.com.

[sage-devel] Re: Package installation/uninstallation confusion

[John H Palmieri]

I created https://trac.sagemath.org/ticket/28721 to add documentation for 
these to the developer's guide. Needs review.

  John


On Thursday, November 7, 2019 at 8:27:32 AM UTC-8, John H Palmieri wrote:
>
> These shell functions are defined and documented in 
> SAGE_ROOT/build/bin/sage-dist-helpers. In my opinion they should also be 
> documented in the developer's guide, but they don't seem to be.
>
>
> On Thursday, November 7, 2019 at 6:35:05 AM UTC-8, Simon King wrote:
>>
>> Hi Dima, 
>>
>> On 2019-11-06, Dima Pasechnik  wrote: 
>> > if you look at its spkg-install, you'd see that shd_install is not 
>> > used at some place, instead 
>> > 
>> > make install 
>> > 
>> > is done, something that won't write any JSON files, IMHO... 
>>
>> Good that I leave comments in my code... 
>>
>> The comment says that I used $MAKE install, because "sdh_make install 
>> got broken by trac ticket #24106". 
>>
>> However, I was unaware that apparently "sdh_make install" ought to be 
>> replaced by "sdh_install". So, I guess I should test this. 
>>
>> Or not? I see that far more packages use sdh_make_install (note the 
>> difference: What got broken apparently was sdh_make install with a blank 
>> space) than sdh_install. 
>>
>> Can you point me to man pages, where sdh_install versus 
>> sdh_make_install is discussed? 
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7ccd2619-78e0-42f7-b4af-98ff6166ee21%40googlegroups.com.

[sage-devel] Re: Package installation/uninstallation confusion

[John H Palmieri]

These shell functions are defined and documented in 
SAGE_ROOT/build/bin/sage-dist-helpers. In my opinion they should also be 
documented in the developer's guide, but they don't seem to be.


On Thursday, November 7, 2019 at 6:35:05 AM UTC-8, Simon King wrote:
>
> Hi Dima, 
>
> On 2019-11-06, Dima Pasechnik > wrote: 
> > if you look at its spkg-install, you'd see that shd_install is not 
> > used at some place, instead 
> > 
> > make install 
> > 
> > is done, something that won't write any JSON files, IMHO... 
>
> Good that I leave comments in my code... 
>
> The comment says that I used $MAKE install, because "sdh_make install 
> got broken by trac ticket #24106". 
>
> However, I was unaware that apparently "sdh_make install" ought to be 
> replaced by "sdh_install". So, I guess I should test this. 
>
> Or not? I see that far more packages use sdh_make_install (note the 
> difference: What got broken apparently was sdh_make install with a blank 
> space) than sdh_install. 
>
> Can you point me to man pages, where sdh_install versus 
> sdh_make_install is discussed? 
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/10e06ff0-55d0-425e-b03a-68096f688cb2%40googlegroups.com.

Re: [sage-devel] Re: Package installation/uninstallation confusion

[John H Palmieri]

Simon, you should look at the json file for p_group_cohomology to see if it 
contains all of the installed files, or if indeed some are not listed. If 
everything is there, there is no need to split it into two packages, unless 
I'm missing something.



On Wednesday, November 6, 2019 at 9:33:04 AM UTC-8, Dima Pasechnik wrote:
>
> sdh_install installs a json file into 
> SAGE_LOCAL/var/lib/sage/installed/ 
> which are then used by unistallaller 
>
> e.g. "make meataxe" produces 
> SAGE_LOCAL/var/lib/sage/installed/meataxe-1.0.p0 
> { 
> "package_name": "meataxe", 
> "package_version": "1.0.p0", 
> "install_date": "Wed Nov  6 17:24:57 GMT 2019", 
> "system_uname": "Linux hilbert 5.1.12-gentoo #1 SMP Fri Jun 21 
> 19:27:38 BST 2019 x86_64 Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz 
> GenuineIntel GNU/Linux", 
> "sage_version": "SageMath version 9.0.beta4, Release Date: 
> 2019-11-02", 
> "test_result": "", 
> "files": [ 
> "bin/cfcomp", 
> "bin/chop", 
> ... 
> } 
>
> I guess sdh_pip_install does not do this, I don't know. 
>
> Anyhow, it would make perfect sense to split the package into two, as 
> you propose. 
>
> On Wed, Nov 6, 2019 at 3:55 PM Simon King  > wrote: 
> > 
> > Hi Eric, 
> > 
> > On 2019-11-06, E. Madison Bray > wrote: 
> > >> However, I heard rumours that in order to make a Sage optional 
> package 
> > >> uninstallable, one needs some new script analogous to spkg-install. 
> > >> 
> > >> Can someone give me a pointer on what should be done in that script 
> and 
> > >> what tools (sdh_*) are available for it? 
> > > 
> > > That's not quite accurate.  In general you do *not* need any 
> > > additional scripts, with some exception. 
> > > These packaging guidelines still need better documentation, but 
> > > essentially you need to make sure the package is built for what is 
> > > referred in GNU standards as a "DESTDIR install" [1].  This means that 
> > > the package is built for installation to some particular prefix (e.g. 
> > > `./configure --prefix=$SAGE_LOCAL` in autoconf terms), but can then be 
> > > *installed* with some additional path (the "DESTDIR") prepended to the 
> > > prefix.  This is similar to providing an alternate root (e.g. prefix 
> > > is appended to DESTDIR instead of just "/"). 
> > 
> > Then what to do with p_group_cohomology? Its spkg-install script 
> > installs two sub-packages. Each of them, I think, follows the above 
> > scheme. However, Sage has no way of knowing that uninstalling 
> > p_group_cohomology means uninstalling two sub-packages. 
> > 
> > Perhaps one possibility is to split the current p_group_cohomology-3.3 
> > into its two sub-packages, and make the first (which is autotoolized) 
> > a dependency for the second (which is a bunch of cython and python 
> > modules linked against the first sub-package. 
> > 
> > Say: 
> > - p_group_cohomology-3.4 shall only comprise what currently is the 
> >   p/cython part of p_group_cohomology-3.3, and have modular_resolution 
> >   as a dependency. 
> > - modular_resolution-1.0 shall only comprise what currently is the 
> >   autotoolized c-library part of p_group_cohomology-3.3 
> > 
> > Advantage: "make p_group_cohomology" would also install the dependency, 
> > hence, both packages get installed. And both packages can also be 
> > un-installed, I suppose. 
> > 
> > Disadvantage: The only purpose of modular_resolution-1.0 would be to 
> > serve as a dependency, it is (to my knowledge at least) of no 
> > independent use. 
> > 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/qpuqe5%247598%241%40blaine.gmane.org.
>  
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f30617cc-9e63-49b2-b097-b10682596c1b%40googlegroups.com.

Re: [sage-support] Re: sage building with python3

[John H Palmieri]

If you want to build Sage for use with Python 3, you should do

$ make distclean
$ ./configure --with-python=3
$ make

Where does this fail for you?



On Monday, November 4, 2019 at 8:21:04 AM UTC-8, Александр Ватузов wrote:
>
> No, I am building sage only for using it with python3. So I need to 
> install ipython and prompt_toolkit
>
> понедельник, 4 ноября 2019 г., 18:56:00 UTC+3 пользователь Dima Pasechnik 
> написал:
>>
>> Well, it is not clear what you are trying to do. Yes, if you want to use 
>> more recent than used in Sage (for compatibility with Python2 reasons) 
>> packages, then various things need to be adjusted. It has to be done in a 
>> systematic way.
>>
>>
>>
>> On Mon, 4 Nov 2019, 15:44 Александр Ватузов,  wrote:
>>
>>> Another error:
>>>
>>> jupyter-console 6.0.0 has requirement prompt-toolkit<2.1.0,>=2.0.0, but 
>>> you'll have prompt-toolkit 1.0.15 which is incompatible.
>>> ipython 7.9.0 has requirement prompt-toolkit<2.1.0,>=2.0.0, but you'll 
>>> have prompt-toolkit 1.0.15 which is incompatible.
>>>
>>> понедельник, 4 ноября 2019 г., 17:37:54 UTC+3 пользователь Dima 
>>> Pasechnik написал:

 looks like you have a bad mix of python packages in a number of 
 locations.

 certainly you can try something like

 ./sage --pip install prompt_toolkit


 On Mon, 4 Nov 2019, 13:05 Александр Ватузов,  wrote:

> next error:
>
> when I try:
> import prompt_toolkit
>
> ImportError: cannot import name 'AsyncGeneratorItem' from 
> 'prompt_toolkit.eventloop' 
> (/home/nouret/SageMath_3/local/lib/python3.7/site-packages/prompt_toolkit/eventloop/__init__.py)
>
> AsyncGeneratorItem is defined in 
> ./local/lib/python3.7/site-packages/prompt_toolkit/eventloop/async_generator.py
>
> /home/nouret/SageMath_3/local/lib/python3.7/site-packages/prompt_toolkit/eventloop/__init__.py
>  
> is empty
>
> понедельник, 4 ноября 2019 г., 14:56:35 UTC+3 пользователь Dima 
> Pasechnik написал:
>>
>> try 
>>
>> ./sage -f ipython 
>>
>> followed by 
>>
>> make build 
>>
>>
>> On Mon, Nov 4, 2019 at 11:47 AM Александр Ватузов  
>> wrote: 
>> > 
>> > sage building is sucsess now. But running sage makes error 
>> > 
>> > cannot import name '_baseclass_reprs' from 'IPython.lib.pretty' 
>> > 
>> > it looks like new libreary, but don't undestend, which one 
>> > 
>> > понедельник, 4 ноября 2019 г., 12:51:24 UTC+3 пользователь Dima 
>> Pasechnik написал: 
>> >> 
>> >> 
>> >> 
>> >> On Mon, 4 Nov 2019, 09:47 Александр Ватузов,  
>> wrote: 
>> >>> 
>> >>> it builds cython lib? 
>> >> 
>> >> yes 
>> >>> 
>> >>> 
>> >>> понедельник, 4 ноября 2019 г., 12:35:17 UTC+3 пользователь Dima 
>> Pasechnik написал: 
>>  
>>  
>>  
>>  On Mon, 4 Nov 2019, 09:27 Александр Ватузов,  
>> wrote: 
>> > 
>> > "./sage -pip install cython" installs cython for python3: 
>> Requirement already satisfied: cython in 
>> ./local/lib/python3.7/site-packages (0.29.14); and 
>> > "Requirement already satisfied: gmpy2 in 
>> ./local/lib/python3.7/site-packages (2.0.8)" 
>> > 
>> > So I think that, may be, cython need gmpy2 installed in other 
>> way? I still have na error: 
>>  
>>  try 
>>  
>>  ./sage -f gmpy2 
>>  
>> > 
>> > [sagelib-8.9] cimport gmpy2 
>> > [sagelib-8.9]^ 
>> > [sagelib-8.9] 
>>  
>> > [sagelib-8.9] 
>> > [sagelib-8.9] sage/rings/complex_double.pyx:110:8: 'gmpy2.pxd' 
>> not found 
>> > 
>> > 
>> > 
>> > 
>> > воскресенье, 3 ноября 2019 г., 23:52:01 UTC+3 пользователь 
>> Simon King написал: 
>> >> 
>> >> Hi Dima, 
>> >> 
>> >> On 2019-11-02, Dima Pasechnik  wrote: 
>> >> > There "python" is Sage's Python, "pip" manages its modules, 
>> etc. 
>> >> 
>> >> IIRC, that's not true for Sage's py-3 version. Namely, if one 
>> opens a 
>> >> sage-with-py-3 shell, then "python" still means "python2". So, 
>> if you 
>> >> really want Sage-with-py-3's Python installation, you should 
>> either do 
>> >> "sage -python" or (in a Sage shell) "python3". And I think the 
>> same 
>> >> holds for pip. 
>> >> 
>> >> Best regards, 
>> >> Simon 
>> >> 
>> > -- 
>> > 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 

[sage-devel] Re: OSX Catalina works

[John H Palmieri]

I am using the same versions of OS and Xcode as you. I am now doing this 
with a third computer. This one had an old Xcode and some homebrew stuff 
already installed, and it gave me some problems. I ended up uninstalling 
and then reinstalling various parts of homebrew, and Sage now builds for 
me. (I had also first installed some things by hand, like gfortran many 
months ago. So I had to delete things like that when doing the homebrew 
installation.)

$ brew list
autoconflibdvdcss   p7zip
automakelibeventpari
boost   libffi  pcre
cabextract  libidn2 pkg-config
cimglibmpc  python
cmake   libomp  readline
emacs-mac   libpng  shared-mime-info
gcc libtasn1sqlite
gdbmlibtool texinfo
gettext libunistringunbound
glibmpfiunrar
gmp mpfrwine
gnutls  nettle  winetricks
gpatch  ntl x265
icu4c   openexr xz
ilmbase openssl yasm
isl openssl@1.1
libde265p11-kit


$ brew --version
Homebrew 2.1.15
Homebrew/homebrew-core (git revision d191f; last commit 2019-11-03)
Homebrew/homebrew-cask (git revision cbd79; last commit 2019-11-03)




On Sunday, November 3, 2019 at 8:53:57 PM UTC-8, Andrew wrote:
>
> I uninstalled xcode and brew's gcc and then reinstall them both but I 
> still the the same failure with givaro.
> I don't know if this is related, but even though I installed ntl using 
> brew it is not used when I compile sage as the log file reports:
>
> checking NTL/ZZ.h usability... no
> checking NTL/ZZ.h presence... yes
> configure: WARNING: NTL/ZZ.h: present but cannot be compiled
> configure: WARNING: NTL/ZZ.h: check for missing prerequisite headers?
> configure: WARNING: NTL/ZZ.h: see the Autoconf documentation
> configure: WARNING: NTL/ZZ.h: section "Present But Cannot Be Compiled"
> configure: WARNING: NTL/ZZ.h: proceeding with the compiler's result
> configure: WARNING: ## -- ##
> configure: WARNING: ## Report this to sage-...@googlegroups.com 
>  ##
> configure: WARNING: ## -- ##
> checking for NTL/ZZ.h... no
> checking whether we can link a program using NTL... no
> checking NTL version >= 10.3... 11.4.1
> using Sage's ntl SPKG
> configure: === checking whether to install the flint SPKG ===
> checking installing mpfr or ntl? ... yes; install flint as well
> using Sage's flint SPKG
> configure: === checking whether to install the arb SPKG ===
> checking installing flint? ... yes; install arb as well
> configure: === checking whether to install the bzip2 SPKG ===
>
> That sage wants compile flint and arb is expected because I try to install 
> them with brew I get errors like:
>
> ==> make
> Last 15 lines from /Users/andrew/Library/Logs/Homebrew/flint/02.make:
>   ~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:324:9:
>  
> error: no member named 'islessgreater' in the global namespace
> using ::islessgreater;
>   ~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:325:9:
>  
> error: no member named 'isunordered' in the global namespace
> using ::isunordered;
>   ~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:326:9:
>  
> error: no member named 'isunordered' in the global namespace
> using ::isunordered;
>   ~~^
> 13 errors generated.
> make[2]: *** [build/interfaces/NTL-interface.lo] Error 1
>
> These are similar to the errors that I get with givaro when compiling sage.
>
> John: what version of xcode and the command line tools are using and if 
> you first do
>
> make distclean
>
> are you still able to compile sage? As I reinstalled xcode from the 
> appsrtore I am using the latest versions av I am using:
>
> ProductName:Mac OS X
> ProductVersion:10.15.1
> BuildVersion:19B88
> Xcode 11.2
> Build version 11B52
>
> Andrew
>
>
>
>
> On Saturday, 2 November 2019 05:45:08 UTC+11, Andrew wrote:
>>
>> Thanks John. I'll give this a try on Monday.
>> Andrew
>>
>> On Saturday, 2 November 2019 04:20:08 UTC+11, John H Palmieri wrote:
>>>
>>> I just upgraded a different machine to Catalina. This one didn't have 
>>> Xcode or homebrew installed beforehand, so I installed Xcode, its 
>>> command-line tools, and homebrew's gcc. Then I built Sage and it worked. I 
>>> have now installed a bunch of othe

Re: [sage-support] Re: sage building with python3

[John H Palmieri]

Since trac #28426 (merged pretty recently), when building with Python 3, we 
do not build Python 2. Before that, we always built both.


On Sunday, November 3, 2019 at 12:57:02 PM UTC-8, Dima Pasechnik wrote:
>
> I am surprised we still even build python2 by default. Isn't it an 
> optional package?
>
> On Sun, 3 Nov 2019, 20:52 Simon King, > 
> wrote:
>
>> Hi Dima,
>>
>> On 2019-11-02, Dima Pasechnik > wrote:
>> > There "python" is Sage's Python, "pip" manages its modules, etc.
>>
>> IIRC, that's not true for Sage's py-3 version. Namely, if one opens a
>> sage-with-py-3 shell, then "python" still means "python2". So, if you
>> really want Sage-with-py-3's Python installation, you should either do
>> "sage -python" or (in a Sage shell) "python3". And I think the same
>> holds for pip.
>>
>> Best regards,
>> Simon
>>
>> -- 
>> 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/qpnel6%24itu%241%40blaine.gmane.org
>> .
>>
>

-- 
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/45d0a564-549e-4fea-addf-dc2e30cc4001%40googlegroups.com.

Re: [sage-devel] Re: Optional and experimental packages

[John H Palmieri]

Two more tickets:

https://trac.sagemath.org/ticket/28686: change a bunch of packages from 
optional to experimental, delete a few pip packages (as Samuel suggested). 
I didn't delete all of the pip packages, just the ones that are not 
compatible with Python 3.

https://trac.sagemath.org/ticket/28687: change scons from optional to 
experimental. I thought briefly of trying to upgrade it instead, but I 
don't really care about the package, so someone else who is actually 
interested will have to do that.

  John



On Friday, November 1, 2019 at 1:27:34 PM UTC-7, John H Palmieri wrote:
>
> Note that "sage --sws2rst ..." relies on sagenb, and therefore will only 
> work with Sage built with Python 2.
>
> In any case, https://trac.sagemath.org/ticket/28685 upgrades to 
> beautifulsoup4, which is compatible with Python 3.
>
>
> On Friday, November 1, 2019 at 3:43:32 AM UTC-7, kcrisman wrote:
>>
>>
>>
>> On Thursday, October 31, 2019 at 8:16:55 AM UTC-4, Dima Pasechnik wrote:
>>>
>>> I think the Sage tutorial mentioning beautifulsoup actually says to 
>>> install it as
>>>
>>> sage --pip install beatifulsoup4
>>>
>>> which would install the package from the net rather than Sage's one 
>>>
>>>>
>>>>
>> Great, perhaps that was updated at some point. 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/04e297b6-d605-489f-8188-8cfb9dd715a4%40googlegroups.com.

Re: [sage-devel] Re: Optional and experimental packages

[John H Palmieri]

Note that "sage --sws2rst ..." relies on sagenb, and therefore will only 
work with Sage built with Python 2.

In any case, https://trac.sagemath.org/ticket/28685 upgrades to 
beautifulsoup4, which is compatible with Python 3.


On Friday, November 1, 2019 at 3:43:32 AM UTC-7, kcrisman wrote:
>
>
>
> On Thursday, October 31, 2019 at 8:16:55 AM UTC-4, Dima Pasechnik wrote:
>>
>> I think the Sage tutorial mentioning beautifulsoup actually says to 
>> install it as
>>
>> sage --pip install beatifulsoup4
>>
>> which would install the package from the net rather than Sage's one 
>>
>>>
>>>
> Great, perhaps that was updated at some point. 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5de7a4df-a9be-45a7-8707-9a5d68318c7d%40googlegroups.com.

[sage-devel] Re: OSX Catalina works

[John H Palmieri]

I just upgraded a different machine to Catalina. This one didn't have Xcode 
or homebrew installed beforehand, so I installed Xcode, its command-line 
tools, and homebrew's gcc. Then I built Sage and it worked. I have now 
installed a bunch of other homebrew packages relevant to Sage, and the 
build is going fine. (I had to log out of the machine, so I had to 
interrupt the build, but it had made it past givaro and ntl, which were 
sticking points for another user in this thread.)

Thinking back on the other machine I upgraded, that one was also relatively 
"clean": no old Xcode or old homebrew stuff. So for those who are having 
problems, I wonder if uninstalling Xcode first would help. Maybe there are 
some other old libraries which should be removed before installing the new 
Xcode.

  John


On Monday, October 14, 2019 at 10:43:09 AM UTC-7, Volker Braun wrote:
>
> Means: I successfully compiled Sage 8.9 on OSX Catalina with Xcode 11.0 
>
>
>
> On Sunday, October 13, 2019 at 9:24:44 PM UTC+2, Samuel Lelievre wrote:
>>
>> Sun 2019-10-13 08:26:52 UTC, Volker Braun:
>>>
>>> I just upgraded the OSX buildbot and Sage works
>>>
>> in case anybody is wondering. This is the first time in years
>>>
>> that the latest OSX release doesn't introduce major toolchain
>>>
>> issues and/or scrambles the filesystem, hope this starts a trend ;-) 
>>>
>>
>> That's good to hear, and there were people wondering.
>> See for instance this question on Ask Sage about SageMath
>> and macOS 10.15 "Catalina":
>>
>> - How to unlock SageMath 8.8 on macOS 10.15 Catalina?
>>   https://ask.sagemath.org/question/48293
>>
>> By "Sage works" do you mean any of the following?
>>
>> - there are / there will be binaries for macOS 10.15 "Catalina"
>> - the SageMath 8.9 binaries for macOS 10.14 "Mojave"
>>   also work for macOS 10.15 "Catalina"
>> - on macOS 10.15 "Catalina" building SageMath 8.9 from
>>   source gives a version that works and is not "locked"
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3a5ac523-a0f1-432d-ae3d-5d9171f08deb%40googlegroups.com.

Re: [sage-devel] Re: OSX Catalina works

[John H Palmieri]

If you have the time, could you try uninstalling Xcode and then 
reinstalling it? You might also try uninstalling and reinstalling 
homebrew's gcc and any other homebrew components that are relevant to Sage. 
There may be some remnants of previously installed software that is somehow 
interfering.

  John


On Wednesday, October 30, 2019 at 8:58:38 PM UTC-7, Andrew wrote:
>
>
>
> On Wednesday, 30 October 2019 23:27:45 UTC+11, Dima Pasechnik wrote:
>>
>> I meant cmath files without extensions. These are C++ header files.
>> It appears there are two such files on the list. Are they different?
>>
>> In the interim have have installed homebrew's gcc to see if this helps, 
> but it doesn't. The cmath files that I now have on my system are:
>
> -rw-r--r--  1 rootwheel  14515 23 Jul 03:08 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath
> -rw-r--r--  1 rootwheel  14515 23 Jul 03:08 
> /Library/Developer/CommandLineTools/usr/include/c++/v1/cmath
>
> As you suspected, these two files are identical.
>
> from homebrew's gcc:
> -rw-r--r--  1 andrew  staff619 14 Aug 22:29 
> /usr/local/Cellar/boost/1.71.0/include/boost/compatibility/cpp_c_headers/cmath
> -rw-r--r--  1 andrew  staff  49094 12 Aug 17:58 
> /usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/cmath
> -rw-r--r--  1 andrew  staff   6570 12 Aug 17:58 
> /usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/ext/cmath
> -rw-r--r--  1 andrew  staff  43806 12 Aug 17:58 
> /usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/tr1/cmath
> -rw-r--r--  1 andrew  wheel619 31 Oct 13:51 
> /usr/local/src/sage/local/include/boost/compatibility/cpp_c_headers/cmath
>
> Andrew
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/181aab57-8e49-46f3-b758-45f700587410%40googlegroups.com.

[Bacula-users] Bacula: improving logging?

[John H Nyhuis]

I want to improve the logging of my Bacula server.

Right now, Bacula seems to log a lot of things I don't care about, such 
as spoolersize and spooler usage, and does not log information I would 
like to see, such as filenames or directories currently being backed up.

Jobs are long, so some status notifying me of progress other than 'The 
Job's still running' is warranted.

All of the reading I have found thus far focuses on different log 
utilities and log rotation, but I want to customize what events are 
being logged by bacula-fd.

I don't currently have -d specified for bacula-fd, so I could play 
around with the debug level to see if this will add the information I 
want, but then it's a matter of turning off the logs (such as the 
default spooler size status message that is logged every second) that I 
do not want.

Has anyone customized bacula logging and would be willing to share what 
they did?

FYI: my logs are filled with this message, repeated every second:

31-Oct 09:58 Scalar-i40 JobId 28: Writing spooled data to Volume. 
Despooling 129,048 bytes ...
31-Oct 09:58 Scalar-i40 JobId 28: Despooling elapsed time = 00:00:01, 
Transfer rate = 129.0 K Bytes/second
31-Oct 09:58 Scalar-i40 JobId 28: Spooling data again ...

In my opinion, the fact that the spooler is working and doing it's job 
isn't something that needs to be logged.  Knowing what file is currently 
being read would be nice.

Thanks in Advance,
-- 
Thanks,

John H. Nyhuis
Desk: (206)-685-8334
jnyh...@uw.edu
Box 359461, 15th floor, 106

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [sage-devel] MacOS 10.15.1: gfortran does not compile in sage-8.9

[John H Palmieri]

I tried building several version of gfortran by hand on 10.15, but I 
couldn't succeed, whereas I could with 10.14. I didn't try just upgrading 
Sage's gfortran/gcc package to 9.x.


On Wednesday, October 30, 2019 at 3:21:58 PM UTC-7, François Bissey wrote:
>
> I suspect gcc/gfortran shipped with sage is too old to build on 10.15. 
> Upgrading to 9.x may help. 
>
> > On 31/10/2019, at 11:04 AM, Dima Pasechnik  > wrote: 
> > 
> > I think at the moment most people who tried cannot build Sage on MacOS 
> > 10.15 with Xcode 11.1 (the latest one). 
> > Regarding gfortran, perhaps one can try installing Homebrew and use 
> > gfortram from there. 
> > 
> > If you just need a working Sage, your best bet on MacOS 10.15 might be 
> > the one from conda-forge. 
> > https://anaconda.org/conda-forge/sage 
> > 
> > 
> > 
> > On Wed, Oct 30, 2019 at 10:57 PM Rob Gross  > wrote: 
> >> 
> >> Hi, 
> >> 
> >> I tried both upgrading to sage-8.9 and compiling from scratch, and both 
> times gfortran would not compile.  I cannot attach the entire log file 
> without an error.  I attach the first few lines and the last few lines, and 
> of course I can e-mail anyone with as much information as needed. 
> >> 
> >> Here is the first error message in the log file: 
> >> 
> >> libtool: compile: 
>  
> /Users/gross/sage-8.9/local/var/tmp/sage/build/gfortran-7.4.0/gcc-build/./gcc/xgcc
>  
> -B/Users/gross/sage-8.9/local/var/tmp/sage/build/gfortran-7.4.0/gcc-build/./gcc/
>  
> -B/Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/bin/ 
> -B/Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/lib/ -isystem 
> /Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/include -isystem 
> /Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/sys-include 
> -DHAVE_CONFIG_H -I. -I../../../src/libssp -Wall -g -O2 -MT gets-chk.lo -MD 
> -MP -MF .deps/gets-chk.Tpo -c ../../../src/libssp/gets-chk.c  -fno-common 
> -DPIC -o .libs/gets-chk.o 
> >> In file included from 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/wait.h:110:0,
>  
>
> >> from 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdlib.h:66,
>  
>
> >> from ../../../src/libssp/gets-chk.c:39: 
> >> 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:
>  
> In function 'getiopolicy_np': 
> >> 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:443:34:
>  
> error: expected declaration specifiers before '__OSX_AVAILABLE_STARTING' 
> >> int getiopolicy_np(int, int) __OSX_AVAILABLE_STARTING(__MAC_10_5, 
> __IPHONE_2_0); 
> >>  ^~~~ 
> >> 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:449:39:
>  
> error: expected '=', ',', ';', 'asm' or '__attribute__' before 
> '__OSX_AVAILABLE_STARTING' 
> >> int setiopolicy_np(int, int, int) 
> __OSX_AVAILABLE_STARTING(__MAC_10_5, __IPHONE_2_0); 
> >> 
> >> Any ideas? 
> >> 
> >> Thanks.--Rob 
> >> 
> >> -- 
> >> 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-...@googlegroups.com . 
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/b557aad7-51f6-469b-9dac-bac679275400%40googlegroups.com.
>  
>
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq3LG%2Bj6eWxrYtJ7K%3Dc__PTtC%3DkNyWX9J8ywNY-u%3DPeugA%40mail.gmail.com.
>  
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f861ebee-f4b2-4f3f-b52a-888a6b6ae9a7%40googlegroups.com.

[sage-devel] Re: MacOS 10.15.1: gfortran does not compile in sage-8.9

[John H Palmieri]

I also had problems with Sage's gfortran package with OS X Catalina. I 
instead installed homebrew (https://brew.sh), and used homebrew to install 
their gcc package. This should install gfortran, which Sage will find as 
part of its configure process, thereby bypassing Sage's gfortran package. 
One benefit: Sage will never try to install gfortran again, which saves a 
good chunk of time. (Installing homebrew's gcc will also create 
/usr/local/bin/gcc-9.2.0 but not /usr/local/bin/gcc. It is important not to 
have /usr/local/bin/gcc, since Sage wants to use the pre-existing 
/usr/bin/gcc.)

  John


On Wednesday, October 30, 2019 at 1:57:03 PM UTC-7, Rob Gross wrote:
>
> Hi,
>
> I tried both upgrading to sage-8.9 and compiling from scratch, and both 
> times gfortran would not compile.  I cannot attach the entire log file 
> without an error.  I attach the first few lines and the last few lines, and 
> of course I can e-mail anyone with as much information as needed.
>
> Here is the first error message in the log file:
>
> libtool: compile:  
> /Users/gross/sage-8.9/local/var/tmp/sage/build/gfortran-7.4.0/gcc-build/./gcc/xgcc
>  
> -B/Users/gross/sage-8.9/local/var/tmp/sage/build/gfortran-7.4.0/gcc-build/./gcc/
>  
> -B/Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/bin/ 
> -B/Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/lib/ -isystem 
> /Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/include -isystem 
> /Users/gross/sage-8.9/local/x86_64-apple-darwin19.0.0/sys-include 
> -DHAVE_CONFIG_H -I. -I../../../src/libssp -Wall -g -O2 -MT gets-chk.lo -MD 
> -MP -MF .deps/gets-chk.Tpo -c ../../../src/libssp/gets-chk.c  -fno-common 
> -DPIC -o .libs/gets-chk.o
> In file included from 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/wait.h:110:0,
>  from 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdlib.h:66,
>  from ../../../src/libssp/gets-chk.c:39:
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:
>  
> In function 'getiopolicy_np':
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:443:34:
>  
> error: expected declaration specifiers before '__OSX_AVAILABLE_STARTING'
>  int getiopolicy_np(int, int) __OSX_AVAILABLE_STARTING(__MAC_10_5, 
> __IPHONE_2_0);
>   ^~~~
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:449:39:
>  
> error: expected '=', ',', ';', 'asm' or '__attribute__' before 
> '__OSX_AVAILABLE_STARTING'
>  int setiopolicy_np(int, int, int) 
> __OSX_AVAILABLE_STARTING(__MAC_10_5, __IPHONE_2_0);
>
> Any ideas?
>
> Thanks.--Rob
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fd1fa9ea-024e-48a4-8b27-0991264dbc19%40googlegroups.com.

Re: [CentOS] udev on CEntOS7 - can't get a match, looking for tips...

[John H Nyhuis]

hmmm, I thought := assigned a key just like +=, except := locked it so 
it could not be changed later.  Am I misunderstanding the man page for udev?

Thanks,

John H. Nyhuis
Desk: (206)-685-8334
jnyh...@uw.edu
Box 359461, 15th floor, 106

On 10/29/2019 4:31 PM, Leon Fauster via CentOS wrote:
> Am 29.10.19 um 23:41 schrieb John H Nyhuis:
>> Thanks, I did catch the mistype (after IU posted).  Still no match with
>> the typo fixed... :-(
>>
>> Thanks,
>>
>> John H. Nyhuis
>> Desk: (206)-685-8334
>> jnyh...@uw.edu
>> Box 359461, 15th floor, 106
>>
>> On 10/29/2019 4:03 AM, Tony Mountifield wrote:
>>> In article <7025a0a8-1471-530d-dad0-3770e902c...@uw.edu>,
>>> John H Nyhuis  wrote:
>>>> The mtx binary requires my tape library to be assigned a sg# driver, 
>>>> but
>>>> the kernel periodically renumbers the sg devices.  Normally, we would
>>>> write a udev rule to manually assign a persistent name, but it looks
>>>> like things have changed as I can't seem to get a match on CEntOS7.  
>>>> I'd
>>>> appreciate any feedback or pointers to help me get my rule working.  My
>>>> two attempts are below.
>>>>
>>>> cat /etc/udev/rules.d/90-local.rules
>>>>
>>>> KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \
>>>> ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8"
>>>>
>>>> SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \
>>>> ATTRS{model}=="Scalar i40-i80  ", SYMLINK:="sg8"
>>>
>>> You have a typo: scsi_genric instead of scsi_generic.
>>>
>>> Don't know if that is the reason.
>>>
> 
> 
> SYMLINK:="sg8" -> SYMLINK+="sg8"
> 
> -- 
> Leon
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] udev on CEntOS7 - can't get a match, looking for tips...

[John H Nyhuis]

Thanks, I did catch the mistype (after IU posted).  Still no match with 
the typo fixed... :-(

Thanks,

John H. Nyhuis
Desk: (206)-685-8334
jnyh...@uw.edu
Box 359461, 15th floor, 106

On 10/29/2019 4:03 AM, Tony Mountifield wrote:
> In article <7025a0a8-1471-530d-dad0-3770e902c...@uw.edu>,
> John H Nyhuis  wrote:
>> The mtx binary requires my tape library to be assigned a sg# driver, but
>> the kernel periodically renumbers the sg devices.  Normally, we would
>> write a udev rule to manually assign a persistent name, but it looks
>> like things have changed as I can't seem to get a match on CEntOS7.  I'd
>> appreciate any feedback or pointers to help me get my rule working.  My
>> two attempts are below.
>>
>> cat /etc/udev/rules.d/90-local.rules
>>
>> KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \
>> ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8"
>>
>> SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \
>> ATTRS{model}=="Scalar i40-i80  ", SYMLINK:="sg8"
> 
> You have a typo: scsi_genric instead of scsi_generic.
> 
> Don't know if that is the reason.
> 
> Cheers
> Tony
> 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [sage-devel] Re: OSX Catalina works

[John H Palmieri]

On Tuesday, October 29, 2019 at 4:45:53 AM UTC-7, Andrew wrote:
>
> Thanks Dima
>
> On Tuesday, 29 October 2019 17:51:02 UTC+11, Dima Pasechnik wrote:
>>
>> Did you  run 
>>
>> xcode-select --install 
>>
>> after Xcode upgrade? 
>>
>
> Yes, the command line tools are correctly installed but, as far as I can 
> see, xcode-select --install  is no longer the correct way to check this 
> because it results in the error:
>
> xcode-select: error: command line tools are already installed, use 
> "Software Update" to install updates
>

After installing Xcode, did you run Xcode? Often it needs to be run once to 
install some components, and in particular the command line tools.

 

>  
>
>> By the way, why don't you use NTL from brew? 
>> https://formulae.brew.sh/formula/ntl#default 
>>
>> you can also make things easier by installing Flint and Arb into 
>> homebrew, by using formulas from 
>> https://github.com/dimpase/homebrew-science 
>>
>> Run 
>>
>> brew install dimpase/science/flint 
>> brew install dimpase/science/arb 
>>
>
> Thanks. I didn't know that there were homebrew formulas for any of these. 
> Unfortunately, neither of these work either, giving similar (but shorter) 
> messages to the compilation errors with sage. Installing flint results in:
>
> ==> Downloading http://flintlib.org/flint-2.5.2.tar.gz
>  
> 100.0%
> ==> ./configure --prefix=/usr/local/Cellar/flint/2.5.2_1 
> --with-gmp=/usr/local/opt/gmp --with-mpfr=/u
> ==> make
> Last 15 lines from /Users/andrew/Library/Logs/Homebrew/flint/02.make:
>   ~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:324:9:
>  
> error: no member named 'islessgreater' in the global namespace
> using ::islessgreater;
>   ~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:325:9:
>  
> error: no member named 'isunordered' in the global namespace
> using ::isunordered;
>   ~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:326:9:
>  
> error: no member named 'isunordered' in the global namespace
> using ::isunordered;
>   ~~^
> 13 errors generated.
> make[2]: *** [build/interfaces/NTL-interface.lo] Error 1
> clang: error: no such file or directory: 
> 'build/interfaces/NTL-interface.lo'
> make[1]: *** [libflint-13.5.2.dylib] Error 1
> make: *** [library] Error 2
>
>
> and arb fails in the same way because it first tries to install flint.
>
> Andrew
>
>
>
>> (these are source-only, so this will build packages from source) 
>>
>>
>> On Tue, Oct 29, 2019 at 2:01 AM Andrew  wrote: 
>> > 
>> > I (stupidly) upgraded to XCode 11.1 on catalina. I have succeeded in 
>> compiling sage with python2, not python 3, on an imac but can't get it to 
>> compile on a macbook pro with fairly similar specs.I am using homebrew and 
>> have: 
>> > 
>> > ProductName:Mac OS X 
>> > ProductVersion:10.15 
>> > BuildVersion:19A603 
>> > Xcode 11.1 
>> > Build version 11A1027 
>> > 
>> > with gcc --version returning 
>> > 
>> > Configured with: 
>> --prefix=/Applications/Xcode.app/Contents/Developer/usr 
>> --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
>>  
>>
>> > Apple clang version 11.0.0 (clang-1100.0.33.8) 
>> > Target: x86_64-apple-darwin19.0.0 
>> > Thread model: posix 
>> > InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>>  
>>
>> > 
>> > When I try to compile sage is breaks with: 
>> > 
>> > * package: givaro-4.1.1 
>> >   log file: /usr/local/src/sage/logs/pkgs/givaro-4.1.1.log 
>> >   build directory: 
>> /usr/local/src/sage/local/var/tmp/sage/build/givaro-4.1.1 
>> > * package: ntl-11.3.2 
>> >   log file: /usr/local/src/sage/logs/pkgs/ntl-11.3.2.log 
>> >   build directory: 
>> /usr/local/src/sage/local/var/tmp/sage/build/ntl-11.3.2 
>> > 
>> > Sometimes I also get ntl failing to compile. I have compared the log 
>> files one the two machines but can't identify the problem. I attach the log 
>> files for givaro and ntl and the install.log from the machine that has the 
>> problem. Does anyone have any ideas how to fix this? 
>> > 
>> > Andrew 
>> > 
>> > -- 
>> > 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-...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/695c9caa-6efe-49ad-a05f-100c49be7a93%40googlegroups.com.
>>  
>>
>>
>

-- 
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] Re: Optional and experimental packages

[John H Palmieri]

Oops, I spoke too soon. Two more files had failures:

- sage -t --long src/sage/databases/stein_watkins.py  # 20 doctests failed
- sage -t --long src/sage/interfaces/frobby.py  # 12 doctests failed



On Monday, October 28, 2019 at 3:02:23 PM UTC-7, John H Palmieri wrote:
>
> With a Python 3 build of Sage on OS X 10.14.6, I decided to install as 
> many optional and experimental packages as I could. The results:
>
> *Optional:*
>
> - the following packages failed to build, and the reason wasn't completely 
> obvious:
>
> awali
> buckygen
> cbc
> gambit
> gdb
> mpi4py
>
> - the following packages failed because they (or their installation 
> scripts) are not compatible with Python 3:
>
> beautifulsoup
> brian
> guppy
> mercurial
> p_group_cohomology (but work is in progress)
> pyx
> scons
> trac
>
> - the following packages failed at first, but built after installing some 
> prerequisities:
>
> deformation — requires installation of mpir
> dot2tex — requires Graphviz
> rst2ipynb — requires pandoc
>
> - I skipped the following packages:
>
> atlas (installation is skipped on OS X)
> python2 (I wanted to use a pure Python 3 build)
>
> - Every other optional package built.
>
> *Question/Proposal:* do we demote the failed packages to experimental? 
> (Not deformation, dot2tex, or rst2ipynb, also not p_group_cohomology 
> because it is just about ready for py3, but the others.) I plan to do this 
> unless there are objections.
>
>
> *Experimental:*
>
> - the following failed to build:
>
> autotools
> cocoalib
> libtheora
> polymake
> qepcad
> scipoptsuite
> surf
> valgrind
>
> - the following succeeded:
>
> gap3
> lie
> modular_decomposition
> perl_term_readline_gnu
>
> polymake succeeded but only after installing the perl JSON package. (Why 
> is jupymake optional and polymake experimental? jupymake has polymake as a 
> dependency, and optional packages should not depend on experimental 
> packages.)
>
> - I skipped the following:
>
> compilerwrapper — when I install this, it breaks the Sage library: after 
> touching any .pyx file, "sage -b" or "make" fails with an error about ld.
>
>
> *Doctesting:*
>
> Then I ran `make ptestalllong`. There were lots of "internet" failures. 
> Otherwise:
>
> - failures in one file because of rst2ipynb
> - failures in two files because of dot2tex
> - failures in one file because of latex
> - failures in one file because of gap_packages (reported by Emmanuel 
> Charpentier on sage-release many times)
>
> Other than the internet problems, not too bad.
>
> -- 
> John
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e97d9f7d-7b76-45cc-ae4a-c29ebb617e5b%40googlegroups.com.

[sage-devel] Optional and experimental packages

[John H Palmieri]

With a Python 3 build of Sage on OS X 10.14.6, I decided to install as many 
optional and experimental packages as I could. The results:

*Optional:*

- the following packages failed to build, and the reason wasn't completely 
obvious:

awali
buckygen
cbc
gambit
gdb
mpi4py

- the following packages failed because they (or their installation 
scripts) are not compatible with Python 3:

beautifulsoup
brian
guppy
mercurial
p_group_cohomology (but work is in progress)
pyx
scons
trac

- the following packages failed at first, but built after installing some 
prerequisities:

deformation — requires installation of mpir
dot2tex — requires Graphviz
rst2ipynb — requires pandoc

- I skipped the following packages:

atlas (installation is skipped on OS X)
python2 (I wanted to use a pure Python 3 build)

- Every other optional package built.

*Question/Proposal:* do we demote the failed packages to experimental? (Not 
deformation, dot2tex, or rst2ipynb, also not p_group_cohomology because it 
is just about ready for py3, but the others.) I plan to do this unless 
there are objections.


*Experimental:*

- the following failed to build:

autotools
cocoalib
libtheora
polymake
qepcad
scipoptsuite
surf
valgrind

- the following succeeded:

gap3
lie
modular_decomposition
perl_term_readline_gnu

polymake succeeded but only after installing the perl JSON package. (Why is 
jupymake optional and polymake experimental? jupymake has polymake as a 
dependency, and optional packages should not depend on experimental 
packages.)

- I skipped the following:

compilerwrapper — when I install this, it breaks the Sage library: after 
touching any .pyx file, "sage -b" or "make" fails with an error about ld.


*Doctesting:*

Then I ran `make ptestalllong`. There were lots of "internet" failures. 
Otherwise:

- failures in one file because of rst2ipynb
- failures in two files because of dot2tex
- failures in one file because of latex
- failures in one file because of gap_packages (reported by Emmanuel 
Charpentier on sage-release many times)

Other than the internet problems, not too bad.

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/150bd508-b9b2-4953-aa50-cb27cc840b78%40googlegroups.com.

[CentOS] udev on CEntOS7 - can't get a match, looking for tips...

[John H Nyhuis]

The mtx binary requires my tape library to be assigned a sg# driver, but 
the kernel periodically renumbers the sg devices.  Normally, we would 
write a udev rule to manually assign a persistent name, but it looks 
like things have changed as I can't seem to get a match on CEntOS7.  I'd 
appreciate any feedback or pointers to help me get my rule working.  My 
two attempts are below.

cat /etc/udev/rules.d/90-local.rules

KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \
ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8"

SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \
ATTRS{model}=="Scalar i40-i80  ", SYMLINK:="sg8"

Neither rule above generates a match with udev, so I still have 
something wrong.  Right now the assignment is sg7 (but it's had other 
names in the past.

udevadm info --query=all --name=/dev/sg7
P: 
/devices/pci:00/:00:07.0/:04:00.0/:05:00.0/:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7
N: sg7
S: tape/by-id/scsi-1QUANTUM_D0H0112430_LLA
E: DEVLINKS=/dev/tape/by-id/scsi-1QUANTUM_D0H0112430_LLA
E: DEVNAME=/dev/sg7
E: 
DEVPATH=/devices/pci:00/:00:07.0/:04:00.0/:05:00.0/:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7
E: ID_MODEL=Scalar_i40-i80
E: ID_MODEL_ENC=Scalar\x20i40-i80\x20\x20
E: ID_REVISION=190G
E: ID_SCSI=1
E: ID_SCSI_SERIAL=QUANTUMD0H0112430_LLA
E: ID_SERIAL=1QUANTUM_D0H0112430_LLA
E: ID_SERIAL_SHORT=QUANTUM_D0H0112430_LLA
E: ID_TYPE=generic
E: ID_VENDOR=QUANTUM
E: ID_VENDOR_ENC=QUANTUM\x20
E: MAJOR=21
E: MINOR=7
E: SUBSYSTEM=scsi_generic
E: USEC_INITIALIZED=28815292891


Assigned and parent device listed below:
udevadm info -a -p `udevadm info -q path -n /dev/sg7`

   looking at device 
'/devices/pci:00/:00:07.0/:04:00.0/:05:00.0/:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7':
 KERNEL=="sg7"
 SUBSYSTEM=="scsi_generic"
 DRIVER==""

   looking at parent device 
'/devices/pci:00/:00:07.0/:04:00.0/:05:00.0/:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1':
 KERNELS=="8:0:0:1"
 SUBSYSTEMS=="scsi"
 DRIVERS=="ch"
 ATTRS{rev}=="190G"
 ATTRS{type}=="8"
 ATTRS{scsi_level}=="4"
 ATTRS{model}=="Scalar i40-i80  "
 ATTRS{state}=="running"
 ATTRS{unpriv_sgio}=="0"
 ATTRS{queue_type}=="none"
 ATTRS{iodone_cnt}=="0xe2"
 ATTRS{iorequest_cnt}=="0xe2"
 ATTRS{queue_ramp_up_period}=="12"
 ATTRS{device_busy}=="0"
 ATTRS{evt_capacity_change_reported}=="0"
 ATTRS{timeout}=="0"
 ATTRS{evt_media_change}=="0"
 ATTRS{ioerr_cnt}=="0x7"
 ATTRS{queue_depth}=="30"
 ATTRS{vendor}=="QUANTUM "
 ATTRS{evt_soft_threshold_reached}=="0"
 ATTRS{device_blocked}=="0"
 ATTRS{evt_mode_parameter_change_reported}=="0"
 ATTRS{evt_lun_change_reported}=="0"
 ATTRS{evt_inquiry_change_reported}=="0"
 ATTRS{dh_state}=="detached"
 ATTRS{iocounterbits}=="32"
 ATTRS{eh_timeout}=="10"


Would anyone mind pointing out the error in my udev rule or proposing a 
better way of getting a persistent sg device name?

-- 
Thanks in advance,

John H. Nyhuis
Desk: (206)-685-8334
jnyh...@uw.edu
Box 359461, 15th floor, 106
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [sage-devel] Switch to Python 3 by default

[John H Palmieri]

+1

On Saturday, October 26, 2019 at 5:27:51 PM UTC-7, vdelecroix wrote:
>
>
> https://trac.sagemath.org/ticket/28660 
>
>
> Le 26/10/2019 à 17:20, François Bissey a écrit : 
> > +1 
> > 
> >> On 27/10/2019, at 12:58 PM, Vincent Delecroix <20100.d...@gmail.com 
> > wrote: 
> >> 
> >> +1 
> >> 
> >> Le 26/10/2019 à 16:58, Volker Braun a écrit : 
> >>> Maybe I missed it, but I didn't find a ticket for that. I think now 
> would 
> >>> be a good time to flip the switch, though. Any thoughts? 
> >> 
> >> -- 
> >> 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-...@googlegroups.com . 
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/4a982d46-747e-abaf-a76a-c7f5764c363f%40gmail.com.
>  
>
> > 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6dae0b8e-0c85-4423-afd5-4302f2d89648%40googlegroups.com.

[sage-support] Re: failure to re-install ipython

[John H Palmieri]

On Friday, October 25, 2019 at 2:59:36 AM UTC-7, Dima Pasechnik wrote:
>
> in the Sage 9.0.beta2 I get 
>  
> [ipython-5.8.0] Successfully installed ipython-5.8.0 
> [ipython-5.8.0] Cleaning up... 
> [ipython-5.8.0] Removed build tracker '/tmp/pip-req-tracker-h6h22jg5' 
> [ipython-5.8.0] 
> [ipython-5.8.0] real 0m2.424s 
> [ipython-5.8.0] user 0m2.136s 
> [ipython-5.8.0] sys 0m0.398s 
> [ipython-5.8.0] Copying package files from temporary location 
> /mnt/opt/Sage/sage-dev/local/var/tmp/sage/build/ipython-5.8.0/inst to 
> /mnt/opt/Sage/sage-dev/local 
> [ipython-5.8.0] cp: not writing through dangling symlink 
> '/mnt/opt/Sage/sage-dev/local/./bin/ipython' 
> [ipython-5.8.0] 
>  
> [ipython-5.8.0] Error copying files for ipython-5.8.0. 
>
>  
>
> I had to apply 
>
> diff --git a/build/pkgs/ipython/spkg-install 
> b/build/pkgs/ipython/spkg-install 
> index 07a28f951c..dd2fcdc698 100644 
> --- a/build/pkgs/ipython/spkg-install 
> +++ b/build/pkgs/ipython/spkg-install 
> @@ -4,6 +4,7 @@ if [ "$SAGE_LOCAL" = "" ]; then 
> exit 1 
>  fi 
>
> +rm -f "$SAGE_LOCAL"/bin/ipython* 
>  cd src 
>
>  sdh_pip_install . 
> @@ -12,10 +13,3 @@ if [ $? -ne 0 ]; then 
>  echo >&2 "Error installing IPython" 
>  exit 1 
>  fi 
> - 
> -# add symlink if we are running on python3 
> -if python -c 'import sys; sys.exit(sys.version_info.major != 3)'; then 
> -cd "$SAGE_LOCAL"/bin 
> -rm -f ipython 
> -ln -s ipython3 ipython 
> -fi 
>
> to make it build. In particular the last chunk removed by this patch 
> looks as something outdated. 
>
> Any ideas? 
>

I just saw this problem today, too. I agree that the last chunk looks 
outdated. 

Just curious: what platform is this? 

-- 
John

-- 
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/b0be0cf0-7d8d-4d4b-b03a-e4a1db92611e%40googlegroups.com.

Re: [sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

On Thursday, October 24, 2019 at 10:57:09 AM UTC-7, Dima Pasechnik wrote:
>
> On Thu, Oct 24, 2019 at 6:48 PM Nils Bruin > 
> wrote: 
> > 
> > On Thursday, October 24, 2019 at 10:29:48 AM UTC-7, Nils Bruin wrote: 
> >> 
> >> 
> >> I guess via ctypes it would be possible too. 
> > 
> > 
> > Browsing the documentation, something like: 
> > 
> > libc=ctypes.cdll.LoadLibrary("libc.so.6") 
> > libc.fflush(0r) 
> > 
> > should work. And this should cause way less overhead than calling cython 
> (because we don't have to call a c compiler). Problem here of course is how 
> to make the "libc.so.6" cross-platform. 
>
> this is something that can be easily done at configure time, figuring 
> out the correct value for this string and putting it into 
> an environment variable. 
>

For one doctest, I don't think we want to bother with configure time and an 
environment variable. Both seem to work, but the cython solution looks 
better to me.
 

>
>
> > So perhaps the cython solution is better ... 
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/3d6e24b1-4ace-4b12-98ea-aa2b4ac70c99%40googlegroups.com.
>  
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/eddcc521-5dbc-4336-a63d-4419d3614ca2%40googlegroups.com.

Re: [sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

On Wednesday, October 23, 2019 at 9:49:56 PM UTC-7, Nils Bruin wrote:
>
> On Wednesday, October 23, 2019 at 2:47:54 PM UTC-7, John H Palmieri wrote:
>>
>>
>>
>> On Wednesday, October 23, 2019 at 1:41:35 PM UTC-7, Nils Bruin wrote:
>>>
>>> On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote:
>>>>
>>>>
>>>> That all looks very complicated.  Before I fixed the eclib source code 
>>>> the previous method did work, namely to flush stdout and stderr from the 
>>>> c/python wrapper code after calling any library function (in some cases 
>>>> this is certainly redundant, but in the case of eclib it was very hard for 
>>>> anyone other than me to know which library functions might spit out some 
>>>> error or warning message).  Somewhere in src/sage/libs/flint are the 
>>>> wrapper functions which need this.
>>>>
>>>>  Given that fflush is a system call, it probably has quite a serious 
>>> overhead. When the routine is meant to do I/O anyway, it's a fair price to 
>>> pay, but just flushing on the odd chance that a warning was generated could 
>>> very well be quite costly. For a low-level library like flint, that might 
>>> be too high a price. I think you want to test for performance regression 
>>> before working around lacking output flushes by flushing always.
>>>
>>
>> Is there a way to just flush output immediately after the relevant 
>> doctest? For the record, the doctest is
>>
>> FLINT memory errors do not crash Sage (:trac:`17629`)::
>>
>> sage: t^(sys.maxsize//2)
>> Traceback (most recent call last):
>> ...
>> RuntimeError: FLINT exception
>>
>> Wouldn't something like
>
> try:
> t^(sys.maxsize//2)
> except:
> sys.stdout.flush()
> raise
>
> do the trick, to ensure that the message gets flushed before the error 
> gets raised?
>
> shouldn't a message like that occur on sys.stderr, though?
>

The relevant print command in FLINT is

flint_printf("Exception (FLINT memory_manager). Unable to allocate 
memory.\n");

and the problem is fixed by adding 

fflush(stdout);

So maybe it should be on stderr, but it's not. Regarding 
sys.stdout.flush(), my understanding, as confirmed by my experience with 
this particular problem, is that this only flushes output coming from 
Python, not from external library calls.
 

>
>
>  
>
>> and the "..." is supposed to capture "Exception (FLINT memory_manager). 
>> Unable to allocate memory." This text is what needs to be flushed, because 
>> otherwise it may not appear here, instead appearing in the output of some 
>> later doctest. So if we can add something at the end of the doctest, an 
>> analogue of
>>
>> sage: sys.stdout.flush()
>> ...
>>
>> that could work and would not impact performance whenever FLINT is used.
>>
>> -- 
>> John
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/689a01d2-8291-47fd-9798-8b9d3e0d840d%40googlegroups.com.

Re: [sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

On Wednesday, October 23, 2019 at 1:41:35 PM UTC-7, Nils Bruin wrote:
>
> On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote:
>>
>>
>> That all looks very complicated.  Before I fixed the eclib source code 
>> the previous method did work, namely to flush stdout and stderr from the 
>> c/python wrapper code after calling any library function (in some cases 
>> this is certainly redundant, but in the case of eclib it was very hard for 
>> anyone other than me to know which library functions might spit out some 
>> error or warning message).  Somewhere in src/sage/libs/flint are the 
>> wrapper functions which need this.
>>
>>  Given that fflush is a system call, it probably has quite a serious 
> overhead. When the routine is meant to do I/O anyway, it's a fair price to 
> pay, but just flushing on the odd chance that a warning was generated could 
> very well be quite costly. For a low-level library like flint, that might 
> be too high a price. I think you want to test for performance regression 
> before working around lacking output flushes by flushing always.
>

Is there a way to just flush output immediately after the relevant doctest? 
For the record, the doctest is

FLINT memory errors do not crash Sage (:trac:`17629`)::

sage: t^(sys.maxsize//2)
Traceback (most recent call last):
...
RuntimeError: FLINT exception

and the "..." is supposed to capture "Exception (FLINT memory_manager). Unable 
to allocate memory." This text is what needs to be flushed, because otherwise 
it may not appear here, instead appearing in the output of some later doctest. 
So if we can add something at the end of the doctest, an analogue of

sage: sys.stdout.flush()
...

that could work and would not impact performance whenever FLINT is used.

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0f54c624-aa1b-4ea9-ac53-52a59aa63b90%40googlegroups.com.

Re: [sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

I found that and 
https://stackoverflow.com/questions/5081657/how-do-i-prevent-a-c-shared-library-to-print-on-stdout-in-python
 
and maybe other related items, but I couldn't figure out how to use them to 
fix this particular problem. Others will know what they're doing more than 
I do regarding a Python/Cython interface to an external library, so others 
might have more luck.



On Wednesday, October 23, 2019 at 12:41:21 PM UTC-7, Dima Pasechnik wrote:
>
> an internet search finds
>
> https://stackoverflow.com/questions/4178614/suppressing-output-of-module-calling-outside-library
>
> is it what would work for us?
>
> On Wed, 23 Oct 2019, 20:06 John H Palmieri,  > wrote:
>
>>
>>
>> On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote:
>>>
>>> On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri  
>>> wrote: 
>>> > I am writing to ask for help fixing a Python 3 problem. On some 
>>> platforms, there are Python 3 doctest failures in 
>>> > 
>>> > - libs/eclib/interface.py (#28454) 
>>>
>>> I believe that this has been fixed upstream, it has certainly been 
>>> reported by me. Are we using the latest eclib version? 
>>>
>>> > How do we fix this? Note that patching FLINT is not ideal, since it 
>>> won't help users who are using the system's version of the library. FLINT's 
>>> most recent release was in 2015, so I don't know how much we can expect 
>>> from upstream regarding new releases. So maybe the ideal solution would be 
>>> to get Python to flush the output from these external libraries. I don't 
>>> know how to do this; can anyone else help? 
>>>
>>> Ideally, the upstream library should properly flush when producing 
>>> output. They should use fflush (in C) or std::endl or std::flush (in 
>>> C++). I guess that Sage could also do the flushing whenever we return 
>>> from a library API call. 
>>>
>>
>> This problem arises with polynomial_rational_flint.pyx (on Ubuntu and 
>> Debian but not OS X, for whatever reason). See 
>> https://trac.sagemath.org/ticket/28334. How can we do this flushing? The 
>> only other solution I can see is to patch FLINT, but this won't work if 
>> users are using a system-wide installation of FLINT.
>>
>> Other flushing problems appear at #28454, now since fixed with an upgrade 
>> to eclib, and #28622: pure Python code, so adding some `sys.stdout.flush()` 
>> commands cleared up that problem. But the FLINT problem remains.
>>
>> -- 
>> John
>>
>> -- 
>> 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/bc6e7a4a-c8a3-4511-94ec-718e0126b19e%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/bc6e7a4a-c8a3-4511-94ec-718e0126b19e%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/73733782-6706-4839-a1ec-1477287dd112%40googlegroups.com.

Re: [sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote:
>
> On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri  > wrote: 
> > I am writing to ask for help fixing a Python 3 problem. On some 
> platforms, there are Python 3 doctest failures in 
> > 
> > - libs/eclib/interface.py (#28454) 
>
> I believe that this has been fixed upstream, it has certainly been 
> reported by me. Are we using the latest eclib version? 
>
> > How do we fix this? Note that patching FLINT is not ideal, since it 
> won't help users who are using the system's version of the library. FLINT's 
> most recent release was in 2015, so I don't know how much we can expect 
> from upstream regarding new releases. So maybe the ideal solution would be 
> to get Python to flush the output from these external libraries. I don't 
> know how to do this; can anyone else help? 
>
> Ideally, the upstream library should properly flush when producing 
> output. They should use fflush (in C) or std::endl or std::flush (in 
> C++). I guess that Sage could also do the flushing whenever we return 
> from a library API call. 
>

This problem arises with polynomial_rational_flint.pyx (on Ubuntu and 
Debian but not OS X, for whatever reason). See 
https://trac.sagemath.org/ticket/28334. How can we do this flushing? The 
only other solution I can see is to patch FLINT, but this won't work if 
users are using a system-wide installation of FLINT.

Other flushing problems appear at #28454, now since fixed with an upgrade 
to eclib, and #28622: pure Python code, so adding some `sys.stdout.flush()` 
commands cleared up that problem. But the FLINT problem remains.

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bc6e7a4a-c8a3-4511-94ec-718e0126b19e%40googlegroups.com.

Re: [sage-devel] Question about deprecation warnings: when do they appear in doctests vs. real life?

[John H Palmieri]

Okay, that makes sense. I thought I had seen deprecation warnings from 
basic commands issued at the "sage:" prompt, but I must be misremembering.

  John


On Saturday, October 19, 2019 at 1:20:15 PM UTC-7, David Roe wrote:
>
> The reason that the warning isn't printed is that the stacklevel is set to 
> 4 by default in order to tell the user where the Integer('012') is 
> occurring.  When you type '012' directly into the command line, the stack 
> isn't deep enough and no warning is printed.  You do see a warning if you 
> write a function that uses it:
>
> sage: def hello():
> : Integer('012')
> : 
> sage: hello()
> /home/sage/sage-8.8/src/bin/sage-ipython:1: DeprecationWarning: use 0o as 
> octal prefix instead of 0
> If you do not want this number to be interpreted as octal, remove the 
> leading zeros.
> See http://trac.sagemath.org/17413 for details.
>   #!/usr/bin/env sage-python23
>
> I think the idea is that if a user's typing interactively then they don't 
> need a deprecation warning (since the behavior currently works).  It's more 
> important to show a user a warning if they have the deprecated behavior in 
> a function they've written.
> David
>
> On Sat, Oct 19, 2019 at 2:56 PM John H Palmieri  > wrote:
>
>> Here is a doctest from sage/rings/integer.pyx:
>>
>> sage: Integer('012')
>> doctest:...: DeprecationWarning: use 0o as octal prefix instead 
>> of 0
>> If you do not want this number to be interpreted as octal, remove 
>> the leading zeros.
>> See http://trac.sagemath.org/17413 for details.
>> 10
>>
>> But if I run the command Integer('012')from the command line (in a newly 
>> started Sage session) or the Jupyter notebook, no deprecation warning is 
>> printed. Same if I just evaluate 012. Is this a bug? It seems to defeat 
>> the purpose of the deprecation warning, which is to actually warn people 
>> that a feature is going away, not just to provide extra characters in 
>> docstrings and the reference manual.
>>
>> -- 
>> John
>>
>> -- 
>> 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/6569111a-90ac-436f-8ecb-2976a9b32ab3%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-devel/6569111a-90ac-436f-8ecb-2976a9b32ab3%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bc924a61-4e75-4733-8b78-eedf61463bac%40googlegroups.com.

[sage-devel] Question about deprecation warnings: when do they appear in doctests vs. real life?

[John H Palmieri]

Here is a doctest from sage/rings/integer.pyx:

sage: Integer('012')
doctest:...: DeprecationWarning: use 0o as octal prefix instead of 0
If you do not want this number to be interpreted as octal, remove 
the leading zeros.
See http://trac.sagemath.org/17413 for details.
10

But if I run the command Integer('012')from the command line (in a newly 
started Sage session) or the Jupyter notebook, no deprecation warning is 
printed. Same if I just evaluate 012. Is this a bug? It seems to defeat the 
purpose of the deprecation warning, which is to actually warn people that a 
feature is going away, not just to provide extra characters in docstrings 
and the reference manual.

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6569111a-90ac-436f-8ecb-2976a9b32ab3%40googlegroups.com.

Re: [sage-devel] Re: sagemath 8.9 is not complied on macOS Catalina with python3

[John H Palmieri]

On Friday, October 18, 2019 at 10:25:07 AM UTC-7, Dima Pasechnik wrote:
>
> Hi John, 
>
> On Fri, Oct 18, 2019 at 5:08 PM John H Palmieri  > wrote: 
> > 
> > I have compiled it without any problems. You should not be using gcc 
> from homebrew, but rather the version of gcc installed by Xcode or its 
> command-line tools. That might help. (You should install the homebrew gcc 
> package to get gfortran, but at least for me, installing homebrew's gcc 
> installed /usr/local/bin/gcc-9, not /usr/local/bin/gcc. The presence of 
> /usr/local/bin/gcc-9 is fine, the presence of /usr/local/bin/gcc is not.) 
>
> If I followed all this up correctly, on Catalina Xcode 11.0 works, but 
> Xcode 11.1 does not. 
> What Xcode version are you using? 
>

11.1. "xcode-select --version" says "xcode-select version 2370". "gcc 
--version" says

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin19.0.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

I also have homebrew's gcc and gforfran installed. I downloaded homebrew 
when I had a beta version of Catalina, about a week before the actual 
Catalina release. Once Catalina was released, I did "brew uninstall gcc" 
and then "brew install gcc" to test it out, and it built gcc and gfortran 
from scratch. I then built Sage using that.

This is not on my main computer, so I didn't mind if things went wrong. I 
was pleasantly surprised that everything worked.
 

> > 
> > 
> > On Friday, October 18, 2019 at 8:07:11 AM UTC-7, Junwei Wang wrote: 
> >> 
> >> Besides, could the SAGE team officially release binary with Python 3 
> (although it is not stable), since we are force to use python3 in many 
> cases and it is painful to compile by user themselves? 
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/5abd9f2c-0905-4565-93c2-aa64ecf84d80%40googlegroups.com.
>  
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e1eeb15e-f207-4064-9fde-7c7e48871e6a%40googlegroups.com.

[sage-devel] Re: sagemath 8.9 is not complied on macOS Catalina with python3

[John H Palmieri]

I have compiled it without any problems. You should not be using gcc from 
homebrew, but rather the version of gcc installed by Xcode or its 
command-line tools. That might help. (You should install the homebrew gcc 
package to get gfortran, but at least for me, installing homebrew's gcc 
installed /usr/local/bin/gcc-9, not /usr/local/bin/gcc. The presence of 
/usr/local/bin/gcc-9 is fine, the presence of /usr/local/bin/gcc is not.)


On Friday, October 18, 2019 at 8:07:11 AM UTC-7, Junwei Wang wrote:
>
> Besides, could the SAGE team officially release binary with Python 3 
> (although it is not stable), since we are force to use python3 in many 
> cases and it is painful to compile by user themselves?
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5abd9f2c-0905-4565-93c2-aa64ecf84d80%40googlegroups.com.

Re: Yahoo Groups going away

[John H. Reinhardt via cctalk]

On 10/17/2019 9:49 PM, Ali via cctalk wrote:

The guy who runs groups.io is the one who created onelist, which became
e-groups, with got swallowed up by Yahoo!, and then he left.

He knows how to do it.  People who have switched over seem happy with
it.
BUT, does he have an appropriate level of resources to handle THAT much
traffic?


I saw a posting about this on one of the groups I am in (XXCopy) and it
seems as if groups.io is not free. At least there was talk of a $110
payment.

-Ali


The groups are free as long as you use less than 1GB of storage.  More storage 
costs.  Unfortunately, since this past February, you also have to pay in order 
to have Groups.IO do the moving of your messages, files and photos.  No freebie 
for that anymore.

--
John H. Reinhardt

[sage-devel] Need help with Python 3, doctesting framework, and patchbot

[John H Palmieri]

With a Python 3 build of Sage, there are three files which exhibit failures 
only (or primarily?) when running the Sage patchbot. This is being tracked 
at https://trac.sagemath.org/ticket/28622. Can anyone help figure out the 
problem and how to fix it? To see the problem, cd to SAGE_ROOT, run Python 
(either 2 or 3) and do this:

>>> import subprocess, os, sys
>>> tee = subprocess.Popen(["tee", 'LOGFILE.log'], stdin=subprocess.PIPE)
>>> os.dup2(tee.stdin.fileno(), sys.stdout.fileno())
>>> os.dup2(tee.stdin.fileno(), sys.stderr.fileno())
>>> os.system('/path/to/sage/sage -t src/sage/repl/attach.py')

What's going on?

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a8efcc61-69d8-4b1d-9f7b-be7d8855dcf3%40googlegroups.com.

Re: [sage-devel] OSX Catalina works

[John H Palmieri]

A few days ago, after the Catalina release, I used Homebrew to build gcc, 
and it worked. Well, it built from source, which took a while, but it built 
a version of gfortran which worked well enough to build Sage. (As far as I 
know, it's completely functional, but the only reason I install gfortran is 
to be able to build Sage.)


On Sunday, October 13, 2019 at 7:04:57 AM UTC-7, Dima Pasechnik wrote:
>
> the fact that Homebrew is not yet ready for 10.15 speaks for itself.
>
> On Sun, 13 Oct 2019, 14:56 David Joyner, > 
> wrote:
>
>>
>>
>> On Sun, Oct 13, 2019 at 4:26 AM Volker Braun > > wrote:
>>
>>> I just upgraded the OSX buildbot and Sage works in case anybody is 
>>> wondering. This is the first time in years that the latest OSX release 
>>> doesn't introduce major toolchain issues and/or scrambles the filesystem, 
>>> hope this starts a trend ;-) 
>>>
>>
>> I can't get the pre-10.15 binaries to work (error in executing python 
>> 2.7), 
>> nor can I get the source to compile on 10.15.1 (stalls out on compiling
>> gfortran-7.4.0). I haven't tried the app version though.
>> This is on a late 2013 macbook pro.
>>
>>  
>>
>>> -- 
>>> 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-...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/069eafdb-e5c7-42cc-a72d-d9ff11b1bf53%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CAEQuuAW6EeWi91CH763omMKn5Obq12m5_t5usA8tUYvOvPKVEw%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6a3e69a5-fd42-4965-a6fe-4a24ee1e8567%40googlegroups.com.

Re: [sage-support] SageMath installation in macOS Catalina

[John H Palmieri]

On Wednesday, October 9, 2019 at 4:51:48 AM UTC-7, David Joyner wrote:
>
>
>
> On Wed, Oct 9, 2019 at 7:42 AM Dima Pasechnik  > wrote:
>
>>
>>
>> On Wed, Oct 9, 2019 at 6:34 AM David Joyner > > wrote:
>>
>>>
>>>
>>> On Wed, Oct 9, 2019 at 7:14 AM Dima Pasechnik >> > wrote:
>>>
 Hi,

 On Wed, Oct 9, 2019 at 6:03 AM George > 
 wrote:

> Hi David,
>
> Thanks for the update and information.
>
> building from source should still work.
 Did you try this ?

>>>
>>> I did. It chokes on the gfortran build:
>>>
>>> ...
>>>
>>> [gfortran-7.4.0] make[7]: *** [gets-chk.lo] Error 1
>>>
>>> [gfortran-7.4.0] make[6]: *** [all] Error 2
>>>
>>> [gfortran-7.4.0] make[5]: *** [all-target-libssp] Error 2
>>>
>>> [gfortran-7.4.0] make[4]: *** [all] Error 2
>>>
>>> [gfortran-7.4.0] 
>>> 
>>>
>>> [gfortran-7.4.0] Error building gfortran-7.4.0
>>>
>>> [gfortran-7.4.0] 
>>> 
>>>
>>>
>>>  
>>>
>> is there Homebrew for  Catalina?
>> Then one can use its gfortran.
>>
>>
> I googled around. Apparently the answer is no
> (or not as of a few days ago anyway).
>

On a recent beta release of Catalina, I used homebrew to install gfortran, 
and it went fine, allowing me to build Sage from scratch. I haven't yet 
tried with the actual release of Catalina, but I will soon.

  John

 

>  
>
>>
>>
 Dima

> G
>
> On Wednesday, October 9, 2019 at 1:00:37 PM UTC+2, David Joyner wrote:
>>
>>
>>
>> On Wed, Oct 9, 2019 at 6:45 AM George  wrote:
>>
>>> Hi,
>>>
>>> I upgraded to the new macOS Catalina and SageMath won't install. I 
>>> get errors like "python2.7 cannot be opened because the developer 
>>> cannot be 
>>> verified" and for numerous other components as well. 
>>>
>>> Is anyone having the same problem? Any tips, advice or ideas on what 
>>> is going on and how to fix this?
>>>
>>>
>> I can confirm this issue. The problem is also discussed in the thread
>>
>> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/sage-support/4dUg8mbiDYw/u5o-U9QBCAAJ
>> That's all I know.
>>  
>>
>>> Thanks a lot,
>>> G
>>>
>>> -- 
>>> 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/e69a4235-ec1b-465e-98da-635ed8be1b23%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-s...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/1cd586e5-35af-4e39-9322-8e055c144601%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-s...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-support/CAAWYfq0ZBO74cNDnkb33ywH7KkGUNci%3DMxXm5Dsoq5ak-mWb9Q%40mail.gmail.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-s...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-support/CAEQuuAWOOuPVgzgGdysYwz3oJ%3DxxV%3DNvj-ePKH__CYTe3x0p%2Bg%40mail.gmail.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-s...@googlegroups.com .
>> To view this discussion on the web visit 
>> 

Re: [sage-devel] scipy fails to build Sage 8.9 - MacOS 10.14.6

[John H Palmieri]

On OS X, Sage by default should use the system's "gcc" (which is actually 
clang), so it's okay to not have a symlink connecting gcc-9 to gcc in 
/usr/local/bin. What you really need is /usr/local/bin/gfortan, and 
homebrew should provide that.

  John


On Tuesday, October 8, 2019 at 3:56:24 PM UTC-7, Zachary Scherr wrote:
>
> Hi Dima,
>
>I have, but I noticed something interesting which is that gcc and g++ 
> are no longer symlinked in my /usr/local/bin.  I have gcc-9 and g++-9 in 
> there, but when I try "which gcc" and "which g++" I get /usr/bin/gcc and 
> /usr/bin/g++ which are the versions installed by command line tools.  This 
> is making me even more confused because sage didn't even attempt to build 
> with the version of gcc installed by homebrew.
>
>I'm currently retesting with gcc and g++ symlinked to the new version. 
>  I'll let you know if I have any success.
>
> Thanks,
> Zach  
>
> On Tuesday, October 8, 2019 at 4:25:23 PM UTC-4, Dima Pasechnik wrote:
>>
>> did you try updating homebrew?
>>
>> I think that what ultimately helped Ben to get a working gfortran, and 
>> correctly build whatever scipy's dependency is causing the problem.
>>
>>
>> On Tue, Oct 8, 2019 at 3:17 PM Zachary Scherr  wrote:
>>
>>> In an attempt to add openssl to sage I ran: sage -i openssl && sage -f 
>>> python2 (which I've done successfully in every previous version of Sage 
>>> 8.x).
>>>
>>> The sage -f python2 failed while trying to build scipy-1.2.0.  This may 
>>> be related to Ben's post 
>>> https://groups.google.com/forum/#!topic/sage-devel/40E66JVHhW8 since it 
>>> also failed with the message
>>>
>>> ld: library not found for -lSystem
>>>
>>> I too have gcc installed through homebrew, but I also tried removing it 
>>> and installing gfortran separately and ended up with the same error.  I've 
>>> attached the log file, anyone know what's going on?
>>>
>>>
>>>
>>> -- 
>>> 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-...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/5a356d10-a069-487a-a75c-ace33ba11f07%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2c09ac1e-466b-49e2-828b-01e24cdb31f9%40googlegroups.com.

[sage-devel] Package installation/uninstallation confusion

[John H Palmieri]

I have been testing new versions of Simon King's p-group cohomology 
package. The current version doesn't work with Python 3, and he has been 
working (#28414) to fix this. My workflow:


   1.  check out his git branch
   2.  run ./sage -f -c p_group_cohomology
   3.  report any issues
   4.  check out develop branch


Here is the problem: if step 2 works (which it has been recently), then 
`build/make/Makefile` gets modified, adding p_group_cohomology to the list 
of installed packages. When I switch back to the develop branch, then 
(since I am using a Python 3 build of Sage), Sage doesn't build any more, 
because it tries to build the broken version of the p_group_cohomology 
package. So then I do

   - "make p_group_cohomology-clean"

but this does not change `build/make/Makefile` and so it does not fix the 
problem. I can either edit the Makefile by hand or rerun ./configure. So 
here are some questions:

   - Is "sage -i PKG" or "sage -f PKG" the preferred way to install an 
   optional package? That's what our Developer's Guide says. Or should I be 
   using "make PKG", which does not modify "build/make/Makefile"?
   - Assuming I should keep using "sage -f PKG", should there be an 
   analogous command which uninstalls and then rebuilds the Makefile? Or 
   should "make PKG-clean" itself rebuild the Makefile?

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8580c565-d127-4b91-ac16-c8ab7514%40googlegroups.com.

Re: [sage-devel] Re: Build failure at matplotlib-2.2.4 and sagenb-1.1.2 on OS X

[John H Palmieri]

Could you also trying using Homebrew to install gfortran?


On Wednesday, September 25, 2019 at 12:09:55 PM UTC-7, Ben Salisbury wrote:
>
> Ok, I tried the Homebrew route, and still the build failed.  First, the 
> computer successfully executed the following:
>
> brew install dimpase/science/flint
> brew install dimpase/science/arb
> brew tap brewsci/bio
> brew install matplotlib
>
> Then I tried to build Sage again, after a distclean, and another 
> matplotlib error came up.  Log file is attached.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/addaf860-2918-4a01-b41f-c8a70110efd3%40googlegroups.com.

[sage-devel] Re: Build failure at matplotlib-2.2.4 and sagenb-1.1.2 on OS X

[John H Palmieri]

On Tuesday, September 24, 2019 at 10:12:17 AM UTC-7, Ben Salisbury wrote:
>
> Hi,
>
> I'm attempting to build Sage from the develop branch on a new office 
> computer running OS X 10.14.6.  I've installed Xcode and Command Line Tools 
> (or at least I thought I had), and I'm getting a build failure at 
> sagenb-1.1.2.  The log files for sagenb-1.1.2 and for matplotlib-2.2.4.p0 
> have been attached.  Any ideas on how to fix?
>
> Ben
>

matplotlib is complaining about png, so you could try "./sage -f libpng". 
(It should have been installed already, but maybe something went wrong.) 
Then try "make" again.

The sagenb error says things like

>
> The full traceback has been saved in 
> /var/folders/d0/bbf0zvnn43b4_fhtkznp_yycgp/T/sphinx-err-ZfIXOy.log, if 
> you want to report the issue to the developers.
>

Can you post that file?

By the way, does "git" work from the command-line? How about "gcc"? I just 
recently did a system upgrade on OS X, and I had to rerun Xcode to get the 
command-line tools to function — it wanted me to click on a licensing 
agreement or something like that.

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/04c4706c-f5d1-42a7-b3db-abdceef51b29%40googlegroups.com.

[RBW] Re: All Rounder

[John H.]

Beautiful build. I've been thinking about running Campy ergo's of that 
generation on my Sam. What's the jtek/cassette setup you have? How's it 
shifting?

John in Cambridge

On Tuesday, September 24, 2019 at 2:32:36 AM UTC-4, Joe Bernard wrote:
>
> Here's the first shots of my new-to-me A/R sans front fender and rack, and 
> before I upright it with Boscos. It's a bummer I can't use those sweet 
> carbon Campy brifters, but alas my arthritic wrists won't put up with drops 
> anymore. 
>
> I'm curious about the sizing. The early Reader geometry chart doesn't 
> match it at all, this one has a 52cm ST, 55cm TT, which mimics the 52cm 
> Bstone XO-1. Based on the serial number (what I can see of it) I believe 
> this was built in 1997, did Waterford ever do custom A/Rs for Riv? 
>
> Joe Bernard
> Novato CA.  
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/9d7747cb-ab9a-4665-a4fe-8fc46cd64955%40googlegroups.com.

[RBW] Re: All Rounder

[John H.]

Beautiful build. I was thinking of running a similar shimergo setup on my Sam. 
What jtek + cassette combo are you running?

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/04befabe-5ed8-4e0a-acd8-c58d96389a8f%40googlegroups.com.

[sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

[John H Palmieri]

+1 for threejs

I tried to compare the two: in a single Jupyter notebook, I plotted the 
same function with both viewers. threejs produced the plot faster, and it 
was snappier when rotating, zooming, etc. (This is with both Firefox and 
Safari on OS X.) Same from the command-line: the threejs window in my 
browser was faster to use than the jmol java app. The jmol app may have 
more features, but since we aren't talking about eliminating jmol, it will 
still be available as a possible viewer for people who need those features.

  John


On Monday, September 23, 2019 at 4:51:23 AM UTC-7, Eric Gourgoulhon wrote:
>
> Dear Sage-dev,
>
> This is a poll to make three.js (https://threejs.org/) the default 3d 
> viewer
> in Sage, in replacement of Jmol (https://sourceforge.net/projects/jmol/).
>
> Indeed, thanks to the work of Paul Masson, the three.js 3d viewer is doing 
> a
> very good job in displaying Sage 3d plots, as you can see in these examples
> taken from Sage reference's manual:
>
> https://nbviewer.jupyter.org/github/egourgoulhon/SageMathTest/blob/master/Worksheets/sage_reference_threejs.ipynb
>
> You can rotate/zoom the 3d view with the mouse and, by clicking on the 
> small black
> arrow at the bottom right of the view, you can download a png screenshot.
>
> Other examples of three.js rendering can be found in this notebook devoted 
> to
> anti de Sitter space:
>
> https://nbviewer.jupyter.org/github/sagemanifolds/SageManifolds/blob/master/Notebooks/SM_anti_de_Sitter.ipynb
>
> For more information about the three.js renderer in Sage, see
> https://doc.sagemath.org/html/en/reference/plot3d/threejs.html
>
> The discussion about having three.js as the default viewer is taking place 
> in
> the ticket
> https://trac.sagemath.org/ticket/22408
> This ticket also contains the git branch to perform the change if decided.
>
> Here is a discussion summary: in favor of three.js, we have
>
> - three.js, which is based on the WebGL API, displays 3d plots faster than
>   Jmol, and with a better quality
>
> - 3d plots rendered with three.js can be publicly shared via
>   nbviewer.jupyter.org, contrary to those rendered with Jmol, which 
> appear as
>   blank spaces, cf. this test notebook:
>   
> https://nbviewer.jupyter.org/github/egourgoulhon/SageMathTest/blob/master/Worksheets/test_3d_view.ipynb
>
> - three.js enables to label the plot axes (via the option 'axes_labels', 
> the default
>   of which is ['x', 'y', 'z']); on the opposite, there are no labels on 
> Jmol
>   plots and the option 'axes_labels' is ineffective, which looks like a 
> serious
>   drawback for a mathematical software...
>
> - Jmol causes many troubles to Sage packagers (see #22408 
>  for details);
>   for instance in Sage 8.8 console, Jmol display is broken on recent
>   Debian-based distros (e.g. Debian Buster and Ubuntu 18.04), due to a JRE
>   issue; fortunately this is fixed by 
> https://trac.sagemath.org/ticket/25026
>
> On the con side, there are
>
> - the current lack of non-interactive conversion of three.js views to 
> static
>   png figures (in interactive mode, the black arrow mentioned above does 
> the
>   job). As a result, the png figures in the reference manual will still be
>   generated with Jmol, as proposed in #22408 
> 
>
> - some minor opacity issues (see #22408 
>  for details)
>
>
> Given the above elements, please vote!
>
> Eric. 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7648af8f-71f2-46a7-ad7d-b6deab846d5e%40googlegroups.com.

Re: [sage-release] Sage 8.9.rc0 released

[John H Palmieri]

On Thursday, September 12, 2019 at 12:30:34 PM UTC-7, Dima Pasechnik wrote:
>
> On Thu, Sep 12, 2019 at 5:55 PM John Cremona  > wrote: 
> > 
> > On ubuntu, upgrade from previous beta, python3 configured: make 
> ptestlong succeeds except for 
> > 
> > sage -t --long --warn-long 81.2 src/sage/libs/gap/element.pyx  # 147 
> doctests failed 
> > 
>
> this looks like a mis-build of sorts. 
>
> Maybe also some crud in ~/.sage/, stale GAP workspace, maybe... 
> Could you try moving it out of the way and re-run the test? 
>
> By the way, I have a fun error if I switch from Python3 to Python2 and 
> re-build, 
> also coming from something in ~/.sage (it goes away after I remove 
> ~/.sage/) 
>
> File "src/sage/symbolic/maxima_wrapper.py", line 81, in 
> sage.symbolic.maxima_wrapper.MaximaWrapper.__getattr__ 
> Failed example: 
> s.completions('u.airy_',globals()) 
> Expected: 
> ['u.airy_ai', 'u.airy_bi', 'u.airy_dai', 'u.airy_dbi'] 
> Got: 
> [u'u.airy_ai', u'u.airy_bi', u'u.airy_dai', u'u.airy_dbi'] 
>
> I guess iPython hard-wires some stuff for Python3, and it's not good 
> for Python2... 
>
>
It's odd that this would come from something in ~/.sage. I typically have 
multiple builds of Sage in different directories, some from scratch, some 
upgrades, some Python 2, some Python 3. They all share the same ./sage 
(that's the default behavior, right? I haven't set DOTSAGE), and I've never 
see this error.

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/19bc5e84-5792-49ea-8808-5ae3ad8ea819%40googlegroups.com.

Re: [sage-release] Sage 8.9.beta9 released

[John H Palmieri]

On Friday, September 6, 2019 at 3:13:07 AM UTC-7, E. Madison Bray wrote:
>
> On Fri, Sep 6, 2019 at 11:36 AM E. Madison Bray  > wrote: 
> > 
> > Consistently getting a test failure on Cygwin related to some oddity in 
> GAP: 
> > 
> > sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py 
> > ** 
> > File "src/sage/tests/cmdline.py", line 535, in 
> > sage.tests.cmdline.test_executable 
> > Failed example: 
> > out 
> > Expected: 
> > '120\n' 
> > Got: 
> > "you can 'quit;' to quit to outer loop, or\nyou can 'return;' to 
> continue\n" 
> > ** 
> > File "src/sage/tests/cmdline.py", line 537, in 
> > sage.tests.cmdline.test_executable 
> > Failed example: 
> > err.replace('gap: halving pool size.', '').strip() 
> > Expected: 
> > '' 
> > Got: 
> > 'Error,  must not contain \'\\\' or \':\' at 
> > /home/embray/src/sagemath/sage/local/share/gap/lib/files.gi:53 called 
> > from\nfunc( C[i] ) at 
> > /home/embray/src/sagemath/sage/local/share/gap/lib/coll.gi:665 called 
> > from\nList( GAPInfo.DirectoriesSystemPrograms, Directory \n ) at 
> > /home/embray/src/sagemath/sage/local/share/gap/lib/files.gd:420 called 
> > from\n(  )\n called 
> > from read-eval loop at 
> > 
> /home/embray/src/sagemath/sage/local/share/gap/pkg/alnuth-3.1.1/defs.g:10\nbrk>
>  
>
> > 120\nbrk>' 
> > ** 
> > 1 item had failures: 
> >2 of 251 in sage.tests.cmdline.test_executable 
> > [250 tests, 2 failures, 273.09 s] 
> > -- 
> > sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py  # 2 doctests 
> failed 
> > -- 
> > 
> > Can't be sure yet that it isn't just a weird, localized issue in my 
> > installation.  Will investigate. 
>
> Yes, that's all it was.  I had a PATH entry with a \ in it, thanks to 
> conda still being a bit buggy on Cygwin :)  Conversely, I don't think 
> GAP should blow up in this case either.  So, two issues to file 
> \o/ 
>


I see this failure if I have a PATH entry with a space in it, as in 
"/Users/palmieri/path\ with\ space/". GAP should be able to handle this, I 
think.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b786f72f-134d-4eac-bb74-12838be0f6aa%40googlegroups.com.

[sage-release] Re: Sage 8.9.rc0 released

[John H Palmieri]

On Wednesday, September 11, 2019 at 4:36:46 PM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>

OS X + Python 3: All tests passed!

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/ed35e75d-3bc9-4b7e-856f-1435724ead1f%40googlegroups.com.

Re: [sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote:
>
> On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri  > wrote: 
> > I am writing to ask for help fixing a Python 3 problem. On some 
> platforms, there are Python 3 doctest failures in 
> > 
> > - libs/eclib/interface.py (#28454) 
>
> I believe that this has been fixed upstream, it has certainly been 
> reported by me. Are we using the latest eclib version? 
>

John Cremona is part of the discussion at #28454, and I assume he knows the 
current state of eclib. I'll let him speak to this.


> > How do we fix this? Note that patching FLINT is not ideal, since it 
> won't help users who are using the system's version of the library. FLINT's 
> most recent release was in 2015, so I don't know how much we can expect 
> from upstream regarding new releases. So maybe the ideal solution would be 
> to get Python to flush the output from these external libraries. I don't 
> know how to do this; can anyone else help? 
>
> Ideally, the upstream library should properly flush when producing 
> output. They should use fflush (in C) or std::endl or std::flush (in 
> C++). 


I can confirm that patching flint to use fflush fixes the problem, and 
similarly for eclib. Patching is not ideal, though, since we are trying to 
move to better support libraries installed system-wide. 
 

> I guess that Sage could also do the flushing whenever we return 
> from a library API call. 
>

Sounds okay to me, but I don't know how to do it. My impression is that 
`sys.stdout.flush()` just flushes Python output, not output coming from 
external libraries.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4df27a03-a625-47bb-ad4c-f2580f4b1298%40googlegroups.com.

[sage-devel] Python 3 and flushing output from external libraries

[John H Palmieri]

I am writing to ask for help fixing a Python 3 problem. On some platforms, 
there are Python 3 doctest failures in

- libs/eclib/interface.py (#28454)
- rings/polynomial/polynomial_rational_flint.pyx (#28334)

and both occur for the same reason: warning messages printed by C or C++ 
libraries are not appearing when they are supposed to, but rather some time 
later. So for example, in

 FLINT memory errors do not crash Sage (:trac:`17629`)::

 sage: t^(sys.maxsize//2)
 Traceback (most recent call last):
 ...
 RuntimeError: FLINT exception

the "..." should capture a message "Exception (FLINT memory_manager). 
Unable to allocate memory", and when you run it from the command line, this 
message appears. When running doctests, though, with Python 3 only and on 
some platforms only (debian, ubuntu — don't know why), this message only 
pops up at some later time, leading to this:

Failed example:
   G = f.galois_group(); G
Expected:
   Transitive group number 5 of degree 4
Got:
   Exception (FLINT memory_manager). Unable to allocate memory.
   Transitive group number 5 of degree 4


The `f.galois_group()` command has nothing to do with this error, but something 
about it triggers the old output to be flushed.

How do we fix this? Note that patching FLINT is not ideal, since it won't 
help users who are using the system's version of the library. FLINT's most 
recent release was in 2015, so I don't know how much we can expect from 
upstream regarding new releases. So maybe the ideal solution would be to 
get Python to flush the output from these external libraries. I don't know 
how to do this; can anyone else help?


I'm also curious about what's causing the problem. Is it a bug in Python 3? If 
not, is this change in behavior documented anywhere? Why does it only appear on 
some platforms?

-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6e394ce1-5c04-40a9-8f17-590a1c4f5e1b%40googlegroups.com.

[sage-release] Re: Sage 8.9.beta9 released

[John H Palmieri]

With a Python 3 build on OS X, I get a sporadic failure in 
numerical/linear_tensor_element.pyx — it fails not every time, but at least 
half the time. As far as I can tell, this is due to #27587 (that is, I get 
failures with 8.9.beta8 + that ticket, but not with 8.9.beta8), but I don't 
understand why.

$ ./sage -t src/sage/numerical/linear_tensor_element.pyx 
too many failed tests, not using stored timings
Running doctests with ID 2019-09-03-15-54-33-30edf809.
Git branch: develop
Using --optional=build,dochtml,python2,sage
Doctesting 1 file.
glp_free: memory allocation error
Error detected in file env/alloc.c at line 72

0   signals.cpython-37m-darwin.so   0x0001026c50ba print_backtrace 
+ 58
...
  [snip]
...
56  libsystem_pthread.dylib 0x7fff667b940d thread_start + 13

Unhandled SIGABRT: An abort() occurred.
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.

sage -t src/sage/numerical/linear_tensor_element.pyx
Killed due to abort
**
Tests run before process (pid=20158) failed:
sage: mip. = MixedIntegerLinearProgram('ppl')   # base ring is QQ ## 
line 6 ##
sage: lt = x[0] * vector([3,4]) + 1;   lt ## line 7 ##
(1, 1) + (3, 4)*x_0
...
  [snip]
...
sage: len(list(d)) ## line 467 ##
2
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## line 
469 ##
0

**
--
sage -t src/sage/numerical/linear_tensor_element.pyx  # Killed due to abort
--




On Monday, September 2, 2019 at 4:22:40 PM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
>
> bdf4b23d74 (trac/develop, tag: 8.9.beta9) Updated SageMath version to 
> 8.9.beta9
> c631202c12 Trac #28411: refresh the prompt in the installation guide
> 45482b13f0 Trac #28387: Implement function that returns the balanced digit 
> representation of an integer
> 4454ffec0d Trac #28384: py2: UnicodeDecodeError in doctest framework 
> exception handling
> 0c8192c3de Trac #28366: Lattice precision timing test fails on Windows 7 
> due to low-ish clock resolution
> 5e1b351a89 Trac #28274: EnumeratedFamily should use integers as keys
> ec9715bb88 Trac #28172: Profile of a Finite Permutation Group
> dcf58df8b5 Trac #28154: SciPy: patch for missing coding lines in some 
> source files
> 82d75fd335 Trac #27917: Standardize doctest headers
> 04d5aab185 Trac #25817: RuntimeError: Encountered operator mismatch in 
> maxima-to-sr translation, integrate
> 45314bcbcf Trac #23639: Strange errors with roots() of polynomials over 
> polynomial rings
> f29cee985f Trac #28419: new pyflakes miscellanous cleanup
> 77bddf472a Trac #28417: removed deprecated stuff in integer_mod
> c565a3aa0a Trac #28412: upgrade Pynac to 0.7.26
> 2e47b34ab8 Trac #28408: fixing a few invalid escape sequences
> 877d26294b Trac #28407: py3: fix quantum_group_gap and graph_latex
> 3db8be3dc0 Trac #28399: remove deprecated things in integer.pyx
> 6a837c5ea6 Trac #27818: Meet-subsemilattice for lattices
> 2920f66a0e Trac #27798: Add `backend` option to associahedron and flow 
> polytope
> 98f3199887 Trac #27587: Follow up to #25680: Fix tempfile handling in 
> doctests
> 0719be21c2 Trac #27473: Matrix inversion fails over a Laurent series ring
> 842a3dcd41 Trac #27444: Expose multithreaded fflas-ffpack features
> cee95e6b38 Trac #28404: Sign of hypergeometric motives is sometimes wrong
> af8bf5ead8 Trac #28400: fixing a few roles
> 1cdf4955c6 Trac #28398: _richcmp_ for quaternion algebra elements
> abb2397287 Trac #28397: fix some wrong doctests that were not run
> 2465a9e494 Trac #28396: faster Möbius matrix for Hasse diagrams
> 4b4b5bf81b Trac #28395: Bug in is_weil_polynomial
> 77466c5716 Trac #28393: add self-tests for polymake
> a7f0a353e5 Trac #28391: dependencies file for jupymake
> e7a3ec0d98 Trac #28377: polymake interface broken with "non-standard" 
> quadratic fields
> a535670711 Trac #28339: Random failure in src/sage/interfaces/expect.py
> f34f77e4da Trac #28271: Implement LexM traversal
> 304feb1626 Trac #28229: Generalized shifted prime tableau
> e570374675 Trac #27689: Implement is_pyramid, is_bipyramid, is_prism for 
> polytopes
> addde7bcc7 Trac #28380: bump up the version of givaro in spkg-configure.m4
> 8f1c30f031 Trac #28403: py3: crypto/block_cipher/present.py doctest 
> failures
> 0ae7ffa669 Trac #25727: Prevent 

Re: DecNet / Linux

[John H. Reinhardt via cctalk]

On 8/31/2019 11:10 AM, John Forecast via cctalk wrote:

I finally got around to getting DECnet running on the latest release of 
Raspbian for the Raspberry Pi (the 2019-7-10 Buster release). I’ve also done 
some (very) limited testing on Debian Buster (both 32- and 64-bit  x86 
kernels). For anyone who is interested the code is available at:

<https://github.com/JohnForecast/RaspbianDECnet 
<https://github.com/JohnForecast/RaspbianDECnet>>

   John.




Thanks! Looking forward to trying it out.

--
John H. Reinhardt

[sage-devel] Re: Wrong python in Sage shell?

[John H Palmieri]

On Thursday, August 29, 2019 at 7:15:51 AM UTC-7, Frédéric Chapoton wrote:
>
> Hello
>
> Somebody (else) should make sure that every single remaining piece of 
> python2 is removed from a python3 sage. In particular, we should not build 
> python2 at all.
>

See https://trac.sagemath.org/ticket/28426 


> Frédéric
>
> Le jeudi 29 août 2019 12:35:46 UTC+2, Simon King a écrit :
>>
>> Hi Dima, 
>>
>> On 2019-08-29, Dima Pasechnik  wrote: 
>> > is  this python2 from your OS, or from Sage's installation? 
>>
>> From Sage's installation (apparently Sage-with-py-3 also builds 
>> python-2): 
>>
>>   (sage-sh) king@klap:~$ which python 
>>   /home/king/Sage/git/py3/local/bin/python 
>>   (sage-sh) king@klap:~$ which python3 
>>   /home/king/Sage/git/py3/local/bin/python3 
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3161c5b6-f438-45d0-8417-04fdf2190dc0%40googlegroups.com.

[sage-release] Re: Sage 8.9.beta8 released

[John H Palmieri]

On Sunday, August 25, 2019 at 3:37:50 PM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
> It is nearing the end of the 8.9 merge window, so if you want something 
> merged then this is your last chance.
>

I would like to see #28334 and #28403 merged (the second will have a 
positive review within a day or so, unless we hear objections). I would 
also like #27967 to be resolved and merged, but unfortunately I don't know 
the timetable. I would ask you to keep an eye on it, and if it has a 
positive review soon, please merge it. After those three tickets, assuming 
no regressions, all tests would pass with Python 3 on OS X, or at least on 
the OS X machines I have access to.
 

>
> I'm inclined to name the next version 9.0. In particular, we now have 
> Python 3 support that, while not perfect, is at least usable so we should 
> mark that with a new major version. Also point-9 is a natural place to 
> switch. If you want to voice your opinion on that issue: now is the time ;-)
>

+1

With 9.0.beta0, do we make building with Python 3 the default? All 
developers are using it by now, right? Right?

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/77b58131-8ac4-46cf-912f-d680afe9fafe%40googlegroups.com.

Re: Too many DEC binders

[John H. Reinhardt via cctalk]

On 8/25/2019 12:28 PM, Shoppa, Tim via cctalk wrote:

Starting around the VMS 5.5 era, isn’t anything from then or later on the 
Condist documentation CD’s? And thus we don’t have to make a priority for 
scanning?

Tim N3QE


IIRC, most of the documentation on the ConDists were in DEC's BookReader 
format.  That might be getting hard to read these days unless you happen to 
have an OpenVMS machine with DECWindows.  I just looked at my earliest CD - 
Sept 1995 ODL and except for some of the basic how to use this CD documents 
(which are in text and PostScript), it's all in BookReader format which means 
you can't read it on a Mac/Windows/Linux system  You need a OpenVMS or Digital 
Unix or Ultrix system.

I have a smattering of CD sets starting with a 1994 SPL and then up through 
2007 VAX and 2010 Alpha.  The ODL sets are available on HPE's site beginning 
with the 2005 sets through the EOL of various platforms - VAX is 2011, Alpha is 
2017, Integrity is ongoing still but coming to an end soon.

--
John H. Reinhardt

Re: Too many DEC binders

[John H. Reinhardt via cctalk]

On 8/24/2019 3:56 PM, Aaron Jackson via cctalk wrote:

I have done some test scans tonight. If anyone has any feedback, now
would be a good time to give it, before I spend many more hours
scanning.

http://aaronsplace.co.uk/private/myscans/

Thanks,
Aaron


I looked at the Error Log Utility Manual and it seems good. Download size of 
2.6MB is reasonable.  The clarity is good at 100%. I zoomed in to 600% and the 
character edges were starting to get ragged but as far as I know that should be 
good. I shrunk down to 50% and they were a little hard to read but I'm on a Mac 
using Preview and that happens to all documents as far as I can tell.  I 
haven't checked with Adobe.


The colors seemed good, too.  The covers were good and the red highlights 
inside were legible.

--
John H. Reinhardt

Re: Too many DEC binders

[John H. Reinhardt via cctalk]

On 8/24/2019 4:11 PM, Al Kossow via cctalk wrote:


On 8/24/19 1:38 PM, John H. Reinhardt via cctalk wrote:

On 8/24/2019 3:30 PM, John H. Reinhardt via cctalk wrote:

I'll have to double check, but from the looks of this list I don't need the 
VAX/VMS Grey Wall that I acquired a couple
months ago.  It's a nearly pristine set of the V5.0 VAX/VMS documentation set. 
Some volumes are still sealed in plastic.

I'll see about getting those up and checked
There is just a lot to do



No hurry, Al.  I tend to work more with the more modern versions - VAX 7.3 and 
Alpha/Integrity 8.x.  I just saw them on Ebay, checked to see if they had been 
archived anywhere and didn't see them in the usual places and didn't want them 
lost. That you have them already scanned, just awaiting that precious time is 
fine with me.


I have some RSX-11M manuals coming next week. I think they are not online, but 
I won't know for sure until they arrive.

--
John H. Reinhardt

Re: Raspberry Pi write cycles

[John H. Reinhardt via cctalk]

On 8/24/2019 2:16 AM, Lars Brinkhoff via cctalk wrote:

Zane Healy wrote:

I use RPi3’s for PDP-10 and DPS-8 emulation, I haven’t tried them for
VAX emulation.  I would like to try a RPi4 for VAX emulation.

I have an RPi4 running ITS.  I attached a fast USB3 memory rather than
running off the SD card.  For the full ITS rebuild from scratch it takes
two hours rather, compared to one hour on my Core i7 2.4 GHz laptop.

An RPi2 with slow SD card takes around 24 hours!


I just did a "make all" for SimH on a 1GB Pi 4B using a SanDisk industrial 8GB 
SD card and it took 75 minutes to build the 75 different emulators.  It has the latest 
updates to Raspbian Buster.


What USB3 thumb drive did you use?


--
John H. Reinhardt

Re: Too many DEC binders

[John H. Reinhardt via cctalk]

On 8/24/2019 3:30 PM, John H. Reinhardt via cctalk wrote:

I'll have to double check, but from the looks of this list I don't need the 
VAX/VMS Grey Wall that I acquired a couple months ago.  It's a nearly pristine 
set of the V5.0 VAX/VMS documentation set. Some volumes are still sealed in 
plastic.

On 8/24/2019 12:03 PM, Al Kossow via cctalk wrote:


here is a list of the manuals I have scanned but not pdf'ed


./VMS_5.0_Apr88/M1A/AA-LA23A-TE_VMS_System_Management_Master_Index_Apr88.tar
./VMS_5.0_Apr88/M1A/m1a_aa-la24a-te_Introduction_to_VMS_System_Management_apr88.tar
./VMS_5.0_Apr88/M1A/m1a_aa-la25a-te_Guide_to_Setting_Up_a_VMS_System_apr88.tar
./VMS_5.0_Apr88/M1A/m1a_aa-la26a-te_VMS_SYSMAN_Utility_Manual_apr88.tar
./VMS_5.0_Apr88/M1B/m1b_aa-la27a-te_VMS_VAXcluster_Manual_apr88.tar
./VMS_5.0_Apr88/M1B/m1b_aa-la28a-te_VMS_Exchange_Utility_Manual_apr88.tar
./VMS_5.0_Apr88/M1B/m1b_aa-la29a-te_VMS_Install_Utility_Manual.tar
./VMS_5.0_Apr88/M1B/m1b_aa-la30a-te_VMS_System_Generation_Utility_Manual.tar
./VMS_5.0_Apr88/M1B/m1b_aa-la31a-te_VMS_Terminal_Fallback_Utility_Manual.tar
./VMS_5.0_Apr88/M1B/m1b_aa-la32a-te_VMS_LAT_Control_Program_LATCP_Manual.tar
./VMS_5.0_Apr88/M2/m2_aa-la34a-te_Guide_to_Maintaining_a_VMS_System.tar
./VMS_5.0_Apr88/M2/m2_aa-la35a-te_VMS_Backup_Utility_Manual.tar
./VMS_5.0_Apr88/M2/m2_aa-la36a-te_VMS_Bad_Block_Locator_Utility_Manual.tar
./VMS_5.0_Apr88/M2/m2_aa-la37a-te_VMS_Error_Log_Utility_Manual.tar
./VMS_5.0_Apr88/M2/m2_aa-la38a-te_VMS_Mount_Utility_Manual.tar
./VMS_5.0_Apr88/M2/m2_aa-la39a-te_VMS_Analyze_Disk_Structure_Utility_Manual.tar
./VMS_5.0_Apr88/M3/m3_aa-la40b-te_Guide_to_VMS_System_Security.tar
./VMS_5.0_Apr88/M3/m3_aa-la41a-te_VMS_Access_Control_List_Editor_Manual.tar
./VMS_5.0_Apr88/M3/m3_aa-la42a-te_VMS_Authorize_Utility_Manual.tar
./VMS_5.0_Apr88/M3/m3_aa-ng63a-te_VMS_Audit_Analysis_Utility_Manual_jun89.tar
./VMS_5.0_Apr88/M4/aa-la43a-te_Guide_to_VMS_Performance_Management.tar
./VMS_5.0_Apr88/M4/aa-la43a-te_guide_to_VMS_performance_Mangement_apr88.tar
./VMS_5.0_Apr88/M4/aa-la44a-te_VMS_Accounting_Utility_Manual.tar
./VMS_5.0_Apr88/M4/aa-la45a-te_VMS_Monitor_Utility_Manual/aa-la45a-te_b.tar
./VMS_5.0_Apr88/M4/aa-la45a-te_VMS_Monitor_Utility_Manual/aa-la45a-te_f.tar
./VMS_5.0_Apr88/M4/aa-la45a-te_Vms_monitor_utility_manual_apr88.tar
./VMS_5.0_Apr88/M4/aa-la46a-te_VMS_Show_Cluster_Utility_Manual.tar
./VMS_5.0_Apr88/M5A/m5a_aa-la47a-te_Guide_to_DECnet-VAX_Networking_apr88.tar
./VMS_5.0_Apr88/M5A/m5a_aa-la48a-te_VMS_Networking_Manual_apr88.tar
./VMS_5.0_Apr88/M5B/m5b_aa-la49a-te_VMS_DECnet_Test_Sender_DECnet_Test_Receiver_Utility_Manual_apr88.tar
./VMS_5.0_Apr88/M5B/m5b_aa-la50a-te_VMS_Network_Control_Program_Manual_apr88.tar
./VMS_5.0_Apr88/P1/AA-LA56A-TE_VMS_Programming_Master_Index_Apr88.tar
./VMS_5.0_Apr88/P1/aa-la57a-te_Guide_to_VMS_Programming_Resources.tar
./VMS_5.0_Apr88/P1/p1_aa-la57a-te_apr88.tar
./VMS_5.0_Apr88/P1/p1_aa-la58a-te_Guide_to_Creating_VMS_Modular_Procedures_apr88.tar
./VMS_5.0_Apr88/P2A/aa-la59a-te_VMS_Debugger_Manual.tar
./VMS_5.0_Apr88/P2B/aa-la60a-te_VMS_Command_Definition_Utility_Manual.tar
./VMS_5.0_Apr88/P2B/aa-la61a-te_VMS_Librarian_Utility_Manual.tar
./VMS_5.0_Apr88/P2B/aa-la62a-te_VMS_Linker_Utility_Manual.tar
./VMS_5.0_Apr88/P2B/aa-la63a-te_VMS_Message_Utility_Manual.tar
./VMS_5.0_Apr88/P2B/aa-la64a-te_VMS_Patch_Utility_Manual.tar
./VMS_5.0_Apr88/P2B/aa-la65a-te_VMS_SUMSLP_Utility_Manual.tar
./VMS_5.0_Apr88/P3/aa-la66a-te_Introduction_to_VMS_System_Routines.tar
./VMS_5.0_Apr88/P3/aa-la67a-te_VMS_Utility_Routines_Manual.tar
./VMS_5.0_Apr88/P4A/aa-la68a-te_Introduction_to_VMS_System_Services.tar
./VMS_5.0_Apr88/P4B/aa-la69a-te_VMS_System_Services_Reference_Manual_apr88.tar
./VMS_5.0_Apr88/P5A/aa-la70a-te_Introduction_to_the_VMS_Run-Time_Library_apr88.tar
./VMS_5.0_Apr88/P5A/aa-la71a-te_vms_rtl_Dectalk_manual_apr88.tar
./VMS_5.0_Apr88/P5A/aa-la72a-te.tar
./VMS_5.0_Apr88/P5A/aa-la72a-te_vms_rtl_mathematics_manual_5.4_jun90.tar
./VMS_5.0_Apr88/P5A/aa-la73a-te_vms_rtl_general_purpose_manual_apr88.tar
./VMS_5.0_Apr88/P5A/aa-la74a-te.tar
./VMS_5.0_Apr88/P5A/aa-la74a-te_vms_rtl_parallel_processing_manual_5.4_Jun90.tar
./VMS_5.0_Apr88/P5B/p5b_aa-la76a-te_VMS_RTL_Library_LIB$_Manual_apr88.tar
./VMS_5.0_Apr88/P5C/aa-la75a-te_vms_rtl_string_manipulation_manual_Apr88.tar
./VMS_5.0_Apr88/P5C/aa-la77a-te_vms_rtl_Screen_management_manual_Apr88.tar
./VMS_5.0_Apr88/P6A/aa-la78a-te_guide_to_vms_file_applications_Apr88.tar
./VMS_5.0_Apr88/P6A/aa-la79a-te_VMS_Analyze_RMS_File_Utility_Manual.tar
./VMS_5.0_Apr88/P6A/aa-la81a-te_VMS_File_Definition_Language_Facility_Manual.tar
./VMS_5.0_Apr88/P6A/aa-la82a-te_VMS_National_Character_Set_Utility_Manual.tar
./VMS_5.0_Apr88/P6B/aa-la83a-te.tar
./VMS_5.0_Apr88/P6B/aa-la83a-te_vms_record_management_services_reference_manual_apr88.tar
./VMS_5.0_Apr88/P7A/p7a_aa-la84a-te_VMS_IO_Users_Reference_Manual_Part 
1_apr88.tar
./VMS_5.0_Apr88/P7A/p7a_aa-la85a-ate_VMS_IO_Users_Reference_Manual_Part 
2_Apr88.tar
./VMS_5.0_Apr88/P7B

Re: Too many DEC binders

[John H. Reinhardt via cctalk]

./VMS_5.0_Apr88/P7B/aa-la87a-te_VMS_System_Dump_Analyzer_Utility_Manual.tar
./VMS_5.0_Apr88/P8/aa-la88a-te_VMS_Device_Support_Apr88.tar
./VMS_5.0_Apr88/P9/aa-la89a-te_VAX_MACRO_and_Instruction_Set_Reference_Manual/p9_aa-la89a-te_b.tar
./VMS_5.0_Apr88/P9/aa-la89a-te_VAX_MACRO_and_Instruction_Set_Reference_Manual/p9_aa-la89a-te_f.tar
./VMS_5.0_Apr88/U1/AA-LA01A-TE_VMS_Master_Index_Apr88.tar
./VMS_5.0_Apr88/U1/AA-LA02A-TE_VMS_General_User_Master_Index_Apr88.tar
./VMS_5.0_Apr88/U1/AA-LA03A-TE_VMS_Glossary_Apr88.tar
./VMS_5.0_Apr88/U2A/u2a_aa-la04a-te_Introduction_to_VMS_apr88.tar
./VMS_5.0_Apr88/U2A/u2a_aa-la05a-te_Guide_to_Using_VMS_apr88.tar
./VMS_5.0_Apr88/U2A/u2a_aa-la06a-te_Guide_to_VMS_Files_and_Devices_apr88.tar
./VMS_5.0_Apr88/U2B/u2b_aa-la07a-te_VMS_Mail_Utility_Manual.tar
./VMS_5.0_Apr88/U2B/u2b_aa-la08a-te_VMS_Phone_Utility_Manual.tar
./VMS_5.0_Apr88/U2B/u2b_aa-la09a-te_VMS_Sort_Merge_Utility_Manual.tar
./VMS_5.0_Apr88/U3/u3_aa-la10a-te_VMS_DCL_Concepts_Manual.tar
./VMS_5.0_Apr88/U3/u3_aa-la11a-te_Guide_to_Using_VMS_Command_Procedures.tar
./VMS_5.0_Apr88/U4/u4_aa-la12a-te_VMS_DCL_Dictionary.tar
./VMS_5.0_Apr88/U5A/u5a_aa-la13a-te_Guide_to_VMS_Text_Processing.tar
./VMS_5.0_Apr88/U5A/u5a_aa-la16a-te_VAX_EDT_Reference_Manual.tar
./VMS_5.0_Apr88/U5B/aa-la14a-te_VMS_Text_Processing_Utility_Manual_front.tar
./VMS_5.0_Apr88/U5B/aa-la14b-te_VMS_Text_Processing_Utility_Manual_V5.2.tar
./VMS_5.0_Apr88/U5B/u5b_aa-ng62a-te_EVE_Reference_Manual_jun89.tar
./VMS_5.0_Apr88/U5C/u5c_aa-la15a-te_VAX_DIGITAL_Standard_Runoff_Reference_Manual_apr88.tar
./VMS_5.0_Apr88/U6A/u6a_aa-la17a-te_VMS_System_Messages_and_Recovery_Procedures_Reference_Manual_Part_1.tar
./VMS_5.0_Apr88/U6B/u6b_aa-la18a-te_VMS_System_Messages_and_Recovery_Procedures_Reference_Manual_Part_2.tar
./VMS_5.0_Apr88/aa-la87a-te_vms5.0sysDmp_apr88.tar
./VMS_5.0_Apr88/aa-lb22a-te_VMS_Version_5.0_Release_Notes_Apr88.tar
./VMS_5.0_Apr88/aa-lb25a-te_VMS_5.0_Obsolete_Features_Manual_Apr88.tar
./VMS_5.0_Apr88/aa-lb34a-te_VAXstation_2000_Installation_Apr88.tar
./VMS_5.0_Apr88/ey-d209e-sg-0001.tar





--
John H. Reinhardt
  PRRT  #8909
  C HS  #11530
  N-Trak   #7566

Re: Current MANX location

[John H. Reinhardt via cctalk]

On 8/20/2019 11:26 PM, John H. Reinhardt via cctalk wrote:

On 8/20/2019 11:08 PM, John H. Reinhardt wrote:

On 8/20/2019 10:37 PM, Zane Healy wrote:

On Aug 20, 2019, at 5:16 PM, John H. Reinhardt via 
cctalk  wrote:

On 8/20/2019 1:51 PM, Zane Healy via cctalk wrote:

On Aug 20, 2019, at 11:43 AM, Noel Chiappa via cctalk  
wrote:


From: Glen Slick
This?

Yes; thanks!

I don't know it didn't show up in my Web searches - I tried a number of
different things, no luck.


Also,http://manx.classiccmp.org/  (which is the medium-old URL I had for it)
redirects to something that has no working link to Manx; probably ought to fix
it to go to the new location.

   Noel

Stupid question.  What is MANX?  I’d thought that it was an alternate source of 
manuals.  To my disappointment, the manuals that turned up when I searched it, 
apparently don’t exist online anywhere.

Zane





It's kind of like an internet index.  Most (if not all?) of the entries are 
pointers to where the document is (or was) located.  I've run across some dead 
links but most seem to be current.  At least the stuff I've searched for.

--
John H. Reinhardt

Leave it to me to search for obscure stuff, like manuals for DEC ALL-IN-1, or 
DEC Ada.  What I found really odd was that it had part numbers and manual names 
from one version, but when I clicked on the links it said no known version 
online.

Zane




Anyway... What version of the ADA manuals are you looking for? VSI has some for 
an Alpha Version 3.5 that they scraped off the HP site before they disappeared. 
 I have some older VAX ConDists that might have ADA documentation.

Some links that still work:

Master SLP/ODL Index 1997- 2017 
<http://h30266.www3.hpe.com/masterindex/Consolidations_external.shtml>

Just Checked.  I have the 1999 Q3 (Sept) SPL and ODL which should have VAX ADA 
V3.5 binaries and Documentation.  Are there Hobbyist PAKs for them?


--
John H. Reinhardt


Here's the link the the VSI "Legacy" documentation page.  The Ada there is V3.5 
for Alpha but if you want VAX I would think that it's close.


<https://www.vmssoftware.com/products_doc_hp_legacy.html>


No comment.  *facepalm*

--
John H. Reinhardt

Re: Current MANX location

[John H. Reinhardt via cctalk]

On 8/20/2019 11:08 PM, John H. Reinhardt wrote:

On 8/20/2019 10:37 PM, Zane Healy wrote:

On Aug 20, 2019, at 5:16 PM, John H. Reinhardt via 
cctalk  wrote:

On 8/20/2019 1:51 PM, Zane Healy via cctalk wrote:

On Aug 20, 2019, at 11:43 AM, Noel Chiappa via cctalk  
wrote:


From: Glen Slick
This?

Yes; thanks!

I don't know it didn't show up in my Web searches - I tried a number of
different things, no luck.


Also,http://manx.classiccmp.org/  (which is the medium-old URL I had for it)
redirects to something that has no working link to Manx; probably ought to fix
it to go to the new location.

   Noel

Stupid question.  What is MANX?  I’d thought that it was an alternate source of 
manuals.  To my disappointment, the manuals that turned up when I searched it, 
apparently don’t exist online anywhere.

Zane





It's kind of like an internet index.  Most (if not all?) of the entries are 
pointers to where the document is (or was) located.  I've run across some dead 
links but most seem to be current.  At least the stuff I've searched for.

--
John H. Reinhardt

Leave it to me to search for obscure stuff, like manuals for DEC ALL-IN-1, or 
DEC Ada.  What I found really odd was that it had part numbers and manual names 
from one version, but when I clicked on the links it said no known version 
online.

Zane




Anyway... What version of the ADA manuals are you looking for?  VSI has some 
for an Alpha Version 3.5 that they scraped off the HP site before they 
disappeared.  I have some older VAX ConDists that might have ADA documentation.

Some links that still work:

Master SLP/ODL Index 1997- 2017 
<http://h30266.www3.hpe.com/masterindex/Consolidations_external.shtml>

Just Checked.  I have the 1999 Q3 (Sept) SPL and ODL which should have VAX ADA 
V3.5 binaries and Documentation.  Are there Hobbyist PAKs for them?


--
John H. Reinhardt


Here's the link the the VSI "Legacy" documentation page.  The Ada there is V3.5 
for Alpha but if you want VAX I would think that it's close.

--
John H. Reinhardt

Re: Current MANX location

[John H. Reinhardt via cctalk]

On 8/20/2019 1:51 PM, Zane Healy via cctalk wrote:

On Aug 20, 2019, at 11:43 AM, Noel Chiappa via cctalk  
wrote:


From: Glen Slick
This?

Yes; thanks!

I don't know it didn't show up in my Web searches - I tried a number of
different things, no luck.


Also, http://manx.classiccmp.org/ (which is the medium-old URL I had for it)
redirects to something that has no working link to Manx; probably ought to fix
it to go to the new location.

   Noel

Stupid question.  What is MANX?  I’d thought that it was an alternate source of 
manuals.  To my disappointment, the manuals that turned up when I searched it, 
apparently don’t exist online anywhere.

Zane





It's kind of like an internet index.  Most (if not all?) of the entries are 
pointers to where the document is (or was) located.  I've run across some dead 
links but most seem to be current.  At least the stuff I've searched for.

--
John H. Reinhardt

Re: [sage-release] Re: Sage 8.7.beta6 released

[John H Palmieri]

Yes, that fits. Now that I know to look, I see buried in my gap install log 

Uninstalling existing 'gap'
Running pre-uninstall script for 'gap'
/Users/jpalmier/Desktop/Sage/git/sage/local/var/lib/sage/scripts/gap/spkg-prerm:
 
line 13: /Users/jpalmier/Desktop/Sage/git/sage/src/bin/sage-dist-helpers: 
No such file or directory
Error: failed to source sage-dist-helpers
Is /Users/jpalmier/Desktop/Sage/git/sage the correct SAGE_ROOT?
Error: The pre-uninstall script for 'gap' failed; the package will not be 
uninstalled, and some manual intervention may be needed to repair the 
package's state before uninstallation can proceed.  Check further up in 
this log for more details, or the pre-uninstall script itself at 
/Users/jpalmier/Desktop/Sage/git/sage/local/var/lib/sage/scripts/gap/spkg-prerm.



On Thursday, August 15, 2019 at 10:58:22 AM UTC-7, Markus Wageringel wrote:
>
> This also happened to me a few weeks ago. The underlying problem seems to 
> be that the uninstall script fails because it tries to call 
> sage-dist-helpers, but cannot find it. This file has recently been moved 
> from src/bin to build/bin, which the uninstall script cannot know about. 
> Once upgraded to Gap 4.10.2.p0, it points to the new location of 
> sage-dist-helpers, so this particular problem should not happen again.
>
> This has also been reported on devel [1,2] and might affect more Mac users 
> when upgrading to 8.9. Perhaps a copy of sage-dist-helpers could be added 
> back to src/bin for some deprecation period?
>
> [1] https://groups.google.com/forum/#!topic/sage-devel/cdw793St6cE
> [2] https://groups.google.com/forum/#!topic/sage-devel/h-hXvO2fxgc
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/d74a2f9c-c53c-47d9-83f3-045b19353cea%40googlegroups.com.

[sage-support] debian virtual machine numerical noise

[John H Palmieri]

In order to try to track down the problem with Python 3 and 
polynomial_rational_flint.pyx on Debian (see 
https://trac.sagemath.org/ticket/28334 — help wanted!), I installed 
VirtualBox and a Debian 10 virtual machine on my iMac. Most doctests pass, 
but I am getting some numerical noise. Did I misconfigure something? Is 
this to be expected? Any advice?

For example:

File "src/sage/calculus/interpolators.pyx", line 191, in 
sage.calculus.interpolators.complex_cubic_spline
Failed example:
cs.derivative(2)
Expected:
(-0.0497765406583...+0.151095006434...j)
Got:
(-0.04977602323949545+0.15109527580806253j)


File "src/sage/calculus/riemann.pyx", line 173, in 
sage.calculus.riemann.Riemann_Map
Failed example:
print("error = {}".format(m.inverse_riemann_map(m.riemann_map(x)) - 
x))  # long time
Expected:
error = (-0.000...+0.0016...j)
Got:
error = (0.0006698241837047592+0.0003692515183057285j)
**
File "src/sage/calculus/riemann.pyx", line 422, in 
sage.calculus.riemann.Riemann_Map.get_szego
Failed example:
s(3*pi / 4)
Expected:
0.0012158...
Got:
0.0012508938619074255
**



There are a few more worrisome failures:

File "src/sage/matrix/matrix_double_dense.pyx", line 629, in 
sage.matrix.matrix_double_dense.Matrix_double_dense.condition
Failed example:
A.condition()  # tol 2e-4
Expected:
16332197709146.014
Got:
5.908570618719731e+19
Tolerance exceeded:
16332197709146.014 vs 5.908570618719731e+19, tolerance 4e6 > 2e-4
**

sage -t --long src/sage/matrix/matrix_integer_dense.pyx
**
File "src/sage/matrix/matrix_integer_dense.pyx", line 3717, in 
sage.matrix.matrix_integer_dense.Matrix_integer_dense.determinant
Failed example:
A.determinant(algorithm='linbox',proof=False) == d
Expected:
True
Got:
False
**

-- 
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/9313fca4-b61a-45c4-b869-206bbacf98f8%40googlegroups.com.

Re: [sage-release] Re: Sage 8.9.beta4 released

[John H Palmieri]

On Tuesday, August 6, 2019 at 5:55:53 AM UTC-7, E. Madison Bray wrote:
>
> On Tue, Aug 6, 2019 at 2:45 PM Eric Gourgoulhon  > wrote: 
> > 
> > Le vendredi 2 août 2019 18:07:16 UTC+2, John H Palmieri a écrit : 
> >> 
> >> 
> >> 
> >> On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote: 
> >>> 
> >>> 
> >>> 
> >>> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit : 
> >>>> 
> >>>> Another question: does Flint pass its test suite on these machines? 
> >>> 
> >>> 
> >>> How could I run this test suite? 
> >>> 
> >>> Eric. 
> >> 
> >> 
> >> "sage -f -c flint" 
> >> 
> > 
> > Thanks for the tip. 
> > Being out of office, I ran the test suite on another computer (Core 
> i7-6700HQ + 16 GB RAM, running Ubuntu 18.04.2), which shows the same 
> doctest failure with Python3 Sage 8.9.beta5. 
> > The test suite seems passed, with many messages like 
> > [flint-2.5.2.p4] zz_pX_to_fmpz_mod_polyPASS 
> > [flint-2.5.2.p4] zz_pE_to_fqPASS 
> > [flint-2.5.2.p4] zz_pEX_to_fq_polyPASS 
> > (I did not see any "FAILED") and at the end: 
> > [flint-2.5.2.p4] Successfully installed flint-2.5.2.p4 
> > [flint-2.5.2.p4] Deleting temporary build directory 
> > [flint-2.5.2.p4] 
> /home/eric/sage/py3/local/var/tmp/sage/build/flint-2.5.2.p4 
> > [flint-2.5.2.p4] Finished installing flint-2.5.2.p4.spkg 
> > 
> > Side note: the "./sage -f -c flint" command continued with 
> > 
> > New packages may have been installed. 
> > Re-running configure and make in case any dependent packages need 
> updating. 
> > 
> > and then proceeded by installing 
> > 
> > arb-2.16.0.p0 
> > eclib-20190226 
> > linbox-1.6.3 
> > singular-4.1.1p2.p0 
> > pynac-0.7.24.p0 
> > sagelib-8.9.beta5 
> > 
> > Just in case, after "./sage -f -c flint", I run 
> > ./sage  -t --long 
> src/sage/rings/polynomial/polynomial_rational_flint.pyx 
> > and get the same error: 
> > 
> > File "src/sage/rings/polynomial/polynomial_rational_flint.pyx", line 
> 2055, in 
> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
>  
>
> > Failed example: 
> > G = f.galois_group(); G 
> > Expected: 
> > Transitive group number 5 of degree 4 
> > Got: 
> > Exception (FLINT memory_manager). Unable to allocate memory. 
> > Transitive group number 5 of degree 4 
> > 
> > Again, on the very same computer, this doctest is passed with Python 2 
> Sage 8.9.beta5. 
>
> It's possible this is similar to 
> https://trac.sagemath.org/ticket/28106 simply insofar as some test is 
> bumping up against the default 3300MB virtual memory limit imposed by 
> the test runner. 
>
> Which doesn't necessarily mean there isn't a problem: If some test is 
> using a lot more memory than it used to, such that it's bumping up 
> against that limit, there might be a leak or some other unintended 
> memory usage consequence to the way a test was written 
>

I get the same error within a Sage session using

sage: from sage.doctest.control import DocTestController, DocTestDefaults
sage: DC = DocTestController(DocTestDefaults(), [
'/path/to/src/sage/rings/polynomial/polynomial_rational_flint.pyx'])
sage: DC.run()

I don't think this uses the memory limits discussed at #28106 — I think 
those are set in the script sage-runtests, not in the library doctesting 
framework.

-- 
John


-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/96724eac-2a93-4004-bf5b-c4e679e4b5ac%40googlegroups.com.

[lattedock] [Bug 410465] Latte-dock did not close properly on reboot

[John H]

https://bugs.kde.org/show_bug.cgi?id=410465

--- Comment #4 from John H  ---
Latte-dock has not crashed on subsequent updates.
Clearing the cache made no perceptible difference to performance.
I have never run the dock from the command line.
Since the crash the optional Lock / Logout widget no longer works.
The last issue arose simultaneously on "KDE Neon" on this machine and 2 other
laptops I own.

-- 
You are receiving this mail because:
You are watching all bug changes.

[sage-release] Re: Sage 8.9.beta5 released

[John H Palmieri]

New failure with Python 3:

sage -t --warn-long 78.7 src/sage/tests/cmdline.py
**
File "src/sage/tests/cmdline.py", line 503, in 
sage.tests.cmdline.test_executable
Failed example:
print(err)
Expected:
Cython (http://cython.org) is a compiler for code written in the
Cython language.  Cython is based on Pyrex by Greg Ewing.
...
Got:
Traceback (most recent call last):
  File 
"/Users/palmieri/Desktop/Sage_stuff/sage_builds/PYTHON3/sage-8.9.beta5/src/bin/sage-cython",
 line 12, in 
from sage.env import SAGE_SRC
ImportError: No module named sage.env



This is because of https://trac.sagemath.org/ticket/28225.


On Saturday, August 3, 2019 at 4:56:05 AM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
> ac8cf16c5c (tag: 8.9.beta5, trac/develop) Updated SageMath version to 
> 8.9.beta5
> 73d2ad18c0 Trac #27819: Poset(), error checking when linear_extension=True
> db426b3de5 Trac #28310: some changes in a few while
> 0d67ce1f41 Trac #28303: better string representation of Macaulay2 elements
> 9d327f005e Trac #28301: remove deprecated method immediate_dominators
> 042137ad3b Trac #28300: py3: fix last 2 doctests in French book
> 75ff484366 Trac #28290: remove some deprecated stuff in graphs and digraphs
> 0ad39b9a9c Trac #28277: py3: add the graphs/ folder to known passing
> d951d9499d Trac #28225: Allow sage to run in the absence of sage-env
> 79a719845f Trac #28221: minor improvement in bidirectional_dijkstra
> a62d7fa54e Trac #28195: Implement LexUP and LexDOWN
> 74b6587a59 Trac #27875: Cythonize line_graph
> e1de3839b2 Trac #28296: Random failure in src/sage/rings/qqbar.py
> 564f26fe5f Trac #28200: reduce base field for scheme morphisms
> d825f97db1 Trac #28023: matplotlib 2.2.4 + patches
> 92ff95d408 Trac #27692: py3: fix src/sage/misc/nested_class.pyx
> 27a54e331a Trac #26932: Upgrade to givaro-4.1.1 fflas-ffpack-2.4.3 
> linbox-1.6.3
> 3caf34d332 Trac #23813: Implement matrix action on polynomial scheme 
> morphisms
> faa92bddc6 Trac #28208: spkg-configure.m4 for symmetrica
> 97fb8a6a43 Trac #27827: spkg-configure.m4 for pkgconf
> 4cc096527a Trac #28268: some typos in combinat
> db35be1dca Trac #28260: Fix typo commmand -> command
> 9b8b6c4061 Trac #28267: a small typo ticket
> 3f60aae59a Trac #28232: py3: fix doctests in doctest/test
> 729d504608 Trac #28137: Fix broken link on Git setup page in Developer's 
> Guide
> b4d255ca65 Trac #28123: Implement method to return the p-primary part of 
> an integer
> 6916817f00 Trac #28071: Enhance global_height functionality for other 
> fields
> 36f9e45109 Trac #27984: Coersion of inputs of orbit into projective space
> 1519de3f6a Trac #28266: Improve speed of diagram algebra multiplication
> 07314c1b48 Trac #28256: add .is_self_dual method for polytopes
> ab950f0e69 Trac #28253: Fixing method "is_SPP()" for plane partition
> 3237170bc2 Trac #28240: Move rational methods of the backend normaliz to 
> the `_QQ` class
> bc9b5e20b8 Trac #28236: add a way to restrict an index face set
> 5d6531f38b Trac #28235: py3: polyhedron folder with optional packages
> 504977080b Trac #28233: fix doctest in gap_packages when ~/.gap is not 
> empty
> 6688d1b1d4 Trac #28227: py3 fixes for weyl_characters.py
> 75b5ab2aca Trac #28217: awali spkg-install wrong on Python 3
> 4aa32b980d Trac #28204: p_group_cohomology version 3.2
> 034d7f8bec Trac #28188: MeatAxe arithmetic tables
> d9e5056677 Trac #27993: Make outer normal fans readily available
> 9e9a2a4c6b Trac #27987: CombinatorialPolyhedron improve initialization, 
> remove bug for unbounded polyhedra
> 1537fe511b (tag: 8.9.beta4) Updated SageMath version to 8.9.beta4
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/20ce85eb-2653-4f09-9239-61561a30146b%40googlegroups.com.

[sage-devel] Re: Grepping Trac

[John H Palmieri]

On Friday, August 2, 2019 at 1:36:36 PM UTC-7, Nils Bruin wrote:
>
> On Friday, August 2, 2019 at 11:39:47 AM UTC-7, Timo Kaufmann wrote:
>>
>> Hi!
>>
>> As part of my packaging workflow, I find myself pasting error messages 
>> into the trac search pretty frequently to discover if something is a known 
>> issue or due to packaging complications. Trac search isn't very helpful 
>> here though, since it will try to split words and look for them 
>> individually. All I want is a literal search. A regex search would be even 
>> better.
>>
>>
> I find that google with "site:trac.sagemath.org" is fairly good at 
> finding relevant tickets. 
>

Searching the Google group sage-trac is also pretty good.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3075e01c-5445-4dc4-8a7b-6a3298fb0f58%40googlegroups.com.

[sage-release] Re: Sage 8.9.beta4 released

[John H Palmieri]

On Friday, August 2, 2019 at 9:07:16 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit :
>>>
>>> Another question: does Flint pass its test suite on these machines?
>>>
>>
>> How could I run this test suite?
>>
>> Eric. 
>>
>
> "sage -f -c flint"
>
> Since the problem doesn't occur with Python 2, it shouldn't be a Flint 
problem. If you have time, can you try "git bisect" to try to track down 
exactly which change caused the problem?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/d80f79ea-0e3a-4382-97ba-60c93f42ac66%40googlegroups.com.

[sage-release] Re: Sage 8.9.beta4 released

[John H Palmieri]

On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote:
>
>
>
> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit :
>>
>> Another question: does Flint pass its test suite on these machines?
>>
>
> How could I run this test suite?
>
> Eric. 
>

"sage -f -c flint"

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/22031de2-a6ae-4443-80ed-e7219417c355%40googlegroups.com.

[sage-release] Re: Sage 8.9.beta4 released

[John H Palmieri]

Another question: does Flint pass its test suite on these machines?


On Thursday, August 1, 2019 at 3:52:07 PM UTC-7, John H Palmieri wrote:
>
> Do you get the same failure with Python 2? If not, any ideas why 
> "Exception (FLINT memory_manager). Unable to allocate memory" would depend 
> on the version of Python? Flint doesn't depend on Python, so if it's Python 
> 3 only, is there some issue with the Flint interface?
>
>
>
> On Tuesday, July 30, 2019 at 5:32:37 AM UTC-7, Emmanuel Charpentier wrote:
>>
>> On a smaller (core i5, 8 GB RAM) machine with a similar setup, I get only 
>> the second failure :
>>
>> charpent@p-202-021:/usr/local/sage-python3$ sage -t --long 
>> src/sage/rings/polynomial/polynomial_rational_flint.pyx
>> too many failed tests, not using stored timings
>> Running doctests with ID 2019-07-30-14-28-30-306c6b55.
>> Git branch: develop
>> Using 
>> --optional=build,dochtml,dot2tex,fricas,giacpy_sage,memlimit,python2,sage
>> Doctesting 1 file.
>> sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx
>> **
>> File "src/sage/rings/polynomial/polynomial_rational_flint.pyx", line 
>> 2055, in 
>> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
>> Failed example:
>> G = f.galois_group(); G
>> Expected:
>> Transitive group number 5 of degree 4
>> Got:
>> Exception (FLINT memory_manager). Unable to allocate memory.
>> Transitive group number 5 of degree 4
>> **
>> 1 item had failures:
>>1 of  16 in 
>> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
>> [397 tests, 1 failure, 3.32 s]
>> --
>> sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 
>> 1 doctest failed
>> --
>> Total time for all tests: 3.4 seconds
>> cpu time: 3.2 seconds
>> cumulative wall time: 3.3 seconds
>>
>> Furthemore, having absentmindedly executed ptestlong on the same machine, 
>> I've got "only" 7 permanent failures. Is this worth pursuing ?
>>
>> HTH,
>>
>>
>> Le lundi 29 juillet 2019 15:13:45 UTC+2, Emmanuel Charpentier a écrit :
>>>
>>> FWIW, on Debian testing running on core i7 + 16 GB RAM, upgrades from 
>>> 8.9.beta3 (using python 3) ; ptest-python3 has to permanent failures :
>>>
>>> charpent@zen-book-flip:/usr/local/sage-P3$ sage -t --long --warn-long 
>>> 159.6 src/sage/algebras/quantum_groups/quantum_group_gap.py
>>> Running doctests with ID 2019-07-29-17-08-22-c25ce133.
>>> Git branch: develop
>>> Using 
>>> --optional=build,dochtml,dot2tex,fricas,gap_packages,giacpy_sage,memlimit,mpir,python2,sage
>>> Doctesting 1 file.
>>> sage -t --long --warn-long 159.6 
>>> src/sage/algebras/quantum_groups/quantum_group_gap.py
>>> **
>>> File "src/sage/algebras/quantum_groups/quantum_group_gap.py", line 1553, 
>>> in sage.algebras.quantum_groups.quantum_group_gap.QuantumGroupModule._latex_
>>> Failed example:
>>> latex(S)  # optional - gap_packages  # random (depends on dot2tex)
>>> Exception raised:
>>> Traceback (most recent call last):
>>>   File 
>>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>>  
>>> line 681, in _run
>>> self.compile_and_execute(example, compiler, test.globs)
>>>   File 
>>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>>  
>>> line 1105, in compile_and_execute
>>> exec(compiled, globs)
>>>   File ">> sage.algebras.quantum_groups.quantum_group_gap.QuantumGroupModule._latex_[4]>",
>>>  
>>> line 1, in 
>>> latex(S)  # optional - gap_packages  # random (depends on 
>>> dot2tex)
>>>   File 
>>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/misc/latex.py", 
>>> line 925, in __call__
>>> return LatexExpr(x._latex_())
>>>   File 
>>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/algebras/quantum_groups/quantum_group_gap.py&qu

[sage-release] Re: Sage 8.9.beta4 released

[John H Palmieri]

Do you get the same failure with Python 2? If not, any ideas why "Exception 
(FLINT memory_manager). Unable to allocate memory" would depend on the 
version of Python? Flint doesn't depend on Python, so if it's Python 3 
only, is there some issue with the Flint interface?



On Tuesday, July 30, 2019 at 5:32:37 AM UTC-7, Emmanuel Charpentier wrote:
>
> On a smaller (core i5, 8 GB RAM) machine with a similar setup, I get only 
> the second failure :
>
> charpent@p-202-021:/usr/local/sage-python3$ sage -t --long 
> src/sage/rings/polynomial/polynomial_rational_flint.pyx
> too many failed tests, not using stored timings
> Running doctests with ID 2019-07-30-14-28-30-306c6b55.
> Git branch: develop
> Using 
> --optional=build,dochtml,dot2tex,fricas,giacpy_sage,memlimit,python2,sage
> Doctesting 1 file.
> sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx
> **
> File "src/sage/rings/polynomial/polynomial_rational_flint.pyx", line 2055, 
> in 
> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
> Failed example:
> G = f.galois_group(); G
> Expected:
> Transitive group number 5 of degree 4
> Got:
> Exception (FLINT memory_manager). Unable to allocate memory.
> Transitive group number 5 of degree 4
> **
> 1 item had failures:
>1 of  16 in 
> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
> [397 tests, 1 failure, 3.32 s]
> --
> sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 
> 1 doctest failed
> --
> Total time for all tests: 3.4 seconds
> cpu time: 3.2 seconds
> cumulative wall time: 3.3 seconds
>
> Furthemore, having absentmindedly executed ptestlong on the same machine, 
> I've got "only" 7 permanent failures. Is this worth pursuing ?
>
> HTH,
>
>
> Le lundi 29 juillet 2019 15:13:45 UTC+2, Emmanuel Charpentier a écrit :
>>
>> FWIW, on Debian testing running on core i7 + 16 GB RAM, upgrades from 
>> 8.9.beta3 (using python 3) ; ptest-python3 has to permanent failures :
>>
>> charpent@zen-book-flip:/usr/local/sage-P3$ sage -t --long --warn-long 
>> 159.6 src/sage/algebras/quantum_groups/quantum_group_gap.py
>> Running doctests with ID 2019-07-29-17-08-22-c25ce133.
>> Git branch: develop
>> Using 
>> --optional=build,dochtml,dot2tex,fricas,gap_packages,giacpy_sage,memlimit,mpir,python2,sage
>> Doctesting 1 file.
>> sage -t --long --warn-long 159.6 
>> src/sage/algebras/quantum_groups/quantum_group_gap.py
>> **
>> File "src/sage/algebras/quantum_groups/quantum_group_gap.py", line 1553, 
>> in sage.algebras.quantum_groups.quantum_group_gap.QuantumGroupModule._latex_
>> Failed example:
>> latex(S)  # optional - gap_packages  # random (depends on dot2tex)
>> Exception raised:
>> Traceback (most recent call last):
>>   File 
>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>  
>> line 681, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File 
>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>  
>> line 1105, in compile_and_execute
>> exec(compiled, globs)
>>   File "> sage.algebras.quantum_groups.quantum_group_gap.QuantumGroupModule._latex_[4]>",
>>  
>> line 1, in 
>> latex(S)  # optional - gap_packages  # random (depends on dot2tex)
>>   File 
>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/misc/latex.py", 
>> line 925, in __call__
>> return LatexExpr(x._latex_())
>>   File 
>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/algebras/quantum_groups/quantum_group_gap.py",
>>  
>> line 1559, in _latex_
>> return latex(self.crystal_graph())
>>   File 
>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/algebras/quantum_groups/quantum_group_gap.py",
>>  
>> line 2097, in crystal_graph
>> vertices = [CrystalGraphVertex(self, d[repr(p)[1:-1]]) for p in 
>> G[bytes('points')]]
>> TypeError: string argument without an encoding
>> **
>> File "src/sage/algebras/quantum_groups/quantum_group_gap.py", line 1658, 
>> in 
>> sage.algebras.quantum_groups.quantum_group_gap.QuantumGroupModule.crystal_graph
>> Failed example:
>> G = V.crystal_graph(); G# optional - gap_packages
>> Exception raised:
>> Traceback (most recent call last):
>>   File 
>> "/usr/local/sage-P3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>>  
>> line 681, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File 
>> 

[kde] [Bug 410465] Latte-dock did not close properly on reboot

[John H]

https://bugs.kde.org/show_bug.cgi?id=410465

John H  changed:

   What|Removed |Added

   Platform|unspecified |Archlinux Packages

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 410465] New: Latte-dock did not close properly on reboot

[John H]

https://bugs.kde.org/show_bug.cgi?id=410465

Bug ID: 410465
   Summary: Latte-dock did not close properly on reboot
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jhump3...@virginmedia.com
  Target Milestone: ---

Application: latte-dock (0.9.0)

Qt Version: 5.13.0
Frameworks Version: 5.60.0
Operating System: Linux 5.2.4-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was rebooting my Arch Linux / KDE sysem after intalling updates plus msmtp
(to send mail from command line).

-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6d39bc9280 (LWP 984))]

Thread 5 (Thread 0x7f6d2b413700 (LWP 1073)):
#0  0x7f6d3d859415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f6d2b57debc in  () at /usr/lib/dri/i965_dri.so
#2  0x7f6d2b57dab8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f6d3d85357f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f6d3e5200e3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f6d31c07700 (LWP 1034)):
#0  0x7f6d3e51118c in read () at /usr/lib/libc.so.6
#1  0x7f6d3c8e89f0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f6d3c936311 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f6d3c937a28 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f6d3c937b51 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f6d3ec169bc in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f6d3ebbd5ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f6d3e9f02f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f6d403618f9 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f6d3e9f1520 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f6d3d85357f in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f6d3e5200e3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f6d33e5d700 (LWP 1018)):
#0  0x7f6d3e515667 in poll () at /usr/lib/libc.so.6
#1  0x7f6d3c937a80 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f6d3c937b51 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f6d3ec169bc in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f6d3ebbd5ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f6d3e9f02f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f6d3eea5b37 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f6d3e9f1520 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f6d3d85357f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f6d3e5200e3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f6d38d76700 (LWP 1017)):
#0  0x7f6d3e515667 in poll () at /usr/lib/libc.so.6
#1  0x7f6d40ae4630 in  () at /usr/lib/libxcb.so.1
#2  0x7f6d40ae62db in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f6d3973b049 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f6d3e9f1520 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f6d3d85357f in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f6d3e5200e3 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f6d39bc9280 (LWP 984)):
[KCrash Handler]
#5  0x7f6d3ea45aa3 in QHashData::nextNode(QHashData::Node*) () at
/usr/lib/libQt5Core.so.5
#6  0x56360a69deae in
Latte::Layout::GenericLayout::addView(Plasma::Containment*, bool, int,
QHash >*) ()
#7  0x56360a692a92 in Latte::CentralLayout::addView(Plasma::Containment*,
bool, int, QHash >*) ()
#8  0x56360a69ac66 in
Latte::Layout::GenericLayout::addContainment(Plasma::Containment*) ()
#9  0x7f6d3ebeab70 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#10 0x7f6d40a24810 in
Plasma::Corona::containmentAdded(Plasma::Containment*) () at
/usr/lib/libKF5Plasma.so.5
#11 0x7f6d40a269f3 in  () at /usr/lib/libKF5Plasma.so.5
#12 0x7f6d40a275f8 in  () at /usr/lib/libKF5Plasma.so.5
#13 0x7f6d40a2aa37 in Plasma::Corona::importLayout(KConfigGroup const&) ()
at /usr/lib/libKF5Plasma.so.5
#14 0x56360a6a5caa in Latte::Layout::Storage::importLayoutFile(QString) ()
#15 0x56360a6aa22b in Latte::Layout::Storage::importToCorona() ()
#16 0x56360a6c4ec3 in
Latte::Layouts::Synchronizer::syncMultipleLayoutsToActivities(QString) ()
#17 0x56360a6c75d2 in  ()
#18 0x7f6d3ebf7bb3 in  () at /usr/lib/libQt5Core.so.5
#19 0x7f6d3ebeb3e5 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#20 0x7f6d3f84a4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 

Re: [sage-support] Is there a binary version of SageMath .app.dmg compatiable with Mac OS X ver. 10.14.6

[John H Palmieri]

On Friday, July 26, 2019 at 9:33:25 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Friday, July 26, 2019 at 12:32:06 AM UTC-7, Dima Pasechnik wrote:
>>
>>
>>
>> On Fri, 26 Jul 2019 at 06:26, Samuel Dupree  wrote:
>>
>>>
>>>
>>> I'm attempting to update SageMath-8.7.app on an iMacPro running Mac OS X 
>>> ver. 10.14.6 tp SageMath-8.8.app. The problem for the moment occurs when I 
>>> decompress sage-8.8-OSX_10.14.5-x86_64.app.dmg, the operation crashes my 
>>> iMacPro with the message captured in the attached file.
>>>
>>
>> there is no OSX-10.14 compatible app version available, for there are 
>> changes needed to be done, and someone with knowledge of OSX (err, Mac OS) 
>> frontend programming needs to step forward and do the needed work...
>>
>
>
> What about 
> http://mirrors.xmission.com/sage/osx/intel/sage-8.8-OSX_10.14.5-x86_64.app.dmg?
>  
> This works for me with OS X 10.14.6, although I haven't yet tried on an 
> iMac Pro. 
>

It works on my iMac Pro, too. Try downloading the file again, maybe from a 
different mirror.



>   John
>
>
>> HTH,
>> Dima
>>
>>
>>> Any suggestions?
>>>
>>>
>>> Sam Dupree.
>>>
>>> -- 
>>> 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/1cd574a4-4709-4156-bd95-d2c9ac162132%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/sage-support/1cd574a4-4709-4156-bd95-d2c9ac162132%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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/5f1610f5-c8a7-4b27-bce7-d5326a9d7d55%40googlegroups.com.

Re: [sage-support] Is there a binary version of SageMath .app.dmg compatiable with Mac OS X ver. 10.14.6

[John H Palmieri]

On Friday, July 26, 2019 at 12:32:06 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Fri, 26 Jul 2019 at 06:26, Samuel Dupree  > wrote:
>
>>
>>
>> I'm attempting to update SageMath-8.7.app on an iMacPro running Mac OS X 
>> ver. 10.14.6 tp SageMath-8.8.app. The problem for the moment occurs when I 
>> decompress sage-8.8-OSX_10.14.5-x86_64.app.dmg, the operation crashes my 
>> iMacPro with the message captured in the attached file.
>>
>
> there is no OSX-10.14 compatible app version available, for there are 
> changes needed to be done, and someone with knowledge of OSX (err, Mac OS) 
> frontend programming needs to step forward and do the needed work...
>


What about 
http://mirrors.xmission.com/sage/osx/intel/sage-8.8-OSX_10.14.5-x86_64.app.dmg? 
This works for me with OS X 10.14.6, although I haven't yet tried on an 
iMac Pro. 

  John


> HTH,
> Dima
>
>
>> Any suggestions?
>>
>>
>> Sam Dupree.
>>
>> -- 
>> 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/1cd574a4-4709-4156-bd95-d2c9ac162132%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/17ed8fd8-7698-415f-9250-105e384af2c4%40googlegroups.com.

RB 3.0.15: warnings from rb-site update_index

[john h]

Hi all,

I recently upgraded a ReviewBoard install from Ubuntu 14.04/RB 1.6.9 to 
18.04/3.0.15.  I did it by advancing through each final minor release of RB 
with pip (starting with 1.7.xx, since that was the earliest available via 
pip), and running rb-site upgrade and recommended commands/edits.  RB was 
messily/incompletely installed, and I had to remove/reinstall 
/usr/local/python2.7/dist-packages to clean up the dependency mess in 
there.  More details if needed-- it was fairly messy, and I'm a little 
unsure the site is 100% clean at this point, but it appears to be Mostly 
Working.

Search functionality had never been enabled or installed in crontab.  I did 
that (using Whoosh, our site seems fairly small at 6000 review requests 
over a decade), but now I'm getting the following error from sudo -u 
www-data "/usr/bin/python" "/usr/local/bin/rb-site" manage 
"/var/www/mercury-reviewboard.pct.niksun.com" update_index -- -a 1:

WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/haystack/indexes.py:167:
 
UserWarning: No updated date field found for 'User' - not restricting by 
age.
  warnings.warn(update_field_msg)

Indexing 82 users
Indexing 0 Review Requests

My first try at indexing had this all running as root, so I removed the 
data/search-index directory, reran everything as the www-data user RB is 
running as, and the error persists.  How might I clear this error?  TOO 
MUCH MAIL FROM ROOT :)

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/4248b707-3179-431a-a8e7-d9bd43c09cf0%40googlegroups.com.

[sage-devel] signature missing in introspection some of the time

[John H Palmieri]

See 
https://ask.sagemath.org/question/47214/help-doesnt-show-function-call/. 
Some of the time when you evaluate

   blah?

the signature is not present. Is this a bug or is it intended?

I like this behavior:

sage: A = SteenrodAlgebra()
sage: A.antipode?
Signature:  B.antipode(self, *args)
Call signature: B.antipode(*args)
Type:   ModuleMorphismByLinearity_with_category
String form:Generic endomorphism of mod 2 Steenrod algebra, milnor basis
File:   ~/Desktop/Sage_stuff/git/sage/local/lib/python2.7/site-
packages/sage/modules/with_basis/morphism.py
Docstring: 

   ...

but not this:

sage: mat = random_matrix(ZZ, 3, 3)
sage: mat.add_multiple_of_row?
Docstring: 
   ...



-- 
John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d22df5bc-8df4-4965-9214-6553f6f1fe2c%40googlegroups.com.

Re: Computer Reset shop, liquidation. (USA)

[John H. Reinhardt via cctalk]

On 7/17/2019 11:34 AM, William Donzelli via cctalk wrote:


I am doing a documentation purge (most DEC) at VCFmw this year, just
as I did a few years ago. And yes, what does not get sold or given
away gets pulped at the end of the show. My van will then be empty so
I can take your stuff.

--
Will


Just curious, but anything worth scanning (DEC)?  Not that I'll make it to 
VCFmw this year.  I'm in/near Fort Worth, TX so it's a long haul for me.  But 
they all are from here.

--
John H. Reinhardt

Re: R: OT: the end of Dyn DNS

[John H. Reinhardt via cctalk]

On 6/27/2019 12:56 PM, Grant Taylor via cctalk wrote:

On 6/27/19 2:38 AM, U'll Be King of the Stars via cctalk wrote:

I have heard the that you shouldn't have your register be the same company as 
your DNS provider, and I intend to revise this proposition. If the argument 
still holds then I would keep gandi.net as my registrar look for a different 
DNS service.


I've not heard that myself.

But I can see how people might say that in an effort to distribute eggs across 
more baskets.




What I've usually heard is don't have your domain registrar also be your site 
host.  Like GoDaddy.  Apparently some people have had problems with the host 
not letting them move the name registration when switching hosting providers.  
Or vice versa. I don't have any experience with that. I've either self hosted 
or, like now, have co-located hardware.

--
John H. Reinhardt

Re: OT: the end of Dyn DNS

[John H. Reinhardt via cctalk]

On 6/26/2019 8:36 PM, Charles Dickman via cctalk wrote:

Now that Dyn has been absorbed by Oracle I need a new DNS service for my
vanity domain. I welcome suggestions for a replacement provider.

-chuck


I use Duck DNS.  I can't really say much about it though. I just signed up last 
month.  So far it works fine.  It's free. The DNS name changes fairly soon 
after my home IP updates.  It works with my Ubiquiti EdgeRouter.


The biggest negative I have so far is that you have to use the 
x.duckdns.org hostname.  One that uses a name of your choice (and 
registration) would be nice.  Do any do that? For free? Or cheap? I didn't dig 
real deep into providers.

--
John H. Reinhardt

Re: RSTS collection in the UK

[John H. Reinhardt via cctalk]

On 6/26/2019 9:45 AM, Al Kossow via cctalk wrote:


On 6/26/19 12:55 AM, Dave Wade via cctalk wrote:


Could really do with a UK RSTS person to take and scan.

yup
I seriously considered it, but money for shipping wasn't available.




I should know better than to ask, but what was the shipping estimate?

--
John H. Reinhardt

Re: RSTS collection in the UK

[John H. Reinhardt via cctalk]

On 6/25/2019 8:00 PM, Al Kossow via cctalk wrote:


On 6/25/19 5:35 PM, John H. Reinhardt via cctalk wrote:


I hope someone scans that RSTS/E documentation.  There isn't a lot of it 
available online.

Seriously?

I count 75 manuals under pdp11/rsts on bitsavers



Sounds like a lot, I know (and I've downloaded them all) but for all 3 versions 
of V06 (A/B/C) there are only 16 manuals total. Some are things like Runoff and 
TextEdit which are semi generic, but others like the Sysgen manual there is 
only V06A, nothing for B or C.  Same for the System Manager's Guide.  And the 
Install notes.  And so forth.  V7 is worse. V7.0 was a major, major change in 
RSTS/E and there are only seven manuals for it.  Only two relatively minor 
manuals for 7.2 and that's it.  V8 has only a beta level internals manual.  V9 
has a good coverage but tht won't help you for earlier versions much.

This collection in UK manuals for version from 4a to 10.1 That's significant 
for a RSTS/E fan.  It could be hundreds of manuals total if each version 
released is represented.


John H. Reinhardt

Re: RSTS collection in the UK

[John H. Reinhardt via cctalk]

On 6/25/2019 11:20 AM, Al Kossow via cctalk wrote:

interface boards, a mix of dual, quad and Unibus. Is there anything in 
particular that you need? Finally I have a mass
of RSTS related documentation, such as one copy of every edition of the US 
publication RSTS Porfessional magazine. Plus
copies of RSTS and RT-11 operating system manuals, from RSTS Version 4a (1974) 
through to Version 10.1 (mid 1990s)."



I hope someone scans that RSTS/E documentation.  There isn't a lot of it 
available online.  Especially earlier version like V06. I wish I was on the 
other side of the ocean but I'm in Fort Worth, TX

--
John H. Reinhardt

Re: [sage-devel] sage foundation ???

[John H Palmieri]

I am writing to follow up on this. The University of Washington has now 
stopped accepting donations to the Sage Foundation fund. People looking for 
ways to donate in support of Sage will need to find other avenues for that, 
and I encourage people to create those avenues if they know how. Of course 
(speaking as chair of the UW Department of Mathematics), we still welcome 
all contributions to support UW mathematics ;)

  John



On Monday, October 1, 2018 at 5:39:22 AM UTC-7, Sylvain Corlay wrote:
>
> Setting up the NumFOCUS EU is work in progress. We will be posting more 
> information on it very soon.
>
> Best,
>
> Sylvain
>
> On Sunday, September 30, 2018 at 5:22:53 AM UTC+2, Jason Grout wrote:
>>
>> The Europe/NumFOCUS situation would be a good thing to reach out to Andy 
>> or Leah about.
>>
>> Jason
>>
>>
>> On Sat, Sep 29, 2018 at 5:10 AM Erik Bray  wrote:
>>
>>> On Fri, Sep 28, 2018 at 10:03 PM Harald Schilly
>>>  wrote:
>>> >
>>> >
>>> >
>>> > On Monday, September 24, 2018 at 3:12:12 PM UTC+2, kcrisman wrote:
>>> >>
>>> >>  Certainly R and probably other similar mathematical FLOSS does have 
>>> foundations...
>>> >
>>> >
>>> > I just came across this thread. Many years ago I had the idea to setup 
>>> an european "sage foundation" similar to the one of R. My main thoughts 
>>> where that this gives european users a way to organize us over here, while 
>>> the UW parent foundation works well for the US. The R foundation [1] is 
>>> situated in Vienna, Austria (incidentally where I live :-) and it's 
>>> absolutely not not a bureaucratic hassle to set up a nonprofit organization 
>>> like that over here. The real challenge is to find a couple of people who 
>>> stick together and run it (a dedicated core team). Going with NumFocus 
>>> sounds like a good idea, but it's also an US entity.
>>>
>>> I believe I've heard--unless I'm misremembering something else--that
>>> there is some interest in setting up a European-based NumFOCUS
>>> companion organization.  That would be a good thing if so.
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To post to this group, send email to sage-...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/46223393-29d5-4af3-870d-da93e75d0fc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] The behavior of empty sums

[John H Palmieri]

On Tuesday, June 25, 2019 at 3:10:29 AM UTC-7, Peter Luschny wrote:
>
> Am Di., 25. Juni 2019 um 10:49 Uhr 'luisfe' :
>
> | When n =0, k ranges from 0 to -1 so there is no k and the list 
> constructed in ib(n,m) 
> |  is just the empty list. Not an empty list of polynomials, just an empty 
> list.
>
> Well, then the way 'sum' is implemented is possibly improvable?
>
> The type information for "binomial(m*n-1, m*k)*polynomial(m,k)" 
> is there, regardless of what the value of the integers m, n, and k is.
>

No, it's not there, that's the problem. Do this:

sage: def list_polys(m, n): return [binomial(m*n-1, 
m*k)*cyclotomic_polynomial(m*(k+1)) for k in (0..n-1)]
sage: list_polys(2,0)
[]

Python evaluates the argument inside sum(...) before applying the sum 
function to it. In this case, it gets an empty list, and so has no way of 
knowing whether it came from a polynomial or anything else. I'm not sure 
what behavior would improve this. If you wanted to try to parse the 
arguments and determine that the expression binomial(m*n-1, 
m*k)*cyclotomic_polynomial(m*(k+1)) was supposed to be a polynomial, you 
need to plug in actual numbers for m, n, and k: Python functions don't have 
defined output types, so you can't tell what "cyclomic_polynomial(m*(k+1))" 
will be until you plug in numbers. In this case, m=2 and n=0, but what 
value should you plug in for k? I can imagine situations where plugging in 
k=0 is right but k=-1 is wrong, and vice versa, so what would a good 
default be?

Sage's solution, as pointed out by slelievre, seems like the right choice.

 

> (The definition of 'polynomial' here does not matter as long as it is a 
> polynomial.) 
>
> To see this try this:
>
> def ib(m, n): 
> R = ZZ['x']
> p = lambda m,n,k: binomial(m*n-1, m*k)*cyclotomic_polynomial(m*(k+1))
> print type(R(p(2,n,0)))
> return [p(m,n,k) for k in (0..n-1)]
>
> for n in (0..3): 
> r = ib(2,n)
> print(type(r), r)
>
> The output includes in *all* cases
>  'sage.rings.polynomial.polynomial_integer_dense_flint.Polynomial_integer_dense_flint'>
>
> So why not use this information to return the zero of this ring if the sum 
> range (a..b) has not a <= b? 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/371b91a6-43b1-44d3-86f7-01e52368e164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.rc2 released

[John H Palmieri]

This problem is being discussed at https://trac.sagemath.org/ticket/28008. 
As François says, you can touch matrix_rational_dense.pyx and do "sage -b", 
or you can do "sage -ba" to rebuild all of Sage's library files, in case 
other ones are also affected.


On Wednesday, June 19, 2019 at 5:52:19 PM UTC-7, François Bissey wrote:
>
> You shouldn't need two copies. It is more like a dependency issue. 
> sage/matrix/matrix_rational_dense.so (and may be other) should be 
> re-built during the incremental build but isn’t/aren't. 
> Touching the relevant .pyx file and using `./sage -b` should fix it. 
>
> > On 20/06/2019, at 12:48 PM, Paul Masson  > wrote: 
> > 
> > In an incremental build from beta 7 on macOX Mojave (10.14.5), I'm still 
> encountering a crash-inducing issue with openblas. The relevant part of the 
> crash log is 
> > 
> > ImportError: 
> dlopen(/Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/sage/matrix/matrix_rational_dense.so,
>  
> 2): Library not loaded: 
> /Users/Masson/Downloads/GitHub/sage/local/lib/libopenblas_haswellp-r0.3.5.dylib
>  
>
> >   Referenced from: 
> /Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/sage/matrix/matrix_rational_dense.so
>  
>
> >   Reason: image not found 
> > 
> > I can work around it by creating a second copy of libopenblas and 
> changing its last digit to 5, but why would I need two copies of the 
> library? 
> > 
> > On Wednesday, June 19, 2019 at 2:54:06 PM UTC-7, Volker Braun wrote: 
> > As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
> > 
> > 
> > 8084b69595 (tag: 8.8.rc2, trac/develop) Updated SageMath version to 
> 8.8.rc2 
> > ab2ee449bb Trac #27961: openblas 0.3.6 vs. OS X on some processors 
> > 57e1ba71f9 Trac #27950: Replace source activate by conda activate in 
> conda install guide 
> > 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-release" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-r...@googlegroups.com . 
> > To post to this group, send email to sage-r...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-release. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/d04fa013-2143-4da5-a1c2-9036d1943fa4%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e228657b-3464-4674-882a-19d8eef9c834%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installation gets stuck when it tries to download zeromq-4.2.5.tar.gz

[John H Palmieri]

On Tuesday, June 18, 2019 at 10:12:06 AM UTC-7, Parth Dubal wrote:
>
> I tried to download manually and put it into upstream directory but it is 
> already present and the installation didn't even reach to that step. I 
> don't understand, if it was already downloaded earlier then why the 
> installation does freeze when it is attempting to download? I am sorry I 
> know its weird.
>

Is the newly downloaded one identical to the old one? The old one might be 
corrupted, so the checksums don't match, and so Sage tries to download a 
new copy. Replacing the old one with the new one might resolve that problem.
 

>
> On Tuesday, June 18, 2019 at 11:47:31 AM UTC-4, Parth Dubal wrote:
>>
>> Hi,
>>
>> I tried three times to install sage as described in github on my virtual 
>> machine (Ubuntu 19) but the installation gets stuck for hours at the point 
>> of downloading zeromq-4.2.5.tar.gz. I am running ubuntu on Hyper-V. My 
>> parent OS is Windows 10 Pro and guest OS is Ubuntu 19. I have 16 Gigs of 
>> memory from which I dedicated 4 Gigs memory to guest OS, 203 Gigs hard 
>> drive out of which 100 Gigs for /dev/sda1. I am attaching the screenshots 
>> which describes the error and also when it got stuck. I waited for 2 hours 
>> to let it complete but then I was tired and I hit Ctrl+C to stop the 
>> installation. Please let me know where am I getting wrong. I did all the 
>> steps given in github. I tried to move on with other commands as this was 
>> stuck but no luck.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9f0285a2-f634-4d5d-9882-e8593fa342a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installation gets stuck when it tries to download zeromq-4.2.5.tar.gz

[John H Palmieri]

On Tuesday, June 18, 2019 at 8:47:31 AM UTC-7, Parth Dubal wrote:
>
> Hi,
>
> I tried three times to install sage as described in github on my virtual 
> machine (Ubuntu 19) but the installation gets stuck for hours at the point 
> of downloading zeromq-4.2.5.tar.gz. I am running ubuntu on Hyper-V. My 
> parent OS is Windows 10 Pro and guest OS is Ubuntu 19. I have 16 Gigs of 
> memory from which I dedicated 4 Gigs memory to guest OS, 203 Gigs hard 
> drive out of which 100 Gigs for /dev/sda1. I am attaching the screenshots 
> which describes the error and also when it got stuck. I waited for 2 hours 
> to let it complete but then I was tired and I hit Ctrl+C to stop the 
> installation. Please let me know where am I getting wrong. I did all the 
> steps given in github. I tried to move on with other commands as this was 
> stuck but no luck.
>

I don't know why downloading the file didn't work, but you can download the 
file manually from 

http://www.sagemath.org/download-packages.html

and then put it in the "upstream" directory 
("/home/parthadubal/sage/upstream").

-- 
John

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7f5a6f93-0e25-4a13-a622-dfeafed1fe13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Missing posts in archive and no Subject: line

[John H. Reinhardt via cctalk]

On 6/17/2019 1:18 PM, Noel Chiappa via cctalk wrote:

So, a couple of posts yesterday did not show up in the date archive:

   http://www.classiccmp.org/pipermail/cctalk/2019-June/date.html

which is how I read the list. They are:


And now I know why your posts always break the threading in Thunderbird... I'd 
wondered how it happened. ;)

Noel


--
John H. Reinhardt

[sage-release] Re: Sage 8.8.rc0 released

[John H Palmieri]

I am having a problem on a different OS X machine (an iMac Pro):

sage -t 
src/doc/en/thematic_tutorials/explicit_methods_in_number_theory/birds_other.rst 

Bad exit: 1
**
...
sage: dimension(M.cuspidal_subspace()) ## line 109 ##
Fatal: Memory exhausted.
**


I am seeing this with 8.8.beta7 + openblas 0.3.6, built from scratch.



On Sunday, June 9, 2019 at 8:19:28 AM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
>
> 2393acebc3 (tag: 8.8.rc0, trac/develop) Updated SageMath version to 8.8.rc0
> d53fd952c8 Trac #27942: Upgrade brial to 1.2.5
> 1e30f76809 Trac #27890: Fix a pickling error for codes
> 6c3a8bd774 Trac #27924: faster generator for noncrossing partitions
> a3a7e83b7d Trac #27530: small change in debugger.py
> cf1f934a9f Trac #25351: Ideal operations unsupported over QQbar
> 0c02b6b7b1 Trac #17908: Sage doesn't grok unsolved integral results from 
> fricas
> ece3afee96 Trac #27930: Py3: Fix combinat.set_partition_ordered doctests
> 12d8480936 Trac #27935: A regression in divisors of function fields
> 974dd47f6f Trac #27927: some pep details in sage-pkg
> 790dd07b79 Trac #27922: some cleanup in homology folder
> d26c6c1fd6 Trac #27918: some details in subword_complex
> b9aee296a8 Trac #27900: removed deprecated dynamics code from schemes
> 97cbf0ec3b Trac #27850: Fix a bug in gens_two method for ideals of 
> function fields
> 37a5846af9 Trac #26991: Refactor function field code
> cc0c8552af Trac #27931: fix LazyPowerSeriesRing in other variable than x
> 91fccfa40d Trac #27925: py3: tiny fixes in gap3 interface
> ffdd2345c9 Trac #27920: Upgrade pynormaliz to 2.7 to fix installation 
> error when a 'configure' script is accessible in PATH
> 024eb1916b Trac #27919: some details in Steenrod algebras
> c1b606e703 Trac #27912: Add GAP package PackageManager to gap_packages
> 275dfbfdc0 Trac #27910: Three.js: Save screenshot as PNG
> 71cecffbaa Trac #27893: Coercion bug with mpz
> 92300feff5 Trac #27700: fix is_simplicial for non-full-dimensional 
> polytopes
> ca4560d077 Trac #27468: Containment check for subgroups broken.
> f276d4b633 Trac #27847: openblas 0.3.6
> b6c623a069 Trac #27906: correct usage of all([...]) in many places
> 5372779dd1 Trac #27903: some care for all in matrix2
> 44c8a4e2f9 Trac #27915: Fix py3_syntax.py doctest on distros
> 41e4710d58 Trac #27914: py3: hash collisions of Laurent polynomials
> b4a1854a77 Trac #27909: py3: fix a doctest in binary_form_reduce
> 6a4a8c0e71 Trac #27904: py3: fix last doctest in interfaces
> d791ed2d39 Trac #27902: 2 more folders in python3-known-passing.txt
> 54386e7bab Trac #27899: cleanup of Dyck words
> dce13c427b Trac #27898: pep cleanup of basic_stats
> 575bc563d7 Trac #27817: remove SAGE_INSTALL_GCC variable
> b6d3c08d3c Trac #27787: py3: matroids.utilities.lift_cross_ratios
> 23c6588c24 Trac #27673: Fix Polyhedron.volume() in 0-dimensional space
> 859ebb6a65 Trac #5583: coercion bug in perm groups
> 777c3a9bd3 Trac #27871: some doc details in projective_curve
> fcf0291084 Trac #27894: some pep and pyflakes care in words
> 167bbc9cb4 Trac #27892: some pep cleanup in elliptic curves over number 
> fields
> 7a65573f6d Trac #27879: some pep and pyflakes cleanup in 
> torsion_quadratic_module.py
> 1851edc567 Trac #27877: faster left-right symmetry for unlabelled binary 
> trees
> 59df72bad0 Trac #27486: Use sdh_cmake for packages that use cmake
> c18d869464 Trac #27889: py3 fixes for matroids
> 4cf85e6e72 Trac #27888: py3 fix for src/sage/all.py
> 2a506aa1b9 Trac #27887: sorting interval-posets using cubical coordinates
> acb869cadd Trac #27885: Py3: symbolic/expression.pyx fix some errors
> 8481b70fba Trac #27856: Tangent vectors should act as derivations on 
> scalar fields
> f6e6ae8d25 Trac #27529: py3: tiny fix in env.py
> 8fc2040b27 Trac #26552: interface glucose-syrup
> 716fb69754 (tag: 8.8.beta7) Updated SageMath version to 8.8.beta7
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/5938aad6-7462-43d5-970c-1c69423eda07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc0 released

[John H Palmieri]

On Monday, June 10, 2019 at 2:58:27 AM UTC-7, David Coudert wrote:
>
> working properly after make distclean with py2. Will now do it for py3. 
>

Right, I think that this is an issue with upgrading from the previous 
version; building from scratch by first doing `make distclean` worked for 
me, too.

 

>
> David.
>
> Le 9 juin 2019 à 23:23, John H Palmieri > 
> a écrit :
>
> I performed the incremental build the way I always do: "git pull trac" 
> followed by "make". When I ran into problems, I restarted from 8.8.beta7, 
> which worked, and then merged #27847, after which I again got a crash.
>
> Building from scratch seems to work; at least Sage builds and runs; now 
> I'm running tests.
>
>   John
>
>
>
> On Sunday, June 9, 2019 at 2:03:45 PM UTC-7, François Bissey wrote:
>>
>> As I suspect in the ticket (in which I also left a comment) the fact 
>> that the version 0.3.5 instead of 0.3.6 is mentioned in the trace make 
>> me think this is an incremental build problem. 
>> Something that should have been rebuilt didn’t and that may be because of 
>> the way you performed the incremental build. 
>>
>> François 
>>
>> > On 10/06/2019, at 7:46 AM, John H Palmieri  
>> wrote: 
>> > 
>> > 
>> > 
>> > On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote: 
>> > I think the problem is with the openblas upgrade, 
>> https://trac.sagemath.org/ticket/27847. 
>> > 
>> > I opened https://trac.sagemath.org/ticket/27961 (not that I know how 
>> to fix it...) 
>> > 
>> > 
>> > 
>> > 
>> > On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote: 
>> > crash with both python 2 and python 3 on osX. I attach the crash report 
>> with python 3. 
>> > 
>> > Any help is more than welcome. 
>> > 
>> > David. 
>> > 
>> > = 
>> > 
>> > confetti:sage dcoudert$ ./sage 
>> > ┌┐ 
>> > │ SageMath version 8.8.rc0, Release Date: 2019-06-09 │ 
>> > │ Using Python 3.7.3. Type "help()" for help.│ 
>> > └┘ 
>> > ┏┓ 
>> > ┃ Warning: this is a prerelease version, and it may be unstable. ┃ 
>> > ┗┛ 
>> > 
>> > ** 
>> > 
>> > 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: 
>> > '/Users/dcoudert/.sage/ipython-5.0.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-s...@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-s...@googlegroups.com < 
>> /Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt 
>> > 
>> > In your email, please also include information about: 
>> > - The operating system under which the crash happened: Linux, macOS, 
>> Windows, 
>> >   other, and which exact version (for example: Ubuntu 16.04.3, macOS 
>> 10.13.2, 
>> >   Windows 10 Pro), and whether it is 32-bit or 64-bit; 
>> > - How Sage was installed: using pip or conda, from GitHub, as part of 
>> >   a Docker container, or other, providing more detail if possible; 
>> > - How to reproduce the crash: what exact sequence of instructions can 
>> one 
>> >   input to get the same crash? Ideally, find a minimal yet complete 
>> sequence 
>> >   of instructions that yields the crash. 
>> > 
>> > 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): 
&g

Re: [sage-release] Sage 8.8.rc0 released

[John H Palmieri]

I performed the incremental build the way I always do: "git pull trac" 
followed by "make". When I ran into problems, I restarted from 8.8.beta7, 
which worked, and then merged #27847, after which I again got a crash.

Building from scratch seems to work; at least Sage builds and runs; now I'm 
running tests.

  John



On Sunday, June 9, 2019 at 2:03:45 PM UTC-7, François Bissey wrote:
>
> As I suspect in the ticket (in which I also left a comment) the fact 
> that the version 0.3.5 instead of 0.3.6 is mentioned in the trace make 
> me think this is an incremental build problem. 
> Something that should have been rebuilt didn’t and that may be because of 
> the way you performed the incremental build. 
>
> François 
>
> > On 10/06/2019, at 7:46 AM, John H Palmieri  > wrote: 
> > 
> > 
> > 
> > On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote: 
> > I think the problem is with the openblas upgrade, 
> https://trac.sagemath.org/ticket/27847. 
> > 
> > I opened https://trac.sagemath.org/ticket/27961 (not that I know how to 
> fix it...) 
> > 
> > 
> > 
> > 
> > On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote: 
> > crash with both python 2 and python 3 on osX. I attach the crash report 
> with python 3. 
> > 
> > Any help is more than welcome. 
> > 
> > David. 
> > 
> > = 
> > 
> > confetti:sage dcoudert$ ./sage 
> > ┌┐ 
> > │ SageMath version 8.8.rc0, Release Date: 2019-06-09 │ 
> > │ Using Python 3.7.3. Type "help()" for help.│ 
> > └┘ 
> > ┏┓ 
> > ┃ Warning: this is a prerelease version, and it may be unstable. ┃ 
> > ┗┛ 
> > 
> > ** 
> > 
> > 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: 
> > '/Users/dcoudert/.sage/ipython-5.0.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-s...@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-s...@googlegroups.com < 
> /Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt 
> > 
> > In your email, please also include information about: 
> > - The operating system under which the crash happened: Linux, macOS, 
> Windows, 
> >   other, and which exact version (for example: Ubuntu 16.04.3, macOS 
> 10.13.2, 
> >   Windows 10 Pro), and whether it is 32-bit or 64-bit; 
> > - How Sage was installed: using pip or conda, from GitHub, as part of 
> >   a Docker container, or other, providing more detail if possible; 
> > - How to reproduce the crash: what exact sequence of instructions can 
> one 
> >   input to get the same crash? Ideally, find a minimal yet complete 
> sequence 
> >   of instructions that yields the crash. 
> > 
> > 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): 
> > c 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-release" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-r...@googlegroups.com . 
> > To post to this group, send email to sage-r...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-release. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/6cab4410-4a6b-49b9-8346-19e3f0cb3f08%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/29806fdd-9364-469f-8839-d3b8b274362a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc0 released

[John H Palmieri]

On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote:
>
> I think the problem is with the openblas upgrade, 
> https://trac.sagemath.org/ticket/27847.
>

I opened https://trac.sagemath.org/ticket/27961 (not that I know how to fix 
it...)


>
>
> On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote:
>>
>> crash with both python 2 and python 3 on osX. I attach the crash report 
>> with python 3.
>>
>> Any help is more than welcome.
>>
>> David.
>>
>> =
>>
>> confetti:sage dcoudert$ ./sage
>> ┌┐
>> │ SageMath version 8.8.rc0, Release Date: 2019-06-09 │
>> │ Using Python 3.7.3. Type "help()" for help.│
>> └┘
>> ┏┓
>> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
>> ┗┛
>>
>> **
>>
>> 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:
>> '/Users/dcoudert/.sage/ipython-5.0.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-s...@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-s...@googlegroups.com < 
>> /Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt
>>
>> In your email, please also include information about:
>> - The operating system under which the crash happened: Linux, macOS, 
>> Windows,
>>   other, and which exact version (for example: Ubuntu 16.04.3, macOS 
>> 10.13.2,
>>   Windows 10 Pro), and whether it is 32-bit or 64-bit;
>> - How Sage was installed: using pip or conda, from GitHub, as part of
>>   a Docker container, or other, providing more detail if possible;
>> - How to reproduce the crash: what exact sequence of instructions can one
>>   input to get the same crash? Ideally, find a minimal yet complete 
>> sequence
>>   of instructions that yields the crash.
>>
>> 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):
>> c
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6cab4410-4a6b-49b9-8346-19e3f0cb3f08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc0 released

[John H Palmieri]

I think the problem is with the openblas upgrade, 
https://trac.sagemath.org/ticket/27847.



On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote:
>
> crash with both python 2 and python 3 on osX. I attach the crash report 
> with python 3.
>
> Any help is more than welcome.
>
> David.
>
> =
>
> confetti:sage dcoudert$ ./sage
> ┌┐
> │ SageMath version 8.8.rc0, Release Date: 2019-06-09 │
> │ Using Python 3.7.3. Type "help()" for help.│
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
>
> **
>
> 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:
> '/Users/dcoudert/.sage/ipython-5.0.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-s...@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-s...@googlegroups.com  < 
> /Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt
>
> In your email, please also include information about:
> - The operating system under which the crash happened: Linux, macOS, 
> Windows,
>   other, and which exact version (for example: Ubuntu 16.04.3, macOS 
> 10.13.2,
>   Windows 10 Pro), and whether it is 32-bit or 64-bit;
> - How Sage was installed: using pip or conda, from GitHub, as part of
>   a Docker container, or other, providing more detail if possible;
> - How to reproduce the crash: what exact sequence of instructions can one
>   input to get the same crash? Ideally, find a minimal yet complete 
> sequence
>   of instructions that yields the crash.
>
> 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):
> c
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/6e1ef0a5-e260-4fe1-b448-9b4fddf6c609%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Apple deprecates Python

[John H Palmieri]

On Saturday, June 8, 2019 at 8:56:09 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Sat, 8 Jun 2019 16:50 John H Palmieri,  > wrote:
>
>>
>>
>> On Saturday, June 8, 2019 at 1:25:11 AM UTC-7, vdelecroix wrote:
>>>
>>> Le 07/06/2019 à 16:44, Jeroen Demeyer a écrit : 
>>> > On 2019-06-07 16:38, E. Madison Bray wrote: 
>>> >> While I agree it's part of an annoying trend, this is one change I 
>>> >> welcome:  The Python interpreter shipped in OSX has always *always* 
>>> >> been broken and unusable 
>>> > 
>>> > What matters for Sage is: was it sufficiently functional to bootstrap 
>>> a 
>>> > build of Sage? 
>>>
>>> Not only. As Volker said in the initial message of the thread, Python is 
>>> a dependency of the Sage binaries. 
>>>
>>
>> Although Sage binaries come with functioning builds of Python, so we 
>> could conceivably use those if there is no system Python.
>>
>
> it is a chicken vs egg problem. One needs system python to install Sage 
> first.
>

When I was trying to fix some problem in relocate-once.py, I tried using 
Sage's Python to execute it, and that seemed to work. Another fix arose, so 
it still uses the system Python, but it is possible that Sage's Python 
could be used to run relocate-once.py. What else do we need the system 
Python for?


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f2f8695f-28e9-436b-9f7d-4bf4b4d79616%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Apple deprecates Python

[John H Palmieri]

On Saturday, June 8, 2019 at 1:25:11 AM UTC-7, vdelecroix wrote:
>
> Le 07/06/2019 à 16:44, Jeroen Demeyer a écrit : 
> > On 2019-06-07 16:38, E. Madison Bray wrote: 
> >> While I agree it's part of an annoying trend, this is one change I 
> >> welcome:  The Python interpreter shipped in OSX has always *always* 
> >> been broken and unusable 
> > 
> > What matters for Sage is: was it sufficiently functional to bootstrap a 
> > build of Sage? 
>
> Not only. As Volker said in the initial message of the thread, Python is 
> a dependency of the Sage binaries. 
>

Although Sage binaries come with functioning builds of Python, so we could 
conceivably use those if there is no system Python.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0736a122-d9e8-4036-b066-bc749cde9ef8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Apple deprecates Python

[John H Palmieri]

On Friday, June 7, 2019 at 7:44:03 AM UTC-7, Jeroen Demeyer wrote:
>
> On 2019-06-07 16:38, E. Madison Bray wrote: 
> > While I agree it's part of an annoying trend, this is one change I 
> > welcome:  The Python interpreter shipped in OSX has always *always* 
> > been broken and unusable 
>
> What matters for Sage is: was it sufficiently functional to bootstrap a 
> build of Sage? 
>

And from this point of view, will Python be included in Xcode's command 
line utilities, or something similar? That would be good enough for our 
purposes. (It doesn't seem like that big a deal if we have to say: install 
the command-line utilities and now also this "scripting language" package.)

-- 
John

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/df47820e-03ae-484e-8ffc-725ee22dcfab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: A genuine bug in numerical evaluation ?

[John H Palmieri]

Oh, and Sage with Python 3 is in pretty good shape these days. Still some 
doctest failures, but I think it is mostly very functional.

  John


On Thursday, June 6, 2019 at 3:20:25 PM UTC-7, John H Palmieri wrote:
>
> I can confirm that it works for me on OS X with Python 3, gives the error 
> you described with Python 2.
>
>
> On Thursday, June 6, 2019 at 2:57:08 PM UTC-7, Emmanuel Charpentier wrote:
>>
>> According to Serge Lelièvre, the proble doesn't occur when ran under a 
>> Python3-based Sage. He advises to run such a Sage, hich seems a bit early, 
>> IMHO?
>>
>> Advice ?
>>
>>
>> Le jeudi 6 juin 2019 11:04:27 UTC+2, Emmanuel Charpentier a écrit :
>>>
>>> This ask.sagemath  question 
>>> <https://ask.sagemath.org/question/46819/numerical-integration-and-plot-failing/>
>>>  seems 
>>> to raise a genuine bug. Perusing Trac doesn't raise muc relevant, possibly 
>>> except for Trac#24428 <https://trac.sagemath.org/ticket/24428> and 
>>> Trac#21754 <https://trac.sagemath.org/ticket/21754>.
>>>
>>> From my comment to the ask.sagemath question :
>>>
>>> Indeed :
>>> sage: var("y,z")
>>> (y, z)
>>> sage: cauchy(z)=solve(z*y^3 +y^2 - 2*z*y+2 ,y)[0].rhs()
>>> sage: def foo(u):return(arg(cauchy(u)).n())
>>> sage: [foo(t) for t in (1,1.1..2)]
>>> [0.828222717321238,
>>> ## Snip...
>>>  0.377665318352514]
>>> Therefore, this function *can* be evaluated. But :
>>> sage: plot(foo,(1,2))
>>> verbose 0 (3635: plot.py, generate_plot_points) WARNING: When 
>>> plotting, failed to evaluate function at 200 points.
>>> verbose 0 (3635: plot.py, generate_plot_points) Last error message: 
>>> 'negative number cannot be raised to a fractional power'
>>> Launched png viewer for Graphics object consisting of 0 graphics 
>>> primitives
>>> ... not in `plot`. Trying  to plot symbolically yelds :
>>> TypeError: Cannot evaluate symbolic expression to a numeric value.
>>> A bug, IMHO.
>>>
>>> Can someone confirm this and, possibly, give me hints as how to flag 
>>> this ticket efficiently ?
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/e0f7b7e2-1f85-46f3-bd12-b8ef02124ece%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: A genuine bug in numerical evaluation ?

[John H Palmieri]

I can confirm that it works for me on OS X with Python 3, gives the error 
you described with Python 2.


On Thursday, June 6, 2019 at 2:57:08 PM UTC-7, Emmanuel Charpentier wrote:
>
> According to Serge Lelièvre, the proble doesn't occur when ran under a 
> Python3-based Sage. He advises to run such a Sage, hich seems a bit early, 
> IMHO?
>
> Advice ?
>
>
> Le jeudi 6 juin 2019 11:04:27 UTC+2, Emmanuel Charpentier a écrit :
>>
>> This ask.sagemath  question 
>> 
>>  seems 
>> to raise a genuine bug. Perusing Trac doesn't raise muc relevant, possibly 
>> except for Trac#24428  and 
>> Trac#21754 .
>>
>> From my comment to the ask.sagemath question :
>>
>> Indeed :
>> sage: var("y,z")
>> (y, z)
>> sage: cauchy(z)=solve(z*y^3 +y^2 - 2*z*y+2 ,y)[0].rhs()
>> sage: def foo(u):return(arg(cauchy(u)).n())
>> sage: [foo(t) for t in (1,1.1..2)]
>> [0.828222717321238,
>> ## Snip...
>>  0.377665318352514]
>> Therefore, this function *can* be evaluated. But :
>> sage: plot(foo,(1,2))
>> verbose 0 (3635: plot.py, generate_plot_points) WARNING: When 
>> plotting, failed to evaluate function at 200 points.
>> verbose 0 (3635: plot.py, generate_plot_points) Last error message: 
>> 'negative number cannot be raised to a fractional power'
>> Launched png viewer for Graphics object consisting of 0 graphics 
>> primitives
>> ... not in `plot`. Trying  to plot symbolically yelds :
>> TypeError: Cannot evaluate symbolic expression to a numeric value.
>> A bug, IMHO.
>>
>> Can someone confirm this and, possibly, give me hints as how to flag this 
>> ticket efficiently ?
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/8569d0c8-b910-4c62-8acf-284d8d399ae5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 9-Track Magtape Drive ID

[John H. Reinhardt via cctalk]

On 6/1/2019 5:24 PM, Mark J. Blair via cctalk wrote:

On Jun 1, 2019, at 14:57, John H. Reinhardt via cctalk  
wrote:
Is this the system that was on Reddit?

Yes. I’ll be fetching it next weekend. I’m excited! I wonder if the hard drive 
is still usable, and if there is anything interesting on it?

By a chance meeting with my neighbor today, I learned he has a bunch of pallet 
racking from a defunct business he emptied out. He offered that I could go grab 
some for myself. He also mentioned that he planned to bring some to his farm 
next door to me before he sells off the rest. Since I’m planning to rent a 
truck next weekend anyway, I offered to help out by hauling for both of us in 
exchange for taking a skim off the top of the pile. It’ll be a busy weekend!

--
Mark J. Blair 
http://www.nf6x.net



Congrats!!  Should be fun to play with.  I just picked up a Micro PDP-11/53 
which is about the biggest I can fit into my office/computer room.  lol

--
John H. Reinhardt
  PRRT  #8909
  C HS  #11530
  N-Trak   #7566

Re: 9-Track Magtape Drive ID

[John H. Reinhardt via cctalk]

On 6/1/2019 1:23 PM, Mark J. Blair via cctalk wrote:

Thanks!

I am taking the whole system. It's in a rack with a PDP-11/34A, a System 
Industries 9400 controller, and what looks to me like a Fujitsu M228x series 
hard drive:

https://pbs.twimg.com/media/D77fRMFU0AEQtSO.jpg

I grabbed the M228x manuals from Bitsavers to look up how the spindle and 
positioner locks work. I had been planning to de-rack it all so my dad and I 
could load it into my pickup truck in bite-sized pieces, but I think I would be 
better off renting a box truck with a lift gate.

What are the chances that it's the same PDP-11/34A that Warner did backups on? 
:D

Would the brown panel between the tape drive and computer be a filler panel, or 
part of the 11/34A? I don't know anything about the system configuration yet 
other than what can be seen in that picture.


Is this the system that was on Reddit?

--
John H. Reinhardt
  PRRT  #8909
  C HS  #11530
  N-Trak   #7566