Re: [sage-devel] Re: Re; Symbolic matrix inverse still gives seg-fault, core-dump

On 06/20/2018 04:21 PM, Nils Bruin wrote: > > Hm, if you intend to use that in sage library code, do remember to > change back the state to domain:complex when you're done Better yet, set it back to whatever it was originally. -- You received this message because you are subscribed to the

Re: [sage-devel] How much do we support the casual user

On 03/27/2018 03:11 PM, William Stein wrote: > > Sorry -- I'm not trying to flamebait you, but in order to have any > further discussion, what exactly do you think a floating point number > in a computer is? > What is the mathematical meaning of > float(1) > The thread was about casual

Re: [sage-devel] How much do we support the casual user

On 03/27/2018 12:22 PM, William Stein wrote: > > There are similar examples in MATLAB, involving rational numbers, > implicit floating point, etc. > Does multiplication by a positive scalar change the rank of a matrix? Can two equal matrices have different ranks? (I'm willing to entertain the

Re: [sage-devel] How much do we support the casual user

On 03/27/2018 12:18 PM, William Stein wrote: > > I don’t consider that a bug.  > I know, but ask anyone without a PhD in math. -- 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,

Re: [sage-devel] How much do we support the casual user

On 03/27/2018 03:07 AM, Ralf Stephan wrote: > Hello, > I thought I'd try Sage for a casual computation. My favorite bug from when I was an undergrad... sage: B = matrix([[ -3, 2, 1 ], : [ 2,-4, 4 ], : [ 1, 2,-5 ]]) sage: B.rank() 2 sage:

[sage-devel] Re: 6 hours left to prepare GSoC application for this year!

sentations as modules). Best regards, Michael On Tuesday, January 23, 2018 at 10:29:34 AM UTC+1, Dima Pasechnik wrote: > > Are we skipping this year? > I'm about to add the 3rd project to the wiki: > https://wiki.sagemath.org/GSoC/2018 > but this is not enough, I think. Can we

Re: [sage-devel] dicts in doctests

On 12/12/2017 09:30 AM, Erik Bray wrote: > > Another workaround that's so obvious I smacked myself on the head is > that for many cases, particularly objects that have a small dict in > their representation, is to simply change the __repr__ so that its > dict is always displayed sorted. If the

[sage-devel] Re: Sage 8.1 building Mac-app fails

I did a make in ~/sage-8.1. When that completes I cd to src/Mac-app and run make again. My version of Mac OS is 10.13.2. -- 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

[sage-devel] Re: Sage 8.1 building Mac-app fails

It appears that diskimage still has the tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg file open. You can find this with "sudo lsof |fgrep tmp-sage-8.1". Killing disk image allows the "hdiutil convert -format UDBZ -o sage-8.1-OSX_10.13.2_x86_64.app.dmg tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg"

[sage-devel] Re: Sage 8.1 building Mac-app fails

Contents/Resources/sage rm -f sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/sage ln -s Contents/Resources/sage/sage sage-8.1-OSX_10.13.2_x86_64/SageMath-8.1.app/sage cp /Users/michael/sage-8.1/src/bin/sage-README-osx.txt sage-8.1-OSX_10.13.2_x86_64/README.txt mkdir -p sage-8.1-OSX_10.13.2_x86_64/.ba

[sage-devel] Sage 8.1 building Mac-app fails

, see below. Hopefully there is an easy fix. Mike *CpResource* sage-document-cython.icns build/Debug/Sage.app/Contents/Resources/sage-document-cython.icns cd /Users/michael/sage-8.1/src/mac-app builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve

[sage-devel] Re: Error Installing Sage 8.0 (gcc-7.2.0 won't install)

I upgraded to Command Line Tools for Xcode V9.1 and Sage 8.1 now compiles. -- 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] Re: Error Installing Sage 8.0 (gcc-7.2.0 won't install)

On Sunday, November 19, 2017 at 11:27:43 AM UTC-5, M Mills wrote: > > Thanks. > > On Sunday, November 19, 2017 at 4:34:30 AM UTC-6, Dima Pasechnik wrote: >> >> 8.0 will not work with the current Xcode. >> You would need 8.1.rc2 (or wait for 8.1 to be done, probably very soon). >> > This is still

Re: [sage-devel] dicts in doctests

On 12/06/2017 09:49 AM, Erik Bray wrote: > > Did anyone ever think up a better solution to this? > Whatever you do, you wind up with a big pile of dict output in the middle of your test case. So (where possible) you might as well use that space to define a new dict containing the expected

[sage-devel] io_shapes_las missing in saga_cmd in fresh linux install

Hello everyone, First all, I am completely new to SAGA as well as GIS. However, I thinks this perhaps just a configuration error on my side on my linux host. I am using arch linux with gcc 7.2.0 I have just cloned the recent version from git. [michael@moo:saga-gis-code|master]$ git remote

Re: [sage-devel] conditionalise installation of many spkg's?

On 11/27/2017 09:00 AM, Erik Bray wrote: > >> On the other hand, if we standardize on the name of the m4 file (i.e. >> it's fixed but optional), then you could use "sinclude" to grab them all >> at once, ignoring the errors from the ones that don't exist. > > I'm not really sure what you mean

Re: [sage-devel] conditionalise installation of many spkg's?

On 11/27/2017 07:39 AM, Erik Bray wrote: > > One thing I might do differently from your proposal: I have some > experimental code for an autoconf macro that can slurp in macros from > multiple sub-directories. The idea being that you could put little > .m4 files in each build/pkgs/ dir with

Re: [sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

This is still broken ins Sage 8.1.rc2 with the same error. Should I post a new thread? -- 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

Re: [sage-devel] build fail on Fedora 26: cannot touch...: Permission denied

On 11/06/2017 09:54 PM, Clay Thompson wrote: > > Usually when I install from source/devel, I install as root ("sudo > make"). But Sage will not allow me to do that. General advice, not specific to SageMath: Most software should be built as an unprivileged (i.e. non-root) user. It's only when

Re: [sage-devel] Implementation plan : inclusion of OpenSSL

On 10/27/2017 10:53 AM, Emmanuel Charpentier wrote: > > Okay : I'm not still convinced, but I'll follow you on a "primum non > nocere" basis. > > If we follow you, we have to take back any talk of *inclusion* right > now. The solution is to depend *unconditionally* on a systemwide OpenSSL > and

Re: [sage-devel] Sagemath mirrors security issues

On 10/25/2017 04:29 PM, Emmanuel Charpentier wrote: > Ouch ! The security proble so well explained by William turns out to be > a much larger "social" problem... > > Worth atacking ? > Not really... you can get commit access to sage.git by asking nicely. Ultimately, HTTPS is pointless unless

Re: [sage-devel] Implementation plan : inclusion of OpenSSL

On 10/25/2017 12:14 PM, Emmanuel Charpentier wrote: > Can you explain how the Wget case is different from ours ? A single entity (the FSF) owned the copyright on all of the code in wget when they changed the license to add the exception. The same is not true of SageMath: we don't have copyright

Re: [sage-devel] Use system R with sage?

On 10/20/2017 11:30 AM, Nils Bruin wrote: > Do we actually get real benefit from packaging R with sage? It seems to > me R is a very popular, very mature piece of software. Isn't it easy to > install R on any of the platforms supported by sage? If that is the > case, wouldn't it be much easier to

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

On 10/17/2017 09:37 PM, William Stein wrote: > > The mail that they sent to contributors ended with, > >   If we do not hear from you, we will assume that you have no objection. > > That's not the way it works, > > > Says who?   This is all about how things work legally, and the

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

On 10/17/2017 08:42 PM, Maarten Derickx wrote: > > What makes you think their process is dubious? They are reaching out for > consent from all people who have contributed, and they have removed the > code from the several people who have objected on record. > The mail that they sent to

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

On 10/17/2017 03:56 PM, Emmanuel Charpentier wrote: > > Throwing my vote away: > > [X] Require OpenSSL to be installed on the system. > > > That's not one of the proposed options. That's what I meant by "throwing my vote away" =) > But it seems to imply that we should wait for

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

On 10/17/2017 02:55 AM, Jeroen Demeyer wrote: > So basically you want to add OpenSSL to Sage and then say > > "We know that distributing SageMath might be illegal, but it is unlikely > that somebody will sue. Use at your own risk!" > > I doubt that this is such a good deal. > Not to mention

Re: [sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

What is the best way to do this? The file is extracted from the mpir-3.0.0.tar.bz2 every time make is run. On Wednesday, August 2, 2017 at 5:41:01 PM UTC-4, Bill Hart wrote: > > The only workaround I'm currently aware of is to remove the offending > addmul_1.asm file. It is to do with our use

[sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

I tried AS_INTEGRATED_ASSEMBLER=1 make without success, I also tried adding it to my environment and also from the debugging shell. I also tried: export CFLAGS="-Wa,-q $CFLAGS" without success. The make ends with: vscanf.o scanf/.libs/vsscanf.o -L/Users/michael/sage-8.0/local/lib

[sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

I found this thread on the MPIR issues list: https://github.com/wbhart/mpir/issues/217 It appears that the MacOS assembler is old. Is there to configure the sage build as they suggest? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Second round poll for H5 a specific guideline for writing docstrings

On 05/19/2017 02:55 AM, david.coud...@inria.fr wrote: > A method like `Graph().is_bipartite(certificate=False)` returns either > ``True``or ``False`` when ``certificate==False``, or a tuple `(bool, > dict)` when ``certificate==True``. What would be the recommended writing > style for the output

Re: [sage-devel] Sage policy question: require docstrings and doctests?

On 05/17/2017 04:07 AM, Jeroen Demeyer wrote: > > Totally +1 > > Too bad that too many people take the coverage script too literal. > > For functions which are meant to be called directly by end users, > doctests are essential because they should show examples of how the > function should

Re: [sage-devel] Sage policy question: require docstrings and doctests?

On 05/09/2017 03:14 PM, John H Palmieri wrote: > Sage's developer's guide says: "Every function must have a docstring" > which must include "An EXAMPLES block for examples. This is not > optional." What is meant by "function"? Here is an example, taken from > ticket #21399: > > | > importsys > >

Re: [sage-devel] Re: Trac slow

On 04/21/2017 05:30 AM, Erik Bray wrote: Does this mean that we need some robots.txt somewhere, perhaps after some restructuring, which would protect expensive resources from this sort of overload? There already is a robots.txt and this host was not respecting it. If this becomes a bigger

Re: [sage-devel] OpenSSL relicensed! (Licensing Update - OpenSSL Blog )

On 03/24/2017 12:44 AM, William Stein wrote: Licensing Update - OpenSSL Blog https://www.openssl.org/blog/blog/2017/03/20/license/ While this would obviously be good for SageMath and most linux distributions, the email that they sent out probably gave some lawyer cramps: If we do not

Re: [sage-devel] Reviewing tickets with dependencies

On 03/16/2017 12:26 AM, Ralf Stephan wrote: > The author of 1234 has IMO the responsibility to monitor 987 and do > timely updates of 1234 when 987 changes, including canceling the > positive flag on 1234. > I don't want to beat this to death, but if the author of 1234 is so vigilant, why can't

Re: [sage-devel] Re: Reviewing tickets with dependencies

On 03/15/2017 07:58 PM, Simon King wrote: > Hi Michael, > > On 2017-03-15, Michael Orlitzky <mich...@orlitzky.com> wrote: >> It's possible, but asking for trouble. If 1234 depends on 987, then it's >> possible that the reviewer in 987 could say "I don't like any of

Re: [sage-devel] Reviewing tickets with dependencies

On 03/15/2017 08:18 AM, Simon King wrote: > > Assume there is ticket 1234 that depends on ticket 987. Moreover, > assume that 987 needs work. Would it still be possible to give > a positive review to 1234? Of course, 1234 would only be merged > after 987 received a positive review, too. > > I

Re: Function calling syntax (was Re: [sage-devel] integration algorithms)

On 02/27/2017 09:25 PM, Nils Bruin wrote: > > But only after you've declared f to be a function. If you want to do it in > one line, you'd have to spell out: > > f(x) = function('f')(x) > > ... > > f=function('f')(x).function(x) Well that's no fun. > which would probably not fill you with

Re: Function calling syntax (was Re: [sage-devel] integration algorithms)

On 02/27/2017 06:18 PM, Nils Bruin wrote: > > Michael Orlitzky wrote: >> >> I tried the thing that makes more semantic sense, >> >> sage: f = function('f',x) >> >> ... > > Ah, OK. And this made more semantic sense to you because you wanted f

Re: [sage-devel] integration algorithms

On 02/26/2017 04:59 PM, Nils Bruin wrote: > On Sunday, February 26, 2017 at 8:17:05 AM UTC-8, Michael Orlitzky wrote: >> >> >> sage: f = function('f')(x) > > > Please consider to stop using such assignments. It propagates a confusion > between the *fun

Re: [sage-devel] integration algorithms

On 02/26/2017 01:52 AM, Ralf Stephan wrote: > Users of integrate() usually don't care which "algorithm" is used, > just that the thing is solved. At the moment the default behaviour > is calling Maxima only, and you have to know/read that you can > try other algorithms too. Many beginners don't

Re: [sage-devel] Meaning of log2 etc.

On 02/23/2017 08:15 AM, Peleg Michaeli wrote: > Is it not far better to have log2 as a function (log2(x) = log(x, 2)) > than having it as a constant? > > It's a bit weird that one tries log2(3) and gets "ValueError: the number > of arguments must be less than or equal to 0". There are a lot of

Re: [sage-devel] Doctests broken in ticket #20729

On 02/20/2017 10:00 AM, Travis Scrimshaw wrote: > Could we get a little more context for your problem? In particular, is > foo.py included in the Sage source tree or is it something that you are > building separately? If it is the former, have you tried "from path.to.foo > import bar", where

Re: [sage-devel] Doctests broken in ticket #20729

On 02/14/2017 10:32 AM, Michael Orlitzky wrote: > On 02/14/2017 10:19 AM, Erik Bray wrote: >> >> Add explicit imports to the test, for example: >> >> ... > > Same error: name 'foo' is not defined > If no one has any idea, I would personally prefer it the nex

Re: [sage-devel] Doctests broken in ticket #20729

On 02/14/2017 10:19 AM, Erik Bray wrote: > > Add explicit imports to the test, for example: > > TESTS:: > > sage: from foo import foo > sage: foo() > True Same error: name 'foo' is not defined -- You received this message because you are subscribed to the

[sage-devel] Doctests broken in ticket #20729

Can someone please give me a hint as to how to fix all of the doctests affected by https://trac.sagemath.org/ticket/20729? Here's an example: $ cat foo.py from sage.all import * def foo(): """ Returns ``True``. TESTS:: sage: foo() True """

[sage-devel] Re: Workaround for missing link to MacTex for MacOS Sage app

age My system does not have a ~/.sage/init.sage file. Mike On Thursday, January 19, 2017 at 11:12:22 PM UTC-5, Michael Frey wrote: > > I found that when trying to access LATeX (MacTeX) calls in a Sage notebook > via MatPlotLib or directly Sage would report that it could not find some

[sage-devel] Workaround for missing link to MacTex for MacOS Sage app

I found that when trying to access LATeX (MacTeX) calls in a Sage notebook via MatPlotLib or directly Sage would report that it could not find some TeX function. It appears that the PATH variable being used by the Sage app is pointing to /usr/texbin, not /Library/TeX/texbin. As a workaround I

[sage-devel] SendGrid (trac emails) issue

[167.89.100.166]:32175: 450 4.3.2 Service currently unavailable; from=<bounces+3351942-d13f-michael=orlitzky@mail.sagemath.org>, to=<mich...@orlitzky.com>, proto=ESMTP, helo= and there are none afterwards. Can someone with access to the SendGrid account please open a support

[sage-devel] Error when attaching file, NameError: name 'cython' is not defined

I am trying to attach a code file to a sage notebook. The call is : attach ("~/.sage/MHF_Bloch_n_Plot.sage"). The error I get is "NameError: name 'cython' is not defined". The code in the attach file is: ... cython(""" #Parallel Cython, Numpy calls -- 3 part3 #Part 1 #Cython version for

Re: [sage-devel] vote on behaviour of is_similar for matrices

On 10/27/2016 12:21 PM, Travis Scrimshaw wrote: > I am for BB because: > Both options have merit. If most people think we should have a user-friendly error for a common mistake (mismatched dimensions), then maybe it makes sense to add an ignore_dims (default: False) parameter for the people who

Re: [sage-devel] add curl as a standard package

On 10/24/2016 09:46 AM, Emmanuel Charpentier wrote: > > Not the same problem. To detect curl, it is enough to find an executable > named "curl" in the path. As far as I know, R uses a library, and this > is known to be not so easy to find. > Which library does R link against? If you can find

Re: [sage-devel] add curl as a standard package

On 10/24/2016 06:41 AM, Vincent Delecroix wrote: > In between? > > * having a curl pacakge that will be installed if not present on the > system (~the same way we deal with gcc) > And the same for pcre and xz. Check for it in ./configure, and give us a way to override it, like

Re: [sage-devel] Problem with pari in 7.4beta6

On 10/01/2016 01:18 PM, Emmanuel Charpentier wrote: > [ Erroneously reported first on sage-release. Apologies.. ] > > I can't build sage 7.4beta6 on Debian testing : PARI fails to build on a > (copy of) a (functional) Sage tree after distclean. See the attached log. > This happens either after

Re: [sage-devel] Re: openblas segfault?

On 09/26/2016 03:03 PM, 'Martin R' via sage-devel wrote: > > Is there a quick fix? > To get something usable, try ./configure --with-blas=atlas before running "make". I had a similar problem: https://trac.sagemath.org/ticket/21561 -- You received this message because you are subscribed

Re: [sage-devel] doctesting and sys.path

On 09/20/2016 01:40 AM, Clemens Heuberger wrote: > I have two .py files (not in the library) in the same directory where one > imports the other. I'd like to run doctests, but the local directory does not > seem to be in the search path. Is there any way of doing this apart from > fiddling around

Re: [sage-devel] Re: giacpy depends (silently) on SageObject

On 09/01/2016 05:39 PM, François Bissey wrote: > > Let's talk about practical matters. I have giacpy_sage in the > sage-on-gentoo overlay already. How would you suggest to deal with this, > in this context? > Since there's no API/ABI convention for the sage library, you have to rebuild

Re: [sage-devel] Re: giacpy depends (silently) on SageObject

On 09/01/2016 09:46 AM, leif wrote: > > Exactly. (See also my other reply.) > > It would be dumb and totally annoying if all such packages would get > rebuilt upon *any* change to the Sage library, and just as bad as having > to "manually" figure out /which/ packages might need rebuilding after

Re: [sage-devel] Re: Ethical evaluation of repository hosting services

On 08/03/2016 12:46 PM, Volker Braun wrote: > > * You can't block by url on https > This is unfortunately becoming less and less true. With Server Name Indication (SNI), the web server waits to see the Host header in your request before deciding which certificate to present to you. That lets

Re: [sage-devel] Re: VotePlugin for trac?

On 07/06/2016 11:06 AM, Erik Bray wrote: >> >> Is there a single example where voting on bugs has been used effectively? > > You mean like hundreds of projects where people write +1/-1/(+/-)0 on > discussions? Usually that's just informal but sometimes it's actually > tallied too, where a

Re: [sage-devel] Re: VotePlugin for trac?

On 07/06/2016 06:30 AM, Simon King wrote: > > It seems useless to me. Thus, counter-question: Any substantial benefit > with this? > Yeah, I've worked on probably a hundred open source projects that have this feature in one way or another. The votes are always completely ignored, and users who

[sage-devel] Could not import nbconvert // Sage 7.2 in virtual machine (CentOs 6.7) OVA file from May, 12th 2016

, Michael -- 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@google

Re: [sage-devel] Re: consistency in trac e-mails

On 06/26/2016 05:55 PM, François Bissey wrote: > On 06/27/16 09:50, Dima Pasechnik wrote: >> could you check sage-trac@googlegroups for these "missing" emails? > > Didn't think about that. I don't remember seeing the tickets in the > digest. But they are there. > The SPF record for

Re: [sage-devel] Re: trac mails are back on

On 06/22/2016 06:39 PM, Dima Pasechnik wrote: > > > (going via sendgrid.net ). > > Why that? I'm getting ugly HTML mails with obfuscated links (and of > course phishing attempt alerts). > > GCE does not allow running smtp on the usual port 25. So one has to

Re: [sage-devel] more tests in sage (not doctests)

On 06/22/2016 04:57 AM, Jeroen Demeyer wrote: > >> b) randomized test, example: check for a number of randomly >> generated number fields that arithmetic operations with randomly >> generated number field elements gives the correct results. >> Randomized tests help to identify issues that occur

Re: [sage-devel] Piecewise functions in Sage 7.2

On 05/21/2016 06:06 PM, paulmasson wrote: > Since the SageMathCell server has been updated to Sage 7.2, I've been > experiencing issues with piecewise functions. For example, define a > simple saw tooth with > Piecewise functions were totally rewritten in #14801. Lower-case "piecewise" now works

Re: [sage-devel] Deprecate the use of properties in all public API

On 05/04/2016 09:13 AM, Erik Bray wrote: > > I call it premature encapsulation. > We can agree there. But when you're programming on a team, the hardest part is making sure everyone else doesn't do anything stupid. And in the Java/C# world, half of the team is 22 years old and writing their

Re: [sage-devel] Deprecate the use of properties in all public API

On 05/03/2016 09:22 AM, Erik Bray wrote: > > You seem to have this view that the sole purpose of getter and setter > methods is to update a private member of some object. Am I > understanding that correctly? Because either I'm misunderstanding > you, or you seem to be confused about why property

Re: [sage-devel] Deprecate the use of properties in all public API

On 05/03/2016 03:51 AM, Erik Bray wrote: > > I can say from significant experience that that is *not* the only > useful feature of property. > > Let's also not forget the even deeper magic that is the descriptor > protocol in general. > Well, what's the other useful feature? It lets you call

Re: [sage-devel] Deprecate the use of properties in all public API

On 05/02/2016 06:07 AM, Erik Bray wrote: > On Mon, May 2, 2016 at 10:35 AM, Jeroen Demeyer > wrote: >> My vote: >> >>> [X] Phase out properties which perform any non-trivial computation >> >> >> In certain cases, properties might be useful (but it could very well be that

Re: [sage-devel] Proposal: install all pip-installable components of Sage via pip, directly

On 04/16/2016 11:06 AM, Jeroen Demeyer wrote: > On 2016-04-16 16:19, Michael Orlitzky wrote: >> It gets us one step closer to a Sage that will use what's already >> installed on the system. > > No, it does not do that. It's just a different way of installing packages. &

Re: [sage-devel] Proposal: install all pip-installable components of Sage via pip, directly

On 04/16/2016 08:06 AM, Jeroen Demeyer wrote: > What is the problem that your proposal fixes? > It gets us one step closer to a Sage that will use what's already installed on the system. Users can upgrade pip-installed packages themselves (pip --update, or whatever). And since Sage won't be

Re: [sage-devel] Re: how we develop sage

On 04/14/2016 09:21 AM, Jeroen Demeyer wrote: > A really important point (which so far hasn't been addressed) is how to > deal with breakages of affiliated packages. I see two ways: > > 1. If I make a change to some core package, it is my responsibility to > ensure that no affiliated package

Re: [sage-devel] Re: how we develop sage

On 04/12/2016 03:58 PM, William Stein wrote: > > It's all my fault originally, but I think I've learned something about > software engineering during the last few years... and I think we're > doing it wrong. > Don't be too hard on yourself. The fact that every function in Sage is documented,

Re: [sage-devel] mails from trac marked as spam?

On 03/22/2016 05:43 AM, Harald Schilly wrote: > > Seems like it works better now? However, we could add a SPF TXT line to > the DNS of sagemath.org? I.e. my idea is, that by including the sender > explicitly in this "v=spf1 include: ?all" entry, the > score would get pushed higher (no longer

Re: [sage-devel] mails from trac marked as spam?

On 03/18/2016 10:39 AM, Daniel Krenn wrote: > On 2016-03-18 14:55, Harald Schilly wrote: >> I have no idea about trac's email setup, can you forward me the source >> code of one of such emails? My guess is, that it doesn't properly sign >> the email, etc. > > The relevant section in the header of

Re: [sage-devel] Sage "and" Anaconda

On 03/11/2016 05:45 AM, Erik Bray wrote: > >> It also has few packages compared to Nix or Gentoo. Building packages >> from source is complicated, and there are a ton of corner cases and >> weird features that you need to support. It also quickly becomes >> necessary to have some way of sharing

Re: [sage-devel] Sage "and" Anaconda

On 03/11/2016 06:03 AM, Erik Bray wrote: > > I don't think this was intentional, but the degree to which this > entire post ignores / dismisses Windows comes off as a bit flippant. > Maybe you didn't know this but I'm working on getting sage and its > dependencies working on Windows. The VM

Re: [sage-devel] Sage "and" Anaconda

On 03/10/2016 03:23 PM, William Stein wrote: > > Could you say more? (I mean about what you might imagine Sage could > do to improve -- both incrementally or dramatically?)I'm sure > everybody really appreciates your experience, and speaking up about > this here. > Oops, I wrote a book:

Re: [sage-devel] Sage "and" Anaconda

On 03/10/2016 02:37 PM, William Stein wrote: >> >> I'm not arguing that complex is better than simple, but most of their >> build scripts are so simple that they don't work. Error handling is >> nonexistent, options are hard-coded, paths are random, the environment >> is not sanitized, installed

Re: [sage-devel] Sage "and" Anaconda

On 03/10/2016 01:47 PM, Jeroen Demeyer wrote: > On 2016-03-10 19:23, Michael Orlitzky wrote: >> Its main issue is that all of the build >> scripts are incredibly naive. For example, the source-based install >> routing for PostgreSQL is, >> >> https://github.co

Re: [sage-devel] Sage "and" Anaconda

On 03/10/2016 11:19 AM, Jeroen Demeyer wrote: > > Never having used conda, some quick questions in case you know the answer: > 1) Does conda support the same operating systems as Sage? > 2) Does conda deal with non-Python packages too? > 3) Does conda support building packages in parallel? > >

Re: [sage-devel] Re: subs deprecation -- what the heck?!

On 03/02/2016 11:45 AM, Nils Bruin wrote: > > It's easy to explain "expressions do not support calling syntax. You > need a function for that". > It's hard to explain "expressions don't really support calling, except > in some edge cases that you will initially encounter most". > By having the

Re: [sage-devel] The package system: redundancy

On 03/04/2016 09:01 AM, kcrisman wrote: > > > The problem, as I see it, is that Sage has built up over the years its > own ad-hoc packaging system. This is actually really cool, because > it's what's allowed Sage to be installable on a wide range of > platforms! I think this

Re: [sage-devel] I think my students hate me

On 03/04/2016 12:59 PM, john_perry_usm wrote: > > I'm about halfway through, and *no one* has gotten full credit on the > problem. To be fair, two people marked it False, but they were also > supposed to provide a true statement. One provided no statement, and the > other -- I am not making this

Re: [sage-devel] Re: subs deprecation -- what the heck?!

On 02/29/2016 06:34 PM, William Stein wrote: > > So we deprecated this 7 years ago? Yikes. Also, that patch is 1.2MB, > so it probably mentions everything. > > Maybe we should finally really deprecate this, or de-deprecate it, if > we're never going to. You can't get rid of it because

Re: [sage-devel] upgrade openssl

On 01/28/2016 01:39 PM, Thierry wrote: > > It should work on OSX as well, at least it was tested on OSX 32bit for > 1.0.1e https://trac.sagemath.org/ticket/16454 > Unrelated: the self-signed certificate on trac.sagemath.org is expired. If someone can generate a new one, just make it valid for

Re: [sage-devel] Re: domain:complex

On 12/03/2015 01:17 PM, Nils Bruin wrote: > On Thursday, December 3, 2015 at 8:24:29 AM UTC-8, Dima Pasechnik wrote: > > as a 1st step, a way for the user to set up Maxima domain is badly > needed. > It does not look like a good idea to hardcode domain once and for all. > > > Though

Re: [sage-devel] Re: sage -i

On 10/29/2015 10:47 AM, William Stein wrote: > > In the meantime, I may just have to patch Sage to get rid of the > interactive nature of "-i"... or use some workaround involving > automate. yes | sage -i csdp -- You received this message because you are subscribed to the Google Groups

[sage-devel] Legend background color

I want to change the color of the bikeshed: http://trac.sagemath.org/ticket/19485 Please limit your insults to myself and my immediate family. Seriously: is there any place (like in the notebook?) where the gray background for legends works better than white? And if not, have I found

Re: [sage-devel] Sage on OS X: El Capitan

not a fan of /Applications/sagemath-$version, as then upgrading causes a new folder to be made, which will break any aliases/dock shortcuts. Michael -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and st

Re: [sage-devel] Re: Sources of funding - perhaps computer manufacturers?

On 09/30/2015 02:25 PM, William Stein wrote: > However, from 2011 to now, year-on-year growth is > slightly less than 0%. It was maybe -10% from 2013 to 2014. There are probably a lot of people like me who haven't been back to sagemath.org since the switch to git. I just `git pull` every once in

Re: [sage-devel] how should the expression relation test be named?

On 09/23/2015 12:31 PM, Ralf Stephan wrote: > Symbolic expressions are tested for zero with bool(ex) at the moment, > regardless if one wants to know if ex is identical with the zero object > or if one wants a simplification of ex (which is slow). > > Because a finer-grained interface is needed

Re: [sage-devel] Re: *.math.washington.edu hardware resources

On 09/14/2015 02:23 PM, Thierry wrote: > Hi, > > i am pretty remote right now (for a Sage tutorial actually;), but you can > count me in, starting from the next week. > > Some few ideas i planned to work on for a while: > > - random testing : the current random doctests uses a single seed, so

Re: [sage-devel] Hello, world - How can a new person help?

On 09/06/2015 09:46 AM, Michael Orlitzky wrote: > On 09/06/2015 01:27 AM, Siddharth Bhat wrote: >> >> c) looked at the "for beginner" issues on Trac, but all of them seem to >> have people assigned to them. >> > > When a new ticket gets created, it a

Re: [sage-devel] Hello, world - How can a new person help?

On 09/06/2015 01:27 AM, Siddharth Bhat wrote: > > c) looked at the "for beginner" issues on Trac, but all of them seem to > have people assigned to them. > When a new ticket gets created, it automatically gets assigned to someone who might be interested. That's mostly a relic from a time when

Re: [sage-devel] Expanding vectors

On 08/30/2015 09:19 AM, Jeremy Martin wrote: It would be helpful if the components of a vector could be expanded and simplified. Right now this happens: Your best bet is to use simplify_full() instead of simplify: sage: (v-w).simplify_full().is_zero() True That's not guaranteed to work

[sage-devel] Simultaneously citing Sage and a new paper

I'm working on a paper where we coin a new term and implement a new algorithm. I'd like to cite Sage as an implementation, but then I have a chicken and egg problem. I'd like the code to work before we submit the paper.. but to do that, I need to add a method that only appears in our paper. The

Re: [sage-devel] Re: Simultaneously citing Sage and a new paper

On 08/20/2015 02:40 PM, Nathann Cohen wrote: I'm working on a paper where we coin a new term and implement a new algorithm. I'd like to cite Sage as an implementation, but then I have a chicken and egg problem. If your algorithm is complicated and needs a proof, then I'd

<    1   2   3   4   5   6   7   8   9   10   >