Re: To be scrapped in as little as 2 months

[John H. Reinhardt via cctalk]

On 4/15/2018 8:42 PM, Pete Lancashire via cctalk wrote:

Other names via cctalk

Ed Sharpesteve shumaker
*Noel Chiappa*
*John H. Reinhardt*

First of, I am sorry for any additional noise on CCTALK.

I will find out who replied first on each of the group of equipment. To
keep the noise down if you name is above contact me directly then I can
keep CCTALK out of the loop



Pete,

I'll keep this public so that everyone concerned can see.  I was just 
commenting.  I just moved from Ohio to Texas and just literally gave away a 
whole basement of DEC and other gear. I'm not in any position to start 
collecting again - as much as I'd like a probable dual processor Alpha.  Please 
give them to Alan (Perry) if he was first so he can give them to Bill 
(Gunshannon). I know Bill from the comp.os.vms newsgroup and he's a stand up 
guy so if he has people that want them, he's a good target.

--
John H. Reinhardt

Re: To be scrapped in as little as 2 months

[John H. Reinhardt via cctalk]

On 4/15/2018 10:26 AM, Pete Lancashire via cctalk wrote:

https://photos.app.goo.gl/eYVej7Sg7GSk9Mv72

On Sun, Apr 15, 2018 at 8:16 AM, Alan Perry via cctalk <
cctalk@classiccmp.org> wrote:


Do you know the size/models of the Alpha systems? I want to make sure they
will fit in my car.

alan


On Apr 14, 2018, at 7:43 PM, Pete Lancashire via cctalk <

cctalk@classiccmp.org> wrote:


3 x DEC Alphas, small deskside models



They look like Compaq DS20E's in desk side format.  At first I thought they were 
Alphaserver 800's which look similar, but the AS800 would DEC and too early for Compaq.  
I wouldn't mind having one but I'm in Fort Worth, TX.  I'll be working in Seattle 4/25 - 
5/2 but flying so I sure can't transport one.  Packing one securely would be a pain, but 
ground shipping would probably "only" run about $100 or so.

[Evolution] 3.28.1-1 Ubuntu 18.04 -- Cannot paste text into message you are writing

[Dr. John H. Lauterbach]

Cannot paste into message.  Cannot add signature to message.
When started from CLI, get errors dealing with WebKitWebView and webkit_editor.

John




___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Evolution] Ubuntu 18.04 upgrade from 16.04 LTS

[Dr. John H. Lauterbach]

After backing up evolution running under 16.04 LTS, I did an in-place upgrade 
to the latest beta of 18.04 LTS.  Evolution 3.28.1-1 came up without any need 
for special commands, etc.  I did not need to use the backup file.
John___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] Compiling on Ubuntu 16.04 LTS?

[Dr. John H. Lauterbach]

No need to compile for 16.04 LTS.  Evolution 3.20.5 available for download from 
gnome3-team and gnome3-team staging.  Add the repositories (gnome3-team first) 
and your are in business.  

John

-Original Message-
From: Bjørn T Johansen 
To: evolution-list@gnome.org
Subject: Re: [Evolution] Compiling on Ubuntu 16.04 LTS?
Date: Tue, 10 Apr 2018 20:36:18 +0200

On Tue, 10 Apr 2018 18:47:13 +0100
Patrick O'Callaghan  wrote:

> On Tue, 2018-04-10 at 12:30 -0500, Paul Stejskal wrote:
> > 在 2018-04-10Tue的 18:56 +0200，Milan Crha写道：  
> > > On Tue, 2018-04-10 at 17:37 +0200, Bjørn T Johansen wrote:  
> > > > - Is this the best way or is there a better way? (I am developer
> > > > myself)
> > > > - Do I need follow some specific compiling/installation guides for
> > > > Ubuntu or can just download the source and start compiling? :)  
> > > 
> > >   Hi,
> > > you might find all the answers here:
> > > https://wiki.gnome.org/Apps/Evolution/Building
> > > and eventually here:
> > > https://wiki.gnome.org/Apps/Evolution/Flatpak
> > > after you read the first paragraph of the former. The Flatpak version
> > > as provided in Evolution sources has also its caveats, which you should
> > > be aware of (also the first paragraph, in the second wiki page).
> > > 
> > > Long story short, main issue (and the reason why LTS distros do not
> > > update evolution) is that evolution requires evolution-data-server,
> > > which is also used by other programs (and even GNOME shell), thus when
> > > you update evolution-data-server you usually need to update also all
> > > other installed applications which depend on it. The Building wiki
> > > compiles into a separate prefix, thus you can run the code "in
> > > parallel", which usually works (at least here). The Ubuntu 16.04 is
> > > really old, you'll see how well it'll work for you.
> > >   Bye,
> > >   Milan  
> > 
> > 18.04 will be out in a few days. April 29th?  
> 
> An alternative is to just use a distro with better support for
> Evolution (e.g. Fedora), which also meets your VMware requirement. OTOH
> Ubuntu *may* improve general Gnome support in the future now that it
> has abandoned Unity.
> 
> poc

Ok, thx for the input.. Doesn't really sound too promising but I'll do some 
reading and see what I do...
If I install the version in Ubuntu 16, version 3.18.x, what am I missing? Will 
it work ok as an IMAP and Exchange MUA?

Fedora would have been a better option, the problem is that only the following 
are supported by the Horizon client: Ubuntu x64 12.04, 14.04, and
16.04, Red Hat Enterprise Linux (RHEL) 6.8, 6.9, 7.2, 7.3, and 7.4 and SUSE 
Linux Enterprise Desktop (SLED) 12 SP2. And to be able to work from remote I 
need a distro where this client works more or less 100%. I bought this laptop 
so I could leave my Windows PC from work at work.. :)

BTJ 
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [sage-devel] Re: Newest Xcode is causing doctest failures

[John H Palmieri]

On Tuesday, April 3, 2018 at 2:09:17 PM UTC-7, François Bissey wrote:
>
>
>
> > On 4/04/2018, at 02:34, John H Palmieri <jhpalm...@gmail.com 
> > wrote: 
> > 
> > 
> > 
> > On Monday, April 2, 2018 at 9:25:56 PM UTC-7, François Bissey wrote: 
> > 
> > 
> > > On 2/04/2018, at 16:27, John H Palmieri <jhpalm...@gmail.com> wrote: 
> > > 
> > > 
> > > 
> > > On Sunday, April 1, 2018 at 1:16:57 PM UTC-7, François Bissey wrote: 
> > > 
> > > 
> > > > On 2/04/2018, at 03:48, John H Palmieri <jhpalm...@gmail.com> 
> wrote: 
> > > > 
> > > > 
> > > > 
> > > > On Sunday, April 1, 2018 at 2:06:37 AM UTC-7, Volker Braun wrote: 
> > > > On Sunday, April 1, 2018 at 9:01:17 AM UTC+2, Dima Pasechnik wrote: 
> > > > - when I do an incremental upgrade, I do not see these failures. 
> > > > - when I do 'make distclean; make ptestlong', I see them (with 
> > > > 8.2.beta8 or later; I haven't checked earlier versions). 
> > > > 
> > > >  Is it the other way round? Surely it should work with  "make 
> distclean; make ptestlong"? 
> > > > 
> > > > 
> > > > It is not the other way around: failures when building from scratch, 
> no failures when upgrading. 
> > > > 
> > > 
> > > I (painfully) checked on my old laptop and I get this stuff when 
> > > building from scratch too. So we have some kind of new mis-compilation 
> > > with clang. 
> > > 
> > > François 
> > > 
> > > You made a guess in email that it was Singular. Suggestions for how to 
> test this? 
> > > 
> > 
> > Based on the libraries apparently involved. But looking at the chain of 
> > calls, i would be more inlined to suspect something in sage itself. 
> Either 
> > in the glue to singular or in the coercion framework. 
> > But that’s speculative, I have no real ideas. Does anyone know if that 
> breaks 
> > 8.1 as well? If not, we may be able to bisect something. 
> > 
> > François 
> > 
> > I just tried with 8.1, and all tests pass. That builds with gcc, not 
> clang, so it's a big difference. 
>
> Forgot about that! So the earliest we can test is 8.2.beta5. 
>
> François 
>
>
8.2.beta5 doesn't build without #24704 ("ppl build fails with clang-5.0"), 
in case that provides any clues. WIth #24704, I get the same doctest errors.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Newest Xcode is causing doctest failures

[John H Palmieri]

On Monday, April 2, 2018 at 9:25:56 PM UTC-7, François Bissey wrote:
>
>
>
> > On 2/04/2018, at 16:27, John H Palmieri <jhpalm...@gmail.com 
> > wrote: 
> > 
> > 
> > 
> > On Sunday, April 1, 2018 at 1:16:57 PM UTC-7, François Bissey wrote: 
> > 
> > 
> > > On 2/04/2018, at 03:48, John H Palmieri <jhpalm...@gmail.com> wrote: 
> > > 
> > > 
> > > 
> > > On Sunday, April 1, 2018 at 2:06:37 AM UTC-7, Volker Braun wrote: 
> > > On Sunday, April 1, 2018 at 9:01:17 AM UTC+2, Dima Pasechnik wrote: 
> > > - when I do an incremental upgrade, I do not see these failures. 
> > > - when I do 'make distclean; make ptestlong', I see them (with 
> > > 8.2.beta8 or later; I haven't checked earlier versions). 
> > > 
> > >  Is it the other way round? Surely it should work with  "make 
> distclean; make ptestlong"? 
> > > 
> > > 
> > > It is not the other way around: failures when building from scratch, 
> no failures when upgrading. 
> > > 
> > 
> > I (painfully) checked on my old laptop and I get this stuff when 
> > building from scratch too. So we have some kind of new mis-compilation 
> > with clang. 
> > 
> > François 
> > 
> > You made a guess in email that it was Singular. Suggestions for how to 
> test this? 
> > 
>
> Based on the libraries apparently involved. But looking at the chain of 
> calls, i would be more inlined to suspect something in sage itself. Either 
> in the glue to singular or in the coercion framework. 
> But that’s speculative, I have no real ideas. Does anyone know if that 
> breaks 
> 8.1 as well? If not, we may be able to bisect something. 
>
> François 
>

I just tried with 8.1, and all tests pass. That builds with gcc, not clang, 
so it's a big difference.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Newest Xcode is causing doctest failures

[John H Palmieri]

Sorry, yes, I have done 'make distclean; make ptestlong' with 8.2.beta8 and 
8.2.rc0, with the same failed doctests resulting.

  John


On Saturday, March 31, 2018 at 1:06:08 PM UTC-7, François Bissey wrote:
>
> We definitely want to know if that works! 
>
> > On 1/04/2018, at 08:03, Dima Pasechnik <dim...@gmail.com > 
> wrote: 
> > 
> > make distclean 
> > and 
> > make ? 
> > 
> > On Saturday, March 31, 2018 at 8:46:41 PM UTC+1, John H Palmieri wrote: 
> > On an OS X machine, I just did a minor upgrade on the operating system 
> (to 10.13.4) and also Xcode and the command line tools. Now I am getting 
> doctest failures: 
> > 
> > sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 
> doctest failed 
> > sage -t --long src/sage/rings/polynomial/groebner_fan.py  # 70 doctests 
> failed 
> > sage -t --long src/doc/fr/tutorial/tour_advanced.rst  # 2 doctests 
> failed 
> > sage -t --long src/doc/en/tutorial/tour_advanced.rst  # 2 doctests 
> failed 
> > sage -t --long src/doc/ja/tutorial/tour_advanced.rst  # 2 doctests 
> failed 
> > sage -t --long src/doc/pt/tutorial/tour_advanced.rst  # 2 doctests 
> failed 
> > sage -t --long src/doc/de/tutorial/tour_advanced.rst  # 2 doctests 
> failed 
> > sage -t --long src/doc/ru/tutorial/tour_advanced.rst  # 2 doctests 
> failed 
> > 
> > Here is a typical example: 
> > 
> > sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py 
> > ** 
> > File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3304, 
> in 
> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_fan 
> > Failed example: 
> > g.reduced_groebner_bases() 
> > Exception raised: 
> > Traceback (most recent call last): 
> >   File 
> "/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.rc0/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 551, in _run 
> > self.compile_and_execute(example, compiler, test.globs) 
> >   File 
> "/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.rc0/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 961, in compile_and_execute 
> > exec(compiled, globs) 
> >   File " sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_fan[3]>",
>  
> line 1, in  
> > g.reduced_groebner_bases() 
> >   File 
> "/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.rc0/local/lib/python2.7/site-packages/sage/rings/polynomial/groebner_fan.py",
>  
> line 1064, in reduced_groebner_bases 
> > X = [ReducedGroebnerBasis(self, [S(f) for f in G[i].split(',')], 
> G[i]) for i in range(len(G))] 
> >   File "sage/structure/parent.pyx", line 920, in 
> sage.structure.parent.Parent.__call__ 
> (build/cythonized/sage/structure/parent.c:9734) 
> > return mor._call_(x) 
> >   File "sage/structure/coerce_maps.pyx", line 145, in 
> sage.structure.coerce_maps.DefaultConvertMap_unique._call_ 
> (build/cythonized/sage/structure/coerce_maps.c:4555) 
> > raise 
> >   File "sage/structure/coerce_maps.pyx", line 140, in 
> sage.structure.coerce_maps.DefaultConvertMap_unique._call_ 
> (build/cythonized/sage/structure/coerce_maps.c:4417) 
> > return C._element_constructor(x) 
> >   File "sage/rings/polynomial/multi_polynomial_libsingular.pyx", 
> line 982, in 
> sage.rings.polynomial.multi_polynomial_libsingular.MPolynomialRing_libsingular._element_constructor_
>  
> (build/cythonized/sage/rings/polynomial/multi_polynomial_libsingular.cpp:12001)
>  
>
> > raise TypeError("Could not find a mapping of the passed element 
> to this ring.") 
> > TypeError: Could not find a mapping of the passed element to this 
> ring. 
> > ** 
> > 
> > Any suggestions? 
> > 
> > -- 
> > 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+...@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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Newest Xcode is causing doctest failures

[John H Palmieri]

On Sunday, April 1, 2018 at 1:16:57 PM UTC-7, François Bissey wrote:
>
>
>
> > On 2/04/2018, at 03:48, John H Palmieri <jhpalm...@gmail.com 
> > wrote: 
> > 
> > 
> > 
> > On Sunday, April 1, 2018 at 2:06:37 AM UTC-7, Volker Braun wrote: 
> > On Sunday, April 1, 2018 at 9:01:17 AM UTC+2, Dima Pasechnik wrote: 
> > - when I do an incremental upgrade, I do not see these failures. 
> > - when I do 'make distclean; make ptestlong', I see them (with 
> > 8.2.beta8 or later; I haven't checked earlier versions). 
> > 
> >  Is it the other way round? Surely it should work with  "make distclean; 
> make ptestlong"? 
> > 
> > 
> > It is not the other way around: failures when building from scratch, no 
> failures when upgrading. 
> > 
>
> I (painfully) checked on my old laptop and I get this stuff when 
> building from scratch too. So we have some kind of new mis-compilation 
> with clang. 
>
> François 
>

You made a guess in email that it was Singular. Suggestions for how to test 
this?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Pointers needed

[John H Palmieri]

On Sunday, April 1, 2018 at 4:08:14 PM UTC-7, Nils Bruin wrote:
>
>
> On Sunday, April 1, 2018 at 3:43:30 PM UTC-7, Simon King wrote:
>>
>> Also: Have there been changes in how to run optional tests? I tried sage 
>> -t --optional=meataxe, but then Sage was skipping all compulsory tests 
>> (i.e., those that haven't been marked "optional"), so that underlying 
>> variable definitions were missing in the actual optional tests. 
>>
>> I think this has been for a long time: if you test without specifying 
> --optional, the tester prints:
>
> Using --optional=mpir,python2,sage
>
> so probably when you invoke with --optional=mpir,python2,sage,meataxe your 
> get what you want.
>

Right, use the "sage" tag along with "meataxe". This is documented here: 
http://doc.sagemath.org/html/en/developer/doctesting.html#run-optional-doctests

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Newest Xcode is causing doctest failures

[John H Palmieri]

On Sunday, April 1, 2018 at 2:06:37 AM UTC-7, Volker Braun wrote:
>
> On Sunday, April 1, 2018 at 9:01:17 AM UTC+2, Dima Pasechnik wrote:
>>
>> - when I do an incremental upgrade, I do not see these failures. 
>> - when I do 'make distclean; make ptestlong', I see them (with 
>> 8.2.beta8 or later; I haven't checked earlier versions). 
>
>
>  Is it the other way round? Surely it should work with  "make distclean; 
> make ptestlong"?
>
>
> It is not the other way around: failures when building from scratch, no 
failures when upgrading.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Newest Xcode is causing doctest failures

[John H Palmieri]

On an OS X machine, I just did a minor upgrade on the operating system (to 
10.13.4) and also Xcode and the command line tools. Now I am getting 
doctest failures:

sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 
doctest failed
sage -t --long src/sage/rings/polynomial/groebner_fan.py  # 70 doctests 
failed
sage -t --long src/doc/fr/tutorial/tour_advanced.rst  # 2 doctests failed
sage -t --long src/doc/en/tutorial/tour_advanced.rst  # 2 doctests failed
sage -t --long src/doc/ja/tutorial/tour_advanced.rst  # 2 doctests failed
sage -t --long src/doc/pt/tutorial/tour_advanced.rst  # 2 doctests failed
sage -t --long src/doc/de/tutorial/tour_advanced.rst  # 2 doctests failed
sage -t --long src/doc/ru/tutorial/tour_advanced.rst  # 2 doctests failed

Here is a typical example:

sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py
**
File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3304, in 
sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_fan
Failed example:
g.reduced_groebner_bases()
Exception raised:
Traceback (most recent call last):
  File 
"/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.rc0/local/lib/python2.7/site-packages/sage/doctest/forker.py",
 
line 551, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.rc0/local/lib/python2.7/site-packages/sage/doctest/forker.py",
 
line 961, in compile_and_execute
exec(compiled, globs)
  File "",
 
line 1, in 
g.reduced_groebner_bases()
  File 
"/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.rc0/local/lib/python2.7/site-packages/sage/rings/polynomial/groebner_fan.py",
 
line 1064, in reduced_groebner_bases
X = [ReducedGroebnerBasis(self, [S(f) for f in G[i].split(',')], 
G[i]) for i in range(len(G))]
  File "sage/structure/parent.pyx", line 920, in 
sage.structure.parent.Parent.__call__ 
(build/cythonized/sage/structure/parent.c:9734)
return mor._call_(x)
  File "sage/structure/coerce_maps.pyx", line 145, in 
sage.structure.coerce_maps.DefaultConvertMap_unique._call_ 
(build/cythonized/sage/structure/coerce_maps.c:4555)
raise
  File "sage/structure/coerce_maps.pyx", line 140, in 
sage.structure.coerce_maps.DefaultConvertMap_unique._call_ 
(build/cythonized/sage/structure/coerce_maps.c:4417)
return C._element_constructor(x)
  File "sage/rings/polynomial/multi_polynomial_libsingular.pyx", line 
982, in 
sage.rings.polynomial.multi_polynomial_libsingular.MPolynomialRing_libsingular._element_constructor_
 
(build/cythonized/sage/rings/polynomial/multi_polynomial_libsingular.cpp:12001)
raise TypeError("Could not find a mapping of the passed element to 
this ring.")
TypeError: Could not find a mapping of the passed element to this ring.
**

Any suggestions?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

I'm curious: why is the 8.2.beta8 tarball so much smaller than previous 
versions? (According to http://files.sagemath.org/devel/index.html, 
8.2beta8 is about 530MB, while 8.2.beta7 was just under 600MB.)

  John


On Saturday, March 10, 2018 at 4:18:24 PM UTC-8, 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
>
> 9bf9f05f1f (tag: 8.2.beta8, trac/develop) Updated SageMath version to 
> 8.2.beta8
> b262bb1d0a Trac #24896: Link DOIs to preferred resolver
> 00f5bf5e2e Trac #24776: Undirected graph, one-line descriptions
> 516cbe1c94 Trac #24895: yet another typo ticket
> c82c5b377f Trac #22836: ccache fails test suite with clang
> 4343fb9d1d Trac #24087: Automorphism group of finite abelian groups.
> fbad515a22 Trac #24893: some details in graph_latex
> 681e427575 Trac #24779: py3: buffet of minor doctest fixes
> ccb4517da2 Trac #24899: py3: using richcmp in p1list.pyx
> fc9a17f699 Trac #24898: wrong relabel handling in modular_decomposition of 
> graphs
> 2b6ad723cb Trac #24884: Matrix-related fixes in differential geometry
> 919ac0ea21 Trac #24817: Faster creation of complex balls from two 
> integers/rationals
> 4f2874af3c Trac #23700: update gc to version 7.6
> 30d778252c Trac #23505: Lattice precision for p-adics
> 15fbaa620f Trac #21524: configure.ac: write build/make/Makefile within an 
> AC_CONFIG_FILE, not during main configure
> 2972b5ab65 Trac #24867: The check for broken GCC should use 
> src/bin/sage-env
> f3fcca21de Trac #24871: fixing doc formatting in widgets.py
> 3ddf32292a Trac #24844: Some elliptic curve functions do not set a point's 
> order
> 9c6fc0fc70 Trac #24821: _mul_ for FGP_Module_class
> e60a2f4d11 Trac #24001: Some "optional - dot2tex" doctests do not depend 
> on dot2tex
> 6ac29abb46 Trac #23229: Cache fraction_field() of p-adic rings, deprecate 
> print_mode options
> 2d0f85491e Trac #24897: cantor_product does an infinite loop
> 95e44ce471 Trac #24882: various enhancements to cluster quivers
> 5b735cdb6b Trac #24881: Minor fixes involving matrices
> 039f3d4a55 Trac #24879: Typo in Sage documentation
> 28fed0df0d Trac #24874: BooleanMonomialMonoid is commutative
> 815b1f128f Trac #24870: is_rational on Integer and Rational
> e7843192cd Trac #24865: Finite field elements should not have a _matrix_ 
> method
> 6fa03a7f6a Trac #24761: py3: implement PolyDict.__hash__
> 81ed14d159 Trac #24706: py3: create a "make buildbot-python3" target
> 70ee16bf62 Trac #24863: Fix signature of Matrix_gfpn_dense.__init__
> 04844a944b Trac #24856: py3: correct many bad imports in valuation folder
> e84b3fc474 Trac #24851: fixing a wrong doc construction
> 08356e1581 Trac #24845: Typos in src/sage/groups/finitely_presented.py
> 5c9461 Trac #24807: Lazy import of number_field/totallyreal*
> ea6b0f1a0a Trac #24805: py3: miscellaneous division-related fixes, 
> particularly for sage_setup.autogen
> 3acf8f0589 Trac #24797: adding colored faces to threejs plot3d viewer
> bfe6c7e2c4 Trac #24793: py3: get rid of some cmp and __cmp__ in the doc of 
> fast_methods
> f2319c20ab Trac #24792: More functionalities for bases of free modules and 
> vector frames
> e18824419f Trac #24553: Make legendre_P() a GinacFunction
> bef891acad Trac #23896: P and Q symbols for shifted insertion
> c26a067dd1 Trac #16726: Binomial Coefficient of Real- or 
> ComplexIntervalField
> 09a16bd955 Trac #16063: Unify the classes RealSet and UnionOfIntervals
> c3be88d769 Trac #24774: py3: get rid of calls to unicode in inventory 
> builder
> 2675dc2d16 Trac #24764: cython() no longer finds .pxd files in the current 
> working directory
> 5e3adb762f Trac #24753: py3: fixes to sage.repl.rich_output
> fab34f610b Trac #24749: Clean up in integer_mod.pyx
> f73df7e425 Trac #24728: Python 3 fixes to Cython
> 92c50f2eca Trac #24627: Use arb 2.6+ comparison functions instead of 
> custom implementation
> e7cc76ae70 Trac #24595: Clicking on a ToggleButtons widget should run 
> interact
> 1ea4633cba Trac #24083: Factory function for TorsionQuadraticForms
> 8ab65853d8 Trac #24036: Orthogonal groups for IntegralLattices
> 2594e7bd9a Trac #22455: _facet_adjacency_matrix not working correctly for 
> non-fulldimensional polyhedra
> 0b00dc5534 Trac #21937: Library of polytopes should allow specifying 
> backend=...
> 7f23a8f8c9 Trac #16618: The optimization 
> Category_over_base._subcategory_hook_ really belongs to 
> Category_over_base_ring
> 57f1b4d137 Trac #24860: Building brial should use -std=gnu++11 on Cygwin
> c4c315e130 Trac #24840: gambit does not install
> 3d890fa16c Trac #24830: port uncompress/tar_file.py to python3
> 7912fd986b Trac #24767: Failing tests in src/sage/doctest/test.py
> 2951221011 Trac #24756: Don't run pcre test suite on Cygwin
> e9108b62cd Trac #24699: Coxeter3 is broken
> 3750eaa411 (tag: 8.2.beta7) Updated SageMath version to 8.2.beta7
>
>

-- 
You received 

[RBW] David Lance Goines Riv Bike Poster

[John H.]

20

John in Boston

-- 
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 post to this group, send email to rbw-owners-bunch@googlegroups.com.
Visit this group at https://groups.google.com/group/rbw-owners-bunch.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: [sage-cell] Where Oh Where is my Divide By Zero Error?

[John H Palmieri]

On Friday, March 16, 2018 at 7:29:30 PM UTC-7, A. Jorge Garcia wrote:
>
> Thanks! 
>
> On Fri, Mar 16, 2018, 10:27 PM Andrey Novoseltsev  > wrote:
>
>> On Fri, Mar 16, 2018 at 4:18 PM, Jorge Garcia > > wrote:
>> > Dear Hive Mind:
>> >
>> > Why is there no Divide By Zero Error here:
>> > 
>> http://sagecell.sagemath.org/?z=eJwljkELgkAUhO-C_2GiAtek1kuX2Eu4pBc3NjEqCqQ2E-QlpvX3cwuGd5jHzDdjZHGyw6BUZdgoFQXYx1JLa2WxRJTkSSSxPuAotYLUWumR64zRcDEJOecBtFhOA3QitHZpyLRFZ1BR03fDvdb9raISJLjrpKItqDReyNnq9Xh-vJTZkHkXdW9DjUcMvu__F2SIlNxhk-Tyt-UHH76usxUny_a9cMbnfLkgdiHcny1oICI9_8u37AuZcDtw=sage
>> >
>> > But there is a Divide By Zero Error here (as expected):
>> > 
>> http://sagecell.sagemath.org/?z=eJwlj0FLw0AQhe-B_IcnVcimQTeXXmQPtRnsXrJhG6q2WAh2GwtlGmKif9_dBoY5zJvvzZsZ6rXewNerMUWGNwK9V7SqsUSht7ogvHxgR9aArDX2Lo5m6KS6z6WUGaxaPGQYVB5HXcJChWma5HP5KBdPLA78_PN9_UuCJgLZOnZ9MzicuRsH378u4_HMLVjJOCpV33DrklyKiStvkPttLmOAgg3SNF2TJegahSGfW2_JP0FTPq_GUaX2t9XTtQf7Iyg_J79K_AMYbUA7=sage
>> >
>> > Can someone please explain this to me? This came up in class and I was
>> > looking for a "teachable moment" asking the students to fix the Divide 
>> By
>> > Zero Error like this:
>> > 
>> http://sagecell.sagemath.org/?z=eJwljkFrg0AUhO-C_2GKKbhW0t1LLmUvwddmLxq2EtKWBKTZWkGeYjX5-3XjbXgz37yJkJmDyQjbD3ySLUDWFhav5kjZQxhE6KVeKSllCqs3jylGrcKgj1lof01i9STXcvPM4swvf7_dLfae8GTt2A3V6NBwP43Ii3JW3-10abgGaxkGuR4qrl2sUiXFQud31F2rdvKoL0OSJDuyBFMiK-gdb-ZAKHe0bJ3dMNjrr3v0pxvA8xvkp6VvL_4B6uc8qg===sage
>> >
>> > Thanx,
>> > AJG
>>
>> Someone probably can, but perhaps not on this list: it has something
>> to do with 0^0 evaluating to 1 and I recall some earlier discussions
>> about it. Forwarding to sage-support.
>>
>
Maybe related to this:

sage: 2/0
---
ZeroDivisionError Traceback (most recent call last)
 in ()
> 1 Integer(2)/Integer(0)

/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-8.2.beta8/local/lib/python2.7/site-packages/sage/rings/integer.pyx
 
in sage.rings.integer.Integer.__div__ 
(build/cythonized/sage/rings/integer.c:13231)()
   1910 if type(left) is type(right):
   1911 if mpz_sgn((right).value) == 0:
-> 1912 raise ZeroDivisionError("rational division by zero")
   1913 x =  Rational.__new__(Rational)
   1914 mpq_div_zz(x.value, (left).value, 
(right).value)

ZeroDivisionError: rational division by zero
sage: 2.0/0
+infinity

I don't like this behavior much. What is the rationale? In inexact rings, 
zero division is not a thing?

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Make JupyterLab a standard package

[John H Palmieri]

I feel like we need another class of package: "pending" (or perhaps some 
other name) = those which we propose to make standard soon. Most optional 
packages are not intended to be converted to standard, as far as I can 
tell, so "optional" isn't the appropriate tag in this case.

  John


On Tuesday, March 13, 2018 at 4:29:06 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Tuesday, March 13, 2018 at 10:26:55 PM UTC, Samuel Lelievre wrote:
>>
>> 2018-03-13 20:01 GMT+01:00 Jeroen Demeyer :
>> >
>> > On 2018-03-13 18:33, Samuel Lelievre wrote:
>> >>
>> >> Let me try to make the case for making JupyterLab a standard package.
>> >
>> > What is your case for *NOT* making it an optional package first?
>>
>> My view is that since it's pip-installable, it's as though it were
>> already an optional package.
>>
>> What would it mean to make it an optional package? Maybe
>> I just don't understand that.
>>
>
> basically, make up a slot in build/pkgs/ with some mostly meta-data.
>
> And we need a vote. Yes, I vote for make it optional, or 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-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: Unicode 11.0 and 12.0 Cover Design Art

[John H. Jenkins via Unicode]

Maybe we should just throw in the towel and put "DON'T PANIC" on the cover in 
big, friendly letters. 

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

[John H Palmieri]

On Saturday, March 10, 2018 at 7:17:24 PM UTC-8, John H Palmieri wrote:
>
> On Saturday, March 10, 2018 at 4:18:24 PM UTC-8, 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
>>
>> 9bf9f05f1f (tag: 8.2.beta8, trac/develop) Updated SageMath version to 
>> 8.2.beta8
>> b262bb1d0a Trac #24896: Link DOIs to preferred resolver
>> 00f5bf5e2e Trac #24776: Undirected graph, one-line descriptions
>> 516cbe1c94 Trac #24895: yet another typo ticket
>> c82c5b377f Trac #22836: ccache fails test suite with clang
>> 4343fb9d1d Trac #24087: Automorphism group of finite abelian groups.
>> fbad515a22 Trac #24893: some details in graph_latex
>> 681e427575 Trac #24779: py3: buffet of minor doctest fixes
>> ccb4517da2 Trac #24899: py3: using richcmp in p1list.pyx
>> fc9a17f699 Trac #24898: wrong relabel handling in modular_decomposition 
>> of graphs
>> 2b6ad723cb Trac #24884: Matrix-related fixes in differential geometry
>> 919ac0ea21 Trac #24817: Faster creation of complex balls from two 
>> integers/rationals
>> 4f2874af3c Trac #23700: update gc to version 7.6
>> 30d778252c Trac #23505: Lattice precision for p-adics
>> 15fbaa620f Trac #21524: configure.ac: write build/make/Makefile within 
>> an AC_CONFIG_FILE, not during main configure
>> 2972b5ab65 Trac #24867: The check for broken GCC should use 
>> src/bin/sage-env
>> f3fcca21de Trac #24871: fixing doc formatting in widgets.py
>> 3ddf32292a Trac #24844: Some elliptic curve functions do not set a 
>> point's order
>> 9c6fc0fc70 Trac #24821: _mul_ for FGP_Module_class
>> e60a2f4d11 Trac #24001: Some "optional - dot2tex" doctests do not depend 
>> on dot2tex
>> 6ac29abb46 Trac #23229: Cache fraction_field() of p-adic rings, deprecate 
>> print_mode options
>> 2d0f85491e Trac #24897: cantor_product does an infinite loop
>> 95e44ce471 Trac #24882: various enhancements to cluster quivers
>> 5b735cdb6b Trac #24881: Minor fixes involving matrices
>> 039f3d4a55 Trac #24879: Typo in Sage documentation
>> 28fed0df0d Trac #24874: BooleanMonomialMonoid is commutative
>> 815b1f128f Trac #24870: is_rational on Integer and Rational
>> e7843192cd Trac #24865: Finite field elements should not have a _matrix_ 
>> method
>> 6fa03a7f6a Trac #24761: py3: implement PolyDict.__hash__
>> 81ed14d159 Trac #24706: py3: create a "make buildbot-python3" target
>> 70ee16bf62 Trac #24863: Fix signature of Matrix_gfpn_dense.__init__
>> 04844a944b Trac #24856: py3: correct many bad imports in valuation folder
>> e84b3fc474 Trac #24851: fixing a wrong doc construction
>> 08356e1581 Trac #24845: Typos in src/sage/groups/finitely_presented.py
>> 5c9461 Trac #24807: Lazy import of number_field/totallyreal*
>> ea6b0f1a0a Trac #24805: py3: miscellaneous division-related fixes, 
>> particularly for sage_setup.autogen
>> 3acf8f0589 Trac #24797: adding colored faces to threejs plot3d viewer
>> bfe6c7e2c4 Trac #24793: py3: get rid of some cmp and __cmp__ in the doc 
>> of fast_methods
>> f2319c20ab Trac #24792: More functionalities for bases of free modules 
>> and vector frames
>> e18824419f Trac #24553: Make legendre_P() a GinacFunction
>> bef891acad Trac #23896: P and Q symbols for shifted insertion
>> c26a067dd1 Trac #16726: Binomial Coefficient of Real- or 
>> ComplexIntervalField
>> 09a16bd955 Trac #16063: Unify the classes RealSet and UnionOfIntervals
>> c3be88d769 Trac #24774: py3: get rid of calls to unicode in inventory 
>> builder
>> 2675dc2d16 Trac #24764: cython() no longer finds .pxd files in the 
>> current working directory
>> 5e3adb762f Trac #24753: py3: fixes to sage.repl.rich_output
>> fab34f610b Trac #24749: Clean up in integer_mod.pyx
>> f73df7e425 Trac #24728: Python 3 fixes to Cython
>> 92c50f2eca Trac #24627: Use arb 2.6+ comparison functions instead of 
>> custom implementation
>> e7cc76ae70 Trac #24595: Clicking on a ToggleButtons widget should run 
>> interact
>> 1ea4633cba Trac #24083: Factory function for TorsionQuadraticForms
>> 8ab65853d8 Trac #24036: Orthogonal groups for IntegralLattices
>> 2594e7bd9a Trac #22455: _facet_adjacency_matrix not working correctly for 
>> non-fulldimensional polyhedra
>> 0b00dc5534 Trac #21937: Library of polytopes should allow specifying 
>> backend=...
>> 7f23a8f8c9 Trac #16618: The optimization 
>> Category_over_base._subcategory_hook_ really belongs to 
>> Category

Re: [Swlfest] Emergency Power

[John H. Carver Jr.]

*Ed, I use the simple poor man's method 
of making Faraday cages.  A dead 
microwave oven is one and the other is a 
metal garbage can lined with foam, a 
tight lid and metal tape around the 
joint when the lid is in place.  Both 
were hauled into town and a friend who 
is cellphone crazy helped me test them.  
A cellphone placed inside refused to 
receive calls and also a radio refused 
to work inside once things were sealed 
up.  I'll always believe it works till 
it doesn't.*


*   John*

On 3/11/2018 1:40 PM, Ed Cummings wrote:
I'd really like to see a SWLfest talk 
next year about emergency backup AC 
and DC power, and voltage spike 
suppression (local and whole-house.)


Maybe even a segment about how to 
cheaply shield backup radios and other 
electronics from destruction by a 
coronal mass ejection (CME) like the 
Carrington Event or an Electromagnetic 
Pulse (EMP).


There's plenty to cover here that 
applies to all of us whose passion for 
reliable access to information brought 
us together. Last weekend's SWLfest 
extended power outage was a reality 
check for us, but it's also a good 
opportunity to prepare better for such 
things in the future.


Who in our group is most qualified and 
willing to present a talk on these 
topics next year?


-Ed





---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Swlfest mailing list
Swlfest@hard-core-dx.com
http://montreal.kotalampi.com/mailman/listinfo/swlfest

To unsubscribe:  Send an E-mail to  
swlfest-requ...@hard-core-dx.com?subject=unsubscribe, or visit the URL shown 
above.

For more information on the Fest, visit:

http://www.swlfest.com
http://swlfest.blogspot.com

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

[John H Palmieri]

On Saturday, March 10, 2018 at 4:18:24 PM UTC-8, 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
>
> 9bf9f05f1f (tag: 8.2.beta8, trac/develop) Updated SageMath version to 
> 8.2.beta8
> b262bb1d0a Trac #24896: Link DOIs to preferred resolver
> 00f5bf5e2e Trac #24776: Undirected graph, one-line descriptions
> 516cbe1c94 Trac #24895: yet another typo ticket
> c82c5b377f Trac #22836: ccache fails test suite with clang
> 4343fb9d1d Trac #24087: Automorphism group of finite abelian groups.
> fbad515a22 Trac #24893: some details in graph_latex
> 681e427575 Trac #24779: py3: buffet of minor doctest fixes
> ccb4517da2 Trac #24899: py3: using richcmp in p1list.pyx
> fc9a17f699 Trac #24898: wrong relabel handling in modular_decomposition of 
> graphs
> 2b6ad723cb Trac #24884: Matrix-related fixes in differential geometry
> 919ac0ea21 Trac #24817: Faster creation of complex balls from two 
> integers/rationals
> 4f2874af3c Trac #23700: update gc to version 7.6
> 30d778252c Trac #23505: Lattice precision for p-adics
> 15fbaa620f Trac #21524: configure.ac: write build/make/Makefile within an 
> AC_CONFIG_FILE, not during main configure
> 2972b5ab65 Trac #24867: The check for broken GCC should use 
> src/bin/sage-env
> f3fcca21de Trac #24871: fixing doc formatting in widgets.py
> 3ddf32292a Trac #24844: Some elliptic curve functions do not set a point's 
> order
> 9c6fc0fc70 Trac #24821: _mul_ for FGP_Module_class
> e60a2f4d11 Trac #24001: Some "optional - dot2tex" doctests do not depend 
> on dot2tex
> 6ac29abb46 Trac #23229: Cache fraction_field() of p-adic rings, deprecate 
> print_mode options
> 2d0f85491e Trac #24897: cantor_product does an infinite loop
> 95e44ce471 Trac #24882: various enhancements to cluster quivers
> 5b735cdb6b Trac #24881: Minor fixes involving matrices
> 039f3d4a55 Trac #24879: Typo in Sage documentation
> 28fed0df0d Trac #24874: BooleanMonomialMonoid is commutative
> 815b1f128f Trac #24870: is_rational on Integer and Rational
> e7843192cd Trac #24865: Finite field elements should not have a _matrix_ 
> method
> 6fa03a7f6a Trac #24761: py3: implement PolyDict.__hash__
> 81ed14d159 Trac #24706: py3: create a "make buildbot-python3" target
> 70ee16bf62 Trac #24863: Fix signature of Matrix_gfpn_dense.__init__
> 04844a944b Trac #24856: py3: correct many bad imports in valuation folder
> e84b3fc474 Trac #24851: fixing a wrong doc construction
> 08356e1581 Trac #24845: Typos in src/sage/groups/finitely_presented.py
> 5c9461 Trac #24807: Lazy import of number_field/totallyreal*
> ea6b0f1a0a Trac #24805: py3: miscellaneous division-related fixes, 
> particularly for sage_setup.autogen
> 3acf8f0589 Trac #24797: adding colored faces to threejs plot3d viewer
> bfe6c7e2c4 Trac #24793: py3: get rid of some cmp and __cmp__ in the doc of 
> fast_methods
> f2319c20ab Trac #24792: More functionalities for bases of free modules and 
> vector frames
> e18824419f Trac #24553: Make legendre_P() a GinacFunction
> bef891acad Trac #23896: P and Q symbols for shifted insertion
> c26a067dd1 Trac #16726: Binomial Coefficient of Real- or 
> ComplexIntervalField
> 09a16bd955 Trac #16063: Unify the classes RealSet and UnionOfIntervals
> c3be88d769 Trac #24774: py3: get rid of calls to unicode in inventory 
> builder
> 2675dc2d16 Trac #24764: cython() no longer finds .pxd files in the current 
> working directory
> 5e3adb762f Trac #24753: py3: fixes to sage.repl.rich_output
> fab34f610b Trac #24749: Clean up in integer_mod.pyx
> f73df7e425 Trac #24728: Python 3 fixes to Cython
> 92c50f2eca Trac #24627: Use arb 2.6+ comparison functions instead of 
> custom implementation
> e7cc76ae70 Trac #24595: Clicking on a ToggleButtons widget should run 
> interact
> 1ea4633cba Trac #24083: Factory function for TorsionQuadraticForms
> 8ab65853d8 Trac #24036: Orthogonal groups for IntegralLattices
> 2594e7bd9a Trac #22455: _facet_adjacency_matrix not working correctly for 
> non-fulldimensional polyhedra
> 0b00dc5534 Trac #21937: Library of polytopes should allow specifying 
> backend=...
> 7f23a8f8c9 Trac #16618: The optimization 
> Category_over_base._subcategory_hook_ really belongs to 
> Category_over_base_ring
> 57f1b4d137 Trac #24860: Building brial should use -std=gnu++11 on Cygwin
> c4c315e130 Trac #24840: gambit does not install
> 3d890fa16c Trac #24830: port uncompress/tar_file.py to python3
> 7912fd986b Trac #24767: Failing tests in src/sage/doctest/test.py
> 2951221011 Trac #24756: Don't run pcre test suite on Cygwin
> e9108b62cd Trac #24699: Coxeter3 is broken
> 3750eaa411 (tag: 8.2.beta7) Updated SageMath version to 8.2.beta7
>
>
Upgrading from 8.2.beta7, the file build/make/Makefile got corrupted, in 
particular the section on dependencies: the first dependency on each line 
got changed by prepending "$(SAGE_LOCAL)/bin/gcc". For example:

deps_libgd =  

[imp] HTML email replies badly formatted

[John H. Bennett III]

Hello all,

I get a lot of html email, and I have my preference set to reply using  
the same format as the original message.  When I go to reply to these  
emails with imp, the reply is badly formatted.  There are multiple  
line breaks everywhere within the response, and I have to actually  
edit the original email to make it not look so slopy and  
unprofessional. 


This doesn't happen in Outlook or Thunderbird, so I'm pretty certain  
it's in the way imp is interpreting the message, but I don't have any  
real way to prove that other than what I see in how the email response  
is formatted.  Has anyone found a fix or permanent workaround for  
this?  How else are others dealing with it?  I had seen a suggestion a  
while back in the archives, but that suggestion would then be broken  
upon the new code upgrade.  I had tested this a while back with the  
GIT checkout I had, and saw the same behavior.


Thank you in advance,

John
--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org

[sage-support] Re: Error compiling : patch-2-7-5

[John H Palmieri]

On Friday, March 2, 2018 at 2:51:17 AM UTC-8, Viviane Pons wrote:
>
> Dear all,
>
> I already have a sage installed from binaries (from the debian package) 
> and I'm trying to compile a dev version from source. 
>
> I'm getting this error (log attached) after less than 1 minute. Does 
> someone know why?
>
> I have a Ubuntu 16.04. My default python is 3.6.1 (is this the problem?). 
>

Yes.

 

> It looks like some conflicts with some local stuff. 
>
> Best
>
> Viviane
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] OS X (or BSD) testers needed

[John H Palmieri]

$ uname -a
Darwin John-iMac-2017.local 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 
09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
$ gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack

status = 4



On Thursday, February 22, 2018 at 7:24:00 AM UTC-8, David Roe wrote:
>
>
> Darwin Davids-MBP 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 
> PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
> status = 4
>
> On Thu, Feb 22, 2018 at 4:21 PM, David Joyner  > wrote:
>
>> On Thu, Feb 22, 2018 at 10:16 AM, Jeroen Demeyer > > wrote:
>> > On 2018-02-22 16:13, David Joyner wrote:
>> >>
>> >> clang: error: no such file or directory: 'forksigaltstack.c'
>> >> clang: error: no input files
>> >
>> >
>> > Sorry, I obviously forgot to mention the step "copy the attached file
>> > forksigaltstack.c to the current working directory" and then run
>> >
>> > uname -a
>> > gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack
>> >
>>
>> jeeves:~ wdj$ gcc forksigaltstack.c -o forksigaltstack && 
>> ./forksigaltstack
>> status = 4
>>
>>
>>
>> > --
>> > 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+...@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.
For more options, visit https://groups.google.com/d/optout.

Re: [Simh] EXT : Alpha ES40 emulator

[John H. Reinhardt]

On 2/19/2018 9:20 AM, Hittner, David T [US] (MS) wrote:

The ES40 emulator does have some issues, and development has been discontinued. 
From the ES40 home page: http://es40.org/Homepage


Discontinuation Notice

ES40 emulator development has virtually been halted since 2009. The lead 
developer of ES40, Camiel Vanderhoevenis developing both Freeware and 
Commercial Alpha and VAX emulators for Migration Specialties.

FreeAXP <http://www.freeaxp.com/> is the Freeware Alpha emulator from Migration 
Specialties.

Avanti <http://www.migrationspecialties.com/Emulator-Alpha.html> is the 
Freeware Alpha emulator from Migration Specialties.

I (and the ES40 author) would highly recommend that you use Migration 
Specialties’s FreeAXP emulator instead of ES40 if you are just looking to 
successfully run OpenVMS on an Alpha emulator. FreeAXP is a stable and 
supported Alpha emulator for both OpenVMS and TRU64 and is available at no cost.

http://www.migrationspecialties.com/FreeAXP.html

Dave


The lack of a Non-Windows host makes this a non-starter for me.  All I have are 
Linux and macOS systems here. I won't buy a Windows license to run under an 
emulator to run an emulator for an Alpha.  The limitation to 128MB of memory on 
the FreeAXP emulator is also a problem.  Being free, I realize I have little 
firm ground to stand on, but I just wanted to make it known that it's hardly an 
ideal solution for everyone.

I look forward if/when SimH has as good of an Alpha emulation as it does PDP 
and VAX.

John H. Reinhardt
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] best way to scan 172 column fanfold 80s printout?

[John H. Reinhardt]

On 2/11/2018 12:17 PM, Al Kossow wrote:



On 2/11/18 10:11 AM, Dan Gahlinger wrote:


which is why I wondered what people thought of turning an old DEC teletype or 
printer into a scanner, by fixing a camera
to it


sounds like a bigger version of the Thunderscan
https://www.folklore.org/StoryView.py?story=Thunderscan.txt


I've still got one along with the ImageWriter II that I used it with.  The 
article was pretty much correct.  The Thunderscan could work really well or 
really not, It just depended on what you were scanning and how well the 
ImageWriter felt like working that day.

John H. Reinhardt
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: OpenVMS software repositories?

[John H. Reinhardt via cctalk]

On 2/8/2018 9:56 AM, John H. Reinhardt via cctalk wrote:

On 2/8/2018 9:39 AM, Zane Healy via cctalk wrote:



On Feb 8, 2018, at 5:28 AM, Bill Gunshannon via cctalk <cctalk@classiccmp.org> 
wrote:

On 02/07/2018 10:30 PM, Zane Healy via cctalk wrote:

On Feb 7, 2018, at 7:22 PM, Grant Taylor via cctalk <cctalk@classiccmp.org> 
wrote:

On 02/07/2018 06:35 PM, Zane Healy via cctalk wrote:

What sites still exist that have VMS software?  I know the about the OpenVMS 
Freeware CD’s from HP VMS Engineering.

I'd suggest that you redirect your question to the comp.os.vms newsgroup.  I 
frequently see discussions there about software archives. In fact, you can 
probably search an archive of the group and find some answers to your question.

I need to see about getting back on comp.os.vms, I’ve not been active there in 
a decade.




Don't worry, it hasn't changed a bit.  :-)

bill


I’m sure.  I just need to figure out how to get access, preferably with ’tin'.  
One of the reasons I dropped off was time, another was my ISP dropping USENET 
access.

Zane





You might try <http://www.eternal-september.org> . I don't know if tin will 
work, but it's recommended by Hoff and others.  It's free and reasonably frustration 
free.  They have had a couple server hiccups in the last year though.  I use it via 
Thunderbird on my Mac without too much trouble.



Apparently tin will work. It's listed under their "FAQ" section as possibly 
needing a special tweak.

tin
add the following line to the .newsauth file in your home directory (or create 
the file, if it doesn't exist) and make sure the file is only readable and 
writable for your user (chmod .newsauth 600):

news.eternal-september.org password username

and start tin with the -A option



--
John H. Reinhardt

Re: OpenVMS software repositories?

[John H. Reinhardt via cctalk]

On 2/8/2018 9:39 AM, Zane Healy via cctalk wrote:



On Feb 8, 2018, at 5:28 AM, Bill Gunshannon via cctalk <cctalk@classiccmp.org> 
wrote:

On 02/07/2018 10:30 PM, Zane Healy via cctalk wrote:

On Feb 7, 2018, at 7:22 PM, Grant Taylor via cctalk <cctalk@classiccmp.org> 
wrote:

On 02/07/2018 06:35 PM, Zane Healy via cctalk wrote:

What sites still exist that have VMS software?  I know the about the OpenVMS 
Freeware CD’s from HP VMS Engineering.

I'd suggest that you redirect your question to the comp.os.vms newsgroup.  I 
frequently see discussions there about software archives. In fact, you can 
probably search an archive of the group and find some answers to your question.

I need to see about getting back on comp.os.vms, I’ve not been active there in 
a decade.




Don't worry, it hasn't changed a bit.  :-)

bill


I’m sure.  I just need to figure out how to get access, preferably with ’tin'.  
One of the reasons I dropped off was time, another was my ISP dropping USENET 
access.

Zane





You might try <http://www.eternal-september.org> . I don't know if tin will 
work, but it's recommended by Hoff and others.  It's free and reasonably frustration 
free.  They have had a couple server hiccups in the last year though.  I use it via 
Thunderbird on my Mac without too much trouble.

--
John H. Reinhardt

Re: [Simh] RSTS/E Reminiscing

[John H. Reinhardt]

On 2/7/2018 1:42 PM, Johnny Billquist wrote:

On 2018-02-07 18:01, John H. Reinhardt wrote:

With all the recent discussion of BASIC games and such, I have been reminiscing 
about my first days introduced to RSTS/E and the PDP-11 at Rose-Hulman 
Institute of Technology's Camp Retupmoc in summer 1977.  At the time they were 
running V6B on their PDP-11/70.  I've searched for some time for various 
versions of RSTS/E and I've found a few distributions.


The joy of reliving yesteryear... ;-)


I have a real PDP-11 chassis and cards which I am slowly working toward 
refurbishing.  But they are newer MicroPDP-11 types and would not run anything 
older than V8 or V9.  I've found a copy of V6C which is pretty close but I'm 
wondering if anyone has V6B on TAP format. Hopefully the SYSGEN tape or a 
running system that can be re-configured.  I would run it on a SIM-11 emulation.


I would have expected V7 something to be the ultimate if you wanted "old" style 
RSTS/E. V8 might also fit the bill. V9 definitely have a different taste, though...


I know mention has been made of source listing/tapes.  I don't know the 
legality but if it's possible to get source for a V6 or even V7 I'd love to 
have it to look at to see how things were done.


While I really can't help with finding any distributions, I can at least 
comment on the legality question, even if you won't like the answer. RSTS/E is 
still owned by someone (XX2247 LLC) and is not available as things stand today.
It's a long story...

   Johnny



Hi Johnny,

We actually ran V7.x for the majority part of the time I was at Rose-Hulman (1978-1983) 
but V6B was my first exposure to RSTS/E and in fact to just about any "large" 
computing system.  At the time in 1977 when I went to the camp I had been working on 
building a Digital Group Z-80 from kits but hadn't finished.  It might be that V7 was the 
epitome classic RSTS/E before DCL, etc but your first is something special.

I have been following all the news about the disappearance of Mentec, the 
shadowy existance of XX2247, LLC and all.  I was hoping there was news that I'd 
missed. But I see not.


--
John H. Reinhardt
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

[Simh] RSTS/E Reminiscing

[John H. Reinhardt]

With all the recent discussion of BASIC games and such, I have been reminiscing 
about my first days introduced to RSTS/E and the PDP-11 at Rose-Hulman 
Institute of Technology's Camp Retupmoc in summer 1977.  At the time they were 
running V6B on their PDP-11/70.  I've searched for some time for various 
versions of RSTS/E and I've found a few distributions.

I have a real PDP-11 chassis and cards which I am slowly working toward 
refurbishing.  But they are newer MicroPDP-11 types and would not run anything 
older than V8 or V9.  I've found a copy of V6C which is pretty close but I'm 
wondering if anyone has V6B on TAP format. Hopefully the SYSGEN tape or a 
running system that can be re-configured.  I would run it on a SIM-11 emulation.

I know mention has been made of source listing/tapes.  I don't know the 
legality but if it's possible to get source for a V6 or even V7 I'd love to 
have it to look at to see how things were done.


--
John H. Reinhardt
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: Support for Extension F

[John H. Jenkins via Unicode]

macOS (and iOS, for that matter) fully support Extension F provided fonts are 
availble. I'm not aware of any work that Apple has done to its fonts for 
Extension F support. Indeed, I'm not aware of any publically available fonts 
for Extension F but would gladly install one myself if it's available.

> On Jan 29, 2018, at 10:26 PM, via Unicode  wrote:
> 
> 
> Dear All,
> 
> As many of you are aware getting characters encoded is only half the battle, 
> enabling people to use them is the other half.
> 
> CJK Extenion F was added last year in Unicode 10. I have come across a number 
> of people saying they are having problems with Ext F. I was wondering what 
> the current support is for Ext F at OS level and in terms of fonts.
> 
> Regards
> John Knightley

[sage-devel] Re: sagemath problems

[John H Palmieri]

Yes, can someone please look into this? zulip hasn't worked in a few days 
now.

  John


On Sunday, January 28, 2018 at 11:51:39 PM UTC-8, Ralf Stephan wrote:
>
> Hello,
> processing of ticket actions is quite slow and zulip.sagemath.org gives a 
> 502, both since at least yesterday. Can someone please have a look?
>
> Regards,
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: TypeError: unsupported operand parent(s) for *: <(1,3)(2,4), (1,4,3,2)> and S4

[John H Palmieri]

I'm not sure if Sage can always tell, if you multiply an element of a 
subgroup by an element of the larger group, that the result should make 
sense and lie in the larger group. You should be able to fix this by 
forcing Sage to consider the subgroup element as lying in the larger group: 
rather than

S4.subgroups()[19][1] * S4[1]

use

S4(S4.subgroups()[19][1]) * S4[1]


On Monday, January 29, 2018 at 3:20:16 PM UTC-8, Hsin-Po Wang wrote:
>
> The following code
>
> sage: S4=SymmetricGroup(*4*)
>
> sage: S4.subgroups()[*19*][*1*]*S4[*1*]
>
> raises an error
>
> TypeError: unsupported operand parent(s) for *: 'Subgroup of (Symmetric 
> group of order 4! as a permutation group) generated by [(1,3)(2,4), 
> (1,4,3,2)]' and 'Symmetric group of order 4! as a permutation group'
>
> I am not sure what exactly happened but this is quite peculiar. Among al 
> 30 subgroups of S4 only the 19th and 27th raise errors.
>
> sage: *for* Sid,S in enumerate(S4.subgroups()):
>
> : *for* s in S:
>
> : *for* g in S4:
>
> : *try*:
>
> : sg=s*g
>
> : *except* *TypeError*:
>
> : #print'For {}-th subgroup: {}*{} is 
> bad'.format(Sid,s,g)
>
> : *print* Sid,
>
> : 
>
>
> 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 
> 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 
> 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 
> 19 19 19 19 19 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 
> 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 
> 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 
> 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 
> 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 
> 27 27 27 27 27 27 27 27
>
> I am using Sage 8.0.0 on macOS 10.13.2
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: I tried plotting the recent equation of sin and it does not let me execute it

[John H Palmieri]

If you tried "-4sin(2x-pi)", maybe try instead "-4*sin(2*x-pi)" -- include 
* for multiplication.

On Friday, January 26, 2018 at 1:11:51 PM UTC-8, benjamin gonzalezjr wrote:
>
> Good afternoon, my name is Benjamin Gonzalez Jr. 
> I need help on how to graph -4sin(2x-pi) on cocalc/sage. I tried 
> everything I could but unfortunately I wasn't able to. I need to plot it 
> and figure out x mins, xmax, etc.. also amplitude, phase, period, 
> midpoint, etc. Thanks you so much! Please answer as soon as possible. 
> Thanks!
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Emoji for major planets at least?

[John H. Jenkins via Unicode]

Well, you can go with Venus = white planet, Mercury = grey planet, Uranus = 
greenish planet, Neptune = bluish planet, Jupiter = striped planet.

As you say, though, without a context, none of them convey much and Venus, at 
least, would just be a circle. 

Plus there's the question of the context in which someone would want to send 
little pictures of the planets. This sounds like it would be adding emoji just 
because.

> On Jan 18, 2018, at 10:44 AM, Asmus Freytag via Unicode  
> wrote:
> 
> On 1/18/2018 6:55 AM, Shriramana Sharma via Unicode wrote:
>> Hello people.
>> 
>> We have sun, earth and moon emoji (3 for the earth and more for the
>> moon's phases). But we don't have emoji for the rest of the planets.
>> 
>> We have astrological symbols for all the planets and a few
>> non-existent imaginary "planets" as well.
>> 
>> Given this, would it be impractical to encode proper emoji characters
>> for the rest of the planets, at least the major ones whose physical
>> characteristics are well known and identifiable?
>> 
>> I mean for example identifying Sedna and Quaoar
>> (https://en.wikipedia.org/wiki/File:EightTNOs.png 
>> ) is probably not
>> going to be practical for all those other than astronomy buffs but the
>> physical shapes of the major planets are known to all high school
>> students…
>> 
> Earth = blue planet (with clouds)
> 
> Mars = red planet
> 
> Saturn = planet with rings
> 
> I don't think any of the other ones are identifiable in a context-free 
> setting, unless you draw a "big planet with red dot" for Jupiter.
> 
> Earth would have to be depicted in a way that doesn't focus on "hemispheres", 
> or you miss the idea of it as "planet".
> 
> 
> 
> A./
> 
> 
> 

[sage-devel] Re: request to build/test mac-app on OSX 10.13

[John H Palmieri]

 I tried this. First I build sage, then did

$ cd src/mac-app
$ make

This led to an apparent error:

mkdir -p sage-8.1-OSX_10.13.2_x86_64
make: *** No rule to make target 
`sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/Contents/Resources/sage/sage', 
needed by `sage_symlink'.  Stop.
make: *** Waiting for unfinished jobs
xcodebuild -target Sage -configuration Debug \
ARCHS=x86_64 \
ONLY_ACTIVE_ARCH=NO \
SDKROOT=
Build settings from command line:
ARCHS = x86_64
ONLY_ACTIVE_ARCH = NO
SDKROOT = 

At this point it continued with 

=== BUILD TARGET Sage OF PROJECT Sage WITH CONFIGURATION Debug ===


and then after just a few minutes, it said

** BUILD SUCCEEDED **
mkdir -p sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app
cp -pRL build/Debug/Sage.app/ sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app
plutil -convert xml1 sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/Contents/
Info.plist
sed -i '' "s/SAGE_VERSION/8.1/" sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app
/Contents/Info.plist

but produced no .dmg file. If I make the change 

diff --git a/src/mac-app/Makefile b/src/mac-app/Makefile
index 430121647a..d0c8238cbc 100644
--- a/src/mac-app/Makefile
+++ b/src/mac-app/Makefile
@@ -103,7 +103,7 @@ $(TARGET)/README.txt: $(SAGE_ROOT)/src/bin/sage-README-
osx.txt
 
 non_app_files: $(TARGET)/README.txt $(TARGET)/.background/sage.png $(TARGET
)/Applications
 
-sage_symlink: $(APP)/Contents/Resources/sage/sage
+sage_symlink: $(APP)/Contents/Resources/sage
rm -f $(APP)/sage
ln -s Contents/Resources/sage/sage $(APP)/sage

 
then it seems to actually build correctly, producing a .dmg file.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [min_spanning_tree] It is not operating correctly

[John H Palmieri]

Can you explain more fully what is wrong? The output looks like a spanning 
tree to me. A question and a comment: what do you mean by "the result is 
193"? Also, according to the documentation, the "starting_vertex" option is 
only available for  the algorithms "Prim_fringe" and "Prim_edge".



On Monday, December 4, 2017 at 5:38:39 PM UTC-8, fco...@uea.edu.br wrote:
>
> Hello.
>
> Apparently, min_spanning_tree is not operating properly (see 
> printscreens). Manually, the result is 193. I tried several algorithms and 
> the error persists. Or am I wrong?
>
> Regards,
> Flávio.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Issue with quick start

[John H Palmieri]

I think it is much more important to fix bugs and to add new functionality 
to Sage.

Regarding consistency:
"A foolish consistency is the hobgoblin of little minds" -- Ralph Waldo 
Emerson
"Consistency is contrary to nature, contrary to life. The only completely 
consistent people are the dead." – Huxley.
'Consistency is the last refuge of the unimaginative': O. Wilde

Regarding your first sentence: do you really think that clarity is somehow 
sacrificed by using "maths" instead of "math"? I am very dubious.

Finally, there is virtue in recognizing that Sage is supported by a 
world-wide network of contributors, and people speak different languages 
around the world (BTW: we welcome translations of Sage documentation to 
more languages!). Even among those of us that speak English, there are 
variations in how we speak it. Recognizing and supporting this is valuable, 
just as is encouraging all other types of diversity in Sage, in 
mathematics, in life.


On Friday, December 1, 2017 at 4:46:35 PM UTC-8, DC wrote:
>
> For the sake of clarity, definite points can be made to unequivocally 
> illustrate the need to take the very simple step and *be* *consistent*, 
> by combing over this system and using the term "MATH" :
>
> Using the full word "mathematics" is a noble suggestion, and even 
> acceptable to a point, however communicative human nature yearns for 
> abbreviation (as seen clearly in many programming languages), so more than 
> likely the proper abbreviation needs to be chosen. Objective consistency is 
> the goal, not personal preference.
>
> Perhaps the absolute indication that the site needs to be revised to use 
> the term "math" is the very premise and name of the product, SageMath. 
> Either the term should remain consistent, or the name of the product must 
> be changed to SageMaths.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Issue with quick start

[John H Palmieri]

On Friday, December 1, 2017 at 6:43:05 AM UTC-8, kcrisman wrote:
>
>
>
> On Thursday, November 30, 2017 at 6:50:09 PM UTC-5, Matthew Schroeder 
> wrote:
>>
>> Dear John,
>>
>> Thank you for your interest in resolving this problem.  
>>
>> To answer your question I am referring to  
>> http://www.sagemath.org/tour-quickstart.html.  I was reading this to get 
>> an idea of what SAGE can do, when I hit this road block :)
>>
>> "Sort of supports" my point?  I tracked down a video of an interview with 
>> a professor of Linguistics, within which she addresses this very issue.  
>> During these dark times in America (and the world) 
>> in which the expert is increasingly marginalized, I am surprised to see 
>> Dr. Murphy's comments so readily dismissed here in an academic forum.
>> Please visit her home page  at 
>> the University
>> of Sussex.  On her homepage you will see that Dr Murphy's areas of 
>> expertise include "American English" and "British English".  In watching 
>> the video, I was struck by the rich and long history of this problem. 
>> I was hoping that by presenting this information, others would have the 
>> intellectual honesty to move past their individual preferences and just 
>> consider the facts.  Doing this seems the only way that mistakes  like 
>> "Maths"
>> will ever be corrected.
>>
>
> I'm not sure if this is parody or not; I'll assume not.  Suffice to say 
> that despite the very sound linguistic analysis of the *origin* of "maths" 
> (I wish the "pea(s)" example were better known), note her key argument in 
> the original blog post:
>
> "there's absolutely no reason why maths should be considered to be more 
> correct than math." 
>
> That is NOT the same as "math should be considered more correct than 
> maths"; I would suspect that most descriptive linguists (which is most 
> academic linguists now?) would not go that far.Even the author says, 
> "Myself, 
> I do tend to say maths in BrE company, but only because it's so painful 
> not to." (and she's American).  I.e., in British English, apparently this 
> has within a century become the nearly-universal accepted rendition.
>
> So the resolution is either
> 1) Do nothing because both are common practice in the standard version of 
> American/received British dialects, and because it's not really that 
> important given that SageMath users come from all over the world - even 
> those who are native English speakers
> 2) Change "maths" to "math" in that isolated instance because the roots of 
> SageMath are in American English vernacular, as evidenced by the fact this 
> entire forum is in English, for consistency's sake
>

(1) makes sense to me, or if we have to make a change, change it to 
"mathematics", as John Cremona said.


> > Anyway, what "quick start" are you talking about? The phrase "symbolic 
> maths" does not appear anywhere in the Sage source code, nor does 
> "numerical maths".
>
> John, he is referring to http://www.sagemath.org/tour-quickstart.html 
> which is indeed not part of the Sage source code.  See 
> https://github.com/sagemath/website/commits/master/src/tour-quickstart.html 
> for the source of this - apparently someone long, long ago wrote this in 
> the original website.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Issue with quick start

[John H Palmieri]

On Thursday, November 30, 2017 at 12:22:05 PM UTC-8, Matthew Schroeder 
wrote:
>
> i did some research.  Please see the link:  Saying "Maths" is wrong 
> 
>

Turns out this is a problem that should be fixed.
>


I assume you're joking. With this assumption: whoa! You found something on 
the internet, in fact a YouTube video, which sort of supports your point. 
You must be right!
 
Anyway, what "quick start" are you talking about? The phrase "symbolic 
maths" does not appear anywhere in the Sage source code, nor does 
"numerical maths".

 

>
> On a side note:  Did someone who speaks French just accuse people of being 
> lazy for ignoring consonants on the end of words?
>
>
> On Tuesday, November 28, 2017 at 4:03:05 PM UTC-8, Matthew Schroeder wrote:
>>
>> In the headings of the quick start it says things like "Symbolic *Maths*"  
>> and "Numerical *Maths*"
>>
>> It is MATH not MATHS.  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

 
On Friday, November 17, 2017 at 10:40:22 AM UTC-8, Simon King wrote:
>
> Hi John, 
>
> On 2017-11-17, John H Palmieri <jhpalm...@gmail.com > wrote: 
> >> And WHY that change was made! 
> >> 
> > 
> > If it takes a while to build the documentation, better to start as soon 
> as 
> > possible, rather than to wait until the last possible time, right? 
>
> If the user's purpose is to use Sage, better make it usable as soon as 
> possible. 
>
> Moreover: Have the for-years-frequently-occurring "sporadic" doc build 
> failures been fixed at last? Otherwise: Better build as soon as possible 
> what does reliably build (i.e., sage/src), rather than frustrating the 
> user. 
>
> Best regards, 
> Simon 
>
>
For the first paragraph, we have to deal with the definition of "usable". 
The philosophy for some time has been that Sage without documentation is 
not fully usable. (Plus having the documentation build in parallel with 
some Sage packages may not slow down the build of 
Sage-minus-the-documentation that much. I don't really know.)

For the second paragraph, there has been some progress made, yes. Also, 
there is the question of to what extent the default build process should be 
tailored toward developers, who are more likely to run into problems with 
the documentation (because the problems have occurred in the past when 
changing branches, for example), vs. toward users who are not developers. 
My opinion is that developers should come low on the priority list; we can 
always use "make build" to skip the documentation build, if we want, or use 
"make doc-html-no-plot" to skip the plots (which can take a while), etc. 
For users who are not developers, having the Sage build process end (fully, 
including the documentation) more quickly is better.

  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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

On Friday, November 17, 2017 at 6:37:54 AM UTC-8, Simon King wrote:
>
> On 2017-11-17, Kwankyu Lee  wrote: 
> > Ah, I didn't know that. This (building the documentation is no longer 
> the 
> > last step) sounds a big change to me. I wonder when that change was 
> made. 
>
> And WHY that change was made! 
>

If it takes a while to build the documentation, better to start as soon as 
possible, rather than to wait until the last possible time, right?


 

>
> Is it still possible to build SageMath without documentation ("make 
> start")? 
>
> Cheers, 
> Simon 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Plane-2-only string

[John H. Jenkins via Unicode]

Ʃ ̥ ́ Ӽ Մ ݭ ݹ ந ன ோ ௦ ௽ ఋ ల ు ూ ృ ౓ ౘ ౥ ౷ ౸ ಜ ೏ ೕ ೖ ക ര േ ൈ ൉ ൩ ൯ ർ ൾ ൿ ග ට ඲ ฉ 

That is an example of forty Cantonese-specific characters which are not obscene 
(that I'm aware of) from Extension B. For the curious, I've appended at the 
bottom the full list of 280 for all of Plane 2 which I was able to pull out of 
the Unihan database. I'm sure some enterprising poet can make something out of 
them.

> On Nov 13, 2017, at 11:20 AM, Peter Constable via Unicode 
>  wrote:
> 
> I’m wondering if anyone could come up with a string of 15 to 40 characters 
> _using only plane 2 characters_ that wouldn’t be gibberish?
> 
> We are considering adding sample-text strings in some of our fonts. (In 
> OpenType, the ‘name’ table can take sample-text strings using name ID 19.) 
> One particular issue we have is the Simsun-ExtB and MingLiU-ExtB fonts, which 
> have CJK characters from plane 2 only.
> 
> Background:
> The Simsun-ExtB and MingLiU-ExtB fonts are meant to complement the Simsun and 
> MingLiU fonts: the combined glyph count exceeds the number of glyphs that can 
> be added in a single OpenType font, and so the “ExtB” fonts are used to 
> contain all of the Plane 2 characters that are supported. For example, the 
> Simsun font supports 28738 BMP characters, and no plane 2 characters, while 
> Simsun-ExtB supports the Basic Latin block from the BMP plus 47,293 plane 2 
> characters. The combined glyph count exceeds 64K, so can’t go into a single 
> font.
> 
> 
> 
> Peter
> 

U+201A9 faan2   (Cant.) to play
U+20325 wu1 wu3 (Cant.) to bow, stoop
U+20341 man3(Cant.) an undesirable situation
U+204FC sip3(Cant.) a wedge; to thrust in
U+20544 nap1(Cant.) 酒Մ, a dimple
U+2076D peng2   (Cant.) to fell, cut; to sweep away
U+20779 gaai3   (Cant.) to cut with a knife or scissors
U+20BA8 naai3   (Cant.) to tie, tow; bring along
U+20BA9 aa1 liu1(Cant.) an interjection; rare, specialized
U+20BCB jai4 jai5   (Cant.) naughty, inferior
U+20BE6 cai3(Cant.) to eat, take a meal
U+20BFD zi1 (Cant.) a final particle indicating affirmation
U+20C0B jaau1   (Cant.) left-handed
U+20C32 eot1(Cant.) to belch
U+20C41 tam3(Cant.) to fool, trick, cheat
U+20C42 dat1(Cant.) to put something or sit wherever one wishes; to 
rebuke, reproach
U+20C43 nip1(Cant.) thin, flat; poor
U+20C53 ngai1   (Cant.) to importune, beg
U+20C58 ngaak6  (Cant.) contrary, opposing, against; disobedient
U+20C65 fik1 jit6 we5   (Cant.) wrangling, a noise; fitful; a soft 
fabric with no body
U+20C77 ming1   (Cant.) small
U+20C78 san2 seon2  (Cant.) phonetic
U+20C9C zaang1  (Cant.) to owe
U+20CCF ce2 ce6 (Cant.) interjection
U+20CD5 caau3   (Cant.) to search
U+20CD6 dap6(Cant.) to strike, pound
U+20D15 miu2(Cant.) to purse the lips; to wriggle
U+20D30 gau6(Cant.) classifier for a piece or lump of something
U+20D47 keu4(Cant.) peculiar, strange
U+20D48 mui2(Cant.) to suck or chew without using the teeth
U+20D49 hong4   (Cant.) hope
U+20D69 go2 (Cant.) that
U+20D6F gwit1 gwit3 (Cant.) onomatopoetic
U+20D7C mang1 mang4 (Cant.) scars on the eyelid; phonetic
U+20D7E waak1   (Cant.) eloquent, sharp-tongued
U+20D7F pe1 pe5 (Cant.) a pair (from the Engl.); to stagger
U+20D9C zai3(Cant.) to do, work; to be willing
U+20DA7 dim6(Cant.) straight, vertical; OK; to pick up with the 
fingers; verbal aspect marker of successful completion
U+20DB2 gap6 kap6   (Cant.) to stare at; to take a big bite
U+20E09 kak1(Cant.) to block, obstruct
U+20E0A tap1(Cant.) an intensifying particle
U+20E0E naa1(Cant.) and, with
U+20E0F ge2 (Cant.) final particle
U+20E10 kam1(Cant.) to endure, last
U+20E11 soek3   (Cant.) soft, sodden
U+20E12 bou2(Cant.) 生ฒ人, a stranger
U+20E3A ngaak6  (Cant.) contrary, opposing
U+20E6D ko1 (Cant.) to call (Engl. loan-word)
U+20E73 git6(Cant.) thick, viscous, dense
U+20E77 ngo4(Cant.) to speak tirelessly
U+20E78 kam2(Cant.) to cover, close up
U+20E7A maai4   (Cant.) verbal aspect marker for comletion or movement 
towards
U+20E7B zam6(Cant.) classifier for smells
U+20E8C gwe1(Cant.) timid
U+20E98 long1 long2 (Cant.) hard to get along with; to rinse, 
spread thin
U+20E9D gaak3   (Cant.) final particle
U+20EA2 gaa1 gaa2   (Cant.) final particle
U+20EAA he3 hi1 (Cant.) in a rush; slovenly
U+20EAB leu1(Cant.) strange, peculiar
U+20EAC he2 (Cant.) final particle
U+20ED7 le4 (Cant.) imperative final particle
U+20ED8  

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

[John H Palmieri]

Yes, I agree, in the sense that the failure is coming from the doctests 
added there. I just tried the same doctests (without the rest of the 
changes from #23742) with 8.1.beta8, and the same thing happens. So it 
looks like #23742 adds doctests but doesn't fully fix the issues that the 
doctests are testing.

Can anyone else reproduce this?


On Thursday, November 9, 2017 at 2:44:43 PM UTC-8, François Bissey wrote:
>
> Smells like https://trac.sagemath.org/ticket/23742 
>
> > On 10/11/2017, at 11:31, John H Palmieri <jhpalm...@gmail.com 
> > wrote: 
> > 
> > WIth OS X 10.12.6, Xcode (and the same happens when building with clang, 
> #12426): 
> > 
> > sage -t --long --warn-long 64.0 src/sage/matrix/matrix_mod2_dense.pyx  # 
> Killed due to kill signal 
> > 
> > ** 
> > Tests run before process (pid=12556) failed: 
> > sage: a = matrix(GF(2),3,range(9),sparse=False); a ## line 8 ## 
> > [0 1 0] 
> > [1 0 1] 
> > [0 1 0] 
> > sage: a.rank() ## line 12 ## 
> > 2 
> > sage: type(a) ## line 14 ## 
> >  
> > sage: a[0,0] = 1 ## line 16 ## 
> > sage: a.rank() ## line 17 ## 
> > 3 
> > sage: parent(a) ## line 19 ## 
> > Full MatrixSpace of 3 by 3 dense matrices over Finite Field of size 2 
> > sage: a^2 ## line 22 ## 
> > [0 1 1] 
> > [1 0 0] 
> > [1 0 1] 
> > sage: a+a ## line 26 ## 
> > [0 0 0] 
> > [0 0 0] 
> > [0 0 0] 
> > sage: b = a.new_matrix(2,3,range(6)); b ## line 31 ## 
> > [0 1 0] 
> > [1 0 1] 
> > sage: a*b ## line 35 ## 
> > sage: b*a ## line 39 ## 
> > [1 0 1] 
> > [1 0 0] 
> > sage: TestSuite(a).run() ## line 43 ## 
> > sage: TestSuite(b).run() ## line 44 ## 
> > sage: a.echelonize(); a ## line 46 ## 
> > [1 0 0] 
> > [0 1 0] 
> > [0 0 1] 
> > sage: b.echelonize(); b ## line 50 ## 
> > [1 0 1] 
> > [0 1 0] 
> > sage: FF = FiniteField(2) ## line 56 ## 
> > sage: V = VectorSpace(FF,2) ## line 57 ## 
> > sage: v = V([0,1]); v ## line 58 ## 
> > (0, 1) 
> > sage: W = V.subspace([v]) ## line 60 ## 
> > sage: W ## line 61 ## 
> > Vector space of degree 2 and dimension 1 over Finite Field of size 2 
> > Basis matrix: 
> > [0 1] 
> > sage: v in W ## line 65 ## 
> > True 
> > sage: M = Matrix(GF(2), [[1,1,0],[0,1,0]]) ## line 68 ## 
> > sage: M.row_space() ## line 69 ## 
> > Vector space of degree 3 and dimension 2 over Finite Field of size 2 
> > Basis matrix: 
> > [1 0 0] 
> > [0 1 0] 
> > sage: M = Matrix(GF(2), [[1,1,0],[0,0,1]]) ## line 75 ## 
> > sage: M.row_space() ## line 76 ## 
> > Vector space of degree 3 and dimension 2 over Finite Field of size 2 
> > Basis matrix: 
> > [1 1 0] 
> > [0 0 1] 
> > sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## 
> line 90 ## 
> > 0 
> > sage: type(random_matrix(GF(2),2,2)) ## line 165 ## 
> >  
> > sage: Matrix(GF(2),3,3,1) # indirect doctest ## line 168 ## 
> > [1 0 0] 
> > [0 1 0] 
> > [0 0 1] 
> > sage: matrix(GF(2),0,[]) * vector(GF(2),0,[]) ## line 177 ## 
> > () 
> > sage: MatrixSpace(GF(2), 2^30)(1) ## line 182 ## 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

WIth OS X 10.12.6, Xcode (and the same happens when building with clang, 
#12426):

sage -t --long --warn-long 64.0 src/sage/matrix/matrix_mod2_dense.pyx  # 
Killed due to kill signal

**
Tests run before process (pid=12556) failed:
sage: a = matrix(GF(2),3,range(9),sparse=False); a ## line 8 ##
[0 1 0]
[1 0 1]
[0 1 0]
sage: a.rank() ## line 12 ##
2
sage: type(a) ## line 14 ##

sage: a[0,0] = 1 ## line 16 ##
sage: a.rank() ## line 17 ##
3
sage: parent(a) ## line 19 ##
Full MatrixSpace of 3 by 3 dense matrices over Finite Field of size 2
sage: a^2 ## line 22 ##
[0 1 1]
[1 0 0]
[1 0 1]
sage: a+a ## line 26 ##
[0 0 0]
[0 0 0]
[0 0 0]
sage: b = a.new_matrix(2,3,range(6)); b ## line 31 ##
[0 1 0]
[1 0 1]
sage: a*b ## line 35 ##
sage: b*a ## line 39 ##
[1 0 1]
[1 0 0]
sage: TestSuite(a).run() ## line 43 ##
sage: TestSuite(b).run() ## line 44 ##
sage: a.echelonize(); a ## line 46 ##
[1 0 0]
[0 1 0]
[0 0 1]
sage: b.echelonize(); b ## line 50 ##
[1 0 1]
[0 1 0]
sage: FF = FiniteField(2) ## line 56 ##
sage: V = VectorSpace(FF,2) ## line 57 ##
sage: v = V([0,1]); v ## line 58 ##
(0, 1)
sage: W = V.subspace([v]) ## line 60 ##
sage: W ## line 61 ##
Vector space of degree 2 and dimension 1 over Finite Field of size 2
Basis matrix:
[0 1]
sage: v in W ## line 65 ##
True
sage: M = Matrix(GF(2), [[1,1,0],[0,1,0]]) ## line 68 ##
sage: M.row_space() ## line 69 ##
Vector space of degree 3 and dimension 2 over Finite Field of size 2
Basis matrix:
[1 0 0]
[0 1 0]
sage: M = Matrix(GF(2), [[1,1,0],[0,0,1]]) ## line 75 ##
sage: M.row_space() ## line 76 ##
Vector space of degree 3 and dimension 2 over Finite Field of size 2
Basis matrix:
[1 1 0]
[0 0 1]
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## line 
90 ##
0
sage: type(random_matrix(GF(2),2,2)) ## line 165 ##

sage: Matrix(GF(2),3,3,1) # indirect doctest ## line 168 ##
[1 0 0]
[0 1 0]
[0 0 1]
sage: matrix(GF(2),0,[]) * vector(GF(2),0,[]) ## line 177 ##
()
sage: MatrixSpace(GF(2), 2^30)(1) ## line 182 ##

**

On Wednesday, November 8, 2017 at 1:30:44 PM UTC-8, 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
>
> b707ce9348 (tag: 8.1.rc0, trac/develop) Updated SageMath version to 8.1.rc0
> 0542f0a7fb Trac #19517: Graphs: canonical_label() and several errors
> c73b0be317 Trac #24143: zeromq: don't use -Werror
> 06dbe2327a Trac #24154: Fix equation handling of 
> Polyhedron.to_linear_program() and thus 
> integral_points_count(preprocess=True)
> 23c060c581 Trac #24062: Upgrade to SymPy-1.1.1
> a89800b2e0 Trac #16801: Conversion of psi(x,y) to/from SymPy
> dc9be1b424 Trac #20204: Fix problems with constructing or converting to 
> SymPy expressions
> 8ad8826519 Trac #23954: Mass change of docstring: from "-" to "--", 
> variables with underscores
> 82666c4788 Trac #24095: Part 2, "Posets.*" to "posets.*"
> 780f69dd4d Trac #24076: Pep8-compliance, lattices.py as an example
> e33beaf80a Trac #24069: let our required header be pep8 compliant
> ca925431c8 Trac #24048: Unify selfdual and self_dual
> 071c1bf918 Trac #18536: Solvers for constant sum games
> 5c90df6193 Trac #24133: py3 : get rid of im_func again
> 13d7a570cb Trac #24132: py3: some care for items() and values()
> 3897c7f864 Trac #24126: py3: some more care for keys()[...]
> 63273442d6 Trac #24119: Create an assuming() context manager
> 701897ecc3 Trac #24114: prefer list(K) over K.list() for syndrom decoder
> 4d82659aaa Trac #24104: Merge the code of ex.solve(...) and solve(...)
> 004a326306 Trac #23991: Update curl to 7.56.1
> 4ddb4717bd Trac #23787: py3: richcmp for ideals
> b78794f137 Trac #23112: Repair math-readline script for interactive use, 
> mathematica_console and make Mathematica pexpect work without helper script
> c59a1adb5b Trac #20439: eigenmatrix_right gives the conjugate of what it 
> should
> a181bc24e8 Trac #24081: Use system curl if possible
> 4398274f52 Trac #24061: Slightly faster test for semiorder
> 7c6371b16d Trac #11541: Add example with solution_dict and substituting in 
> a matrix
> 9d1fdaa3c0 Trac #24127: py3: adding hash for complex fields
> 7ec526c44c Trac #24124: lazy import hecke algebras
> 75e5ef97f6 Trac #24120: Implement the q-Pochhammer symbol
> 20f0073693 Trac #24116: Fix Cython warnings in finite_rings
> 9896ca2282 Trac #24113: Add test for cactus graph
> 326106ee54 Trac #24110: Upgrade to Cython 0.27.2
> 7b3992b637 Trac #24109: Always enable debug.bad_parent_warnings
> 02cebd0016 Trac #24105: Deprecate Sage-specific Cython pragmas like #clib
> e738d859cb Trac #24103: Remove a lot of deprecated code
> b8686f64dd Trac #24026: Upgrade R to 3.4.2
> 75506c95b1 Trac #23982: perfect matchings and containment
> a62930e0e7 Trac #23919: Sage library: standardize on C99 and C++11
> 

Authentication using http

[Thompson, John H. (GSFC-606.2)[PATUXENT TECHNOLOGY PARTNERS]]

Will storing the allowed connections in LDAP work with HTTP
header authentication"?

From reading about LDAP, it seems the answer is “no”
"if the bind attempt is successful, the set of available Guacamole
connections is queried from the LDAP directory by executing an LDAP
query as the bound user. Each Guacamole connection is represented within
the directory as a special type of group: guacConfigGroup. Attributes
associated with the group define the protocol and parameters of the
connection, and users are allowed access to the connection only if they
are associated with that group."

From reading http header, it seems the answer is "maybe  ?"
"This authentication method must be layered on top of some other
authentication extension, such as those available from the main project
website, in order to provide access to actual connections."

The Guacamole documentation is somewhat unclear as to authentication versus 
authorization.

Thanks in advance for any insight you can share!

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

[John H Palmieri]

By the way, on OS X, an SSL-enabled curl is installed along with Xcode, so 
if we use that in Sage, I wonder if R will work with full functionality. 
(See #24081.) If so, OpenSSL would only be "needed" for Sage's pip.

  John


On Monday, October 23, 2017 at 9:05:16 AM UTC-7, Erik Bray wrote:
>
> On Mon, Oct 23, 2017 at 5:15 PM, Emmanuel Charpentier 
> <emanuel.c...@gmail.com > wrote: 
> > 
> >> 
> >> Other participants to discussion, which did not formally vote, or 
> "threw 
> >> their vote away" ((C) Michael Orlitzky) in favor of another option : 10 
> >> people 
> > 
> > 
> > No : make that 7 people... 
> > 
> >> 
> >> David Joyner 
> >> Michael Orlitzky 
> >> Nicolas M Thiéry 
> >> Dr David Kirby 
> >> Thierry (sage-googlesucks@xxx) 
> >> kcrisman 
> >> John H Palmieri 
> > 
> > 
> > Thats seven indeed... Sorry for that lapsus. I was probably thinking of 
> the 
> > sum of discussant + "No" voters... 
>
> I should note that up thread I think I changed my vote to "No", but 
> really there should be a third option specifically along the lines of 
> "support SSL optionally". 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: which browser

[John H Palmieri]

Have you tried setting the BROWSER environment variable? If that doesn't 
work, what about SAGE_BROWSER?

  John


On Friday, October 20, 2017 at 7:38:58 AM UTC-7, John Cremona wrote:
>
> On 20 October 2017 at 15:34, John Cremona  > wrote: 
> > I am running Sage on a linux machine which has chromium-browser as the 
> > default browser, but when I type 
> > 
> > sage --notebook=jupyter 
> > 
> > it starts firefox and opens in a tab there.  How can I get it to use 
> chrome? 
>
>
> sage --notebook=jupyter --browser=chromium-browser 
>
>
> does work but can I make it the default? 
> > 
> > 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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [imp] Trouble viewing a specific email in Imp

[John H. Bennett III]

Quoting Jan Schneider <j...@horde.org>:


Zitat von John H. Bennett III <benne...@thebennetthome.com>:


Quoting "John H. Bennett III" <benne...@thebennetthome.com>:


Quoting Jan Schneider <j...@horde.org>:


Zitat von John H. Bennett III <benne...@thebennetthome.com>:


Hello all,

I am having an issue viewing all of the content in a particular  
email.  I sent info offlist, as the email had some personal  
stuff in it, but the email was viewed fine, so I'm asking the  
larger list for any assistance.


The email has some text that is not being displayed in horde,  
but is showing up on my mobile device.  When I go to open the  
email in horde+, I see these errors in my log, which I didn't  
bother to check earlier.


Oct  10 18:52:59 www HORDE: [imp] Error running command:  
/usr/bin/identify -format "%n" /tmp/imgPysnjx Error:  
/invalidaccess in --run-- Operand stack:--dict:9/18(L)--
F2   78.591   --dict:6/6(L)--   --dict:6/6(L)--
ArialNarrow-Italic   --dict:11/12(ro)(G)--   --nostringval--
CIDFontObject   --dict:6/6(L)--   --dict:6/6(L)--   59231
--dict:6/6(L)--   --nostringval--   PDFCIDFontName
ArialNarrow-Italic Execution stack:%interp_exit   .runexec2   
 --nostringval--   --nostringval--   --nostringval--   2
%stopped_push   --nostringval--   --nostringval--
--nostringval--   false   1   %stopped_push   1862   1   3
%oparray_pop   1861   1   3   %oparray_pop   1845   1   3
%oparray_pop   --nostringval--   --nostringval--   2   1   1
--nostringval--   %for_pos_int_continue   --nostringval--
--nostringval--   --nostringval--   --nostringval--
%array_continue   --nostringval--   false   1   %stopped_push
--nostringval--   %loop_continue   --nostringval--
--nostringval--   --nostringval--   --nostringval--
--nostringval--   --nostringval--   %array_continue
--nostringval--   --nostringval--   --nostringval--
--nostringval--   --nostringval-- Dictionary stack: 
--dict:1154/1684(ro)(G)--   --dict:1/20(G)--
--dict:75/200(L)--   --dict:75/200(L)--
--dict:106/127(ro)(G)--   --dict:286/300(ro)(G)--
--dict:22/25(L)--   --dict:4/6(L)--   --dict:22/40(L)--
--dict:1/1(ro)(G)-- Current allocation mode is local [pid 20530  
on line 814 of "/usr/share/pear/Horde/Image/Im.php"]


This is probably just from creating an attachment preview. The  
body of the message should still render just fine.


Yes sir, I understand that is should render just fine, but it  
isn't for me using edge, chrome, FF, and that is what I am needing  
assistance with.  Mike showed it did on his system, so I'm hopeful  
that it's simply a matter of me having something misconfigured.   
What else could I look at?  mime_driver settings are where I plan  
to start next when I'm able to get back to looking into this.




Looking at the headers, I see these content-types

Content-Type: multipart/mixed; boundary="001a114e27f69963c9055ae41f12"

--001a114e27f69963c9055ae41f12
Content-Type: multipart/related; boundary="001a114e27f69963c7055ae41f11"

--001a114e27f69963c7055ae41f11
Content-Type: multipart/alternative;  
boundary="001a114e27f69963c3055ae41f10"


--001a114e27f69963c3055ae41f10
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


My horde5 installation is up to date. I have this configured in  
horde, conf.php


$conf['image']['convert'] = '/usr/bin/convert';
$conf['image']['identify'] = '/usr/bin/identify';
$conf['image']['driver'] = 'Im';

I'm running a distro based on CentOS 6.

PHP 5.3.3 (cli) (built: Mar 22 2017 12:27:09)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies


I have this installed, ImageMagick-6.7.2.7-6.el6.x86_64

I see on the config page that the pecl version is the preferred  
on to use, but it requires at least php 5.4, and I'm not in a  
position to try to upgrade php on this system.


[root@www RPMS]# pecl install imagick
pecl/imagick requires PHP (version >= 5.4.0), installed version is 5.3.3

I would appreciate any help.

I will try setting this up on CentOS7, and see if the problem  
clears, and if so, then know that I need to get there, so I have  
more current packages installed.


Thank you in advanced,

John




--
Jan Schneider
The Horde Project
https://www.horde.org/

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org


Thank you again,

John


Finally had a chance to look at this more.  In my  
imp/config/mime_drivers.local.php file I have
$mime_drivers['html']['inline'] = true;.  If I change that to  
false, then I can see the text of the email that I reported having  
problems viewing in imp, that displays fine on my mobile device.   
But, that presents another issue in that html email now can't be  
viewed, because of the changed setting.

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

[John H Palmieri]

On Thursday, October 19, 2017 at 2:17:10 PM UTC-7, Dima Pasechnik wrote:
>
> the 1-click openssl install image for OSX is called Xcode, and one can go 
> for a long lunch while waiting for it to finish, even on a fast network...
>
> Apple should pick up the bill for these lunches, and much more, I fully 
> agree.
>

But I don't think that Xcode includes the openssl headers. At least I've 
never been able to find them. Plus perhaps their installed versions of 
libssl are outdated? That's what I've heard about their reasons for not 
including the header files.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [imp] Trouble viewing a specific email in Imp

[John H. Bennett III]

Quoting "John H. Bennett III" <benne...@thebennetthome.com>:


Quoting Jan Schneider <j...@horde.org>:


Zitat von John H. Bennett III <benne...@thebennetthome.com>:


Hello all,

I am having an issue viewing all of the content in a particular  
email.  I sent info offlist, as the email had some personal stuff  
in it, but the email was viewed fine, so I'm asking the larger  
list for any assistance.


The email has some text that is not being displayed in horde, but  
is showing up on my mobile device.  When I go to open the email in  
horde+, I see these errors in my log, which I didn't bother to  
check earlier.


Oct  10 18:52:59 www HORDE: [imp] Error running command:  
/usr/bin/identify -format "%n" /tmp/imgPysnjx Error:  
/invalidaccess in --run-- Operand stack:--dict:9/18(L)--   F2   
 78.591   --dict:6/6(L)--   --dict:6/6(L)--   ArialNarrow-Italic
--dict:11/12(ro)(G)--   --nostringval--   CIDFontObject
--dict:6/6(L)--   --dict:6/6(L)--   59231   --dict:6/6(L)--
--nostringval--   PDFCIDFontName   ArialNarrow-Italic Execution  
stack:%interp_exit   .runexec2   --nostringval--
--nostringval--   --nostringval--   2   %stopped_push
--nostringval--   --nostringval--   --nostringval--   false   1
%stopped_push   1862   1   3   %oparray_pop   1861   1   3
%oparray_pop   1845   1   3   %oparray_pop   --nostringval--
--nostringval--   2   1   1   --nostringval--
%for_pos_int_continue   --nostringval--   --nostringval--
--nostringval--   --nostringval--   %array_continue
--nostringval--   false   1   %stopped_push   --nostringval--
%loop_continue   --nostringval--   --nostringval--
--nostringval--   --nostringval--   --nostringval--
--nostringval--   %array_continue   --nostringval--
--nostringval--   --nostringval--   --nostringval--
--nostringval-- Dictionary stack:--dict:1154/1684(ro)(G)--
--dict:1/20(G)--   --dict:75/200(L)--   --dict:75/200(L)--
--dict:106/127(ro)(G)--   --dict:286/300(ro)(G)--
--dict:22/25(L)--   --dict:4/6(L)--   --dict:22/40(L)--
--dict:1/1(ro)(G)-- Current allocation mode is local [pid 20530 on  
line 814 of "/usr/share/pear/Horde/Image/Im.php"]


This is probably just from creating an attachment preview. The body  
of the message should still render just fine.


Yes sir, I understand that is should render just fine, but it isn't  
for me using edge, chrome, FF, and that is what I am needing  
assistance with.  Mike showed it did on his system, so I'm hopeful  
that it's simply a matter of me having something misconfigured.   
What else could I look at?  mime_driver settings are where I plan to  
start next when I'm able to get back to looking into this.




Looking at the headers, I see these content-types

Content-Type: multipart/mixed; boundary="001a114e27f69963c9055ae41f12"

--001a114e27f69963c9055ae41f12
Content-Type: multipart/related; boundary="001a114e27f69963c7055ae41f11"

--001a114e27f69963c7055ae41f11
Content-Type: multipart/alternative;  
boundary="001a114e27f69963c3055ae41f10"


--001a114e27f69963c3055ae41f10
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


My horde5 installation is up to date. I have this configured in  
horde, conf.php


$conf['image']['convert'] = '/usr/bin/convert';
$conf['image']['identify'] = '/usr/bin/identify';
$conf['image']['driver'] = 'Im';

I'm running a distro based on CentOS 6.

PHP 5.3.3 (cli) (built: Mar 22 2017 12:27:09)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies


I have this installed, ImageMagick-6.7.2.7-6.el6.x86_64

I see on the config page that the pecl version is the preferred on  
to use, but it requires at least php 5.4, and I'm not in a  
position to try to upgrade php on this system.


[root@www RPMS]# pecl install imagick
pecl/imagick requires PHP (version >= 5.4.0), installed version is 5.3.3

I would appreciate any help.

I will try setting this up on CentOS7, and see if the problem  
clears, and if so, then know that I need to get there, so I have  
more current packages installed.


Thank you in advanced,

John




--
Jan Schneider
The Horde Project
https://www.horde.org/

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org


Thank you again,

John


Finally had a chance to look at this more.  In my  
imp/config/mime_drivers.local.php file I have
$mime_drivers['html']['inline'] = true;.  If I change that to false,  
then I can see the text of the email that I reported having problems  
viewing in imp, that displays fine on my mobile device.  But, that  
presents another issue in that html email now can't be viewed, because  
of the changed setting.


On some emails, I get the below message.

This message part contains HTML data, but inline HTML display is disabled.
View

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

[John H Palmieri]

It looks like you haven't installed the OS X command line tools, or they 
got removed when you updated to High Sierra. Try (re)installing them: run 
"xcode-select --install" from a terminal window.

On Monday, October 16, 2017 at 7:58:33 PM UTC-7, moep wrote:
>
> Thanks for the response! I tried out Choice 1 and I got the git business 
> to work (I also pulled #23972, because the first time I tried 'make', the 
> 7.2 tarball got deleted).
> But I still get an error in the end with building gcc-7.2.0. I have 
> attached the log (it's huge, ~6MB).
>
> At this point, I don't even understand what the error is... Any 
> suggestions?
>
>
> On Monday, October 16, 2017 at 5:11:15 PM UTC-4, John H Palmieri wrote:
>>
>> You have at least two choices. For both, start by downloading (
>> http://www.sagemath.org/download-source.html) and unpacking 
>> sage-8.0.tar.gz wherever you plan to build it.
>>
>> Choice 1: install git-trac-config: see 
>> http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-command.
>>  
>> (So run "git clone https://github.com/sagemath/git-trac-command.git; in 
>> some suitable directory, separate from the Sage installation, and then run 
>> "source git-trac-command/enable.sh".
>>
>> Then cd into the Sage-8.0 directory. Run "git trac config". Then run "git 
>> trac checkout 23898". Also download the tarball for gcc-7.2 from that 
>> ticket and put it in sage-8.0/upstream. Then run "make".
>>
>> Choice 2: skip the git business and just make the changes directly: edit 
>> the file "sage-8.0/build/pkgs/gcc/package-version.txt" to say "7.2.0". Also 
>> download a gzipped tarball for gcc-7.2 (for example from 
>> ftp://ftp.fu-berlin.de/unix/languages/gcc/releases/gcc-7.2.0/gcc-7.2.0.tar.gz)
>>  
>> and put it in sage-8.0/upstream. Then run "./sage --package fix-checksum 
>> gcc". Then run "make".
>>
>>
>> On Monday, October 16, 2017 at 1:12:47 PM UTC-7, Ling Lin wrote:
>>>
>>> Hi,
>>>
>>> I'm having a similar problem, since I have to install Sage on a new 
>>> computer (Macbook Pro 2017 with OS10.13).
>>> I think the issue is again with building gcc-5.4.0, which was mentioned 
>>> in ticket ##23898. Since I'm not familiar with git, I cloned the repository 
>>> for both the master and developer branch and tried to build that. In both 
>>> cases, it still tries to build gcc-5.4.0, which then fails.
>>>
>>> Would it be possible to spell out the fix for dummies?
>>>
>>> Thanks,
>>> Ling
>>>
>>>
>>> On Friday, October 13, 2017 at 3:08:31 AM UTC-4, Arvind Ayyer wrote:
>>>>
>>>> After many hours of compiling (and when it seemed close to completing), 
>>>> it gave an error while installing curl-7.53.1, as John had predicted. The 
>>>> error is funny because this is MacOS 10.13:
>>>>
>>>> [curl-7.53.1] libtool: compile:  clang -DHAVE_CONFIG_H 
>>>>> -I../include/curl -I../include -I../include -I../lib -I../lib 
>>>>> -DBUILDING_LIBCURL -DCURL_HIDDEN_SYMBOLS 
>>>>> -I/Applications/Sage-6.2.app/Contents/Resources/sage/local/include 
>>>>> -fvisibility=hidden -Qunused-arguments -Os -mmacosx-version-min=10.8 
>>>>> -Werror=partial-availability -MT libcurl_la-connect.lo -MD -MP -MF 
>>>>> .deps/libcurl_la-connect.Tpo -c connect.c  -fno-common -DPIC -o 
>>>>> .libs/libcurl_la-connect.o
>>>>> [curl-7.53.1] connect.c:1087:12: error: 'connectx' is only available 
>>>>> on macOS 10.11 or newer [-Werror,-Wunguarded-availability]
>>>>> [curl-7.53.1]   rc = connectx(sockfd, , SAE_ASSOCID_ANY,
>>>>> [curl-7.53.1]^~~~
>>>>> [curl-7.53.1] /usr/include/sys/socket.h:713:5: note: 'connectx' has 
>>>>> been explicitly marked partial here
>>>>> [curl-7.53.1] int connectx(int, const sa_endpoints_t *, sae_associd_t, 
>>>>> unsigned int,
>>>>> [curl-7.53.1] ^
>>>>> [curl-7.53.1] connect.c:1087:12: note: enclose 'connectx' in a 
>>>>> __builtin_available check to silence this warning
>>>>> [curl-7.53.1]   rc = connectx(sockfd, , SAE_ASSOCID_ANY,
>>>>> [curl-7.53.1]^~~~
>>>>> [curl-7.53.1] 1 error generated.
>>>>>
>>>>
>>>>
>>>> What's the quickest way out now? If I download curl-7.56.0 in the 
>>>> upstream directory and rerun "SAGE_INSTALL_GCC=yes make ptestlong", will 
>>>> it 
>>>> delete all the existing builds?
>>>>
>>>> Thanks,
>>>> Arvind
>>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

[John H Palmieri]

You have at least two choices. For both, start by downloading 
(http://www.sagemath.org/download-source.html) and unpacking 
sage-8.0.tar.gz wherever you plan to build it.

Choice 1: install git-trac-config: see 
http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-command.
 
(So run "git clone https://github.com/sagemath/git-trac-command.git; in 
some suitable directory, separate from the Sage installation, and then run 
"source git-trac-command/enable.sh".

Then cd into the Sage-8.0 directory. Run "git trac config". Then run "git 
trac checkout 23898". Also download the tarball for gcc-7.2 from that 
ticket and put it in sage-8.0/upstream. Then run "make".

Choice 2: skip the git business and just make the changes directly: edit 
the file "sage-8.0/build/pkgs/gcc/package-version.txt" to say "7.2.0". Also 
download a gzipped tarball for gcc-7.2 (for example from 
ftp://ftp.fu-berlin.de/unix/languages/gcc/releases/gcc-7.2.0/gcc-7.2.0.tar.gz) 
and put it in sage-8.0/upstream. Then run "./sage --package fix-checksum 
gcc". Then run "make".


On Monday, October 16, 2017 at 1:12:47 PM UTC-7, Ling Lin wrote:
>
> Hi,
>
> I'm having a similar problem, since I have to install Sage on a new 
> computer (Macbook Pro 2017 with OS10.13).
> I think the issue is again with building gcc-5.4.0, which was mentioned in 
> ticket ##23898. Since I'm not familiar with git, I cloned the repository 
> for both the master and developer branch and tried to build that. In both 
> cases, it still tries to build gcc-5.4.0, which then fails.
>
> Would it be possible to spell out the fix for dummies?
>
> Thanks,
> Ling
>
>
> On Friday, October 13, 2017 at 3:08:31 AM UTC-4, Arvind Ayyer wrote:
>>
>> After many hours of compiling (and when it seemed close to completing), 
>> it gave an error while installing curl-7.53.1, as John had predicted. The 
>> error is funny because this is MacOS 10.13:
>>
>> [curl-7.53.1] libtool: compile:  clang -DHAVE_CONFIG_H -I../include/curl 
>>> -I../include -I../include -I../lib -I../lib -DBUILDING_LIBCURL 
>>> -DCURL_HIDDEN_SYMBOLS 
>>> -I/Applications/Sage-6.2.app/Contents/Resources/sage/local/include 
>>> -fvisibility=hidden -Qunused-arguments -Os -mmacosx-version-min=10.8 
>>> -Werror=partial-availability -MT libcurl_la-connect.lo -MD -MP -MF 
>>> .deps/libcurl_la-connect.Tpo -c connect.c  -fno-common -DPIC -o 
>>> .libs/libcurl_la-connect.o
>>> [curl-7.53.1] connect.c:1087:12: error: 'connectx' is only available on 
>>> macOS 10.11 or newer [-Werror,-Wunguarded-availability]
>>> [curl-7.53.1]   rc = connectx(sockfd, , SAE_ASSOCID_ANY,
>>> [curl-7.53.1]^~~~
>>> [curl-7.53.1] /usr/include/sys/socket.h:713:5: note: 'connectx' has been 
>>> explicitly marked partial here
>>> [curl-7.53.1] int connectx(int, const sa_endpoints_t *, sae_associd_t, 
>>> unsigned int,
>>> [curl-7.53.1] ^
>>> [curl-7.53.1] connect.c:1087:12: note: enclose 'connectx' in a 
>>> __builtin_available check to silence this warning
>>> [curl-7.53.1]   rc = connectx(sockfd, , SAE_ASSOCID_ANY,
>>> [curl-7.53.1]^~~~
>>> [curl-7.53.1] 1 error generated.
>>>
>>
>>
>> What's the quickest way out now? If I download curl-7.56.0 in the 
>> upstream directory and rerun "SAGE_INSTALL_GCC=yes make ptestlong", will it 
>> delete all the existing builds?
>>
>> Thanks,
>> Arvind
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: python3 status

[John H Palmieri]

That's great! Thank you for all of your work on this.

  John


On Friday, October 13, 2017 at 8:56:11 AM UTC-7, Frédéric Chapoton wrote:
>
> Hello,
>
> I have reached this point with the ugly python3 experimental branch 
> "public/python3-experiment-8.1.b7":
>
>
> ┌┐
> │ SageMath version 8.1.beta7, Release Date: 2017-10-03   │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> sage: 3*3
> 9
> sage: parent(_)
> Integer Ring
>
>
> Cool, no ? Or maybe nobody cares ?
>
> Many things are still not working. The cmp problem has been much reduced, 
> but still not fully fixed. On our way is a large-scale unicode problem, and 
> maybe another large scale hash problem.
>
> Frederic
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [imp] Trouble viewing a specific email in Imp

[John H. Bennett III]

Quoting Jan Schneider <j...@horde.org>:


Zitat von John H. Bennett III <benne...@thebennetthome.com>:


Hello all,

I am having an issue viewing all of the content in a particular  
email.  I sent info offlist, as the email had some personal stuff  
in it, but the email was viewed fine, so I'm asking the larger list  
for any assistance.


The email has some text that is not being displayed in horde, but  
is showing up on my mobile device.  When I go to open the email in  
horde+, I see these errors in my log, which I didn't bother to  
check earlier.


Oct  10 18:52:59 www HORDE: [imp] Error running command:  
/usr/bin/identify -format "%n" /tmp/imgPysnjx Error: /invalidaccess  
in --run-- Operand stack:--dict:9/18(L)--   F2   78.591
--dict:6/6(L)--   --dict:6/6(L)--   ArialNarrow-Italic
--dict:11/12(ro)(G)--   --nostringval--   CIDFontObject
--dict:6/6(L)--   --dict:6/6(L)--   59231   --dict:6/6(L)--
--nostringval--   PDFCIDFontName   ArialNarrow-Italic Execution  
stack:%interp_exit   .runexec2   --nostringval--
--nostringval--   --nostringval--   2   %stopped_push
--nostringval--   --nostringval--   --nostringval--   false   1
%stopped_push   1862   1   3   %oparray_pop   1861   1   3
%oparray_pop   1845   1   3   %oparray_pop   --nostringval--
--nostringval--   2   1   1   --nostringval--
%for_pos_int_continue   --nostringval--   --nostringval--
--nostringval--   --nostringval--   %array_continue
--nostringval--   false   1   %stopped_push   --nostringval--
%loop_continue   --nostringval--   --nostringval--
--nostringval--   --nostringval--   --nostringval--
--nostringval--   %array_continue   --nostringval--
--nostringval--   --nostringval--   --nostringval--
--nostringval-- Dictionary stack:--dict:1154/1684(ro)(G)--
--dict:1/20(G)--   --dict:75/200(L)--   --dict:75/200(L)--
--dict:106/127(ro)(G)--   --dict:286/300(ro)(G)--
--dict:22/25(L)--   --dict:4/6(L)--   --dict:22/40(L)--
--dict:1/1(ro)(G)-- Current allocation mode is local [pid 20530 on  
line 814 of "/usr/share/pear/Horde/Image/Im.php"]


This is probably just from creating an attachment preview. The body  
of the message should still render just fine.


Yes sir, I understand that is should render just fine, but it isn't  
for me using edge, chrome, FF, and that is what I am needing  
assistance with.  Mike showed it did on his system, so I'm hopeful  
that it's simply a matter of me having something misconfigured.  What  
else could I look at?  mime_driver settings are where I plan to start  
next when I'm able to get back to looking into this.




Looking at the headers, I see these content-types

Content-Type: multipart/mixed; boundary="001a114e27f69963c9055ae41f12"

--001a114e27f69963c9055ae41f12
Content-Type: multipart/related; boundary="001a114e27f69963c7055ae41f11"

--001a114e27f69963c7055ae41f11
Content-Type: multipart/alternative; boundary="001a114e27f69963c3055ae41f10"

--001a114e27f69963c3055ae41f10
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


My horde5 installation is up to date. I have this configured in  
horde, conf.php


$conf['image']['convert'] = '/usr/bin/convert';
$conf['image']['identify'] = '/usr/bin/identify';
$conf['image']['driver'] = 'Im';

I'm running a distro based on CentOS 6.

PHP 5.3.3 (cli) (built: Mar 22 2017 12:27:09)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies


I have this installed, ImageMagick-6.7.2.7-6.el6.x86_64

I see on the config page that the pecl version is the preferred on  
to use, but it requires at least php 5.4, and I'm not in a position  
to try to upgrade php on this system.


[root@www RPMS]# pecl install imagick
pecl/imagick requires PHP (version >= 5.4.0), installed version is 5.3.3

I would appreciate any help.

I will try setting this up on CentOS7, and see if the problem  
clears, and if so, then know that I need to get there, so I have  
more current packages installed.


Thank you in advanced,

John




--
Jan Schneider
The Horde Project
https://www.horde.org/

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org


Thank you again,

John

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org

[imp] Trouble viewing a specific email in Imp

[John H. Bennett III]

Hello all,

I am having an issue viewing all of the content in a particular email.  
 I sent info offlist, as the email had some personal stuff in it, but  
the email was viewed fine, so I'm asking the larger list for any  
assistance.


The email has some text that is not being displayed in horde, but is  
showing up on my mobile device.  When I go to open the email in  
horde+, I see these errors in my log, which I didn't bother to check  
earlier.


Oct  10 18:52:59 www HORDE: [imp] Error running command:  
/usr/bin/identify -format "%n" /tmp/imgPysnjx Error: /invalidaccess in  
--run-- Operand stack:--dict:9/18(L)--   F2   78.591
--dict:6/6(L)--   --dict:6/6(L)--   ArialNarrow-Italic
--dict:11/12(ro)(G)--   --nostringval--   CIDFontObject
--dict:6/6(L)--   --dict:6/6(L)--   59231   --dict:6/6(L)--
--nostringval--   PDFCIDFontName   ArialNarrow-Italic Execution stack:  
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
--nostringval--   --nostringval--   false   1   %stopped_push   1862
1   3   %oparray_pop   1861   1   3   %oparray_pop   1845   1   3
%oparray_pop   --nostringval--   --nostringval--   2   1   1
--nostringval--   %for_pos_int_continue   --nostringval--
--nostringval--   --nostringval--   --nostringval--   %array_continue   
 --nostringval--   false   1   %stopped_push   --nostringval--
%loop_continue   --nostringval--   --nostringval--   --nostringval--
--nostringval--   --nostringval--   --nostringval--   %array_continue   
 --nostringval--   --nostringval--   --nostringval--
--nostringval--   --nostringval-- Dictionary stack: 
--dict:1154/1684(ro)(G)--   --dict:1/20(G)--   --dict:75/200(L)--
--dict:75/200(L)--   --dict:106/127(ro)(G)--   --dict:286/300(ro)(G)--  
  --dict:22/25(L)--   --dict:4/6(L)--   --dict:22/40(L)--
--dict:1/1(ro)(G)-- Current allocation mode is local [pid 20530 on  
line 814 of "/usr/share/pear/Horde/Image/Im.php"]



Looking at the headers, I see these content-types

Content-Type: multipart/mixed; boundary="001a114e27f69963c9055ae41f12"

--001a114e27f69963c9055ae41f12
Content-Type: multipart/related; boundary="001a114e27f69963c7055ae41f11"

--001a114e27f69963c7055ae41f11
Content-Type: multipart/alternative; boundary="001a114e27f69963c3055ae41f10"

--001a114e27f69963c3055ae41f10
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


My horde5 installation is up to date. I have this configured in horde,  
conf.php


$conf['image']['convert'] = '/usr/bin/convert';
$conf['image']['identify'] = '/usr/bin/identify';
$conf['image']['driver'] = 'Im';

I'm running a distro based on CentOS 6.

PHP 5.3.3 (cli) (built: Mar 22 2017 12:27:09)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies


I have this installed, ImageMagick-6.7.2.7-6.el6.x86_64

I see on the config page that the pecl version is the preferred on to  
use, but it requires at least php 5.4, and I'm not in a position to  
try to upgrade php on this system.


[root@www RPMS]# pecl install imagick
pecl/imagick requires PHP (version >= 5.4.0), installed version is 5.3.3

I would appreciate any help.

I will try setting this up on CentOS7, and see if the problem clears,  
and if so, then know that I need to get there, so I have more current  
packages installed.


Thank you in advanced,

John



--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

[John H Palmieri]

Also, if you have problems with the curl package, try 
https://trac.sagemath.org/ticket/23991

On Sunday, October 8, 2017 at 10:02:36 AM UTC-7, John H Palmieri wrote:
>
> Are you trying to install Sage 6.2 (as your log seems to indicate)? That 
> is extremely old. Try with a fresh source installation: either 
> http://www.sagemath.org/download-source.html for stable source or 
> http://www.sagemath.org/download-latest.html for the latest development 
> version. Also, do you have the Xcode command-line tools installed? Run 
> "xcode-select -install" from the terminal.
>
> Finally, as Dima says, Sage won't build as is on OS X High Sierra, but the 
> problems should come later in the installation process.
>
>
>
> On Sunday, October 8, 2017 at 4:06:20 AM UTC-7, Arvind Ayyer wrote:
>>
>> Dear all, 
>>
>>
>> I recently upgraded my Mac OS to HighSierra and have installed the latest 
>> version of XCode. Strangely enough, the gcc version is still 4.2.1.
>>
>> I'm trying to install the latest version of sage using my git account 
>> (userid: ayyer) using the guidelines from the TentativeConventions file. 
>>
>>
>> I have a 2013 MacBook Pro Retina 13-inch. The processor is a 2.6 GHz 
>> Intel Core i5. The error has occurred in the very beginning while 
>> installing patch-2.7.5. 
>>
>>
>> I have tried to find out what the error is and it may be related to the 
>> conflict between these lines starting at 281:
>>
>>
>> checking libgen.h usability... yes
>>>  282 checking libgen.h presence... yes
>>>  283 checking for libgen.h... yes
>>>
>>
>> an these lines starting at 1968:
>>
>>
>> checking libgen.h usability... no
>>> checking libgen.h presence... yes
>>> configure: WARNING: libgen.h: present but cannot be compiled
>>> configure: WARNING: libgen.h: check for missing prerequisite headers?
>>> configure: WARNING: libgen.h: see the Autoconf documentation
>>> configure: WARNING: libgen.h: section "Present But Cannot Be 
>>> Compiled"
>>> configure: WARNING: libgen.h: proceeding with the compiler's result
>>> configure: WARNING: ##  ##
>>> configure: WARNING: ## Report this to bug-...@gnu.org ##
>>> configure: WARNING: ##  ##
>>> checking for libgen.h... no
>>>
>>>
>> As per the instructions generating the error message, I'm emailing you 
>> the log file. 
>>
>>
>> Please let my know if you need any more information from me. 
>>
>>
>> Thanks a lot for your time and help.
>>
>> Regards,
>> Arvind
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Problem installing sage on High Sierra (Mac OS 10.13)

[John H Palmieri]

Are you trying to install Sage 6.2 (as your log seems to indicate)? That is 
extremely old. Try with a fresh source installation: either 
http://www.sagemath.org/download-source.html for stable source or 
http://www.sagemath.org/download-latest.html for the latest development 
version. Also, do you have the Xcode command-line tools installed? Run 
"xcode-select -install" from the terminal.

Finally, as Dima says, Sage won't build as is on OS X High Sierra, but the 
problems should come later in the installation process.



On Sunday, October 8, 2017 at 4:06:20 AM UTC-7, Arvind Ayyer wrote:
>
> Dear all, 
>
>
> I recently upgraded my Mac OS to HighSierra and have installed the latest 
> version of XCode. Strangely enough, the gcc version is still 4.2.1.
>
> I'm trying to install the latest version of sage using my git account 
> (userid: ayyer) using the guidelines from the TentativeConventions file. 
>
>
> I have a 2013 MacBook Pro Retina 13-inch. The processor is a 2.6 GHz 
> Intel Core i5. The error has occurred in the very beginning while 
> installing patch-2.7.5. 
>
>
> I have tried to find out what the error is and it may be related to the 
> conflict between these lines starting at 281:
>
>
> checking libgen.h usability... yes
>>  282 checking libgen.h presence... yes
>>  283 checking for libgen.h... yes
>>
>
> an these lines starting at 1968:
>
>
> checking libgen.h usability... no
>> checking libgen.h presence... yes
>> configure: WARNING: libgen.h: present but cannot be compiled
>> configure: WARNING: libgen.h: check for missing prerequisite headers?
>> configure: WARNING: libgen.h: see the Autoconf documentation
>> configure: WARNING: libgen.h: section "Present But Cannot Be Compiled"
>> configure: WARNING: libgen.h: proceeding with the compiler's result
>> configure: WARNING: ##  ##
>> configure: WARNING: ## Report this to bug-...@gnu.org  
>> ##
>> configure: WARNING: ##  ##
>> checking for libgen.h... no
>>
>>
> As per the instructions generating the error message, I'm emailing you the 
> log file. 
>
>
> Please let my know if you need any more information from me. 
>
>
> Thanks a lot for your time and help.
>
> Regards,
> Arvind
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[Elecraft] KX3 SSB ALC Mic Gain - a new problem

[John H Farmer]

Dear Don & Group,

Thanks for your suggestions.  After some more exploration, I think the problem 
is the MH3 and here's why:

Backing down the mic gain didn't help and neither did a firmware reload.  I was 
suspicious of the MH3 being at fault, as the ALC / Mic gain adjustment remained 
perfectly consistent and reliable in data modes.
I then remembered I had a Yamaha CM500 headset lying in a drawer. I made an 
adapter (thanks Walter, K6WRU for your very helpful and clear webpage 
describing the adapter cable) I plugged it into the KX3 mic socket and lo and 
behold, the KX3 plays perfectly with it - the ALC shows 5-7 bars with a mic 
gain of 35-37 and I get the expected RF output, which is exactly how it used to 
be with the MH3.

I took the MH3 apart and mechanically it all looks sound, no loose wires or dry 
joints, and I checked that there is indeed a bias voltage on the mic + ( tip) 
wire at the microphone.  There's not much to go wrong in there, so I wonder if 
the electret element has died.

I'll order a replacement MH3, because even though the CM500 headset works well, 
I like using the handmic and I've always had good audio reports using it.  

Thanks everyone for your interest.

73,

John
VK7JB

-Original Message-
From: Don Wilhelm [mailto:donw...@embarqmail.com] 
Sent: Sunday, 8 October 2017 11:09
To: Dr John H Farmer <opensile...@bigpond.com>; elecraft@mailman.qth.net
Subject: Re: [Elecraft] KX3 SSB ALC Mic Gain - a new problem

John,

Try backing down the MIC Gain setting to something low or mid-range.
If you get the mic voltage too high, the mic amplifier detects that and inserts 
attenuation that will shut the audio from the mic down.

So bottom line, start with a low MIC Gain setting and increase it until you see 
5 to 7 bars on the ALC meter.

73,
Don W3FPR

On 10/7/2017 7:53 PM, Dr John H Farmer wrote:

> Yesterday, I noted that I had no RF output on SSB and find that now I 
> get no ALC indication until the Mic gain is advanced to the maximum setting 
> of 80.
> Nothing else has changed in my
> 
> setup.  I've checked that MIC Bias is set to ON and the TX EQ settings 
> have not changed.  I've also checked and there is indeed a bias 
> voltage on the Mic socket.

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

[Elecraft] KX3 SSB ALC Mic Gain - a new problem

[Dr John H Farmer]

Hi All,

 

Apologies if this question posts twice - my attempt yesterday was
unsuccessful, so here goes again.

 

I've been running KX3 #2511 for several years on SSB with the MH3 mic and
with settings:  Mic gain 35 and compression 12.  It's worked flawlessly and
that combination of settings has

given me an ALC indication of 5 bars while speaking normally.  I'm running
the latest firmware.

 

Yesterday, I noted that I had no RF output on SSB and find that now I get no
ALC indication until the Mic gain is advanced to the maximum setting of 80.
Nothing else has changed in my

setup.  I've checked that MIC Bias is set to ON and the TX EQ settings have
not changed.  I've also checked and there is indeed a bias voltage on the
Mic socket.

 

I can still run digital modes in DATA mode A,  using an external soundcard
connected to the KX3 mic socket via an adapter cable and I easily get 4 bars
of ALC with the 5th flickering with a Mic gain of 35.  That hasn't changed.

 

I don't have another MH3 mic to check whether it's the microphone that's at
fault here, but that's my suspicion.

 

Any ideas where to look next? 

 

Many thanks, 

 

John

VK7JB

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

[sage-devel] Request reviewers for trac 23898, update our version of GCC

[John H Palmieri]

At https://trac.sagemath.org/ticket/23898, I propose updating to GCC 7.2.0. 
This seems to fix the problem with building Sage with Apple's latest 
version of Xcode (there is also separate work going to let Sage build with 
clang with the latest Xcode: #12426 and #23922).

I have tested this on a few different OS X machines, but we need people to 
test it on other platforms. So please help out!

Thanks,
  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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage / gcc build failed on macOS High Sierra

[John H Palmieri]

The problem with gcc has been reported here: 
https://trac.sagemath.org/ticket/23898. No one seems to have made any 
progress on it. In the meantime, I've been able to build Sage using 
https://trac.sagemath.org/ticket/12426 and 
https://trac.sagemath.org/ticket/23922. (In my case this is with Xcode 9, 
the new one, but not on High Sierra. It's usually Xcode causing the 
problems, not the version of the OS, but caveat emptor.)



On Tuesday, October 3, 2017 at 12:40:19 PM UTC-7, nbl...@uic.edu wrote:
>
> Not sure what info is useful here; I've attached the log file, but below 
> is what seems most relevant to my untrained eye.
>
>
> I'm (optimistically?) running a fresh copy of High Sierra, with 
> command-line tools and Xcode both installed. Any help is greatly 
> appreciated! Headed for a Sage coding sprint in a few weeks so I'd like to 
> have this working. Thanks!
>
>
> .
>
> [gcc-5.4.0] 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2:
>  
> error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean 
> simply 'fancy_abort'?
>
> [gcc-5.4.0] _VSTD::abort();
>
> [gcc-5.4.0] ^~~
>
> 
>
> [gcc-5.4.0] 13 warnings and 1 error generated.
>
> [gcc-5.4.0] make[6]: *** [auto-profile.o] Error 1
>
> [gcc-5.4.0] make[5]: *** [all-stage1-gcc] Error 2
>
> [gcc-5.4.0] make[4]: *** [stage1-bubble] Error 2
>
> [gcc-5.4.0] make[3]: *** [all] Error 2
>
> [gcc-5.4.0] 
>
> [gcc-5.4.0] real 15m53.799s
>
> [gcc-5.4.0] user 5m38.933s
>
> [gcc-5.4.0] sys 10m3.973s
>
> [gcc-5.4.0] 
> 
>
> [gcc-5.4.0] Error installing package gcc-5.4.0
>
> ...
>
> make[2]: *** 
> [/Users/nathanbliss/sage/local/var/lib/sage/installed/gcc-5.4.0] Error 1
>
> make[1]: *** [all-toolchain] Error 2
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: doctesting tab completion

[John H Palmieri]

Is there a typo? Should the line causing the crash start with "from"? (Same 
question on the trac ticket.)


On Wednesday, September 27, 2017 at 8:55:16 PM UTC-7, Dima Pasechnik wrote:
>
> How does one write a doctest for tab completion on the command line?
> I don't care for the output, I just need to check there is no crash, as in 
> https://trac.sagemath.org/ticket/23700#comment:11
>
> sage: from sage.libs.ecl import *
> sage: sage.interfaces.maxima_lib import 
>
>
> causes a segfault in ECL for me.
>
> Thanks
> Dima
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] let's make FriCAS optional

[John H Palmieri]

On Wednesday, September 27, 2017 at 10:40:36 AM UTC-7, Jeroen Demeyer wrote:
>
> On 2017-09-27 16:10, Vincent Delecroix wrote: 
> > Not sufficient: the package has to be useful for Sage and used in 
> > Sage... emacs is unlikely to become an optional package even if it 
> > satisfies the above conditions. 
>
> That's why I added "as opposed to experimental" :-) 
>
> emacs shouldn't be experimental either. 
>

Indeed, it should be mandatory.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Is trac down?

[John H Palmieri]

On Tuesday, September 26, 2017 at 1:56:39 PM UTC-7, mforets wrote:
>
>
>
> El martes, 26 de septiembre de 2017, 22:38:23 (UTC+2), Samuel Lelievre 
> escribió:
>>
>> Tue2017-09-26 10:29:17 UTC, Maarten Derickx:
>> > Seems to be back up again.
>>
>> Not sure if it's related but when I click on the branch at
>> https://trac.sagemath.org/ticket/21944
>> I get the following error:
>>
>> Internal Server Error
>>
>> The server encountered an internal error or misconfiguration
>> and was unable to complete your request.
>>
>> Please contact the server administrator at [no address given]
>> to inform them of the time this error occurred, and the actions
>> you performed just before this error.
>>
>> More information about this error may be available in the server error 
>> log.
>>
>> Apache/2.4.7 (Ubuntu) Server at git.sagemath.org Port 443
>>
>
> same error here. i pulled this branch some days ago, and it was working.
>
>
>
That seems to be specific to that ticket: branches on other tickets seem to 
be working.

  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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Consider not upgrading to Xcode 9.0

[John H Palmieri]

Trying to build gfortran yields the same error as reported at 
https://trac.sagemath.org/ticket/23898.

  John


On Wednesday, September 20, 2017 at 3:08:05 PM UTC-7, John H Palmieri wrote:
>
> I successfully built with the current version (not the updated one) of 
> eclib plus the patch you mentioned. I will also try to see if gfortran 
> builds.
>
> On Wednesday, September 20, 2017 at 2:56:59 PM UTC-7, François Bissey 
> wrote:
>>
>> So I have a build of sage 8.1.beta5 on OS X with Xcode 9 using 
>>
>> * #12426 - building with clang - you need autotools installed or generate 
>> configure 
>> somewhere that does and copy it in place. 
>>
>> * an external fortran compiler, given the problems with gcc it may 
>> very well be that gfortran won’t build either - I need to further check 
>> that. 
>>
>> * an updated eclib 
>> https://github.com/JohnCremona/eclib/archive/v20170815.tar.gz 
>> probably not necessary but defaulting to C++11 make logs much nicer since 
>> it cuts down on the warnings. Beware this is not a sdist tarball. 
>>
>> * the patch at 
>> https://github.com/JohnCremona/eclib/issues/19#issuecomment-314952542 
>> this is absolutely needed. 
>>
>> François 
>>
>> > On 21/09/2017, at 07:10, François Bissey <frp.b...@gmail.com> wrote: 
>> > 
>> > We in fact have a patch on github for a similar problem that was 
>> spotted 
>> > before. It proved effective in this instance. So I will proceed with 
>> trying 
>> > to build the rest of sage. 
>> > 
>> > François 
>> > 
>> >> On 21/09/2017, at 04:05, John H Palmieri <jhpalm...@gmail.com> wrote: 
>> >> 
>> >> I put the log for that failure at #12426, and then François created an 
>> upstream ticket at 
>> >> 
>> >>   https://github.com/JohnCremona/eclib/issues/28 
>> >> 
>> >> in case you want to take a look. 
>> >> 
>> >> 
>> >> On Wednesday, September 20, 2017 at 3:08:13 AM UTC-7, Dima Pasechnik 
>> wrote: 
>> >> The eclib does not look like a big problem, some rather standard C++ 
>> template issue to be tweaked... 
>> >> 
>> >> On Wednesday, September 20, 2017 at 12:50:32 AM UTC+1, John H Palmieri 
>> wrote: 
>> >> I just upgraded an OS X box to Xcode 9.0, and now Sage doesn't build: 
>> >> 
>> >> - with a fresh Sage 8.1.beta5 tarball, gcc doesn't build: 
>> >> 
>> >> 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2:
>>  
>> error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean 
>> simply 'fancy_abort'? 
>> >>_VSTD::abort(); 
>> >>^~~ 
>> >> 
>> >> I'll open a ticket and post the full gcc log. 
>> >> 
>> >> - instead using trac 12426 (compile with clang instead of gcc), eclib 
>> doesn't build: 
>> >> 
>> >> 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:572:12:
>>  
>> error: call to function 'isnan' that is neither visible in the template 
>> definition nor found by argument-dependent lookup 
>> >>return isnan(__lcpp_x); 
>> >> 
>> >>  
>> >> 
>> >> 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:592:12:
>>  
>> error: call to function 'isinf' that is neither visible in the template 
>> definition nor found by argument-dependent lookup 
>> >>return isinf(__lcpp_x); 
>> >> 
>> >> -- 
>> >> 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+...@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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Consider not upgrading to Xcode 9.0

[John H Palmieri]

I successfully built with the current version (not the updated one) of 
eclib plus the patch you mentioned. I will also try to see if gfortran 
builds.

On Wednesday, September 20, 2017 at 2:56:59 PM UTC-7, François Bissey wrote:
>
> So I have a build of sage 8.1.beta5 on OS X with Xcode 9 using 
>
> * #12426 - building with clang - you need autotools installed or generate 
> configure 
> somewhere that does and copy it in place. 
>
> * an external fortran compiler, given the problems with gcc it may 
> very well be that gfortran won’t build either - I need to further check 
> that. 
>
> * an updated eclib 
> https://github.com/JohnCremona/eclib/archive/v20170815.tar.gz 
> probably not necessary but defaulting to C++11 make logs much nicer since 
> it cuts down on the warnings. Beware this is not a sdist tarball. 
>
> * the patch at 
> https://github.com/JohnCremona/eclib/issues/19#issuecomment-314952542 
> this is absolutely needed. 
>
> François 
>
> > On 21/09/2017, at 07:10, François Bissey <frp.b...@gmail.com 
> > wrote: 
> > 
> > We in fact have a patch on github for a similar problem that was spotted 
> > before. It proved effective in this instance. So I will proceed with 
> trying 
> > to build the rest of sage. 
> > 
> > François 
> > 
> >> On 21/09/2017, at 04:05, John H Palmieri <jhpalm...@gmail.com 
> > wrote: 
> >> 
> >> I put the log for that failure at #12426, and then François created an 
> upstream ticket at 
> >> 
> >>   https://github.com/JohnCremona/eclib/issues/28 
> >> 
> >> in case you want to take a look. 
> >> 
> >> 
> >> On Wednesday, September 20, 2017 at 3:08:13 AM UTC-7, Dima Pasechnik 
> wrote: 
> >> The eclib does not look like a big problem, some rather standard C++ 
> template issue to be tweaked... 
> >> 
> >> On Wednesday, September 20, 2017 at 12:50:32 AM UTC+1, John H Palmieri 
> wrote: 
> >> I just upgraded an OS X box to Xcode 9.0, and now Sage doesn't build: 
> >> 
> >> - with a fresh Sage 8.1.beta5 tarball, gcc doesn't build: 
> >> 
> >> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2:
>  
> error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean 
> simply 'fancy_abort'? 
> >>_VSTD::abort(); 
> >>^~~ 
> >> 
> >> I'll open a ticket and post the full gcc log. 
> >> 
> >> - instead using trac 12426 (compile with clang instead of gcc), eclib 
> doesn't build: 
> >> 
> >> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:572:12:
>  
> error: call to function 'isnan' that is neither visible in the template 
> definition nor found by argument-dependent lookup 
> >>return isnan(__lcpp_x); 
> >> 
> >>  
> >> 
> >> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:592:12:
>  
> error: call to function 'isinf' that is neither visible in the template 
> definition nor found by argument-dependent lookup 
> >>return isinf(__lcpp_x); 
> >> 
> >> -- 
> >> 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+...@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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Consider not upgrading to Xcode 9.0

[John H Palmieri]

I put the log for that failure at #12426, and then François created an 
upstream ticket at

   https://github.com/JohnCremona/eclib/issues/28

in case you want to take a look.


On Wednesday, September 20, 2017 at 3:08:13 AM UTC-7, Dima Pasechnik wrote:
>
> The eclib does not look like a big problem, some rather standard C++ 
> template issue to be tweaked...
>
> On Wednesday, September 20, 2017 at 12:50:32 AM UTC+1, John H Palmieri 
> wrote:
>>
>> I just upgraded an OS X box to Xcode 9.0, and now Sage doesn't build:
>>
>> - with a fresh Sage 8.1.beta5 tarball, gcc doesn't build:
>>
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2:
>>  
>> error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean 
>> simply 'fancy_abort'?
>> _VSTD::abort();
>> ^~~
>>
>> I'll open a ticket and post the full gcc log.
>>
>> - instead using trac 12426 (compile with clang instead of gcc), eclib 
>> doesn't build:
>>
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:572:12:
>>  
>> error: call to function 'isnan' that is neither visible in the template 
>> definition nor found by argument-dependent lookup
>> return isnan(__lcpp_x);
>>
>> 
>>
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:592:12:
>>  
>> error: call to function 'isinf' that is neither visible in the template 
>> definition nor found by argument-dependent lookup
>> return isinf(__lcpp_x);
>>
>> -- 
>> 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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Consider not upgrading to Xcode 9.0

[John H Palmieri]

I just upgraded an OS X box to Xcode 9.0, and now Sage doesn't build:

- with a fresh Sage 8.1.beta5 tarball, gcc doesn't build:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2:
 
error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean 
simply 'fancy_abort'?
_VSTD::abort();
^~~

I'll open a ticket and post the full gcc log.

- instead using trac 12426 (compile with clang instead of gcc), eclib 
doesn't build:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:572:12:
 
error: call to function 'isnan' that is neither visible in the template 
definition nor found by argument-dependent lookup
return isnan(__lcpp_x);



/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath:592:12:
 
error: call to function 'isinf' that is neither visible in the template 
definition nor found by argument-dependent lookup
return isinf(__lcpp_x);

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Signs and graded algebras

[John H Palmieri]

I have a graded algebra A over a field k, and I would like the following 
behavior: when I multiply homogeneous elements of the tensor square (A 
tensor A), I want signs to appear, as in:

  (a tensor b) (c tensor d) = (-1)^(deg b deg c) (ac tensor bd)

You could ask for the same when multiplying elements of (A tensor B) for 
two graded algebras A and B. This may not be desirable for all graded 
algebras in Sage, but it might be useful in more than one case. How should 
this be implemented?

I'm guessing and/or hoping that modifying something in the category code 
would help, and that one could appropriately initialize the categories of A 
and B to turn this feature on, but I'm confused enough by the category code 
that I don't know where to start. Any suggestions? (Or is the category 
approach not viable, so something else (and what?) should be done?)

To illustrate my confusion, if A is the mod 3 Steenrod algebra and if y is 
an element in (A tensor A), I don't even know how the multiplication y*y is 
defined. Is this category code, coercion, something else? Note that this 
example leads to a bug:

sage: A = SteenrodAlgebra(3)
sage: x = A.Q(0)
sage: x**2
0

sage: y = x.coproduct()
sage: y**2
2*Q_0 # Q_0

The coproduct is an algebra map, so if x**2=0, then (x.coproduct())**2 
should also be zero, but it's not. If the signs were dealt with 
appropriately, this would be okay, but as it is, we have a bug.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Free for pick up - West Chester, Ohio (Cincinnati area) - DEC/Compaq/HP

[John H. Reinhardt via cctalk]

I'm moving from SW Ohio to the Dallas - Fort Worth area.  I have a storage unit 
and basement full of stuff I can't take and I'm looking for someone that wants 
it.  Hopefully in one big load but if I have to I will piece it out.  There are 
two deadlines - one is impossibly close.  I'm leaving town Friday, so if there 
is ANYBODY that can be here and load things from my basement or the storage 
unit 3 miles away by late Thursday, Sept 21st then I want to hear from you.  
Otherwise anything I don't take will probably be in the storage unit and 
available until late October.  But that will be the hard deadline. After that 
it goes to a scrapper.

An incomplete list of items follows.  There are other spares and miscellaneous 
items that are way too many to list.


▪   (2) 42u AlphaServer racks.  36” deep with front and rear doors.
▪   DEC RAID Array R7000/R8000 4x6 storage array.  Currently it has 
in it two HSG80 storage controllers and is set up for 1GB FC access.  I have 2 
or 3 HSZ70 controller cards that came in it originally and they worked at the 
time of removal.  However, I'd been told that there is a NVRAM battery on board 
them that if it dies, the controller dies and can't be restored.  Since they 
have been in storage for about 7 years I'd say they were toast (assuming what 
I'd been told was correct).  It has a range of drives in it from 9.1Gb to 18.2 
or maybe 36GB.  Some of my DEC brick drives had died so I opened them up and 
replaced them with Seagate drives of larger capacity.  I have a few extra empty 
containers as well as some extra power supplies.
▪   HP EVA3000 - in pieces - No management workstation.
⁃   (2) HSV110 Controller
⁃   (2) FC-AL hubs
⁃   (3) MSA 5314 Fibre storage shelves
⁃   (x) 36GB Fibre drives
⁃   (x) bus cables, hubs, misc parts.
▪   HP MSA1500cs - 4 SCSI modules, 2 FC modules
▪   HP MSA1500cs - Unknown configuration - probably 1 SCSI module, 
1 FC module
▪   HP MSA20 w/12 750GB LFF drives
▪   (3) Compaq 4314 SCSI Dual bus storage shells with 18GB and 36GB 
drives
▪   (2) HP DL380 G3 Dual Xeon 2.4Ghz, 4GB RAM, SA6400 RAID, 2GB FC, 
6x36GB SCSI disk
▪   HP DL380 G3 Dual Xeon 2.8Ghz, 4GB RAM, SA6400 RAID, 2GB FC, 
6x36GB SCSI disk
▪   (2) HP DL360 G3 1-4GB memory, 2 SCSI drives 9.1GB or 18.2GB
▪   (2) HP DL360 G1 1-4GB memory, 2 SCSI drives 9.1GB or 18.2GB
▪   (2) DEC AlphaServer 800's.  500MHz CPU, I think they have 2GB 
of memory each and a couple 9GB hard drives in the disk slots.  Each has at 
least one SCSI card and a 1GB FC card. I think they have a DEC DE500 or a 
Compaq NC31xx series 100Meg network card.
▪   (1) DEC AlphaServer 1200 and (1) DEC Digital Server 5305 Each of these 
has two 500MHz CPUs and also 2GB of memory.  They each have several of the DEC 
StorageWorks disk "bricks" and at least 2 SCSI cards and a 1GB FC card.  They 
also have a DEC DE500 or a Compaq NC31xx series 100Meg network card.  The “white box” 
5305 has NVRAM modified to run OpenVMS
▪   DEC Alphastation 255 that won't boot due to a hardware fault.  
Might be memory but I never looked into it.  IIRC, memory for that system was 
tough to come by.
▪   DEC/Compaq PWS533 that hasn't been run in a while.  
Configuration unknown.
▪   HP ZX2000 is a 1.4GHz system, faster than most out there.  Has 
1GB of memory and I have 2GB here that I never got around to installing.  It's 
got two 250GB IDE drives, 1 IDE CDRom and a Plexor PX-716a SCSI cd burner.  
Currently it's got Windows 2000 server (IA64 version) on it. Theoretically 
OpenVMS can be installed but you need a SCSI card/drives.  I think I bought a 
compatible SCSI card but I never got around to installing it.
▪   HP ZX6000 is either a dual 1.3GHz or 1.4GHz system.  Memory is 
unknown but I've got enough around here to put up to 6GB in it.
▪   (2) HP RX2600 dual 1.4GHz CPU systems.  Each has at least 4GB 
of memory, 3x36GB SCSI drives, DVD Optical Drive, 2GB FC card and a management 
processor card.
▪   Compaq TL891 tape library with two TK89 DLT drives.  Was in 
working condition 8 years ago when replaced with
▪   Compaq SSL2020 library with 2 Sony AIT-2 drives  50/100GB 
capacity tapes.  Also was in working condition when it was replaced with
▪   Compaq SSL2020 library with 2 Sony AIT-2 drives  50/100GB 
capacity tapes.  About 50 nearly new tape cartridges available. Also was in 
working condition when it was replaced with
▪   Compaq MSL5026 with (2) SDLT 1  160/320GB drives.  Drives are 
SCSI. Has NSR1200 FC interface card in library also in working condition when 
replaced with a MSL2024 LTO library.
▪   Several Compaq/HP SAN switches.  1 really old Compaq 1GB 

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

[John H Palmieri]

By the way, if the problem can be reduced to building the documentation 
(that is, if "make build" succeeds but "make" does not), another option 
would be to try "make doc-html-no-plot", or essentially equivalently do 

export SAGE_DOCBUILD_OPTS+=' --no-plot'
make

It is possible that the plots in the documentation are causing some of the 
problems.

   John


On Saturday, September 16, 2017 at 6:21:54 PM UTC-7, Samuel Lelievre wrote:
>
> Miguel Angel,
>
> Let me try and summarize the discussion so far and some options.
>
> The failure:
>
> - error while running 'make' on a CentOS machine with 2 GB of RAM
> - occurred while building Sage's documentation, which is heavy on RAM
> - likely an out of memory error; not surprising with only 2 GB of RAM
>
> Various suggestions for fixing that:
>
> 1.  add RAM
>
> 2.  build Sage without the documentation
>
>   - for that, run 'make build' instead of 'make'
>
>   - gets you a fully functional Sage, just no HTML documentation
> (the HTML documentation is available online anyway)
>
>   - you could build (the same version of) Sage on another machine
> (possibly with a different OS) and copy over the doc folder
>
> 3.  build Sage on other machine with same system but more RAM, then
>   copy Sage installation over; need same path to Sage on both sides
>
> 4.  use binary-pkg to build a binary on other machine with same system
>   and more RAM; then install on original machine from that binary
>
> 5.  change OS
>
> Comments about each option
>
> 1.  you said it is not an option in your case
> 2.  you said 'make build' failed in your case
> 3.  not suggested so far, you may want to try
> 4.  you said that did not work
> 5.  you said you were considering it
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [Simh] Terminal Emulation for SIMH?

[John H. Reinhardt]

On 9/12/2017 2:41 PM, Zane Healy wrote:

What terminal emulators are currently available for Mac OS X that support VT 
emulation, specifically the emulation of the keypad?  I previously used a 
script to reconfigure an X-Term, but I seem to recall the functionality in 
xterm was dropped.

Zane


I use ZOC V7 from EmTec.  Not free, $79.99 but has been worth it. I bought it 
on V6 and V7 upgrade was free.  Currently any V7.xx update will be free, 
updates are not timed to a year but version.  I'm guessing I'll have to pay for 
V8 whenever it comes (no plans for it that I know of yet).  I've been using ZOC 
for 2-3 years now since I switched from iTerm/iTerm2.  It has semi programmable 
keyboard layouts similar to PowerTerm.  It doesn't handle LAT, but has Telnet, 
SSH, and serial ports.  It can also send commands via rlogin, rsh.  It has a 
macro language based on REXX.  It handles file transfers via SCP, Zmodem, 
Xmodem, Ymodem, Kermit protocols

I've corresponded with the creator. He's friendly and responds quickly.  He 
actually develops it on OS X and ports a copy to Windows so the Mac isn't an 
afterthought like some products.

<https://www.emtec.com/zoc/index.html>  It has a 30 day trial.

--
John H. Reinhardt

.
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

[sage-support] Re: Problem with upgrade on OS X

[John H Palmieri]

Sage will build its own gcc, so as long as you have some functioning 
version of gcc, you shouldn't need to worry about upgrading that. Just try 
installing a new version of Sage (from scratch, not by upgrading 6.7) and 
see what happens.

  John


On Thursday, September 7, 2017 at 8:56:03 AM UTC-7, Arvind Ayyer wrote:
>
> Thanks a lot, Dima! I managed to downgrade to 6.7 successfully for now. 
> Once I upgrade my gcc, I'll go for the latest version.
>
> Regards,
> Arvind
>
> On Wednesday, 6 September 2017 18:14:04 UTC+4, Dima Pasechnik wrote:
>>
>>
>>
>> On Wednesday, September 6, 2017 at 2:27:55 PM UTC+1, Arvind Ayyer wrote:
>>>
>>>
>>> Dear developers, 
>>>
>>>
>>> I'm trying to upgrade from 6.7 to the current version using my git 
>>> account (userid: ayyer) using the guidelines from the TentativeConventions 
>>> file. 
>>>
>>>
>>> I have a 2013 MacBook Pro Retina 13-inch with OS X  (version 10.8.5). The 
>>> processor is a 2.6 GHz Intel Core i5. I had managed to get Sage 6.7 
>>> running with a lot of help from Karl-Dieter Crisman (installing Xcode, 
>>> figuring out various funny errors, etc!).
>>>
>>>
>>> The error occurred while installing openblas-0.2.19.p0. As per the 
>>> instructions generating the error message, I'm emailing you the log file 
>>> and the crash report file.
>>>
>>
>> You are using an old version of gcc; the current Sage's gcc is version 
>> 5.4.
>> (that was the one in 6.7, I guess).
>>
>> It might be much better to build a new Sage version from source; 
>> upgrading from such an old version
>> won't give you any time saving, as you'd have to rebuild basically all of 
>> Sage anyway.
>>  
>>
>>>
>>> Please let my know if you need any more information from me. If this is 
>>> too much trouble, could you tell me if there is an easy way to get back to 
>>> version 6.7 instead? 
>>>
>> if you are on the git tree, you might be able check out the right branch 
>> and rebuild.
>>  
>>
>>>
>>> Thanks a lot for your time and help.
>>>
>>>
>>> Regards,
>>> Arvind
>>>
>>> PS: arv...@iisc.ac.in is my new email address. Please update your 
>>> addressbook. 
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Does anyone use SAGE64?

[John H Palmieri]

On Saturday, September 2, 2017 at 11:54:00 AM UTC-7, Dr. David Kirkby 
(Kirkby Microwave Ltd) wrote:
>
> On 2 September 2017 at 01:41, John H Palmieri <jhpalm...@gmail.com 
> > wrote:
>
>>
>>
>> Hi Dave,
>>
>> Can you clarify? You say that the are necessary on Solaris, but is that 
>> recent information? It is possible that newer versions of Sage and/or 
>> Solaris might make SAGE64 unnecessary.
>>
>> Regards,
>>   John
>>
>
> Hi John, 
>
> https://docs.oracle.com/cd/E18659_01/html/821-1384/gexcx.html
>
> says that the -m64 flag would be needed to create a 64-bit executable. It 
> also says -m32 it required to create 32-bit executable. It is not too clear 
> on the default, but I rather suspect it is still 32-bit. The latest version 
> is Solaris 11.3. I'm running Solaris 11, but not 11.3. 
>

I don't know if Sage works on Solaris right now, but if it does, does it 
build gcc (as it does on OS X), or does it use a preexisting compiler?
 

>
> I believe SAGE64 does more than just add the -m64 flag in a couple of 
> places, so I would propose it is not removed, as it would effectively kit 
> any attempt to build a 64-bit Solaris version of Sage. 
>

I think it mainly adds -m64, but this is not hard to investigate. 

  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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Does anyone use SAGE64?

[John H Palmieri]

On Friday, September 1, 2017 at 3:47:28 PM UTC-7, Dr. David Kirkby (Kirkby 
Microwave Ltd) wrote:
>
>
> On 1 Sep 2017 23:21, "John H Palmieri" <jhpalm...@gmail.com > 
> wrote:
> >
> > Does anyone use the environment variables SAGE64 of CFLAG64? At 
> https://trac.sagemath.org/ticket/23733, it is suggested that they be 
> deprecated and then removed. Any comments?
> >
> > -- 
> > John
>
> They are necessary if one attempts to build a 64 bit version on Solaris. I 
> think they might be used on some versions of OSX too, but I am not sure 
> about that. 
>
> I would say that they should not be removed.  
>
> I never managed to get a reliable 64 bit version on Solaris, but at one 
> point the 32-bit version passed all the doctests. 
>

Hi Dave,

Can you clarify? You say that the are necessary on Solaris, but is that 
recent information? It is possible that newer versions of Sage and/or 
Solaris might make SAGE64 unnecessary.

Regards,
  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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Does anyone use SAGE64?

[John H Palmieri]

Does anyone use the environment variables SAGE64 of CFLAG64? At 
https://trac.sagemath.org/ticket/23733, it is suggested that they be 
deprecated and then removed. Any comments?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: LA-180 ? On Craigslist near Duluth MI

[John H. Reinhardt via cctalk]

On 8/26/2017 7:39 PM, Warner Losh via cctalk wrote:

On Sat, Aug 26, 2017 at 4:50 PM, John H. Reinhardt via cctalk <
cctalk@classiccmp.org> wrote:


On 8/26/2017 4:02 PM, Pete Lancashire via cctalk wrote:


https://eauclaire.craigslist.org/atq/d/aa-occasional-sales/6
248628617.html

Picture #8 in rear right corner



And #11.  It's got a keyboard and number pad so I'm thinking it's more
likely a LA120 DECwriter III



Could easily be a DECwrite II as well. It looks just like the one I used in
high school and college. Can't tell from the picture though if it has the
baud rate selection switches on the left hand side which is a dead-giveaway
for it.

Warner



Picture #8 clearly shows (if you click on it it expands to a larger size) no keypad on the left of the 
keyboard which is how the LA36/DECwriter II set baud rate and did line and form feeds.  The DECwriter III had 
a "Setup" key above the "Escape" and "1" keys to set baud and other 
characteristics and LF, FF and other keys above the number row on the right side for forms handling.  At 
least that's how my LA120 keyboard is set up.

It's hard to see if those keys are there in picture #8 or #11, but since the 
left keypad is missing, I'm going to assume they are.

John H. Reinhardt

Re: LA-180 ? On Craigslist near Duluth MI

[John H. Reinhardt via cctalk]

On 8/26/2017 4:02 PM, Pete Lancashire via cctalk wrote:

https://eauclaire.craigslist.org/atq/d/aa-occasional-sales/6248628617.html

Picture #8 in rear right corner


And #11.  It's got a keyboard and number pad so I'm thinking it's more likely a 
LA120 DECwriter III



No association with the seller just passing the info on



Picture #9 has a Model 43 Teletype in a row with what looks like an old 
mimeograph or electrostatic copier, some early electric typewrite and then an 
IBM Selectric of some sort.

--
John H. Reinhardt

Re: [sage-devel] Re: python3 in sage

[John H Palmieri]

On Thursday, August 24, 2017 at 2:50:09 PM UTC-7, William wrote:
>
> On Thu, Aug 24, 2017 at 2:17 PM, Nils Bruin  
> wrote: 
> > On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote: 
> >> 
> >> I'm not sure what the status is these days, but we may want to stop 
> >> including a python3 binary in Sage by default with "python3" right 
> >> there in the "sage -sh" path... 
> > 
> > 
> > As far as I understand, having python3 included in sage is part of the 
> > deliberate strategy towards porting sage to python3. Since sage comes 
> with 
> > its own python(2), the most straightforward move of sage would be 
> towards 
> > sage working on top of an included python3. 
>
> The problem is simply the "python3" executable which gets picked up 
> and breaks things. 
>

Will any python3 executable break things, or is there something 
specifically wrong with the one that Sage builds?
 

>
> > If you're using jupyter for non-sage-specific purposes (apparently 
> relying 
> > on a system python3), why not use system jupyter? Personally, I just 
> install 
> > the sage-jupyter kernel in the system jupyter. That way, your main 
> jupyter 
> > runs independent of sage (other than the extensions that get registered 
> upon 
> > registering the sage kernel), and doesn't get confused by the system 
> things 
> > sage does. 
>
> Nope.For example, Sage worksheets in Cocalc have a full "jupyter 
> bridge" that lets you simultaneously use several different Jupyter 
> kernels from within a Sage session, e.g., in different cells of a 
> notebook.  Having python3 in the PATH randomly breaks many of these. 
> Removing it, and everything works fine. 
>
> For now I guess we'll keep deleting local/bin/python3 ourselves... 
>
> Frickin' Guido... 
>
> William 
>
>
> -- 
> William (http://wstein.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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error Compiling Sage 8.0 from Source

[John H Palmieri]

Or as a stopgap, try building with the command

OPENBLAS_CONFIGURE="TARGET=HASWELL" make



On Thursday, August 17, 2017 at 2:00:03 PM UTC-7, Dima Pasechnik wrote:
>
> OK, this is what they call Kaby Lake H.
>
> You may try the patch on 
> https://trac.sagemath.org/ticket/23272
> (it also upgrades openblas to the latest release)
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[John H Palmieri]

On Tuesday, August 15, 2017 at 9:49:35 PM UTC-7, William wrote:
>
> On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri <jhpalm...@gmail.com 
> > wrote:
>
>> One of the very last lines of the report says
>>
>>>
>>> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
>>> or directory
>>>
>>>
>> You need to install gfortran on your computer.
>>
>
> We should really build binaries that don't require fortran to be 
> installed, or put in an error before Python even starts importing.
>

Yes, I agree.
 

>
> I personally hit or saw the above crash report dozens of times recently, 
> due to installing Sage binaries in various fairly minimal Docker containers.
>
> william
>
> -- 
> -- William Stein
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[John H Palmieri]

One of the very last lines of the report says

>
> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
> or directory
>
>
You need to install gfortran on your computer.



On Tuesday, August 15, 2017 at 6:15:01 PM UTC-7, kats...@gmail.com wrote:
>
> Sage Crash Report
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Calling java classes from Sage using Py4J

[John H Palmieri]

In Sage, "10" is a Sage integer, not a Python int. I am guessing that 
gateway.jvm.java.util.Random.nextInt 
expects a Python int for its input, and when it gets a Sage Integer, that 
causes a problem. What happens if you replace "random.nextInt(10)" with 
"random.nextInt(int(10))"?




On Wednesday, August 2, 2017 at 12:16:54 PM UTC-7, Paul DesJardin wrote:
>
> Hi, I'm new to using Sage and trying to interface to java classes using 
> py4j.  I've been successful using py4j using an anaconda installed version 
> of python (on a mac) but I'm running into Attribute errors using Sage.  The 
> one below is 'sage.rings.integer.Integer' object has no attribute 
> '_get_object_id'.  I don't understand the reason for the differences and 
> how to interpret the errors I'm receiving.  Any assistance or ideas of what 
> is causing this would be very much appreciated.  Thank you, PD  
>
>
>
>
> sage: *from* *py4j.java_gateway* *import* JavaGateway
>
> sage: gateway = JavaGateway()
>
> sage: random = gateway.jvm.java.util.Random()
>
> sage: number1 = random.nextInt(*10*)
>
> ---
>
> AttributeErrorTraceback (most recent call 
> last)
>
>  in ()
>
> > 1 number1 = random.nextInt(Integer(10))
>
>
>
> /Applications/SageMath/local/lib/python2.7/site-packages/py4j/java_gateway.pyc
>  
> in __call__(self, *args)
>
> *   1149* 
>
> *   1150* def __call__(self, *args):
>
> -> 1151 args_command, temp_args = self._build_args(*args)
>
> *   1152* 
>
> *   1153* command = proto.CALL_COMMAND_NAME +\
>
>
>
> /Applications/SageMath/local/lib/python2.7/site-packages/py4j/java_gateway.pyc
>  
> in _build_args(self, *args)
>
> *   1119* 
>
> *   1120* args_command = "".join(
>
> -> 1121 [get_command_part(arg, self.pool) for arg in 
> new_args])
>
> *   1122* 
>
> *   1123* return args_command, temp_args
>
>
> /Applications/SageMath/local/lib/python2.7/site-packages/py4j/protocol.pyc 
> in get_command_part(parameter, python_proxy_pool)
>
> *288* command_part += ";" + interface
>
> *289* else:
>
> --> 290 command_part = REFERENCE_TYPE + parameter._get_object_id()
>
> *291* 
>
> *292* command_part += "\n"
>
>
> /Applications/SageMath/src/sage/structure/element.pyx in 
> sage.structure.element.Element.__getattr__ 
> (/Applications/SageMath/src/build/cythonized/sage/structure/element.c:4230)
> ()
>
> *457* AttributeError: 
> 'LeftZeroSemigroup_with_category.element_class' object has no attribute 
> 'blah_blah'
>
> *458* """
>
> --> 459 return self.getattr_from_category(name)
>
> *460* 
>
> *461* cdef getattr_from_category(self, name):
>
>
> /Applications/SageMath/src/sage/structure/element.pyx in 
> sage.structure.element.Element.getattr_from_category 
> (/Applications/SageMath/src/build/cythonized/sage/structure/element.c:4339)
> ()
>
> *470* else:
>
> *471* cls = P._abstract_element_class
>
> --> 472 return getattr_from_other_class(self, cls, name)
>
> *473* 
>
> *474* def __dir__(self):
>
>
> /Applications/SageMath/src/sage/structure/misc.pyx in 
> sage.structure.misc.getattr_from_other_class 
> (/Applications/SageMath/src/build/cythonized/sage/structure/misc.c:1933)()
>
> *297* dummy_error_message.cls = type(self)
>
> *298* dummy_error_message.name = name
>
> --> 299 raise dummy_attribute_error
>
> *300* attribute = attr
>
> *301* # Check for a descriptor (__get__ in Python)
>
>
> AttributeError: 'sage.rings.integer.Integer' object has no attribute 
> '_get_object_id'
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: numerical semigroup in sagemath

[John H Palmieri]

On Tuesday, July 25, 2017 at 5:53:37 AM UTC-7, springfield .gion wrote:
>
> Hi, I need to create and manipulate the additive semigroups generated by 
> integers (such as those generated by tuples of coprime integers), but I am 
> struggling with the syntax; is there an easy way to create something along 
> the line of:
>
> S = ZZ.Semigroup([2,3])   
> S = {0,2,3,4,}
>
> Thanks in advance
>

You can try this:

S = NN.subsemigroup([2,3])   # or ZZ.subsemigroup([2,3])

although (a) it is not clear to me that this the right thing (it looks like 
the multiplicative subsemigroup, not the additive one) and (b) I can't do 
anything sensible with it.

So I tried to use multiplicative semigroups instead. If A is the 
multiplicative semigroup consisting of powers of 2, then we could ask for 
the multiplicative subsemigroup generated by 2**2 and 2**3, which should be 
analogous to what you want. Unfortunately, it is broken:

sage: A = NN.subsemigroup([2])
sage: S = A.subsemigroup([2**2, 2**3])

Listing some elements and their base 2 logs is promising:

sage: list(S.some_elements())  # output omitted since it is a little 
lengthy
sage: [log_b(ZZ(_),2) for _ in list(S.some_elements())]   # output 
omitted

but this is surprising:

sage: S.cardinality()
11441

I certainly didn't know that this semigroup was finite, let alone precisely 
what its cardinality is.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: sage installation on kubuntu 16.04

[John H Palmieri]

One of the last lines in the crash report:

   ImportError: libgfortran.so.3: cannot open shared object file: No such file 
or directory

It looks like you need to install gfortran.

-- 
John




On Sunday, July 23, 2017 at 2:54:43 AM UTC-7, Santosh Pattanayak wrote:
>
>  Hello,
>  I tried to install sage: 7.5.1 on my kubuntu 6.4 laptop. When I 
> tried to run the command ./sage it gave me the following error. The crash 
> report is also attached herewith for your reference.
>
> ==
> ==
>
> ops, Sage crashed. We do our best to make it stable, but...
>
> A crash report was automatically generated with the following information:
>   - A verbatim copy of the crash traceback.
>   - A copy of your input history during this session.
>   - Data on your current Sage configuration.
>
> It was left in the file named:
> '/home/santosh/.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  < 
> /home/santosh/.sage/ipython-5.0.0/Sage_crash_report.txt
>
> To ensure accurate tracking of this issue, please file a report about it 
> at:http://trac.sagemath.org
>
> Hit  to quit (your terminal may close):
> ==
>
> Thanks
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

[John H Palmieri]

I just had the same problem with a new computer (Kaby Lake processor, 
apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but 
can't detect the precise CPU? (I can't do this, but maybe someone else can.)

  John


On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik wrote:
>
> Indeed, OPENBLAS_CONFIGURE="TARGET=ATOM" is a catch-all x86_64 processors 
> target.
> Perhaps one can try the development version of openblas on these processors
> (from https://github.com/xianyi/OpenBLAS)
>
> On Friday, July 14, 2017 at 12:29:12 AM UTC+1, Christopher Phoenix wrote:
>>
>> I'm building Sage 7.6 on my laptop, and there was an error making 
>> openblas that directed me to the log files for that package. The log file 
>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>> suggested I email this google group to explain the problem, with the 
>> relevant part of the log files. So I've attached it below. 
>>
>> OS: Ubuntu Mate 16.04 LTS
>> Sage Version: 7.6
>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>> cpu cores
>>
>> Before the build, I made sure that I had all the listed dependencies and 
>> suggested packages already installed. Then I cloned the Git repo, set 
>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>> it stopped and reported the error. I asked about this issue on sage-support 
>> earlier (https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ
>> ).
>>
>> Someone had the same issue on very similar hardware (another 11e) here: 
>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>> log files look almost exactly the same. They reported that setting 
>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>> going to try setting this and building Sage again later today. I was a 
>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>> a catch-all setting for lower-end processors?
>>
>> Any advice will be greatly appreciated!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[John H Palmieri]

On Sunday, June 18, 2017 at 4:41:22 AM UTC-7, Dima Pasechnik wrote:
>
> git repo is not relevant, but a python module that shadows a Sage python 
> module would be a problem.


For example, if you have your own file "parser.py", it would interfere with 
the standard Python module "parser". 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Option for docbuilding without plots?

[John H Palmieri]

Also "make doc-html-no-plot" as documented here:

  http://doc.sagemath.org/html/en/installation/source.html#make-targets

John



On Saturday, June 17, 2017 at 12:26:21 AM UTC-7, Thierry 
(sage-googlesucks@xxx) wrote:
>
> Hi, 
>
> each of the following should work: 
>
> export SAGE_SKIP_PLOT_DIRECTIVE='yes' 
>
> or 
>
> export SAGE_DOCBUILD_OPTS+=' --no-plot' 
>
> See ticket #17498. 
>
> Ciao, 
> Thierry 
>
>
> On Fri, Jun 16, 2017 at 10:05:20PM -0700, Travis Scrimshaw wrote: 
> > While I do enjoy the plots (thank you to everyone who has been working 
> on 
> > them to improve our documentation), they take a lot of time to render 
> while 
> > building the docs. I have to do doc-cleans often enough that I don't 
> want 
> > to have to rebuild the plots just to check that the documentation does 
> > build for my changes. 
> > 
> > Is there currently such an option? If not, I am asking nicely someone 
> more 
> > familiar with the docbuilding to add it. 
> > 
> > Thanks, 
> > Travis 
> > 
> > -- 
> > 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.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: typo in simplicial complex documentation?

[John H Palmieri]

On Sunday, June 11, 2017 at 10:13:52 AM UTC-7, David Joyner wrote:
>
> On Sun, Jun 11, 2017 at 11:30 AM, John H Palmieri 
> <jhpalm...@gmail.com > wrote: 
> > 
> > 
> > On Saturday, June 10, 2017 at 7:05:49 PM UTC-7, David Joyner wrote: 
> >> 
> >> On Thu, Jun 8, 2017 at 10:49 PM, John H Palmieri <jhpalm...@gmail.com> 
> >> wrote: 
> >> > 
> >> > 
> >> > On Thursday, June 8, 2017 at 5:16:15 PM UTC-7, David Joyner wrote: 
> >> >> 
> >> >> Hi all: 
> >> >> 
> >> >> This is kind of a newbie question, as I'm not an expert on 
> simplicial 
> >> >> complexes. It's also a minor technical issue on the documentation, 
> not 
> >> >> the code. 
> >> >> 
> >> >> I'm trying to debug some code of mine and, on reading the 
> >> >> documentation for chain_complex on 
> >> >> 
> >> >> 
> >> >> 
> http://doc.sagemath.org/html/en/reference/homology/sage/homology/simplicial_complex.html,
>  
>
> >> >> found this: "The rows and columns of the boundary matrices are 
> indexed 
> >> >> by the lists given by the n_cells() method, which by default are 
> >> >> sorted." On the other hand, the documentation for n_cells has this 
> >> >> statement: "Sort the list if the argument sort is True. If sort is 
> >> >> None (the default), then sort depending on the value of the 
> >> >> sort_facets parameter (from  the initialization of the simplicial 
> >> >> complex)." However, the sort_facets parameter (unless I'm mistaken) 
> >> >> does not sort the individual faces but rather sorts the vertices in 
> >> >> each facet. 
> >> > 
> >> > 
> >> > The documentation means that if "sort_facets" was True originally, 
> then 
> >> > n_cells will also sort its result before returning it. ("then sort 
> >> > depending 
> >> > on the value of the sort_facets parameter": so if sort_facets was 
> True, 
> >> > then 
> >> > n_cells should also sort. It doesn't mean "sort using the effect of 
> the 
> >> > sort_facets parameter", but sort depending on its value, which is 
> True 
> >> > or 
> >> > False. This could be made clearer, I guess.) 
> >> > 
> >> 
> >> 
> >> To be clear, I am getting different computations using the same sage 
> >> computations on different machines. One (recent, but used, linux) 
> >> machine consistently gives ones result, the other gives (randomly?) 
> >> several others. The "other" (a 8 yr old, a mac with possibly memory 
> >> issues) machine gives different results. I'm not saying your methods 
> >> are machine dependent, just that *for me* they seem to be. 
> >> 
> >> To be clear, these "inconsistent" computations take at least one day. 
> >> The "toy" (consistent) examples are okay. 
> > 
> > 
> > That's strange. Are you just getting different orders when you sort, or 
> > different answers for homology? Are the answers consistent on each 
> machine? 
> > What type of object are the vertices? 
> > 
>
> The example which gives strange output is the bipyramid complex: 
>
> S = SimplicialComplex(maximal_faces=[(1,2,3), (1,2,4),\ 
>   (1,2,5), (1,3,4),(1,3,5),(2,3,4),(2,3,5)]) 
>
> which has 9 1-faces. I'm computing the list of all stable configurations, 
> namely vectors c in ZZ^9 having non-negative components which cannot 
> fire (in the sense of chip-firing - see Duval, Klivans, Martin 
> https://arxiv.org/pdf/1101.3981.pdf) with respect to the 1-dimls 
> simplicial 
> spanning tree given by the 1-faces (1, 4), (1,5), (2,5), (3,4). On an old 
> mac running OS 10.11.6 and sage 7.2.b0, the output is usually 268125, 
> after about a day, but once I also got 137500. On a linux machine running 
> ubuntu and sage 7.3, I always get 395625. These computations use 
> the S.chain_complex.differential method to compute the 1-diml 
> combinatorial up Laplacian, Q, then does a time-consuming search. 
> (Basically, I check that no column vector q of Q, except possibly one 
> corresponding to a face in the spanning tree, has the property that 
> all components of c-q remain non-negative, except possibly those 
> corresponding to a face in the spanning tree.) 
>
> A similar computation using the 3-simplex is relatively quick and 
> always produces 
> 2500 st

Re: [sage-support] Re: typo in simplicial complex documentation?

[John H Palmieri]

On Saturday, June 10, 2017 at 7:05:49 PM UTC-7, David Joyner wrote:
>
> On Thu, Jun 8, 2017 at 10:49 PM, John H Palmieri <jhpalm...@gmail.com 
> > wrote: 
> > 
> > 
> > On Thursday, June 8, 2017 at 5:16:15 PM UTC-7, David Joyner wrote: 
> >> 
> >> Hi all: 
> >> 
> >> This is kind of a newbie question, as I'm not an expert on simplicial 
> >> complexes. It's also a minor technical issue on the documentation, not 
> >> the code. 
> >> 
> >> I'm trying to debug some code of mine and, on reading the 
> >> documentation for chain_complex on 
> >> 
> >> 
> http://doc.sagemath.org/html/en/reference/homology/sage/homology/simplicial_complex.html,
>  
>
> >> found this: "The rows and columns of the boundary matrices are indexed 
> >> by the lists given by the n_cells() method, which by default are 
> >> sorted." On the other hand, the documentation for n_cells has this 
> >> statement: "Sort the list if the argument sort is True. If sort is 
> >> None (the default), then sort depending on the value of the 
> >> sort_facets parameter (from  the initialization of the simplicial 
> >> complex)." However, the sort_facets parameter (unless I'm mistaken) 
> >> does not sort the individual faces but rather sorts the vertices in 
> >> each facet. 
> > 
> > 
> > The documentation means that if "sort_facets" was True originally, then 
> > n_cells will also sort its result before returning it. ("then sort 
> depending 
> > on the value of the sort_facets parameter": so if sort_facets was True, 
> then 
> > n_cells should also sort. It doesn't mean "sort using the effect of the 
> > sort_facets parameter", but sort depending on its value, which is True 
> or 
> > False. This could be made clearer, I guess.) 
> > 
>
>
> To be clear, I am getting different computations using the same sage 
> computations on different machines. One (recent, but used, linux) 
> machine consistently gives ones result, the other gives (randomly?) 
> several others. The "other" (a 8 yr old, a mac with possibly memory 
> issues) machine gives different results. I'm not saying your methods 
> are machine dependent, just that *for me* they seem to be. 
>
> To be clear, these "inconsistent" computations take at least one day. 
> The "toy" (consistent) examples are okay. 
>

That's strange. Are you just getting different orders when you sort, or 
different answers for homology? Are the answers consistent on each machine? 
What type of object are the vertices?
 

>
> > I don't know if there is ever a good reason to specify 
> sort_facets=False. 
> > Maybe we should deprecate it? 
> > 
> >> 
> >> In my code, I expected the faces of a fixed dimension to 
> >> be returned as a deterministic sorted list not a set whose ordering 
> >> could be random. Now, it *does* seem as though the faces are sorted. 
> >> It's just that, to me, the documentation of n_cells doesn't make that 
> >> clear. 
> >> 
> >> I'm asking if I'm mis-understanding something here or not. 
> >> 
> >> - David Joyner 
> > 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To post to this group, send email to sage-s...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-support. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 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.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: typo in simplicial complex documentation?

[John H Palmieri]

On Thursday, June 8, 2017 at 5:16:15 PM UTC-7, David Joyner wrote:
>
> Hi all: 
>
> This is kind of a newbie question, as I'm not an expert on simplicial 
> complexes. It's also a minor technical issue on the documentation, not 
> the code. 
>
> I'm trying to debug some code of mine and, on reading the 
> documentation for chain_complex on 
>
> http://doc.sagemath.org/html/en/reference/homology/sage/homology/simplicial_complex.html,
>  
>
> found this: "The rows and columns of the boundary matrices are indexed 
> by the lists given by the n_cells() method, which by default are 
> sorted." On the other hand, the documentation for n_cells has this 
> statement: "Sort the list if the argument sort is True. If sort is 
> None (the default), then sort depending on the value of the 
> sort_facets parameter (from  the initialization of the simplicial 
> complex)." However, the sort_facets parameter (unless I'm mistaken) 
> does not sort the individual faces but rather sorts the vertices in 
> each facet.


The documentation means that if "sort_facets" was True originally, then 
n_cells will also sort its result before returning it. ("then sort 
depending on the value of the sort_facets parameter": so if sort_facets was 
True, then n_cells should also sort. It doesn't mean "sort using the effect 
of the sort_facets parameter", but sort depending on its value, which is 
True or False. This could be made clearer, I guess.)

I don't know if there is ever a good reason to specify sort_facets=False. 
Maybe we should deprecate it?
 

> In my code, I expected the faces of a fixed dimension to 
> be returned as a deterministic sorted list not a set whose ordering 
> could be random. Now, it *does* seem as though the faces are sorted. 
> It's just that, to me, the documentation of n_cells doesn't make that 
> clear. 
>
> I'm asking if I'm mis-understanding something here or not. 
>
> - David Joyner 
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [Evolution] Clicking delete icon on highlighted message sometimes causes following message to be deleted, too

[Dr. John H. Lauterbach]

Thank you, Andre.  Problem turned out to be hardware:  a worn out mouse.  
Problem went away with new mouse.

John

-Original Message-
From: Andre Klapper <ak...@gmx.net>
To: evolution-list@gnome.org
Subject: Re: [Evolution] Clicking delete icon on highlighted message sometimes 
causes following message to be deleted, too
Date: Mon, 05 Jun 2017 17:33:34 +0200

On Mon, 2017-06-05 at 10:07 -0400, Dr. John H. Lauterbach wrote:
> evolution 3.20.5 operating under Ubuntu 16.04 64-bit
> 
> Intermittent error that has been around for past month or so.  If
> message in message list (inbox, for example) is highlighted, clicking
> on the DELETE icon (Trash bucket) deletes not only the highlighted
> message but also the message below.  This does not happen if the
> Delete key is used.  Mouse is Logitech M185.

Never heard of that, but the "keyboard input vs toolbar button"
behavior sounds like https://bugzilla.gnome.org/show_bug.cgi?id=775656
which is fixed in Evolution version 3.22.5.

You could ask packagers of your distribution to backport the fix, or
upgrade to a more recent version of your distribution which includes
Evolution 3.22.5 or newer, or try to find some more recent third-party
packages out there (Ubuntu calls that "PPA") for your distribution.

andre
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] Repeated errors due to missing file

[Dr. John H. Lauterbach]

evolution version 3.20.5 works very well under Ubuntu 16.04.

John 

-Original Message-
From: Jim Ohlstein 
To: evolution-list@gnome.org
Subject: Re: [Evolution] Repeated errors due to missing file
Date: Wed, 07 Jun 2017 07:14:16 -0400

On Wed, 2017-06-07 at 08:22 +0200, Milan Crha wrote:
> On Tue, 2017-06-06 at 08:40 -0400, Jim Ohlstein wrote:
> > 
> > I've recently switched to Evolution on Ubuntu 16.04 using Gnome.
>   Hi,
> Ubuntu 16.04, Ubuntu 16.04,... what is the version of Evolution
> there,
> please?

3.18.5.2

> 
> > 
> > when a new mail arrives I see a yellow error banner
> > and a message like "Execution of filter 'Junk check' failed: Empty
> > cache file: /home/jim/.cache/evolution/mail/1496683913.10061.19@lin
> > us
> > /folders/INBOX/cur/30/1350 ".
> That comes from an IMAPx account and it had been (mostly?) addressed
> in
> 3.22.x or 3.24.x of evolution-data-server. I guess it's not the
> version
> you use, because it wasn't available in early 2016.

Yes, this is the "stock" version installed with Gnome.

> 
> > 
> > I haven't set up a "Junk check" filter, and can't find it.
> Each IMAP account has a checkbox in its Properties->Receiving Options
> tab, saying whether to apply filters and another specific to Junk
> filtering. There is also Edit->Preferences->Mail Preferences->Junk
> tab.
> There had been some bug about junk filtering being run for new
> messages
> regardless these options in the recent past, but I do not recall
> whether it went anywhere, I'm sorry.
> 
> > 
> > It doesn't seem to cause any ill effect. Is there a way to correct
> > this, or at least to suppress the warning?
> You can try to limit concurrent connections, also in account
> Properties->Receiving Options tab, to 1, but it has some side
> effects,
> like slower response from the account (as one connection used for
> everything means that any operation is waiting in a queue until the
> current operation is finished, thus for example folder update blocks
> message download).a try.

Thanks. I'll give that 

> 
>   Bye,
>   Milan
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[sage-support] Re: Sage Crash Report

[John H Palmieri]

"ImportError: libgfortran.so.3: cannot open shared object file: No such file or 
directory"

It looks like you need to install fortran on your machine.



On Monday, June 5, 2017 at 10:12:12 AM UTC-7, Vincent HERBERT wrote:
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[Evolution] Clicking delete icon on highlighted message sometimes causes following message to be deleted, too

[Dr. John H. Lauterbach]

evolution 3.20.5 operating under Ubuntu 16.04 64-bit

Intermittent error that has been around for past month or so.  If message in
message list (inbox, for example) is highlighted, clicking on the DELETE icon
(Trash bucket) deletes not only the highlighted message but also the message
below.  This does not happen if the Delete key is used.  Mouse is Logitech M185.

John___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[sage-devel] Sage Python 3 proposal

[John H Palmieri]

I have a proposal for making the transition to use Sage with Python 3. See 
https://trac.sagemath.org/ticket/23119 for details (and a branch which 
works, at least in my limited testing). The proposal:

- Have a new command "sage3" which runs Sage using Python 3.

- If you build Sage with the environment variable SAGE_PYTHON3 set to 
"yes", then build for both Python 2 and Python 3. Although this will 
increase the build time and the required disk space (by 800MB when I tried 
it), it means that you should have a choice about how to run Sage which 
does not depend on how you built it.

- Although for now, SAGE_PYTHON3 will not be set, eventually we could 
switch to having it always set to "yes", to encourage Python 3 development 
and prevent Python 3 incompatibilities. (Then later we can change the 
behavior again, only building for Python 3.)

- It would probably be good to have a ./configure option instead of the 
environment variable, but I have not tried to implement that.

Please provide feedback. I have not heard any other suggestions for how to 
run Sage with Python 3, so I thought a concrete proposal would be good to 
get the ball rolling.

This proposal still requires solving the problems Frédéric has already 
mentioned 
(https://groups.google.com/d/msg/sage-devel/FqR-37Fu3tY/RjDx_SG_BAAJ), as 
well as ongoing work to make the Sage library compatible with Python 3. 
Everyone is encouraged to contribute!

-- 
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.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

I'm getting intermittent timeouts from src/sage/doctest/external.py, and in 
particular the "has_mathematica()" test. This is a new (but underpowered) 
computer and it does not have mathematica installed. If I run

   $ sage --sh
   $ math-readline

then 19 out of 20 times, it fails immediately, but every now and then, 
maybe when the computer is more heavily loaded, it does something else: it 
says

   /bin/sh: math: command not found

(as with the immediate failures) and then it waits for input. This must be 
what is causing the timeout in the doctest. If I hit RET, I get the shell 
prompt back. Why is it waiting for input when the "math" process failed? 
Any suggestions for how I could diagnose what's going on?

  John


 
On Wednesday, May 24, 2017 at 2:49:41 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
>
> c011cfa Updated SageMath version to 8.0.beta8
> 5bb7623 Trac #22559: Matchings in Bipartite Graphs
> 2b9da89 Trac #23050: method to reverse row and column orders of a matrix
> 461264e Trac #23049: py3: fix bad syntax for print again
> 9575130 Trac #23048: Fix directions acceptable keywords in limit function
> b4ed7f4 Trac #23041: Update documentation of MILP
> 4832a1d Trac #23040: Fix conway_polynomials build with SAGE_PYTHON3=yes
> f86b45a Trac #23033: preliminary work for unicode interfaces
> 783d707 Trac #22995: Dummy inverse Laplace for giac
> fcdb474 Trac #22975: py3: some absolute import in pyx files
> 17fb69c Trac #21791: Improve Order Ideals Lattice and Linear Extension 
> Cardinality.
> cbf72fe Trac #21066: Unpickle overrides for finite fields
> 00ab801 Trac #16825: Implement untwisted affine Lie algebras
> 3fe2a5b Trac #23013: Random failure in libecm.pyx
> 0042496 Trac #23007: Remove "public" from methods where it is not needed
> 1bcb8e2 Trac #22295: Some updates to the installation guide
> c78d6b9 Trac #21180: cantor_product: allow keyword arguments to be passed 
> on to IntegerListsLex
> 033128d Trac #20099: test improved evaluation of trigonometric functions 
> and complex exponential function
> cc913d6 Trac #23021: Implement Essential quasisymmetric functions
> 39fb68f Trac #22490: Upgrade pygments to version 2.2.0
> 77bb055 Trac #22411: Improve handling of MtxLibDir
> 354dd4a Trac #22159: Upgrade to libpng 1.6.29
> a2b2bea Trac #23031: Fix ECM 7.0 build on Cygwin
> acddf45 Trac #21258: Random failure in trace.py
> 51bea96 Trac #23019: Documentation fix for 
> ImplicitSuffixTree.transition_function
> 0f7ca2f Trac #22985: (EASY) bug in constructing an error message for 
> DiGraph constructor
> 399682e Trac #22974: LatticePoset: few more crosslinks
> a5bdf27 Trac #13733: Incorrect integral in Maxima
> 8a9298b Trac #23035: yet another load of typos
> 222f7f9 Trac #23034: Remove "sage --bdist" from top-level README.md
> 1474b34 Trac #23006: small cleanup of primes.py
> 9fe6d3f Trac #23003: adding a method "without_bounds" to posets
> ae277e5 Trac #22996: change catalan number behaviour at n=-1
> cf32199 Trac #23036: Speedup KR rigged configurations
> 9ff7e17 Trac #23032: linear_code.covering_radius fails due to unloaded gap 
> package
> 064f48b Trac #23030: remove call of apply() in expressions.pyx
> a78e08e Trac #23022: Use patched Cython for farey_symbol
> 0196818 Trac #23014: Use maximal vector in the local energy function
> 94e3b65 Trac #22998: Unable to parse hypergeometric result from 
> mathematica_free
> e8ed035 Trac #22969: Upgrade to Pynac-0.7.7
> 6207566 Trac #22632: Cythonize CombinatorialFreeModuleElement
> ffa1af4 Trac #23005: py3: get rid of cmp in doctest framework
> d4d0988 Trac #23004: Add Cython patch for Cygwin
> c532ae3 Trac #23001: Implement is_NaN for all rings with NaN elements
> 441c576 Trac #23000: Fix inconsistency in 
> `Modules.FiniteDimensional.extra_super_categories`
> 3fa0c6a Trac #23029: Bug in headers included from Linbox with variable 
> named "B0"
> 569f508 Trac #22997: Parse unevaluated integral from giac
> c5e3b18 Trac #22961: wrong answers from codesize_upper_bound()
> 94ca8bd Trac #22896: Stop using stdsage.pxi
> d34101e Trac #22305: weak_dict.pyx is not python3 compatible
> d567f99 Trac #16822: Implement PBW bases for the universal enveloping 
> algebra
> ca7a1d5 Trac #15423: Add auto-rebasing mechanism for Cygwin
> 2334124 Trac #22992: Speedup highest weight rigged configuration crystals
> d043f54 Trac #22917: update zlib to 1.2.11
> 8e21be9 Trac #22739: Background image for .app.dmg disappears under Mac OS 
> Sierra
> 9127284 Trac #11349: Doctest fix for: Sage can't make sense of a Maxima 
> result
> 1fe0b90 Trac #20084: residue: mathematically wrong output
> 77262a2 Trac #20986: Enhancements to sage-rebase scripts
> 7a36941 Updated SageMath version to 8.0.beta7
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To 

Re: [Evolution] Subfolders under Inbox suddenly disappeared

[Dr. John H. Lauterbach]

Thank you, Paul:

Here are the answers to your questions.

All e-mail accounts on secretary's PC are POP.

If I go to /home/holly/.local/share/evolution/mail, I don't see the list of 
subfolders that used to be there and I find on my PC for evolution 3.20.5

Yes, I am logged in as Holly.  She found the problem with missing Firefox 
bookmarks.

Evolution on her PC is connected to the Internet.

Have about 9% free disk on partition that holds her home directory and 
Evolution files.

John





-Original Message-
From: Paul Smith <p...@mad-scientist.net>
Reply-to: p...@mad-scientist.net
To: j...@lauterbachandassociates.com, evolution-list <evolution-list@gnome.org>
Subject: Re: [Evolution] Subfolders under Inbox suddenly disappeared
Date: Sat, 27 May 2017 11:42:02 -0400

On Sat, 2017-05-27 at 10:17 -0400, Dr. John H. Lauterbach wrote:
> RE: Evolution 3.20.5 running under Ubuntu 16.04 64-bit
> 
> Between the time my secretary left the past Wednesday and when she
> started work Friday noon (PC running all the time, APC UPS on incoming
> power line) Evolution lost the subfolders under Inbox.  I tried
> deleting renaming folders.db to folders.dbb and letting Evolution
> rebuild folders.db on restart, but no change, with about 4K e-mails in
> the Inbox that had not been sorted into subfolders.  Unfortunately, no
> recent full Evolution backup available.  Have checked disk partitions
> for errors using "Check" function on bootable CD-ROM version of
> Gparted and all are okay.

Thank you for the version information.  Please also provide
information on the type of email account: are you using POP?  IMAP? 
Gmail?  Exchange?  SMTP?

I'm not clear what you see.  Is the Inbox folder visible but no
subfolders?  If so I assume you've clicked the arrow next to "Inbox" to
make sure it's expanded?  If the Inbox folder is visible is there any
email in it?

Also, check the icon at the lower-left of the Evolution window; is it
"connected"?  If you hover over it with your mouse does it say
"Evolution is currently online"?

> One other note:  The bookmarks list for Firefox was also lost.

It almost sounds like you are logged in as a different user account than
before, that is not configured the same way.  I can't think of a reason
that only Firefox bookmarks and Evolution folders would be invisible but
everything else is the same.

Have you verified that you're not low on disk space?
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] Subfolders under Inbox suddenly disappeared

[Dr. John H. Lauterbach]

Thank you, Peter.  We use Nemo with the "show hidden files" option on. If they 
were there, we would see them as I double checked with my laptop PC where same 
version of evolution and same OS is being used.

Looking for way of rebuilding database as size of vfolders.db is correct size 
for containing missing subfolders.

John

-Original Message-
From: Pete Biggs 
To: evolution-list@gnome.org
Subject: Re: [Evolution] Subfolders under Inbox suddenly disappeared
Date: Sun, 28 May 2017 19:21:00 +0100

> All e-mail accounts on secretary's PC are POP.
> 
> If I go to /home/holly/.local/share/evolution/mail, I don't see the
> list of subfolders that used to be there and I find on my PC for
> evolution 3.20.5

If it's POP, then the mail is stored in the local folders so you should
be looking in .local/share/evolution/mail/local - and, apologies if you
already know this, the mail is stored in Maildir format so the actual
mail folder names all start with a '.' so you will have to use 'ls -a'
to see them.

P.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[sage-devel] Re: python3 : help needed

[John H Palmieri]

On Friday, May 26, 2017 at 8:40:22 AM UTC-7, Nils Bruin wrote:
>
> On Friday, May 26, 2017 at 7:52:57 AM UTC-7, John H Palmieri wrote:
>>
>> If you build Sage's IPython package with SAGE_PYTHON3=yes, then it will 
>> install a script local/bin/ipython3. (Note then that if the sage-location 
>> script runs, its function make_scripts_relative will break 
>> local/bin/ipython3 because it will replace the #! line, which initially 
>> uses Sage's Python3, to a generic /usr/bin/env python. Another broken part 
>> to fix.)
>>
>
> Ah, that would explain it. 
>

This issues is tracked at https://trac.sagemath.org/ticket/23039 (not that 
I know how to fix it properly).

  John

 

> Data point on naming: on my fedora25, there are /usr/bin/ipython, 
> /usr/bin/ipython2, /usr/bin/python3 (each separate files). ipython and 
> ipython3 are identical. The ipython2 might be a historical remnant, though.
>
> For Python, there are /usr/bin/python2.7, /usr/bin/python3.5 with 
> /usr/bin/python a symlink pointing to /usr/bin/python2.7 (via some other 
> symlinks). 
>
> So there seems to be precedent that the naming convention for "python" 
> does not translate to naming convention for "ipython".
>
> In any case, I think it would be good to ensure we at least have 
> functioning *python2* and *python3* links. What the unnumbered names refer 
> to is then slightly less vital.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.