Re: [sage-devel] Trouble building cython

[Zachary Scherr]

I need to sign off for the night, but the numpy error is definitely related 
to gfortran.  If you have gcc installed via homebrew then it should come 
with the latest version of gfortran.  You can see from your config.log file 
that gfortran is not found:

configure:7281: checking for gfortran
configure:7311: result: no

and other standard homebrew packages are not found, like openblas:

configure:12171: checking BLAS library
configure:12190: result: openblas
configure:12239: checking whether any of gfortran is installed as or will 
be installed as SPKG
configure:12243: result: yes; install openblas as well
configure:13540: no suitable system package found for SPKG openblas

are you aware if you have gcc and openblas installed via homebrew? I also 
see that you didn't run "source .homebrew-build-env" before running 
./configure since I don't see certain items on your path.  If you go to the 
sage installation guide 
at 
https://doc.sagemath.org/html/en/installation/source.html#macos-recommended-installation
 
you can see a list of homebrew packages you might want to have before 
installing sage.  I think if you get everything in working order with 
homebrew then you shouldn't have any issues installing sage.  Here is my 
best suggestion as to what to try:

- fix all "brew doctor" warnings.  This might not be necessary, but I get 
worried when I see so many warnings.  You can probably just delete all the 
suggested files and you should be fine.

- install all the recommended homebrew packages.  If any are already 
installed then maybe try "brew reinstall" to make sure it is installed 
properly.  If you think you have homebrew gcc installed then you should be 
able to do "which gfortran" and "gfortran --version".  That should 
hopefully show you that you have gfortran 10.2.0_3.

- in your sage folder under the develop branch you should run the commands 
I mentioned, and don't skip out on "source .homebrew-build-env":

>> make distclean
>> ./bootstrap
>> source .homebrew-build-env
>> ./configure

Before running "make -j4 build" you can look at config.log and make sure 
that it picked up all of the relevant homebrew packages.





On Monday, February 8, 2021 at 10:52:43 PM UTC-5 Trevor Karn wrote:

> Here is the new one. Thanks so much for all of your help on this, Zachary.
>
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 9:40 PM Zachary Scherr  wrote:
>
>> At some point you should deal with those warnings, but I don't think that 
>> is what is causing your problems (although they are probably symptomatic of 
>> other possible issues).  
>>
>> The config.log file you posted earlier is picking up a lot of packages 
>> that were built by sage and not from homebrew.  Do you have the config.log 
>> file that you got after running make distclean? 
>>
>> On Monday, February 8, 2021 at 10:10:01 PM UTC-5 Trevor Karn wrote:
>>
>>> brew doctor is giving lots of errors about unbrewed files:
>>>
>>> trevorkarn@Trevors-MacBook-Air sage % brew doctor
>>>
>>> *Please note that these warnings are just used to help the Homebrew 
>>> maintainers*
>>>
>>> *with debugging if you file an issue. If everything you use Homebrew for 
>>> is*
>>>
>>> *working fine: please don't worry or file an issue; just ignore this. 
>>> Thanks!*
>>>
>>>
>>> Warning: Unbrewed dylibs were found in /usr/local/lib.
>>>
>>> If you didn't put them there on purpose they could cause problems when
>>>
>>> building Homebrew formulae, and may need to be deleted.
>>>
>>>
>>> Unexpected dylibs:
>>>
>>>   /usr/local/lib/libtcl8.6.dylib
>>>
>>>   /usr/local/lib/libtk8.6.dylib
>>>
>>>
>>> Warning: Unbrewed header files were found in /usr/local/include.
>>>
>>> If you didn't put them there on purpose they could cause problems when
>>>
>>> building Homebrew formulae, and may need to be deleted.
>>>
>>>
>>> Unexpected header files:
>>>
>>>   /usr/local/include/fakemysql.h
>>>
>>>   /usr/local/include/fakepq.h
>>>
>>>   /usr/local/include/fakesql.h
>>>
>>>   /usr/local/include/itcl.h
>>>
>>>   /usr/local/include/itcl2TclOO.h
>>>
>>>   /usr/local/include/itclDecls.h
>>>
>>>   /usr/local/include/itclInt.h
>>>
>>>   /usr/local/include/itclIntDecls.h
>>>
>>>   /usr/local/include/itclMigrate2TclCore.h
>>>
>>>   /usr/local/include/itclTclIntStubsFcn.h
>>>
>>>   /usr/local/include/mysqlStubs.h
>>>
>>>   /usr/local/include/odbcStubs.h
>>>
>>>   /usr/local/include/pqStubs.h
>>>
>>>   /usr/local/include/tcl.h
>>>
>>>   /usr/local/include/tclDecls.h
>>>
>>>   /usr/local/include/tclOO.h
>>>
>>>   /usr/local/include/tclOODecls.h
>>>
>>>   /usr/local/include/tclPlatDecls.h
>>>
>>>   /usr/local/include/tclThread.h
>>>
>>>   /usr/local/include/tclTomMath.h
>>>
>>>   /usr/local/include/tclTomMathDecls.h
>>>
>>>   /usr/local/include/tdbc.h
>>>
>>>   /usr/local/include/tdbcDecls.h
>>>
>>>   /usr/local/include/tdbcInt.h
>>>
>>>   /usr/local/include/tk.h
>>>
>>>   /usr/local/include/tkDecls.h
>>>
>>>   /usr/local/include/tkPlatDecls.h
>>>
>>>
>>> Warning: Unbrewed '.pc' fi

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

At some point you should deal with those warnings, but I don't think that 
is what is causing your problems (although they are probably symptomatic of 
other possible issues).  

The config.log file you posted earlier is picking up a lot of packages that 
were built by sage and not from homebrew.  Do you have the config.log file 
that you got after running make distclean? 

On Monday, February 8, 2021 at 10:10:01 PM UTC-5 Trevor Karn wrote:

> brew doctor is giving lots of errors about unbrewed files:
>
> trevorkarn@Trevors-MacBook-Air sage % brew doctor
>
> *Please note that these warnings are just used to help the Homebrew 
> maintainers*
>
> *with debugging if you file an issue. If everything you use Homebrew for 
> is*
>
> *working fine: please don't worry or file an issue; just ignore this. 
> Thanks!*
>
>
> Warning: Unbrewed dylibs were found in /usr/local/lib.
>
> If you didn't put them there on purpose they could cause problems when
>
> building Homebrew formulae, and may need to be deleted.
>
>
> Unexpected dylibs:
>
>   /usr/local/lib/libtcl8.6.dylib
>
>   /usr/local/lib/libtk8.6.dylib
>
>
> Warning: Unbrewed header files were found in /usr/local/include.
>
> If you didn't put them there on purpose they could cause problems when
>
> building Homebrew formulae, and may need to be deleted.
>
>
> Unexpected header files:
>
>   /usr/local/include/fakemysql.h
>
>   /usr/local/include/fakepq.h
>
>   /usr/local/include/fakesql.h
>
>   /usr/local/include/itcl.h
>
>   /usr/local/include/itcl2TclOO.h
>
>   /usr/local/include/itclDecls.h
>
>   /usr/local/include/itclInt.h
>
>   /usr/local/include/itclIntDecls.h
>
>   /usr/local/include/itclMigrate2TclCore.h
>
>   /usr/local/include/itclTclIntStubsFcn.h
>
>   /usr/local/include/mysqlStubs.h
>
>   /usr/local/include/odbcStubs.h
>
>   /usr/local/include/pqStubs.h
>
>   /usr/local/include/tcl.h
>
>   /usr/local/include/tclDecls.h
>
>   /usr/local/include/tclOO.h
>
>   /usr/local/include/tclOODecls.h
>
>   /usr/local/include/tclPlatDecls.h
>
>   /usr/local/include/tclThread.h
>
>   /usr/local/include/tclTomMath.h
>
>   /usr/local/include/tclTomMathDecls.h
>
>   /usr/local/include/tdbc.h
>
>   /usr/local/include/tdbcDecls.h
>
>   /usr/local/include/tdbcInt.h
>
>   /usr/local/include/tk.h
>
>   /usr/local/include/tkDecls.h
>
>   /usr/local/include/tkPlatDecls.h
>
>
> Warning: Unbrewed '.pc' files were found in /usr/local/lib/pkgconfig.
>
> If you didn't put them there on purpose they could cause problems when
>
> building Homebrew formulae, and may need to be deleted.
>
>
> Unexpected '.pc' files:
>
>   /usr/local/lib/pkgconfig/tcl.pc
>
>   /usr/local/lib/pkgconfig/tk.pc
>
>
> Warning: Unbrewed static libraries were found in /usr/local/lib.
>
> If you didn't put them there on purpose they could cause problems when
>
> building Homebrew formulae, and may need to be deleted.
>
>
> Unexpected static libraries:
>
>   /usr/local/lib/libtclstub8.6.a
>
>   /usr/local/lib/libtkstub8.6.a
>
>
> Warning: You have unlinked kegs in your Cellar.
>
> Leaving kegs unlinked can lead to build-trouble and cause formulae that 
> depend on
>
> those kegs to fail to run properly once built. Run `brew link` on these:
>
>   ffmpeg
>
>   ghostscript
>
>
> Warning: Homebrew's "sbin" was not found in your PATH but you have 
> installed
>
> formulae that put executables in /usr/local/sbin.
>
> Consider setting your PATH for example like so:
>
>   echo 'export PATH="/usr/local/sbin:$PATH"' >> ~/.zshrc
>
>
> Warning: Broken symlinks were found. Remove them with `brew cleanup`:
>
>   /usr/local/bin/git-trac
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasy10.pfb
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasy5.pfb
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasy6.pfb
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasy7.pfb
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasy8.pfb
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasy9.pfb
>
>   /usr/local/share/ghostscript/9.27/Resource/Font/wasyb10.pfb
>
>   /usr/local/share/man/man1/brew-cask.1
>
>   /usr/local/share/zsh/site-functions/_brew_cask
>
> trevorkarn@Trevors-MacBook-Air sage % brew cleanup
>
> Removing: /usr/local/Cellar/gettext/0.20.1... (1,899 files, 18.5MB)
>
> Removing: /usr/local/Cellar/gmp/6.1.2_2... (18 files, 3.1MB)
>
> Removing: /usr/local/Cellar/gnutls/3.6.9... (1,227 files, 9.9MB)
>
> Removing: /usr/local/Cellar/icu4c/64.2... (257 files, 69.2MB)
>
> Removing: /usr/local/Cellar/libevent/2.1.11... (1,063 files, 5MB)
>
> Removing: /usr/local/Cellar/libffi/3.2.1... (16 files, 296.8KB)
>
> Removing: /usr/local/Cellar/libidn2/2.2.0_1... (70 files, 700.9KB)
>
> Removing: /usr/local/Cellar/libtasn1/4.14... (59 files, 384KB)
>
> Removing: /usr/local/Cellar/nettle/3.4.1... (85 files, 2MB)
>
> Error: Interrupted system call @ dir_initialize - /usr/local/Cellar/opus
>
> trevorkarn@Trevors-MacBook-Air sage % ;2D
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 8:38 PM Zacha

Re: [sage-devel] Trouble building cython

[Trevor Karn]

brew doctor is giving lots of errors about unbrewed files:

trevorkarn@Trevors-MacBook-Air sage % brew doctor

*Please note that these warnings are just used to help the Homebrew
maintainers*

*with debugging if you file an issue. If everything you use Homebrew for is*

*working fine: please don't worry or file an issue; just ignore this.
Thanks!*


Warning: Unbrewed dylibs were found in /usr/local/lib.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected dylibs:

  /usr/local/lib/libtcl8.6.dylib

  /usr/local/lib/libtk8.6.dylib


Warning: Unbrewed header files were found in /usr/local/include.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected header files:

  /usr/local/include/fakemysql.h

  /usr/local/include/fakepq.h

  /usr/local/include/fakesql.h

  /usr/local/include/itcl.h

  /usr/local/include/itcl2TclOO.h

  /usr/local/include/itclDecls.h

  /usr/local/include/itclInt.h

  /usr/local/include/itclIntDecls.h

  /usr/local/include/itclMigrate2TclCore.h

  /usr/local/include/itclTclIntStubsFcn.h

  /usr/local/include/mysqlStubs.h

  /usr/local/include/odbcStubs.h

  /usr/local/include/pqStubs.h

  /usr/local/include/tcl.h

  /usr/local/include/tclDecls.h

  /usr/local/include/tclOO.h

  /usr/local/include/tclOODecls.h

  /usr/local/include/tclPlatDecls.h

  /usr/local/include/tclThread.h

  /usr/local/include/tclTomMath.h

  /usr/local/include/tclTomMathDecls.h

  /usr/local/include/tdbc.h

  /usr/local/include/tdbcDecls.h

  /usr/local/include/tdbcInt.h

  /usr/local/include/tk.h

  /usr/local/include/tkDecls.h

  /usr/local/include/tkPlatDecls.h


Warning: Unbrewed '.pc' files were found in /usr/local/lib/pkgconfig.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected '.pc' files:

  /usr/local/lib/pkgconfig/tcl.pc

  /usr/local/lib/pkgconfig/tk.pc


Warning: Unbrewed static libraries were found in /usr/local/lib.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected static libraries:

  /usr/local/lib/libtclstub8.6.a

  /usr/local/lib/libtkstub8.6.a


Warning: You have unlinked kegs in your Cellar.

Leaving kegs unlinked can lead to build-trouble and cause formulae that
depend on

those kegs to fail to run properly once built. Run `brew link` on these:

  ffmpeg

  ghostscript


Warning: Homebrew's "sbin" was not found in your PATH but you have installed

formulae that put executables in /usr/local/sbin.

Consider setting your PATH for example like so:

  echo 'export PATH="/usr/local/sbin:$PATH"' >> ~/.zshrc


Warning: Broken symlinks were found. Remove them with `brew cleanup`:

  /usr/local/bin/git-trac

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy10.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy5.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy6.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy7.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy8.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy9.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasyb10.pfb

  /usr/local/share/man/man1/brew-cask.1

  /usr/local/share/zsh/site-functions/_brew_cask

trevorkarn@Trevors-MacBook-Air sage % brew cleanup

Removing: /usr/local/Cellar/gettext/0.20.1... (1,899 files, 18.5MB)

Removing: /usr/local/Cellar/gmp/6.1.2_2... (18 files, 3.1MB)

Removing: /usr/local/Cellar/gnutls/3.6.9... (1,227 files, 9.9MB)

Removing: /usr/local/Cellar/icu4c/64.2... (257 files, 69.2MB)

Removing: /usr/local/Cellar/libevent/2.1.11... (1,063 files, 5MB)

Removing: /usr/local/Cellar/libffi/3.2.1... (16 files, 296.8KB)

Removing: /usr/local/Cellar/libidn2/2.2.0_1... (70 files, 700.9KB)

Removing: /usr/local/Cellar/libtasn1/4.14... (59 files, 384KB)

Removing: /usr/local/Cellar/nettle/3.4.1... (85 files, 2MB)

Error: Interrupted system call @ dir_initialize - /usr/local/Cellar/opus

trevorkarn@Trevors-MacBook-Air sage % ;2D

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 8:38 PM Zachary Scherr  wrote:

> In your original config.log, it looked like sage was picking up its own
> fortran:
>
> configure:11991: gfortran has already been installed by SageMath
> configure:39396: result: gfortran-9.2.0:
>  already installed as an SPKG
>
> The current version of gfortran from homebrew is 10.2.0 version 3
>
> GNU Fortran (Homebrew GCC 10.2.0_3) 10.2.0
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> ./configure should be picking up homebrew's gfortran (installed with gcc),
> and it seems from your config.log file that you do have homebrew and
> therefore you s

Re: [sage-devel] possible bug: kernel of ring homomorphism

[Samuel Lelievre]

For reference this is also asked on Ask Sage:
https://ask.sagemath.org/question/55618

-- 
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/d43f0d17-d243-40ec-98be-65e8ea5f970bn%40googlegroups.com.

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

In your original config.log, it looked like sage was picking up its own 
fortran:

configure:11991: gfortran has already been installed by SageMath
configure:39396: result: gfortran-9.2.0: 
 already installed as an SPKG

The current version of gfortran from homebrew is 10.2.0 version 3

GNU Fortran (Homebrew GCC 10.2.0_3) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

./configure should be picking up homebrew's gfortran (installed with gcc), 
and it seems from your config.log file that you do have homebrew and 
therefore you should have the most recent gfortran.
Do you have the newest config.log file from after running make distclean? 
You may also want to try running

brew doctor

to see if there is something wrong with your homebrew. 
On Monday, February 8, 2021 at 9:27:11 PM UTC-5 Trevor Karn wrote:

> Unfortunately, that did not seem to work. 
>
> Here are the last few lines of the terminal output and I've attached the 
> numpy log.
>
> [singular-4.1.1p2.p0] real 28m38.843s
>
> [singular-4.1.1p2.p0] user 24m18.545s
>
> [singular-4.1.1p2.p0] sys 3m53.423s
>
> [singular-4.1.1p2.p0] Copying package files from temporary location 
> /Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/singular-4.1.1p2.p0/inst
>  
> to /Users/trevorkarn/Applications/sage/local
>
> [singular-4.1.1p2.p0] Successfully installed singular-4.1.1p2.p0
>
> [singular-4.1.1p2.p0] Deleting temporary build directory
>
> [singular-4.1.1p2.p0] 
> /Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/singular-4.1.1p2.p0
>
> [singular-4.1.1p2.p0] Finished installing singular-4.1.1p2.p0
>
> make[2]: *** [all-build] Error 2
>
>
> real 182m14.796s
>
> user 355m33.883s
>
> sys 72m32.388s
>
> ***
>
> Error building Sage.
>
>
> The following package(s) may have failed to build (not necessarily
>
> during this run of 'make all-build'):
>
>
> * package: numpy-1.19.4
>
>   last build time: Feb 8 19:48
>
>   log file:
> /Users/trevorkarn/Applications/sage/logs/pkgs/numpy-1.19.4.log
>
>   build directory: 
> /Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/numpy-1.19.4
>
>
> 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.
>
>
> make[1]: *** [all-build] Error 1
>
> make: *** [build] Error 2
>
> trevorkarn@Trevors-MacBook-Air sage %
>
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 1:56 PM Zachary Scherr  wrote:
>
>> yea, something seems messed up.  For example, the numpy problem was fixed 
>> on beta 6 and should still be fixed in beta 7.  It looks like somehow you 
>> have old files hanging around which are causing problems.  Hopefully make 
>> distclean will clean everything and let you start fresh.
>>
>> On Monday, February 8, 2021 at 2:25:16 PM UTC-5 Trevor Karn wrote:
>>
>>> I must have typed it wrong. The second option you gave failed on numpy, 
>>> but I tried the first option again, and it is compiling.
>>>
>>> Best Regards,
>>>
>>> Trevor Karn
>>>
>>>
>>> On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr  wrote:
>>>
 Are you sure you typed it correctly? Maybe try running

 ./bootstrap

 to make sure that the make targets are in order.

 On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:

> I tried make distclean and got an error “make: *** No rule to make 
> target ‘distclean’. Stop.”
>
> So I tried your second suggestion and it seems to be working so far, 
> but it is still compiling.
>
> On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  
> wrote:
>
>> Probably the thing to try would be:
>>
>> make distclean
>>
>> and then you can build from scratch via:
>>
>> ./bootstrap
>> source .homebrew-build-env
>> ./configure
>> make -j4 build
>>
>> But if you want to try cleaning wheel first before starting from 
>> scratch, you could just try
>>
>> make wheel-clean
>> make -j4 build
>>
>> but it might be better to clean everything and start from scratch.
>>
>> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>>
>>> I do not see pep425tags.py in that directory. 
>>>
>>> trevorkarn@Trevors-MacBook-Air sage % cd 
>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>>
>>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>>
>>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>>
>>> __main__.py bdist_wheel.p

Re: [sage-devel] Trouble building cython

[Trevor Karn]

Unfortunately, that did not seem to work.

Here are the last few lines of the terminal output and I've attached the
numpy log.

[singular-4.1.1p2.p0] real 28m38.843s

[singular-4.1.1p2.p0] user 24m18.545s

[singular-4.1.1p2.p0] sys 3m53.423s

[singular-4.1.1p2.p0] Copying package files from temporary location
/Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/singular-4.1.1p2.p0/inst
to /Users/trevorkarn/Applications/sage/local

[singular-4.1.1p2.p0] Successfully installed singular-4.1.1p2.p0

[singular-4.1.1p2.p0] Deleting temporary build directory

[singular-4.1.1p2.p0]
/Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/singular-4.1.1p2.p0

[singular-4.1.1p2.p0] Finished installing singular-4.1.1p2.p0

make[2]: *** [all-build] Error 2


real 182m14.796s

user 355m33.883s

sys 72m32.388s

***

Error building Sage.


The following package(s) may have failed to build (not necessarily

during this run of 'make all-build'):


* package: numpy-1.19.4

  last build time: Feb 8 19:48

  log file:
/Users/trevorkarn/Applications/sage/logs/pkgs/numpy-1.19.4.log

  build directory:
/Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/numpy-1.19.4


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.


make[1]: *** [all-build] Error 1

make: *** [build] Error 2

trevorkarn@Trevors-MacBook-Air sage %


Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 1:56 PM Zachary Scherr  wrote:

> yea, something seems messed up.  For example, the numpy problem was fixed
> on beta 6 and should still be fixed in beta 7.  It looks like somehow you
> have old files hanging around which are causing problems.  Hopefully make
> distclean will clean everything and let you start fresh.
>
> On Monday, February 8, 2021 at 2:25:16 PM UTC-5 Trevor Karn wrote:
>
>> I must have typed it wrong. The second option you gave failed on numpy,
>> but I tried the first option again, and it is compiling.
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr  wrote:
>>
>>> Are you sure you typed it correctly? Maybe try running
>>>
>>> ./bootstrap
>>>
>>> to make sure that the make targets are in order.
>>>
>>> On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:
>>>
 I tried make distclean and got an error “make: *** No rule to make
 target ‘distclean’. Stop.”

 So I tried your second suggestion and it seems to be working so far,
 but it is still compiling.

 On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr 
 wrote:

> Probably the thing to try would be:
>
> make distclean
>
> and then you can build from scratch via:
>
> ./bootstrap
> source .homebrew-build-env
> ./configure
> make -j4 build
>
> But if you want to try cleaning wheel first before starting from
> scratch, you could just try
>
> make wheel-clean
> make -j4 build
>
> but it might be better to clean everything and start from scratch.
>
> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>
>> I do not see pep425tags.py in that directory.
>>
>> trevorkarn@Trevors-MacBook-Air sage % cd
>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>
>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>
>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>
>> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>>
>> Is there a way to clean the build environment?
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik 
>> wrote:
>>
>>> the only explanation for pep425tags.py would be an unclean build
>>> environment - e.g. weird env vars set, or strange stuff in PATH.
>>>
>>> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr 
>>> wrote:
>>> >
>>> > and do you see that pep425tags.py file in that directory?
>>> >
>>> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>>> >>
>>> >> The only contents of the file you pointed me towards are
>>> >>
>>> >> __version__ = '0.36.2'
>>> >>
>>> >> Best Regards,
>>> >>
>>> >> Trevor Karn
>>> >>
>>> >>
>>> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr 
>>> wrote:
>>> >>>
>>> >>> I really don't understand.  The Cython log file shows that the
>>> problem is in
>>> >>>
>>> >>>
>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>>> >>>
>>> >>> I could be mistaken, but I don't thin

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Matthias Koeppe]

On Monday, February 8, 2021 at 10:42:59 AM UTC-8 Matthias Koeppe wrote:

>
> I think it should be the responsibility of the downstream package to 
> define a versioning policy - define when they plan to drop support for a 
> particular Sage version. 
> Then we can use an appropriate version constraint in the 
> "install-requires.txt" file for this package in build/pkgs.
>

Another thing that a downstream package can do is declare an 
"install_requires" on the Sage library, specifying a supported range of 
versions. Then we should be able to use the dependency resolution by pip to 
be sure to install a compatible version.

Note https://trac.sagemath.org/ticket/30912 updates the metadata of the 
Sage library, defining the distribution name "sagemath-standard". (Another 
distribution that could be used for versioning is "sage_conf".)

Also note the pip dependency resolver has just changed with the update to 
pip 20.3.3 in #30589 (see 
https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020).


 

-- 
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/5194dd30-733d-4c9e-9581-b3fd50f0191dn%40googlegroups.com.

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Thierry]

Hi,

On Mon, Feb 08, 2021 at 10:42:59AM -0800, Matthias Koeppe wrote:
[...]
> As Vincent has pointed out, we currently do not use version
> constraints for
> these (downstream) user packages.

I think that if we do not provide explicit version of downstream
packages, we are going to run into troubles, as we can not expect users
to use latest Sagemath version when they install some downstream
package.

To take the previous example:

https://github.com/mkauers/ore_algebra/commit/8c678f9c70aee8df211c04211dd2f7e230a4770f

without versionning on our side, if a user tries to install ore_algebra
after 7 November 2017 while using 8.0, they would get import errors.

Note also that this downstream change was done during the preparation of
8.1 (that was released on 7 December 2017), so even up-to-date
non-developer users would have been running 8.0 at that time and
therefore get errors.

On Mon, Feb 08, 2021 at 01:17:34PM +0100, Vincent Delecroix wrote:
[...]
> $ cat ore_algebra/requirements.txt
> git+https://github.com/mkauers/ore_algebra@6826ac49b4cdf66a563449aced21a2fd1fd085c9#egg=ore_algebra
>
> If instead ore_algebra would properly release on PyPI, the
> sage side of things would be simpler.

I do not see how having ore_algebra in PyPI would fix the issue of not
providing downstream versions.

Ciao,
Thierry

-- 
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/20210208224808.ebn7ilm3g32o6rdh%40metelu.net.

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

yea, something seems messed up.  For example, the numpy problem was fixed 
on beta 6 and should still be fixed in beta 7.  It looks like somehow you 
have old files hanging around which are causing problems.  Hopefully make 
distclean will clean everything and let you start fresh.

On Monday, February 8, 2021 at 2:25:16 PM UTC-5 Trevor Karn wrote:

> I must have typed it wrong. The second option you gave failed on numpy, 
> but I tried the first option again, and it is compiling.
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr  wrote:
>
>> Are you sure you typed it correctly? Maybe try running
>>
>> ./bootstrap
>>
>> to make sure that the make targets are in order.
>>
>> On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:
>>
>>> I tried make distclean and got an error “make: *** No rule to make 
>>> target ‘distclean’. Stop.”
>>>
>>> So I tried your second suggestion and it seems to be working so far, but 
>>> it is still compiling.
>>>
>>> On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  wrote:
>>>
 Probably the thing to try would be:

 make distclean

 and then you can build from scratch via:

 ./bootstrap
 source .homebrew-build-env
 ./configure
 make -j4 build

 But if you want to try cleaning wheel first before starting from 
 scratch, you could just try

 make wheel-clean
 make -j4 build

 but it might be better to clean everything and start from scratch.

 On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:

> I do not see pep425tags.py in that directory. 
>
> trevorkarn@Trevors-MacBook-Air sage % cd 
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>
> trevorkarn@Trevors-MacBook-Air wheel % ls
>
> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>
> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>
> Is there a way to clean the build environment?
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  
> wrote:
>
>> the only explanation for pep425tags.py would be an unclean build
>> environment - e.g. weird env vars set, or strange stuff in PATH.
>>
>> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  
>> wrote:
>> >
>> > and do you see that pep425tags.py file in that directory?
>> >
>> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>> >>
>> >> The only contents of the file you pointed me towards are
>> >>
>> >> __version__ = '0.36.2'
>> >>
>> >> Best Regards,
>> >>
>> >> Trevor Karn
>> >>
>> >>
>> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  
>> wrote:
>> >>>
>> >>> I really don't understand.  The Cython log file shows that the 
>> problem is in
>> >>>
>> >>> 
>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>> >>>
>> >>> I could be mistaken, but I don't think pep425tags.py has been a 
>> part of the wheel package for a while now.  Certainly when I looked at 
>> wheel on my sage there was no such file.
>> >>>
>> >>> Can you go to your 
>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>  
>> directory and take a look at __init__.py.  Does the version say 0.36.2?
>> >>>
>> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>> 
>> 
>>  Here is what I get. It seems like it is the same as yours?
>> 
>> 
>>  trevorkarn@Trevors-MacBook-Air sage % brew info python3
>> 
>>  python@3.9: stable 3.9.1
>> 
>>  Interpreted, interactive, object-oriented programming language
>> 
>>  https://www.python.org/
>> 
>>  /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>> 
>>    Built from source on 2021-02-05 at 16:39:31
>> 
>>  From: 
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>> 
>>  License: Python-2.0
>> 
>>  ==> Dependencies
>> 
>>  Build: pkg-config ✔
>> 
>>  Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔, 
>> xz ✔
>> 
>>  ==> Caveats
>> 
>>  Python has been installed as
>> 
>>    /usr/local/bin/python3
>> 
>> 
>>  Unversioned symlinks `python`, `python-config`, `pip` etc. 
>> pointing to
>> 
>>  `python3`, `python3-config`, `pip3` etc., respectively, have 
>> been installed into
>> 
>>    /usr/local/opt/python@3.9/libexec/bin
>> 
>> 
>>  You can install Python packages with
>> 
>>    pip3 install 

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I must have typed it wrong. The second option you gave failed on numpy, but
I tried the first option again, and it is compiling.

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr  wrote:

> Are you sure you typed it correctly? Maybe try running
>
> ./bootstrap
>
> to make sure that the make targets are in order.
>
> On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:
>
>> I tried make distclean and got an error “make: *** No rule to make target
>> ‘distclean’. Stop.”
>>
>> So I tried your second suggestion and it seems to be working so far, but
>> it is still compiling.
>>
>> On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  wrote:
>>
>>> Probably the thing to try would be:
>>>
>>> make distclean
>>>
>>> and then you can build from scratch via:
>>>
>>> ./bootstrap
>>> source .homebrew-build-env
>>> ./configure
>>> make -j4 build
>>>
>>> But if you want to try cleaning wheel first before starting from
>>> scratch, you could just try
>>>
>>> make wheel-clean
>>> make -j4 build
>>>
>>> but it might be better to clean everything and start from scratch.
>>>
>>> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>>>
 I do not see pep425tags.py in that directory.

 trevorkarn@Trevors-MacBook-Air sage % cd
 /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/

 trevorkarn@Trevors-MacBook-Air wheel % ls

 __init__.py __pycache__ cli metadata.py util.py wheelfile.py

 __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored

 Is there a way to clean the build environment?

 Best Regards,

 Trevor Karn


 On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:

> the only explanation for pep425tags.py would be an unclean build
> environment - e.g. weird env vars set, or strange stuff in PATH.
>
> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr 
> wrote:
> >
> > and do you see that pep425tags.py file in that directory?
> >
> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
> >>
> >> The only contents of the file you pointed me towards are
> >>
> >> __version__ = '0.36.2'
> >>
> >> Best Regards,
> >>
> >> Trevor Karn
> >>
> >>
> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr 
> wrote:
> >>>
> >>> I really don't understand.  The Cython log file shows that the
> problem is in
> >>>
> >>>
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
> >>>
> >>> I could be mistaken, but I don't think pep425tags.py has been a
> part of the wheel package for a while now.  Certainly when I looked at
> wheel on my sage there was no such file.
> >>>
> >>> Can you go to your
> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
> directory and take a look at __init__.py.  Does the version say 0.36.2?
> >>>
> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
> 
> 
>  Here is what I get. It seems like it is the same as yours?
> 
> 
>  trevorkarn@Trevors-MacBook-Air sage % brew info python3
> 
>  python@3.9: stable 3.9.1
> 
>  Interpreted, interactive, object-oriented programming language
> 
>  https://www.python.org/
> 
>  /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
> 
>    Built from source on 2021-02-05 at 16:39:31
> 
>  From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
> 
>  License: Python-2.0
> 
>  ==> Dependencies
> 
>  Build: pkg-config ✔
> 
>  Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔,
> xz ✔
> 
>  ==> Caveats
> 
>  Python has been installed as
> 
>    /usr/local/bin/python3
> 
> 
>  Unversioned symlinks `python`, `python-config`, `pip` etc.
> pointing to
> 
>  `python3`, `python3-config`, `pip3` etc., respectively, have been
> installed into
> 
>    /usr/local/opt/python@3.9/libexec/bin
> 
> 
>  You can install Python packages with
> 
>    pip3 install 
> 
>  They will install into the site-package directory
> 
>    /usr/local/lib/python3.9/site-packages
> 
> 
>  See: https://docs.brew.sh/Homebrew-and-Python
> 
>  ==> Analytics
> 
>  install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365
> days)
> 
>  install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812
> (365 days)
> 
>  build-error: 0 (30 days)
> 
> 
>  Best Re

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

[dwb...@gmail.com]

With this, I can now build the documentation. (Thanks!)

On Sunday, February 7, 2021 at 1:16:38 PM UTC-8 Matthias Koeppe wrote:

> Please try the current branch on https://trac.sagemath.org/ticket/31344, 
> we have added another fix.
>
> On Sunday, February 7, 2021 at 6:11:55 AM UTC-8 dwb...@gmail.com wrote:
>
>>
>> Even after applying the fix in #31344 I still get a similar crash 
>> building the documentation. I am attaching my dochtml.log.
>>
>> Daniel Bump
>> On Friday, February 5, 2021 at 11:24:59 AM UTC-8 Matthias Koeppe wrote:
>>
>>> Fixed in https://trac.sagemath.org/ticket/31344
>>>
>>> On Thursday, February 4, 2021 at 4:30:45 AM UTC-8 Dima Pasechnik wrote:
>>>
 Probably https://bugs.python.org/issue19733 is still relevant? 
 Note messages 

 test_image (tkinter.test.test_ttk.test_widgets.ButtonTest) ... skipped 
 'crashes with Cocoa Tk (issue19733)' 

 one gets by running 

 python3 runtktests.py 

 Even though 19733 was closed, it's not clear whether they tested on 
 macOS 11. 


 in 
 /usr/local/Cellar/python@3.9/3.9.1_7/Frameworks/Python.framework/Versions/3.9/lib/python3.9/tkinter/test/
  


 On Thu, Feb 4, 2021 at 4:32 AM Zachary Scherr  
 wrote: 
 > 
 > I found something possibly relevant at 
 > 
 > https://bugs.python.org/issue42691 
 > 
 > although there the complaint was that Homebrew built python against 
 system tcl and the suggestion was that Homebrew use its own tcl-tk. It 
 seems that Homebrew is correctly using its own tcl-tk 
 > since the line 
 > 
 > 5 libtcl8.6.dylib 0x00032998c72e AtForkPrepare + 38 
 > 
 > says that python is using tcl 8.6 and system tcl is 8.5. No idea 
 what's going on, but it might be good to try to produce a minimal 
 reproducible example to show to the python/tcl people. 
 > On Wednesday, February 3, 2021 at 12:11:54 PM UTC-5 dim...@gmail.com 
 wrote: 
 >> 
 >> 
 >> 
 >> On Wed, 3 Feb 2021, 17:03 John H Palmieri,  
 wrote: 
 >>> 
 >>> 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 
 >> 
 >> 
 >> yes, I see this too. (with latest Homebrew python 3.9.) 
 >> 
 >> What exactly is broken there? 
 >> 
 >> 
 > 
 > 
 > 
  
 > 0 signals.cpython-39-darwin.so 0x00010cd40542 
 print_backtrace + 66 
 > 1 signals.cpython-39-darwin.so 0x00010cd44167 sigdie + 39 
 > 2 signals.cpython-39-darwin.so 0x00010cd4406a 
 cysigs_signal_handler + 282 
 > 3 libsystem_platform.dylib 0x7fff203bcd7d _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_d

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Matthias Koeppe]

On Monday, February 8, 2021 at 10:42:59 AM UTC-8 Matthias Koeppe wrote:

>
> I think it should be the responsibility of the downstream package to 
> define a versioning policy - define when they plan to drop support for a 
> particular Sage version. 
> Then we can use an appropriate version constraint in the 
> "install-requires.txt" file for this package in build/pkgs.
>

I meant "requirements.txt" actually.

 

-- 
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/8e645573-cde1-4567-b1c6-4bcb5822d84an%40googlegroups.com.

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Matthias Koeppe]

On Monday, February 8, 2021 at 4:06:38 AM UTC-8 Thierry 
(sage-googlesucks@xxx) wrote:

> On Sun, Feb 07, 2021 at 04:49:23PM -0800, Matthias Koeppe wrote: 
> > The first few user packages have been added in 9.3.beta7: 
> > ore_algebra, sage_flatsurf, admcycles, slabbe, surface_dynamics. 
>
> We should notice that, contrary to other packages, those packages should 
> be considered as downstream (not upstream), and this should be reflected 
> in our release process. 
>

That's right, this is an important distinction.

In the current case, it should be the opposite, after downstream adapted 
> their code to our changes, so that those packages are not broken for the 
> official release. 
>
> Hence, there should be a way to update the versions of such packages 
> during beta[-1] (the one before rc0), at least those packages should be 
> tagged "downstream" somewhere (e.g. whithin SPKG.rst file or whatever), 
> so that someone could have a look before the rc. 
>

As Vincent has pointed out, we currently do not use version constraints for 
these (downstream) user packages. 

I think it should be the responsibility of the downstream package to define 
a versioning policy - define when they plan to drop support for a 
particular Sage version. 
Then we can use an appropriate version constraint in the 
"install-requires.txt" file for this package in build/pkgs.

Another question: what happens if at the end of a Sage release cycle, 
> the downstream package is still broken ? Shall we remove the package 
> from build/pkgs ? Shall we add a temporary patch within the spkg 
> directory ? Or add a "broken" keyword for the "type" file ? 


Setting type to "experimental" would be good enough, I think. This already 
issues a scary warning.


-- 
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/b17bbe5c-67be-4ed1-a8c5-3dd5c0199b05n%40googlegroups.com.

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Matthias Koeppe]

On Sunday, February 7, 2021 at 11:55:22 PM UTC-8 vdelecroix wrote:

>
> Should they be removed from the wiki? 
> (https://wiki.sagemath.org/SageMathExternalPackages) 
> The list of "official" user packages are now part of the sage 
> documentation. We could keep the wiki for the not yet integrated 
> user packages. 
>

I would suggest that we remove them from that page when 9.3 is released.

 

-- 
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/43715ad4-f094-4fbf-b8af-df64ba0b6f90n%40googlegroups.com.

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

Are you sure you typed it correctly? Maybe try running

./bootstrap

to make sure that the make targets are in order.

On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:

> I tried make distclean and got an error “make: *** No rule to make target 
> ‘distclean’. Stop.”
>
> So I tried your second suggestion and it seems to be working so far, but 
> it is still compiling.
>
> On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  wrote:
>
>> Probably the thing to try would be:
>>
>> make distclean
>>
>> and then you can build from scratch via:
>>
>> ./bootstrap
>> source .homebrew-build-env
>> ./configure
>> make -j4 build
>>
>> But if you want to try cleaning wheel first before starting from scratch, 
>> you could just try
>>
>> make wheel-clean
>> make -j4 build
>>
>> but it might be better to clean everything and start from scratch.
>>
>> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>>
>>> I do not see pep425tags.py in that directory. 
>>>
>>> trevorkarn@Trevors-MacBook-Air sage % cd 
>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>>
>>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>>
>>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>>
>>> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>>>
>>> Is there a way to clean the build environment?
>>>
>>> Best Regards,
>>>
>>> Trevor Karn
>>>
>>>
>>> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:
>>>
 the only explanation for pep425tags.py would be an unclean build
 environment - e.g. weird env vars set, or strange stuff in PATH.

 On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
 >
 > and do you see that pep425tags.py file in that directory?
 >
 > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
 >>
 >> The only contents of the file you pointed me towards are
 >>
 >> __version__ = '0.36.2'
 >>
 >> Best Regards,
 >>
 >> Trevor Karn
 >>
 >>
 >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  
 wrote:
 >>>
 >>> I really don't understand.  The Cython log file shows that the 
 problem is in
 >>>
 >>> 
 /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
 >>>
 >>> I could be mistaken, but I don't think pep425tags.py has been a 
 part of the wheel package for a while now.  Certainly when I looked at 
 wheel on my sage there was no such file.
 >>>
 >>> Can you go to your 
 "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
  
 directory and take a look at __init__.py.  Does the version say 0.36.2?
 >>>
 >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
 
 
  Here is what I get. It seems like it is the same as yours?
 
 
  trevorkarn@Trevors-MacBook-Air sage % brew info python3
 
  python@3.9: stable 3.9.1
 
  Interpreted, interactive, object-oriented programming language
 
  https://www.python.org/
 
  /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
 
    Built from source on 2021-02-05 at 16:39:31
 
  From: 
 https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
 
  License: Python-2.0
 
  ==> Dependencies
 
  Build: pkg-config ✔
 
  Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔, 
 xz ✔
 
  ==> Caveats
 
  Python has been installed as
 
    /usr/local/bin/python3
 
 
  Unversioned symlinks `python`, `python-config`, `pip` etc. 
 pointing to
 
  `python3`, `python3-config`, `pip3` etc., respectively, have been 
 installed into
 
    /usr/local/opt/python@3.9/libexec/bin
 
 
  You can install Python packages with
 
    pip3 install 
 
  They will install into the site-package directory
 
    /usr/local/lib/python3.9/site-packages
 
 
  See: https://docs.brew.sh/Homebrew-and-Python
 
  ==> Analytics
 
  install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 
 days)
 
  install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 
 (365 days)
 
  build-error: 0 (30 days)
 
 
  Best Regards,
 
  Trevor Karn
 
 
  On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  
 wrote:
 >
 > Could it be that you need to update your Homebrew (?) python3 
 package?
 > What version do you have now?
 > E.g. on a box where the latest Sage builds I have
 >
 > % brew inf

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I tried make distclean and got an error “make: *** No rule to make target
‘distclean’. Stop.”

So I tried your second suggestion and it seems to be working so far, but it
is still compiling.

On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  wrote:

> Probably the thing to try would be:
>
> make distclean
>
> and then you can build from scratch via:
>
> ./bootstrap
> source .homebrew-build-env
> ./configure
> make -j4 build
>
> But if you want to try cleaning wheel first before starting from scratch,
> you could just try
>
> make wheel-clean
> make -j4 build
>
> but it might be better to clean everything and start from scratch.
>
> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>
>> I do not see pep425tags.py in that directory.
>>
>> trevorkarn@Trevors-MacBook-Air sage % cd
>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>
>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>
>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>
>> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>>
>> Is there a way to clean the build environment?
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:
>>
>>> the only explanation for pep425tags.py would be an unclean build
>>> environment - e.g. weird env vars set, or strange stuff in PATH.
>>>
>>> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
>>> >
>>> > and do you see that pep425tags.py file in that directory?
>>> >
>>> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>>> >>
>>> >> The only contents of the file you pointed me towards are
>>> >>
>>> >> __version__ = '0.36.2'
>>> >>
>>> >> Best Regards,
>>> >>
>>> >> Trevor Karn
>>> >>
>>> >>
>>> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr 
>>> wrote:
>>> >>>
>>> >>> I really don't understand.  The Cython log file shows that the
>>> problem is in
>>> >>>
>>> >>>
>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>>> >>>
>>> >>> I could be mistaken, but I don't think pep425tags.py has been a part
>>> of the wheel package for a while now.  Certainly when I looked at wheel on
>>> my sage there was no such file.
>>> >>>
>>> >>> Can you go to your
>>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>> directory and take a look at __init__.py.  Does the version say 0.36.2?
>>> >>>
>>> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>>> 
>>> 
>>>  Here is what I get. It seems like it is the same as yours?
>>> 
>>> 
>>>  trevorkarn@Trevors-MacBook-Air sage % brew info python3
>>> 
>>>  python@3.9: stable 3.9.1
>>> 
>>>  Interpreted, interactive, object-oriented programming language
>>> 
>>>  https://www.python.org/
>>> 
>>>  /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>>> 
>>>    Built from source on 2021-02-05 at 16:39:31
>>> 
>>>  From:
>>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>>> 
>>>  License: Python-2.0
>>> 
>>>  ==> Dependencies
>>> 
>>>  Build: pkg-config ✔
>>> 
>>>  Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔,
>>> xz ✔
>>> 
>>>  ==> Caveats
>>> 
>>>  Python has been installed as
>>> 
>>>    /usr/local/bin/python3
>>> 
>>> 
>>>  Unversioned symlinks `python`, `python-config`, `pip` etc. pointing
>>> to
>>> 
>>>  `python3`, `python3-config`, `pip3` etc., respectively, have been
>>> installed into
>>> 
>>>    /usr/local/opt/python@3.9/libexec/bin
>>> 
>>> 
>>>  You can install Python packages with
>>> 
>>>    pip3 install 
>>> 
>>>  They will install into the site-package directory
>>> 
>>>    /usr/local/lib/python3.9/site-packages
>>> 
>>> 
>>>  See: https://docs.brew.sh/Homebrew-and-Python
>>> 
>>>  ==> Analytics
>>> 
>>>  install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365
>>> days)
>>> 
>>>  install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812
>>> (365 days)
>>> 
>>>  build-error: 0 (30 days)
>>> 
>>> 
>>>  Best Regards,
>>> 
>>>  Trevor Karn
>>> 
>>> 
>>>  On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik 
>>> wrote:
>>> >
>>> > Could it be that you need to update your Homebrew (?) python3
>>> package?
>>> > What version do you have now?
>>> > E.g. on a box where the latest Sage builds I have
>>> >
>>> > % brew info python3
>>> >
>>> > python@3.9: stable 3.9.1 (bottled)
>>> > Interpreted, interactive, object-oriented programming language
>>> > https://www.python.org/
>>> > /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>>> >   Poured from bottle on 2021-02-06 at 10:13:24
>>> > From:
>>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt..

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

Probably the thing to try would be:

make distclean

and then you can build from scratch via:

./bootstrap
source .homebrew-build-env
./configure
make -j4 build

But if you want to try cleaning wheel first before starting from scratch, 
you could just try

make wheel-clean
make -j4 build

but it might be better to clean everything and start from scratch.

On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:

> I do not see pep425tags.py in that directory. 
>
> trevorkarn@Trevors-MacBook-Air sage % cd 
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>
> trevorkarn@Trevors-MacBook-Air wheel % ls
>
> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>
> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>
> Is there a way to clean the build environment?
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:
>
>> the only explanation for pep425tags.py would be an unclean build
>> environment - e.g. weird env vars set, or strange stuff in PATH.
>>
>> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
>> >
>> > and do you see that pep425tags.py file in that directory?
>> >
>> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>> >>
>> >> The only contents of the file you pointed me towards are
>> >>
>> >> __version__ = '0.36.2'
>> >>
>> >> Best Regards,
>> >>
>> >> Trevor Karn
>> >>
>> >>
>> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  
>> wrote:
>> >>>
>> >>> I really don't understand.  The Cython log file shows that the 
>> problem is in
>> >>>
>> >>> 
>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>> >>>
>> >>> I could be mistaken, but I don't think pep425tags.py has been a part 
>> of the wheel package for a while now.  Certainly when I looked at wheel on 
>> my sage there was no such file.
>> >>>
>> >>> Can you go to your 
>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>  
>> directory and take a look at __init__.py.  Does the version say 0.36.2?
>> >>>
>> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>> 
>> 
>>  Here is what I get. It seems like it is the same as yours?
>> 
>> 
>>  trevorkarn@Trevors-MacBook-Air sage % brew info python3
>> 
>>  python@3.9: stable 3.9.1
>> 
>>  Interpreted, interactive, object-oriented programming language
>> 
>>  https://www.python.org/
>> 
>>  /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>> 
>>    Built from source on 2021-02-05 at 16:39:31
>> 
>>  From: 
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>> 
>>  License: Python-2.0
>> 
>>  ==> Dependencies
>> 
>>  Build: pkg-config ✔
>> 
>>  Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔, xz ✔
>> 
>>  ==> Caveats
>> 
>>  Python has been installed as
>> 
>>    /usr/local/bin/python3
>> 
>> 
>>  Unversioned symlinks `python`, `python-config`, `pip` etc. pointing 
>> to
>> 
>>  `python3`, `python3-config`, `pip3` etc., respectively, have been 
>> installed into
>> 
>>    /usr/local/opt/python@3.9/libexec/bin
>> 
>> 
>>  You can install Python packages with
>> 
>>    pip3 install 
>> 
>>  They will install into the site-package directory
>> 
>>    /usr/local/lib/python3.9/site-packages
>> 
>> 
>>  See: https://docs.brew.sh/Homebrew-and-Python
>> 
>>  ==> Analytics
>> 
>>  install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>> 
>>  install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 
>> (365 days)
>> 
>>  build-error: 0 (30 days)
>> 
>> 
>>  Best Regards,
>> 
>>  Trevor Karn
>> 
>> 
>>  On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  
>> wrote:
>> >
>> > Could it be that you need to update your Homebrew (?) python3 
>> package?
>> > What version do you have now?
>> > E.g. on a box where the latest Sage builds I have
>> >
>> > % brew info python3
>> >
>> > python@3.9: stable 3.9.1 (bottled)
>> > Interpreted, interactive, object-oriented programming language
>> > https://www.python.org/
>> > /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>> >   Poured from bottle on 2021-02-06 at 10:13:24
>> > From: 
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>> >
>> >
>> > On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  
>> wrote:
>> > >
>> > > Ah I see, thanks for explaining.
>> > >
>> > > Here is my top-level config.log.
>> > >
>> > > Best Regards,
>> > >
>> > > Trevor Karn
>> > >
>> > >
>> > > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  
>> wrote:
>> > >>
>> > >>
>> > >>
>> > >> On

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I do not see pep425tags.py in that directory.

trevorkarn@Trevors-MacBook-Air sage % cd
/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/

trevorkarn@Trevors-MacBook-Air wheel % ls

__init__.py __pycache__ cli metadata.py util.py wheelfile.py

__main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored

Is there a way to clean the build environment?

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:

> the only explanation for pep425tags.py would be an unclean build
> environment - e.g. weird env vars set, or strange stuff in PATH.
>
> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
> >
> > and do you see that pep425tags.py file in that directory?
> >
> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
> >>
> >> The only contents of the file you pointed me towards are
> >>
> >> __version__ = '0.36.2'
> >>
> >> Best Regards,
> >>
> >> Trevor Karn
> >>
> >>
> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  wrote:
> >>>
> >>> I really don't understand.  The Cython log file shows that the problem
> is in
> >>>
> >>>
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
> >>>
> >>> I could be mistaken, but I don't think pep425tags.py has been a part
> of the wheel package for a while now.  Certainly when I looked at wheel on
> my sage there was no such file.
> >>>
> >>> Can you go to your
> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
> directory and take a look at __init__.py.  Does the version say 0.36.2?
> >>>
> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
> 
> 
>  Here is what I get. It seems like it is the same as yours?
> 
> 
>  trevorkarn@Trevors-MacBook-Air sage % brew info python3
> 
>  python@3.9: stable 3.9.1
> 
>  Interpreted, interactive, object-oriented programming language
> 
>  https://www.python.org/
> 
>  /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
> 
>    Built from source on 2021-02-05 at 16:39:31
> 
>  From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
> 
>  License: Python-2.0
> 
>  ==> Dependencies
> 
>  Build: pkg-config ✔
> 
>  Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔, xz ✔
> 
>  ==> Caveats
> 
>  Python has been installed as
> 
>    /usr/local/bin/python3
> 
> 
>  Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
> 
>  `python3`, `python3-config`, `pip3` etc., respectively, have been
> installed into
> 
>    /usr/local/opt/python@3.9/libexec/bin
> 
> 
>  You can install Python packages with
> 
>    pip3 install 
> 
>  They will install into the site-package directory
> 
>    /usr/local/lib/python3.9/site-packages
> 
> 
>  See: https://docs.brew.sh/Homebrew-and-Python
> 
>  ==> Analytics
> 
>  install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
> 
>  install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812
> (365 days)
> 
>  build-error: 0 (30 days)
> 
> 
>  Best Regards,
> 
>  Trevor Karn
> 
> 
>  On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik 
> wrote:
> >
> > Could it be that you need to update your Homebrew (?) python3
> package?
> > What version do you have now?
> > E.g. on a box where the latest Sage builds I have
> >
> > % brew info python3
> >
> > python@3.9: stable 3.9.1 (bottled)
> > Interpreted, interactive, object-oriented programming language
> > https://www.python.org/
> > /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
> >   Poured from bottle on 2021-02-06 at 10:13:24
> > From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
> >
> >
> > On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn 
> wrote:
> > >
> > > Ah I see, thanks for explaining.
> > >
> > > Here is my top-level config.log.
> > >
> > > Best Regards,
> > >
> > > Trevor Karn
> > >
> > >
> > > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik 
> wrote:
> > >>
> > >>
> > >>
> > >> On Mon, 8 Feb 2021, 13:02 Trevor Karn, 
> wrote:
> > >>>
> > >>> Thanks for sending that link. I am confused though, because it
> says a fix was issued. Does that mean it should work now?
> > >>
> > >>
> > >> sorry, I was not clear. What I meant to say that it appears to be
> a well-known issue in the Python@macOS universe,
> > >> and lately all seems to be OK with Sage.
> > >>
> > >> To figure out exactly goes wrong in your case, we need to know
> where Python3 used in Sage is coming from.
> > >> Please post the top-level config.log
> > >>
> > >>
> > >>>
> > >>> And ye

Re: [sage-devel] Trouble building cython

[Dima Pasechnik]

the only explanation for pep425tags.py would be an unclean build
environment - e.g. weird env vars set, or strange stuff in PATH.

On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
>
> and do you see that pep425tags.py file in that directory?
>
> On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>>
>> The only contents of the file you pointed me towards are
>>
>> __version__ = '0.36.2'
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  wrote:
>>>
>>> I really don't understand.  The Cython log file shows that the problem is in
>>>
>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>>>
>>> I could be mistaken, but I don't think pep425tags.py has been a part of the 
>>> wheel package for a while now.  Certainly when I looked at wheel on my sage 
>>> there was no such file.
>>>
>>> Can you go to your 
>>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>>  directory and take a look at __init__.py.  Does the version say 0.36.2?
>>>
>>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:


 Here is what I get. It seems like it is the same as yours?


 trevorkarn@Trevors-MacBook-Air sage % brew info python3

 python@3.9: stable 3.9.1

 Interpreted, interactive, object-oriented programming language

 https://www.python.org/

 /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *

   Built from source on 2021-02-05 at 16:39:31

 From: 
 https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb

 License: Python-2.0

 ==> Dependencies

 Build: pkg-config ✔

 Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔, xz ✔

 ==> Caveats

 Python has been installed as

   /usr/local/bin/python3


 Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to

 `python3`, `python3-config`, `pip3` etc., respectively, have been 
 installed into

   /usr/local/opt/python@3.9/libexec/bin


 You can install Python packages with

   pip3 install 

 They will install into the site-package directory

   /usr/local/lib/python3.9/site-packages


 See: https://docs.brew.sh/Homebrew-and-Python

 ==> Analytics

 install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)

 install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365 
 days)

 build-error: 0 (30 days)


 Best Regards,

 Trevor Karn


 On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>
> Could it be that you need to update your Homebrew (?) python3 package?
> What version do you have now?
> E.g. on a box where the latest Sage builds I have
>
> % brew info python3
>
> python@3.9: stable 3.9.1 (bottled)
> Interpreted, interactive, object-oriented programming language
> https://www.python.org/
> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>   Poured from bottle on 2021-02-06 at 10:13:24
> From: 
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>
>
> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  wrote:
> >
> > Ah I see, thanks for explaining.
> >
> > Here is my top-level config.log.
> >
> > Best Regards,
> >
> > Trevor Karn
> >
> >
> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  wrote:
> >>
> >>
> >>
> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
> >>>
> >>> Thanks for sending that link. I am confused though, because it says a 
> >>> fix was issued. Does that mean it should work now?
> >>
> >>
> >> sorry, I was not clear. What I meant to say that it appears to be a 
> >> well-known issue in the Python@macOS universe,
> >> and lately all seems to be OK with Sage.
> >>
> >> To figure out exactly goes wrong in your case, we need to know where 
> >> Python3 used in Sage is coming from.
> >> Please post the top-level config.log
> >>
> >>
> >>>
> >>> And yes, I am on the most recent develop branch
> >>>
> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  
> >>> wrote:
> 
>  This seems to be well-known issue, see e.g
>  https://github.com/pypa/virtualenv/issues/2027
> 
>  Are you on the most recent develop branch (9.3.beta7)?
> 
>  On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn  
>  wrote:
>  >
>  > Hi,
>  >
>  > I'm trying to build Sage from the source code. I cloned it from 
>  > git, and tried to build from the develop branch using make from 
>  > the sage directory. I ran into trouble building cython. The error 
>  > mess

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

and do you see that pep425tags.py file in that directory?

On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:

> The only contents of the file you pointed me towards are
>
> __version__ = '0.36.2'
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  wrote:
>
>> I really don't understand.  The Cython log file shows that the problem is 
>> in
>>
>>
>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>>
>> I could be mistaken, but I don't think pep425tags.py has been a part of 
>> the wheel package for a while now.  Certainly when I looked at wheel on my 
>> sage there was no such file.
>>
>> Can you go to your 
>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>  
>> directory and take a look at __init__.py.  Does the version say 0.36.2?
>>
>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>>
>>>
>>> Here is what I get. It seems like it is the same as yours?
>>>
>>>
>>> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>>>
>>> python@3.9: stable 3.9.1
>>>
>>> Interpreted, interactive, object-oriented programming language
>>>
>>> https://www.python.org/
>>>
>>> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>>>
>>>   Built from source on 2021-02-05 at 16:39:31
>>>
>>> From: 
>>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb 
>>> 
>>>
>>> License: Python-2.0
>>>
>>> ==> *Dependencies*
>>>
>>> Build: *pkg-config **✔*
>>>
>>> Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, 
>>> *tcl-tk 
>>> **✔*, *xz **✔*
>>>
>>> ==> *Caveats*
>>>
>>> Python has been installed as
>>>
>>>   /usr/local/bin/python3
>>>
>>>
>>> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
>>>
>>> `python3`, `python3-config`, `pip3` etc., respectively, have been 
>>> installed into
>>>
>>>   /usr/local/opt/python@3.9/libexec/bin
>>>
>>>
>>> You can install Python packages with
>>>
>>>   pip3 install 
>>>
>>> They will install into the site-package directory
>>>
>>>   /usr/local/lib/python3.9/site-packages
>>>
>>>
>>> See: https://docs.brew.sh/Homebrew-and-Python
>>>
>>> ==> *Analytics*
>>>
>>> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>>>
>>> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365 
>>> days)
>>>
>>> build-error: 0 (30 days)
>>>
>>> Best Regards,
>>>
>>> Trevor Karn
>>>
>>>
>>> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>>>
 Could it be that you need to update your Homebrew (?) python3 package?
 What version do you have now?
 E.g. on a box where the latest Sage builds I have

 % brew info python3

 python@3.9: stable 3.9.1 (bottled)
 Interpreted, interactive, object-oriented programming language
 https://www.python.org/
 /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
   Poured from bottle on 2021-02-06 at 10:13:24
 From: 
 https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb 
 


 On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  wrote:
 >
 > Ah I see, thanks for explaining.
 >
 > Here is my top-level config.log.
 >
 > Best Regards,
 >
 > Trevor Karn
 >
 >
 > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  
 wrote:
 >>
 >>
 >>
 >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
 >>>
 >>> Thanks for sending that link. I am confused though, because it says 
 a fix was issued. Does that mean it should work now?
 >>
 >>
 >> sorry, I was not clear. What I meant to say that it appears to be a 
 well-known issue in the Python@macOS universe,
 >> and lately all seems to be OK with Sage.
 >>
 >> To figure out exactly goes wrong in your case, we need to know where 
 Python3 used in Sage is coming from.
 >> Please post the top-level config.log
 >>
 >>
 >>>
 >>> And yes, I am on the most recent develop branch
 >>>
 >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  
 wrote:
 
  This seems to be well-known issue, see e.g
  https://github.com/pypa/virtualenv/issues/2027
 
  Are you on the most recent develop branch (9.3.beta7)?
 
  On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn  
 wrote:
  >
  > Hi,
  >
  > I'm trying to build Sage from the source code. I cloned it from 
 git, and tried to build from the develop branch using make from the sage 
 directory. I ran into trouble building cython. The error message suggested 
 that I email this group. Does anyone have any advice on how to proceed?
  >
  > I am using macOS Big Sur 11.2 on a MacBook Air.
  >
 >>

Re: [sage-devel] Trouble building cython

[Trevor Karn]

The only contents of the file you pointed me towards are

__version__ = '0.36.2'

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  wrote:

> I really don't understand.  The Cython log file shows that the problem is
> in
>
>
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>
> I could be mistaken, but I don't think pep425tags.py has been a part of
> the wheel package for a while now.  Certainly when I looked at wheel on my
> sage there was no such file.
>
> Can you go to your
> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
> directory and take a look at __init__.py.  Does the version say 0.36.2?
>
> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>
>>
>> Here is what I get. It seems like it is the same as yours?
>>
>>
>> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>>
>> python@3.9: stable 3.9.1
>>
>> Interpreted, interactive, object-oriented programming language
>>
>> https://www.python.org/
>>
>> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>>
>>   Built from source on 2021-02-05 at 16:39:31
>>
>> From:
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>> 
>>
>> License: Python-2.0
>>
>> ==> *Dependencies*
>>
>> Build: *pkg-config **✔*
>>
>> Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, 
>> *tcl-tk
>> **✔*, *xz **✔*
>>
>> ==> *Caveats*
>>
>> Python has been installed as
>>
>>   /usr/local/bin/python3
>>
>>
>> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
>>
>> `python3`, `python3-config`, `pip3` etc., respectively, have been
>> installed into
>>
>>   /usr/local/opt/python@3.9/libexec/bin
>>
>>
>> You can install Python packages with
>>
>>   pip3 install 
>>
>> They will install into the site-package directory
>>
>>   /usr/local/lib/python3.9/site-packages
>>
>>
>> See: https://docs.brew.sh/Homebrew-and-Python
>>
>> ==> *Analytics*
>>
>> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>>
>> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365
>> days)
>>
>> build-error: 0 (30 days)
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>>
>>> Could it be that you need to update your Homebrew (?) python3 package?
>>> What version do you have now?
>>> E.g. on a box where the latest Sage builds I have
>>>
>>> % brew info python3
>>>
>>> python@3.9: stable 3.9.1 (bottled)
>>> Interpreted, interactive, object-oriented programming language
>>> https://www.python.org/
>>> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>>>   Poured from bottle on 2021-02-06 at 10:13:24
>>> From:
>>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>>> 
>>>
>>>
>>> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  wrote:
>>> >
>>> > Ah I see, thanks for explaining.
>>> >
>>> > Here is my top-level config.log.
>>> >
>>> > Best Regards,
>>> >
>>> > Trevor Karn
>>> >
>>> >
>>> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik 
>>> wrote:
>>> >>
>>> >>
>>> >>
>>> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
>>> >>>
>>> >>> Thanks for sending that link. I am confused though, because it says
>>> a fix was issued. Does that mean it should work now?
>>> >>
>>> >>
>>> >> sorry, I was not clear. What I meant to say that it appears to be a
>>> well-known issue in the Python@macOS universe,
>>> >> and lately all seems to be OK with Sage.
>>> >>
>>> >> To figure out exactly goes wrong in your case, we need to know where
>>> Python3 used in Sage is coming from.
>>> >> Please post the top-level config.log
>>> >>
>>> >>
>>> >>>
>>> >>> And yes, I am on the most recent develop branch
>>> >>>
>>> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik 
>>> wrote:
>>> 
>>>  This seems to be well-known issue, see e.g
>>>  https://github.com/pypa/virtualenv/issues/2027
>>> 
>>>  Are you on the most recent develop branch (9.3.beta7)?
>>> 
>>>  On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
>>> wrote:
>>>  >
>>>  > Hi,
>>>  >
>>>  > I'm trying to build Sage from the source code. I cloned it from
>>> git, and tried to build from the develop branch using make from the sage
>>> directory. I ran into trouble building cython. The error message suggested
>>> that I email this group. Does anyone have any advice on how to proceed?
>>>  >
>>>  > I am using macOS Big Sur 11.2 on a MacBook Air.
>>>  >
>>>  > The log file is attached, this is from a second run - it failed
>>> once, and I tried running make a second time without any changes and this
>>> is the log from the second run, which returns the same error just without
>>> all of the info before it (eg. the flint installation).
>>>  >
>>>  > Thanks so much.
>>> >

Re: [sage-devel] Trouble building cython

[Zachary Scherr]

I really don't understand.  The Cython log file shows that the problem is in

/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py

I could be mistaken, but I don't think pep425tags.py has been a part of the 
wheel package for a while now.  Certainly when I looked at wheel on my sage 
there was no such file.

Can you go to your 
"/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/" 
directory and take a look at __init__.py.  Does the version say 0.36.2?

On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:

>
> Here is what I get. It seems like it is the same as yours?
>
>
> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>
> python@3.9: stable 3.9.1
>
> Interpreted, interactive, object-oriented programming language
>
> https://www.python.org/
>
> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>
>   Built from source on 2021-02-05 at 16:39:31
>
> From: 
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb 
> 
>
> License: Python-2.0
>
> ==> *Dependencies*
>
> Build: *pkg-config **✔*
>
> Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, 
> *tcl-tk 
> **✔*, *xz **✔*
>
> ==> *Caveats*
>
> Python has been installed as
>
>   /usr/local/bin/python3
>
>
> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
>
> `python3`, `python3-config`, `pip3` etc., respectively, have been 
> installed into
>
>   /usr/local/opt/python@3.9/libexec/bin
>
>
> You can install Python packages with
>
>   pip3 install 
>
> They will install into the site-package directory
>
>   /usr/local/lib/python3.9/site-packages
>
>
> See: https://docs.brew.sh/Homebrew-and-Python
>
> ==> *Analytics*
>
> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>
> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365 
> days)
>
> build-error: 0 (30 days)
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>
>> Could it be that you need to update your Homebrew (?) python3 package?
>> What version do you have now?
>> E.g. on a box where the latest Sage builds I have
>>
>> % brew info python3
>>
>> python@3.9: stable 3.9.1 (bottled)
>> Interpreted, interactive, object-oriented programming language
>> https://www.python.org/
>> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>>   Poured from bottle on 2021-02-06 at 10:13:24
>> From: 
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb 
>> 
>>
>>
>> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  wrote:
>> >
>> > Ah I see, thanks for explaining.
>> >
>> > Here is my top-level config.log.
>> >
>> > Best Regards,
>> >
>> > Trevor Karn
>> >
>> >
>> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  wrote:
>> >>
>> >>
>> >>
>> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
>> >>>
>> >>> Thanks for sending that link. I am confused though, because it says a 
>> fix was issued. Does that mean it should work now?
>> >>
>> >>
>> >> sorry, I was not clear. What I meant to say that it appears to be a 
>> well-known issue in the Python@macOS universe,
>> >> and lately all seems to be OK with Sage.
>> >>
>> >> To figure out exactly goes wrong in your case, we need to know where 
>> Python3 used in Sage is coming from.
>> >> Please post the top-level config.log
>> >>
>> >>
>> >>>
>> >>> And yes, I am on the most recent develop branch
>> >>>
>> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  
>> wrote:
>> 
>>  This seems to be well-known issue, see e.g
>>  https://github.com/pypa/virtualenv/issues/2027
>> 
>>  Are you on the most recent develop branch (9.3.beta7)?
>> 
>>  On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn  
>> wrote:
>>  >
>>  > Hi,
>>  >
>>  > I'm trying to build Sage from the source code. I cloned it from 
>> git, and tried to build from the develop branch using make from the sage 
>> directory. I ran into trouble building cython. The error message suggested 
>> that I email this group. Does anyone have any advice on how to proceed?
>>  >
>>  > I am using macOS Big Sur 11.2 on a MacBook Air.
>>  >
>>  > The log file is attached, this is from a second run - it failed 
>> once, and I tried running make a second time without any changes and this 
>> is the log from the second run, which returns the same error just without 
>> all of the info before it (eg. the flint installation).
>>  >
>>  > Thanks so much.
>>  >
>>  > Best,
>>  > Trevor
>>  >
>>  > --
>>  > 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 

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I also have this. Is there any reason it might be calling python instead of
python3?

trevorkarn@Trevors-MacBook-Air sage % python3 --version

Python 3.9.1

trevorkarn@Trevors-MacBook-Air sage % python --version

Python 2.7.16

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 8:28 AM Trevor Karn  wrote:

>
> Here is what I get. It seems like it is the same as yours?
>
>
> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>
> python@3.9: stable 3.9.1
>
> Interpreted, interactive, object-oriented programming language
>
> https://www.python.org/
>
> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>
>   Built from source on 2021-02-05 at 16:39:31
>
> From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>
> License: Python-2.0
>
> ==> *Dependencies*
>
> Build: *pkg-config **✔*
>
> Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, *tcl-tk
> **✔*, *xz **✔*
>
> ==> *Caveats*
>
> Python has been installed as
>
>   /usr/local/bin/python3
>
>
> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
>
> `python3`, `python3-config`, `pip3` etc., respectively, have been
> installed into
>
>   /usr/local/opt/python@3.9/libexec/bin
>
>
> You can install Python packages with
>
>   pip3 install 
>
> They will install into the site-package directory
>
>   /usr/local/lib/python3.9/site-packages
>
>
> See: https://docs.brew.sh/Homebrew-and-Python
>
> ==> *Analytics*
>
> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>
> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365
> days)
>
> build-error: 0 (30 days)
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>
>> Could it be that you need to update your Homebrew (?) python3 package?
>> What version do you have now?
>> E.g. on a box where the latest Sage builds I have
>>
>> % brew info python3
>>
>> python@3.9: stable 3.9.1 (bottled)
>> Interpreted, interactive, object-oriented programming language
>> https://www.python.org/
>> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>>   Poured from bottle on 2021-02-06 at 10:13:24
>> From:
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>>
>>
>> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn 
>> wrote:
>> >
>> > Ah I see, thanks for explaining.
>> >
>> > Here is my top-level config.log.
>> >
>> > Best Regards,
>> >
>> > Trevor Karn
>> >
>> >
>> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik 
>> wrote:
>> >>
>> >>
>> >>
>> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn, 
>> wrote:
>> >>>
>> >>> Thanks for sending that link. I am confused though, because it says a
>> fix was issued. Does that mean it should work now?
>> >>
>> >>
>> >> sorry, I was not clear. What I meant to say that it appears to be a
>> well-known issue in the Python@macOS universe,
>> >> and lately all seems to be OK with Sage.
>> >>
>> >> To figure out exactly goes wrong in your case, we need to know where
>> Python3 used in Sage is coming from.
>> >> Please post the top-level config.log
>> >>
>> >>
>> >>>
>> >>> And yes, I am on the most recent develop branch
>> >>>
>> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik 
>> wrote:
>> 
>>  This seems to be well-known issue, see e.g
>>  https://github.com/pypa/virtualenv/issues/2027
>> 
>>  Are you on the most recent develop branch (9.3.beta7)?
>> 
>>  On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
>> wrote:
>>  >
>>  > Hi,
>>  >
>>  > I'm trying to build Sage from the source code. I cloned it from
>> git, and tried to build from the develop branch using make from the sage
>> directory. I ran into trouble building cython. The error message suggested
>> that I email this group. Does anyone have any advice on how to proceed?
>>  >
>>  > I am using macOS Big Sur 11.2 on a MacBook Air.
>>  >
>>  > The log file is attached, this is from a second run - it failed
>> once, and I tried running make a second time without any changes and this
>> is the log from the second run, which returns the same error just without
>> all of the info before it (eg. the flint installation).
>>  >
>>  > Thanks so much.
>>  >
>>  > Best,
>>  > Trevor
>>  >
>>  > --
>>  > 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/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com
>> .
>> 
>>  --
>>  You received this message because you are subscribed to a topic in
>> the Google Groups "sage-devel" group.
>>  To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
>>  To unsubscribe from this group and all its 

Re: [sage-devel] Trouble building cython

[Trevor Karn]

Here is what I get. It seems like it is the same as yours?


trevorkarn@Trevors-MacBook-Air sage % brew info python3

python@3.9: stable 3.9.1

Interpreted, interactive, object-oriented programming language

https://www.python.org/

/usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *

  Built from source on 2021-02-05 at 16:39:31

From:
https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb

License: Python-2.0

==> *Dependencies*

Build: *pkg-config **✔*

Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, *tcl-tk
**✔*, *xz **✔*

==> *Caveats*

Python has been installed as

  /usr/local/bin/python3


Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to

`python3`, `python3-config`, `pip3` etc., respectively, have been installed
into

  /usr/local/opt/python@3.9/libexec/bin


You can install Python packages with

  pip3 install 

They will install into the site-package directory

  /usr/local/lib/python3.9/site-packages


See: https://docs.brew.sh/Homebrew-and-Python

==> *Analytics*

install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)

install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365 days)

build-error: 0 (30 days)

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:

> Could it be that you need to update your Homebrew (?) python3 package?
> What version do you have now?
> E.g. on a box where the latest Sage builds I have
>
> % brew info python3
>
> python@3.9: stable 3.9.1 (bottled)
> Interpreted, interactive, object-oriented programming language
> https://www.python.org/
> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>   Poured from bottle on 2021-02-06 at 10:13:24
> From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>
>
> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn 
> wrote:
> >
> > Ah I see, thanks for explaining.
> >
> > Here is my top-level config.log.
> >
> > Best Regards,
> >
> > Trevor Karn
> >
> >
> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  wrote:
> >>
> >>
> >>
> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
> >>>
> >>> Thanks for sending that link. I am confused though, because it says a
> fix was issued. Does that mean it should work now?
> >>
> >>
> >> sorry, I was not clear. What I meant to say that it appears to be a
> well-known issue in the Python@macOS universe,
> >> and lately all seems to be OK with Sage.
> >>
> >> To figure out exactly goes wrong in your case, we need to know where
> Python3 used in Sage is coming from.
> >> Please post the top-level config.log
> >>
> >>
> >>>
> >>> And yes, I am on the most recent develop branch
> >>>
> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik 
> wrote:
> 
>  This seems to be well-known issue, see e.g
>  https://github.com/pypa/virtualenv/issues/2027
> 
>  Are you on the most recent develop branch (9.3.beta7)?
> 
>  On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
> wrote:
>  >
>  > Hi,
>  >
>  > I'm trying to build Sage from the source code. I cloned it from
> git, and tried to build from the develop branch using make from the sage
> directory. I ran into trouble building cython. The error message suggested
> that I email this group. Does anyone have any advice on how to proceed?
>  >
>  > I am using macOS Big Sur 11.2 on a MacBook Air.
>  >
>  > The log file is attached, this is from a second run - it failed
> once, and I tried running make a second time without any changes and this
> is the log from the second run, which returns the same error just without
> all of the info before it (eg. the flint installation).
>  >
>  > Thanks so much.
>  >
>  > Best,
>  > Trevor
>  >
>  > --
>  > 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/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com
> .
> 
>  --
>  You received this message because you are subscribed to a topic in
> the Google Groups "sage-devel" group.
>  To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
>  To unsubscribe from this group and all its topics, 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/CAAWYfq3CFFAYzUtNnSrt_RPKW7X_p8j_VXGtZbKLWG%2BST%3DCO%2BQ%40mail.gmail.com
> .
> >>>
> >>> --
> >>> Best,
> >>>
> >>> Trevor
> >>>
> >>> --
> >>> 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+unsubsc

[sage-devel] Re: [GSoC Mentors Announce] Now Accepting GSoC 2021 Mentoring Organization Applications until Feb 19

[mmarco]

I have participated as mentor other years... but this year I just don't 
think I have the needed energy.

I think Harald's proposal to pass this year and reconsider the next one 
makes sense (sadly).
El domingo, 7 de febrero de 2021 a las 17:54:07 UTC+1, harald@gmail.com 
escribió:

> Hi, a word from my side: I would really like to stop being admin as well 
> and hope someone else can take over. I'm the one writing the application 
> each year and I could this time around, but in general I want to focus on 
> other things after all those years.
>
> Despite that, looks like there are only two mentors. Feels like this is 
> below the threshold where it makes sense to pursue this? Maybe we should 
> pass this year and re-evaluate for the next one?
>
> -- Harald
>
>
>
>

-- 
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/9526f83f-77e0-4cd6-bab9-3973401fa03bn%40googlegroups.com.

Re: [sage-devel] Trouble building cython

[Dima Pasechnik]

Could it be that you need to update your Homebrew (?) python3 package?
What version do you have now?
E.g. on a box where the latest Sage builds I have

% brew info python3

python@3.9: stable 3.9.1 (bottled)
Interpreted, interactive, object-oriented programming language
https://www.python.org/
/usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
  Poured from bottle on 2021-02-06 at 10:13:24
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb


On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  wrote:
>
> Ah I see, thanks for explaining.
>
> Here is my top-level config.log.
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  wrote:
>>
>>
>>
>> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
>>>
>>> Thanks for sending that link. I am confused though, because it says a fix 
>>> was issued. Does that mean it should work now?
>>
>>
>> sorry, I was not clear. What I meant to say that it appears to be a 
>> well-known issue in the Python@macOS universe,
>> and lately all seems to be OK with Sage.
>>
>> To figure out exactly goes wrong in your case, we need to know where Python3 
>> used in Sage is coming from.
>> Please post the top-level config.log
>>
>>
>>>
>>> And yes, I am on the most recent develop branch
>>>
>>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  wrote:

 This seems to be well-known issue, see e.g
 https://github.com/pypa/virtualenv/issues/2027

 Are you on the most recent develop branch (9.3.beta7)?

 On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn  wrote:
 >
 > Hi,
 >
 > I'm trying to build Sage from the source code. I cloned it from git, and 
 > tried to build from the develop branch using make from the sage 
 > directory. I ran into trouble building cython. The error message 
 > suggested that I email this group. Does anyone have any advice on how to 
 > proceed?
 >
 > I am using macOS Big Sur 11.2 on a MacBook Air.
 >
 > The log file is attached, this is from a second run - it failed once, 
 > and I tried running make a second time without any changes and this is 
 > the log from the second run, which returns the same error just without 
 > all of the info before it (eg. the flint installation).
 >
 > Thanks so much.
 >
 > Best,
 > Trevor
 >
 > --
 > 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/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com.

 --
 You received this message because you are subscribed to a topic in the 
 Google Groups "sage-devel" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
 To unsubscribe from this group and all its topics, 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/CAAWYfq3CFFAYzUtNnSrt_RPKW7X_p8j_VXGtZbKLWG%2BST%3DCO%2BQ%40mail.gmail.com.
>>>
>>> --
>>> Best,
>>>
>>> Trevor
>>>
>>> --
>>> 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/CAJ6VCMAVGG57CHovd7zoXa0C3Nxsr3WfXi0FWwapKrDfup7_sA%40mail.gmail.com.
>>
>> --
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "sage-devel" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAAWYfq026cNP9FTmBySPskZZoc%2BH4ykTQO7je6TW4YTkirg_qw%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/CAJ6VCMDJEN7KzDmvB0x0GDrXiQrK3F_e_eBZvSJf-JxVre0n-Q%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/C

Re: [sage-devel] Trouble building cython

[Dima Pasechnik]

On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:

> Thanks for sending that link. I am confused though, because it says a fix
> was issued. Does that mean it should work now?
>

sorry, I was not clear. What I meant to say that it appears to be a
well-known issue in the Python@macOS universe,
and lately all seems to be OK with Sage.

To figure out exactly goes wrong in your case, we need to know where
Python3 used in Sage is coming from.
Please post the top-level config.log



> And yes, I am on the most recent develop branch
>
> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  wrote:
>
>> This seems to be well-known issue, see e.g
>> https://github.com/pypa/virtualenv/issues/2027
>>
>> Are you on the most recent develop branch (9.3.beta7)?
>>
>> On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
>> wrote:
>> >
>> > Hi,
>> >
>> > I'm trying to build Sage from the source code. I cloned it from git,
>> and tried to build from the develop branch using make from the sage
>> directory. I ran into trouble building cython. The error message suggested
>> that I email this group. Does anyone have any advice on how to proceed?
>> >
>> > I am using macOS Big Sur 11.2 on a MacBook Air.
>> >
>> > The log file is attached, this is from a second run - it failed once,
>> and I tried running make a second time without any changes and this is the
>> log from the second run, which returns the same error just without all of
>> the info before it (eg. the flint installation).
>> >
>> > Thanks so much.
>> >
>> > Best,
>> > Trevor
>> >
>> > --
>> > 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/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com
>> .
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "sage-devel" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAAWYfq3CFFAYzUtNnSrt_RPKW7X_p8j_VXGtZbKLWG%2BST%3DCO%2BQ%40mail.gmail.com
>> .
>>
> --
> Best,
>
> Trevor
>
> --
> 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/CAJ6VCMAVGG57CHovd7zoXa0C3Nxsr3WfXi0FWwapKrDfup7_sA%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/CAAWYfq026cNP9FTmBySPskZZoc%2BH4ykTQO7je6TW4YTkirg_qw%40mail.gmail.com.

Re: [sage-devel] Trouble building cython

[Trevor Karn]

Thanks for sending that link. I am confused though, because it says a fix
was issued. Does that mean it should work now?

And yes, I am on the most recent develop branch

On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  wrote:

> This seems to be well-known issue, see e.g
> https://github.com/pypa/virtualenv/issues/2027
>
> Are you on the most recent develop branch (9.3.beta7)?
>
> On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
> wrote:
> >
> > Hi,
> >
> > I'm trying to build Sage from the source code. I cloned it from git, and
> tried to build from the develop branch using make from the sage directory.
> I ran into trouble building cython. The error message suggested that I
> email this group. Does anyone have any advice on how to proceed?
> >
> > I am using macOS Big Sur 11.2 on a MacBook Air.
> >
> > The log file is attached, this is from a second run - it failed once,
> and I tried running make a second time without any changes and this is the
> log from the second run, which returns the same error just without all of
> the info before it (eg. the flint installation).
> >
> > Thanks so much.
> >
> > Best,
> > Trevor
> >
> > --
> > 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/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com
> .
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAAWYfq3CFFAYzUtNnSrt_RPKW7X_p8j_VXGtZbKLWG%2BST%3DCO%2BQ%40mail.gmail.com
> .
>
-- 
Best,

Trevor

-- 
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/CAJ6VCMAVGG57CHovd7zoXa0C3Nxsr3WfXi0FWwapKrDfup7_sA%40mail.gmail.com.

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Vincent Delecroix]

For most of the packages, there is no explicit version tracking. On
the current rather small list only ore_algebra has an explicit
reference to a commit in requirements.txt

$ cat admcycles/requirements.txt
admcycles

$ cat surface_dynamics/requirements.txt
surface_dynamics

$ cat ore_algebra/requirements.txt
git+https://github.com/mkauers/ore_algebra@6826ac49b4cdf66a563449aced21a2fd1fd085c9#egg=ore_algebra

If instead ore_algebra would properly release on PyPI, the
sage side of things would be simpler.

Best
Vincent

PS: still there is the issue of "old" SageMath versions that might
not be compatible with "recent" package versions. The only mechanism
is to tight a single version of a package to a SageMath version as it
was done with ore_algebra. The latter is quite restrictive given that
packges might evolve between two sage releases.

Le 08/02/2021 à 13:06, Thierry a écrit :

Hi,

On Sun, Feb 07, 2021 at 04:49:23PM -0800, Matthias Koeppe wrote:

The first few user packages have been added in 9.3.beta7:
ore_algebra, sage_flatsurf, admcycles, slabbe, surface_dynamics.


We should notice that, contrary to other packages, those packages should
be considered as downstream (not upstream), and this should be reflected
in our release process.

Indeed, their code get adapted after Sage changes, see e.g. (randomly
chosen examples):

https://github.com/mkauers/ore_algebra/commit/2d71b50ebad81e62432482facfe3f78cc4961c4f
https://github.com/mkauers/ore_algebra/commit/8c678f9c70aee8df211c04211dd2f7e230a4770f

For upstream packages (especially important ones), they should usually
be merged in the beginning of a new release (on beta[n] with small n),
so that incompatibilities could be reported and fixed before the
official release.

In the current case, it should be the opposite, after downstream adapted
their code to our changes, so that those packages are not broken for the
official release.

Hence, there should be a way to update the versions of such packages
during beta[-1] (the one before rc0), at least those packages should be
tagged "downstream" somewhere (e.g.  whithin SPKG.rst file or whatever),
so that someone could have a look before the rc.

While our naming of development releases is pretty poor (beta or rc), we
should perhaps indicate somewhere which intervals are reserved for
backward-incompatible changes, and so on.

Another question: what happens if at the end of a Sage release cycle,
the downstream package is still broken ? Shall we remove the package
from build/pkgs ? Shall we add a temporary patch within the spkg
directory ? Or add a "broken" keyword for the "type" file ?

Ciao,
Thierry


  

On Wednesday, January 13, 2021 at 7:41:48 PM UTC-8 Matthias Koeppe wrote:


Meta-ticket https://trac.sagemath.org/ticket/31164 proposes to add user
packages, such as those listed at
https://wiki.sagemath.org/SageMathExternalPackages, to the Sage
distribution as "pip" packages. This has the following benefits:

- They will be automatically included in our reference manual and Sage
website (https://trac.sagemath.org/ticket/29655).
- We have GitHub Actions workflows in place
(tox-optional.yml, tox-experimental.yml), which will automatically try to
build the packages on each beta release. This provides continuous
integration that will allow us to catch unintended breaking changes during
the Sage development cycle.

Help is needed with this task.
- If a package listed at
https://wiki.sagemath.org/SageMathExternalPackages is outdated (does not
work with a current version of Sage), it will be helpful to add a note to
the wiki page and to notify the package authors.
- If a package seems to work with current Sage, help by creating a ticket
for the inclusion in Sage and list the ticket in meta-ticket
https://trac.sagemath.org/ticket/31164
- If a significant package is neither listed in build/pkgs/ nor in the
wiki page, please add 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/88ba0229-2e6f-4a04-a955-157248c5f90bn%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/b467c19d-ad98-2c57-4e56-a35d7bf5f7eb%40gmail.com.

Re: [sage-devel] Re: Help needed with adding user packages as optional/experimental packages

[Thierry]

Hi,

On Sun, Feb 07, 2021 at 04:49:23PM -0800, Matthias Koeppe wrote:
> The first few user packages have been added in 9.3.beta7:
> ore_algebra, sage_flatsurf, admcycles, slabbe, surface_dynamics.

We should notice that, contrary to other packages, those packages should
be considered as downstream (not upstream), and this should be reflected
in our release process.

Indeed, their code get adapted after Sage changes, see e.g. (randomly
chosen examples):

https://github.com/mkauers/ore_algebra/commit/2d71b50ebad81e62432482facfe3f78cc4961c4f
https://github.com/mkauers/ore_algebra/commit/8c678f9c70aee8df211c04211dd2f7e230a4770f

For upstream packages (especially important ones), they should usually
be merged in the beginning of a new release (on beta[n] with small n),
so that incompatibilities could be reported and fixed before the
official release.

In the current case, it should be the opposite, after downstream adapted
their code to our changes, so that those packages are not broken for the
official release.

Hence, there should be a way to update the versions of such packages
during beta[-1] (the one before rc0), at least those packages should be
tagged "downstream" somewhere (e.g.  whithin SPKG.rst file or whatever),
so that someone could have a look before the rc.

While our naming of development releases is pretty poor (beta or rc), we
should perhaps indicate somewhere which intervals are reserved for
backward-incompatible changes, and so on.

Another question: what happens if at the end of a Sage release cycle,
the downstream package is still broken ? Shall we remove the package
from build/pkgs ? Shall we add a temporary patch within the spkg
directory ? Or add a "broken" keyword for the "type" file ?

Ciao,
Thierry


 
> On Wednesday, January 13, 2021 at 7:41:48 PM UTC-8 Matthias Koeppe wrote:
> 
> > Meta-ticket https://trac.sagemath.org/ticket/31164 proposes to add user 
> > packages, such as those listed at  
> > https://wiki.sagemath.org/SageMathExternalPackages, to the Sage 
> > distribution as "pip" packages. This has the following benefits:
> >
> >- They will be automatically included in our reference manual and Sage 
> >website (https://trac.sagemath.org/ticket/29655).
> >- We have GitHub Actions workflows in place 
> >(tox-optional.yml, tox-experimental.yml), which will automatically try 
> > to 
> >build the packages on each beta release. This provides continuous 
> >integration that will allow us to catch unintended breaking changes 
> > during 
> >the Sage development cycle.
> >
> > Help is needed with this task. 
> > - If a package listed at 
> > https://wiki.sagemath.org/SageMathExternalPackages is outdated (does not 
> > work with a current version of Sage), it will be helpful to add a note to 
> > the wiki page and to notify the package authors.
> > - If a package seems to work with current Sage, help by creating a ticket 
> > for the inclusion in Sage and list the ticket in meta-ticket 
> > https://trac.sagemath.org/ticket/31164
> > - If a significant package is neither listed in build/pkgs/ nor in the 
> > wiki page, please add 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/88ba0229-2e6f-4a04-a955-157248c5f90bn%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/20210208120633.jwd5ylynvrabclid%40metelu.net.

Re: [sage-devel] Trouble building cython

[Dima Pasechnik]

This seems to be well-known issue, see e.g
https://github.com/pypa/virtualenv/issues/2027

Are you on the most recent develop branch (9.3.beta7)?

On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn  wrote:
>
> Hi,
>
> I'm trying to build Sage from the source code. I cloned it from git, and 
> tried to build from the develop branch using make from the sage directory. I 
> ran into trouble building cython. The error message suggested that I email 
> this group. Does anyone have any advice on how to proceed?
>
> I am using macOS Big Sur 11.2 on a MacBook Air.
>
> The log file is attached, this is from a second run - it failed once, and I 
> tried running make a second time without any changes and this is the log from 
> the second run, which returns the same error just without all of the info 
> before it (eg. the flint installation).
>
> Thanks so much.
>
> Best,
> Trevor
>
> --
> 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/1c93ec2e-86bd-45f0-bba0-cc254a392305n%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/CAAWYfq3CFFAYzUtNnSrt_RPKW7X_p8j_VXGtZbKLWG%2BST%3DCO%2BQ%40mail.gmail.com.

Re: [sage-devel] possible bug: kernel of ring homomorphism

[Akos M]

It seems that unfortunately the problem persists for multivariate rings as 
well:

A. = QQ[]
B. = QQ[]
H = B.quotient(B.ideal([B.2]))
f = A.hom([H.0, H.1], H)
f
f.kernel()

Ring morphism: 
 From: Multivariate Polynomial Ring in t, u over Rational Field 
 To: Quotient of Multivariate Polynomial Ring in x, y, z over Rational 
Field by the ideal (z) 
 Defn: t |--> xbar 
   u |--> ybar 
Ideal (-t, -u, 0) of Multivariate Polynomial Ring in t, u over Rational 
Field

I have the impression that the fact that the ring homomorphism is to a 
quotient ring introduces the error, but that's just a wild guess. 
On Monday, February 8, 2021 at 11:09:52 AM UTC+1 dim...@gmail.com wrote:

> A wild guess would be that it's due to univariate and multivariate
> rings handled by different backends in Sage, one sees this kinds of
> corner cases errors.
>
> On Mon, Feb 8, 2021 at 10:06 AM John Cremona  wrote:
> >
> > It looks like a bug to me. f.kernel() expands to
> > f._inverse_image_ideal(f.codomain().zero_ideal()) and
> > f.codomain().zero_ideal() looks OK so the problem must be in the
> > inverse image. The author is apparently Simon King (2011). Simon,
> > can you help?
> >
> > John
> >
> > On Mon, 8 Feb 2021 at 09:20, Akos M  wrote:
> > >
> > > Hi,
> > >
> > > I'm not sure whether this is a bug or not, but the kernel of a ring 
> homomorphism to a quotient ring gives unexpected results:
> > >
> > > A. = QQ[]
> > > B. = QQ[]
> > > H = B.quotient(B.ideal([B.1]))
> > > f = A.hom([H.0], H)
> > > f
> > > f.kernel()
> > >
> > > outputs:
> > >
> > > Ring morphism: From: Univariate Polynomial Ring in t over Rational 
> Field
> > > To: Quotient of Multivariate Polynomial Ring in x, y over Rational 
> Field by the ideal (y) Defn: t |--> xbar
> > > Principal ideal (t) of Univariate Polynomial Ring in t over Rational 
> Field
> > >
> > > whereas the kernel of f:A[t]->B[x,y]->B[x,y]/(y), for f(t)=x should be 
> (0).
> > >
> > > Is this a bug?
> > >
> > > Thanks,
> > > Akos
> > >
> > > --
> > > 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/3eeea5f7-4ea2-4586-bbb6-04d00c0d4fa9n%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 discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAD0p0K45OKUuLWegC6sXWHoTWs9ppPf7htmZ1wVyBo_O08%3DNTw%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/d4bb76c9-3002-47b2-9275-3977ce1912a8n%40googlegroups.com.

Re: [sage-devel] possible bug: kernel of ring homomorphism

[Dima Pasechnik]

A wild guess would be that it's due to univariate and multivariate
rings handled by different backends in Sage, one sees this kinds of
corner cases errors.

On Mon, Feb 8, 2021 at 10:06 AM John Cremona  wrote:
>
> It looks like a bug to me.   f.kernel() expands to
> f._inverse_image_ideal(f.codomain().zero_ideal()) and
> f.codomain().zero_ideal() looks OK so the problem must be in the
> inverse image.  The author is apparently Simon King (2011).  Simon,
> can you help?
>
> John
>
> On Mon, 8 Feb 2021 at 09:20, Akos M  wrote:
> >
> > Hi,
> >
> > I'm not sure whether this is a bug or not, but the kernel of a ring 
> > homomorphism to a quotient ring gives unexpected results:
> >
> > A. = QQ[]
> > B. = QQ[]
> > H = B.quotient(B.ideal([B.1]))
> > f = A.hom([H.0], H)
> > f
> > f.kernel()
> >
> > outputs:
> >
> > Ring morphism: From: Univariate Polynomial Ring in t over Rational Field
> > To: Quotient of Multivariate Polynomial Ring in x, y over Rational Field by 
> > the ideal (y) Defn: t |--> xbar
> > Principal ideal (t) of Univariate Polynomial Ring in t over Rational Field
> >
> > whereas the kernel of f:A[t]->B[x,y]->B[x,y]/(y), for f(t)=x should be (0).
> >
> > Is this a bug?
> >
> > Thanks,
> > Akos
> >
> > --
> > 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/3eeea5f7-4ea2-4586-bbb6-04d00c0d4fa9n%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/CAD0p0K45OKUuLWegC6sXWHoTWs9ppPf7htmZ1wVyBo_O08%3DNTw%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/CAAWYfq20%3DzALr7w3-On2KXfALj5zyzrcmB_Aug%3D5Lyk4g7Cagg%40mail.gmail.com.

Re: [sage-devel] possible bug: kernel of ring homomorphism

[John Cremona]

It looks like a bug to me.   f.kernel() expands to
f._inverse_image_ideal(f.codomain().zero_ideal()) and
f.codomain().zero_ideal() looks OK so the problem must be in the
inverse image.  The author is apparently Simon King (2011).  Simon,
can you help?

John

On Mon, 8 Feb 2021 at 09:20, Akos M  wrote:
>
> Hi,
>
> I'm not sure whether this is a bug or not, but the kernel of a ring 
> homomorphism to a quotient ring gives unexpected results:
>
> A. = QQ[]
> B. = QQ[]
> H = B.quotient(B.ideal([B.1]))
> f = A.hom([H.0], H)
> f
> f.kernel()
>
> outputs:
>
> Ring morphism: From: Univariate Polynomial Ring in t over Rational Field
> To: Quotient of Multivariate Polynomial Ring in x, y over Rational Field by 
> the ideal (y) Defn: t |--> xbar
> Principal ideal (t) of Univariate Polynomial Ring in t over Rational Field
>
> whereas the kernel of f:A[t]->B[x,y]->B[x,y]/(y), for f(t)=x should be (0).
>
> Is this a bug?
>
> Thanks,
> Akos
>
> --
> 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/3eeea5f7-4ea2-4586-bbb6-04d00c0d4fa9n%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/CAD0p0K45OKUuLWegC6sXWHoTWs9ppPf7htmZ1wVyBo_O08%3DNTw%40mail.gmail.com.

[sage-devel] possible bug: kernel of ring homomorphism

[Akos M]

Hi, 

I'm not sure whether this is a bug or not, but the kernel of a ring 
homomorphism to a quotient ring gives unexpected results:

A. = QQ[] 
B. = QQ[] 
H = B.quotient(B.ideal([B.1])) 
f = A.hom([H.0], H) 
f 
f.kernel()

outputs:
Ring morphism: From: Univariate Polynomial Ring in t over Rational Field 
To: Quotient of Multivariate Polynomial Ring in x, y over Rational Field by 
the ideal (y) Defn: t |--> xbar 
Principal ideal (t) of Univariate Polynomial Ring in t over Rational Field

whereas the kernel of f:A[t]->B[x,y]->B[x,y]/(y), for f(t)=x should be (0).

Is this a bug?
Thanks,
Akos

-- 
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/3eeea5f7-4ea2-4586-bbb6-04d00c0d4fa9n%40googlegroups.com.

Re: [sage-devel] Re: sorting output dicts in doctests

[John Cremona]

#3 is now under review, so if any one thinks that the tests I put
in there need changing they can say so on trac.

John

On Sun, 7 Feb 2021 at 23:18, 'Travis Scrimshaw' via sage-devel
 wrote:
>
> Hi John,
>>
>>
>> Travis, this relates to ticket #3 which I should be uploading code for 
>> today, so there is nothing to see there yet.  The output to one function 
>> will be a pair, True/False and a dict, so this fits with what you said.  
>> What I will do is assign the two parts to variables and display each 
>> separately.  I prefer that to the second suggestion, though that would 
>> certainly work too.
>
>
> In this case, it might also be good to instead (or also) verify the 
> certificate through tests. That way to get to further illustrate your code 
> and it is a less brittle doctest.
>
> Best,
> Travis
>
>>
>> John
>>
>> On Thursday, February 4, 2021 at 11:49:49 PM UTC hel...@potuz.net wrote:
>>>
>>> In addition to that I've been using the idiom
>>>
>>> MyOutput == {this : dict}
>>> True
>>>
>>> And that works for tests and renders well on documents
>>>
>>> R
>>>
>>>
>>> On February 4, 2021 8:34:36 PM GMT-03:00, 'Travis Scrimshaw' via sage-devel 
>>>  wrote:

 Hi John,
 IIRC, a dict has its keys automatically sorted in the output. However, 
 if the dict is inside of another object, then no sorting is done. So if it 
 is a simple dict with a total ordering on the keys, then you can simply 
 put the output. You can also run sorted() on the items if they dicts are 
 inside of other objects. Otherwise you might be better off testing the 
 individual aspects you want, such as specific values are correct. Could 
 you point to which ticket and/or test you want?

 Best,
 Travis


 On Friday, February 5, 2021 at 3:06:52 AM UTC+10 john.c...@gmail.com wrote:
>
> Can someone remind me the preferred way to get doctests to pass when
> the output -- which we do want to include in the docstring -- includes
> a dict whose keys come out in random order?
>
> John
>>>
>>>
>>> --
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> --
> 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/f27b35cf-66f7-48d9-a9bc-e1fd486556afn%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/CAD0p0K5RK9EridY1-%2BU3bLZ7qczZ%3DXNhQnt6zT3rjZGQSaa3Og%40mail.gmail.com.