On 2014-08-05 02:04, kcrisman wrote:
Or is gcc and friends required for using sage -i?
With a few exceptions (like pure database or pure Python packages), yes.
Usually installing packages requires some code to be compiled.
--
You received this message because you are subscribed to the Google G
>
> Does anybody actually doctest code in the Sage library that uses
> optional packages? I wrote the "#optional" tags so that this would be
> possible, but never really kept up with it.
>
>
Yes, though not as often as one might like. There are plenty of tickets
where (eventually) bugs have
IMHO we should try to switch to hashdist for Sage-7.0. This would solve our
dependency problems...
On Monday, August 4, 2014 5:08:38 PM UTC+1, wstein wrote:
>
> Would switching to that package manager that you recently rewrote help
> here?
>
--
You received this message because you are subscr
On 2014-08-04 18:07, William A Stein wrote:
Probably somebody should disable the install_package command in Sage,
and remove explicit reference to it in sage source code, if there is
no plan to fix it.
The plan to fix it is now
http://trac.sagemath.org/ticket/16759
--
You received this message
On 2014-08-04 18:07, William A Stein wrote:
I'm going to give up on changing sage for this particular issue, and
just put "sage -b" in my own script for installing optional packages
to SMC.
I think it's even safer to use "make" instead, which not only runs "sage
-b" but also rebuilds the documen
On Mon, Aug 4, 2014 at 8:35 AM, Volker Braun wrote:
> (5) have any dependency handling for optional packages.
Would switching to that package manager that you recently rewrote help here?
>
> Really, this thread boils down to: the Sage library depends on some optional
> packages. Any kind of hack
(5) have any dependency handling for optional packages.
Really, this thread boils down to: the Sage library depends on some
optional packages. Any kind of hacks around that (like running "sage -b" by
hand in scripts) will just lead to race conditions.
On Monday, August 4, 2014 2:58:02 PM UTC+
On Mon, Aug 4, 2014 at 8:14 AM, Jeroen Demeyer wrote:
> On 2014-08-04 16:35, Burcin Erocal wrote:
>>
>> There is one more option:
>>
>> (4) include the relevant python/cython code in the package, build
>> and install it with the package.
I like (4) the best, but it requires a significant cha
On 2014-08-04 16:35, Burcin Erocal wrote:
There is one more option:
(4) include the relevant python/cython code in the package, build
and install it with the package.
That's a possibility, although it complicates doctesting: that extra
code wouldn't get doctested.
--
You received this me
On 2014-08-04 15:57, William A Stein wrote:
(2) Tell people they have to run "sage -b" clearly in the package
install message. This won't work, because after 20 pages of build
output, nobody is likely to read this.
How about mentioning this after the build finished? Would that be more
like
On Mon, 4 Aug 2014 06:57:20 -0700
William A Stein wrote:
> This is absolutely not how Sage should behave. The fixes I can
> think of:
>
> (1) Run "sage -b" as part of installing any package that requires it
> for the install to finish. Your argument not to run "sage -b" isn't
> convincing,
On Mon, Aug 4, 2014 at 6:30 AM, Jeroen Demeyer wrote:
> On 2014-08-04 15:17, William A Stein wrote:
>>
>> Hi,
>>
>> I installed Sage-6.3.beta6 on SageMathCloud, then installed a big list
>> of optional packages, including cryptominisat.I was surprised when
>> the next day a user reported that
On 2014-08-04 15:17, William A Stein wrote:
Hi,
I installed Sage-6.3.beta6 on SageMathCloud, then installed a big list
of optional packages, including cryptominisat.I was surprised when
the next day a user reported that CryptoMiniSat didn't work, and when
you attempt to use it, you see
Hi,
I installed Sage-6.3.beta6 on SageMathCloud, then installed a big list
of optional packages, including cryptominisat.I was surprised when
the next day a user reported that CryptoMiniSat didn't work, and when
you attempt to use it, you see
Run "install_package('cryptominisat')" t
14 matches
Mail list logo
