[sage-devel] Scalability of the rich output supported types list

Hi! In http://trac.sagemath.org/ticket/7298 (on HTML5 for animations) and some other tickets I'm currently dealing with the effects of the rich output framework introduced by Volker in http://trac.sagemath.org/ticket/17234. I've some concerns about the scalability of this approach, and would

[sage-devel] Avoid assignment to numeric literals after preparse

Hi! http://trac.sagemath.org/ticket/11542 deals with the fact that in preparsed code, assigments to numeric literals will not cause syntax errors since the literals get replaced by variables which are assumed to be constants but which are not constant in this scenario. I've got a branch attache

Re: [sage-devel] Re: How to save an animation

On Tuesday, April 14, 2015 at 9:21:22 PM UTC+2, Volker Braun wrote: > > The output type control for "show" should be more about what the user > wants to achieve, not the technical minutiae of file type that can achieve > it. That is, "show" should be more about raster vs. vector graphics, lossy

Re: [sage-devel] How to save an animation

Thanks for your input! On Tuesday, April 14, 2015 at 6:11:01 PM UTC+2, William wrote: > > I vote for 3, which is the situation with 2d graphics for the last *9 > years*, and isn't it the current situation with animations right now. > I'm not sure why you don't clearly say for this poll what th

[sage-devel] Deprecate or just remove

Hi! The deprecation guideline reads: “Before removing any functionality, you should keep a deprecation warning in place for at least one year (if possible).” To me, “any functionality” means just that: any functionality,

[sage-devel] How to save an animation

Hi! This is a quick poll, triggered by comment 50 of ticket 7298 and also comment 17 of ticket 18176 . How would you like to create and save an animation using Sage. Options (perhaps presented i

[sage-devel] Re: [sage-support] Re: Whats wrong with my function syntax?

On Thu, Apr 2, 2015 at 7:02 AM, kcrisman > wrote: > Interesting idea, though what if it was intended in something, such as a > plot legend? > Perhaps we could run such substitutions at a time where strings have been removed from the code during preparse. The preparser works by stripping st

[sage-devel] Re: reducing upstream tarballs in a reproducible way

On Monday, January 12, 2015 at 11:59:53 AM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > > Another mid-term compromise could be to strip some few upstream source, > but in a checkable and reproducible manner, that is, with a spkg-src > script that will produce deterministic tarballs, so that an

[sage-devel] self in the INPUT section of the docstring

Hello. This post is motivated by #17567 . There I implemented a method which is only defined for vectors of length 3 and 7. I felt like documenting the fact “self has to be length 3 or 7” in the INPUT section of the docstring would be a good ide

[sage-devel] Re: trac milestone

On Friday, November 14, 2014 at 7:25:09 PM UTC+1, kcrisman wrote: > I meant that some people suggested making no milestone the default. I'm > not sure what I think about that, I can see pros and cons. > I'd vote for no milestone by default. As it currently is, I feel like my tickets opened fo

[sage-devel] dict with key coercion

Hi! There are several places in sage where some operation returns a dictionary, and the values of the dictionary all come from a single category. In some places, that category is less than obvious. Example: sage: R. = PolynomialRing(QQ, order='lex') sage: I = R.ideal(c^2-2, b-c, a) sage: v = I.

[sage-devel] Re: The Sage dev scripts

Hadn't known of git-trac before. Since the tool has some sage settings hard-wired into it, perhaps it should be called git-sage instead, to avoid clashes? Recently I've been using git the hard way for pretty much everything except pushing, for which I used "./sage -dev push --ticket" in the hop

Re: [sage-devel] Re: Checking whether a Parent models the real field

On Friday, December 19, 2014 10:25:26 AM UTC+1, John Cremona wrote: > > It's quite possible that both of those were written by me, since I did > write code which had to distinguish between real and complex places. The > number of different "real fields" which people might use is rather large, >

Re: [sage-devel] Re: Checking whether a Parent models the real field

On Tuesday, December 16, 2014 11:14:35 PM UTC+1, Jeroen Demeyer wrote: > > > However, I wonder if there is a more elegant solution: is > > there currently a way to determine whether a given Parent class > models > > the real numbers, such that code like the above could be replaced >

[sage-devel] Re: Doctest granularity for private methods

On Wednesday, July 16, 2014 4:39:39 PM UTC+2, Volker Braun wrote: > > For better or worse, the decision is to doctest every method. > Have there been any discussions about using tools like coverage.py to ensure actual coverage of actually executable code

[sage-devel] Re: Doctest granularity for private methods

On Wednesday, July 16, 2014 4:39:39 PM UTC+2, Volker Braun wrote: > > Doctests are also part of the documentation that you see when you inspect > the method, not only when you read the source. > But these methods are private. They start with an underscore, so they are not included in the generat

[sage-devel] Doctest granularity for private methods

In #16571 I'm discussing doctests for a new class, and would like broader input from you all. Suppose I have a class with a bunch of private methods. These methods call one another, set internal state, and in general are tightly interwoven. Writing doctes

[sage-devel] Reviewer wanted for animate and qqbar

Hi! I've been fairly busy these past few days, and come up with quite a large number of tickets which are currently in need of review. The majority of them is for the animate module, with second place to the qqbar module. I would be really happy if someone could have a look at some of the items

[sage-devel] How to obtain the sources

Hi! Reading the dev guide at http://sagemath.org/doc/developer/, I find that I'm missing a relevant piece of information: how to obtain the sources and start using all these commands in the first place. For most packages, I use a binary installation (compiled from source since I'm on Gentoo, b

[sage-devel] Re: Towards git development

I guess I found the documentation I had been expecting: http://trac.sagemath.org/wiki/QuickStartSageGit Makes me realize that “master” isn't the same as “public/sage-git/master”, so it seems I was using the wrong branch. I'm doing things by the book now, and everything looks good so far. I also

[sage-devel] Towards git development

I'm still trying to come to grips with the transition to git. I hear about it in this threadand now wanted to use it for a requested rebase . Here is what I did: 1. Checked out

[sage-devel] Re: Walk-through impressions and mercurial workflow

On Tuesday, July 30, 2013 6:16:48 PM UTC+2, Volker Braun wrote: > > We are in the process of updating the developer guide for the new git > workflow. The current state is here: > > http://sagemath.github.io/git-developer-guide/ > > Help is of course welcome, the github project page is here: > htt

Re: [sage-devel] Walk-through impressions and mercurial workflow

After writing my post, while skimming some other headers here in this group, I found http://wiki.sagemath.org/WorkflowSEP. So now I'm somewhat aware, but I wasn't before. Thanks for pointing this out. -- You received this message because you are subscribed to the Google Groups "sage-devel" gro

[sage-devel] Walk-through impressions and mercurial workflow

After using sage for quite some time, and contributing some input to the sage-on-gentoo project, I finally decided to get my hands dirty and tackle some annyoing bugs in sage itself, #14403 in particular. In the process, I used the Dev Walk-Through at http://www.sagemath.org/doc/developer/walk_t