Re: Advice on Desoldering an IC

[John H. Reinhardt via cctalk]

I bought a Hakko FR301-03 in mid 2020 and, while I haven't used it for a lot, I 
can attest it has worked very well for what I have done.  I have used it to 
replace the RIFA caps on the boards of 3 H7864 power supplies and the pico 
fuses on several KDJ11-B 11/73/83 CPU boards.  In each case the solder was 
removed quickly and the parts literally dropped off the boards.  I have also 
used it to rework some badly soldered (by me) sockets on a QBone card I was 
assembling.  While it was relatively expensive (to me) it has been worth the 
cost.

John H. Reinhardt



On 4/15/2022 4:32 PM, Rob Jarratt via cctalk wrote:

I do have some diagonal cutters, but although small they seem to be still too 
bulky to reach the pins. I will have to try to find some finer ones. These seem 
to look OK: 
https://uk.farnell.com/klein-tools/d275-5/wire-cutter-diagonal-127mm/dp/2839543

  


Also, I have seen the recommendations regarding a Hakko 808. It looks like the 
modern successor is the FR301 
https://www.hakko.co.uk/product/fr-301-portable-desoldering-gun/. I think what 
may be better about this is the wider choice of nozzles.

  


Regards

  


Rob

  


From: Chris Zach 
Sent: 15 April 2022 18:51
To: r...@jarratt.me.uk; Rob Jarratt ; General Discussion: 
On-Topic and Off-Topic Posts ; Rob Jarratt via cctalk 

Subject: Re: Advice on Desoldering an IC

  


Cut the pins with a very sharp set of dykes then remove them one at a time. 
Then use flux and detailer braid to remove the solder

On April 15, 2022 1:49:33 PM EDT, Rob Jarratt via cctalk mailto:cctalk@classiccmp.org> > wrote:

I am trying to remove an IC from my PDP 11/24 CPU, a DS8641. I am really
struggling to desolder it. I am using the technique of applying fresh solder
and then removing it. But after multiple cycles of this I think I am
starting to damage the PCB.

  


I am using a fairly cheap desoldering station (this one
https://cpc.farnell.com/duratool/d00672/desoldering-station-uk-eu-plug/dp/SD
01384?st=duratool%20desoldering). Its spec in terms of vacuum pressure is
equivalent to that of the professional Hakko ones though. I am also trying a
hand desoldering pump. None of these are able to clear many of the holes of
solder, although some are doing better than others. Nevertheless, the IC
remains stubbornly unmoving.

  


Are there any tips for removing ICs?

  


Thanks

  


Rob

Re: [sage-devel] Copy & Paste

[John H Palmieri]

ot/src/bin/sage-env -> 
> ../../../../../src/bin/sage-env
> ~/sage-9.6$
>
> ~/sage-9.6$ ls -l sage/pkgs/sagemath-categories/bin/sage
> lrwxrwxrwx 1 hph hph 21 Apr 10 19:49 
> sage/pkgs/sagemath-categories/bin/sage -> ../../../src/bin/sage
> ~/sage-9.6$ ls -l sage/pkgs/sagemath-categories/bin/sage-env
> lrwxrwxrwx 1 hph hph 25 Apr 10 19:49 
> sage/pkgs/sagemath-categories/bin/sage-env -> ../../../src/bin/sage-env
> ~/sage-9.6$
>
> ~/sage-9.6$ ls -l sage/pkgs/sagemath-objects/bin/sage
> lrwxrwxrwx 1 hph hph 21 Apr 10 19:49 sage/pkgs/sagemath-objects/bin/sage 
> -> ../../../src/bin/sage
> ~/sage-9.6$ ls -l sage/pkgs/sagemath-objects/bin/sage-env
> lrwxrwxrwx 1 hph hph 25 Apr 10 19:49 
> sage/pkgs/sagemath-objects/bin/sage-env -> ../../../src/bin/sage-env
> ~/sage-9.6$
>
> ~/sage-9.6$ ls -l sage/build/pkgs/sagemath_categories/src/bin/sage
> lrwxrwxrwx 1 hph hph 21 Apr 10 19:49 
> sage/build/pkgs/sagemath_categories/src/bin/sage -> ../../../src/bin/sage
> ~/sage-9.6$ ls -l sage/build/pkgs/sagemath_categories/src/bin/sage-env
> lrwxrwxrwx 1 hph hph 25 Apr 10 19:49 
> sage/build/pkgs/sagemath_categories/src/bin/sage-env -> 
> ../../../src/bin/sage-env
> ~/sage-9.6$
>
> ~/sage-9.6$ ls -l sage/build/pkgs/sagemath_objects/src/bin/sage
> lrwxrwxrwx 1 hph hph 21 Apr 10 19:49 
> sage/build/pkgs/sagemath_objects/src/bin/sage -> ../../../src/bin/sage
> ~/sage-9.6$ ls -l sage/build/pkgs/sagemath_objects/src/bin/sage-env
> lrwxrwxrwx 1 hph hph 25 Apr 10 19:49 
> sage/build/pkgs/sagemath_objects/src/bin/sage-env -> 
> ../../../src/bin/sage-env
> ~/sage-9.6$
>
>
> On Thu, Apr 14, 2022 at 8:25 PM John H Palmieri  
> wrote:
>
>> I think your search is following some symbolic links: only three of these 
>> instances are under version control (git):
>>
>> % git grep 'resolvelinks()'
>> sage:resolvelinks() {
>> src/bin/sage:resolvelinks() {
>> src/bin/sage-env:resolvelinks() {
>>
>> The last one should probably have a comment in line with the first two.
>>
>>
>> On Thursday, April 14, 2022 at 4:55:08 PM UTC-7 hohoa...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> 
>>> Personally, I would rather see the time spent investigating whether or
>>> not we truly need the symlink-free path in the instances where
>>> resolvelinks() is currently used. I would guess not -- that there is a
>>> better solution to whatever other problem prompted the resolvelinks()
>>> function. But I don't know what that problem was. And to remove the
>>> function and "see what happens" would be committing yourself to
>>> answering bug reports from weird sage installs for the next twelve
>>> months.
>>> 
>>>
>>> Now your concern is truly appreciated.
>>>
>>>  "Find in File" in "Visual Studio Code" reveals duplications in* 24 
>>> files in 13 directories* (please find the results appended below)
>>>
>>> It is amazing that SageMath is still maintainable up to now,  release 9.6
>>> Maybe 'resolvelinks' is just  the tip of an iceberg (something more 
>>> important is missing?)
>>>
>>> Best wishes,
>>>
>>> phiho
>>>
>>> *# Query: resolvelinks()*
>>> # ContextLines: 1
>>>
>>> 24 results - 24 files
>>>
>>> sage/sage:
>>>   32  # meantime however the two should be kept synchronized.
>>>   33: resolvelinks() {
>>>   34  # $in is what still needs to be converted (normally has no 
>>> starting slash)
>>>
>>> sage/build/pkgs/sagelib/src/bin/sage:
>>>   4  # the top-level "sage" script. Please keep them synchronized.
>>>   5: resolvelinks() {
>>>   6  # $in is what still needs to be converted (normally has no 
>>> starting slash)
>>>
>>> sage/build/pkgs/sagelib/src/bin/sage-env:
>>>   35  #
>>>   36: resolvelinks() {
>>>   37  # $in is what still needs to be converted (normally has no 
>>> starting slash)
>>>
>>> sage/build/pkgs/sagemath_categories/src/bin/sage:
>>>   4  # the top-level "sage" script. Please keep them synchronized.
>>>   5: resolvelinks() {
>>>   6  # $in is what still needs to be converted (normally has no 
>>> starting slash)
>>>
>>> sage/build/pkgs/sagemath_categories/src/bin/sage-env:
>>>   35  #
>>>   36: resolvelinks() {
>>>   37  # $in is what still needs to be converted (normally has no 
>>> starting slash)
>>>
>

Re: [sage-devel] Copy & Paste

[John H Palmieri]

I think your search is following some symbolic links: only three of these 
instances are under version control (git):

% git grep 'resolvelinks()'
sage:resolvelinks() {
src/bin/sage:resolvelinks() {
src/bin/sage-env:resolvelinks() {

The last one should probably have a comment in line with the first two.


On Thursday, April 14, 2022 at 4:55:08 PM UTC-7 hohoa...@gmail.com wrote:

> Hi,
>
> 
> Personally, I would rather see the time spent investigating whether or
> not we truly need the symlink-free path in the instances where
> resolvelinks() is currently used. I would guess not -- that there is a
> better solution to whatever other problem prompted the resolvelinks()
> function. But I don't know what that problem was. And to remove the
> function and "see what happens" would be committing yourself to
> answering bug reports from weird sage installs for the next twelve
> months.
> 
>
> Now your concern is truly appreciated.
>
>  "Find in File" in "Visual Studio Code" reveals duplications in* 24 files 
> in 13 directories* (please find the results appended below)
>
> It is amazing that SageMath is still maintainable up to now,  release 9.6
> Maybe 'resolvelinks' is just  the tip of an iceberg (something more 
> important is missing?)
>
> Best wishes,
>
> phiho
>
> *# Query: resolvelinks()*
> # ContextLines: 1
>
> 24 results - 24 files
>
> sage/sage:
>   32  # meantime however the two should be kept synchronized.
>   33: resolvelinks() {
>   34  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/build/pkgs/sagelib/src/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/build/pkgs/sagelib/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/build/pkgs/sagemath_categories/src/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/build/pkgs/sagemath_categories/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/build/pkgs/sagemath_objects/src/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/build/pkgs/sagemath_objects/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagelib/src/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagelib/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagelib/src/build/scripts-3.10/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagelib/src/build/scripts-3.10/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagemath_categories/src/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagemath_categories/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagemath_objects/src/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: resolvelinks() {
>   6  # $in is what still needs to be converted (normally has no 
> starting slash)
>
>
> sage/pkgs/sage-conf_pypi/sage_root/build/pkgs/sagemath_objects/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/pkgs/sage-conf_pypi/sage_root/src/bin/sage-env:
>   35  #
>   36: resolvelinks() {
>   37  # $in is what still needs to be converted (normally has no 
> starting slash)
>
> sage/pkgs/sagemath-categories/bin/sage:
>   4  # the top-level "sage" script. Please keep them synchronized.
>   5: 

Re: [Evolution] Evolution 3.44.0-1 not showing message contents

[Dr. John H. Lauterbach]

On Fri, 2022-04-08 at 07:18 +0200, Milan Crha via evolution-list wrote:
> On Thu, 2022-04-07 at 20:23 -0400, Dr. John H. Lauterbach wrote:
> > I just set up another PC and OS (Ubuntu 22.04) installed Evolution
> > 3.44.0-1.  It loads the email from my various IMAP accounts but will
> > not show message contents.  Moreover, it will not let me insert text
> > in a new email message.
> 
> Hi,
> it depends. Could you run Evolution from a terminal and see whether it
> prints any runtime warning there, please? I suppose you see an error
> message in the Evolution GUI too, you only did not provide it here for
> some reason; maybe?
> 
> Both parts you name are using WebKitGTK, thus the problem is likely
> with it.
> 
> I guess, and only guess, what you see is related to the recent threads:
> https://mail.gnome.org/archives/evolution-list/2022-March/msg00096.html
> https://mail.gnome.org/archives/evolution-list/2022-March/msg00042.html
> 
> You can also try to run Evolution from a terminal as:
> 
>    $ WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
> 
> to see whether it'll help with anything.
> Bye,
> Milan

Hello Milan.  Thank you for your help.  Your suggestion worked.

There were no error messages associated with the problem I reported yesterday.

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-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Evolution] Evolution 3.44.0-1 not showing message contents

[Dr. John H. Lauterbach]

I just set up another PC and OS (Ubuntu 22.04) installed Evolution 3.44.0-1.  It
loads the email from my various IMAP accounts but will not show message 
contents.
 Moreover, it will not let me insert text in a new email message.

All related Evolution preferences are the same as they are on version I am using
(3.40.4-1ubuntu2 ) to compose this message.

Is this a known problem?

Thank you,

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-release] Re: Sage 9.6.beta7 released

[John H Palmieri]

Quick work, thanks!

On Wednesday, April 6, 2022 at 12:33:08 PM UTC-7 arojas wrote:

> https://trac.sagemath.org/ticket/33647
>
> El miércoles, 6 de abril de 2022 a las 21:23:05 UTC+2, John H Palmieri 
> escribió:
>
>> I'm getting a doctest failure (OS X, iMac Pro):
>>
>> sage -t --random-seed=282087015394155253226119703033530733169 
>> src/sage/libs/pari/tests.py
>> **
>> File "src/sage/libs/pari/tests.py", line 786, in sage.libs.pari.tests
>> Failed example:
>> pari('x+O(x^8)').cosh()
>> Expected:
>> 1 + 1/2*x^2 + 1/24*x^4 + 1/720*x^6 + O(x^8)
>> Got:
>> 1 + 1/2*x^2 + 1/24*x^4 + 1/720*x^6 + 1/40320*x^8 + O(x^9)
>> **
>>
>> This is using pari from homebrew, pari updated this morning to version 
>> 2.13.4.
>>
>> On Saturday, April 2, 2022 at 12:12:48 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
>>>
>>> 78bfb6c7ad (tag: 9.6.beta7, trac/develop) Updated SageMath version to 
>>> 9.6.beta7
>>> 199ee74bdd Trac #33563: fix some tests of emptiness
>>> 596c5ebe69 Trac #33552: adjust error messages in toric/
>>> 36ffa34de1 Trac #33551: various details in pyx files
>>> b9c0c5cb3e Trac #33545: fix W391 in rings
>>> 160a503a46 Trac #33539: sage.manifolds, sage.tensor: Fix spelling errors
>>> 26c9c81022 Trac #33519: fix indentation in integration.pyx
>>> 6312320fb8 Trac #33517: fix W391 in categories
>>> eb33795b51 Trac #33516: fix W391 in schemes
>>> 2258189a8d Trac #33510: clean build/sage_bootstrap
>>> 23ac99956a Trac #33506: spaces around some % in combinat/
>>> 5b4fe73af3 Trac #33503: adjust a few more error messages
>>> aba82b3e94 Trac #33422: Bug in equivalence_decomposition of inductive 
>>> valuation
>>> f516aabdee Trac #33400: Add pictures to various 3d graphics manual pages
>>> f4a39b12e3 Trac #29775: Add a bit of typing to manifold code
>>> a45aa86091 Trac #33604: Remove random_DAG from global namespace
>>> c55624e4dc Trac #33603: Fix Conic doctests
>>> 76167599cc Trac #33602: Deprecate the import of some element classes in 
>>> sage/ring/all.py
>>> 9b8d0ef4f1 Trac #33595: fix indentation (E111) in some pyx files, mostly 
>>> in rings/
>>> aa11173798 Trac #33594: fix W391 in manifolds, geometry and graphs
>>> 4a8c685227 Trac #33583: Move integration and volume to Polyhedron_base7
>>> 8f750d97b3 Trac #33581: small cleanup for mathics.py
>>> a79b1b8baa Trac #33573: extend method cores to accept graphs with 
>>> multiple edges
>>> 9543d076d5 Trac #33570: Add CONTRIBUTING.md to the repository
>>> 86d9846846 Trac #33569: Speed up methods allow_multiple_edges and 
>>>  multiple_edges
>>> 08a942330a Trac #33507: sagemath_doc_html: Use jupyter-sphinx for 3D 
>>> graphics
>>> 3dd4e6b470 Trac #33568: Add method `is_integral_domain` for polynomial 
>>> quotient rings
>>> 76d0d33770 Trac #33567: finer category for cubic braid group quotients
>>> 328de7a17c Trac #33564: add one test in TestSuite of Coxeter groups
>>> 08854a8167 Trac #33559: Fix bug in 
>>> sage.graphs.graph_coloring.vertex_coloring
>>> 1762a6ca6d Trac #33558: get rid of __nonzero__ and use __bool__ instead
>>> fbc8bd05e9 Trac #33555: refresh the file subword.py
>>> 42a088a131 Trac #33553: README Build from Source: m4 (step 5) is needed 
>>> to run `make configure` (step 3)
>>> ce74d3217f Trac #33540: remove class inheritance of object in combinat
>>> d8f2ce96a0 Trac #33538: More doctests fix in sage_docbuild
>>> a5446dbaa4 Trac #33536: Some changes suggested by lgtm
>>> b9cdb7c713 Trac #33529: Remove old thebe package
>>> 211da0e7d1 Trac #33214: Vélu isogeny formulas use incorrect a-invariants 
>>> when pre-isomorphism is set
>>> 64bd36ebc8 Trac #32687: error in height difference bound
>>> f6ce4103f3 Trac #8784: remove quit_sage() command from all.py top level
>>> 3c6f5086b7 Trac #33585: doctest failure when doc html not 
>>> built/installed but sphinx is available in PYTHONPATH
>>> afa0d9633b Trac #33584: Adapt Mathics interface to SymPy upgrade from 
>>> 1.8 to 1.10 (resp.1.9)
>>> 58bf1ba6bb Trac #33520: scipy, networkx: Update install-requires.txt
&

[sage-release] Re: Sage 9.6.beta7 released

[John H Palmieri]

I'm getting a doctest failure (OS X, iMac Pro):

sage -t --random-seed=282087015394155253226119703033530733169 
src/sage/libs/pari/tests.py
**
File "src/sage/libs/pari/tests.py", line 786, in sage.libs.pari.tests
Failed example:
pari('x+O(x^8)').cosh()
Expected:
1 + 1/2*x^2 + 1/24*x^4 + 1/720*x^6 + O(x^8)
Got:
1 + 1/2*x^2 + 1/24*x^4 + 1/720*x^6 + 1/40320*x^8 + O(x^9)
**

This is using pari from homebrew, pari updated this morning to version 
2.13.4.

On Saturday, April 2, 2022 at 12:12:48 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
>
> 78bfb6c7ad (tag: 9.6.beta7, trac/develop) Updated SageMath version to 
> 9.6.beta7
> 199ee74bdd Trac #33563: fix some tests of emptiness
> 596c5ebe69 Trac #33552: adjust error messages in toric/
> 36ffa34de1 Trac #33551: various details in pyx files
> b9c0c5cb3e Trac #33545: fix W391 in rings
> 160a503a46 Trac #33539: sage.manifolds, sage.tensor: Fix spelling errors
> 26c9c81022 Trac #33519: fix indentation in integration.pyx
> 6312320fb8 Trac #33517: fix W391 in categories
> eb33795b51 Trac #33516: fix W391 in schemes
> 2258189a8d Trac #33510: clean build/sage_bootstrap
> 23ac99956a Trac #33506: spaces around some % in combinat/
> 5b4fe73af3 Trac #33503: adjust a few more error messages
> aba82b3e94 Trac #33422: Bug in equivalence_decomposition of inductive 
> valuation
> f516aabdee Trac #33400: Add pictures to various 3d graphics manual pages
> f4a39b12e3 Trac #29775: Add a bit of typing to manifold code
> a45aa86091 Trac #33604: Remove random_DAG from global namespace
> c55624e4dc Trac #33603: Fix Conic doctests
> 76167599cc Trac #33602: Deprecate the import of some element classes in 
> sage/ring/all.py
> 9b8d0ef4f1 Trac #33595: fix indentation (E111) in some pyx files, mostly 
> in rings/
> aa11173798 Trac #33594: fix W391 in manifolds, geometry and graphs
> 4a8c685227 Trac #33583: Move integration and volume to Polyhedron_base7
> 8f750d97b3 Trac #33581: small cleanup for mathics.py
> a79b1b8baa Trac #33573: extend method cores to accept graphs with multiple 
> edges
> 9543d076d5 Trac #33570: Add CONTRIBUTING.md to the repository
> 86d9846846 Trac #33569: Speed up methods allow_multiple_edges and 
>  multiple_edges
> 08a942330a Trac #33507: sagemath_doc_html: Use jupyter-sphinx for 3D 
> graphics
> 3dd4e6b470 Trac #33568: Add method `is_integral_domain` for polynomial 
> quotient rings
> 76d0d33770 Trac #33567: finer category for cubic braid group quotients
> 328de7a17c Trac #33564: add one test in TestSuite of Coxeter groups
> 08854a8167 Trac #33559: Fix bug in 
> sage.graphs.graph_coloring.vertex_coloring
> 1762a6ca6d Trac #33558: get rid of __nonzero__ and use __bool__ instead
> fbc8bd05e9 Trac #33555: refresh the file subword.py
> 42a088a131 Trac #33553: README Build from Source: m4 (step 5) is needed to 
> run `make configure` (step 3)
> ce74d3217f Trac #33540: remove class inheritance of object in combinat
> d8f2ce96a0 Trac #33538: More doctests fix in sage_docbuild
> a5446dbaa4 Trac #33536: Some changes suggested by lgtm
> b9cdb7c713 Trac #33529: Remove old thebe package
> 211da0e7d1 Trac #33214: Vélu isogeny formulas use incorrect a-invariants 
> when pre-isomorphism is set
> 64bd36ebc8 Trac #32687: error in height difference bound
> f6ce4103f3 Trac #8784: remove quit_sage() command from all.py top level
> 3c6f5086b7 Trac #33585: doctest failure when doc html not built/installed 
> but sphinx is available in PYTHONPATH
> afa0d9633b Trac #33584: Adapt Mathics interface to SymPy upgrade from 1.8 
> to 1.10 (resp.1.9)
> 58bf1ba6bb Trac #33520: scipy, networkx: Update install-requires.txt
> d20cc4945d Trac #33139: Fix sagemath_doc_html build failure on Cygwin
> e39a3a2736 Trac #31924: sage -t: Do not run pytest on individual Python 
> files unless they match the pytest file pattern
> a275e1f383 Trac #33607: jupyterlab: Use jupyterlab-server < 2.11
> 949bb36dd0 Trac #33523: Fix crosslinks in algebras catalog
> e3fce642a0 Trac #33469: %matplotlib widget does not work in the scope of 
> %display latex
> baf6b19517 Trac #33443: slow doctest improvements (isogeny_small_degree, 
> function_field, doctest/test.py)
> b11471b30b Trac #33393: Implement Krawtchouk, Meixner, and Hahn polynomials
> a54d7ce44a Trac #33114: Feature.require vs. is_present, is_functional
> c399fc096b Trac #32364: every quaternion lies in every quaternion order
> 5166ac1413 Trac #20343: Add file `sage/misc/latex_standalone.py` and class 
> `TikzPicture`
> 0991f82d57 Trac #33547: Update sympy to 1.10.1
> 0d0bb77fb2 Trac #33508: OpenSSL 3.0.2 security update
> 56d233b1f6 Trac #33227: SystemError: calling remove_from_pari_stack() 
> inside sig_on() in expression.pyx
> 43474c96d5 (tag: 

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

[John H Palmieri]

I don't see it at any of the mirrors yet...

On Sunday, March 27, 2022 at 11:03:35 AM UTC-7 Volker Braun wrote:

> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> 43474c96d5 (tag: 9.6.beta6, trac/develop) Updated SageMath version to 
> 9.6.beta6
> f43e375fb5 Trac #33505: partial pep8 cleanup in arith/misc.py
> 8a3ece590f Trac #33502: various small details in code formatting
> cbd71f5148 Trac #33491: fix usage of Matplotlib color maps
> 29f7b5ab37 Trac #33451: Change "hasattr(x, '__call__')" to "callable(x)" 
> etc
> 5b015213e7 Trac #33122: add torsion_subgroup() method to 
> AdditiveAbelianGroupWrapper
> 87a2e5724f Trac #32207: homebrew  llvm / clang - followup to #30835
> 9d867e2bc8 Trac #33541: some more precise unittest assert
> fef33af293 Trac #33535: get rid of #py2 outside of explain_pickle
> d88ed13837 Trac #33526: igraph, python_igraph: Upgrade, fix system package 
> version check, fix dependencies
> 9906dcdaa6 Trac #33525: modernize coercion in monsky_washnitzer.py
> 2b4757d8a1 Trac #33524: fix indentation E111 in some pyx files
> 6adda63733 Trac #33518: crystals.TensorProduct does not respect super 
> crystals
> 8aec9c744b Trac #33515: fix W391 in modular
> 26574b0f82 Trac #33512: Update python3 to 3.10.3
> 7a7956dd66 Trac #33511: more precise asserts in convex_sets
> 86b1833506 Trac #33504: sage.graphs, sage.numerical.mip: Remove 
> unnecessary uses of set_binary, set_integer
> 822f4d0668 Trac #33501: Get rid of sqrt in spherical harmonics
> 438d5f8d8c Trac #33500: fix and activate pycodestyle E111
> 6d7ed571fd Trac #33498: Fix random order of cubic braid group elements
> 41a6910dae Trac #33496: Adjust doctest for interrupting large 
> multiplication
> e419b25d9d Trac #33495: Fix tests with networkx 2.7
> 2345381772 <(234)%20538-1772> Trac #33494: bitset_intrinsics.h: Fix 
> "expression result unused" warning
> cedd9bbb57 Trac #33492: make sure "real" gcc is rejected on macOS
> 0444bcabf6 Trac #33482: Improve variable declaration and naming of 
> localization of integral domains
> fd656d14c5 Trac #33456: GH Actions: Re-add pyright check
> 53ca6151f2 Trac #32385: Compute the Bergman and augmented Bergman complex 
> of a matroid
> 6dbf0930e7 Trac #30845: Fixes for the conda-for-Sage-developers 
> installation method, add GH Actions workflow
> 95307a68b5 Trac #33522: pythran: Update to 0.11.0
> 3afe1c712a Trac #33440: sage.libs.singular: Do not fail if the Singular 
> binary is not in PATH
> 3cc2873986 Trac #33437: Add Lehrer-Solomon symmetric function
> 6e77b3fd5b Trac #33416: Colormaps and contours for complex_plot
> a636498287 Trac #33407: sage -t --installed
> ff2baed67c Trac #33396: removing some useless ...: in the doc
> dce5f06cf9 Trac #33233: sage -t --baseline-stats-path
> f06a7f845e Trac #33170: Update doctests for compatibility with ipython 8.x
> 2fbf359176 Trac #33156: fix wrong results & huge slowdown due to broken 
> caching in .multiplication_by_m()
> b8d91ace4f Trac #33141: Fix doctests in sage_setup and sage_docbuild for 
> sage-on-distribution
> f30a4c8b06 Trac #32942: Introduce `align_latex` option that allows latex 
> displays aligned left or centered
> 39de62bca0 Trac #32429: Typos
> d79b00d98a Trac #30078: Check for duplicate hyperplanes in arrangements 
> over any base ring
> a633cce6f8 Trac #33532: Doctest failure when SAGE_LIB doesn't match 
> `.../site-packages`
> 9873ee5a57 Trac #33361: configure: Handle the case of SAGE_LOCAL = a 
> system directory with gcc better
> dc311dcd82 Trac #32975: Improve doctest interaction with pytest
> 0e4f121222 Trac #33471: Add pictures to various 2d graphics manual pages
> 5b20998e56 Trac #33487: Package CyLP
> df50acb8cc Trac #33477: Conversion problem between multivariate Laurent 
> polynomial ring and its field of fraction
> 3c80055420 Trac #33475: deTeX document titles of sage documentation
> 5b872c9d08 Trac #30717: add "How to cite SageMath" to FAQ
> a61c15ecd6 Trac #29631: spkg-configure.m4 for linbox
> 55a711e3d6 (tag: 9.6.beta5) Updated SageMath version to 9.6.beta5
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/7644ef75-d32c-47b8-8f4d-30b8f5ab9d37n%40googlegroups.com.

[sage-devel] Re: Cannot compile sage on macosx 12.3

[John H Palmieri]

config.log shows lots of errors of the form

ld: warning: directory not found for option '-L/opt/homebrew/opt/lib'

I wonder if .homebrew-build-env is producing the wrong information as 
compared to your homebrew installation. Where are homebrew's libraries 
actually installed, if not in /opt/homebrew/opt/lib? Sage should not have 
to build openblas if it's already installed via homebrew.

-- 
John


On Monday, March 21, 2022 at 3:54:55 AM UTC-7 Andrew wrote:

> Thanks. I'll try that!
> Andrew
>
> On Monday, 21 March 2022 at 7:54:19 pm UTC+11 Kwankyu Lee wrote:
>
>> This occurred to me from time to time, I just do "sage -i openblas" and 
>> "make" again. 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f17a300b-c1f1-4751-a92c-5f22f82e3008n%40googlegroups.com.

[sage-support] Re: OS X 12.3 intel: scipy fails to build

[John H Palmieri]

"./sage -pip install -U pythran" seems to have worked. I checked Sage's 
pythran log and didn't see anything suspicious, for what that's worth.

On Thursday, March 17, 2022 at 2:34:56 PM UTC-7 Matthias Koeppe wrote:

> It would be worth checking whether "./sage -pip install -U pythran" or 
> "./sage -pip install -U git+https://github.com/serge-sans-paille/pythran; 
> fixes this issue
>
> On Thursday, March 17, 2022 at 2:01:49 PM UTC-7 John H Palmieri wrote:
>
>> Since upgrading to OS X 12.3 a few days ago, along with the corresponding 
>> Xcode and command line tools, I have been unable to build scipy. The end of 
>> the log file says
>>
>>   Building wheel for scipy (pyproject.toml): finished with status 'error'
>>   ERROR: Failed building wheel for scipy
>>
>> A little before that:
>>
>>   
>> /Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.6.beta5/local/var/lib/sage/venv-python3.10.2/lib/python3.10/site-packages/pythran/pythonic/types/str.hpp:417:12:
>>  
>> error: no matching constructor for initialization of 'typename 
>> str::reverse_iterator' (aka 'reverse_iterator<(anonymous 
>> namespace)::pythonic::types::string_iterator>')
>>   return {data->rend()};
>>  ^~
>>
>> Log files attached. I've tried this using all of my installed homebrew 
>> packages and also using (as you can see in config.log) 
>> "--with-system-python3=no", same result either way. Any suggestions?
>>
>> -- 
>> John
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/ab5310b6-e8ce-41dd-8b20-0124dd99092dn%40googlegroups.com.

[RBW] Re: FS: Crust Towel Rack Bars

[John H.]

The bars have been sold.

On Wednesday, March 16, 2022 at 6:28:37 PM UTC-4 John H. wrote:

> Hey Bunch -- These Crust Towel Rack bars didn't work for me. Maybe they'll 
> work for someone out there.
>
> Silver 600mm (narrowest version), like new (>10 miles), Latest generation, 
> shown here <https://crustbikes.com/products/towel-rack-bar>
>
>
> $100 shipped CONUS. 
> $90 for local (Boston Metro) pickup
>
> Local pickup preferred. Picture below.
>
> -John
> Cambridge
>
> [image: IMG_2789.jpg]
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/040ce6fe-bfb0-4fa4-b7c3-14f4dc6205e5n%40googlegroups.com.

[sage-devel] Re: Questions about what directory and files are safe to delete.

[John H Palmieri]

In theory you should be able to run "make micro_release". According to the 
comment in Makefile, this will "Remove everything that is not necessary to 
run Sage and pass all its doctests." I say "in theory" because I haven't 
personally tried it and I don't know if it's regularly tested by anyone. If 
you're willing to start from scratch if things are broken, then it's worth 
trying.

-- 
John


On Tuesday, March 8, 2022 at 11:50:01 AM UTC-8 Ethan Lin wrote:

> Hello! I have a question concerning what is safe to delete after make.
> After make I was informed with this message.
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> WARNING: If you now run 'make' again, the build directory of the
> same version of the package will, by default, be deleted. Set the
> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
> What is safe to delete? And what are the paths to them?
> I started to remove the /logs/pkgs log files... then I wasn't 
> sure if that was the correct directory...
> Cheers!
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e6189124-f40a-4e45-ae42-815328299e16n%40googlegroups.com.

Re: [sage-support] Re: Basic Stats deprecated?

[John H Palmieri]

Should there be a small list of functions which we import automatically? 
For example in sage.all we could do: "from numpy import mean, median". It 
seems strange to not have a top-level "mean" or "median" function, given 
all of the other esoteric top-level functions.


On Friday, February 25, 2022 at 10:28:17 PM UTC-8 Matthias Koeppe wrote:

> On Friday, February 25, 2022 at 8:32:39 PM UTC-8 wst...@gmail.com wrote:
>
>> Also, if you want to argue that users should explicitly import 
>> everything...
>
>
> No, that's not what I'm arguing. 
>
> The deprecation of the basic_stats module happened because Sage has 
> nothing to offer in this area;
> it's a module with 5 functions that hasn't seen development since 2009. 
> Underdeveloped modules like this reflect poorly on the rest of Sage.
>
> It's a disservice to learners to offer these facilities of Sage as the 
> standard vocabulary of doing basic stats on the computer.
> They will be better off with virtually any other solution: With the 
> built-in stats module of Python; with Numpy/SciPy; with Pandas; with R.
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/ad50aa77-c5fc-4b6d-8b2b-c364518b83bcn%40googlegroups.com.

[sage-devel] Re: Question about some Sage scripts

[John H Palmieri]

Thanks.

I've always kind of hated this construction/obfuscation of script names, 
because it makes it harder to find out where and how they are used. But 
presumably it has its uses.

On Wednesday, February 23, 2022 at 6:17:21 PM UTC-8 Matthias Koeppe wrote:

> On Wednesday, February 23, 2022 at 2:21:08 PM UTC-8 John H Palmieri wrote:
>
>> I have questions about some of the scripts in src/bin:
>>
>
>>- sage-native-execute: looks like a no-op. Delete?
>>- sage-open — used in OS X; can we just use "open"?
>>
>> Yes on both of these. They have not been needed since Sage stopped 
> setting LD_LIBRARY_PATH (or its defunct equivalent on macOS).
>
>>
>>- sage-rebase* — used on Cygwin only: move to build/bin?
>>
>> On Cygwin, users also may need to run this after using "sage -pip install 
> ...", so I'd suggest to keep it in src/bin
>
>>
>>- sage-venv-config — where is this used? `git grep sage-venv-config` 
>>doesn't reveal much.
>>
>> "git grep venv-config" reveals that it is called by the installed sage 
> script. (The name of the script is constructed from $0.)
> Its only function at the moment is to determine SAGE_VENV, which is then 
> used by sage-env.
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1df7aeea-940b-4b77-b5f7-b569b673c141n%40googlegroups.com.

[sage-devel] Question about some Sage scripts

[John H Palmieri]

I have questions about some of the scripts in src/bin:

   - math-readline — used sometimes in Sage's mathematica interface. Is it 
   necessary?
   - sage-inline-fortran — does anyone use this?
   - sage-native-execute: looks like a no-op. Delete?
   - sage-open — used in OS X; can we just use "open"?
   - sage-rebase* — used on Cygwin only: move to build/bin?
   - sage-cachegrind, sage-callgrind, sage-massif, sage-omega, 
   sage-valgrind — do people use these?
   - sage-venv-config — where is this used? `git grep sage-venv-config` 
   doesn't reveal much.
   - sage-location, sage-update-src: in the process of being removed already

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7618d17d-9dcf-4ab1-a84e-b5fbbb8d5a62n%40googlegroups.com.

[sage-support] Re: Tensor Multiprocessing broken. SageMath 9.5 on Apple Mac OSX 12.1 . SageMath-9.5_x86_64

[John H Palmieri]

Are you using OS X? Could this possibly be due to how Python handles 
multiprocessing on OS X vs. other platforms? (See 
https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods,
 
in particular the comment "On macOS, the *spawn* start method is now the 
default" and https://bugs.python.org/issue33725.)



On Tuesday, January 25, 2022 at 12:34:07 PM UTC-8 alan_thoma...@yahoo.co.uk 
wrote:

> Process SpawnPoolWorker-1: Traceback (most recent call last): File 
> "/private/var/tmp/sage-9.5-current/local/var/lib/sage/venv-python3.9.9/lib/python3.9/multiprocessing/process.py",
>  
> line 315, in _bootstrap self.run() File 
> "/private/var/tmp/sage-9.5-current/local/var/lib/sage/venv-python3.9.9/lib/python3.9/multiprocessing/process.py",
>  
> line 108, in run self._target(*self._args, **self._kwargs) File 
> "/private/var/tmp/sage-9.5-current/local/var/lib/sage/venv-python3.9.9/lib/python3.9/multiprocessing/pool.py",
>  
> line 114, in worker task = get() File 
> "/private/var/tmp/sage-9.5-current/local/var/lib/sage/venv-python3.9.9/lib/python3.9/multiprocessing/queues.py",
>  
> line 368, in get return _ForkingPickler.loads(res) File 
> "/private/var/tmp/sage-9.5-current/local/var/lib/sage/venv-python3.9.9/lib/python3.9/site-packages/sage/manifolds/differentiable/chart.py",
>  
> line 36, in 
> On Tuesday, January 25, 2022 at 8:13:20 PM UTC egourg...@gmail.com wrote:
>
>> Hi,
>>
>> Le mardi 25 janvier 2022 à 12:54:57 UTC+1, alan_thoma...@yahoo.co.uk a 
>> écrit :
>>
>>> I get errors in this notebook if I set the variable tpar to any value 
>>> greater than one. (Number of Tensor processing cores.)
>>>
>>> *http://alan.atstafford.co.uk/Sage9.5Problem.ipynb 
>>> *
>>>
>>
>> Your notebook works well with tpar=4 on my Ubuntu computer running Sage 
>> 9.5.rc4.
>> What kind of error do you get?
>>
>> Eric.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/4e5362fc-05b2-48ac-9783-66e6e70d6f21n%40googlegroups.com.

Re: Plessy core memory - UNIBOne Info

[John H. Reinhardt via cctalk]

You can contact Joerg at his site http://retrocmp.com/contact  For email see 
the UNIBone - Get One Page 
http://retrocmp.com/projects/unibone/283-unibone-getting-one

A fellow on the VCF DEC forum tried to contact Joerg about a UNIBone recently 
and said he had better luck using the contact page on the web site.  You can 
also take a look a the Google Group for the UNIBone and the QBone (QBus 
version).

If you're not phased by CPL programming and surface mount IC then I'd say go 
for the board from Todd (I've bought boards from him before, he's good).  If 
not then you might want a kit from Joerg. The Get One page lists kits for €170 
or assembled for €260.  In either case you have to supply your own Beaglebone 
Black though Joerg might still have some for €60.  I bought an assembled QBone 
and then later two QBone kits form Joerg.  His work is also good. I just 
finished one QBone kit (assembly - testing is to come) and it went well but the 
kit board (both QBone and UNIBone) come with all SMD items installed and the 
two CPL's programmed so is mostly easy through-hole soldering.  The trickiest 
part is the connection for the BBB.

Here are the build instructions - 
http://retrocmp.com/projects/unibone/286-unibone-building

--

John H. Reinhardt

On 1/10/2022 1:43 PM, Chris Zach via cctalk wrote:

Hm. That is an idea. Technically I'm just wanting to get the thing working to 
see if it works, so a Unibone would be reasonable. Now where do I buy one/a 
kit/whatever.

C


On 1/10/2022 10:46 AM, Jay Logue via cctalk wrote:

On 1/9/2022 7:59 PM, Chris Zach via cctalk wrote:

*nod* I'll put the system aside again for awhile. But if I come across a DD11-C 
or D I'll go back to work on it.


I understand your frustration, as I've spent the better part of a year 
acquiring and fixing an ME11-L and associated board sets trying to get my 
short-box 11/05 up to a full compliment of memory.

Perhaps you've already considered this, but an alternative that just makes the problem 
"go away" is to get yourself a Unibone. Not period correct (and not core, which 
is what motivates me), but super useful and can emulate as much memory as you need.

--Jay

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

[John H Palmieri]

I think Samuel is correct and #32868 will fix it. I was not running 
./bootstrap with a fresh tarball, and I'm glad that with the fix, I will be 
able to continue not running it. (I think that './configure; make' should 
be sufficient. I have 'source .homebrew-build-env' in my .profile, so I 
don't have to worry about that.)

  John


On Wednesday, January 5, 2022 at 3:10:32 AM UTC-8 david@gmail.com wrote:

> I have not experienced what you report. On macOS 10.15.7, I’m always doing:
> ./bootstrap 
> source .homebrew-build-env
> ./configure
> make 
>
> Best,
> David.
>
> Le 5 janv. 2022 à 05:10, John H Palmieri  a écrit :
>
> I am having intermittent problems building Sage on OS X from a fresh 
> tarball: it's worked sometimes, failed others. When it fails, it seems to 
> be because there is no script "sage" in venv/bin. (There may be other 
> problems, too, but this one is a major symptom.) I think this is the 
> pattern: if I take a fresh tarball, run ./configure and make, it fails. If 
> I instead run ./bootstrap then ./configure then make, it succeeds. Any 
> ideas what's going on? Has anyone else seen this?
>
>   John
>
> On Wednesday, December 29, 2021 at 3:39:39 AM UTC-8 axio...@yahoo.de 
> wrote:
>
>> The findstat failure is, unfortunately, an upstream problem, which I 
>> cannot fix myself.  Currently, the depth parameter is ignored in map 
>> queries.  I notified the person that is hopefully able to fix it.
>>
>> On Wednesday, 29 December 2021 at 11:38:41 UTC+1 Sébastien Labbé wrote:
>>
>>> On Ubuntu 20.04, make build works fine and running tests with few 
>>> optional and external packages I get:
>>>
>>> Using 
>>> --optional=4ti2,bliss,build,cbc,ccache,cryptominisat,database_symbolic_data,debian,debugpy,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,rubiks,sage,sage_numerical_backends_coin,sage_spkg
>>> Features to be detected: 
>>> 4ti2,benzene,bliss,buckygen,conway_polynomials,cplex,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,gurobi,imagemagick,internet,jupymake,kenzo,latex,latex_package_tkz_graph,latte_int,lrslib,lualatex,macaulay2,magma,maple,mathematica,matlab,mcqd,meataxe,octave,pandoc,pdf2svg,pdflatex,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,scilab,tdlib,xelatex
>>>
>>> [...]
>>>
>>> --
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/sage/databases/findstat.py  # 2 doctests failed
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/sage/databases/oeis.py  # 1 doctest failed
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/sage/interfaces/octave.py  # 3 doctests failed
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/sage/sat/boolean_polynomials.py  # 1 doctest failed
>>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>>> src/sage/tests/cmdline.py  # 1 doctest failed
>>> --
>>> Features detected for doctesting: 
>>> dvipng,ffmpeg,graphviz,imagemagick,internet,latex,latex_package_tkz_graph,lualatex,octave,pandoc,pdf2svg,pdflatex,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,xelatex
>>>
>>> Rerunning failed tests, the issue with boolean_polynomials.py does not 
>>> reappear:
>>>
>>> --
>>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>>> src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
>>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>>> src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
>>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>>> src/sage/databases/findstat.py  # 2 doctests failed
>>> sage -t --long --random-seed=30

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

[John H Palmieri]

I am having intermittent problems building Sage on OS X from a fresh 
tarball: it's worked sometimes, failed others. When it fails, it seems to 
be because there is no script "sage" in venv/bin. (There may be other 
problems, too, but this one is a major symptom.) I think this is the 
pattern: if I take a fresh tarball, run ./configure and make, it fails. If 
I instead run ./bootstrap then ./configure then make, it succeeds. Any 
ideas what's going on? Has anyone else seen this?

  John

On Wednesday, December 29, 2021 at 3:39:39 AM UTC-8 axio...@yahoo.de wrote:

> The findstat failure is, unfortunately, an upstream problem, which I 
> cannot fix myself.  Currently, the depth parameter is ignored in map 
> queries.  I notified the person that is hopefully able to fix it.
>
> On Wednesday, 29 December 2021 at 11:38:41 UTC+1 Sébastien Labbé wrote:
>
>> On Ubuntu 20.04, make build works fine and running tests with few 
>> optional and external packages I get:
>>
>> Using 
>> --optional=4ti2,bliss,build,cbc,ccache,cryptominisat,database_symbolic_data,debian,debugpy,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,rubiks,sage,sage_numerical_backends_coin,sage_spkg
>> Features to be detected: 
>> 4ti2,benzene,bliss,buckygen,conway_polynomials,cplex,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,gurobi,imagemagick,internet,jupymake,kenzo,latex,latex_package_tkz_graph,latte_int,lrslib,lualatex,macaulay2,magma,maple,mathematica,matlab,mcqd,meataxe,octave,pandoc,pdf2svg,pdflatex,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,scilab,tdlib,xelatex
>>
>> [...]
>>
>> --
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/sage/databases/findstat.py  # 2 doctests failed
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/sage/databases/oeis.py  # 1 doctest failed
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/sage/interfaces/octave.py  # 3 doctests failed
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/sage/sat/boolean_polynomials.py  # 1 doctest failed
>> sage -t --long --random-seed=40537233215386142174776538763210859962 
>> src/sage/tests/cmdline.py  # 1 doctest failed
>> --
>> Features detected for doctesting: 
>> dvipng,ffmpeg,graphviz,imagemagick,internet,latex,latex_package_tkz_graph,lualatex,octave,pandoc,pdf2svg,pdflatex,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,xelatex
>>
>> Rerunning failed tests, the issue with boolean_polynomials.py does not 
>> reappear:
>>
>> --
>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>> src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>> src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>> src/sage/databases/findstat.py  # 2 doctests failed
>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>> src/sage/databases/oeis.py  # 1 doctest failed
>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>> src/sage/interfaces/octave.py  # 3 doctests failed
>> sage -t --long --random-seed=300887881046897568887396291869982609842 
>> src/sage/tests/cmdline.py  # 1 doctest failed
>> --
>> Features detected for doctesting: internet,octave,pandoc
>>
>> The failures with linear_algebra.rst, coding_in_other.rst and octave.py 
>> are new to me and are all related to optional octave doctests. They are 
>> copied below. For comparison with other machines, the version of octave 
>> available on the system is:
>>
>> $ octave --version
>> GNU Octave, version 5.2.0
>> Copyright (C) 2020 John W. Eaton and others.
>> This is free software; see the source code for copying conditions.
>> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
>> FITNESS FOR A PARTICULAR PURPOSE.
>> Octave was configured for "x86_64-pc-linux-gnu".
>> Additional information about Octave is available at 
>> https://www.octave.org.
>> Please contribute if you find this 

Re: VAX 780 on eBay

[John H. Reinhardt via cctalk]

On 1/1/2022 1:10 PM, Jon Elson via cctalk wrote:

On 1/1/22 12:12 PM, Noel Chiappa via cctalk wrote:

This:

 https://www.ebay.com/itm/275084268137

The starting price is expensive, but probably not utterly unreasonable,
given that:


They don't have a front picture, but there is a rear picture of a TU-77/TU-78 
tape drive interior.

As for testing, the 780 came wired for 208/240 3 phase power, with a big 5-pin 
plug.

The CPU cabinet seems to have 2 Massbus controllers, I think. So, maybe there's 
a Massbus disk included.

Jon



In separate auctions they have a RM05 and a TU77

TU77: https://www.ebay.com/itm/275083502085 (The 11/780 is visible in the 
background of the first picture)
RM05: https://www.ebay.com/itm/284587865252

--

John H. Reinhardt

Re: VAX 780 on eBay

[John H. Reinhardt via cctalk]

On 1/1/2022 12:40 PM, Paul Koning via cctalk wrote:



On Jan 1, 2022, at 1:12 PM, Noel Chiappa via cctalk  
wrote:

This:

https://www.ebay.com/itm/275084268137

The starting price is expensive, but probably not utterly unreasonable,
given that:

- the 780 was the first VAX, and thus historically important

- 780's are incredibly rare; this is the first one I recall seeing for sale
  in the classic computer era (versus several -11/70's, /40s, etc)

- this one appears to be reasonably complete; no idea if all the key CPU
  boards are included, but it's things like the backplane, etc (all of which
  seem to be there) which would be completely impossible to find now - if any
  boards _are_ missing, there's at least the _hope_ that they can be located
  (780 boards seem to come by every so often on eBait), since people seem to
  keep boards, not realizing that without the other bits they are useless

Interesting, but the argument for why it's not tested is implausible which 
makes me very suspicious.  I suppose there might be a few American homes that  
have only 110 volt power, but I'm hard pressed to think of any I have ever 
seen, and that includes really old houses.

paul




Possibly part of the same installation they have:

TU77: https://www.ebay.com/itm/275083502085 (The 11/780 is visible in the 
background of the first picture)
RM05: https://www.ebay.com/itm/284587865252
LA120: https://www.ebay.com/itm/275084461044

Prices seem on the high end but not totally unreasonable.  There don't seem to 
be any RM05 packs included with the drive.

--
John H. Reinhardt

[sage-devel] Re: \Bold command definition in every LaTeX output

[John H Palmieri]

Sure, that sounds like a good idea.

- John

On Wednesday, December 22, 2021 at 3:05:44 AM UTC-8 Eric Gourgoulhon wrote:

> Le mercredi 22 décembre 2021 à 00:26:58 UTC+1, John H Palmieri a écrit :
>
>> I have no objection to this, but the purpose for using \Bold{...} was to 
>> make its behavior easily customizable, since some people might want 
>> \mathbf{...} and some might want \mathbb{...}. 
>>
>
> The customization could be performed at the Python level, instead of the 
> LaTeX one, e.g.  something like:
>
> def _latex_(self):
> return LatexExpr.bold_command() + r"{Q}"
>
> with bold_command() being a static method of LatexExpr that returns the 
> class attribute _bold_command. The latter would be initialized to 
> r"\mathbf" and could be customized by the end user thanks to some 
> static/class method of LatexExpr, e.g. 
>
> sage: LatexExpr.set_bold_command("mathbb")
>
> Eric.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/faf43380-4bb6-4d2d-8e38-255f1af00671n%40googlegroups.com.

[sage-devel] Re: \Bold command definition in every LaTeX output

[John H Palmieri]

I have no objection to this, but the purpose for using \Bold{...} was to 
make its behavior easily customizable, since some people might want 
\mathbf{...} and some might want \mathbb{...}. Are you suggesting replacing 
\Bold in the latex() method for the object, or keeping it but doing the 
redefinition as \mathbf using Python/Sphinx rather than in LaTeX?

-- 
John



On Tuesday, December 21, 2021 at 8:54:56 AM UTC-8 Matthias Koeppe wrote:

> On Tuesday, December 21, 2021 at 2:49:11 AM UTC-8 Eric Gourgoulhon wrote:
>
>> Unless there might be a reason for it, why not replacing lines like
>> return r"\Bold{Q}"
>> by
>> return r"\mathbf{Q}"
>> in the relevant  _latex_ methods ? 
>>
>
> +1
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b894b35c-d7f5-487a-8346-6d976dc24aa7n%40googlegroups.com.

[sage-devel] Re: First impressions on Sage 9.4 source build

[John H Palmieri]

On Friday, December 17, 2021 at 2:33:55 PM UTC-8 Randall wrote:

> Hi all:
>
> I am building sage version 9.4 from source on my OpenSuse Linux Leap 15.2 
> OS and like the install document stated, it has taken hours (using a HP 
> Z420 workstation with 6 Xeon processors) 
>
> I have noticed some odd things occurring which caught my attention as at 
> one time in my life I was in charge of 1+million line code handoff to 
> another company and our code had to be very high quality.
>
> Here's what caught my eye:
>
> 1. dozens of warnings during Cythonizing of comparing signed variables to 
> unsigned. This warning needs to be heeded and the code fixed
> 2. dozens of warnings of compares using uninitialized variables. It goes 
> without saying that using uninitialized variables is only asking for 
> trouble later on. These need to be fixed also.
> 3. hundreds of warnings during package compilation, the source code does 
> need improvement. I did notice that some C programmers were attempting to 
> write C++ code, but this is asking for trouble too. C++ is not advanced C, 
> despite the popular (mis) belief in this.
>
> I am attempting to install the optional packages just to see what happens, 
> for the build process, but it looks like bundling several packages (say x) 
> on the ./compile line is only asking for repeats of the whole compile run 
> x-times. It should be possible to install all on only one run, not x-runs.
>

Do you mean the "./configure" line? If you do "./configure --enable-qhull 
--enable-libsemigroups" at the start, then "make" should just increase the 
build time by whatever it takes for those two packages — it shouldn't 
repeat anything.

I have some questions here
>
> 1. Will "make all" build all the optional packages and avoid the 
> experimental?
> (I did NOT try make all, because just doing make itself chewed up about 9 
> hours time)
>

No, "make all" just builds the standard packages and the documentation.

9 hours seems way too long. Are you building in parallel (step 7 in 
https://doc.sagemath.org/html/en/installation/source.html#step-by-step-installation-procedure)?
 
That should speed things up. For instance it takes under an hour on my 2017 
iMac, not a super-fast machine, although it does use some system packages 
to avoid building time-consuming packages like gcc/gfortran.
 

>
> 2. I noticed that sage recommended several OpenSuse system packages on the 
> zypper install line, but I did run this and believe it or not, nothing was 
> available. Is there some consideration to creating a public mathematical 
> software repository where these OpenSuse packages are available? (This 
> probably needs to be extended to most of the public Linux systems)
>

We rely on package managers for the different linux systems to produce 
packages and then we use what's available. (Some Sage developers help with 
those packages.) I don't know how receptive OpenSuse would be to a 
repository of packages that they hadn't vetted; would they welcome this or 
view it suspiciously.

For the way we use packages now, see 
https://doc.sagemath.org/html/en/developer/packaging.html#allowing-for-the-use-of-system-packages
 
and for example build/pkgs/arb/distros/opensuse.txt.
 

> 3. Can the dochtml installer be decoupled from the regular install, and it 
> run optionally? It  takes up a lot of time for it to discover that 
> everything has already been installed.
>

Running "make build" will build the standard packages and not build the 
documentation.

 
-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ac46712f-4fa4-42fe-b972-f8fa70fa6b6dn%40googlegroups.com.

[sage-support] Re: LatexExpr

[John H Palmieri]

Or if you need single and double quotes, delimit the string with """ or ''' 
(three double-quotes or three single-quotes):

r"""here is "some" 'text' """

On Monday, November 29, 2021 at 11:07:21 AM UTC-8 slelievre wrote:

> 2021-11-29 18:05:58 UTC+1, Cyrille Piatecki:
> >
> > I often use LatexExpr(r'\text{blabla} x_i =') encapsulated
> > in show(). It's very easy to use but not if I need single quotes
> > as in "it's". Is there a way to escape the quotes?
>
> LatexExpr(r"\text{there's a way} x_i =")
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/ce3ddb95-05d2-46ae-9bfa-e4253527a997n%40googlegroups.com.

[sage-devel] Re: sage --install

[John H Palmieri]

Fixed in https://trac.sagemath.org/ticket/32885.

-- 
John

On Friday, November 19, 2021 at 8:23:41 PM UTC-8 Steven Trogdon wrote:

> Is this still supposed to work?
>
> ./sage --installed
> [package]...[latest version] ([version])
>
> Traceback (most recent call last):
>   File "/local/sage-git/sage/src/bin/sage-list-packages", line 102, in 
> 
> pkg.installed_version = pkg.installed_version or 'not_installed'
> AttributeError: can't set attribute
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/beb87809-1fe5-4dee-93ca-2b234e2c4295n%40googlegroups.com.

Re: [sage-support] Using SageMath app online and saving worksheets?

[John H Palmieri]

The default behavior, at least if you start Sage from a terminal window 
with "sage -n", is to store the notebooks in the current directory. If you 
want to change this, then: after you download Sage, from a terminal you 
should run "sage --jupyter notebook --generate-config". This will print a 
message like

Writing default config to: 
/Users/jpalmier/.sage//jupyter-4.1/jupyter_notebook_config.py

Within the named file, there are lines

## The directory to use for notebooks and kernels.
#  Default: ''
# c.NotebookApp.notebook_dir = ''

You can change the last line to

c.NotebookApp.notebook_dir = '/Users/my_user_id/any/directory/I/want/'

and Sage will store your notebooks in that directory.

On Tuesday, November 9, 2021 at 8:34:23 PM UTC-8 cyrille piatecki wrote:

> For Mac I don't know where the system keep the files. I have tried to find 
> it because some of my student use a Mac, but without success. Sorry
>
> --
> *De: *"LouP" 
> *À: *"sage-support" 
> *Envoyé: *Mardi 9 Novembre 2021 23:35:46
> *Objet: *Re: [sage-support] Using SageMath app online and saving 
> worksheets?
>
> Thank you Mr. Piatecki.  I should have mentioned I am using a Mac.  Sorry. 
> But it does sound like the files are local.  -- Lou Pecora
> On Tuesday, November 9, 2021 at 12:48:21 PM UTC-5 cyrille piatecki wrote:
>
>> You can install Sagemath on your computer if you download the good file (
>> https://www.sagemath.org/download.html).
>> Under Windows your files are stored into c:\user\yourname\...
>>
>> --
>> *De: *"LouP" 
>> *À: *"sage-support" 
>> *Envoyé: *Mardi 9 Novembre 2021 14:59:00
>> *Objet: *[sage-support] Using SageMath app online and saving worksheets?
>>
>> After Googling and checking the resources suggested I have not found 
>> answers to two simple questions about SageMath:
>> (1) Can I run this offline?
>> (2) Where are my worksheets stored and can I back them up?
>>
>> Thanks for any hints.
>>
>>  -- Lou Pecora
>>
>> -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/4ad6d585-cfda-4336-b7cc-91f3a3fd7b05n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-support...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/cc0827e6-3af8-45ea-8dc9-c06a3b726fb7n%40googlegroups.com
>  
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/76b099ae-6099-4f6f-9fd3-e53c7d21c16en%40googlegroups.com.

Re: [sage-support] Re: trouble displaying 3D graphics

[John H Palmieri]

Is there a way for users to redefine SAGE_TMP (without editing Sage source 
code) so that these graphics files would be produced elsewhere?

On Tuesday, November 9, 2021 at 4:06:34 AM UTC-8 dim...@gmail.com wrote:

> Right, one can see more of these "Chromium cannot open hidden 
> files/directories" posts
> elsewhere, cf. e.g.
>
> https://askubuntu.com/questions/1312932/cant-browse-access-hidden-files-and-folders-with-chromium
>
> I don't see a good and quick way out, rather than renaming ~/.sage/ to 
> something without leading '.'.
>
>  
>
>
>
>
> On Tue, Nov 9, 2021 at 10:23 AM Eric Gourgoulhon  
> wrote:
>
>> Le mardi 9 novembre 2021 à 10:38:29 UTC+1, dim...@gmail.com a écrit :
>>
>>> I wonder if 'file:///' must be present in the URL for the script source 
>>> for Chrome/Chromium to load it.
>>>
>>> This does not seem to be an issue with 'file:///' in the URL since 
>> Chromium refuses to open any hidden directory while browsing directories in 
>> the window opened after CTRL+O.  
>>
>> -- 
>>
> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/dd62df2d-4a09-4475-bdf6-62af5a3249e3n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/616a26f8-ff7c-48a4-be91-7b2ed52e094en%40googlegroups.com.

[sage-devel] tox -p: necessary resources?

[John H Palmieri]

If I want to run "tox -p auto" on my machine, what sort of resources do I 
need to allocate to Docker ahead of time, so that it won't run out of disk 
space? Any other tips for using it? What's a "local squid," anyway?

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e52a632d-7d2e-4c06-9b06-72a72364b2ccn%40googlegroups.com.

Re: Terminal Emulator

[John H. Reinhardt via cctalk]

On 10/1/2021 12:34 PM, Zane Healy wrote:

On Oct 1, 2021, at 9:36 AM,   wrote:


Zane wrote...
A few years ago, I looked at ZOC v7, and others.  I opted for SecureCRT, and 
use it on my Mac and my iPad.  Though the Mac version is well over $100.  It 
seems to have about the best DEC Terminal emulation I could find on the Mac, 
and it supports keyboard mapping.
--

Seconded on "SecureCRT". It is one of the few programs that I pay for a license 
for. I do believe it has the most complete/solid vt100 and other dec terms emulation I 
have ever seen. Most other term progs only support the basics of vt100 and a few more 
advanced options. I haven't found anything yet that securecrt doesn't implement and 
implement correctly as far as vt100 goes. I have never needed anything color-related 
though, that may or may not be as well done.

I paid for a windows license, but I believe I also get free access to linux and mac 
versions just for licensing the windows version. In addition, every time I have emailed 
them (Van Dyke) and said "hey, would be handy to have feature xxx", it has come 
out in the next version. The really do listen to customers for product 
enhancements/features.

It is the only term program I use, as it literally handles anything I've ever 
considered possibly wanting to do (including a pretty full featured scripting 
language). There is one exception - HP terminal emulation - specifically the 
ones with the 8 function labels at the bottom of the screen. For anything 
old-HP related, I use QCterm. Also free, and does a great job with all the 
funky HP terminal oddities 

SecureCRT for windows - software + 1 year of support = $99usd. I do the 3yr 
option instead which is $139usd. Of all the software products I have paid for, 
this one is probably the best value to me.

J


I do keep a VT420 on a DECserver next to my Mac, as sometimes it’s more 
convenient to have the proper LK401 keyboard.  My only complaint about 
SecureCRT would be its handling of Double-Width/Double-Height characters, but 
that’s not something you normally run into.

It would be nice if they’d add REGIS support. :-)

As long as you have active support, you get free upgrades.

It’s xterm emulation offers 256 colour.  VT100/VT102/VT220/VT320 emulation 
offers ANSI Colour, but I’ve never played with that.  Trying it just now, it 
gives me colours on a Linux system.  I don’t know that I have anything on VMS 
that would give colours.

Zane







I tried SecureCRT a couple of times, once for home use and once at work.  I 
didn't like it but I can't remember why.  ZOC has done everything I need.  
Between the Matias keyboard which has 19 F keys and the correct number of 
keypad keys (not PC layout) and the ZOC keyboard mapping I have pretty much a 
VT200 style keyboard on my Mac.

Em-Tec gives product support for life, basically. I've emailed the author and 
gotten responses and help immediately.  Once you buy a version you get updates 
until the next major version and if you buy late into the current version you 
often get the next version free.  That happened to me between V6 and V7.  V7 
went nearly 3 years before I had to upgrade by paying $29.99.

In 2018 V7.21 of ZOC scored 105 (97 regular + 8 extra credit) on the VTTEST 
suite for VT100/VT102 terminals. 
file:///Volumes/Users/jhreinhardt/Downloads/ZOC_vttest_Score_Sheet-1.pdf

No REGIS graphics though.  It will do the VT line drawing character set. 
https://www.emtec.com/zoc/vt220-terminal-emulator.html

Double-width/double-height lines work  
https://www.emtec.com/images/zoc/us/mainwinvt102_osx.png

I've not had it have a problem with any part of VT100/102/200 emulation that I 
can remember.

--
John H. Reinhardt

Re: Terminal Emulator

[John H. Reinhardt via cctalk]

I've been using a terminal emulator called ZOC. It comes in Windows and Mac 
flavors (I use the Mac) It seems to fit most of your criteria.  I've been using 
it since V6 (current is V8) for connection to many different PDP-11's, VAXen, 
Alphas, RasPi, device serial ports on switches, routers and storage servers. 
Setup can be a bit confusing at first.  The app manages config files for 
keyboard types (yes, keyboards are configurable - somewhat) and connection 
types.  I ended up creating a generic standard config for VAXen, PDP, Alpha, 
etc and then saving a customized version for each individual system.  They all 
get linked together by the connection manager.

Product Page: https://www.emtec.com/zoc/index.html
Features:  https://www.emtec.com/zoc/features.html

It has a 30 day free trial with no limitations so you can try it and see.

On 9/30/2021 1:57 PM, Mike Katz via cctalk wrote:

I am looking for a good terminal emulator.  Not for connecting to older 
computers serially but to connect with my embedded designs.
Do any of you have any recommendations.

I've been using Realterm for years but it's not very good.

I used UCON, hyper term, terra term, telix (going way back) and a few I can't 
remember the name of.

Here are my needs:

1.  Runs under Windows 10 (linux optionally)

    Yes - Windows 7, 8 , 10 and probably 11 when it comes

2. Has user selectable baud rates (I use 500K baud frequently)

    Yes - Baud rates from 300 to 921600 (460800 is the closest to 500k)

3. Can use any Windows Com Port.

    Not sure as I don't use Windows but I imagine any COM port will work

4. Can send files as raw binary

    Yes - Raw Binary or as ASCII

5. Has X-modem built in (nice but optional)

    Yes - XModem, ZModem, YMode, Kermit, SCP, Sealink (?)

6. Has some kind of basic VT-100 support

    Yes - VT100 or VT200 plus other Non-DEC

7. Can display both ascii characters and binary data has hex numbers, 
preferably on alternate lines (hex above the ascii character like this:
        45 76 65 72 79
 E    V   E   R   Y

    No...  I don't see an option for this.  But I've never seen an emulator 
that does.  You have one?

8. Can send short manually entered strings in hex or ascii.

    Doesn't appear to be able to do this.  But it might be possible with a 
programmed macro (yes, it has a scripting language)

9. Can recognize protocols (based on start and/or end of text characters)

    Might be possible with the scripting language.

10. Costs less than $100

    Price is $79.99 US or €79 for a version license.  Currently V8. When V9 
comes then upgrade is $29.99 US or €29

11. Can Capture what comes in the port

    Yes - Multiple logging and screen capture options

12. Has local echo (when connected to systems that don't echo what you type)

    Yes - Part of terminal settings

13. Has a large scroll back buffer.

    Yes - user selectable to about as large as your computer can handle

14. Has programmable macro buttons or function keys.

    Yes - Optional Tool bar and user defined buttons

15. Can handle removal and insertion of the TTL to Serial USB converter without 
crashing.

    I don't think I have tried.  There have been a couple times when it's hung 
up on me but that was possibly odd output from a bum serial port.


Thank you






--
John H. Reinhardt

[sage-devel] Re: Building sage fails at gsl because of openblas

[John H Palmieri]

One guess would be that ./configure found what it thought was a usable 
installation of openblas, but when gsl tried to build, that openblas was 
not in fact usable. You can bypass this by either installing a system 
version of gsl or using `./configure --with-system-openblas=no` to force 
Sage to build its own openblas.



On Wednesday, September 29, 2021 at 2:06:43 AM UTC-7 Kwankyu Lee wrote:

> My question is: why "make" does not build openblas first and then gsl, 
> instead of forcing me to do this manually?  
>
>
> On Wednesday, September 29, 2021 at 6:03:15 PM UTC+9 Kwankyu Lee wrote:
>
>> Hi,
>>
>> I started to build the latest Sage 9.5.beta2 from some old Sage 
>> installation on Mac. Then it failed while building "gsl" complaining 
>> missing "openblas" library. I could overcome the problem by issuing "sage 
>> -i openblas". I went through this twice on two Sage installations on the 
>> same machine.
>>
>> But my question is: if openblas is a requirement of building gsl, then 
>> why "make" build openblas first and then gsl, instead of forcing me to do 
>> this manually?  I guess there is a bug in the make script...
>>
>> Thank you for attention.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b409d267-5aa1-43b6-935b-21bdb3c278d0n%40googlegroups.com.

[sage-devel] Sympow build warning

[John H Palmieri]

On an OS X machine, the sympow build prints a warning at the start. Well, 
it calls it an error and then proceeds to build anyway:

-

CFLAGS for SYMPOW:  -std=gnu17 -fno-fast-math -mfpmath=sse -ffp-contract=on 
-Dx86  -O0
The double precision of your FPU is 105 bits.
Error: the Quad Double library used by SYMPOW assumes IEEE-754 double
precision numbers with exactly 53 bits in the mantissa (64 bits in
total).  Unfortunately, this is not the case on your system and we
currently have no workaround for your system.  Running SYMPOW will
almost certainly fail on some inputs.

Please report this problem to sage-devel
(http://groups.google.com/group/sage-devel), mentioning in particular
your operating system, processor type and compiler version
(run gcc --version).

-

So I'm reporting to sage-devel. This is with OS X 11.6. For processor type:

% sysctl -n machdep.cpu.brand_string
Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz

And gcc:

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

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7cf8fac7-e81b-4d6c-aeb3-275260b21d4en%40googlegroups.com.

Re: [sage-devel] Re: #32532 - removing gcc and gfortran spkgs

[John H Palmieri]

Item #2 actually happened. Can you cite posts from people successfully 
using the tools you mention to get around it? 


On Thursday, September 23, 2021 at 7:48:35 PM UTC-7 Michael Orlitzky wrote:

> On Thu, 2021-09-23 at 18:12 -0700, Matthias Koeppe wrote:
> > I repeat my strong objections to the proposed change -- which does not 
> > solve any problems and only creates new ones.
> > 
>
> 2, 4, 6, and 7 are addressed by Conda, Nix, Guix, Homebrew, or even
> Gentoo Prefix. These projects *want* to build entire distributions that
> run out of your home directory.
>
>
>
> > 5. The gcc spkg is specifically used in building the binary 
> distribution. 
> > Any discussion of removing the gcc/gfortran spkgs without including a 
> > discussion of deployment as the binary package is incomplete. 
> Availability 
> > of the compilers at runtime is a key feature that we have advertised 
> > through facilities such as the magic %cython directive and others.
> > 
>
> Whoever is building the binary images could install a compiler into
> SAGE_LOCAL with "dpkg-deb -x" or whatever before they start. There's no
> need for it to come from an SPKG.
>
> The fact that we even have to consider these issues supports the claim
> that these packages are a maintenance burden.
>
> And, veering off-topic:
>
> Our binaries aren't really binaries in the traditional sense. We ship a
> 3GB image of an entire operating system. This could be done much easier
> by... shipping an image of an entire operating system: QEMU,
> VirtualBox, Docker, etc. You could tar up an entire Gentoo system with
> sage installed and it would probably take up less space than our
> existing binaries. Similarly, I'm sure we could tar up a Conda image
> where sage was installed and tell people to download that. Provide a
> launcher script and it would work out-of-the-box.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fddc13dc-a843-4bc2-a06e-390a54cbe0fan%40googlegroups.com.

[R-pkg-devel] Namespace is imported from in YAML header, but attracts Note that is is not imported from

[John H Maindonald]

On the Atlas and Linux builds of my package `qra` that has just been posted 
on CRAN, I am getting the message:

> Namespace in Imports field not imported from: ‘bookdown’
>   All declared Imports should be used.

This, in spite of the fct that the YAML header in two of the Rmd files for the 
vignettes has:

> output:
>   bookdown::html_document2:
> theme: cayman

Do I need to worry about this?

John Maindonald
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [sage-devel] #32532 - removing gcc and gfortran spkgs

[John H Palmieri]

I presume that this is not an issue for linux, but maybe I'm wrong about 
that. In any case, I'm concerned about OS X.

- How well tested are the various standalone Fortran options for OS X? I 
mean, how well tested are they for building Sage? Gfortran coming from 
homebrew is already included in tox.ini, I assume conda too, but perhaps ​​
https://github.com/fxcoudert/gfortran-for-macOS 
 should be added, 
especially if we're going to advertise it.

- How well supported are the various Fortran options for older versions of 
OS X?

  John

On Thursday, September 23, 2021 at 3:47:16 PM UTC-7 François Bissey wrote:

> As someone who contributed to those (and literally created the gfortran 
> package when I pushed for enabling clang support on OS X) I welcome their 
> demise. I’ll review their removal with pleasure if you need it.
>
> François
>
> > On 24/09/2021, at 10:17, Dima Pasechnik  wrote:
> > 
> > https://trac.sagemath.org/ticket/32532 proposes to remove these 
> packages as not needed, and a huge time sink for everyone involved.
> > 
> > Rationale: nowadays every platform that Sage supports has said tools (or 
> their equivalents - e.g. clang/clang++ in case of macOS and FreeBSD) 
> available, if not outright as a system package, but surely with a very 
> minimal effort.
> > 
> > There is no need to carry this baggage forward.
> > Moreover, it seems that Sage is the only Python library/platform around 
> which (potentially) vendors gcc/g++/gfortran. 
> > 
> > 
> > 
> > -- 
> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0hsaf3SR-78Wajb_OdYjZq1MyReRH2vcwSO%2BU7CzLtYw%40mail.gmail.com
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/599264b1-2877-4074-b890-61bc279b6adfn%40googlegroups.com.

Re: Setting up a VMS system

[John H. Reinhardt via cctalk]

On 9/23/2021 8:12 AM, Scott Quinn via cctalk wrote:

On Wed, 2021-09-22 at 12:00 -0500, cctalk-requ...@classiccmp.org wrote:

Currently the Hobbyist Program covers Alpha and Itanium.  We?ve been
told it will cover x86 at some point.  I for one can?t wait for x86,
as I don?t really want to add an Itanium to run some of the newer
software.

Zane

Not even that... looked at the VSI stuff and it is only the newest
Alphas that are supported. 21064/21164 and, I believe, 21264 are not


The VSI SPD for OpenVMS V8.4-2L1 (the version given with the VSI Commumity License program) 
indicated DS10 and newer.  However, as often mentioned, there is a difference between 
"supported" and "works".  People in comp.os.vms have installed the VSI releases 
on Alphastation 255's Alphaserver 800/1200 and other EV4 and EV5 Alphas.  VSI won't mark them as 
supported probably because they don't have any such systems to test on or just don't want to bother 
testing on such systems.

If you have somehow gotten a copy of VSI OpenVMS V8.4-2L2 then it was 
specifically built to support EV6 and newer Alphas.  It will NOT work on older 
systems such as the AlphaServer 800/1200/4100 and AlphaStation 255 series.


supported by any release licensed by VSI, and they changed the PRODUCER
key so you can't use those PAKs on DEC/CPQ/HP variants of VMS.


Part of their licensing agreement with HPE which prohibits them from 
selling/licensing any previous version of OpenVMS that they haven't worked on.


HP stopped issuing new hobbyist PAKs back very early in 2020. I put in
for a renew March or so and never got it. They were so disinterested in
the program that they didn't mention stopping it, so I guess it isn't
surprising that the page is still up.


If it's a VAX PAK you need, contact me and I can send you a copy of the last 
VAX OpenVMS Hobbyist PAK sent out.  Note that it expires on 1-JAN-2022 so it's 
good only for a few more months.



Isn't VMS DCL pretty close to RSX? Never used RSX, but that is what I
was always told. Anyway, good system, pretty solid, expect to do a LOT
of typing for commands if you're used to UNIX, and don't put any VAX
with a public DCL account on the Internet because there is a huge
security hole in DCL that was never fixed for VAX.



--

John H. Reinhardt

Re: Setting up a VMS system

[John H. Reinhardt via cctalk]

On 9/22/2021 7:21 AM, Philip Pemberton via cctalk wrote:

Hopefully a few of the DEC/VMS fans here might be able to help!

I'm on a bit of a quest. I've been given some old VAX/VMS software -- a cross 
compiler and some source code -- that I'd like to get running. My goal is to 
get the source code building and experiment with the compiler a bit.

Problem is that I've never used VMS before, and don't have a clue how to 
install or use it.

Can any point me to an idiot's guide to VMS, how to set it up and make it 
possible to send files to it from my Linux box?

I'm thinking of using SIMH, unless there's a better emulator available.


That is pretty much it for VAX emulation.  Going with the V4 release stream 
gives you a number of options, but they are all basically the same.



I'm still waiting on a reply from HP with a hobbyist licence PAK (I've filled 
out the form), but I figure I can get started on the learning while I wait.



That will be a long wait.  HPE stopped responding to OpenVMS Hobbyist requests 
around May 2020.  If you email me I can send you a copy of the last set of VAX 
OpenVMS PAKs that were sent out.  They are generic, as opposed to what they 
used to send out which had authorization # tailored to each requestor.  These 
are good only for a few more months s they expire on 1-Jan-2022.  As they were 
generic and the last Hobbyist PAKS that HPE was going to send out we got 
unofficial (from Hari, the HPE employee in India that ran the Hobbyist program) 
permission to give them to anyone that asked.


You don't say how old the software is that you want to run.  If it's VAX/VMS V4 
vintage then you gan get away without the PAKS as that is pre-LMF and PAK 
usage. But then again, V4.7 era is somewhat harder to install and set up than a 
V7.3 (the last VAX version)



Cheers
Phil.



--
John H. Reinhardt

[sage-release] Re: Sage 9.3.beta7 released

[John H Palmieri]

Sorry to resurrect this old thread, but I'm seeing the same numerical 
doctest failures on an OS X machine with Sage 9.5.beta1. Any ideas where 
these could be coming from? Some miscompiled component coming from the 
system, or something from within Sage itself? I started seeing these after 
upgrading to OS X 11.5.2 (it was on 10.?? before). I tried reinstalling all 
of homebrew's packages, and that didn't help.





On Sunday, February 7, 2021 at 5:12:40 PM UTC-8 matthia...@gmail.com wrote:

> On Sunday, February 7, 2021 at 2:04:42 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 
>>
>> 8453ffb849 (tag: 9.3.beta7, trac/develop) Updated SageMath version to 
>> 9.3.beta7
>>
>>
> First test results from 
> https://github.com/sagemath/sage/actions/runs/545994902:
>
> ubuntu-bionic-standard: (python 3.6) still 
> https://trac.sagemath.org/ticket/31191
>
> debian-bullseye-standard: New(?) numerics issues:
> sage -t --random-seed=0 src/sage/finance/time_series.pyx  # 8 doctests 
> failed
> sage -t --random-seed=0 src/sage/geometry/polyhedron/library.py  # 1 
> doctest failed
> sage -t --random-seed=0 src/sage/geometry/polyhedron/base.py  # 1 doctest 
> failed
> sage -t --random-seed=0 src/sage/matrix/matrix_double_dense.pyx  # 2 
> doctests failed
> sage -t --random-seed=0 src/sage/matrix/matrix_integer_dense.pyx  # 1 
> doctest failed
> sage -t --random-seed=0 src/sage/numerical/sdp.pyx  # 2 doctests failed
> sage -t --random-seed=0 
> src/sage/tests/books/computational-mathematics-with-sagemath/float_doctest.py 
>  
> # 1 doctest failed
>
>
>
>
>
>  
>

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

[sage-devel] Re: Outdated instructions in "git the hard way"

[John H Palmieri]

Could you please open a ticket for this?

On Tuesday, September 7, 2021 at 3:47:44 PM UTC-7 Nils Bruin wrote:

> On:
>
> https://doc.sagemath.org/html/en/developer/manual_git.html
>
> it is suggested to start with
>
> git clone https://gitlab.com/sagemath/dev/tracmirror.git
>
> however, the gitlab mirror is stuck at 9.3. The github mirror tracks the 
> development tree much better. Shouldn't we be pointing people to that 
> instead? Or perhaps straight to trac.sagemath.org ?
>
> Incidentally, on FC 33 and FC 34, the default settings are pretty strict 
> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" fails 
> as a result.  A way of making FC >=33 more accepting of outdated signature 
> schemes is by:
>
> sudo update-crypto-policies --set LEGACY
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a463f4a1-b75f-40b9-b88a-0ecaaf401d84n%40googlegroups.com.

[sage-support] Re: Sage 9.4_20.04 Ubuntu: error relocate-once.py

[John H Palmieri]

Also addressed in https://github.com/sagemath/binary-pkg/pull/29


On Friday, September 3, 2021 at 10:15:02 AM UTC-7 Matthias Koeppe wrote:

> Thanks, I've noted this in 
> https://wiki.sagemath.org/ReleaseTours/sage-9.4#Availability_as_binaries_and_in_distributions
>
> On Friday, September 3, 2021 at 3:02:47 AM UTC-7 Rolandb wrote:
>
>> Hi,
>>
>> Running the file 'relocate-once.py', I got an error: directory 'python' 
>> not recognized.
>> Changing the line #!.. python into #!.. python3 solved the problem.
>>
>> Roland  
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/3db75689-efd7-4e45-a59f-c8d2f92fb479n%40googlegroups.com.

Re: [sage-support] Other mailing lists

[John H Palmieri]

I believe that most of the traffic these days is on sage-support and 
sage-devel, rather than the more specialized groups. Feel free to post 
questions about Sage's algebra capabilities here.

On Monday, August 23, 2021 at 8:03:33 PM UTC-7 H wrote:

> On August 23, 2021 7:18:16 PM EDT, David Joyner  wrote:
> >On Mon, Aug 23, 2021 at 7:13 PM H  wrote:
> >
> >> I just joined this list a few days ago but also tried to join
> >> sage-algebra, that list however seems dead. The moderator has after
> >almost
> >> a week not approved my membership and the last Google group posting
> >seems
> >> to be from 2018...
> >>
> >> Are there any other mailing lists/groups? I should also mention that
> >the
> >> rss feeds mentioned on the sage site have
> >
> >
> >Some are listed here:
> >https://www.sagemath.org/help-groups.html
> >and others are here
> >https://www.sagemath.org/development-groups.html
> >
> >defective links... Is the software dying or am I missing something?
> >>
> >> --
> >> 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 view this discussion on the web visit
> >>
> >
> https://groups.google.com/d/msgid/sage-support/FA4ECD7D-AC30-4982-8B7F-A6BEDBF1BD91%40meddatainc.com
> >> .
> >>
>
> Yes, that's the page with the dead sage-algebra group and the non-working 
> rss feeds...
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/bd9058fe-52c9-4096-be88-cedf76cfd6f6n%40googlegroups.com.

Re: [sage-devel] Problem Building Sage from Source

[John H Palmieri]

(I'm not sure where this comes from, since searching for "givaro" on 
brew.sh comes up empty.)

On Wednesday, August 18, 2021 at 6:48:10 PM UTC-7 John H Palmieri wrote:

> You could try uninstalling homebrew's givaro and/or use `./configure 
> --with-system-givaro=no` to force Sage to build its own givaro.
>
> On Wednesday, August 18, 2021 at 4:45:54 PM UTC-7 Brian Sun wrote:
>
>> I ran the two commands (and also uninstalled Macaulay2 and the copy of 
>> fflas-ffpack using Homebrew and tried it), and it still does not seem to 
>> work. I've the linbox log file again, which seems to be the only issue in 
>> the installation. The errors seem similar to last time -- stuff about 
>> "redefinition" and "implicit instantiation."
>>
>> Brian
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e10a9b20-673a-464e-8419-9c3caaa45408n%40googlegroups.com.

Re: [sage-devel] Problem Building Sage from Source

[John H Palmieri]

You could try uninstalling homebrew's givaro and/or use `./configure 
--with-system-givaro=no` to force Sage to build its own givaro.

On Wednesday, August 18, 2021 at 4:45:54 PM UTC-7 Brian Sun wrote:

> I ran the two commands (and also uninstalled Macaulay2 and the copy of 
> fflas-ffpack using Homebrew and tried it), and it still does not seem to 
> work. I've the linbox log file again, which seems to be the only issue in 
> the installation. The errors seem similar to last time -- stuff about 
> "redefinition" and "implicit instantiation."
>
> Brian
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fd2ab24d-7651-40fd-a7b6-67eee061ac64n%40googlegroups.com.

[sage-devel] Re: Implementation for representation of 2-knots

[John H Palmieri]

I think that more math of almost any sort would be great to add to Sage. 
Improving the knot and link capabilities would be great!

  John


On Monday, August 2, 2021 at 12:59:13 PM UTC-7 Calvin Godfrey wrote:

> First of all, I apologize if this isn't the right place to ask this. I 
> spent ages looking for links on the sage website, and this seemed like the 
> most relevant.
>
> I spent this summer doing an undergraduate research project on 2-knots, 
> based primarily off of the work from https://arxiv.org/abs/1507.08370. In 
> particular, we have a way to represent 2-knots as a triplet of braid words, 
> and we're able to calculate the Alexander Invariant (an ideal over the ring 
> of Laurent polynomials) for an arbitrary 2-knot with this representation.
>
> Would this be something worth fleshing out to add to sage? I looked 
> through the developer's guide, and it looked like there were a lot of steps 
> to do everything properly. I just want to make sure this would be fruitful 
> work before I get started downloading and compiling from source.
>
> If not the full implementation, there are some smaller parts that I think 
> could be useful to have in sage. In particular, an alternative closure of a 
> braid on 2n strands. Instead of joining the top and bottom of each strand, 
> we join together the top and bottom of adjacent strands, like in this 
> crudely made diagram.
>
> [image: knot.png]
>
> I would appreciate any feedback!
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6a26b675-4dad-4cd6-ba38-a413f84200ean%40googlegroups.com.

Re: [sage-devel] Re: Library code returning int value

[John H Palmieri]

I think that we should prefer tuples to lists when that is appropriate, 
lists to tuples when that is appropriate. Python has both types for good 
reasons, I think, and I don't see why we should globally recommend one over 
the other.

On Wednesday, July 14, 2021 at 7:21:48 PM UTC-7 Kwankyu Lee wrote:

> While we are at
>
> https://trac.sagemath.org/ticket/32200
>
> which is really about standardizing types of return values. How about 
> including recommendation to prefer `tuple` to `list`? Of course this is 
> only to apply to functions and methods for users. I think it is good to 
> have a default type so that users do not need to check for any reason 
> whether the return value is a tuple or a list.
>
> I dimly remember there was a  discussion about list vs tuple long time 
> ago, but with no conclusion. I don't intend to provoke another discussion. 
> But if we now have reached a consensus on this matter, then we can add it 
> to the ticket.  
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/17671f54-054d-4fa0-a900-e998515552cen%40googlegroups.com.

Re: [sage-devel] spoken languages and banner translations

[John H Palmieri]

Does anyone have experience working with graphic designers? How much would 
it cost to get a logo designed by a professional?

On Sunday, July 4, 2021 at 10:27:07 AM UTC-7 Nils Bruin wrote:

> Oh my, those logos are absolutely atrocious! Never mind the translation: 
> the text is clipped to incomprehensibility anyway (at least when displayed 
> in firefox) -- and that includes the english language one. On the plus 
> side, these logos are so obviously bad that I don't think anybody 
> reasonable will consider using them.
>
> Concerning the dutch translation: Especially for professional/business 
> terminology, the Netherlands have a strong preference for just borrowing 
> the english term (this may be a bit different in Flemish-Belgium), so "open 
> source mathematics" or "open source wiskunde" sounds completely acceptable 
> to me. The most direct translation "vrije broncode wiskunde" sounds a 
> little strange. It would need to be "wiskundige software met open broncode" 
> which doesn't really have a punch. Using "bronnen" (sources) has no 
> software association in dutch at all, so it would seem that it's about 
> mathematics that uses available (historical?) sources rather than secret 
> ones.
>
> As anecdotal evidence of use of english terms in official dutch 
> communication meant for a dutch audience:
>
> https://www.rivm.nl/bevolkingsonderzoeken-en-screeningen/bevolkingsonderzoek-organisatie/broncode-vrijgegeven
> (note uses of "open source", "ICT" (meant as an english acronym, although 
> a translation would have the same letters). Indeed, a good effort in using 
> the word "broncode" in various places.
>
> On Friday, 2 July 2021 at 07:35:11 UTC-7 Frédéric Chapoton wrote:
>
>> So should I replace "wiskunde met vrije licentie" by "open bronnen 
>> wiskunde" ? 
>>
>> This would be a more accurate translation, maybe ?
>>
>> Le vendredi 2 juillet 2021 à 15:43:12 UTC+2, dim...@gmail.com a écrit :
>>
>>> I think one does not translate "open source" in Dutch. (maybe you can 
>>> write "opensource" or "open bronnen")
>>>
>>>
>>>
>>> On Fri, 2 Jul 2021, 10:18 Frédéric Chapoton,  wrote:
>>>
 Hello,

 if you speak interesting languages, could you please have a look at

 https://wiki.sagemath.org/CorporateIdentity

 and either check the text of existing banners or suggest new 
 translations ? The reference for the translations is the english text : 
 "open source mathematics".

 thanks,
 Frédéric

 -- 
 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 view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/54fdb0b8-b6a2-4e3a-b052-ab9f861fed0bn%40googlegroups.com
  
 
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/53772a08-aa36-4470-896d-d860ced3b1f6n%40googlegroups.com.

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

[John H Palmieri]

After seeing the message "Pytest is not installed, skip checking tests that 
rely on it" a number of times, I decided to install it. There were two 
files with resulting doctest failures:

sage -t --long --warn-long 131.5 --random-seed=0 src/sage/doctest/test.py  
# 7 doctests failed
sage -t --long --warn-long 131.5 --random-seed=0 src/sage/tests/cmdline.py  
# 2 doctests failed

I think these are all because the return value from a process is nonzero; 
for example

File "src/sage/doctest/test.py", line 26, in sage.doctest.test
Failed example:
subprocess.call(["sage", "-t", "--warn-long", "0", "--random-seed=0", 
"longtime.rst"], **kwds)  # long time
Expected:
Running doctests...
Doctesting 1 file.
sage -t --warn-long 0.0 --random-seed=0 longtime.rst
[0 tests, ...s]
--
All tests passed!
--
...
0
Got:
Running doctests with ID 2021-07-02-10-56-11-f6aa1957.
Git branch: develop
Using --optional=build,dochtml,homebrew,pip,sage,sage_spkg
Doctesting 1 file.
sage -t --warn-long 0.0 --random-seed=0 longtime.rst
[0 tests, 0.00 s]
--
All tests passed!
--
Total time for all tests: 0.0 seconds
cpu time: 0.0 seconds
cumulative wall time: 0.0 seconds
= test session starts 
==
platform darwin -- Python 3.9.5, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
rootdir: 
/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.4.beta4/src, 
configfile: tox.ini
collected 0 items

 no tests ran in 0.02s 
=
5


On Thursday, July 1, 2021 at 2:49:37 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 
>
>
> 473cd41f19 (tag: 9.4.beta4, trac/develop) Updated SageMath version to 
> 9.4.beta4
> 06ec5d949d Trac #31987: Adding category options to Representations
> a8a5110e9a Trac #31978: E701, E702 for databases
> c6eb54e107 Trac #31977: E701, E702 for groups
> 3b60a97925 Trac #31976: E701, E702 for interfaces
> 0381045034 Trac #31974: E701, E702 for algebras, crypto, quadratic form, 
> structure
> c0f1a74a63 Trac #31965: Improve the handling of temporary symbolic 
> variables in sage
> 57627cad2a Trac #31859: method stack_sort for permutations
> 5f639d3c78 Trac #31822: Check containment for combinatorial faces
> d29034d38a Trac #31819: Only subfaces/supfaces for polyhedral face iterator
> 2a1799f45c Trac #31774: Wrong degree limit in PrimitiveGroup()
> f69ce021dd Trac #31719: Fix deprecation warning with viewing KR crystals
> 389057aa4a Trac #31616: Make quaternion_algebra() method of Brandt modules 
> directly call QuaternionAlgebra()
> a8cce88f0e Trac #30832: Connect RealSet to sage.manifolds
> 69e4080eda Trac #29683: "look up" a face in the face lattice of a 
> polyhedron
> 66aa3c0754 Trac #24171: Formal set membership function
> dae5f2cbd6 Trac #31160: Remove strict requirement for libreadline when 
> building python3
> af326a8c9a Trac #31941: Make empty RealSet false
> f64fd90fca Trac #31931: _sympy_ methods for some parent classes
> 7cbc6685d3 Trac #31927: RealSet: Replace is_included_in, is_disjoint_from 
> by is_subset, is_disjoint
> 90ee1b0655 Trac #31925: Reorganize topology
> a8da0f6360 Trac #31877: Refine category of RealSet
> 3fa193391a Trac #31834: Make Hrepresentation of `CombinatorialPolyhedron` 
> bit more consistent
> fc26215dc7 Trac #31831: tox.ini, GH Actions: Add ubuntu-impish, 
> linuxmint-20.2, fedora-35
> 075b352b88 Trac #31696: Sphinx/docutils update for Sage 9.4
> 5c9eab3b85 Trac #31550: fix some NOTE and EXAMPLES
> 2b8876798b Trac #31490: openblas: Run spkg-check with the same 
> configuration as spkg-install
> af77aabbc7 Trac #31443: update eclib and improve interface for elliptic 
> curve saturation
> 1650c1a835 Trac #31333: sage.env.sage_include_directories: Remove hard 
> dependency on numpy
> 265cd1339b Trac #30755: control the number of digits to display in 
> matrices via IPython's %precision magic
> c920272293 Trac #30698: Add Gauss-Legendre integrator to documentation
> e9fb18b6cd Trac #32071: Update version ranges in install-requires.txt for 
> several recently updated packages
> 97fb1eef56 Trac #21243: RealSet: add methods closure, interior, boundary, 
> is_open, is_closed
> 0a8b42b265 Trac #18119: New methods for WordMorphism
> 098a2474cd Trac #30972: Versioned installation of threejs
> 70c0b075b8 Trac #32031: Stop setuptools install from nuking the 
> setuptools_scm installation
> 68b61d5edc Trac #32048: Two doctests in modular depending on 
> 

Re: [Evolution] Generating message list (cancelling) won't cancel. Evolution locked up

[Dr. John H. Lauterbach]

Hello Milan,

Thank you for your message.  My problem appears related to your recent post 
"Gmail & Yahoo".

Evolution version is 3.40.0-1.  This newer version came when I upgraded Ubuntu 
from 20.10 to 21.04.
 This gets in to the question of connecting to Yahoo email accounts, even 
though address is
my_n...@bellsouth.net.  The server settings from Outlook (my bellsouth email 
runs fine on a Win 10
PC) are:

imap.mail.yahoo.com
smtp.mail.yahoo.com

The simple fix for now is to move critical personal email to another IMAP email 
service that is not
involved with Yahoo.

John 



On Mon, 2021-06-14 at 11:40 +0200, Milan Crha via evolution-list wrote:
> On Sun, 2021-06-13 at 19:14 -0400, Dr. John H. Lauterbch wrote:
> > What do I need to do to get out of this problem.  I need to delete
> > problem email account, but as soon as evolution starts, it locaks up
> > as noted above.
> 
> Hi,
> it would help to see what evolution is trying to do, to eventually fix
> it, but I'm afraid the account is gone now, thus no way to get the
> backtrace, right?
> 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

Re: [Evolution] Generating message list (cancelling) won't cancel. Evolution locked up

[Dr. John H. Lauterbach]

Thank you, Pete.

John

On Mon, 2021-06-14 at 00:47 +0100, Pete Biggs wrote:
> On Sun, 2021-06-13 at 19:14 -0400, Dr. John H. Lauterbch wrote:
> > I am writing this from one of my backup PC's as evolution 3.40.0-1 on
> > my main PC is frozen as it is trying to scan a problem IMAPX server,
> > and even if i reboot PC and start eveolution, it starts locked on
> > Scanning folders in IMAP server and Generating message list
> > (cancelling) .
> > 
> > What do I need to do to get out of this problem.  I need to delete
> > problem email account, but as soon as evolution starts, it locaks up as
> > noted above.
> > 
> You can start Evolution from the command line with the '--offline'
> flag. It won't then scan the remote folders and you will be able to
> disable/delete the bad mail account.
> 
> 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

[Evolution] Generating message list (cancelling) won't cancel. Evolution locked up

[Dr. John H. Lauterbch]

I am writing this from one of my backup PC's as evolution 3.40.0-1 on
my main PC is frozen as it is trying to scan a problem IMAPX server,
and even if i reboot PC and start eveolution, it starts locked on
Scanning folders in IMAP server and Generating message list
(cancelling) .

What do I need to do to get out of this problem.  I need to delete
problem email account, but as soon as evolution starts, it locaks up as
noted above.

Thank you,


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-release] Re: Sage 9.4.beta1 released

[John H Palmieri]

It builds for me on OS X Big Sur and I see no new doctest failures, but the 
PDF documentation doesn't build. When building it/a_tour_of_sage, I see 
this error:

! Package inputenc Error: Unicode character リ (U+30EA)

Indeed, the file 
`local/share/doc/sage/latex/it/a_tour_of_sage/a_tour_of_sage.tex has the 
line

\renewcommand{\releasename}{リリース}

Why does the Italian tour have these Japanese characters in it? A few lines 
earlier, I also see

\date{2021年06月08日}

and at the bottom

\renewcommand{\indexname}{索引}

These lines are the same as in ja/a_tour_of_sage/a_tour_of_sage.tex.

I've opened https://trac.sagemath.org/ticket/31936 for this.

On Sunday, June 6, 2021 at 11:40:20 AM UTC-7 Volker Braun wrote:

> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html 
>
>
> 30ee8d6505 (tag: 9.4.beta1, trac/develop) Updated SageMath version to 
> 9.4.beta1
> 7690208434 Trac #31903: Build errors in padic_relaxed_element
> 605c100c46 Trac #31848: Random failure: sage.libs.gap.util.GAPError: 
> Error, OnSets:  must be a set
> 24a34ee595 Trac #31825: Failure when testing sage_conf version
> 5067635403 <(506)%20763-5403> Trac #31692: Refactor display behavior of 
> mixed forms
> 08b5a55b44 Trac #31691: Turn mixed form algebra into de Rham complex
> e30645c055 Trac #31686: Speed up factoring finite field multiplicative 
> order
> 490c3ddfeb Trac #31684: Improve WordMorphism._language_naive
> 3e413ce3b4 Trac #31681: DiGraph.layout_acyclic_dummy assumes it can sort 
> lists of vertices
> 5b23c1fac2 Trac #31677: Open subsets of arbitrary subsets of manifolds
> a8ed75663a Trac #31676: Hash of mpmath complex numbers produces 
> OverFlowError
> 24c78cf7f3 Trac #31674: Make open subsets of immersed/embedded 
> submanifolds immersed/embedded submanifolds
> 2f2b1540f7 Trac #31658: Slight speed-up in copy method
> fc7a3728c8 Trac #31654: copy_from for scalar fields
> db698c31ed Trac #31653: Images of continuous maps and embedded 
> submanifolds as manifold subsets
> b573a54ba3 Trac #31650: improve LazyImport
> 8600573a7f Trac #31647: Update sympy to 1.8
> b2aa0f6261 Trac #31633: Simplify VectorField.__call__
> 4200c96400 Trac #31619: Cholesky factorization and positive-definite 
> testing over inexact rings
> 60380a3cf3 Trac #31618: Some documentation improvements in 
> sage.modular.quatalg.brandt
> ab0715d126 Trac #31615: faster order complex for posets
> c95fe8492a Trac #31614: Remove dead _cholesky_decomposition_ from 
> matrix2.pyx
> 749b0ad122 Trac #31613: ClusterAlgebra.greedy_element bug and further 
> improvements
> ad89df812b Trac #31609: Add method tangent_vector to differentiable 
> manifolds
> 63c3d0fecb Trac #31594: Accept giac-1.7.x from the system
> c58463cf86 Trac #31526: Drop support for optional packages with system gcc 
> 4.x on ubuntu-trusty, debian-jessie, linuxmint-17, centos-7
> 8d55a3f756 Trac #31489: Galois subgroups
> 9c85a6c1cf Trac #30352: Interface to the KnotInfo and LinkInfo databases
> 9f031cdb05 Trac #29222: Improvements to padic polylog
> 9caac06757 Trac #28890: Install fewer static libraries
> e94bd31252 Trac #26635: Major extensions to local components code
> 9f3988d9a5 Trac #21203: basic element and parent for k-regular sequences
> 3b414bea4b Trac #20331: A MIPVariable's repr should include some useful 
> information
> 061d4b71df Trac #31860: Restore support for sage-bootstrap-python = python 
> 3.6
> 6aa4ecee16 (tag: 9.4.beta0) Updated SageMath version to 9.4.beta0
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/796ab67d-7369-4076-ad28-bbabed36d386n%40googlegroups.com.

[sage-devel] ask.sagemath.org is down

[John H Palmieri]

As pointed out in another message, ask.sagemath.org is down. Can anyone 
help?

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6ed60f74-51d7-4d2a-9af6-b0cbc472348bn%40googlegroups.com.

Re: Python 3.x fails build on Solaris 10

[John H]

Thanks for the suggestion, Jeff- but I noticed -lcrypt appears during the build 
process. I added it manually anyway but that led to errors concerning OpenSSL 
so will follow Miko's advice and send to 
pkgsrc-users.

Apologies for the mismail, I'm sure I could come up with an excuse at a push. (:

John

On Tue, May 25, 2021 at 05:37:56PM -0400, Jeffrey Walton wrote:
> On Tue, May 25, 2021 at 5:06 PM John H  wrote:
> >
> > Setting up pkgsrc-2021Q1 on Solaris 10 x86 for an experiment. Going quite 
> > well so far, but still using an old gcc version (3.4.3) to build a newer 
> > one within the pkgsrc ecosystem, however, seems I need Python
> > first. whenever I attempt to build any version of python 3.x I am dropped 
> > out with this:
> >
> > ld: fatal: library -lcrypt: not found
> >
> > ...which leads to
> >
> > ERROR: The following files are in the PLIST but not in 
> > /usr/pkgsrc/lang/python39/work/.destdir/usr/pkg:
> > ERROR: 
> > /usr/pkgsrc/lang/python39/work/.destdir/usr/pkg/lib/python3.9/lib-dynload/_crypt.so
> >
> > Hoping there's something simple I need to install first like a crypt 
> > library, any ideas appreciated!
> 
> I believe you need to add -lcrypt to LIBS during configure. (It is not
> a problem on Linux because glibc provides the functions).
> 
> It's been a while since I built Python on NetBSD, so I may be mistaken.
> 
> Jeff

-- 
j...@sdf.org
SDF Public Access UNIX System - http://sdf.org

Python 3.x fails build on Solaris 10

[John H]

Hi Everyone

Setting up pkgsrc-2021Q1 on Solaris 10 x86 for an experiment. Going quite well 
so far, but still using an old gcc version (3.4.3) to build a newer one within 
the pkgsrc ecosystem, however, seems I need Python 
first. whenever I attempt to build any version of python 3.x I am dropped out 
with this:

ld: fatal: library -lcrypt: not found

...which leads to 

ERROR: The following files are in the PLIST but not in 
/usr/pkgsrc/lang/python39/work/.destdir/usr/pkg:
ERROR: 
/usr/pkgsrc/lang/python39/work/.destdir/usr/pkg/lib/python3.9/lib-dynload/_crypt.so

Hoping there's something simple I need to install first like a crypt library, 
any ideas appreciated!

John

-- 
j...@sdf.org
SDF Public Access UNIX System - http://sdf.org

Re: SCSI2SD

[John H. Reinhardt via cctalk]

On 5/22/2021 10:29 AM, Zane Healy wrote:

On May 21, 2021, at 5:15 PM, John H. Reinhardt via cctalk 
 wrote:


On 5/21/2021 3:41 PM, Zane Healy via cctalk wrote:

Does anyone have experience using a SCSI2SD board to replace a Hard Drive on a 
VAXstation or an AlphaStation?  I’m thinking about using them on some of my 
systems to reduce the amount of noise.  I’ve gotten used to a quiet office. :-)

Zane





I've got a SCSI2SD V5 in my MicroVAX 3100 M95. It sits on the SCSI bus along 
with the CDrom drive and a couple of 18GB Compaq/Seagate drives.  I've also got 
a SCSI2SD V6 in each of my two AlphaSever DS10 systems.  I had a few issues 
with the MV and an earlier version of the V5 firmware, but the last few 
versions have been no trouble at all.

In the MV3100 I mounted the SCSI2SD on a 3.5" 3-D printed mount which is mounted on a 
3.5" to 5.25" mount and it's mounted in the front opening next to the CDROM drive.

In the DS10's the 3.5" 3-D printed mount is put in the floppy opening.


This is definitely good info John, how is the SCSI2SD performance on the 
DS10’s?  I’m pondering using either an AlphaStation 200 4/233 or a AlphaStation 
500/333 as a workstation, rather than my DEC PWS 433a or my Compaq XP1000/667, 
simply due to power usage, and heat generation.

I just placed an order for the initial 4 V5.2 boards I’ll need.  Once they have 
V6 boards back in stock, I’ll need to order a couple of those as well.  These 
should definitely help reduce heat, noise, and power consumption.

Zane




Zane,

  They perform adequately.  They are no speed demons for sure since they're basically a SCSI-2 
(there is a SCSI-2 Mode enable option) disk.  They go about as fast as most drives with a 50-pin 
interface do. It's been a while since I configured them but I'm sure I have them set to the fastest 
speed.  The SCSI2SD utility for V6 has a dropdown box with speed choices and mine are either set to 
"Synch, 10MB/s" or to "No Limit (safe)".

  Truthfully though I haven't used them in a while in the DS10's since I did an 
experiment with a P410 SmartArray card with two 256GB Samsung SSD's and it 
worked (and is still working).  The only downside to that is they have to be 
configured somewhere else since the Alpha MSA utility doesn't understand them.  
But once configured (both cards and SSD) then they work great.  The other 
downside is no boot support so I need to either boot from a normal SCSI drive 
or the SCSI2SD.  I've thought about the latter, but haven't tried it yet.  
Though I have booted from the SCSI2SD before.

  I'm pretty sure at some point I experimented with using HBVS between two 
SCSI2SD drives (partitions on the same SD since I only have one card in each 
system) and it worked.  But I can't find any notes so it might be something I 
intended to do but didn't.

Regards,
 John H. Reinhardt

Re: SCSI2SD

[John H. Reinhardt via cctalk]

On 5/21/2021 3:41 PM, Zane Healy via cctalk wrote:

Does anyone have experience using a SCSI2SD board to replace a Hard Drive on a 
VAXstation or an AlphaStation?  I’m thinking about using them on some of my 
systems to reduce the amount of noise.  I’ve gotten used to a quiet office. :-)

Zane





I've got a SCSI2SD V5 in my MicroVAX 3100 M95. It sits on the SCSI bus along 
with the CDrom drive and a couple of 18GB Compaq/Seagate drives.  I've also got 
a SCSI2SD V6 in each of my two AlphaSever DS10 systems.  I had a few issues 
with the MV and an earlier version of the V5 firmware, but the last few 
versions have been no trouble at all.

In the MV3100 I mounted the SCSI2SD on a 3.5" 3-D printed mount which is mounted on a 
3.5" to 5.25" mount and it's mounted in the front opening next to the CDROM drive.

In the DS10's the 3.5" 3-D printed mount is put in the floppy opening.

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

Re: Looking for VAXSET Software Engineering Tools for VMS 4.x

[John H. Reinhardt via cctalk]

On 4/17/2021 2:15 AM, Mark J. Blair via cctalk wrote:



On Apr 16, 2021, at 11:38 AM, Malte Dehling via cctalk  
wrote:

Whether VAXSET is on there or not, I would be very interested in ISOs of
both of these either way!

If Antonio does not mind sharing them a bit more widely, I would also like to 
have ISOs of them. I'm interested in running earlier VMS versions on my 11/730.


I too would be interested if it is possible to get disk images of these two CDs.

--
John H. Reinhardt

Re: DEC H8575-A DB25 to MMJ

[John H. Reinhardt via cctalk]

On 4/1/2021 7:54 PM, Glen Slick via cctalk wrote:


If you want to make up a large number of MMJ cables using some
original DECconnect cable, here is a listing of a 1000ft spool of
original DEC H8240 cable. Some people have bought some of those spools
and reported that they are original DECconnect branded cable:
https://www.ebay.com/itm/162291819594


I can now verify that this is indeed DEC cable.  Boxed and labelled externally 
and internally:

DIGITAL EQUIPMENT CORP
H8240
QTY:1    DATE 5191

Between this and a generic 6-wire silver satin spool (which I also use for 
model railroading uses), I should be set for life.

--

John H. Reinhardt

Re: DEC H8575-A DB25 to MMJ

[John H. Reinhardt via cctalk]

On 4/7/2021 10:37 PM, Ron Pool via cctalk wrote:

I found some more DEC MMJ crimpers that look pretty decent out there on eBay, 
but they're not well labelled.

https://www.ebay.com/itm/Ideal-30-558-Crimp-Die-for-RJ-11-MJ-Modular-Plug-Crimpmaster-Tool-Frame-30-506/333697351548
 $15 plus shipping new (2 avail) MMJ die for ideal crimp frame 30-506.

There are new and used Ideal 30-506 frames on eBay for reasonable prices.  Search for 
"Ideal 30-506".

https://www.ebay.com/itm/Ideal-Twisted-Pair-Kit-33-650-w-Plugs-and-30-506-30-559-30-560-30-558-Dies/265100183244
 $55 plus shipping used kit (2 avail) including above die, other dies, and 
30-506 crimp frame plus cable cutter and stripper.

https://www.ebay.com/itm/IDEAL-TWISTED-PAIR-KIT-45-074/301901645725 $55 free 
ship in US used Ideal kit (without case) similar to above including DEC MMJ and 
other dies and tools, but of a different vintage

And it could be worth searching for Crimpmaster instead of Ideal.  There are 
lots of used Ideal Crimpmaster frames with dies, but not all of them include 
Ideal in the description.  Maybe some of them are DEC RJ-11 MMJ.

 -- Ron Pool





The Ideal Crimpmaster tool looks a lot like the Paladin / Greenlee / Tempo 
tool.  It may be that the Ideal dies will fit.

<https://www.idealind.com/shop/30-506.html>

A search of the Ideal site finds no mention of the 30-558 RJ11 MJ crimp die 
though so perhaps it's out of production there as well. If you find one and 
want it, get it as who knows if they will be available again.

--
John H. Reinhardt

Re: DEC H8575-A DB25 to MMJ

[John H. Reinhardt via cctalk]

On 4/7/2021 10:43 AM, Glen Slick via cctalk wrote:

On Fri, Apr 2, 2021 at 9:53 AM Jonathan Stone  wrote:

  Google Shopping shows the PA2067 MMJ die available at 3 online stores. 
Digi-Key lists it too.

What are the pros and cons of the die and a PA8000 CrimpALL, versus the IEC 
tool ( https://iec.net/product/modular-crimp-tool-for-rj11-dec-mmj-connectors/) 
? If one either already has an RJ45 crimp tool; or doesn't have any crimping 
tool at all?

I can't answer the question about how the Paladin / Greenlee / Tempo
Communications PA8000 CrimpALL + PA2067 MMJ die compares to other
crimping tools. I don't have any first hand comparison knowledge.


I have two of the Paladin Crimpall handles.  I keep a DEC MMJ die (PA2067) in 
one and the other gets swapped with RJ45 and RJ11/12 as needed.  They work well 
and the ratchet handle allows a good amount of crimp pressure.



As far as availability of the PA2067 dies, Mouser and DigiKey say
Obsolete and none in stock. The PA8035 (PA8000 with PA2067) that I
have I bought from Online Components. They now show none in stock for
both the PA8035 and PA2067.

While there might be some of these floating around in inventory
somewhere, I'm skeptical that most that show up in search results for
online stores are actually available. Most likely if an order was
placed it would be canceled after a few days when the seller realizes
they have none in stock and they can no longer order any from the
manufacturer.


There are lots of sources for the crimper handles.  Look for the PA1300 and PA8000 as 
typical examples.  But the dies are fading.  As Glen mentions, the hits you get for the 
PA2067 from Google are all false hits.  The most promising one I found was Gordon 
Electronics, but I confirmed with a phone call this morning that it is a non-stock item 
that they have to order from the factory - so no go there.  I have looked at the GreenLee 
and Tempo web sites and there is very little mentioned.  Tempo has a "Discontinued 
Items" section and you will find the crimper handles and dies listed. I don't know 
when they went out of production.  My assumption is that Paladin was bought by Greenlee 
and then sold to Tempo as it seems Tempo is the most recent source.  In any case, the DEC 
MMJ die is virtually extinct in the wild and the others seem to be going away also.

I've ordered the IEC crimper to see what it's like and to have a backup in case 
something happens to my Paladin.  Hopefully, it is a good tool and IEC keeps it 
in production as it seems to be the only source now.

--

John H. Reinhardt

[sage-support] Re: loading large file

[John H Palmieri]

Another option might have been to preparse separately (using "sage 
-preparse matp11n2.sage" at the shell prompt) and then load the resulting 
Python file.

  John

On Friday, April 2, 2021 at 12:02:38 PM UTC-7 Luis Finotti wrote:

> The solution I found was to increase the recursion limit: I did 
>
> sys.setrecursionlimit(4500)
>
> It was enough for this.
> On Friday, April 2, 2021 at 7:51:42 AM UTC-4 Luis Finotti wrote:
>
>> I produced a very large text file (139MB) containing some input for Sage.
>>
>> The problem is that when I try to load it, I get:
>>
>>
>> sage: load('matp11n2.sage') 
>>
>> --- 
>> RecursionErrorTraceback (most recent call 
>> last) 
>>  in  
>> > 1 load('matp11n2.sage') 
>>
>> ~/src/sage-9.2/local/lib/python3.8/site-packages/sage/misc/persist.pyx 
>> in sage.misc.persist.load (build/cythonized/sage/misc/persis
>> t.c:2558)() 
>>141 
>>142 if sage.repl.load.is_loadable_filename(filename): 
>> --> 143 sage.repl.load.load(filename, globals()) 
>>144 return 
>>145 
>>
>> ~/src/sage-9.2/local/lib/python3.8/site-packages/sage/repl/load.py in 
>> load(filename, globals, attach) 
>>270 add_attached_file(fpath) 
>>271 with open(fpath) as f: 
>> --> 272 exec(preparse_file(f.read()) + "\n", globals) 
>>273 elif ext == '.spyx' or ext == '.pyx': 
>>274 if attach: 
>>
>> RecursionError: maximum recursion depth exceeded during compilation
>>
>> Any ideas on how I could load such file?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/ae9d3d68-6318-4aea-8cf2-ce29ef2687a3n%40googlegroups.com.

Re: DEC H8575-A DB25 to MMJ

[John H. Reinhardt via cctalk]

On 3/31/2021 1:37 AM, idinc--- via cctalk wrote:

hello all

i am looking to purchase qty 2 DEC H8575-A DB25 to MMJ adapters.


Stonewall Cables has been a supplier for a long time. Before getting a crimper 
I bought lots of cables from them.
https://www.stonewallcable.com/oem-equivalent/dec

https://www.stonewallcable.com/dec-h8575-a-eq

And DEC cables/connectors in general:

https://www.stonewallcable.com/catalogsearch/result/?q=dec+mmj

Pacific Cable - I have no experience with them:
http://www.pacificcable.com/Picture_Page.asp?DataName=H8575-A

There are a few actual H8575-A available on EBay
https://www.ebay.com/sch/i.html?_from=R40&_trksid=p2546172.m570.l1313&_nkw=DEC+H8571-A&_sacat=0


anybody have some that they can sell?

also need a couple of mmj to mmj cables, 10' or longer would work.

DEC MMJ plugs are available from:

Cables.Com: https://www.cables.com/dec-mmj-6p6c-modular-plug.html
Pacific Cables: http://www.pacificcable.com/Picture_Page.asp?DataName=MMJ

A DEC MMJ Crimp tool is available from:

IEC: https://iec.net/product/modular-crimp-tool-for-rj11-dec-mmj-connectors/

If you can find them there is a Paladin crimper that you can get a DEC MMJ die. 
 I have one of those, it works sell, but is apparently discontinued.

Cables are available from:

Stonewall Cables has been a supplier for a long time. Before getting a crimper 
I bought lots of cables from them.
https://www.stonewallcable.com/oem-equivalent/dec

Cable Depot:  http://www.cabledepot.com/05MCPhoneMMJ.html
Pacific Cables: 
http://www.pacificcable.com/DEC-Cables-Digital-Equipment-Corporation-Cables.html


thanks

tim

timothy rutherford
t...@nmia.com
505-550-5110



--

John H. Reinhardt

[sage-support] Re: Cannot install Sage 9.2 on macOS 10.15.7 Catalina

[John H Palmieri]

What happens if you install into another location, for example the Desktop?

On Sunday, March 28, 2021 at 9:26:28 AM UTC-7 Anscari wrote:

> I installed the app you suggested but when I open jupyter I find too many 
> bugs. I am not even able to access the jupyter folder created using 
> previous versions. :(
>
> El sábado, 27 de marzo de 2021 a las 19:01:55 UTC+1, Nathan Dunfield 
> escribió:
>
>> Suggest you try the version in development here:
>>
>> https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.0-beta
>>
>> To be clear, it's the same Sage 9.2 as you are trying to install, the 
>> "beta" refers to the packaging method.
>>
>> Nathan
>>
>> On Saturday, March 27, 2021 at 11:58:38 AM UTC-5 Anscari wrote:
>>
>>> I downloaded the binary sage-9.2-OSX_10.15.7_x86_64.app.dmg in order to 
>>> install SageMath 9.2 as an app on my MacBook Pro (Intel Core i7, 2015) 
>>> running macOS Catalina 10.15.7. I already have SageMath 8.0 as an app, 
>>> which I installed with no problem some time ago, but since I don't know of 
>>> a better way to upgrade I am just trying to install the SageMath 9.2 app.
>>>
>>> The download works fine and when I open the dmg and drag the app to 
>>> 'Applications' the app starts copying just fine, but after a few minutes I 
>>> get an error message saying 'The operation can't be completed because you 
>>> don't have permission to access "SageMath-9.2".' and the process stops.
>>>
>>> [image: Screenshot 2021-03-26 at 13.18.03.png]
>>> Copying normally ^
>>>
>>>
>>> [image: Screenshot 2021-03-26 at 13.21.53.png]
>>>
>>> After some minutes this happens ^
>>>
>>>
>>> Do you have any suggestions as to why this might be happening and how to 
>>> solve it?
>>>
>>> Thank you very much!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/0674bbe0-9142-4329-ad6c-dcfcff007578n%40googlegroups.com.

Re: VCF Swap Meet in Wall, NJ

[John H. Reinhardt via cctalk]

On 3/19/2021 8:57 PM, Fred Cisin via cctalk wrote:

On Fri, 19 Mar 2021, Bill Degnan via cctalk wrote:

What about giant squid?  You dont think it can happen to you and then...


There will always be SOMETHING.

I read on the interwebs that Lee Harvey Oswald was hired by JFK to distract the 
press to avoid coverage of the Staten Island Ferry giant squid attack. 
http://www.sioctopusdisaster.com/memorial.html

But, there have been no verified accounts of giant squid attacks in Wall, NJ.


See?  It worked!

--
John H. Reinhardt

[sage-devel] Downgrade R to optional? See #31409.

[John H Palmieri]

Dear all,

You should be aware that ticket #31409 
(https://trac.sagemath.org/ticket/31409) intends to downgrade R to an 
optional package because of difficulties building it on Cygwin. Just 
letting you know in case you care about R being part of Sage and/or you 
have ideas about how to fix the Cygwin build.

(The branch there to downgrade R already has a positive review, by the way. 
I have no position on this, but I thought that more Sage developers should 
be aware.)

-- 
John


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/89dc24fe-ae9e-42fd-ad90-8104d691900bn%40googlegroups.com.

Re: Vax/pdp on ebay

[John H. Reinhardt via cctalk]

On 3/7/2021 1:56 PM, Glen Slick via cctalk wrote:

On Thu, Mar 4, 2021 at 11:25 PM Wayne S via cctalk
 wrote:

Is anyone from this list bidding on this.
If so i’ll back out. Just don’t want it to be “recycled “ and i have room for 
it.

https://www.ebay.com/itm/Digital-DEC-BA23-Lot-Micro-PDP-11-73-VAXstation-3200-x2-VT220-x2-Extras-Docs/224368924502?hash=item343d6e1756:g:zp8AAOSwvWNgO9qe


Sold for $4,900. Looks like a couple of low score bidders got in a
bidding war and really wanted to win.

Nice bit of kit to jumpstart a QBus VAX / PDP collection, but that
price seems just a tad bit too much...

At least I doubt it will be getting recycled anytime soon.


I was watching the auction because I thought I might bid.  Silly me. :-) With 
15 minutes to go, it was $595.  At 10 minutes it was up around $1200.  The last 
2 minutes were something to watch as the price jumped to $2000, then $2400, 
$2700, $3700 and higher.  The last 15 seconds saw the price soar through the 
$4000's and nearly make it to $5000.  By then, I was hoping to see it that 
$5000 mark but it fell just short.

--
John H. Reinhardt

Re: Vax/pdp on ebay

[John H. Reinhardt via cctalk]

I need one for an 11/83 (if I can get my CPU board to run). It's on my "to do" 
list to try to 3-D model one for FMD or resin printing.

--
John H. Reinhardt

On 3/5/2021 10:51 AM, Nigel Johnson via cctalk wrote:

Speaking of badges, I have a BA23 that doesn't have one. It was an 11/73
but that badge is gone, and I am trying to repair an 11/93 to go in there.

Does anybody have a spare 11/73 badge for the BA23 that could be used as
a model for a printed version that says 11/93?  I don't believe there
ever was one for the BA23 chassis!  I have a BA123 micro VAX II badge
going spare if anybody needs it, or to swap for an 11/73!

Cheers,

Nigel


Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype:  TILBURY2591 nw.john...@ieee.org



On 2021-03-05 11:46 a.m., Zane Healy via cctalk wrote:

On Mar 4, 2021, at 1:55 PM, Wayne S via cctalk  wrote:

Is anyone from this list bidding on this.
If so i’ll back out. Just don’t want it to be “recycled “ and i have room for 
it.

https://www.ebay.com/itm/Digital-DEC-BA23-Lot-Micro-PDP-11-73-VAXstation-3200-x2-VT220-x2-Extras-Docs/224368924502?hash=item343d6e1756:g:zp8AAOSwvWNgO9qe

I’m relieved it’s not closer to me, or I’d be sorely tempted to go for that.  
That’s a seriously nice pile of gear.  Especially as they have the right badges 
on the pedestals.  I’m more interested in downsizing than adding more, but 
that’s exactly the sort of thing that would tempt me.

Zane

Re: Vax/pdp on ebay

[John H. Reinhardt via cctalk]

On 3/5/2021 3:03 AM, Ed C. via cctalk wrote:

Not me, but please ping me if you do and would like to part one of the
11/73. Regards.

On Fri, Mar 5, 2021 at 8:25 AM Wayne S via cctalk 
wrote:


Is anyone from this list bidding on this.
If so i’ll back out. Just don’t want it to be “recycled “ and i have room
for it.


https://www.ebay.com/itm/Digital-DEC-BA23-Lot-Micro-PDP-11-73-VAXstation-3200-x2-VT220-x2-Extras-Docs/224368924502?hash=item343d6e1756:g:zp8AAOSwvWNgO9qe






Sent from my iPhone



That's a nice collection of DEC kit. The PDP-11/73 pedestal would be nice.

--
John H. Reinhardt

Re: digital group's Richard Bemis

[John H. Reinhardt via cctalk]

On 3/5/2021 8:30 AM, Liam Proven via cctalk wrote:

On Thu, 4 Mar 2021 at 05:23, Brad H via cctalk  wrote:

Hi there,

I am working on a 30 minute historical video about the digital group.

[Spelling out my thought process]

"the digital group" -- so he means Digital Equipment Corporation.
Never heard them called a "group" but fine.


when dg was still operational

"dg"? Huh? He means DG? Data General?

Well which _do_ you mean?

Digital meant Digital Equipment Corporation meant DEC.

DG meant Data General.

Neither was anything "group".

I don't know who you mean...





No, he means "The Digital Group". It was a microcomputer company in the 
1975-1979 time frame.

http://bytecollector.com/the_digital_group.htm

https://en.wikipedia.org/wiki/The_Digital_Group

--
John H. Reinhardt

Re: Massbus - was: Re: VAX 11/750

[John H. Reinhardt via cctalk]

On 2/26/2021 8:40 AM, Lars Brinkhoff via cctalk wrote:

Toby Thain wrote:

Rich Alderson wrote:

You could ask our friends Keith Perez (Massbus Disk Emulator v1) and
Bruce Sherry (MDE v2) about it, or even ask me.  ...  produced, and
we had to do something.  My brilliant friend Keith sat down with a
logic analyzer and an RP06 attached to a KL-10, and proceeded to
spend the next two years (when not called on for other projects)
creating a disk emulator. ...

Later, Bruce came on board as the museum was ramping up, and redid
the design in a Xilinx chip with VHDL. ...

Are the above projects published?

See here:

https://github.com/livingcomputermuseum?tab=repositories

Also here is Rich's announcement on DEC-10 day of 2017


Happy DEC-10 Day!

It is my honor to announce that we at Living Computers: Museum + Labs
are releasing to the computing community our Massbus Disk Emulator
and all the associated software.  This device connects via Massbus
cables to the RH10 and RH20 interfaces on KI-10 and KL-10 systems, to
the RH11 interface on KS-10 and small PDP-11 systems (including the
front end 11/40 on the KL-10), and to the RH70 on the PDP-11/70.  The
MDE provides up to 8 emulated RP06 or RP07 disks (represented by disk
files in the format used by the SimH emulation of these systems).

We expect that it will also work with the RH780 on the VAX-11/780 and
VAX-11/785 although we have not yet tested it in this configuration.

The original MDE was designed by Keith Perez in 2005, and emulated up
to four RP06 drives connected to a KL-10.  The current generation was
a redesign by Bruce Sherry in conjunction with the restoration of our
DECsystem-1070 in 2012, and initially provided eight RP06 drives on
the RH10.  It has undergone continual development, with associated
software created for us by Bob Armstrong, and is now being opened up
for the use of the relevant communities.

To this end, we have placed the design files for the hardware and the
source files for the software to interface with it, along with our
library of Universal Peripheral Emulator routines, on public access
repositories at Github.  The URLs for these repositories are

 https://github.com/livingcomputermuseum/MDE2

 https://github.com/livingcomputermuseum/MBS

 https://github.com/livingcomputermuseum/UPELIB

These are released under a very liberal license which will allow for
free use of the MDE by any interested party.

Happy Dec-10 Day!

 Rich


Richard Alderson, Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134

Cell: (206) 465-2916
Desk: (206) 342-2239

http://www.livingcomputerss.org/





--
John H. Reinhardt

[sage-release] Re: Sage 9.3.beta7 released

[John H Palmieri]

I just noticed something which has been happening for all of the 9.3 beta 
releases, maybe before that. In the dochtml.log file, I see the message

Help file /Applications/usr/share/giac/doc/fr/aide_cas not found

(This is on OS X.) That's a strange path — there is no /Applications/usr — 
so it's not surprising that it's not found. What is producing this message? 
The path should be fixed.

-- 
John

On Sunday, February 7, 2021 at 2:04:42 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 
>
> 8453ffb849 (tag: 9.3.beta7, trac/develop) Updated SageMath version to 
> 9.3.beta7
> 6096110e06 Trac #30517: MemoryError in doctesting 
> combinat/designs/gen_quadrangles_with_spread.pyx
> e67fc51749 Trac #31148: MR51: Allow Matplotlib to use system qhull >= 7.2.0
> f3740e8add Trac #31147: Add missing curly braces in latex of Kodaira symbol
> d856033dd6 Trac #31144: refresh the file polyhedron/plot.py
> eb9bae531a Trac #31143: shorten range(0, *) in combinat folder
> 9d4f2d1525 Trac #31140: use ⨂ for unicode of tensor symbol
> 5a4ad12275 Trac #31138: Document WSL Installation
> c8a7960598 Trac #31134: Update setuptools and setuptools_scm
> 45e7ada314 Trac #24459: Segfault in matrix_integer_dense
> 9bdf1d149f Trac #24317: Doctest: Improve conversion of inexact symbolic 
> values
> 85f81e86d3 Trac #21907: Bug in Maxima interface wrt polylog
> 913b025ac5 Trac #31283: 1000× speedup of conjugate of double dense matrices
> bfe6fd9654 Trac #31273: Remove deprecated `form` input for bundle 
> connections
> 00cacf3803 Trac #31272: Improve the documentation for tensor()
> 50c1a5d655 Trac #31270: Remove sage-location's "sage-force-relocate" 
> mechanism, fix script to work without SAGE_ROOT
> 3f5faf58b6 Trac #31266: Signed tensor products does not allow tensor 
> products with non-signed modules
> 1d8b95def5 Trac #31265: changes in kschur to get rid of specific product 
> definition there
> 9c39188e60 Trac #31262: Implement non zero chunks for sparse bitsets
> 35ad55518c Trac #31261: Update pplpy to 0.8.6
> d5581ba0ea Trac #31258: Upgrade cmake to 3.19.3
> 57211cf752 Trac #31257: quo_rem gives wrong answers for 
> LaurentPolynomial_mpair
> b282cf6d2d Trac #31256: more care for pbori
> e8c83f5b70 Trac #31255: Follow Up: Mutability of Sections and Tensor Fields
> 573df518ba Trac #31254: Do not perform unnecesssary subdivisions in 
> matrices
> 09f5b07182 Trac #31239: Add ore_algebra optional package
> 6a5ad3f3eb Trac #31216: tox.ini (local): Add environment variables to skip 
> system package installs and other steps, add mechanism for a local 
> interactive shell
> 1ad5cb3ec9 Trac #31197: Use bitsets/binary matrix for edges of dense graphs
> 3925e96e0a Trac #31196: Code Improvements for Mutability module
> 01ad25fc3f Trac #31194: Make Class with Mutability compatible with 
> require_mutable wrapper
> 99d4307f61 Trac #31121: Further refactoring of eta products file
> 6dda91cd3b Trac #31035: Remove mathjax configuration/symlink from jupyter 
> notebook
> 2c32dab63a Trac #27103: Enable SIMD-instructions for Bitsets
> 6b64832a66 Trac #21783: QEPCAD: get rid of qepcad bits in 
> src/bin/sage-location
> 5e36f5d72b Trac #31271: MR52: upgrade ubuntu system in docker image
> 7823deee62 Trac #31263: Broken `sage -b`
> f0ca7dfb31 Trac #30725: macOS: spkg-install scripts that force use of 
> clang conflict with '-march=native'
> aadda8f345 Trac #30731: Replace use of build/bin/sage-python23 by just 
> python3
> 70291edd23 Trac #14821: Weird error in exponential integral
> 583e83e86d Trac #7423: plot3d can't handle log(0)
> d7c2285977 Trac #31243: Stronger Categories for Manifold Examples: 
> Connectedness
> 6ef10b86c1 Trac #31240: sage-flatsurf pip package
> 513046f42d Trac #31238: Add admcycles as an optional package
> a33370064e Trac #31237: Add slabbe as an optional package
> 712ca6e170 Trac #31234: multiplication of matrix with zero columns or rows 
> fails
> 8c3804cc20 Trac #31233: Categories for Homset of Manifolds do not meet
> e1bd5e3fe5 Trac #31229: more typing annotations in Tamari interval posets
> 02d0fc8821 Trac #31226: Generalize face iterator of combinatorial 
> polyhedron to locally branched lattices
> d9745ca3e1 Trac #31224: Add surface-dynamics as a pip package
> 8101d78056 Trac #31221: Alllow arbitrary folder as output directory of 
> docbuild
> 96bac10d15 Trac #31220: Remove test for safe directory while doctesting
> 7eebf61583 Trac #31219: Fix escape of docstring for derivative method
> a704ef5b17 Trac #31215: Documentation of Item Assignment Behavior for 
> Bundle Connections
> c4f0516700 Trac #31212: fix submonoid method when the generating set 
> include the identity
> bf9205aebc Trac #31210: Make it possible to run github workflows manually
> 5477ab510c Trac #31208: Use popcnt and tzcnt to speed up bitsets on Intel 
> and AMD
> 7edddbd058 Trac 

Re: [wsjt-devel] Release 2.4.0...

[John H. Long Jr.]

Mind if I jump in here also?Just trying to setup FST4 tonight for the first time.Please also let me know when one of you are trying FST4 on 160 as I would like to see if I am set up correctly and receiving FST4 messages.Thanks,JohnKW7AUtah, USAJohn H. Long Jr.KW7A1370 N 150ENephi, Utah 84648USA (435) 888-LONG  Admit it ... Life Would be Boring without me! 


 Original Message 
Subject: Re: [wsjt-devel] Release 2.4.0...
From: Jim Brown 
Date: Fri, February 05, 2021 10:58 pm
To: wsjt-devel@lists.sourceforge.net

On 2/5/2021 6:03 PM, k...@earthlink.net wrote:
> Hi, Jim:
> 
> What frequency are you using FST4 on 160m?

I'm using a dial frequency of 1837.5 and offset of about 2.4 kHz, which 
puts TX/RX just below FT8. I'm using that dial frequency so that big FT8 
signals don't limit the dynamic range of the FST4 decoder. And I'm using 
FST4-60, mostly at 5W. Tonight, I turned on the amp for 30-40 minutes, 
but still my only report was from AZ. First night operating worked AZ, 
MS, MI, and OH with 5W. I just shut down and came into the house.

73, Jim K9YC


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [sage-devel] sage -b is broken

[John H Palmieri]

Good, thank you for pointing that ticket out.

On Wednesday, February 3, 2021 at 9:43:46 AM UTC-8 dmo...@deductivepress.ca 
wrote:

> I believe this was fixed by gh-kliem in trac #31263.
>
> On Wednesday, February 3, 2021 at 10:08:45 AM UTC-7 dim...@gmail.com 
> wrote:
>
>> finally :-) (not sure bug or feature)
>>
>> well,
>>
>> make build
>>
>> works
>>
>> On Wed, 3 Feb 2021, 17:05 John H Palmieri,  wrote:
>>
>>> I'm not sure when it happened, but with the latest beta, I see
>>>
>>> % ./sage -b
>>> Makefile:25: *** This Makefile needs to be invoked by 
>>> build/make/install.  Stop.
>>>
>>> -- 
>>> 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 view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/8f906c06-3482-4ed7-ae28-dfedb09013a9n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/sage-devel/8f906c06-3482-4ed7-ae28-dfedb09013a9n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8e8cbcae-bbf5-4287-90f8-599fcf2647ddn%40googlegroups.com.

[sage-devel] sage -b is broken

[John H Palmieri]

I'm not sure when it happened, but with the latest beta, I see

% ./sage -b
Makefile:25: *** This Makefile needs to be invoked by build/make/install.  
Stop.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8f906c06-3482-4ed7-ae28-dfedb09013a9n%40googlegroups.com.

[sage-devel] Re: Problems with 9.3.beta6 + OS X Big Sur

[John H Palmieri]

Right, thank you. Python 3.9 builds successfully.

On Monday, February 1, 2021 at 7:14:29 PM UTC-8 zsc...@gmail.com wrote:

> For the --with-system-python3=no, I don't know what the problem is but I 
> think it was fixed by upgrading to python 3.9 in 
> https://trac.sagemath.org/ticket/30589
>
> On Monday, February 1, 2021 at 9:45:37 PM UTC-5 John H Palmieri wrote:
>
>> On OS X Big Sur (intel), as of the most recent Xcode and homebrew, I am 
>> currently unable to build Sage with either homebrew's Python or with 
>> `./configure --with-system-python3=no`.
>>
>> - With homebrew's Python, actually Sage builds but the documentation does 
>> not (similar problems on both Big Sur and Catalina), ending with
>>
>> 
>> 0   signals.cpython-39-darwin.so0x00010cd40542 
>> print_backtrace + 66
>> 1   signals.cpython-39-darwin.so0x00010cd44167 sigdie + 39
>> 2   signals.cpython-39-darwin.so0x00010cd4406a 
>> cysigs_signal_handler + 282
>> 3   libsystem_platform.dylib0x7fff203bcd7d _sigtramp + 29
>> 4   ??? 0x003f 0x0 + 63
>> 5   libtcl8.6.dylib 0x00032998c72e AtForkPrepare 
>> + 38
>> 6   libsystem_pthread.dylib 0x7fff203781a3 
>> _pthread_atfork_prepare_handlers + 90
>> 7   libSystem.B.dylib   0x7fff2a575934 
>> libSystem_atfork_prepare + 11
>> 8   libsystem_c.dylib   0x7fff2025bb1b fork + 12
>> 9   _posixsubprocess.cpython-39-darwin. 0x00010b63db89 
>> subprocess_fork_exec + 1573
>> 10  Python  0x00010af10904 cfunction_call 
>> + 127
>> 11  Python  0x00010aedffa3 
>> _PyObject_MakeTpCall + 266
>> 12  Python  0x00010af88027 call_function 
>> + 455
>> ...
>> 157 Python  0x00010afcf10f Py_BytesMain + 
>> 42
>> 158 libdyld.dylib   0x7fff20393621 start + 1
>> 
>> Unhandled SIGILL: An illegal instruction occurred.
>> This probably occurred because a *compiled* module has a bug
>> in it and is not properly wrapped with sig_on(), sig_off().
>> Python will now terminate.
>> 
>> ...
>>   File 
>> "/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.3.beta6/local/lib/python3.9/site-packages/sage_setup/docbuild/utils.py",
>>  
>> line 221, in reap_workers
>> w = bring_out_yer_dead(w, task, exitcode)
>>   File 
>> "/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.3.beta6/local/lib/python3.9/site-packages/sage_setup/docbuild/utils.py",
>>  
>> line 157, in bring_out_yer_dead
>> raise WorkerDiedException(
>> sage_setup.docbuild.utils.WorkerDiedException: worker for 
>> ('reference/misc', 'en', 'html', {}) died with non-zero exit code -4
>>
>> - With `./configure --with-system-python3=no`, Python fails to build (on 
>> Big Sur only; it succeeds on Catalina), saying
>>
>> ModuleNotFoundError: No module named 'readline'
>>
>> and
>>
>> ModuleNotFoundError: No module named 'zlib'
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bb4efc7f-f38b-47cc-8ff2-4f7f447aad34n%40googlegroups.com.

[sage-devel] Problems with 9.3.beta6 + OS X Big Sur

[John H Palmieri]

On OS X Big Sur (intel), as of the most recent Xcode and homebrew, I am 
currently unable to build Sage with either homebrew's Python or with 
`./configure --with-system-python3=no`.

- With homebrew's Python, actually Sage builds but the documentation does 
not (similar problems on both Big Sur and Catalina), ending with


0   signals.cpython-39-darwin.so0x00010cd40542 print_backtrace 
+ 66
1   signals.cpython-39-darwin.so0x00010cd44167 sigdie + 39
2   signals.cpython-39-darwin.so0x00010cd4406a 
cysigs_signal_handler + 282
3   libsystem_platform.dylib0x7fff203bcd7d _sigtramp + 29
4   ??? 0x003f 0x0 + 63
5   libtcl8.6.dylib 0x00032998c72e AtForkPrepare + 
38
6   libsystem_pthread.dylib 0x7fff203781a3 
_pthread_atfork_prepare_handlers + 90
7   libSystem.B.dylib   0x7fff2a575934 
libSystem_atfork_prepare + 11
8   libsystem_c.dylib   0x7fff2025bb1b fork + 12
9   _posixsubprocess.cpython-39-darwin. 0x00010b63db89 
subprocess_fork_exec + 1573
10  Python  0x00010af10904 cfunction_call + 
127
11  Python  0x00010aedffa3 
_PyObject_MakeTpCall + 266
12  Python  0x00010af88027 call_function + 
455
...
157 Python  0x00010afcf10f Py_BytesMain + 42
158 libdyld.dylib   0x7fff20393621 start + 1

Unhandled SIGILL: An illegal instruction occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.

...
  File 
"/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.3.beta6/local/lib/python3.9/site-packages/sage_setup/docbuild/utils.py",
 
line 221, in reap_workers
w = bring_out_yer_dead(w, task, exitcode)
  File 
"/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.3.beta6/local/lib/python3.9/site-packages/sage_setup/docbuild/utils.py",
 
line 157, in bring_out_yer_dead
raise WorkerDiedException(
sage_setup.docbuild.utils.WorkerDiedException: worker for 
('reference/misc', 'en', 'html', {}) died with non-zero exit code -4

- With `./configure --with-system-python3=no`, Python fails to build (on 
Big Sur only; it succeeds on Catalina), saying

ModuleNotFoundError: No module named 'readline'

and

ModuleNotFoundError: No module named 'zlib'

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a8e16bb8-e6b7-4116-973a-3b8cb0aan%40googlegroups.com.

[sage-devel] Re: Unable to build develop branch

[John H Palmieri]

I've seen this one, and I don't remember if there is a ticket for it. I 
think it arises from using the version of Python 3 that Apple provides. You 
could install homebrew's Python 3, or you could try building Sage (from 
scratch) with "./configure --with-system-python3=no".

-- 
John

On Saturday, January 23, 2021 at 5:28:00 AM UTC-8 dwb...@gmail.com wrote:

> I cannot build the documentation. It actually crashes python. I'm 
> attaching my
> docbuild log.
>
> I have another problem which is that 'sage -b' does not work. It gives me 
> the error
> "This Makefile needs to be invoked by 'build/make/install'". If I set the 
> parameter
> SAGEPKGCONFIG then it works, but I shouldn't need to do that.
>
> Dan
>
> On Friday, January 22, 2021 at 5:16:28 PM UTC-8 John H Palmieri wrote:
>
>> Great, I'm glad to hear it!
>>
>> Have you run doctests? If so, are there many failures?
>>
>>
>> On Friday, January 22, 2021 at 4:45:59 PM UTC-8 dwb...@gmail.com wrote:
>>
>>>
>>> Contrary to my previous message, Ticket 31183 does fix the problem and I 
>>> can now build sage.
>>>
>>> Thanks,
>>> Dan
>>> On Friday, January 22, 2021 at 3:21:10 PM UTC-8 John H Palmieri wrote:
>>>
>>>> I literally meant "merge that [the branch from #31183] into the develop 
>>>> branch" (or vice versa), not just use the branch from #31183. The develop 
>>>> branch has some crucial pieces for building Sage in Big Sur.
>>>>
>>>>   John
>>>>
>>>> On Friday, January 22, 2021 at 11:30:57 AM UTC-8 dwb...@gmail.com 
>>>> wrote:
>>>>
>>>>> Thanks!
>>>>>
>>>>> But it didn't fix it for me. For me the u/jhpalmieri/scipy-big-sur 
>>>>> <https://trac.sagemath.org/git-merger/470ffac111a769b3f2b02631e5174ff6fa483f2b>
>>>>>  fails 
>>>>> in numpy and
>>>>> doesn't get to scipy. So I merged the change in #31166 (addressing 
>>>>> numpy) into
>>>>> the scipy-big-sur branch and that fails to build in scipy again.
>>>>>
>>>>> Dan
>>>>>
>>>>> On Thursday, January 21, 2021 at 8:09:14 PM UTC-8 John H Palmieri 
>>>>> wrote:
>>>>>
>>>>>> Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix 
>>>>>> that. Merging that into the develop branch works for me.
>>>>>>
>>>>>> -- 
>>>>>> John
>>>>>>
>>>>>>
>>>>>> On Thursday, January 21, 2021 at 8:03:55 PM UTC-8 dwb...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> I'm unable to build the develop branch since upgrading my iMac to 
>>>>>>> Big Sur. I have python3 and scipy installed through homebrew. In 
>>>>>>> /usr/local/bin I have a symbolic link from python to python3.
>>>>>>>
>>>>>>> Although I have scipy through homebrew, Sage insists on installing 
>>>>>>> the spkg. In previous build attempts (in late December) the build 
>>>>>>> failed in 
>>>>>>> numpy.
>>>>>>>
>>>>>>> I'm attaching my scipy.1.5.4.log. I would appreciate any suggestions.
>>>>>>>
>>>>>>> Thank you,
>>>>>>> Daniel Bump
>>>>>>>
>>>>>>>
>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/260952ca-ec7a-461e-b69f-6adecbdf260en%40googlegroups.com.

[sage-devel] Re: Unable to build develop branch

[John H Palmieri]

Great, I'm glad to hear it!

Have you run doctests? If so, are there many failures?


On Friday, January 22, 2021 at 4:45:59 PM UTC-8 dwb...@gmail.com wrote:

>
> Contrary to my previous message, Ticket 31183 does fix the problem and I 
> can now build sage.
>
> Thanks,
> Dan
> On Friday, January 22, 2021 at 3:21:10 PM UTC-8 John H Palmieri wrote:
>
>> I literally meant "merge that [the branch from #31183] into the develop 
>> branch" (or vice versa), not just use the branch from #31183. The develop 
>> branch has some crucial pieces for building Sage in Big Sur.
>>
>>   John
>>
>> On Friday, January 22, 2021 at 11:30:57 AM UTC-8 dwb...@gmail.com wrote:
>>
>>> Thanks!
>>>
>>> But it didn't fix it for me. For me the u/jhpalmieri/scipy-big-sur 
>>> <https://trac.sagemath.org/git-merger/470ffac111a769b3f2b02631e5174ff6fa483f2b>
>>>  fails 
>>> in numpy and
>>> doesn't get to scipy. So I merged the change in #31166 (addressing 
>>> numpy) into
>>> the scipy-big-sur branch and that fails to build in scipy again.
>>>
>>> Dan
>>>
>>> On Thursday, January 21, 2021 at 8:09:14 PM UTC-8 John H Palmieri wrote:
>>>
>>>> Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix that. 
>>>> Merging that into the develop branch works for me.
>>>>
>>>> -- 
>>>> John
>>>>
>>>>
>>>> On Thursday, January 21, 2021 at 8:03:55 PM UTC-8 dwb...@gmail.com 
>>>> wrote:
>>>>
>>>>> I'm unable to build the develop branch since upgrading my iMac to Big 
>>>>> Sur. I have python3 and scipy installed through homebrew. In 
>>>>> /usr/local/bin 
>>>>> I have a symbolic link from python to python3.
>>>>>
>>>>> Although I have scipy through homebrew, Sage insists on installing the 
>>>>> spkg. In previous build attempts (in late December) the build failed in 
>>>>> numpy.
>>>>>
>>>>> I'm attaching my scipy.1.5.4.log. I would appreciate any suggestions.
>>>>>
>>>>> Thank you,
>>>>> Daniel Bump
>>>>>
>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/960cb430-8313-4fc5-8071-cd1220ba7746n%40googlegroups.com.

[sage-devel] Re: Unable to build develop branch

[John H Palmieri]

I literally meant "merge that [the branch from #31183] into the develop 
branch" (or vice versa), not just use the branch from #31183. The develop 
branch has some crucial pieces for building Sage in Big Sur.

  John

On Friday, January 22, 2021 at 11:30:57 AM UTC-8 dwb...@gmail.com wrote:

> Thanks!
>
> But it didn't fix it for me. For me the u/jhpalmieri/scipy-big-sur 
> <https://trac.sagemath.org/git-merger/470ffac111a769b3f2b02631e5174ff6fa483f2b>
>  fails 
> in numpy and
> doesn't get to scipy. So I merged the change in #31166 (addressing numpy) 
> into
> the scipy-big-sur branch and that fails to build in scipy again.
>
> Dan
>
> On Thursday, January 21, 2021 at 8:09:14 PM UTC-8 John H Palmieri wrote:
>
>> Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix that. 
>> Merging that into the develop branch works for me.
>>
>> -- 
>> John
>>
>>
>> On Thursday, January 21, 2021 at 8:03:55 PM UTC-8 dwb...@gmail.com wrote:
>>
>>> I'm unable to build the develop branch since upgrading my iMac to Big 
>>> Sur. I have python3 and scipy installed through homebrew. In /usr/local/bin 
>>> I have a symbolic link from python to python3.
>>>
>>> Although I have scipy through homebrew, Sage insists on installing the 
>>> spkg. In previous build attempts (in late December) the build failed in 
>>> numpy.
>>>
>>> I'm attaching my scipy.1.5.4.log. I would appreciate any suggestions.
>>>
>>> Thank you,
>>> Daniel Bump
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/426b1255-daea-4cfa-a4af-1ff42029f9acn%40googlegroups.com.

[sage-devel] Re: Unable to build develop branch

[John H Palmieri]

Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix that. 
Merging that into the develop branch works for me.

-- 
John


On Thursday, January 21, 2021 at 8:03:55 PM UTC-8 dwb...@gmail.com wrote:

> I'm unable to build the develop branch since upgrading my iMac to Big Sur. 
> I have python3 and scipy installed through homebrew. In /usr/local/bin I 
> have a symbolic link from python to python3.
>
> Although I have scipy through homebrew, Sage insists on installing the 
> spkg. In previous build attempts (in late December) the build failed in 
> numpy.
>
> I'm attaching my scipy.1.5.4.log. I would appreciate any suggestions.
>
> Thank you,
> Daniel Bump
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bc5e2f69-672c-416e-910c-8f92e9f6e596n%40googlegroups.com.

Re: [Evolution] Safety of removing .cache files

[Dr. John H. Lauterbach]

I was able to remove the .cache files without a problem.  I closed Evolution, 
used Nemo with
elevated permissions to delete the files.  A restarted Evolution.  Problem 
solved.  Thank you to
all for your comments.  John


On Fri, 2021-01-01 at 14:43 -0700, Zan Lynx wrote:
> On 1/1/21 1:25 PM, Andre Klapper via evolution-list wrote:
> > On Fri, 2021-01-01 at 12:18 -0700, Zan Lynx wrote:
> > On 12/31/20 5:19 AM, Patrick O'Callaghan wrote:
> > > It's always safe to remove cached files. Evo will just recreate them
> > > if
> > > needed. Just be sure that Evo isn't running when you do it.
> > 
> > That is quite a caveat to add on there.
> > 
> > Evolution has so many small daemon pieces that it is almost impossible
> > to tell if it is "running" and nearly impossible to prevent it from running.
> > 
> > No. It's easily possible not to run Evolution: Just don't start it.
> 
> Yeah, right. I know for a fact that these Evolution data server bits 
> will access data when you least expect it. I just haven't looked 
> recently to see what particular data is used.
> 
> > 
> > You seem to mix up two very different things:
> > Evolution and evolution-data-server.
> > 
> > I don't use Evolution on this Ubuntu machine. I've never configured it.
> > 
> > Then I wonder what brings you to this mailing list...
> 
> I have used Evolution in the past. I've even done development on it. 
> Mostly bug fixes and attempts at bug fixes. Trying to make Evolution 
> work for a linux-kernel virtual folder without becoming completely 
> confused or crashing with a 3 GB memory leak, for example.
> 
> Or trying to batch edit a bunch of downloaded email using Perl scripts.
> 
> > 
> > And yet there are four /usr/libexec/evolution-* processes running. If
> > you kill one DBUS semi-randomly restarts it.
> > 
> > First there were "so many small daemon pieces". Now there are only four?
> > I can't make much sense out of this conversation so far.
> 
> Yeah I think I recognize your name from past conversations and you never 
> have been willing to understand other people's problems.
> 
> If you actually know for a fact that the cache files will only by 
> touched by the Evolution GUI client then just say so.
> 

___
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] Safety of removing .cache files

[Dr. John H. Lauterbach]

Is it safe to delete
/home/johnl/.cache/evolution/mail/e73fb70d2e40e23bc8fc94509b23c9adc77cc577/folders/Bulk
Mail/cur/09/419787 ?

Above directory refers to the "Bulk Mail" account on an IMAP email account from 
bellsouth.net.  I
cannot delete such a folder on my evolution email account.  My evolution 
version is 3.38.1-1.

I have other PC's (Win 10 -- Outlook 365) with the same email account  and 
folders and have no
problem deleting undesired email in the Bulk Mail account.

Thank you,

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: PDP-8 memory card on eBay?

[John H. Reinhardt via cctalk]

On 12/30/2020 5:36 AM, Al Kossow via cctalk wrote:

On 12/30/20 3:19 AM, Noel Chiappa via cctalk wrote:

Anyone recognize this card:

    https://www.ebay.com/itm/313323417718

I looked, and it doesn't seem to be any of those for a PDP-11. However, I
see the DRAM array is 12x4 chips, which makes me think it might be for a
PDP-8?

   Noel



it's a 32k 8a memory board



If it helps, when you zoom in on the red card it says MS8-CA.  Looks like the 
listing has ended but no buyer.

--
John H. Reinhardt

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

[John H Palmieri]

With OS X 11.1, I am unable to build Sage at all. With 9.3.beta5 as well as 
earlier releases, cffi fails:

Installing cffi-1.14.3
Traceback (most recent call last):
  File 
"/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.3.beta5/local/var/tmp/sage/build/cffi-1.14.3/src/setup.py",
 
line 152, in 
if 'darwin' in sys.platform and macosx_deployment_target() >= (10, 15):
  File 
"/Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.3.beta5/local/var/tmp/sage/build/cffi-1.14.3/src/setup.py",
 
line 76, in macosx_deployment_target
return tuple(map(int, 
get_config_var("MACOSX_DEPLOYMENT_TARGET").split('.')))
AttributeError: 'int' object has no attribute 'split'
Error: could not determine package name

numpy fails with a similar error. If I patch both to handle this (by 
calling 'str', as in 'str(get_config_var(...))'), then scipy fails with an 
error that I don't know how to fix, as reported at 
https://trac.sagemath.org/ticket/30651.


On Monday, December 28, 2020 at 11:10:36 AM UTC-8 John H Palmieri wrote:

> I've been having problems with computers running Mac OS for several Sage 
> releases now. With OS X 10.15.7 and a pretty full homebrew installation, 
> cypari fails:
>
>   cypari2/gen.c:23742:70: error: too many arguments to function call, 
> expected 3, have 4
> __pyx_v__ret = asympnum0(__pyx_v__expr, __pyx_v_k, __pyx_v__alpha, 
> __pyx_v_precision);
>~   
> ^
>   /usr/local/include/pari/paripriv.h:101:1: note: 'asympnum0' declared here
>   GEN  asympnum0(GEN u, GEN alpha, long prec);
>   ^
>   cypari2/gen.c:28023:18: error: implicit declaration of function 
> 'bnfcompress' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
> __pyx_v__ret = bnfcompress(__pyx_v__bnf);
>^
>   cypari2/gen.c:28023:16: warning: incompatible integer to pointer 
> conversion assigning to 'GEN' (aka 'long *') from 'int' [-Wint-conversion]
> __pyx_v__ret = bnfcompress(__pyx_v__bnf);
>  ^ ~
>   cypari2/gen.c:79145:52: error: too few arguments to function call, 
> expected 3, have 2
> __pyx_v__ret = lfuntwist(__pyx_v__L, __pyx_v__chi);
>~ ^
>   /usr/local/include/pari/paridecl.h:4164:1: note: 'lfuntwist' declared 
> here
>   GEN lfuntwist(GEN ldata1, GEN ldata2, long bitprec);
>   ^
>   cypari2/gen.c:80115:70: error: too many arguments to function call, 
> expected 3, have 4
> __pyx_v__ret = limitnum0(__pyx_v__expr, __pyx_v_k, __pyx_v__alpha, 
> __pyx_v_precision);
>~   
> ^
>   /usr/local/include/pari/paripriv.h:125:1: note: 'limitnum0' declared here
>   GEN  limitnum0(GEN u, GEN alpha, long prec);
>   ^
>   cypari2/gen.c:101823:18: error: implicit declaration of function 
> 'nfbasis_gp' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
> __pyx_v__ret = nfbasis_gp(__pyx_v__T);
>^
>   cypari2/gen.c:101823:18: note: did you mean 'nfbasis'?
>   /usr/local/include/pari/paridecl.h:2231:9: note: 'nfbasis' declared here
>   GEN nfbasis(GEN x, GEN *y);
>   ^
>   cypari2/gen.c:101823:16: warning: incompatible integer to pointer 
> conversion assigning to 'GEN' (aka 'long *') from 'int' [-Wint-conversion]
> __pyx_v__ret = nfbasis_gp(__pyx_v__T);
>  ^ ~~
>   cypari2/gen.c:112854:16: warning: incompatible pointer to integer 
> conversion assigning to 'long' from 'GEN' (aka 'long *'); dereference with 
> * [-Wint-conversion]
> __pyx_v__ret = permorder(__pyx_v__x);
>  ^ ~
>*
>   cypari2/gen.c:116073:18: error: implicit declaration of function 
> 'isirreducible' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
> __pyx_v__ret = isirreducible(__pyx_v__pol);
>^
>   cypari2/gen.c:116073:18: note: did you mean 'polisirreducible'?
>   /usr/local/include/pari/paridecl.h:4812:9: note: 'polisirreducible' 
> declared here
>   longpolisirreducible(GEN x);
>   ^
>   cypari2/gen.c:124325:49: error: too few arguments to function call, 
> expected 3, have 2
> __pyx_v__ret = qfbsolve(__pyx_v__Q, __pyx_v__p);
>   ^
>   /usr/local/include/pari/paridecl.h:1880:1: note: 'qfbsolve' declared here
>   GEN qfbsolve(GEN Q, GEN n, long flag);
>   ^
>   cypari2/gen.c:134243:69: error: too many arguments to function call, 
> expected 3, have 4
> __pyx_v__ret = rnfkummer(__pyx_v__bnr, __pyx_v__subgp, __pyx_v_d, 
> __pyx_v_precision);
>

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

[John H Palmieri]

I've been having problems with computers running Mac OS for several Sage 
releases now. With OS X 10.15.7 and a pretty full homebrew installation, 
cypari fails:

  cypari2/gen.c:23742:70: error: too many arguments to function call, 
expected 3, have 4
__pyx_v__ret = asympnum0(__pyx_v__expr, __pyx_v_k, __pyx_v__alpha, 
__pyx_v_precision);
   ~   
^
  /usr/local/include/pari/paripriv.h:101:1: note: 'asympnum0' declared here
  GEN  asympnum0(GEN u, GEN alpha, long prec);
  ^
  cypari2/gen.c:28023:18: error: implicit declaration of function 
'bnfcompress' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__pyx_v__ret = bnfcompress(__pyx_v__bnf);
   ^
  cypari2/gen.c:28023:16: warning: incompatible integer to pointer 
conversion assigning to 'GEN' (aka 'long *') from 'int' [-Wint-conversion]
__pyx_v__ret = bnfcompress(__pyx_v__bnf);
 ^ ~
  cypari2/gen.c:79145:52: error: too few arguments to function call, 
expected 3, have 2
__pyx_v__ret = lfuntwist(__pyx_v__L, __pyx_v__chi);
   ~ ^
  /usr/local/include/pari/paridecl.h:4164:1: note: 'lfuntwist' declared here
  GEN lfuntwist(GEN ldata1, GEN ldata2, long bitprec);
  ^
  cypari2/gen.c:80115:70: error: too many arguments to function call, 
expected 3, have 4
__pyx_v__ret = limitnum0(__pyx_v__expr, __pyx_v_k, __pyx_v__alpha, 
__pyx_v_precision);
   ~   
^
  /usr/local/include/pari/paripriv.h:125:1: note: 'limitnum0' declared here
  GEN  limitnum0(GEN u, GEN alpha, long prec);
  ^
  cypari2/gen.c:101823:18: error: implicit declaration of function 
'nfbasis_gp' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__pyx_v__ret = nfbasis_gp(__pyx_v__T);
   ^
  cypari2/gen.c:101823:18: note: did you mean 'nfbasis'?
  /usr/local/include/pari/paridecl.h:2231:9: note: 'nfbasis' declared here
  GEN nfbasis(GEN x, GEN *y);
  ^
  cypari2/gen.c:101823:16: warning: incompatible integer to pointer 
conversion assigning to 'GEN' (aka 'long *') from 'int' [-Wint-conversion]
__pyx_v__ret = nfbasis_gp(__pyx_v__T);
 ^ ~~
  cypari2/gen.c:112854:16: warning: incompatible pointer to integer 
conversion assigning to 'long' from 'GEN' (aka 'long *'); dereference with 
* [-Wint-conversion]
__pyx_v__ret = permorder(__pyx_v__x);
 ^ ~
   *
  cypari2/gen.c:116073:18: error: implicit declaration of function 
'isirreducible' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__pyx_v__ret = isirreducible(__pyx_v__pol);
   ^
  cypari2/gen.c:116073:18: note: did you mean 'polisirreducible'?
  /usr/local/include/pari/paridecl.h:4812:9: note: 'polisirreducible' 
declared here
  longpolisirreducible(GEN x);
  ^
  cypari2/gen.c:124325:49: error: too few arguments to function call, 
expected 3, have 2
__pyx_v__ret = qfbsolve(__pyx_v__Q, __pyx_v__p);
      ^
  /usr/local/include/pari/paridecl.h:1880:1: note: 'qfbsolve' declared here
  GEN qfbsolve(GEN Q, GEN n, long flag);
  ^
  cypari2/gen.c:134243:69: error: too many arguments to function call, 
expected 3, have 4
__pyx_v__ret = rnfkummer(__pyx_v__bnr, __pyx_v__subgp, __pyx_v_d, 
__pyx_v_precision);
   ~  
^
  /usr/local/include/pari/paridecl.h:4110:1: note: 'rnfkummer' declared here
  GEN rnfkummer(GEN bnr, GEN subgroup, long prec);
  ^
  cypari2/gen.c:145599:18: error: implicit declaration of function 
'zetamult0' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__pyx_v__ret = zetamult0(__pyx_v__s, __pyx_v__T, __pyx_v_precision);
   ^
  cypari2/gen.c:145599:18: note: did you mean 'zetamult'?
  /usr/local/include/pari/paridecl.h:5345:9: note: 'zetamult' declared here
  GEN zetamult(GEN avec, long prec);
  ^
  cypari2/gen.c:145599:16: warning: incompatible integer to pointer 
conversion assigning to 'GEN' (aka 'long *') from 'int' [-Wint-conversion]
__pyx_v__ret = zetamult0(__pyx_v__s, __pyx_v__T, __pyx_v_precision);
 ^ 
  cypari2/gen.c:167603:15: error: implicit declaration of function 
'isirreducible' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__pyx_v_t = isirreducible(__pyx_v_self->__pyx_base.g);
^
  4 warnings and 10 errors generated.
  error: command '/usr/bin/gcc' failed with exit code 1


If I use `./configure --with-system-python3=no`, then the build succeeds 
but I get a bunch of doctest failures, I think all of the form

File "src/sage/misc/sagedoc.py", line 646, in sage.misc.sagedoc.format

Re: [sage-support] Re: Install of sage on macOS

[John H Palmieri]

The short answer is that Sage is designed for (among others) research 
mathematicians, who may not have the interest or inclination to learn how 
to install lots of system packages. So from the beginning it included as 
many components as possible. Years ago the presence of MacPorts and other 
similar systems would actually break the Sage build process, so the build 
process may attempt to disable them. Whether it tried to disable them, for 
a long time Sage refused to use any system packages and just built 
everything itself (with a few exceptions, like gcc).

This has been changing recently, and now Sage can use many system packages. 
This is restricted to systems (OS + package manager) used by Sage 
developers, and apparently no developer uses MacPorts, or at least not 
enough to spend time getting Sage to work with it. Homebrew is pretty well 
integrated with the Sage build process.

On Wednesday, December 23, 2020 at 6:11:32 AM UTC-8 u...@ll.mit.edu wrote:

> I looked into build/pgks/* (1.5 GB) and it appears that Sage is trying to 
> be a package manager, in addition to what people probably want it for. 
>
> I guess at version 9.2 it's rather late to ask why it isn't good enough to 
> just list in the README a set of packages that Sage requires to run, and 
> have a minimal config that would check for their presence at install time? 
> Letting user to worry about, e.g., where and how to install OpenSSL-1.1.x 
> or python38?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/06787647-8d63-4e0b-912b-3ddefc516833n%40googlegroups.com.

[sage-devel] Re: Installing SageMath on macOS Big Sur 11.1

[John H Palmieri]

For what it's worth, I was able to build Sage on 11.0 using homebrew, but 
since the upgrade to 11.1, the build fails for me. Discussion at #30651 
(started at #30589, but should be continued at #30651).


On Monday, December 21, 2020 at 2:46:00 PM UTC-8 Samuel Lelievre wrote:

> Supporting macOS 11 Big Sur is tracked at
>
> - Sage Trac ticket 30651
>   Meta-ticket: support macOS 11 Big Sur
>   https://trac.sagemath.org/ticket/30651
>
> Binaries for Sage 9.2 from the Sage download website
> will not work for macOS 11 Big Sur. Hopefully we will
> be able to provide Big Sur binaries for Sage 9.3
>
> In the meantime you might be able to install Sage via Conda
> based on Miniforge, a Conda distribution that already supports
> macOS 11 and even the latest Apple M1 processors.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9127aa8e-5e15-46e8-9625-e9515a1df0abn%40googlegroups.com.

[sage-devel] Re: Sage 9.2 fails to build because of cysignals on macos 10.15.7

[John H Palmieri]

Actually, I can't recommend having Sage build its own Python. I get 
failures with several packages (gmpy2, markupsafe, cython) of this sort:

Successfully built gmpy2
...
ERROR: gmpy2-2.1.0b5-cp38-cp38-macosx_10_9_x86_64.whl is not a supported 
wheel on this platform.


On Monday, December 14, 2020 at 4:02:49 PM UTC-8 John H Palmieri wrote:

> Maybe something is going wrong with using the homebrew version of Python — 
> some conflict somewhere — so could you try
>
> make distclean
> ./configure --with-system-python3=no
> make
>
> (I'm having different problems with the system python: see my posts about 
> MACOSX_DEPLOYMENT_TARGET.)
>
> -- 
> John
>
>
> On Monday, December 14, 2020 at 2:07:11 AM UTC-8 vanhove...@gmail.com 
> wrote:
>
>> Hello,
>>
>> Sage 9.2 fails to build because of cysignals on macos 10.15.7
>>
>> Error installing package cysignals-1.10.2
>>
>> I had been able to build Sage 9.2 from source when it came out. 
>>
>> Then I tried to install the optional package sirocco, the -i optional 
>> failed, so I used -p and tried to rebuild sage from source. Now, I'm 
>> getting this compilation failure.
>>
>> What should I do?
>>
>> Thank you for your help,
>> Pierre Vanhove
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e1217ab0-274c-457f-87b1-98fe51f0b1f5n%40googlegroups.com.

[sage-devel] Re: Sage 9.2 fails to build because of cysignals on macos 10.15.7

[John H Palmieri]

Maybe something is going wrong with using the homebrew version of Python — 
some conflict somewhere — so could you try

make distclean
./configure --with-system-python3=no
make

(I'm having different problems with the system python: see my posts about 
MACOSX_DEPLOYMENT_TARGET.)

-- 
John


On Monday, December 14, 2020 at 2:07:11 AM UTC-8 vanhove...@gmail.com wrote:

> Hello,
>
> Sage 9.2 fails to build because of cysignals on macos 10.15.7
>
> Error installing package cysignals-1.10.2
>
> I had been able to build Sage 9.2 from source when it came out. 
>
> Then I tried to install the optional package sirocco, the -i optional 
> failed, so I used -p and tried to rebuild sage from source. Now, I'm 
> getting this compilation failure.
>
> What should I do?
>
> Thank you for your help,
> Pierre Vanhove
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ec07ba9b-8b4e-4ed9-918a-5b2286b3bd91n%40googlegroups.com.

[sage-devel] MACOSX_DEPLOYMENT_TARGET problems

[John H Palmieri]

I am having problems building Sage with a recently updated homebrew Python 
3.9 on OS X Big Sur, apparently because it sets MACOSX_DEPLOYMENT_TARGET to 
11. (Insert Spinal Tap joke here.) If you run `brew update` on Big Sur, I'm 
guessing that you will run into this.

- There is a problem because of wheel: see https://github.com/pypa/
wheel/issues/385. (Update at #31050.) This leads to failures when building 
gmpy2 and cython.

- There is a problem with cffi because its setup.py has

get_config_var("MACOSX_DEPLOYMENT_TARGET").split('.')

This fails because `get_config_var` returns an `int` in this case rather 
than a string.

(No trac ticket yet. The most recent version of cffi doesn't fix this, as 
far as I can tell, but it's easy to write a patch.)

- There is a similar problem with numpy:

os.environ['MACOSX_DEPLOYMENT_TARGET'] = target
...
   TypeError: str expected, not int

I haven't tried to fix that one yet, so I don't know if there are more 
problems.

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ebae6ed3-7da9-4292-b3e0-e680bac669bbn%40googlegroups.com.

[gem5-users] Re: DRRIP implementation

[John H via gem5-users]

Hi Daniel

Thanks for the reply.

I just wanted to know what is the equivalent of ReplacementCandidate in the
new gem5 in base.hh? I saw that it is defined as a struct in the base.hh of
the previous version.

Thanks

John

On Sun, Nov 22, 2020 at 5:41 AM Daniel Carvalho  wrote:

> Hello, John,
>
> I have sent you the link to the last patch in the series. On the right
> there is a list (called Relation Chain) containing the links to the 4
> patches. I will copy and paste the links here, just in case:
>
> 1st: https://gem5-review.googlesource.com/c/public/gem5/+/37895/1
> 2nd: https://gem5-review.googlesource.com/c/public/gem5/+/37896/1
> 3rd: https://gem5-review.googlesource.com/c/public/gem5/+/37897/1
> 4th: https://gem5-review.googlesource.com/c/public/gem5/+/37898/1
>
> To download them, you go to the top right corner, to the three vertical
> dots. Click on "Download Patch" (NOT Cherry Pick) and then a new window
> will pop up, which allows you to select how you will download. If
> downloading individually, copy the cherry pick command and run locally. If
> you want to download the whole patch chain at once go to the 4th patch in
> the series and select "Checkout".
>
> Ideally you'd want to cherry-pick, because then you'd keep using the
> stable gem5 version; however when cherry picking you will need to
> cherry-pick other patches for this to work (I think picking
> https://gem5-review.googlesource.com/c/public/gem5/+/37135 would be
> enough).
>
> Regarding SRRIP, it is implemented as RRIPRP().
>
> Regards,
> Daniel
> Em sábado, 21 de novembro de 2020 22:40:48 GMT+1, John H <
> h92420...@gmail.com> escreveu:
>
>
> Hi
>
> Thanks for the reply. I don't know how to access the entire code about
> which you mentioned in the email. I can only see a 2 line change in
> ReplacementPolicies.py in the patch. Can you please provide me with the
> entire patch file(all the changes required for DRRIP for your
> implementation) if that's ok with you.That will really help me to
> understand it.
>
> Also is SRRIP implemented in the new gem5?
>
> Thanks
>
> John
>
> On Sat, Nov 21, 2020 at 10:27 AM Daniel Carvalho 
> wrote:
>
> Hello, John,
>
> I have uploaded for review some patches to make DRRIP work:
> https://gem5-review.googlesource.com/c/public/gem5/+/37898
> I believe the code is well documented enough to help you understand how it
> works.
>
> To use DRRIPRP you must set the constituency size and the number of
> entries per team per constituency (team size) on instantiation.
>
> As an example, if:
> - table size=32KB
> - associativity=4
>
> And we want:
> - 32 dedicated sets per team
>
> Then we'd instantiate DRRIPRP(constituency_size=1024, team_size=4)
>
> Since, IIRC, there is no analysis in the paper describing why specifically
> pick complements, instead of implementing DIP's complement-select policy, I
> implemented a "consecutive-select" policy (i.e., pick the first team_size
> entries of the set to be samples for team 0, and the next team_size entries
> of the set to be samples for team 1). If you really want that policy, you
> can implement it easily by modifying DuelingMonitor::initEntry.
>
> Regards,
> Daniel
> Em sábado, 21 de novembro de 2020 03:46:27 GMT+1, John H via gem5-users <
> gem5-users@gem5.org> escreveu:
>
>
> Hello,
>
> I am new with gem5, just getting started. I wanted to implement DRRIP
> cache replacement policy. Have any one of you tried implementing this? Any
> pointers on this would be helpful.
>
> Thanks,
>
> John
> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-users] Adding new replacement policy error

[John H via gem5-users]

Hello,

I tried creating a separate .cc and .hh file for implementing a new
replacement policy and added it to Scons within replacement policies.
However, when i run gem5 build, I get the following error message
build/X86/mem/cache/replacement_policies/ship_rp.cc:13:22: error: 'Params'
does not name a type
 SHIPRP::SHIPRP(const Params *p)
  ^
build/X86/mem/cache/replacement_policies/ship_rp.cc:13:30: error: ISO C++
forbids declaration of 'p' with no type [-fpermissive]
 SHIPRP::SHIPRP(const Params *p)
  ^
build/X86/mem/cache/replacement_policies/ship_rp.cc:13:31: error: invalid
use of incomplete type 'class SHIPRP'
 SHIPRP::SHIPRP(const Params *p)
   ^
In file included from
build/X86/mem/cache/replacement_policies/ship_rp.cc:8:0:
build/X86/params/SHIPRP.hh:4:7: error: forward declaration of 'class SHIPRP'
 class SHIPRP;
   ^
build/X86/mem/cache/replacement_policies/ship_rp.cc:16:1: error: expected
unqualified-id before '{' token
 {
 ^
scons: *** [build/X86/mem/cache/replacement_policies/ship_rp.o] Error 1
scons: building terminated because of errors.

Can you please guide me on how to fix this?

Thanks,

John
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Re: [sage-release] Sage 9.3.beta2 released

[John H Palmieri]

Dima is suggesting the command locale.setlocale(locale.LC_ALL,''), where 
just before the parenthesis should be two single quotes. No quotes after 
the parenthesis. Or if you prefer: locale.setlocale(locale.LC_ALL,"") with 
two double quotes just before the parenthesis.


On Thursday, November 26, 2020 at 3:11:19 PM UTC-8 Kenji Iohara wrote:

> Dima, 
>
>  It gives me 
>
> sage: *import* *locale*  
>
> sage: locale.setlocale(locale.LC_ALL,")" 
> :  
>
>
> or
>
>
> sage: *import* *locale*  
>
> sage: locale.setlocale(locale.LC_ALL,'')''   
>
>   File "", line 1
> locale.setlocale(locale.LC_ALL,'')''
>   ^
> SyntaxError: invalid syntax
>
> or
>
> sage: *import* *locale*  
>
> sage: locale.setlocale(locale.LC_ALL,")''
>
>   File "", line 1
> locale.setlocale(locale.LC_ALL,")''
>^
> SyntaxError: EOL while scanning string literal
>
>
> …. Is this alright ??
>
> 26/11/2020 22:09、Dima Pasechnik のメール:
>
>
>
> On Thu, 26 Nov 2020, 20:39 Kenji Iohara,  wrote:
>
>> I am sorry for this Japanese…..
>>
>>
>> 起動準備中です -  警告メッセージ:this means<< in preparation for booting… 
>>  Warning message >>
>>
>>
>> It gives me
>>
>>
>> sage: *import* *locale*  
>>
>> sage: locale.setlocale(locale.LC_ALL,")  
>>
>>   File "", line 1
>> locale.setlocale(locale.LC_ALL,")
>>  ^
>> SyntaxError: EOL while scanning string literal
>>
>> Does this tell you something ?
>>
>
> oops, sorry, there is " there, but it should be two ' characters one after 
> another.
>
>
>>
>> 26/11/2020 21:35、Dima Pasechnik のメール:
>>
>> A number of tests in your case fail due to a Japanese locale problem, e.g.
>>
>> Failed example:
>>sage.misc.sageinspect.sage_getargspec(r.lm)
>> Expected:
>>ArgSpec(args=['self'], varargs='args', keywords='kwds', defaults=None)
>> Got:
>> 起動準備中です -  警告メッセージ:
>>1: Setting LC_COLLATE failed, using "C"
>>2: Setting LC_TIME failed, using "C"
>>3: Setting LC_MESSAGES failed, using "C"
>>4: Setting LC_MONETARY failed, using "C"
>>ArgSpec(args=['self'], varargs='args', keywords='kwds', defaults=None)
>>
>> I am not sure what's going on there. It looks like these are coming from
>> a non-Sage python module, such as re.
>> What is the output of
>>
>> sage: import locale
>> sage: locale.setlocale(locale.LC_ALL, '')
>>
>> on your system?
>>
>>
>>
>>
>> On Thu, Nov 26, 2020 at 9:53 AM Kenji Iohara  
>> wrote:
>>
>>
>> I have updated to Mac OS 11.0.1 and the compilation from the first built 
>> done without problem !
>> However, for make ptestlong, there are several errors:
>>
>> --
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-release/25C8E4CC-C2F5-4E9A-B5D2-51971F40C185%40gmail.com
>> .
>>
>>
>> 25/11/2020 22:59、Emmanuel Charpentier のメール:
>>
>> On Debian testing running on core 17 + 16 GB RAM, upgrading (including 
>> bootstrap and configure) and running ptestlong led to no transient and one 
>> permanent failure as follows :
>>
>> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 
>> 168.6 --random-seed=0 src/sage/misc/trace.py
>> Running doctests with ID 2020-11-25-22-51-10-7a62d8a2.
>> Git branch: develop
>> Using 
>> --optional=build,cbc,debian,dochtml,dot2tex,fricas,gap_jupyter,memlimit,pari_jupyter,pip,pysingular,saclib,sage,sage_numerical_backends_coin,sage_spkg,singular_jupyter
>> Doctesting 1 file.
>> sage -t --long --warn-long 168.6 --random-seed=0 src/sage/misc/trace.py
>> **
>> File "src/sage/misc/trace.py", line 67, in sage.misc.trace.trace
>> Failed example:
>>print(s.before[s.before.find(b'--'):].decode())
>> Expected:
>>--...
>>ipdb> c
>>2 * 5
>> Got:
>>--Call--
>>
>>
>> /usr/local/sage-9/local/lib/python3.8/site-packages/sage/arith/misc.py(2422)factor()
>>
>>   2420 
>>   2421 
>>-> 2422 def 
>> factor(n,
>>  
>> proof=None,
>>  
>> int_=False,
>>  
>> algorithm='pari',
>>  
>> verbose=0,
>>  
>> **kwds):
>>   2423 """
>>   2424 Return 
>> the factorization 
>> of 
>> ``n``.
>>  
>>  The result depends 
>> on 
>> the
>>
>>ipdb> c
>> 2 * 5CSI-?2004l>
>>
>> **
>> 1 item had failures:
>>   1 of  11 in sage.misc.trace.trace
>>[10 tests, 1 

[sage-support] Re: The pip ssl mess on Mac OS X: ways forwards

[John H Palmieri]

Is it possible to create a binary distribution that relies on a system 
Python 3? Those may already be built with ssl support.

On Sunday, November 22, 2020 at 11:24:45 AM UTC-8 watso...@gmail.com wrote:

>
> Right now pip doesn't work in the binary distributions due to the absence 
> of the ssl module. This is apparently due to licensing restrictions, thanks 
> to the terrible license of OpenSSL.
>
> My suggestion is that we hack together  a build curl+NSS, which is freely 
> redistributable. Then as part of the post-install fixup the curl grabs 
> OpenSSL and the ssl python module, and we run a hacky install of the local 
> copy with pip.  Better options highly welcome.
>
> Sincerely,
> Watson Ladd
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/03af83f0-3419-474f-8ef1-e78166b8d793n%40googlegroups.com.

[gem5-users] Re: DRRIP implementation

[John H via gem5-users]

Hi

Thanks for the reply. I don't know how to access the entire code about
which you mentioned in the email. I can only see a 2 line change in
ReplacementPolicies.py in the patch. Can you please provide me with the
entire patch file(all the changes required for DRRIP for your
implementation) if that's ok with you.That will really help me to
understand it.

Also is SRRIP implemented in the new gem5?

Thanks

John

On Sat, Nov 21, 2020 at 10:27 AM Daniel Carvalho 
wrote:

> Hello, John,
>
> I have uploaded for review some patches to make DRRIP work:
> https://gem5-review.googlesource.com/c/public/gem5/+/37898
> I believe the code is well documented enough to help you understand how it
> works.
>
> To use DRRIPRP you must set the constituency size and the number of
> entries per team per constituency (team size) on instantiation.
>
> As an example, if:
> - table size=32KB
> - associativity=4
>
> And we want:
> - 32 dedicated sets per team
>
> Then we'd instantiate DRRIPRP(constituency_size=1024, team_size=4)
>
> Since, IIRC, there is no analysis in the paper describing why specifically
> pick complements, instead of implementing DIP's complement-select policy, I
> implemented a "consecutive-select" policy (i.e., pick the first team_size
> entries of the set to be samples for team 0, and the next team_size entries
> of the set to be samples for team 1). If you really want that policy, you
> can implement it easily by modifying DuelingMonitor::initEntry.
>
> Regards,
> Daniel
> Em sábado, 21 de novembro de 2020 03:46:27 GMT+1, John H via gem5-users <
> gem5-users@gem5.org> escreveu:
>
>
> Hello,
>
> I am new with gem5, just getting started. I wanted to implement DRRIP
> cache replacement policy. Have any one of you tried implementing this? Any
> pointers on this would be helpful.
>
> Thanks,
>
> John
> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-users] DRRIP implementation

[John H via gem5-users]

Hello,

I am new with gem5, just getting started. I wanted to implement DRRIP cache
replacement policy. Have any one of you tried implementing this? Any
pointers on this would be helpful.

Thanks,

John
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Re: DEC PDP-8/E wanted

[John H. Reinhardt via cctalk]

On 11/20/2020 8:01 AM, Tom Hunter via cctalk wrote:

I know it is the year 2020 but nevertheless what are my chances of finding
a complete and repairable DEC PDP-8/E or as a second choice a PDP-8/I ?

Is there any hope or should I be just content with my SIMH based PiDP-8/I?

Thanks
Tom Hunter

Funny you should mention...

There is a guy in Endicott, NY with a PDP-8/E possibly looking for a new home.  
Posted a couple days ago on the VCF DEC Forum
<http://www.vcfed.org/forum/showthread.php?77602-DEC-de-accession-value-estimates-sought=643984#post643984>


Circumstances require selling off some or all the DECs [ will still have some 
DGs to play with ].
One can often get a general idea of value based on prior open market (like 
eBay) sales but not
enough comparables out there, so would like to get a ball-park idea.

Prefer to see them stay within VCF but because of the amount previously invested I'm not 
able to "give it away"
at hobby prices as I would like in an ideal world. Everything is good shape and 
complete, but not booted up since dry long term storage. May sell some or all 
of it but will try here before eBay. Here's a quick overview, informed and 
straightforward feedback much appreciated.

> Complete PDP-8/E, 8k core, full flip chip/board set (have list), good 
condition, long dry storage.
> Complete PDP-11/05, 8k core, full flip chip/board set (have list) good 
condition, long dry storage.
> DECScope VT-52, good condition nothing missing or damaged from long term 
storage.
> RX-01 dual floppy drive, good condition nothing missing or damaged, from long 
storage.

thanks for your help.
Roger in NY 


Be aware people are telling him his system is probably worth about $1000.  I 
have seen other 8's go for more on Ebay but I don't recall which model.

--

John H. Reinhardt

Re: [sage-support] The best practices for using SageNB in SagaMath 9.1?

[John H Palmieri]

I was hoping that it might be missing dependencies when building sagenb, 
but when I tried this, it didn't help. Maybe something this will work:

./configure --with-python=2 --enable-sagenb=yes 
--enable-flask_autoindex=yes --enable-flask_babel=yes --enable-flask=yes 
--enable-flask_oldsessions=yes --enable-flask_openid=yes 
--enable-flask_silk=yes --enable-twisted=yes --enable-speaklater=yes

followed by

make

(When we switched to Python 3, we made various packages optional, some of 
which are necessary for sagenb. We didn't record them as dependencies of 
sagenb, so "--enable-sagenb=yes" is not sufficient to build them.)



On Wednesday, November 18, 2020 at 4:52:14 AM UTC-8 Xie wrote:

> Yes. If one people  edit the notebook  then the other's browser will auto 
> refresh.  Not a very good experience, just works.
>
>
> 在2020年11月18日星期三 UTC+8 下午5:04:02 写道：
>
>> On Wed, Nov 18, 2020 at 2:42 AM Xie  wrote:
>>
>>> Thanks, but jupyterhub  does not supoort  real-time collaboration now 
>>> though  roadmap  contains  this.
>>
>> there was no RTC (2+ people working on the same sheet in real time) in 
>> sageNB either, if I recall right.
>> The jupyter roadmap is via jupyterlab, I think.
>>
>>
>>
>>>
>>>
>>>
>>> 在2020年11月18日星期三 UTC+8 上午2:07:29 写道：
>>>
 On Tue, Nov 17, 2020 at 2:50 PM Xie  wrote:

> Yes.  I use  *Jupyter* *Notebook*   myself. But  I need share with 
> other people sometimes.  And  *Jupyter* Notebook*  does not* provide 
> a server mode to make the others register an  account.  


 what you need is 
 https://jupyterhub.readthedocs.io/en/latest/

 Here are SageMath-specific instructions: 
 https://opendreamkit.org/2018/10/17/jupyterhub-docker/
 see also 
 https://discourse.jupyter.org/t/trouble-getting-sagemath-up-and-running-solved/1354
 (there conda is recommended, and perhaps it is indeed the quickest way 
 to get everything set up)

 The SageMath docs on this are not complete, but there is work being 
 done on it:
 https://trac.sagemath.org/ticket/30476


  

> Most students use Windows, which is not very friendly to SageMath.   I 
> also tried Cocalc in  Docker. Its UI   is a bit complicated for 
> *newbie*.
> In addition, Ubuntu 18.04 and Archlinux can run SageMath 8.9 without 
> problems.  Now I use  SageMath 8.9 on 
> a Ubuntu 18.04   server to run SageNB.
> 在2020年11月17日星期二 UTC+8 下午9:44:53 写道：
>
>> Hi,
>> SageMath never supported SageNB on Python3, it did not "drop" such a 
>> support.
>> SageNB has been *retired *since SageMath stopped supporting Python2 
>> in version 9.2, and it is high time to switch to
>> another notebook solution, while converters from SageNB are readily 
>> available.
>> This should not be a surprise, as a deprecation notice for SageNB has 
>> been up since Sage 8.5 (i.e. in 2018), I think,
>> see https://github.com/sagemath/sagenb/pull/451 and 
>> https://trac.sagemath.org/ticket/25852
>>
>> Having said that, I could also point out that the latest Arch, as 
>> well as the latest update of Ubuntu 18.04 have been released after Sage 
>> 9.1, so there is absolutely no guarantee that 9.1 would work on them, 
>> with 
>> Python 2 or 3.
>>
>> HTH
>> Dima
>>
>> On Tue, Nov 17, 2020 at 1:07 PM 漂  wrote:
>> >
>> > Hi,  I maintain a  SageNB server since 2011. But as you know, 
>> SageMath has droped the support of SageNB on Python3. Now I want to run 
>> SageNB in SagaMath 9.1. But I failed many times. 
>> >
>> > I follows the codes  by Samuel Lelièvre given  in
>> >  
>> https://ask.sagemath.org/question/53501/get-the-error-nameerror-name-_interact_-is-not-defined-when-run-sagenb/
>>  
>> .
>> >
>> > make configure 
>> > ./configure --with-python=2 --enable-sagenb=yes
>> >  make -s V=0
>> >
>> > I have tried the source "sage-9.1.tar.gz" and  the tag9.1 source in 
>>  github. I test on Archl linux and Ubuntu 18.04.  I always get the 
>> following error. 
>> >
>> > Traceback (most recent call last): File "", line 1, in 
>>  File "_sage_input_6.py", line 8, in  
>> _interact_.SAGE_CELL_ID=1 NameError: name '_interact_' is not defined
>> >
>> >
>> > This problem may be caused by the codes in 
>> sage/local/lib/python2.7/site-packages/sagenb-1.1.3-py2.7.egg/sagenb/notebook/worksheet.py.
>>   
>> In the line ~3145.
>> >
>> > def initialize_sage(self):
>> >   S = self.__sage 
>> >try: 
>> >from . import misc
>> > cmd = '''import base64 
>> > import sagenb.misc.support as _support_ 
>> > import sagenb.notebook.interact as _interact_ 
>> > # for setting current cell id  ''' 
>> > S.execute(cmd)
>> >
>> > I think 'cmd' is not be executed. If I put some error code in 
>> 'cmd', 

[sage-devel] Re: OS X Big Sur progress report

[John H Palmieri]

You can probably eliminate some of the doctest errors with the following 
hack, which may not be the right way to proceed, but at least for me it 
allows doctesting to complete. Some of your other errors may be caused by 
using Python 3.9, and people are working on fixing those.

diff --git a/src/sage/doctest/parsing.py b/src/sage/doctest/parsing.py
index 4e1a6b32e4..bfb7f36940 100644
--- a/src/sage/doctest/parsing.py
+++ b/src/sage/doctest/parsing.py
@@ -40,6 +40,7 @@ optional_regex = re.compile(r'(arb216|arb218|py2|py3|long 
time|not implemented|n
 # which has not been patched, we need to ignore that message.
 # See :trac:`29317`.
 glpk_simplex_warning_regex = re.compile(r'(Long-step dual simplex will be 
used)')
+big_sur_warning_regex = re.compile(r'ld: warning: dylib.*was built for 
newer macOS version .* than being linked.*')
 find_sage_prompt = re.compile(r"^(\s*)sage: ", re.M)
 find_sage_continuation = re.compile(r"^(\s*)\.\.\.\.:", re.M)
 find_python_continuation = re.compile(r"^(\s*)\.\.\.([^\.])", re.M)
@@ -1087,6 +1088,7 @@ class SageOutputChecker(doctest.OutputChecker):
 """
 got = self.human_readable_escape_sequences(got)
 got = glpk_simplex_warning_regex.sub('', got)
+got = big_sur_warning_regex.sub('', got)
 if isinstance(want, MarkedOutput):
 if want.random:
 return True


On Tuesday, November 17, 2020 at 1:33:26 AM UTC-8 Andrew wrote:

> Just to confirm, I was able to compile 9.3.beta1 on macosx 10.0.1 running 
> xcode 12.2 with homebrew.
>
> The following doctests failed with `make ptestlong`:
>
> sage -t --long --random-seed=0 src/sage/misc/sagedoc.py  # 1 doctest failed
> sage -t --long --random-seed=0 src/sage/tests/cmdline.py  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/structure/element.pyx  # 8 
> doctests failed
> sage -t --long --random-seed=0 src/sage/misc/sageinspect.py  # 11 doctests 
> failed
> sage -t --long --random-seed=0 src/sage/functions/other.py  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/misc/cachefunc.pyx  # 6 doctests 
> failed
> sage -t --long --random-seed=0 src/sage/misc/cython.py  # 10 doctests 
> failed
> sage -t --long --random-seed=0 src/sage/graphs/connectivity.pyx  # 2 
> doctests failed
> sage -t --long --random-seed=0 src/sage/repl/ipython_extension.py  # 1 
> doctest failed
> sage -t --long --random-seed=0 src/sage/parallel/decorate.py  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/ext/memory_allocator.pxd  # 3 
> doctests failed
> sage -t --long --random-seed=0 src/sage/ext/memory_allocator.pyx  # 3 
> doctests failed
> sage -t --long --random-seed=0 src/sage/arith/long.pxd  # 2 doctests failed
> sage -t --long --random-seed=0 src/sage/cpython/cython_metaclass.pyx  # 1 
> doctest failed
> sage -t --long --random-seed=0 src/sage/misc/superseded.py  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/cpython/getattr.pyx  # 2 doctests 
> failed
> sage -t --long --random-seed=0 src/sage/structure/factory.pyx  # 2 
> doctests failed
> sage -t --long --random-seed=0 src/sage/misc/lazy_attribute.pyx  # 1 
> doctest failed
> sage -t --long --random-seed=0 src/sage/misc/inherit_comparison.pyx  # 1 
> doctest failed
> sage -t --long --random-seed=0 src/sage/rings/integer_fake.pxd  # 1 
> doctest failed
> sage -t --long --random-seed=0 src/sage/misc/session.pyx  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/docs/instancedoc.pyx  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/repl/preparse.py  # 12 doctests 
> failed
> sage -t --long --random-seed=0 src/sage/cpython/wrapperdescr.pxd  # 1 
> doctest failed
> sage -t --long --random-seed=0 src/sage/misc/nested_class.pyx  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/cpython/string.pyx  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/misc/gperftools.py  # 1 doctest 
> failed
> sage -t --long --random-seed=0 src/sage/rings/tate_algebra_ideal.pyx  # 2 
> doctests failed
>
> but the most amusing failure was at the end:
>
> Doctests interrupted: 2791/4216 files tested
> --
> Total time for all tests: 4482.7 seconds
> cpu time: 10717.5 seconds
> cumulative wall time: 13159.6 seconds
> Traceback (most recent call last):
> ...
> OSError: [Errno 24] Too many open files
> make: *** [ptestlong] Error 1
>
> That sage is compiling with the just released version of macosx and the 
> latest xcode I think that this is a win.
> On Tuesday, 17 November 2020 at 5:11:16 pm UTC+11 Andrew wrote:
>
>> Thanks very much for this Matthias. This is almost certainly my problem 
>> -- and I have to confess to user error as this was a hack I put in at one 
>> point to get around problems with an xcode update. I have deleted a bunch 
>> of spurious links like these and am now recompiling. It has already gotten 
>> much further than before. Ih particular, givaro now