Re: [sage-devel] Re: Can't compile 8.4.beta3

2018-09-10 Thread Andrew
Dear John and Erik,

Thanks for the hints. I have tried recompiling several times as suggested 
but the build still fails, sometimes on pip-18.0 and sometimes on 
python3-3.6.6.p0. Given the potential race condition in 
https://trac.sagemath.org/ticket/18438 I'll try compiling with a single 
core and see if this works.

Andrew

On Tuesday, 11 September 2018 01:22:55 UTC+10, Erik Bray wrote:
>
> On Mon, Sep 10, 2018 at 6:33 AM John H Palmieri  > wrote: 
> > 
> > One thing to try, in case you haven't already: run make once, and if it 
> fails with a warning like this, try running make again immediately (without 
> doing "make distclean"). (Sage may be using Sage's python in the 
> installation process before it's quite ready, but when you run 'make' a 
> second time, the installation of python2 will have completed.) 
>
> +1 You're probably running into https://trac.sagemath.org/ticket/18438 
>  which is a race condition in parallel builds. 
>
> Just re-run `make` without doing `make distclean` and it should continue. 
>
> > On Sunday, September 9, 2018 at 9:28:11 PM UTC-7, Andrew wrote: 
> >> 
> >> I'm now trying, without success, to compile 8.4.beta4. 
> >> 
> >> I have homebrew installed. For the past few years I have stopped it 
> from affecting the sage compliation by setting my PATH accordingly. If I do 
> this and use 
> >> make distclean && make 
> >> 
> >> then I still the error above with make failing on pip-18.0. Here is the 
> pip-18.0.log file: 
> >> 
> >> pip-18.0 
> >>  
> >> Setting up build directory for pip-18.0 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 
> >> Finished extraction 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src 
> >> No patch files found in ../patches 
> >>  
> >> Host system: 
> >> Darwin p718m.pc.maths.usyd.edu.au 17.7.0 Darwin Kernel Version 17.7.0: 
> Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64 
> >>  
> >> C compiler: gcc 
> >> C compiler version: 
> >> Configured with: 
> --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1 
> >> Apple LLVM version 9.1.0 (clang-902.0.39.2) 
> >> Target: x86_64-apple-darwin17.7.0 
> >> Thread model: posix 
> >> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>  
>
> >>  
> >> No record that 'pip' was ever installed; skipping uninstall 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src 
> >> /usr/local/src/sage/local/bin/python3: No module named pip 
> >> 
> 
>  
>
> >> Error building / installing pip3 
> >> 
> 
>  
>
> >> 
> >> real 0.102  user 0.044  sys 0.024   pcpu 67.51 
> >> 
> >> 
>  
> >> Error installing package pip-18.0 
> >> 
>  
> >> Please email sage-devel (http://groups.google.com/group/sage-devel) 
> >> explaining the problem and including the log file 
> >>   /usr/local/src/sage/logs/pkgs/pip-18.0.log 
> >> Describe your computer, operating system, etc. 
> >> If you want to try to fix the problem yourself, *don't* just cd to 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 and type 'make' 
> or whatever is appropriate. 
> >> Instead, the following commands setup all environment variables 
> >> correctly and load a subshell for you to debug the error: 
> >>   (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0' && 
> '/usr/local/src/sage/sage' --sh) 
> >> When you are done debugging, you can type "exit" to leave the subshell. 
> >> 
>  
> >> 
> >> make distclean && make I hit an error compiling python3-3.6.6.p0. The 
> log file python3.6 is attached. 
> >> 
> >> If, instead, I run make distclean && make without removing brew then I 
> get a little further, with make now breaking on the build of 
> python3-3.6.6.p0, with 
> >> python3-3.6.6.p0.log now looking like: 
> >> 
> >> 
> >> Found local metadata for python3-3.6.6.p0 
> >> Traceback (most recent call last): 
> >>   File "/usr/local/src/sage/local/lib/python2.7/site.py", line 62, in 
>  
> >> import os 
> >>   File "/usr/local/src/sage/local/lib/python2.7/os.py", line 49, in 
>  
> >> import posixpath as path 
> >>   File "/usr/local/src/sage/local/lib/python2.7/posixpath.py", line 17, 
> in  
> >> import warnings 
> >> ImportError: No module named warnings 
> >> 
>  
> >> Error downloading 

Re: [sage-devel] QQ not isomorphic to itself?!

2018-09-10 Thread Jeroen Demeyer

On 2018-09-10 21:36, John Cremona wrote:

The bug is because of this:


Since you almost fixed this bug, could you actually create a ticket to 
fix it?


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


[sage-devel] QQ not isomorphic to itself?!

2018-09-10 Thread John Cremona
sage: Qx = PolynomialRing(QQ,'x')
sage: F1 = NumberField(Qx([0,1]),'a1'); F1
Number Field in a1 with defining polynomial x
sage: F2 = NumberField(Qx([0,1]),'a2'); F2
Number Field in a2 with defining polynomial x
sage: F1.is_isomorphic(F2)
False

The bug is because of this:

sage: f1=F1.pari_polynomial(); f1
x
sage: f2=F2.pari_polynomial(); f2
x
sage: f1.nfisisom(f2)
[0]
sage: f1.nfisisom(f2) ==0
True

So pari correctly finds an isomorphism but Sage thinks that paris's [0] is
the same as pari's 0, the latter being what is returned when the fields are
not isomorphic.

John

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


Re: [sage-devel] Re: Can't compile 8.4.beta3

2018-09-10 Thread Erik Bray
On Mon, Sep 10, 2018 at 6:33 AM John H Palmieri  wrote:
>
> One thing to try, in case you haven't already: run make once, and if it fails 
> with a warning like this, try running make again immediately (without doing 
> "make distclean"). (Sage may be using Sage's python in the installation 
> process before it's quite ready, but when you run 'make' a second time, the 
> installation of python2 will have completed.)

+1 You're probably running into https://trac.sagemath.org/ticket/18438
 which is a race condition in parallel builds.

Just re-run `make` without doing `make distclean` and it should continue.

> On Sunday, September 9, 2018 at 9:28:11 PM UTC-7, Andrew wrote:
>>
>> I'm now trying, without success, to compile 8.4.beta4.
>>
>> I have homebrew installed. For the past few years I have stopped it from 
>> affecting the sage compliation by setting my PATH accordingly. If I do this 
>> and use
>> make distclean && make
>>
>> then I still the error above with make failing on pip-18.0. Here is the 
>> pip-18.0.log file:
>>
>> pip-18.0
>> 
>> Setting up build directory for pip-18.0
>> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0
>> Finished extraction
>> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
>> No patch files found in ../patches
>> 
>> Host system:
>> Darwin p718m.pc.maths.usyd.edu.au 17.7.0 Darwin Kernel Version 17.7.0: Thu 
>> Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
>> 
>> C compiler: gcc
>> C compiler version:
>> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
>> --with-gxx-include-dir=/usr/include/c++/4.2.1
>> Apple LLVM version 9.1.0 (clang-902.0.39.2)
>> Target: x86_64-apple-darwin17.7.0
>> Thread model: posix
>> InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>> 
>> No record that 'pip' was ever installed; skipping uninstall
>> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
>> /usr/local/src/sage/local/bin/python3: No module named pip
>> 
>> Error building / installing pip3
>> 
>>
>> real 0.102  user 0.044  sys 0.024   pcpu 67.51
>>
>> 
>> Error installing package pip-18.0
>> 
>> Please email sage-devel (http://groups.google.com/group/sage-devel)
>> explaining the problem and including the log file
>>   /usr/local/src/sage/logs/pkgs/pip-18.0.log
>> Describe your computer, operating system, etc.
>> If you want to try to fix the problem yourself, *don't* just cd to
>> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 and type 'make' or 
>> whatever is appropriate.
>> Instead, the following commands setup all environment variables
>> correctly and load a subshell for you to debug the error:
>>   (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0' && 
>> '/usr/local/src/sage/sage' --sh)
>> When you are done debugging, you can type "exit" to leave the subshell.
>> 
>>
>> make distclean && make I hit an error compiling python3-3.6.6.p0. The log 
>> file python3.6 is attached.
>>
>> If, instead, I run make distclean && make without removing brew then I get a 
>> little further, with make now breaking on the build of python3-3.6.6.p0, with
>> python3-3.6.6.p0.log now looking like:
>>
>>
>> Found local metadata for python3-3.6.6.p0
>> Traceback (most recent call last):
>>   File "/usr/local/src/sage/local/lib/python2.7/site.py", line 62, in 
>> 
>> import os
>>   File "/usr/local/src/sage/local/lib/python2.7/os.py", line 49, in 
>> import posixpath as path
>>   File "/usr/local/src/sage/local/lib/python2.7/posixpath.py", line 17, in 
>> 
>> import warnings
>> ImportError: No module named warnings
>> 
>> Error downloading Python-3.6.6.tar.gz
>> 
>> Please email sage-devel (http://groups.google.com/group/sage-devel)
>> explaining the problem and including the log file
>>   /usr/local/src/sage/logs/pkgs/python3-3.6.6.p0.log
>> Describe your computer, operating system, etc.
>> 
>> I am seeing the same behaviour on an imac and on a macbook pro. both of 
>> which are running:
>> ProductName:Mac OS X
>> ProductVersion:10.13.6
>> BuildVersion:17G65
>> Xcode 9.4.1
>> Build version 9F2000
>> Does anyone have  an idea of what's going 

Re: [sage-devel] Re: zn_poly status?

2018-09-10 Thread Jean-Pierre Flori


On Monday, September 10, 2018 at 2:34:06 PM UTC+2, Erik Bray wrote:
>
> On Mon, Sep 10, 2018 at 1:43 PM 'Bill Hart' via sage-devel 
> > wrote: 
> > 
> > NTL is your best best. However zn_poly is a tour de force. It would be 
> hard to beat. 
>
IIRC it's very hardcoded into hypellfrob 
(http://web.maths.unsw.edu.au/~davidharvey/code/hypellfrob/) and very fast 
indeed.
As far as I know we have no alternative implementation to whats in 
hypellfrob though PARI/GP now offers more or less the same functionality 
with a different algorithm.

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


Re: [sage-devel] Re: zn_poly status?

2018-09-10 Thread Erik Bray
On Mon, Sep 10, 2018 at 1:43 PM 'Bill Hart' via sage-devel
 wrote:
>
> NTL is your best best. However zn_poly is a tour de force. It would be hard 
> to beat.

If nothing else, I am making it easier to maintain now, so if someone
wants to hack on it it will be easier to do so now and has an
"official" home: https://gitlab.com/sagemath/zn_poly/

Though I'm not 100% sure about putting it at the top-level of the
sagemath/ org.  I might make a sub-org like "related-projects" or
something.  Any thoughts?


> On Friday, 7 September 2018 19:13:32 UTC+2, Antonio Rojas wrote:
>>
>>
>>
>> El viernes, 7 de septiembre de 2018, 15:53:43 (UTC+2), Erik Bray escribió:
>>>
>>> Hi all,
>>>
>>> Does anyone know what that current status is of the upstream zn_poly
>>> package?  According to its website
>>> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
>>> though it has been re-released under a BSD-compatible license.
>>>
>>
>> Given that the library has been unmaintained for years, has someone looked 
>> into whether its functionality can be provided by some other library 
>> nowadays?
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

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


[sage-devel] Re: zn_poly status?

2018-09-10 Thread 'Bill Hart' via sage-devel
NTL is your best best. However zn_poly is a tour de force. It would be hard 
to beat.

On Friday, 7 September 2018 19:13:32 UTC+2, Antonio Rojas wrote:
>
>
>
> El viernes, 7 de septiembre de 2018, 15:53:43 (UTC+2), Erik Bray escribió:
>>
>> Hi all, 
>>
>> Does anyone know what that current status is of the upstream zn_poly 
>> package?  According to its website 
>> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained", 
>> though it has been re-released under a BSD-compatible license. 
>>
>>
> Given that the library has been unmaintained for years, has someone looked 
> into whether its functionality can be provided by some other library 
> nowadays? 
>

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