On Tue, Feb 06, 2018 at 05:09:11PM -0800, Dima Pasechnik wrote:
[...]
> They don't really report things, apart from occasional posts on
> sage-packaging,
> you have to ask there if you need to know details.
Thanks for the pointer. On their patch [1], it is written:
"Forwarded: TODO, maybe
On Tuesday, February 6, 2018 at 9:23:14 PM UTC, Thierry
(sage-googlesucks@xxx) wrote:
>
> On Tue, Feb 06, 2018 at 08:37:20PM +0100, Thierry wrote:
> [...]
> > If on the other way, i try to let Sage use system's R by:
> > - replacing r spkg-install by "true"
> > - exporting RHOMES=/usr/li
But implementation details can surely be worked out. A totally basic idea:
put the specifics of the integer type and integer wrap/unwrapping in an
cython include file. At build time, copy the include file with the desired
implementation.
--
You received this message because you are subscribed
Hi Eran,
Sage's Trac has a wiki page about building SageMath in 64-bit Cygwin:
https://trac.sagemath.org/wiki/Cygwin64Port
(maybe you knew that already).
Another way to go about building SageMath under Windows 10
is to activate the "Windows Subsystem for Linux" (you need to
go to advanced p
On Wed, Feb 07, 2018 at 10:32:27AM +1300, François Bissey wrote:
> > On 7/02/2018, at 10:23, Thierry wrote:
[...]
> > I diffed with Debian's file, and apparently they added a '--no-readline'
> > option to the call to R in $SAGE_ROOT/src/sage/interfaces/r.py and it
> > seems to fix the issue, i ha
> On 7/02/2018, at 10:23, Thierry wrote:
>
> On Tue, Feb 06, 2018 at 08:37:20PM +0100, Thierry wrote:
> [...]
>> If on the other way, i try to let Sage use system's R by:
>> - replacing r spkg-install by "true"
>> - exporting RHOMES=/usr/lib/R/ in rpy2 spkg-install (instead of
>>$SAGE_LOC
On Tue, Feb 06, 2018 at 08:37:20PM +0100, Thierry wrote:
[...]
> If on the other way, i try to let Sage use system's R by:
> - replacing r spkg-install by "true"
> - exporting RHOMES=/usr/lib/R/ in rpy2 spkg-install (instead of
> $SAGE_LOCAL/lib/R)
>
> Then from the Sage command line, i go
On Wed, Feb 07, 2018 at 09:05:01AM +1300, François Bissey wrote:
> That definitely a bug that should be fixed. I imagine that could mess
> installation
> of packages from CRAN and other.
This is now https://trac.sagemath.org/ticket/24675
Note that for the other way (the expect interface that fre
That definitely a bug that should be fixed. I imagine that could mess
installation
of packages from CRAN and other.
François
> On 7/02/2018, at 08:37, Thierry wrote:
>
> If i want to let rstudio use Sage's R, i get some errors since it seems
> that some paths are incorrect in our install. For
Hi,
since various people requested it, Sage Debian Live [1] tries to ship
other interfaces to R (Rcmdr, JGR, rstudio).
I do not want to have 2 different installs of R on the live since it might
cause confusion (e.g. if they install a package, it will only be available
in one install, not the othe
On Tuesday, February 6, 2018 at 5:18:02 PM UTC, Avinandan Das wrote:
>
> Consider the following :-
>
> a=[[0, 4, 8], [9, 0, 9], [1000, 1000, 0]]
> a=Matrix(a)
> H=DiGraph(a,weighted=True)
> H.hamiltonian_path(used_edge_labels=True)
>
> This returns (1009, Subgraph of (): Digraph on 3 vertices)
On 2018-02-05 22:47, Volker Braun wrote:
A better implementation would be to make the integer implementation(s) a
build-time option; pplpy could internally use a fused type for all
available implementations.
I think that's a lot easier said than done. Also, a Python class cannot
really contain
Consider the following :-
a=[[0, 4, 8], [9, 0, 9], [1000, 1000, 0]]
a=Matrix(a)
H=DiGraph(a,weighted=True)
H.hamiltonian_path(used_edge_labels=True)
This returns (1009, Subgraph of (): Digraph on 3 vertices) but the minimum
weight Hamiltonian path has weight 13.
I have installed sage-8.1 and
the error is certainly here:
building 'crypt' extension
...
gcc -shared -Wl,--enable-auto-image-base -L. -L/home/Erana/sage/local/lib
-Wl,-rpath,/home/Erana/sage/local/lib -L. -L/home/Erana/sage/local/lib
-Wl,-rpath,/home/Erana/sage/local/lib
build/temp.cygwin-2.10.0-x86_64-2.7/home/Erana/sage/
Hi,
a doctest in line 1051 of parent.pyx indirectly can influence the doctest
in line 1514 which checks the coercion cache. While I could change the
latter doctest, is there either 1) a way to completely erase that cache, or
2) a way to restart Sage doctesting within one file to get a fresh inst
On Tuesday, February 6, 2018 at 2:25:58 PM UTC+1, Erik Bray wrote:
>
> "What's in it for Sage users?" -- Eventually, anyways, being able to
> drop code from Sage in favor of other, better-supported code that
> provides the same thing, so that Sage developers can work on other
> things.
>
Well
On Mon, Feb 5, 2018 at 10:47 PM, Volker Braun wrote:
> On Monday, February 5, 2018 at 8:14:12 PM UTC+1, vdelecroix wrote:
>>
>> And without having gmpy2 it is hard to set pplpy a standalone
>> package.
>
>
>
> Obviously thats the only real argument here; The question is, whats in it
> for Sage use
17 matches
Mail list logo
