[sage-devel] Re: VOTE: move Sage development to Github

+1 for GitHub (hi folks 🙂) -Keshav On Wednesday, September 21, 2022 at 10:23:36 AM UTC-7 David Roe wrote: > Dear Sage developers, > Following extensive discussion, both recently > > (prompted > by issues upgrading the trac

[sage-devel] Re:

On 07/21/2015 10:37 AM, Елена Соменко wrote: > > Hello, Keshav! Thank you for information and for help! > > > Yes, now my goal is to create user interface for Sage Notebook at least. > Maybe, then I'll try to work on documentation and other. For your > advice, I’ll send my translated files on g

[sage-devel] Re:

On 07/20/2015 06:18 AM, Елена Соменко wrote: > Hello, Mr. Kini. > > My name is Olena Somenko. I am from Kirovograd, Ukraine. I work as a > senior teacher in Kirovograd Institute of Human Development. Our > teachers and students actively use Sage in the work. So, there is a > need to create Ukrain

[sage-devel] Re: systemd and trac #381

Henry de Valence writes: > Hi all, > > while looking at the SAGE FAQ here [1], I noticed the link to Trac #381 [2] > (the link is broken, on the FAQ page, though). > > One option which is not mentioned, but which is extremely convenient, > is to run Sage using a systemd user session. The Arch Linu

[sage-devel] Re: Giant email subjects from Trac

P Purkayastha writes: > On 02/01/2014 12:33 AM, Keshav Kini wrote: >> Hi, >> >> Check this out: http://i.imgur.com/sbNIk6J.png >> >> I *literally* cannot read this mail, because my monitor is not large >> enough for the message body to even appear in my

[sage-devel] Giant email subjects from Trac

Hi, Check this out: http://i.imgur.com/sbNIk6J.png I *literally* cannot read this mail, because my monitor is not large enough for the message body to even appear in my mail client! :) Even "View Source" doesn't work, since the thing is UUencoded! I guess someone will say I should use a better

[sage-devel] Re: Remaining Mercurial patches

maldun writes: > And I have another question: why github? afaik bitbucket would allow > to use both git and mercurial. So it is possible for users to submit > a mercurial patch on a git repo and vice versa. I think this would > avoid a lot of compability issues. I've never heard of such a featur

[sage-devel] Re: motivation: here's one reason your contributions to Sage matter...

john_perry_usm writes: > On Tuesday, October 1, 2013 1:42:43 AM UTC-5, Keshav Kini wrote: > > But as far as I know, Sage is not proof-aware in any way. I've > never > heard theorem-proving people talk about making use of existing > computer > a

[sage-devel] Re: motivation: here's one reason your contributions to Sage matter...

rjf writes: > On Monday, September 30, 2013 11:42:43 PM UTC-7, Keshav Kini wrote: > But as far as I know, Sage is not proof-aware in any way. > > Why would you necessarily know about this? I don't know, why would I? > I am well aware > that Maxima, a component of

[sage-devel] Re: motivation: here's one reason your contributions to Sage matter...

Julien Puydt writes: > Le 01/10/2013 08:42, Keshav Kini a écrit : >> But as far as I know, Sage is not proof-aware in any way. I've never >> heard theorem-proving people talk about making use of existing computer >> algebra systems and I can't imagine how they cou

[sage-devel] Re: motivation: here's one reason your contributions to Sage matter...

rjf writes: > On Sunday, September 29, 2013 9:53:07 AM UTC-7, Keshav Kini wrote: > > > > Could you elaborate on what relevance you see Sage having to > truth > maintenance and theorem proving? > > > Typically the people who work in the

[sage-devel] Re: motivation: here's one reason your contributions to Sage matter...

rjf writes: > 5. Assemblies of people who study large computer systems, parallel > computing, software techniques for > compilation, truth maintenance, theorem proving, etc ... in which > Sage is some kind of example of a > problem and solution which can be explained to others and others can > off

[sage-devel] Re: centered banner

P Purkayastha writes: > Hi devs, > > How would you like a centered banner when sage is started? Is that > something desirable, or do you always prefer a left-aligned banner? Left-aligned, please, unless you can get it to re-center when the terminal changes size. -Keshav -- You received this m

[sage-devel] Re: Is the glass half-full or half-empty ? Pick a standard.

Darij Grinberg writes: > Hi, > > On Tuesday, 20 August 2013 23:21:43 UTC+2, Andrew Gainer-Dewar wrote: > > How about extending the input signature of Graph.is_connected() > to > include an option > > empty_graph_is_connected = False > > ? > > > The problem with suc

[sage-devel] Re: Is the glass half-full or half-empty ? Pick a standard.

John Cremona writes: > [...] and then you will not have the silly > situation that (in 5.11) > > sage: G = Graph([]); G > Graph on 0 vertices > sage: G.is_connected() > True > sage: G.connected_components() > [] > as to me it seems contradictory to have a graph claiming to be > connected but havin

[sage-devel] Re: setlocale problem

Volker Braun writes: > Are you ssh-ing into the machine or not? And if yes, from where? It > is not recommended to forward the environment by default over ssh but > it can be configured (see SendEnv, AcceptEnv in the ssh > configuration, /etc/ssh/ or ~/.ssh/config) It's not recommended? Debian s

[sage-devel] Re: UTF-8 and old terminals (new startup banner)

William Stein writes: > Also, UTF is clearly the future of strings, having native default > support in modern interpreters, editors, etc., and also being critical > to supporting users who aren't using English. Maybe one day Sage will support something like agda-input-method in Emacs :) -Keshav

[sage-devel] Re: New Trac Server

"R. Andrew Ohana" writes: > Ok, everything should be back up and running now. Cool! Bug report: http://trac.tangentspace.org/ doesn't work anymore. If that is intended behavior, then I guess the fact that trac email notifications link to trac.tangentspace.org is correspondingly unintended behav

[sage-devel] Re: The 2013 Spies Prize winner is...

William Stein writes: > Jeroen Demeyer has provided excellent service to the Sage community as > release manager, starting with Version 4.6.1 in January 2011, just > five months after his first code contribution. He has continued to > contribute significant code to the Sage library in the area o

[sage-devel] Re: New doctest continuation ....:

Simon King writes: > On 2013-06-20, kcrisman wrote: >>> the matroids code (#7477) has plenty of examples. Until now I wasn't even >>> aware of the existence of live documentation... but it's incredibly useful! >>> >> >> It is SO useful!!! > > I've never heard of it either. Can you briefly expl

[sage-devel] Re: New doctest continuation ....:

Keshav Kini writes: > Keshav Kini writes: >> Stefan writes: >> >>> I'd ask for p[6:], that's the expected use and consistent with the previous >>> line which tests for '... ' (note the space). >> >> I agree with that - I was j

[sage-devel] Re: New doctest continuation ....:

Keshav Kini writes: > Stefan writes: > >> I'd ask for p[6:], that's the expected use and consistent with the previous >> line which tests for '... ' (note the space). > > I agree with that - I was just miming the .lstrip() after 'sage:' fo

[sage-devel] Re: New doctest continuation ....:

Stefan writes: > I'd ask for p[6:], that's the expected use and consistent with the previous > line which tests for '... ' (note the space). I agree with that - I was just miming the .lstrip() after 'sage:' found in previous lines. I'll fix it. -Keshav -- You received this message because yo

[sage-devel] Re: New doctest continuation ....:

Stefan writes: > The fix should be adding two lines after line 374 of > > https://github.com/sagemath/sagenb/blob/master/sagenb/notebook/docHTMLProcessor.py > > I don't have time to get acquainted with Notebook development right now, or > I'd fix it myself... Like this, I imagine? https://gith

[sage-devel] Re: A file-based Cc in Trac

kcrisman writes: > Personally, I find this very annoying. Maybe we can encourage people > to add something to the comments whenever they update a patch (at > least if they want it reviewed). As a data point, I seem to recall being told to do this at Sage Days 27, when I had only been working wi

[sage-devel] Re: A file-based Cc in Trac

Nathann Cohen writes: > Hellooo everybody !!! > > I just wondered if there was a way (or if there *will* be a way when > we will be using git) to be automatically emailed when a ticket > contains a patch that touches a specific file. Well, with git, if you kept a local mirror of trac's r

[sage-devel] Re: Mirror for 32-bit Ubuntu LTS.

leif writes: > Thierry wrote: >> Hi, >> >> looking at >> http://ask.sagemath.org/question/2582/installing-error-in-linux-mint-13 >> i saw that sagemath.org only distributes 32-bit binaries for Ubuntu >> 13.04. While it is good to have binaries for the last version of ubuntu, >> it could be nice to

[sage-devel] Re: Integer vs. int in python

Volker Braun writes: > Anything that does isinstance(i,int) in the Python standard library > is broken. Usually thats when multiple input types are allowed. In > this case the argument to match.group() could be a string if you use > the ?P syntax to name the match group. Yup. For example the sim

[sage-devel] Re: Reasons for upgrading

Simon King writes: > Does D) really work, currently? If it did, it would be my main reason > for using upgrade, because I find it a pain in the neck to first build > Sage from scratch, then check for each patch in my patch queue whether > it has meanwhile been merged, and import the remaining patc

[sage-devel] Re: New Trac Server

Jeroen Demeyer writes: > On 04/22/2013 09:32 PM, John Cremona wrote: >> I volunteer to be the official red-green colour-blind >> guinea-pig if you point me to a suitable sample page. > Me too by the way. Wait, weren't you the one who decided this color scheme during Sage Days 40.5 last year...? I

[sage-devel] Re: browsing Sage source code

William Stein writes: > On Apr 22, 2013 11:28 AM, "Jeroen Demeyer" wrote: >> As only link or even the default link, I am against this because >> the repo doesn't correspond to Sage. If I would be new to Sage, I >> would find it very confusing that the source code repo doesn't >> correspond to the

[sage-devel] Re: GIT + release management

Jeroen Demeyer writes: > Dear Sage lovers, > > I'm here at the Sage-GIT workshop and it's very clear that the switch > to GIT is happening. > > The current idea is to have Sage 5.9 and Sage 5.10 with the current > Mercurial-based workflow. Hopefully before Sage 5.10, there will > already be a usa

[sage-devel] Re: one test fails because of optional package

John H Palmieri writes: > And after it (between 'atlas...' and 'blas...'), just in case. Maybe > something like > > ['atlas...', ..., 'python...', ...] Another, probably less computationally expensive option:: sage: len(filter( : lambda x: x.startswith('atlas') or x.start

[sage-devel] Re: one test fails because of optional package

leif writes: > kcrisman wrote: >> >> >> On Friday, March 22, 2013 9:21:54 AM UTC-4, Rajeev wrote: >> >> Hi, >> >> The following test fails because I have some optional packages >> installed - >> >> $ sage -t --long -force_lib devel/sage/sage/misc/package.py >> sage -t --long -

[sage-devel] Re: [sage-combinat-devel] Re: Adding data in patch

Simon King writes: > Hi Keshav, > > On 2013-03-22, Keshav Kini wrote: >> Simon King writes: >>> However, if you *are* upstream (i.e., if your data are only published in >>> this form, but not as an independent project), I'd say tracking it with >>

[sage-devel] Re: [sage-combinat-devel] Re: Adding data in patch

Simon King writes: > However, if you *are* upstream (i.e., if your data are only published in > this form, but not as an independent project), I'd say tracking it with > mercural is fine. But perhaps other people have a different viewpoint. Please don't. When we merge all the SPKGs' repositories

[sage-devel] Re: gcd regression (?)

"D. S. McNeil" writes: > I think this is a known issue: see > > http://groups.google.com/d/topic/sage-support/_LvmAECVeDg/discussion Ah, I missed that too - ignore my previous post. Thanks :) -Keshav -- You received this message because you are subscribed to the Google Groups "sage-devel" gro

[sage-devel] Re: gcd regression (?)

kcrisman writes: > This caused an interact in class today to break. Yikes. Why does > this no longer work? > > -- > | Sage Version 5.7.rc0, Release Date: 2013-02-16 > | > | Type "notebook()" for the browser-b

[sage-devel] Spanish speaking reviewer needed

Hi, If there are any Spanish speaking Sage devs who have a little time, could you please review this Spanish translation of the sagenb UI? https://github.com/sagemath/sagenb/pull/133 Thanks, Keshav -- You received this message because you are subscribed to the Google Groups "sage-devel" g

[sage-devel] Re: Notebook localization

v...@ukr.net writes: > Hello! > I have just noticed (accidentally) that there is a Russian interface > for Notebook. Well, that's great, but I didn't know somebody started > the Notebook interface localization. Or have I missed the announcement? > Anyway, I would like to take part in translat

[sage-devel] Re: Installing Sage 5.6

Keshav Kini writes: > Jeroen Demeyer writes: >> On 2013-02-18 10:10, sea21 wrote: >>> It's "ldd (GNU libc) 2.3.3". >> That is an extremely old version, dating back to 2004 (!) > > The Linux kernel version, 2.6.10, is also from 2004 :) I am i

[sage-devel] Re: Installing Sage 5.6

Jeroen Demeyer writes: > On 2013-02-18 10:10, sea21 wrote: >> It's "ldd (GNU libc) 2.3.3". > That is an extremely old version, dating back to 2004 (!) The Linux kernel version, 2.6.10, is also from 2004 :) I am interested to know what distro this might be... -Keshav -- You received this messag

[sage-devel] Re: Shibboleth and Sage ?

Thierry Dumont writes: > Sometime ago, I devopped a small patch to do ldap authentification; > this patch is not very beautiful, it can no more be used with > nowaday's versions of the notebook Well, if you are interested in LDAP, Robin Martinjak has been kindly maintaining a pull request to add

[sage-devel] Re: sage -t Help

Jeroen Demeyer writes: > - set SAGE_ROOT in your ~/.bashrc (or whatever rc file for your shell) Wait, do we still recommend this? I thought this was discouraged, judging from the significant number of people who have had issues starting sage on IRC and then found that unsetting $SAGE_ROOT made ev

[sage-devel] Re: Egg-path error in installing Sage 5.6

Kwankyu Lee writes: > Hi Keshav, > > > I was wondering what could be causing your problem but didn't > comment > because I didn't have a solution. > > > I still don't know exactly what caused the problem, but I suspect the > notebook files stored under ~/.sage was somehow out of date a

[sage-devel] Re: 32-bit testing

John Cremona writes: > 32-bit machines are getting rarer, but still exist -- e.g. my 2008 > laptop! Is there a 32-bit testing platform we can access at sagemath, > skynet or similar? There is arando, the 32-bit Ubuntu 12.04 buildbot running at Nanyang Technological University and administered by

[sage-devel] Re: Egg-path error in installing Sage 5.6

Kwankyu Lee writes: > I solved the problem by moving out the ".sage" folder. Thanks for all > your attention! I was wondering what could be causing your problem but didn't comment because I didn't have a solution. Could you elaborate on how you fixed it? What was your current directory, where was

[sage-devel] Re: Python 3 formatting

Robert Bradshaw writes: > (4) Perhaps I could configure things differently, but littering my > directory with reject files when things don't apply cleanly vs. git's > inline > > << OLD > ... > > ... >>> NEW > > is so much easier to deal with (as well as being a lot safer in making

[sage-devel] Re: Should sage -b run sage -sync-build to get rid of outdated .py and .pyc files?

Robert Bradshaw writes: > On Thu, Jan 31, 2013 at 7:29 PM, Keshav Kini wrote: >> But an import statement succeeding when it shouldn't *is* something >> going wrong - it is exactly the kind of problem which is caused by not >> doing `sage --sync-build` after running `

[sage-devel] Re: Python 3 formatting

Harald Schilly writes: > On Thu, Jan 31, 2013 at 11:00 AM, Jeroen Demeyer < > jdeme...@cage.ugent.be> wrote: > > On 2013-01-31 10:58, Volker Braun wrote: > > commit hook > What's that? > > > For an hg/git commit, a script is called prior to actually doing the > commit. if its exit code

[sage-devel] Re: Should sage -b run sage -sync-build to get rid of outdated .py and .pyc files?

Dima Pasechnik writes: > On 2013-01-31, Keshav Kini wrote: >> Dima Pasechnik writes: >>> On 2013-01-23, Robert Bradshaw wrote: >>>> On Tue, Jan 22, 2013 at 9:53 PM, tom d wrote: >>>>> Another possible solution would be to change the error mes

[sage-devel] Re: Should sage -b run sage -sync-build to get rid of outdated .py and .pyc files?

Dima Pasechnik writes: > On 2013-01-23, Robert Bradshaw wrote: >> On Tue, Jan 22, 2013 at 9:53 PM, tom d wrote: >>> Another possible solution would be to change the error message one gets on a >>> failed import statement. (I also lost hair on this issue a couple days >>> ago.) Right now it say

[sage-devel] Re: Python 3 formatting

William Stein writes: > I remember adding code that used "with" to Sage back in I think 2008 > when working on generators for the coercion model. We've been using > with for a long time. Sure. In general the newer pieces of code in Sage do tend to use more modern Python than older pieces of code

[sage-devel] Re: Python 3 formatting

Travis Scrimshaw writes: > Hey everyone, >Should we be encouraging (or enforce) new code to be python 3 > compliant? In particular, not using removed syntax such as exceptions > as `raise ExceptionType, args` or `<>` comparisons? Encouraging, yes; enforcing, I'd say no. I don't think a Python

[sage-devel] Re: git integration repository, please test

Dima Pasechnik writes: > On 2013-01-17, Robert Bradshaw wrote: >> On Wed, Jan 16, 2013 at 11:17 PM, Dima Pasechnik wrote: >>> On 2013-01-17, Robert Bradshaw wrote: On Wed, Jan 16, 2013 at 6:13 PM, Dima Pasechnik wrote: > On 2013-01-16, Volker Braun wrote: >> --=_Part_588_629

[sage-devel] Re: git integration repository, please test

Dima Pasechnik writes: >> Expanding on http://wiki.sagemath.org/WorkflowSEP one would have >> >> sage_root/ >> sage # the binary >> Makefile # top level Makefile >> (configure) # perhaps, eventually >> ... # other standard top level files (README, etc.) >>

[sage-devel] Re: git integration repository, please test

Michael Orlitzky writes: > For the *really* messed-up packages, we would keep the ebuilds in an > overlay and do whatever we want with them there. And over time, > hopefully fix them and send those fixes upstream. Well, this is pretty much what the sage-on-gentoo overlay does :) http://github.co

[sage-devel] Re: Patch made from a previous version of sage

Kannappan Sampath writes: > Hello friends,  > > I have the following question: The patch here: > > http://trac.sagemath.org/sage_trac/ticket/10080 > > seems to come from a previous version of the file for which it > proposes some change. Now, apparently, I feel that some of the issues > have been

[sage-devel] Re: git integration repository, please test

kcrisman writes: > On Tuesday, January 15, 2013 10:19:45 PM UTC-5, Michael Orlitzky > wrote: > > On 01/15/2013 10:17 PM, Michael Orlitzky wrote: > > FreeBSD: pkg install subversion > > ... > > Just went insane for a second there =) > > > Actually, we DO have a FreeBSD port, tha

[sage-devel] Re: Evolve extension in hg: almost ready for use

Jordi Gutiérrez Hermoso writes: >> Also, is there a specific feature of Evolve that would greatly >> benefit Sage's development? > > Evolve is directly targetting to replace MQ usage. For Sage users > already used to MQ, they can use Evolve as a direct replacement for MQ > without having to learn

[sage-devel] Re: Why does - (x > 100) return -x > -100 ?

Benjamin Jones writes: > On Mon, Jan 7, 2013 at 10:53 AM, Keshav Kini wrote: >> Benjamin Jones writes: >>> sage: y = var('y') >>> sage: x * (y > 0) >>> x*y > 0 >>> >>> Just like applying the operator (x*_) over a list [ y, 0

[sage-devel] Re: hg.sagemath.org oddity

I posted about this a few weeks ago. Turns out the problem is that the Mercurial version on boxen is too old. Also it's not clear to me how the repositories there are updated. To copy from my conversation with Minh: On Thu, Dec 6, 2012 at 12:19 AM, Keshav Kini wrote: > Looks like the

[sage-devel] Re: Why does - (x > 100) return -x > -100 ?

Benjamin Jones writes: > On Mon, Dec 17, 2012 at 9:32 PM, P Purkayastha > wrote: > > On 12/18/2012 10:10 AM, Benjamin Jones wrote: > > if y > 0 is true, > is x*(y > 0) true or false? > > > Why is this kind of operation (+,-,*, etc) distributive over > comp

[sage-devel] Re: why is email in sagenb?

William Stein writes: > Yes, unless it's needed by the notebook for some reason, in which case > we have to have two copies, since the notebook is supposed to not > depend on sage... Note: Robin Martinjak recently submitted a pull request to sagenb implementing email notifications for sagenb err

Re: [sage-devel] hg.sagemath.org server error

On Wed, Dec 5, 2012 at 11:19 PM, Minh Nguyen wrote: > Hi Keshav, > > On Sat, Dec 1, 2012 at 8:57 AM, Keshav Kini wrote: >> The sage-root repo seemingly isn't being served correctly, as the >> following URL returns an HTTP 500: >> >> http://hg.sagemath.org/s

[sage-devel] Re: Can not run notebook on sage-5.5rc0

kcrisman writes: > While mistyping this, I discovered that a lot of ticket "do not > exist". E.g. http://trac.sagemath.org/sage_trac/ticket/11044 and > many, many others. Why? Presumably not because they are > duplicates. Didn't we at some point have spam tickets that got outright deleted? I

[sage-devel] Re: Normalization of a vector

Kannappan Sampath writes: > Perhaps, I should explain my rationale for the terms I chose, my > first preference is `echelonize(v)`  (although I wrote it second) > because, what the function returns amounts to its reduced row echelon > form, if you think of it as 1 x n matrix.  My rationale for "m

[sage-devel] Re: Normalization of a vector

Kannappan Sampath writes: > Here's a "natural" place where I can see this is helpful:  > > To carry out, Gauss-Jordan like row reductions, where you'd like the > first non-zero entry in a row (the so-called pivot) to be 1, I think > this is very helpful. > > So, I'd be **for** keeping this, perhap

[sage-devel] hg.sagemath.org server error

Hi, The sage-root repo seemingly isn't being served correctly, as the following URL returns an HTTP 500: http://hg.sagemath.org/sage-root/ -Keshav -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@g

[sage-devel] Re: License issues if linking Mathematica and Sage

David Kirkby writes: > Sage > > http://www.sagemath.org/ > > is an open-source mathematical package released under the GPL version > 2, or if the user wishes, any later version of the GPL. Well, according to William as of October 2011 in an email to me: > The complete Sage distribution is GPLv3

[sage-devel] Re: How do you remove attachments that become irrelevant at some point from a trac ticket?

kcrisman writes: > On Thursday, November 29, 2012 7:41:46 AM UTC-5, kannappan sampath > wrote: > > Hello, > I wanted to ask the mailing list if there is a way to remove > attachments that become irrelevant, either due to a completely > new patch or a patch that coalesces all the p

[sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

Robert Bradshaw writes: > On Tue, Nov 27, 2012 at 10:51 AM, Jason Grout > wrote: >> On 11/24/12 7:41 PM, Robert Bradshaw wrote: >> >>> Cool. (The doable part, not the unholy mess part :-). If that's the >>> case, how about we simply ignore the issue at the moment, remove it >>> all in the git con

[sage-devel] Re: What to do with research-y code.

Robert Bradshaw writes: > On Mon, Nov 26, 2012 at 9:46 AM, kcrisman wrote: >> In sage-combinat, >> again, the queue seems to solve this, and there is a lot of impressive >> teamwork. > > Yes, and I think it'd be really interesting to get one of them to > understand outline their goals (and how we

[sage-devel] Re: What to do with research-y code.

Robert Bradshaw writes: > Another crazy idea: encourage uploading of unfinished code with > optional nag reminders. I'd rather people upload code without tests > and people start reviewing it than hold onto it until they "get around > to" adding all the examples. Just having public "todo" lists ca

[sage-devel] Re: What to do with research-y code.

William Stein writes: > On Mon, Nov 26, 2012 at 11:48 PM, Burcin Erocal wrote: >>Package dependencies for optional/experimental packages is beyond >>the capabilities of the sage packaging system. Adding >>"sage -i " commands to spkg-install is a very ugly >>hack. > > What's the si

[sage-devel] Re: which letter to use for the universal cyclotomics ?

Volker Braun writes: > But again that does nothing to help discover the functionality. When > I first used cyclotomics in Sage I tried E(3) first, but clearly that > didn't work. Well, you said yourself that if you're not a GAP user then E() will not be intuitive. What percentage of Sage users ar

[sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

Volker Braun writes: > On Sunday, November 25, 2012 7:30:21 PM UTC, Keshav Kini wrote: > > Yup. (The latter would of course be better.) But it would be on > everyone's local sage install, not on trac or in the release > management > scripts :) > >

[sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

Ivan Andrus writes: > On Nov 25, 2012, at 1:01 AM, Keshav Kini wrote: > >> Travis Scrimshaw writes: >>> Hey, >>> I'd be happy with A), but perhaps we could have an option D) where >>> when we upload (or merge) patches into sage, we automaticall

[sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

Robert Bradshaw writes: > On Fri, Nov 23, 2012 at 12:23 PM, Volker Braun wrote: >> b) misguides people writing patches into making unnecessary whitespace >> changes ("trailing whitespace is bad, hence I'll take it out everywhere") >> >> Its confusing and slows us down with no real benefit. > > Th

[sage-devel] Re: upgrading sage while working on patches

Charles Bouillaguet writes: > Hi all, > > I just tried to upgrade from 5.4 to 5.4.1, and it worked. > > However, the upgrade process interacts bizarrely with mercurial's > patch queue. I had a non-empty patch queue, and applied the upgrade. > But now, all the upgraded files appear as "uncommitted

[sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

Ivan Andrus writes: > I disagree. Perhaps I am alone in this, but I often (used to) move > to the end of the line, go back a few characters (to get inside > parenthesis or something), and start typing. If there is trailing > whitespace that I didn't know about I would be extremely annoyed > beca

[sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

Travis Scrimshaw writes: > Hey, >I'd be happy with A), but perhaps we could have an option D) where > when we upload (or merge) patches into sage, we automatically strip > all whitespace in the patch file? This will get nasty once we stop using patch files and switch to git. Commits should no

[sage-devel] Re: Line continuations in doctests, changing files in sage/tests

David Roe writes: > Hi everyone, > I'm working on #12415 and am revising the methods for continuing > lines.  Currently you can continue a line with the standard python > ..., which looks good in standard Python doctests since it has the > same length as >>>, but doesn't look at nice in Sage.  Af

[sage-devel] Re: Indexing of symbolic expressions

Jason Grout writes: > On 11/5/12 7:40 PM, Michael Orlitzky wrote: >> I didn't realize foo[1,2] would pass the tuple (1,2) to __getitem__ >> until the very end, so it would make sense to go back and replace the >> function calls with indexing. >> >> I think the only thing we'd lose is a() -> 'a', a

[sage-devel] Re: achieving 90% coverage

Volker Braun writes: > Incidentally, about the legacy code for loading old notebooks: here > is one lesson to be learned about long-term support of data files. > The only sane way to handle this imho is: > > * The current code can read/write the current data format > * Whenever you upgrade from fo

[sage-devel] Re: Ascii Output

David Roe writes: > Maxima will use ascii-art to print expressions (http:// > www.sagemath.org/doc/reference/sage/interfaces/maxima.html), but it > will just leave sqrt as sqrt.  I don't know a way to get an ascii art > representation for sqrt. > David Sympy does this:: sage: from sympy impo

[sage-devel] Re: ARM box?

Christopher Swenson writes: > Raspberry Pi? No, a Trim-Slice H250: http://thread.gmane.org/gmane.comp.mathematics.sage.devel/58670/focus=58749 -Keshav Join us in #sagemath on irc.freenode.net ! -- You received this message because you are subscribed to the Google Groups "sage-devel" g

[sage-devel] Re: CTRL-C crashes the notebook in 5.3

Daniel Smertnig writes: > AFAIK the only reason 5.3 shipped with pyOpenSSL 0.12 was that 0.13 > has problem with older OpenSSL versions (<0.9.8f or something). This > is not an issue on Ubuntu, so pyOpenSSL 0.13 should be safe to use. > Of course, if you don't upgrade, the SSL notebook will not wo

[sage-devel] Re: Sage 5.2 fails to build

P Purkayastha writes: > https://groups.google.com/forum/?fromgroups=#!topic/sage-devel/q9_Mn3f467g Note that this will no longer be necessary in 5.4 once #13385 gets in. -Keshav Join us in #sagemath on irc.freenode.net ! -- You received this message because you are subscribed to the Go

[sage-devel] Re: sign of permutations

Kwankyu Lee writes: > Signature means to me a hand-written name. Well, there are other valid mathematical or CS meanings to "signature". I agree that this one should be "sign", though. -Keshav Join us in #sagemath on irc.freenode.net ! -- You received this message because you are subscri

[sage-devel] Re: Need developer account on OSX 10.4 PPC (or remove from supported platforms)

Volker Braun writes: > I was hoping for something more reliable than a one-time ssh tunnel. Our 32-bit Ubuntu 12.04 buildbot, arando, is set up via ssh tunnels. On boot I log in and run a script which keeps up a reverse tunnel to sage.math, so you can generally ssh to arando from sage.math by co

[sage-devel] Re: Need developer account on OSX 10.4 PPC (or remove from supported platforms)

"Georg S. Weber" writes: > On Sunday, 2 September 2012 12:50:22 UTC+2, Volker Braun wrote: > > Something in our OSX 10.4 build uses the reference blas instead > of the accelerate framework. See http://trac.sagemath.org/10508 > for some heroic efforts by Karl-Dieter to debug this by wor

[sage-devel] Re: How do I specify location of openssl headers?

David Kirkby writes: > On 2 September 2012 01:08, John H Palmieri wrote: >> >> On Saturday, September 1, 2012 3:22:21 PM UTC-7, Dr. David Kirkby wrote: >>> >>> I'm trying to build Sage on Solaris 10 (March 2005 edition), which has >>> worked many times before. > > I should have said this was SPAR

[sage-devel] Re: creating a local patch

Julien Puydt writes: > Le 31/08/2012 00:19, Robert Bradshaw a écrit : >> On Thu, Aug 30, 2012 at 12:17 PM, David Roe wrote: What in particular was bothersome about github? > >> Issue-tracking in particular is sub-par on github (though I've heard >> they've been working on this), and having t

[sage-devel] Re: creating a local patch

Jason Grout writes: > On 8/30/12 1:10 PM, Julien Puydt wrote: >> Le 30/08/2012 19:51, Jason Grout a écrit : >>> If/when we move to github or to bitbucket or something, where people can >>> easily push their own branches, it will be much more natural to push >>> your in-progress code up and collabo

[sage-devel] Re: Proposal: Remove GNUTLS from Sage.

fero writes: > IMHO gnutls should be removed from SAGE if it is just used for > notebook secure=True to provide https connection, > because this argument could be relegated to the deployment > enivronment which should be in care of sysadmins that deploy > SAGE notebook somewhere. See trac #13392

[sage-devel] Re: sagemath cluster

William Stein writes: > Incidentally, I've been investing in setting this up recently: http://salv.us > So far I've written very little notebook-style code, but I've done a > lot of work on basic scalable infrastructure. The initial release > will probably be like a very stripped down version of

[sage-devel] Re: Proposal: Remove GNUTLS from Sage.

Keshav Kini writes: > I made this #13385 - http://trac.sagemath.org/sage_trac/ticket/13385 There's now also a pull request on github for removing the pyOpenSSL dependency from sagenb: https://github.com/sagemath/sagenb/pull/95 Anyone want to review it real quick? +22/-6 diff.

[sage-devel] Re: one doctest fails on ubuntu 12.04

Rajeev Singh writes: > I have compiled sage-5.2 on ubuntu 12.04. The following test fails - > > sage -t --long -force_lib > "devel/sage/sage/modular/modform/find_generators.py" > > There was a segmentation fault. Can you rerun that particular file and attach or pastebin the output, so we c

[sage-devel] Re: Proposal: Remove GNUTLS from Sage.

Keshav Kini writes: > If this is still your view, it seems to me that we can probably even get > rid of the OpenSSL headers dependency which has been causing users so > much trouble since 5.2 was released. We can just stop packaging > pyOpenSSL with the sagenb SPKG, and instead requi

  1   2   3   4   5   6   7   >