If you want to start porting dependencies to native windows, I'd suggest
getting all dependencies of sage ported to conda. I maintain a lot of sage
dependencies for conda-forge and would love to have more packages ported to
windows and then maybe some day build sage.
There are lots of packages
In case it matters, I have just uploaded Sagetex 3.2 to CTAN.
Not sure whether Debian does any synchronisation of Sagetex@CTAN with
Sagtex @ sage - hopefully it does not break anything for you.
On Thu, Jan 10, 2019 at 3:41 PM Jerome BENOIT wrote:
>
>
>
> On 10/01/2019 10:31, Dima Pasechnik
On Wednesday, January 23, 2019 at 9:58:19 AM UTC-8, E. Madison Bray wrote:
>
> On Wed, Jan 23, 2019 at 6:26 PM John H Palmieri > wrote:
> >
> >
> >
> > On Wednesday, January 23, 2019 at 9:11:17 AM UTC-8, John H Palmieri
> wrote:
> >>
> >>
> >>
> >> On Wednesday, January 23, 2019 at
I see, now. Thank you.
On Wednesday, January 23, 2019 at 2:32:18 PM UTC-5, Travis Scrimshaw wrote:
>
> Change element_class() to element_class.
>
> It is all in the error message (remember that self is always an argument).
>
> Best,
> Travis
>
>
--
You received this message because you are
Change element_class() to element_class.
It is all in the error message (remember that self is always an argument).
Best,
Travis
--
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,
On Wed, Jan 23, 2019 at 6:26 PM John H Palmieri wrote:
>
>
>
> On Wednesday, January 23, 2019 at 9:11:17 AM UTC-8, John H Palmieri wrote:
>>
>>
>>
>> On Wednesday, January 23, 2019 at 9:06:45 AM UTC-8, John H Palmieri wrote:
>>>
>>>
>>>
>>> On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John
On Wednesday, January 23, 2019 at 9:11:17 AM UTC-8, John H Palmieri wrote:
>
>
>
> On Wednesday, January 23, 2019 at 9:06:45 AM UTC-8, John H Palmieri wrote:
>>
>>
>>
>> On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John H Palmieri wrote:
>>>
>>>
>>>
>>> On Wednesday, January 23, 2019 at
On Wednesday, January 23, 2019 at 9:06:45 AM UTC-8, John H Palmieri wrote:
>
>
>
> On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John H Palmieri wrote:
>>
>>
>>
>> On Wednesday, January 23, 2019 at 3:59:41 AM UTC-8, E. Madison Bray wrote:
>>>
>>> On Tue, Jan 22, 2019 at 8:30 PM John H
On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John H Palmieri wrote:
>
>
>
> On Wednesday, January 23, 2019 at 3:59:41 AM UTC-8, E. Madison Bray wrote:
>>
>> On Tue, Jan 22, 2019 at 8:30 PM John H Palmieri
>> wrote:
>> >
>> > Here is the situation: I've been playing around with new
On Wednesday, January 23, 2019 at 3:59:41 AM UTC-8, E. Madison Bray wrote:
>
> On Tue, Jan 22, 2019 at 8:30 PM John H Palmieri > wrote:
> >
> > Here is the situation: I've been playing around with new versions of
> Sphinx. If I've installed a new version and then go back to an old version,
On Wed, Jan 23, 2019 at 3:36 AM E. Madison Bray wrote:
> > If I had to run Sage on Windows for some reason today, I would use
> > Docker or VirtualBox.I helped support somebody using the Cygwin
> > version of Sage on Windows at the Sage booth at the Joint Math
> > Meetings last week, and it
On Tue, Jan 22, 2019 at 10:32 PM Jeroen Demeyer wrote:
>
> On 2019-01-23 00:11, William Stein wrote:
> > I helped support somebody using the Cygwin
> > version of Sage on Windows at the Sage booth at the Joint Math
> > Meetings last week, and it typically took about 1 minute to start up
> > Sage,
> If I had to run Sage on Windows for some reason today,
> I would use Docker or VirtualBox.
I’ve been using Sage for many years mainly on Windows.
First with the Virtual box. This had many disadvantages. On
the one hand the VirtualBox was error-prone and often did not
work as expected. It
On Wednesday, January 23, 2019 at 12:12:39 AM UTC+1, William wrote:
>
> If I had to run Sage on Windows for some reason today, I would use
> Docker or VirtualBox.
I recently tried out the new Windows 10 Subsystem for LInux and its pretty
sleek. I built Sage for shits & giggles and everything
On Wed, Jan 23, 2019 at 1:41 PM nandini nandu
wrote:
>
> While running ./sage from my terminal, I got this error. Please help me. I am
> using Ubuntu 18.04. I succesfully installed LaTex, ImageMagick.
>
>
> Error: The path to the Sage directory ($SAGE_ROOT) MUST NOT contain spaces.
> It is
While running ./sage from my terminal, I got this error. Please help me. I
am using Ubuntu 18.04. I succesfully installed LaTex, ImageMagick.
Error: The path to the Sage directory ($SAGE_ROOT) MUST NOT contain spaces.
It is currently "/home/sanju/Program
On Tue, Jan 22, 2019 at 8:30 PM John H Palmieri wrote:
>
> Here is the situation: I've been playing around with new versions of Sphinx.
> If I've installed a new version and then go back to an old version, the
> directory local/lib/python2.7/site-libraries/sphinx/ is not removed and then
>
On Wed, Jan 23, 2019 at 7:32 AM Jeroen Demeyer wrote:
>
> On 2019-01-23 00:11, William Stein wrote:
> > I helped support somebody using the Cygwin
> > version of Sage on Windows at the Sage booth at the Joint Math
> > Meetings last week, and it typically took about 1 minute to start up
> > Sage,
On Wed, Jan 23, 2019 at 12:12 AM William Stein wrote:
>
> On Tue, Jan 22, 2019 at 2:34 PM deSitter wrote:
> >
> > Hello all,
> >
> > I am interested in creating a native Windows port completely independent of
> > the ugh-worthy Cygwin. Does such a project exist?
>
> Not anymore. I came the
On Tue, Jan 22, 2019 at 11:34 PM deSitter wrote:
>
> Hello all,
>
> I am interested in creating a native Windows port completely independent of
> the ugh-worthy Cygwin. Does such a project exist?
>
> TIA
>
> -drl
This is something I had planned to do from the start. It was never my
preference
20 matches
Mail list logo
