Re: [sage-devel] Native Windows version

2019-01-22 Thread Jeroen Demeyer

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, which was scary.


But mathematical computations (which do not involve syscalls) shouldn't 
be slower, right?


--
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Native Windows version

2019-01-22 Thread Dima Pasechnik
On Tue, Jan 22, 2019 at 10: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?

there are parts of Sage that are really stumbling blocks for such a project,
GAP one of them.
You might start with GAP - I'd expect that it might be quite an effort, though.


>
> TIA
>
> -drl
>
> --
> 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, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Native Windows version

2019-01-22 Thread William Stein
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 closest to writing one, but still didn't
really get close (this was a long time ago -- back when Microsoft way
paying REvolution to port R to Windows).  It's very difficult, because
numerous Sage dependencies have never been properly ported to Windows.
  If I were to try today, I would start by trying to refactor Sage
itself into a sage-core, with minimal dependencies, and other
libraries that depend on sage-core.  Once that is done [1], then I
would worry about porting only sage-core to Windows, as a standard
Python library that is Anaconda installable (I would leverage Anaconda
as much as possible [2]).   With that done, I would turn to whatever
major modules (e.g., sage-combinat, sage-nt, sage-algebra, etc.) are
of most interest, and try to port them one-by-one to Windows.  Some
would not be possible due to dependencies, and others would be easy.
  In any case, I never succeeded at a proper port, nor did anybody
else, so don't take my advise regarding Windows too seriously.

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 typically took about 1 minute to start up
Sage, which was scary.  She also was 100% convinced that copy/paste in
the Sage terminal (really cygwin) didn't work, which would make using
Sage very painful indeed.   It turned out that copy/paste does work if
you use the context menu.

 -- William

[1] I realize that maybe Sage is such a complicated Python library at
this point (million lines of code), with so many outstanding "needs
review" tickets on trac (always over 200!) that such a refactor would
be brutally difficult for any single human being, and very invasive to
Sage development.  It's probably totally unrealistic.

[2] When I was trying hard to do the Windows port of Sage in 2007 (?),
I was very, very frustrated because the Anaconda (or whatever it was
called) was all a closed source product of Enthought, and we couldn't
use it for our Sage port.   I pointed this out during my invited Scipy
talk, and it made the people who invited me pretty angry at me.  In
any case, Anaconda has since been very generously made open source.  I
would make step 0 of porting sage to windows be to fully understand
and appreciate what Anaconda on Windows is currently, and very likely
build on that.  The build system for something complicated like Sage
on windows is really important, and the current Sage build system
doesn't make sense to use natively with Windows.

>
> TIA
>
> -drl
>
> --
> 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, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William (http://wstein.org)

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Native Windows version

2019-01-22 Thread deSitter
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

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Re: Wrong solution/output for differential equation

2019-01-22 Thread Thrash
Thanks, I've just created this one here:
https://sourceforge.net/p/maxima/bugs/3522/

Am Dienstag, 22. Januar 2019 22:19:49 UTC+1 schrieb Eric Gourgoulhon:
>
> Le mardi 22 janvier 2019 20:55:11 UTC+1, Thrash a écrit :
>>
>> Can someone please report it upstream? Or tell me how to do it?
>>
>>
> You should report it here:
> https://sourceforge.net/p/maxima/bugs/
>
> Here is a recent example of bug report arising from a SageMath user:
> https://sourceforge.net/p/maxima/bugs/3521/
>
> Best wishes,
>
> Eric.
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Re: Wrong solution/output for differential equation

2019-01-22 Thread Eric Gourgoulhon
Le mardi 22 janvier 2019 20:55:11 UTC+1, Thrash a écrit :
>
> Can someone please report it upstream? Or tell me how to do it?
>
>
You should report it here:
https://sourceforge.net/p/maxima/bugs/

Here is a recent example of bug report arising from a SageMath user:
https://sourceforge.net/p/maxima/bugs/3521/

Best wishes,

Eric.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Re: Wrong solution/output for differential equation

2019-01-22 Thread Thrash
Can someone please report it upstream? Or tell me how to do it?

Am Montag, 21. Januar 2019 15:10:38 UTC+1 schrieb Dima Pasechnik:
>
> On Mon, Jan 21, 2019 at 2:07 PM Thrash > 
> wrote: 
> > 
> > Thank you very much! 
> > 
> > "Not yet reported upstream" 
> > What does that mean? 
>
> The bug is in Maxima, not in Sage itself. Sage components such as 
> Maxima are generally called "upstream". 
>
> > 
> > Am Freitag, 18. Januar 2019 16:06:31 UTC+1 schrieb Emmanuel Charpentier: 
> >> 
> >> This is now  Trac#27076. Not yet reported upstream (I have to finde a 
> way to recover access toi the damn sourceforge site...). 
> >> 
> >> As far as I can tell, this bug is distinct from all bugs reported 
> against desolve ; a cursoly look at othe "symbolics" tickets did not raise 
> this exact error, but I may have been mistaken : pleas feel free to correct 
> me... 
> >> 
> >> Thanks to Thrash for taking the time to formally report the bug. 
> >> 
> >> HTH, 
> >> 
> >> Le mercredi 16 janvier 2019 19:05:59 UTC+1, Thrash a écrit : 
> >>> 
> >>> As advised in the thread 
> >>> 
> >>> 
> https://ask.sagemath.org/question/45046/wrong-solutionoutput-for-differential-equation/
>  
> >>> 
> >>> I'm opening this one now. 
> >>> 
> >>> 
> >>> When running the following code, one obtains a wrong output: 
> >>> 
> >>> y=function('y')(x) 
> >>> desolve(diff(y)==4*y/x+x*sqrt(y),y,ics=[1,1]).factor() 
> >>> 
> >>> The output is 
> >>> 1/4*x^4*(log(x) - 2)^2 
> >>> instead of 
> >>> 1/4*x^4*(log(x) + 2)^2 
> >>> . Mathematica however outputs both (by running 
> >>> DSolve[{D[y[x], x] == 4*y[x]/x + x*Sqrt[y[x]], y[1] == 1}, y[x], x] 
> >>> ). 
> >>> 
> >>> 
> >>> Giac also gives the right answer: 
> >>> sage: giac("desolve([y'=4*y/x+x*sqrt(y),y(1)=1],y)").sage() 
> >>> [1/4*(ln(x) + 2)^2*e^(4*ln(x))] 
> >>> . 
> > 
> > -- 
> > 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, send 
> an email to sage-devel+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] How is package installation/uninstallation supposed to work?

2019-01-22 Thread John H Palmieri
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 recreated, but instead the changed files are reinstalled, leaving 
remnants of the previous version there. Is this how things are supposed to 
work?

In this particular case, things break: in both versions of Sphinx, there is 
a file sphinx/util/parallel.py which has the line

from math import sqrt

In the new version of Sphinx, there is a file sphinx/util/math.py, but 
sphinx/util/parallel.py also has the line from __future__ import 
absolute_import, so no confusion. In the old version of Sphinx, the 
absolute_import line is not there. In a better world, sphinx/util/math.py 
would be removed when I install the old version (since it belongs to the 
new version, not the old), but it remains, so parallel.py tries and fails 
to import sqrt from this file.

-- 
John

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Build error

2019-01-22 Thread Dima Pasechnik
On Tue, Jan 22, 2019 at 12:53 PM Devika Sugathan <
devikasugathan...@gmail.com> wrote:

>
> Please find the markupsafe-1.0.log file attached.
>

Thanks - if you look into what's in the file you will see a failure to
download the package source.
Try  running make again, making sure your machine is online

>
>
>
> On Mon, Jan 21, 2019 at 11:33 PM Dima Pasechnik  wrote:
>
>> Well, post the log file then: it's
>> /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>>
>>
>> On Mon, Jan 21, 2019 at 5:43 PM Devika Sugathan <
>> devikasugathan...@gmail.com> wrote:
>>
>>> I tried to rebuild it got a new error with some other package.
>>> Error:
>>>
>>> Error building Sage.
>>>
>>> The following package(s) may have failed to build (not necessarily
>>> during this run of 'make all-start'):
>>>
>>> * package: markupsafe-1.0
>>>   log file: /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>>>   build directory:
>>> /home/devikasugathan/sage/local/var/tmp/sage/build/markupsafe-1.0
>>>
>>> The build directory may contain configuration files and other potentially
>>> helpful information. WARNING: if you now run 'make' again, the build
>>> directory will, by default, be deleted. Set the environment variable
>>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>>
>>> Makefile:31: recipe for target 'all-start' failed
>>> make[1]: *** [all-start] Error 1
>>> make[1]: Leaving directory '/home/devikasugathan/sage'
>>> Makefile:13: recipe for target 'all' failed
>>> make: *** [all] Error 2
>>>
>>>
>>> On Mon, Jan 21, 2019 at 10:41 PM E. Madison Bray 
>>> wrote:
>>>
 FWIW this is another report (the second I've seen in a week) of
 https://trac.sagemath.org/ticket/26996 which has a potential fix
 awaiting review: https://trac.sagemath.org/ticket/27016

 The issue only occurs when trying to install the gfortran SPKG on Linux
 systems (which is usually unnecessary since most Linux distributions
 already have a perfectly usable gfortran either already installed, or
 available as a standard system package which can be installed).

 On Sun, Jan 20, 2019 at 10:59 AM Devika Sugathan <
 devikasugathan...@gmail.com> wrote:

> Hello,
> I'm a second year engineering student and would like to contribute to
> sage math. Can someone please help me with my doubts on how to proceed and
> please do give me an idea of the skill sets required for contributing. I
> have faced an issue while building the environment.
>
> While running the command *make* I got an error and the screenshot is
> attached below. Later I tried opening the log file gfortran-7.2.0.log and
> received some other error message. Kindly view the screenshots and help me
> out in this regard.
>
>
> --
> Regards
> Devika Sugathan
>
> --
> 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, send
> an email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 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, send
 an email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at https://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>> --
>>> Regards
>>> Devika S
>>> FOSS@Amrita 
>>> GitHub  | CodeChef
>>> 
>>>
>>> --
>>> 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, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Regards
> Devika S
> FOSS@Amrita 
> GitHub  | CodeChef
> 

Re: [sage-devel] Upcoming Debian freeze

2019-01-22 Thread Dima Pasechnik
On Tue, Jan 22, 2019 at 1:11 PM E. Madison Bray  wrote:
>
> On Sun, Jan 20, 2019 at 4:14 PM Samuel Lelievre
>  wrote:
> >
> > Mon 2019-01-07 14:09:18 UTC, Thierry:
> > >
> > > In his email, Tobias pointed the link (after the signature):
> > >
> > > [3] https://release.debian.org/buster/freeze_policy.html
> > >
> > > [...]
> > >
> > > Tobias, what would be the other problematic packages or issues?
> > > What should we focus on?
> >
> > There is now a "Sage Buster roadmap":
> >
> > https://wiki.debian.org/DebianScience/Sage#Buster_roadmap
>
> FWIW I added some notes next to the bullet point about gap-io.
> There's a link there to a patch I proposed a few weeks ago which
> should fix the root problem, at least on Debian.

Erik,
we have a ticket for GAP's IO package, updating your patch:
https://trac.sagemath.org/ticket/26930
- ready for review
>
> --
> 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, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Build error

2019-01-22 Thread Jean-Florent Raymond
Hello,

Were your computer connected to internet when you tried to build?
If not then try again with internet.
According to the log a problem occurred when trying to download files.




On 22.01.19 13:53, Devika Sugathan wrote:
> Please find the markupsafe-1.0.log file attached.
> 
> 
> 
> On Mon, Jan 21, 2019 at 11:33 PM Dima Pasechnik  wrote:
> 
>> Well, post the log file then: it's
>> /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>>
>>
>> On Mon, Jan 21, 2019 at 5:43 PM Devika Sugathan <
>> devikasugathan...@gmail.com> wrote:
>>
>>> I tried to rebuild it got a new error with some other package.
>>> Error:
>>>
>>> Error building Sage.
>>>
>>> The following package(s) may have failed to build (not necessarily
>>> during this run of 'make all-start'):
>>>
>>> * package: markupsafe-1.0
>>>   log file: /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>>>   build directory:
>>> /home/devikasugathan/sage/local/var/tmp/sage/build/markupsafe-1.0
>>>
>>> The build directory may contain configuration files and other potentially
>>> helpful information. WARNING: if you now run 'make' again, the build
>>> directory will, by default, be deleted. Set the environment variable
>>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>>
>>> Makefile:31: recipe for target 'all-start' failed
>>> make[1]: *** [all-start] Error 1
>>> make[1]: Leaving directory '/home/devikasugathan/sage'
>>> Makefile:13: recipe for target 'all' failed
>>> make: *** [all] Error 2
>>>
>>>
>>> On Mon, Jan 21, 2019 at 10:41 PM E. Madison Bray 
>>> wrote:
>>>
 FWIW this is another report (the second I've seen in a week) of
 https://trac.sagemath.org/ticket/26996 which has a potential fix
 awaiting review: https://trac.sagemath.org/ticket/27016

 The issue only occurs when trying to install the gfortran SPKG on Linux
 systems (which is usually unnecessary since most Linux distributions
 already have a perfectly usable gfortran either already installed, or
 available as a standard system package which can be installed).

 On Sun, Jan 20, 2019 at 10:59 AM Devika Sugathan <
 devikasugathan...@gmail.com> wrote:

> Hello,
> I'm a second year engineering student and would like to contribute to
> sage math. Can someone please help me with my doubts on how to proceed and
> please do give me an idea of the skill sets required for contributing. I
> have faced an issue while building the environment.
>
> While running the command *make* I got an error and the screenshot is
> attached below. Later I tried opening the log file gfortran-7.2.0.log and
> received some other error message. Kindly view the screenshots and help me
> out in this regard.
>
>
> --
> Regards
> Devika Sugathan
>
> --
> 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, send
> an email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 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, send
 an email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at https://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>> --
>>> Regards
>>> Devika S
>>> FOSS@Amrita 
>>> GitHub  | CodeChef
>>> 
>>>
>>> --
>>> 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, send an
>>> email to sage-devel+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
> 
> 

-- 
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, send an email 

Re: [sage-devel] Upcoming Debian freeze

2019-01-22 Thread E. Madison Bray
On Sun, Jan 20, 2019 at 4:14 PM Samuel Lelievre
 wrote:
>
> Mon 2019-01-07 14:09:18 UTC, Thierry:
> >
> > In his email, Tobias pointed the link (after the signature):
> >
> > [3] https://release.debian.org/buster/freeze_policy.html
> >
> > [...]
> >
> > Tobias, what would be the other problematic packages or issues?
> > What should we focus on?
>
> There is now a "Sage Buster roadmap":
>
> https://wiki.debian.org/DebianScience/Sage#Buster_roadmap

FWIW I added some notes next to the bullet point about gap-io.
There's a link there to a patch I proposed a few weeks ago which
should fix the root problem, at least on Debian.

-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: GSoC 2019?

2019-01-22 Thread Harald Schilly
Just FYI: I'll write an application and invite anyone who is interested to 
it.

I've also started the page for project 
ideas: https://wiki.sagemath.org/GSoC/2019

-- h


-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Build error

2019-01-22 Thread Devika Sugathan
Please find the markupsafe-1.0.log file attached.



On Mon, Jan 21, 2019 at 11:33 PM Dima Pasechnik  wrote:

> Well, post the log file then: it's
> /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>
>
> On Mon, Jan 21, 2019 at 5:43 PM Devika Sugathan <
> devikasugathan...@gmail.com> wrote:
>
>> I tried to rebuild it got a new error with some other package.
>> Error:
>>
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: markupsafe-1.0
>>   log file: /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>>   build directory:
>> /home/devikasugathan/sage/local/var/tmp/sage/build/markupsafe-1.0
>>
>> The build directory may contain configuration files and other potentially
>> helpful information. WARNING: if you now run 'make' again, the build
>> directory will, by default, be deleted. Set the environment variable
>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>
>> Makefile:31: recipe for target 'all-start' failed
>> make[1]: *** [all-start] Error 1
>> make[1]: Leaving directory '/home/devikasugathan/sage'
>> Makefile:13: recipe for target 'all' failed
>> make: *** [all] Error 2
>>
>>
>> On Mon, Jan 21, 2019 at 10:41 PM E. Madison Bray 
>> wrote:
>>
>>> FWIW this is another report (the second I've seen in a week) of
>>> https://trac.sagemath.org/ticket/26996 which has a potential fix
>>> awaiting review: https://trac.sagemath.org/ticket/27016
>>>
>>> The issue only occurs when trying to install the gfortran SPKG on Linux
>>> systems (which is usually unnecessary since most Linux distributions
>>> already have a perfectly usable gfortran either already installed, or
>>> available as a standard system package which can be installed).
>>>
>>> On Sun, Jan 20, 2019 at 10:59 AM Devika Sugathan <
>>> devikasugathan...@gmail.com> wrote:
>>>
 Hello,
 I'm a second year engineering student and would like to contribute to
 sage math. Can someone please help me with my doubts on how to proceed and
 please do give me an idea of the skill sets required for contributing. I
 have faced an issue while building the environment.

 While running the command *make* I got an error and the screenshot is
 attached below. Later I tried opening the log file gfortran-7.2.0.log and
 received some other error message. Kindly view the screenshots and help me
 out in this regard.


 --
 Regards
 Devika Sugathan

 --
 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, send
 an email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at https://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> 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, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Regards
>> Devika S
>> FOSS@Amrita 
>> GitHub  | CodeChef
>> 
>>
>> --
>> 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, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Regards
Devika S
FOSS@Amrita 
GitHub  | CodeChef


-- 
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, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more