Re: [sage-devel] Re: Machine Learning people apparently built a symbolic integrator

2019-12-26 Thread Dima Pasechnik
On Thu, Dec 26, 2019 at 11:54 AM Brent W. Baccala  wrote:
>
>
> I know the Risch algorithm fairly well.
>
> I made two screencast videos describing how to use Axiom or Sage to simplify 
> one of the integrals used in the Facebook paper.
>
> Quick summary - Axiom works quite well.  Sage can't do it in one step, but 
> the new function field features in Sage 9 allow the integral to computed, but 
> you have to know something about the Risch algorithm to step through it.
>
> The second video is a whirlwind overview of the Risch theorem and shows how 
> to do a Risch calculation (on the Facebook integral) using Sage.
>
> You can view the videos here:
>
> https://www.freesoft.org/blogs/soapbox/the-facebook-integral/
>
>
> --
> 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/d4b54993-e650-4627-a7fa-27b6b0c289c0%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/CAAWYfq0uuG9nogA8qcPkoCO9dhzskD3-_jtO3kkfYOvESmsW9Q%40mail.gmail.com.


[sage-devel] Re: Sage 8.9 build fails on macOS Catalina

2019-12-26 Thread Volker Braun
The OSX code signing is a major annoyance. We can't notarize our binaries 
since we rewrite paths to shared libraries on start. But that modifies the 
binary and invalidates any signature. I think we can clear the quarantine 
flag, so you'd only get the gatekeeper warning dialog once. Maybe one of 
you can try out if this works, just run

xattr -rd com.apple.quarantine /path/to/sage

to recursively clear the quarantine flag. After that sage should start 
fine...




On Saturday, December 21, 2019 at 4:40:34 PM UTC+1, Clayton Cafiero wrote:
>
> macOS Catalina 10.15.2 (19C57)
>
> Tried downloading and installing binary (sage-8.9-OSX_10.14.6-x86_64.dmg) 
> but when run macOS complained bitterly about every file Sage tried to load 
> when starting with
>
> “python2.7” cannot be opened because the developer cannot be verified."
>
>
> If I use System Preferences > Security & Privacy to allow python2.7, then 
> another warning appears:
>
>
> “libpython2.7.dylib” cannot be opened because the developer cannot be 
> verified."
>
>
> ...I had patience for about the first 100 files (_locale.so, zlib.so, 
> _collections.so, blah, blah, blah), then I threw in the towel and tried to 
> build.
>
> % xcodebuild -version   
> Xcode 11.2
> Build version 11B52
>
> Downloaded Sage 8.9 source from mirror. Followed instructions in 
> README.md, specifically
>
> * __OS X:__
>* Make sure you have installed the most recent version
>of Xcode which you can install for free from the App Store.
>* You also need to install the "command line tools". When
>using OS X Mavericks, after installing Xcode, run
>`xcode-select --install` from a terminal window:
>Then click "Install" in the pop-up window.
>When using OS X Mountain Lion or earlier, you need to install the
>command line tools from Xcode: run Xcode; then from the File
>menu, choose "Preferences", then the "Downloads" tab, and then
>"Install" the Command Line Tools. You might also have Homebrew or
>a similar "Apple's missing package manager" system installed, with
>and libraries such gfortran, gmp, etc installed. (However, this
>is still experimental as of May 2019).
>
> ...
>
> Extract the tarball
>
>tar zxvf sage-*.tar.gz
>
> cd into the Sage directory and type make
>
>cd sage-*/
>make
>
> This ran for quite a while and then failed, informing me to 
> check /Users/myname/Downloads/sage-8.9/logs/pkgs/gfortran-7.4.0.log for 
> more information. This file has over 500k lines and ends with
>
> ../../../src/libssp/gets-chk.c:59:13: error: storage class specified for 
> parameter '__chk_fail'
>  extern void __chk_fail (void) __attribute__((__noreturn__));
>  ^~
> ../../../src/libssp/gets-chk.c:63:1: error: expected '=', ',', ';', 'asm' 
> or '__attribute__' before '{' token
>  {
>  ^
> In file included from 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/wait.h:110:0,
>  from 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdlib.h:66,
>  from ../../../src/libssp/gets-chk.c:39:
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:447:9:
>  
> error: old-style parameter declarations in prototyped function definition
>  int getiopolicy_np(int, int) __OSX_AVAILABLE_STARTING(__MAC_10_5, 
> __IPHONE_2_0);
>  ^~
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:447:1:
>  
> error: parameter name omitted
>  int getiopolicy_np(int, int) __OSX_AVAILABLE_STARTING(__MAC_10_5, 
> __IPHONE_2_0);
>  ^~~
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/resource.h:447:1:
>  
> error: parameter name omitted
> ../../../src/libssp/gets-chk.c:92:1: error: expected '{' at end of input
>  }
>  ^
> ../../../src/libssp/gets-chk.c:92:1: warning: control reaches end of 
> non-void function [-Wreturn-type]
>  }
>  ^
> make[7]: *** [gets-chk.lo] Error 1
> make[6]: *** [all] Error 2
> make[5]: *** [all-target-libssp] Error 2
> make[4]: *** [all] Error 2
>
> 
> Error building gfortran-7.4.0
>
> 
>
> Zip of this complete file is attached. 
>
> Any suggestions? Please advise. TYVVM.
>
>
>
>
>

-- 
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 

[sage-devel] srange under python3

2019-12-26 Thread chris wuthrich

 I have a question about the future of srange under python 3, which changes 
the behaviour of range. Probably this has been discussed before but I could 
not find it.

In 9.0.beta10 we have

sage: range(1,3)
range(1, 3)
sage: srange(1,3)
[1, 2]
sage: sxrange(1,3)

sage: [1..2]
[1, 2]
sage: type(range(1,3)), type(srange(1,3)), type(sxrange(1,3)), type([1..2])
(, , , )

and no xrange anymore.

Would it make sense to drop sxrange and make srange an iterator like range, 
while keeping [a..b] as a list as suggested by its notation?

Chris


-- 
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/eb56b434-5e1e-4ce7-9585-16f00efb49f6%40googlegroups.com.