Hi!
This is awesome! thanks so much! That seemed to be the problem! It's fixed
now! Thanks!!
J.
On Fri, Aug 19, 2016 at 8:45 AM, leif wrote:
> Jeroen Demeyer wrote:
> > On 2016-08-19 04:16, James Khan wrote:
> >> Hi!
> >>
> >> Many thanks for your message and kind help.
> >>
> >> I am runnin
Jeroen Demeyer wrote:
> On 2016-08-19 04:16, James Khan wrote:
>> Hi!
>>
>> Many thanks for your message and kind help.
>>
>> I am running virtual machine on windows 7 and the sage 7.3 link is not
>> ready yet (the source code is there but not the sage-7.3.ova) so I am
>> stuck with 7.2 for the tim
On 2016-08-19 04:16, James Khan wrote:
Hi!
Many thanks for your message and kind help.
I am running virtual machine on windows 7 and the sage 7.3 link is not
ready yet (the source code is there but not the sage-7.3.ova) so I am
stuck with 7.2 for the time being :(
I have indeed tried ./sage -i
Hi!
Many thanks for your message and kind help.
I am running virtual machine on windows 7 and the sage 7.3 link is not
ready yet (the source code is there but not the sage-7.3.ova) so I am stuck
with 7.2 for the time being :(
I have indeed tried ./sage -i TOPCOM versus "-i topcom" and then also h
James Khan wrote:
> Hi!
>
> Thanks a lot for getting back promptly! Sorry it's an old post; I was
> just getting desperate and was googling. :) Would you think updating to
> SAGE 7.3 would help?
I guess it will, at least give better error messages... ;-)
> I don't why TOPCOM is not loading. I
Hi!
Thanks a lot for getting back promptly! Sorry it's an old post; I was just
getting desperate and was googling. :) Would you think updating to SAGE 7.3
would help?
I don't why TOPCOM is not loading. I am running a windows version, maybe
that's a problem?
thanks!!
On Thu, Aug 18, 2016 at 12:5
James Khan wrote:
> Hi!
>
> Thanks for pointing this out. I am having the same problems!
>
> I have the most recent version of SAGE (7.2)
FWIW, the most recent version is Sage 7.3, released a couple of days ago.
There have been changes also to the topcom package IIRC, although the
error you get
Hi!
Thanks for pointing this out. I am having the same problems!
I have the most recent version of SAGE (7.2)
and I have tried all the combinations suggested in this thread: TOPCOM,
topcom, download the bz2 and plaving in /upstream/ but still no luck. I
wonder why this is the case.
I get the
Great, it works!
Thanks a lot for the help.
Best,
Oskar
On Wednesday, April 30, 2014 3:24:34 PM UTC+2, Volker Braun wrote:
>
> Lower case. Open a terminal and run "sage -i topcom" (or
> "/Applications/sage/sage -i topcom" if it isn't in the search path).
>
>
>
>
> On Wednesday, April 30, 2
Lower case. Open a terminal and run "sage -i topcom" (or
"/Applications/sage/sage -i topcom" if it isn't in the search path).
On Wednesday, April 30, 2014 2:12:34 PM UTC+1, Oskar Till wrote:
>
> Hi Guys,
>
> thanks for the support. However, I don't know where I'm supposed to type
> 'sage -i
Hi Guys,
thanks for the support. However, I don't know where I'm supposed to type
'sage -i topcom' ? is this the same as "sage: -i topcom", or the command
"sage: install_package('TOPCOM') " ?
I have the latest version installed, i.e 6.1.1 for mac OS.
When I type sage: install_package('TOPCOM'
John H Palmieri wrote:
On Tuesday, April 29, 2014 6:20:25 PM UTC-7, John H Palmieri wrote:
On Tuesday, April 29, 2014 4:45:35 PM UTC-7, leif wrote:
leif wrote:
> Volker Braun wrote:
>> there is no separate spkg in sage >= 6, its is an optional
pkg but lives
On Tuesday, April 29, 2014 6:20:25 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, April 29, 2014 4:45:35 PM UTC-7, leif wrote:
>>
>> leif wrote:
>> > Volker Braun wrote:
>> >> there is no separate spkg in sage >= 6, its is an optional pkg but
>> lives
>> >> in the git tree.
>> >
>> >
On Tuesday, April 29, 2014 4:45:35 PM UTC-7, leif wrote:
>
> leif wrote:
> > Volker Braun wrote:
> >> there is no separate spkg in sage >= 6, its is an optional pkg but
> lives
> >> in the git tree.
> >
> > But the first error seems to be that $SAGE_ROOT/upstream/ doesn't exist
> > (becaus
leif wrote:
Volker Braun wrote:
there is no separate spkg in sage >= 6, its is an optional pkg but lives
in the git tree.
But the first error seems to be that $SAGE_ROOT/upstream/ doesn't exist
(because it's a binary distribution of Sage I guess), and after that
error, sage-spkg downloads the
Volker Braun wrote:
there is no separate spkg in sage >= 6, its is an optional pkg but lives
in the git tree.
But the first error seems to be that $SAGE_ROOT/upstream/ doesn't exist
(because it's a binary distribution of Sage I guess), and after that
error, sage-spkg downloads the legacy TOPC
there is no separate spkg in sage >= 6, its is an optional pkg but lives in
the git tree.
On Tuesday, April 29, 2014 7:52:58 PM UTC+1, kcrisman wrote:
>
>
>
> On Tuesday, April 29, 2014 2:36:45 PM UTC-4, Volker Braun wrote:
>>
>> It seems that whichever version you have is too old for the topcom
On Tuesday, April 29, 2014 2:36:45 PM UTC-4, Volker Braun wrote:
>
> It seems that whichever version you have is too old for the topcom
> package. You probably need sage >= version 6.
>
>
Or is it the other way around? If the spkg-install file refers to
sage/spkg/standard, then presumably TOPC
It seems that whichever version you have is too old for the topcom package.
You probably need sage >= version 6.
On Tuesday, April 29, 2014 2:24:08 PM UTC+1, Oskar Till wrote:
>
> WARNING: spkg-install is not executable, making it executable
> ./spkg-install: line 11: cd: /Applications/sage/spkg
19 matches
Mail list logo
