Two more tickets:
https://trac.sagemath.org/ticket/28686: change a bunch of packages from
optional to experimental, delete a few pip packages (as Samuel suggested).
I didn't delete all of the pip packages, just the ones that are not
compatible with Python 3.
Note that "sage --sws2rst ..." relies on sagenb, and therefore will only
work with Sage built with Python 2.
In any case, https://trac.sagemath.org/ticket/28685 upgrades to
beautifulsoup4, which is compatible with Python 3.
On Friday, November 1, 2019 at 3:43:32 AM UTC-7, kcrisman wrote:
>
>
Hi,
Le lundi 28 octobre 2019 23:02:23 UTC+1, John H Palmieri a écrit :
>
>
>
> *Experimental:*
>
> - the following failed to build:
>
> autotools
> cocoalib
> libtheora
> polymake
> qepcad
> scipoptsuite
> surf
> valgrind
>
> - the following succeeded:
>
> gap3
> lie
> modular_decomposition
>
On Friday, November 1, 2019 at 12:22:01 AM UTC-4, Samuel Lelievre wrote:
>
> Le jeu. 31 oct. 2019 à 08:09, kcrisman:
> >
> > On Wednesday, October 30, 2019 at 1:47:48 AM UTC-4, Samuel Lelievre
> wrote:
> >>
> >> We should keep the ability to export sagenb ".sws" worksheets
> >> to rst and
On Thursday, October 31, 2019 at 8:16:55 AM UTC-4, Dima Pasechnik wrote:
>
> I think the Sage tutorial mentioning beautifulsoup actually says to
> install it as
>
> sage --pip install beatifulsoup4
>
> which would install the package from the net rather than Sage's one
>
>>
>>
Great, perhaps
Le jeu. 31 oct. 2019 à 08:09, kcrisman:
>
> On Wednesday, October 30, 2019 at 1:47:48 AM UTC-4, Samuel Lelievre wrote:
>>
>> We should keep the ability to export sagenb ".sws" worksheets
>> to rst and to ipynb for a long time. There are many, really many
>> people still using SageNB, and many,
I think the Sage tutorial mentioning beautifulsoup actually says to install
it as
sage --pip install beatifulsoup4
which would install the package from the net rather than Sage's one
On Thu, 31 Oct 2019, 14:09 kcrisman, wrote:
>
>
> On Wednesday, October 30, 2019 at 1:47:48 AM UTC-4, Samuel
On Wednesday, October 30, 2019 at 1:47:48 AM UTC-4, Samuel Lelievre wrote:
>
> Tue 2019-10-29 11:57 UTC, kcrisman:
> >
> >> Perhaps should we simply remove the pseudo-packages whose type is "pip"
> >> (since there is the "sage -pip install" command), that is:
> >>
> >> beautifulsoup
> >>
Tue 2019-10-29 11:57 UTC, kcrisman:
>
>> Perhaps should we simply remove the pseudo-packages whose type is "pip"
>> (since there is the "sage -pip install" command), that is:
>>
>> beautifulsoup
>> biopython
>> brian
>> guppy
>> mercurial
>> mpi4py
>> nibabel
>> pybtex
>> pyflakes
>> sqlalchemy
>>
> >
> > Sage-wise, I believe Mercurial is a remnant of the time
> > before we switched to Git. I think we should remove it.
>
>
I'm surprised it hadn't been long before. Even I would approve that.
>
> Perhaps should we simply remove the pseudo-packages whose type is "pip"
> (since there
Hi,
On Mon, Oct 28, 2019 at 04:37:53PM -0700, Samuel Lelievre wrote:
[...]
> >
> > - the following packages failed because they (or their installation
> > scripts) are not compatible with Python 3:
> >
> > beautifulsoup
> >
>
> I think we should either remove BeautifulSoup
> or replace it by
Mon 2019-10-28 22:02:23 UTC, John H Palmieri:
>
> With a Python 3 build of Sage on OS X 10.14.6, I decided to install
>
as many optional and experimental packages as I could. The results:
>
Thanks John for trying this and reporting!
> *Optional:*
>
> - the following packages failed to build,
Oops, I spoke too soon. Two more files had failures:
- sage -t --long src/sage/databases/stein_watkins.py # 20 doctests failed
- sage -t --long src/sage/interfaces/frobby.py # 12 doctests failed
On Monday, October 28, 2019 at 3:02:23 PM UTC-7, John H Palmieri wrote:
>
> With a Python 3 build
13 matches
Mail list logo
