+1 to make threejs the default viewer.
--
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
Hi!
At #28414, I'm trying to upgrade my group cohomology package so that it
works both on sage-with-py2 and sage-with-py3.
On the laptop where I work on the new package version (I didn't publish
the code yet), I have a py2 and a py3 installation of Sage. To build the
package without the hassle of
Shouldn't coexisting installations like this have different --prefix ?
On Tue, 24 Sep 2019 15:29 Simon King, wrote:
> Hi!
>
> At #28414, I'm trying to upgrade my group cohomology package so that it
> works both on sage-with-py2 and sage-with-py3.
>
> On the laptop where I work on the new packag
Are you sure that the problem comes from the C files? If you erase
them between the two installations what do you get?
Le 24/09/2019 à 16:33, Dima Pasechnik a écrit :
Shouldn't coexisting installations like this have different --prefix ?
On Tue, 24 Sep 2019 15:29 Simon King, wrote:
Hi!
At
Hi Vincent,
On 2019-09-24, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> Are you sure that the problem comes from the C files? If you erase
> them between the two installations what do you get?
That's what I'm testing now.
BTW, meanwhile I found that I can prescribe in my setup.py where
Hi Dima,
On 2019-09-24, Dima Pasechnik wrote:
> Shouldn't coexisting installations like this have different --prefix ?
Of course. But if I understand correctly, this only affects where stuff
is installed, not where it is built. The situation is as follows:
- the .c files are created in the sour
I'm surprised that *.c files created by Cython for pyX may be used for
py(5-X) without many problems.
I'd expect this to break down totally...
Dima
On Tue, Sep 24, 2019 at 6:06 PM Simon King wrote:
>
> Hi Dima,
>
> On 2019-09-24, Dima Pasechnik wrote:
> > Shouldn't coexisting installations like
On Tuesday, September 24, 2019 at 10:12:17 AM UTC-7, Ben Salisbury wrote:
>
> Hi,
>
> I'm attempting to build Sage from the develop branch on a new office
> computer running OS X 10.14.6. I've installed Xcode and Command Line Tools
> (or at least I thought I had), and I'm getting a build failu
I'll try "./sage -f libpng". In the meantime, I've attached the log file
requested. Also:
mth153844pe212:~ salis1bt$ git --version
git version 2.20.1 (Apple Git-117)
mth153844pe212:~ salis1bt$ gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx
-include
by the way, there is
https://trac.sagemath.org/ticket/28513
where I proposed a fix for this sort of error -- least the error
message is much more clear...
On Tue, Sep 24, 2019 at 6:53 PM John H Palmieri wrote:
>
>
>
> On Tuesday, September 24, 2019 at 10:12:17 AM UTC-7, Ben Salisbury wrote:
>>
>>
Hi Dima,
On 2019-09-24, Dima Pasechnik wrote:
> I'm surprised that *.c files created by Cython for pyX may be used for
> py(5-X) without many problems.
> I'd expect this to break down totally...
Indeed. It is surprising that I only got two kinds of spurious errors:
In one place, a pickle of a di
On Tue, Sep 24, 2019 at 8:54 PM Ben Salisbury wrote:
>
> Trying "./sage -f libpng" first did not work. But there are new errors this
> time!
hmm, in the scipy log one sees
> ld: library not found for -lSystem
coming from gfortran, more precisely, from
/Users/salis1bt/sage-git/local/bin/
A new version of NTL is available. Details
here: https://www.shoup.net/ntl/doc/tour-changes.html
--
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+unsu
13 matches
Mail list logo