On Sunday, January 24, 2021 at 3:02:02 AM UTC-8 Dima Pasechnik wrote:
> $ ./sage --package fix-checksum
> ERROR [package|all:249]: Failed to open pyopenssl
>
[...]
> File
> "/home/scratch2/dimpase/sage/sage/build/bin/../sage_bootstrap/tarball.py",
> line 102, in upstream_fqn
> return os.pat
On Saturday, September 27, 2014 10:36:14 PM UTC+2, kcrisman wrote:
>
> If I recall correctly sometimes one needs to use dash instead of bash on
> Cygwin, but nonetheless it somehow works, maybe because dash is only
> necessary when going "outside" of Sage for rebasing or something?
>
Yes, (appr
If I recall correctly sometimes one needs to use dash instead of bash on
Cygwin, but nonetheless it somehow works, maybe because dash is only
necessary when going "outside" of Sage for rebasing or something?
>
> To be precise, /bin/bash is a genuine bash on Debian, /bin/sh
> points to /bin/d
Hi,
On Fri, Sep 26, 2014 at 02:47:21PM +, Dima Pasechnik wrote:
> Sage scripts have "!/usr/bin/env bash" all over the place.
> I don't know about 'bashisms' though - one should test on a Debian system,
> where bash is not essential, as they have a push to move to dash years already
> on.
> (a
On 2014-09-26, Jean-Pierre Flori wrote:
>>
>
>> > 2. Dima -- do we specifically use bash features in the build scripts of
>> > Sage?
>>
>> Sage scripts have "!/usr/bin/env bash" all over the place.
>> I don't know about 'bashisms' though - one should test on a Debian system,
>> where bash is
>
> > 2. Dima -- do we specifically use bash features in the build scripts of
> > Sage?
>
> Sage scripts have "!/usr/bin/env bash" all over the place.
> I don't know about 'bashisms' though - one should test on a Debian system,
> where bash is not essential, as they have a push to move to das
On 2014-09-26, William A Stein wrote:
> On Fri, Sep 26, 2014 at 7:06 AM, John Cremona > wrote:
>> On 26 September 2014 14:59, Dima Pasechnik > wrote:
>>> From the noises I hear, in particular on our departamental email,
> sysadmins might be tempted to "rm -f /bin/bash"
>>> from any place they can
On 2014-09-26, Ivan Andrus wrote:
> On Sep 26, 2014, at 7:59 AM, Dima Pasechnik wrote:
>
>> From the noises I hear, in particular on our departamental email, sysadmins
>> might be tempted to "rm -f /bin/bash"
>> from any place they can get their hands on.
>>
>> It might mean that for building/w
On Feb 22, 12:18 pm, Bernie wrote:
Hi Bernie,
> Hi! If not so much problem can anybody tell me how to fix this
> problems? I'm trying to add some structures as Vincent did, but all my
> problems are still here after some hours of work :-(
> I did something similar to Vincent, adding my ne
Hi! If not so much problem can anybody tell me how to fix this
problems? I'm trying to add some structures as Vincent did, but all my
problems are still here after some hours of work :-(
I did something similar to Vincent, adding my new package to
$SAGE_ROOT/devel/sage/sage, and modify the all
On 13 jan, 22:43, mabshoff wrote:
> A couple remarks:
>
> * spkgs usually install software into $SAGE_ROOT/local or in local/
> lib/python/site-packages (via standard distutils mechanism, i.e.
> "python setup.py install") and not into the Sage library and I would
> highly discourage anyone to
A couple remarks:
* spkgs usually install software into $SAGE_ROOT/local or in local/
lib/python/site-packages (via standard distutils mechanism, i.e.
"python setup.py install") and not into the Sage library and I would
highly discourage anyone to attempt to install into the Sage library
itself
Vincent Delecroix wrote:
>
>
> Jason was right : "I have some python code that creates some objects
> that are interesting to me; how do I get this into Sage
> permanently ?". I've aldready put my files in the $SAGE_ROOT/devel/
> sage/sage directory and I've done two modifications of the
> conf
On Jan 13, 2009, at 12:54 PM, Vincent Delecroix wrote:
>
> Jason was right : "I have some python code that creates some objects
> that are interesting to me; how do I get this into Sage
> permanently ?". I've aldready put my files in the $SAGE_ROOT/devel/
> sage/sage directory and I've done two mo
On 13 jan, 20:27, Jason Grout wrote:
> Simon King wrote:
> > Dear Vincent,
>
> > On Jan 13, 6:38 pm, Vincent Delecroix <20100.delecr...@gmail.com>
> > wrote:
> >> I need objects in Sage that not yet totally exist (a combinatoric one,
> >> and another derived from oriented graph). So I write som
Simon King wrote:
> Dear Vincent,
>
> On Jan 13, 6:38 pm, Vincent Delecroix <20100.delecr...@gmail.com>
> wrote:
>> I need objects in Sage that not yet totally exist (a combinatoric one,
>> and another derived from oriented graph). So I write some python files
>> (pure python for the moment) to c
Dear Vincent,
On Jan 13, 6:38 pm, Vincent Delecroix <20100.delecr...@gmail.com>
wrote:
> I need objects in Sage that not yet totally exist (a combinatoric one,
> and another derived from oriented graph). So I write some python files
> (pure python for the moment) to create those new objects. My p
On Jan 13, 2009, at 9:38 AM, Vincent Delecroix wrote:
> Hi sage-developers,
>
> I need objects in Sage that not yet totally exist (a combinatoric one,
> and another derived from oriented graph). So I write some python files
> (pure python for the moment) to create those new objects. My problem
>
On 13 jan, 18:46, "David Joyner" wrote:
> On Tue, Jan 13, 2009 at 12:38 PM, Vincent Delecroix
>
> <20100.delecr...@gmail.com> wrote:
>
> > Hi sage-developers,
>
> > I need objects in Sage that not yet totally exist (a combinatoric one,
> > and another derived from oriented graph). So I write some
On Tue, Jan 13, 2009 at 12:38 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> Hi sage-developers,
>
> I need objects in Sage that not yet totally exist (a combinatoric one,
> and another derived from oriented graph). So I write some python files
> (pure python for the moment) to creat
An appropriate amount of time has passed and I consider this a
positive vote for the inclusion of GHMM into Sage.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [
On Jan 17, 11:57 pm, "Bill Page" <[EMAIL PROTECTED]> wrote:
> On 1/17/08, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
> > [I am not CCing the FriCAS google group since I am not subscribed]
>
> > On Jan 17, 10:44 pm, "Bill Page" <[EMAIL PROTECTED]> wrote:
> > ...
>
> > > In principle doing a new fric
On 1/17/08, mabshoff <[EMAIL PROTECTED]> wrote:
>
> [I am not CCing the FriCAS google group since I am not subscribed]
>
> On Jan 17, 10:44 pm, "Bill Page" <[EMAIL PROTECTED]> wrote:
> ...
> >
> > In principle doing a new fricas4sage release is fairly easy. First you
> > need to generate a cached
[I am not CCing the FriCAS google group since I am not subscribed]
On Jan 17, 10:44 pm, "Bill Page" <[EMAIL PROTECTED]> wrote:
> Martin,
Hi,
> You are right. The version of axiom4sage (fricas4sage) is a bit old
> and based on only the first experimental release of the Lisp caching
> scheme impl
24 matches
Mail list logo
