Re: [sage-release] Sage 7.6.beta2 released
Le samedi 4 février 2017 14:41:49 UTC+1, Volker Braun a écrit : > > On Saturday, February 4, 2017 at 11:55:00 AM UTC+1, Samuel Lelievre wrote: >> >> Should 'make ptestlong' ignore the content of 'init.sage'? >> > > Yes. > Note that there is a ticket for that: #20270 some doctests are influenced by the contents of init.sage https://trac.sagemath.org/ticket/20270 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Conda package for Sage
Le 05/02/2017 à 21:13, Samuel Lelievre a écrit : Sun 2017-02-05 13:27:02 UTC+1, Isuru Fernando: I've packaged sage 7.5.1 for conda for linux and have uploaded it to anaconda.org. To try it out you can do on linux with miniconda3, (Downloads about 1 GB) conda create -n sage sage sage-spkg-sources -c isuruf -c conda-forge This was a hacky build and I don't expect everything to work properly. sage command, sage notebook, gap, maxima and a few packages I've checked works. There were 86 standard packages in conda-forge and default channel. (conda-forge is a community effort, see https://conda-forge.github.io/). These conda packages were used instead of sage's packages 74 standard packages were built in the docker container condaforge/linux-anvil with SAGE_FAT_BINARY=yes, which should make the packages compatible with distros as old as CentOS 6. I used sage's build process to create these, kept track of which files were created and copied them over to a conda package. Things to note are, 1. anaconda.org r channel is incompatible with conda-forge. So rpy2 and r is not bundled, but conda-forge has started packaging the r packages. 2. only the SAGE_LOCAL folder is packaged. So no development. 3. sage-env is sourced when the env is activated, but the deactivation doesn't seem to work properly. Your shell session may become unusable. 4. pinning needs to happen so that ABI compatibility is there. 5. Packages are built with gmp. 6. miniconda2 has issues with path names having non-ASCII characters, so you have to use miniconda3 as your root environment. Anybody interested in making proper conda packages for the remaining 74 packages and sage itself? Isuru Fernando Hi Isuru Fernando, Thanks for this packaging and for reporting to sage-devel. I'm cc-ing sage-packaging and sage-release which are also appropriate place to announce this. I updated the "Distribution" wiki page at https://wiki.sagemath.org/Distribution Best, Samuel Note that there are Sage days on march 13-17 dedicated to packaging https://wiki.sagemath.org/days85 You might want to participate. Vincent -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Conda package for Sage
Sun 2017-02-05 13:27:02 UTC+1, Isuru Fernando: > I've packaged sage 7.5.1 for conda for linux and have uploaded it to anaconda.org. > > To try it out you can do on linux with miniconda3, (Downloads about 1 GB) > > conda create -n sage sage sage-spkg-sources -c isuruf -c conda-forge > > This was a hacky build and I don't expect everything to work properly. sage command, sage notebook, gap, maxima and a few packages I've checked works. > > There were 86 standard packages in conda-forge and default channel. (conda-forge is a community effort, see https://conda-forge.github.io/). These conda packages were used instead of sage's packages > > 74 standard packages were built in the docker container condaforge/linux-anvil with SAGE_FAT_BINARY=yes, which should make the packages compatible with distros as old as CentOS 6. I used sage's build process to create these, kept track of which files were created and copied them over to a conda package. > > Things to note are, > 1. anaconda.org r channel is incompatible with conda-forge. So rpy2 and r is not bundled, but conda-forge has started packaging the r packages. > 2. only the SAGE_LOCAL folder is packaged. So no development. > 3. sage-env is sourced when the env is activated, but the deactivation doesn't seem to work properly. Your shell session may become unusable. > 4. pinning needs to happen so that ABI compatibility is there. > 5. Packages are built with gmp. > 6. miniconda2 has issues with path names having non-ASCII characters, so you have to use miniconda3 as your root environment. > > Anybody interested in making proper conda packages for the remaining 74 packages and sage itself? > > Isuru Fernando Hi Isuru Fernando, Thanks for this packaging and for reporting to sage-devel. I'm cc-ing sage-packaging and sage-release which are also appropriate place to announce this. I updated the "Distribution" wiki page at https://wiki.sagemath.org/Distribution Best, Samuel -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
