[sage-devel] Re: make doc fails on manifolds

[Zachary Scherr]

Yes, through Homebrew.  I'll unlink it tomorrow and I'm guessing that'll 
fix the problem.  Thanks, I got confused because it looked like it was 
grabbing it from my sage folder and not /usr/local, but I didn't notice ECL 
being built.

On Wednesday, October 7, 2020 at 11:09:19 PM UTC-4 Matthias Koeppe wrote:

> On Wednesday, October 7, 2020 at 4:42:23 PM UTC-7, Zachary Scherr wrote:
>>
>>I was building sage today, and the building of sage seems to work fine 
>> but building the documentation crashed for me at manifolds.  Does anyone 
>> have any insight as to what's going on?
>>
>
> From the log:
>
> 
> [manifolds] from sage.libs.ecl import EclObject, ecl_eval
> [manifolds] ImportError: 
> dlopen(/Users/zscherr/sage/local/lib/python3.8/site-packages/sage/libs/ecl.cpython-38-darwin.so,
>  2): Symbol not found: _ecl_process_env
> [manifolds]   Referenced from: 
> /Users/zscherr/sage/local/lib/python3.8/site-packages/sage/libs/ecl.cpython-38-darwin.so
> [manifolds]   Expected in: flat namespace
>
>
> Do you have another installation of ecl, perhaps in /usr/local?  In that 
> case, this problem may have a similar cause as the problems related to 
> ntl/flint that you reported earlier.
>  
>

-- 
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/dc17c0fc-f882-4f9e-92ec-940583276de7n%40googlegroups.com.

[sage-devel] Re: make doc fails on manifolds

[Matthias Koeppe]

On Wednesday, October 7, 2020 at 4:42:23 PM UTC-7, Zachary Scherr wrote:
>
>I was building sage today, and the building of sage seems to work fine 
> but building the documentation crashed for me at manifolds.  Does anyone 
> have any insight as to what's going on?
>

>From the log:


[manifolds] from sage.libs.ecl import EclObject, ecl_eval
[manifolds] ImportError: 
dlopen(/Users/zscherr/sage/local/lib/python3.8/site-packages/sage/libs/ecl.cpython-38-darwin.so,
 2): Symbol not found: _ecl_process_env
[manifolds]   Referenced from: 
/Users/zscherr/sage/local/lib/python3.8/site-packages/sage/libs/ecl.cpython-38-darwin.so
[manifolds]   Expected in: flat namespace


Do you have another installation of ecl, perhaps in /usr/local?  In that 
case, this problem may have a similar cause as the problems related to 
ntl/flint that you reported earlier.
 

-- 
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/c0f7db29-97ff-40f2-8cfd-2962960c0b05o%40googlegroups.com.

Re: [sage-devel] Re: Beta 12 not building (Homebrew singular issue?)

[Zachary Scherr]

I should probably also add that while sage builds with 
the spkg-configure.m4 fix, my documentation will not build unless I brew 
unlink singular.

On Wednesday, October 7, 2020 at 10:33:32 AM UTC-4 Zachary Scherr wrote:

> I was just curious as to what the status of this issue is, and if there 
> was anything I could do to help with review.  I can build rc0 using Dima's 
> suggested spkg-configure.m4 fix, but I can't build it otherwise unless I 
> brew unlink singular first. 
>
> On Friday, September 11, 2020 at 6:47:23 PM UTC-4 dim...@gmail.com wrote:
>
>> as an experiment, I hardcoded the necessary paths for using Homebrew's 
>> Singular here:
>>
>> https://trac.sagemath.org/attachment/ticket/29024/homebrew-singular-experiment.patch
>> (the part for  src/sage/libs/singular/singular.pxd is probably not 
>> needed, but anyway)
>>
>> running tests now.
>>
>> On Fri, Sep 11, 2020 at 6:15 PM Dima Pasechnik  wrote:
>>
>>>
>>>
>>> On Fri, Sep 11, 2020 at 3:32 PM Dima Pasechnik  wrote:
>>>
 I think there is at least one place elsewhere in the code that assumes 
 that Singular is installed in $SAGE_LOCAL

 at least I got an error of this sort while trying to build Sage's docs 
 in this configuration.
 I'll look into it once back at the keyboard

>>>
>>> this problem is explained in 
>>> https://trac.sagemath.org/ticket/29024#comment:8
>>>
>>> The fix needs some programming - specifically, the code in singular.pyx 
>>> calls dlopen on SINGULAR_SO,
>>> which is computed by _get_shared_lib_filename dynamically in env.py, 
>>> and assuming that it is in SAGE_LOCAL.
>>> So this probably can instead by handled using cython_aliases from the 
>>> same module (which does compute
>>> all the needed info for Singular, it seems).
>>> Or by fixing _get_shared_lib_filename so that it also searches 
>>> elsewhere.
>>>
>>>
 On Fri, 11 Sep 2020, 15:10 Zachary Scherr,  wrote:

> Hi Dima,
>
>Thanks! Downloading spkg-configure.m4 allowed me to build 
> successfully.
>
> Best,
> Zach
>
> On Friday, September 11, 2020 at 5:45:00 AM UTC-4 dim...@gmail.com 
> wrote:
>
>> On Fri, Sep 11, 2020 at 10:11 AM Dima Pasechnik  
>> wrote:
>>
>>> [sagelib-9.2.beta12] installing. Log file: 
>>> /Users/zscherr/sage/develop/logs/pkgs/sagelib-9.2.beta12.log
>>>   [sagelib-9.2.beta12] error installing, exit status 1. End of log 
>>> file:
>>>   [sagelib-9.2.beta12]   
>>> /usr/local/include/singular/Singular/libsingular.h:15:10: fatal error: 
>>> 'polys/shiftop.h' file not found
>>>   [sagelib-9.2.beta12]   #include "polys/shiftop.h"
>>>   [sagelib-9.2.beta12]^
>>>
>>> the include path looks funny with its "singular/Singular/"
>>> I don't know what brew does here, maybe it drops "singular/" bit?
>>>
>>
>> no, in fact it's all fine, it's just include flags that need to be 
>> adjusted.
>> Note that you still have 
>> -I/Users/zscherr/sage/develop/local/include/singular
>> in the failing gcc call, which seems to indicate you didn't use
>>
>> https://trac.sagemath.org/attachment/ticket/29024/spkg-configure.m4
>>
>> - of if you did, you didn't run
>>
>> make singular-clean
>>
>> ./bootstrap && ./configure
>>
>> after putting that file
>> in build/pkgs/singular/
>>
>>
>>
>>
>> Try
>>
>> CXXFLAGS="$CXXFLAGS -I//usr/local/include/singular/
>>
>>>
>>>
>>> On Thu, Sep 10, 2020 at 9:20 PM Zachary Scherr  
>>> wrote:
>>>
 Hi Matthias,

It's attached to this message.

 Best,
 Zach

 On Thursday, September 10, 2020 at 1:07:27 PM UTC-4 Matthias Koeppe 
 wrote:

> On Thursday, September 10, 2020 at 9:58:02 AM UTC-7, Zachary 
> Scherr wrote:
>>
>>
>> Obviously this is not a big deal since I can just brew uninstall 
>> singular and then it builds successfully, but I've been wanting to 
>> contribute to sage development so I'm going to take this as an 
>> opportunity 
>> to try to track down what's going on. 
>>
>>
> Yes, this is much appreciated. So far I can't reproduce the error 
> here (after installing homebrew's singular), unfortunately. 
>
> Could you post install.log please?
>
 -- 
 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/3c9f01e9-ded6-43bd-8861-301d1e97a06an%40googlegroups.com
  
 

[sage-devel] Re: SageMath Anaconda and Python 3.8

[Zachary Scherr]

You should probably follow the directions 
here: https://doc.sagemath.org/html/en/installation/conda.html

and install sage into its own environment so that it correctly installs all 
the dependencies.  Sage 9.2 will support python 3.8.

On Wednesday, October 7, 2020 at 2:18:27 PM UTC-4 asv...@gmail.com wrote:

> My Anaconda is instaled with Python 3.8.
> I tried to attach Sage to Anaconda by running one of the commands listed 
> here
> https://anaconda.org/conda-forge/sage
> However, there is python incompatibility. Is there any plan for an upgrade?
>
> The message on a terminal window is 
>
>
> UnsatisfiableError: The following specifications were found
> to be incompatible with the existing python installation in your 
> environment: 
>
> Specifications: 
> - sage -> 
> python[version='2.7.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0'] 
> Your python: python=3.8 
>
> If python is on the left-most side of the chain, that's the version you've 
> asked for. 
> When python appears to the right, that indicates that the thing on the 
> left is somehow 
> not available for the python version you are constrained to. Note that 
> conda will not 
> change your python version to a different minor version unless you 
> explicitly specify 
> that.
>

-- 
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/f8d1b6ef-eaa9-4627-bab8-ec5e96a3c4ddn%40googlegroups.com.

[sage-devel] SageMath Anaconda and Python 3.8

[Vaiva Petrikaite]

My Anaconda is instaled with Python 3.8.
I tried to attach Sage to Anaconda by running one of the commands listed 
here
https://anaconda.org/conda-forge/sage
However, there is python incompatibility. Is there any plan for an upgrade?

The message on a terminal window is 


UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your 
environment: 

Specifications: 
- sage -> 
python[version='2.7.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0'] 
Your python: python=3.8 

If python is on the left-most side of the chain, that's the version you've 
asked for. 
When python appears to the right, that indicates that the thing on the left 
is somehow 
not available for the python version you are constrained to. Note that 
conda will not 
change your python version to a different minor version unless you 
explicitly specify 
that.

-- 
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/ca51a2a5-5c45-49d4-b3db-f4217a499360n%40googlegroups.com.

Re: [sage-devel] Re: Beta 12 not building (Homebrew singular issue?)

[Zachary Scherr]

I was just curious as to what the status of this issue is, and if there was 
anything I could do to help with review.  I can build rc0 using Dima's 
suggested spkg-configure.m4 fix, but I can't build it otherwise unless I 
brew unlink singular first. 

On Friday, September 11, 2020 at 6:47:23 PM UTC-4 dim...@gmail.com wrote:

> as an experiment, I hardcoded the necessary paths for using Homebrew's 
> Singular here:
>
> https://trac.sagemath.org/attachment/ticket/29024/homebrew-singular-experiment.patch
> (the part for  src/sage/libs/singular/singular.pxd is probably not needed, 
> but anyway)
>
> running tests now.
>
> On Fri, Sep 11, 2020 at 6:15 PM Dima Pasechnik  wrote:
>
>>
>>
>> On Fri, Sep 11, 2020 at 3:32 PM Dima Pasechnik  wrote:
>>
>>> I think there is at least one place elsewhere in the code that assumes 
>>> that Singular is installed in $SAGE_LOCAL
>>>
>>> at least I got an error of this sort while trying to build Sage's docs 
>>> in this configuration.
>>> I'll look into it once back at the keyboard
>>>
>>
>> this problem is explained in 
>> https://trac.sagemath.org/ticket/29024#comment:8
>>
>> The fix needs some programming - specifically, the code in singular.pyx 
>> calls dlopen on SINGULAR_SO,
>> which is computed by _get_shared_lib_filename dynamically in env.py, and 
>> assuming that it is in SAGE_LOCAL.
>> So this probably can instead by handled using cython_aliases from the 
>> same module (which does compute
>> all the needed info for Singular, it seems).
>> Or by fixing _get_shared_lib_filename so that it also searches elsewhere.
>>
>>
>>> On Fri, 11 Sep 2020, 15:10 Zachary Scherr,  wrote:
>>>
 Hi Dima,

Thanks! Downloading spkg-configure.m4 allowed me to build 
 successfully.

 Best,
 Zach

 On Friday, September 11, 2020 at 5:45:00 AM UTC-4 dim...@gmail.com 
 wrote:

> On Fri, Sep 11, 2020 at 10:11 AM Dima Pasechnik  
> wrote:
>
>> [sagelib-9.2.beta12] installing. Log file: 
>> /Users/zscherr/sage/develop/logs/pkgs/sagelib-9.2.beta12.log
>>   [sagelib-9.2.beta12] error installing, exit status 1. End of log 
>> file:
>>   [sagelib-9.2.beta12]   
>> /usr/local/include/singular/Singular/libsingular.h:15:10: fatal error: 
>> 'polys/shiftop.h' file not found
>>   [sagelib-9.2.beta12]   #include "polys/shiftop.h"
>>   [sagelib-9.2.beta12]^
>>
>> the include path looks funny with its "singular/Singular/"
>> I don't know what brew does here, maybe it drops "singular/" bit?
>>
>
> no, in fact it's all fine, it's just include flags that need to be 
> adjusted.
> Note that you still have 
> -I/Users/zscherr/sage/develop/local/include/singular
> in the failing gcc call, which seems to indicate you didn't use
>
> https://trac.sagemath.org/attachment/ticket/29024/spkg-configure.m4
>
> - of if you did, you didn't run
>
> make singular-clean
>
> ./bootstrap && ./configure
>
> after putting that file
> in build/pkgs/singular/
>
>
>
>
> Try
>
> CXXFLAGS="$CXXFLAGS -I//usr/local/include/singular/
>
>>
>>
>> On Thu, Sep 10, 2020 at 9:20 PM Zachary Scherr  
>> wrote:
>>
>>> Hi Matthias,
>>>
>>>It's attached to this message.
>>>
>>> Best,
>>> Zach
>>>
>>> On Thursday, September 10, 2020 at 1:07:27 PM UTC-4 Matthias Koeppe 
>>> wrote:
>>>
 On Thursday, September 10, 2020 at 9:58:02 AM UTC-7, Zachary Scherr 
 wrote:
>
>
> Obviously this is not a big deal since I can just brew uninstall 
> singular and then it builds successfully, but I've been wanting to 
> contribute to sage development so I'm going to take this as an 
> opportunity 
> to try to track down what's going on. 
>
>
 Yes, this is much appreciated. So far I can't reproduce the error 
 here (after installing homebrew's singular), unfortunately. 

 Could you post install.log please?

>>> -- 
>>> 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/3c9f01e9-ded6-43bd-8861-301d1e97a06an%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+...@googlegroups.com.
 To view this di

Re: [sage-devel] zenodo (DOI) for Sage releases is back!

[Dima Pasechnik]

please see https://trac.sagemath.org/ticket/30737
- the question is how to test this well.

On Tue, Oct 6, 2020 at 11:06 PM Dima Pasechnik  wrote:
>
> On Tue, Oct 6, 2020 at 9:53 PM François Bissey  wrote:
> >
> > That’s nice but it looks like there could be improvement to the authors’ 
> > list.
> > Some people appear by handle rather than name. Is it because they don’t 
> > give their real
> > names on GitHub?
>
> yes, people who are listed by their github handles are ones who don't
> have "real" full names on GitHub.
>
> As far as truncation of the list goes, it seems they always stop at 30 names.
>
> Not sure how to fix this, hopefully it is possible.
>
> > Or don’t have a GitHub account? It also looks truncated.
> >
> > > On 7/10/2020, at 9:46 AM, Dima Pasechnik  wrote:
> > >
> > > We've recovered the settings for getting DOI for Sage releases via
> > > zenodo, something that was broken for years.
> > > cf https://zenodo.org/record/4066866
> > > and this is DOI for Sage 9.1: https://doi.org/10.5281/zenodo.4066866
> > >
> > > --
> > > 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/CAAWYfq1%2BmY1uULNUsEXwOk8rVyYVJ0%3DxJ9EoRp2naDFz7o99xg%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/54FC8789-0BA0-4CC6-A273-34E55CB94785%40gmail.com.

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

[sage-devel] Sage 9.2 cycle at the "release candidate" stage

[Samuel Lelievre]

Dear sage-devel,

The Sage 9.2 cycle progresses, with Sage 9.2.rc0 recently released.

We still have three "blocker" and around a hundred "critical" tickets.

https://trac.sagemath.org/query?order=id&desc=1&group=status&col=id&col=summary&col=component&col=type&col=milestone&col=author&col=cc&status=!closed&priority=blocker

https://trac.sagemath.org/query?order=id&desc=1&group=status&col=id&col=summary&col=component&col=type&col=milestone&col=author&col=cc&status=!closed&priority=critical

Can we make progress on solving, updating or closing most of them?
Some might be obsolete.  Kind regards,  --Samuel

-- 
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/63720fd1-91cb-476f-b2b1-6a5e32b70340o%40googlegroups.com.