Re: [sage-devel] Re: Trac reports

> One request: can we have a query for "Tickets I authored (including > closed)", and similarly "Tickets reviewed by me"? (For me "All my tickets > (including closed)" brings up over 500 tickets, but the vast majority of > those are ones where I just made one trivial comment or metadata > correctio

Re: [sage-devel] Re: Trac reports

I've removed 500984 unauthenticated accounts. We're getting about one more each minute; Tom is looking at server logs. Unfortunately, this doesn't seem to resolve the slowness of the users page. David On Thu, Mar 22, 2012 at 02:58, Maarten Derickx wrote: > I'm for removing these accounts. Hopef

[sage-devel] Experimental Trac Server

Andrew Ohana and I have created http://trac.sagemath.org/experimental/ as a place to experiment with Trac Plugins (and eventually using a git repository). Changes to tickets, attachments, etc can be made to either the experimental or the normal trac server: they share the same database and attachm

Re: [sage-devel] Re: Experimental Trac Server

Yeah, we're messing with Code Comments. Did you get that failure on experimental, or on sage_trac? David On Fri, Mar 23, 2012 at 00:52, Jason Grout wrote: > On 3/23/12 2:40 AM, David Roe wrote: > >> Andrew Ohana and I have created >> http://trac.sagemath.o

Re: [sage-devel] Re: Experimental Trac Server

Cool. Things should be working now: you should be able to create a ticket on experimental without getting the error. David On Fri, Mar 23, 2012 at 01:10, Jason Grout wrote: > On 3/23/12 4:01 AM, David Roe wrote: > >> Yeah, we're messing with Code Comments. Did you ge

Re: [sage-devel] Re: Trac reports

> > Is there a report that lists "tickets needing work that I *attached a > patch to*"? > These are now reports 84 and 85 (sorted by time and component respectively). David -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sa

Re: [sage-devel] categories and element classes

Elements are supposed to inherit from their category's element_class, but this requirement is waived for elements that are implemented in Cython. See the following snippet from sage.structure.element.Element._test_category (line 495 of element.pyx): # Tests that self inherits methods from

Re: [sage-devel] is_PrimeField error

Ah ha! Apparently that function is not used anywhere in Sage. It's just a typo: it should be "from finite_rings.constructor import is_FiniteField. Want to practice your new developer skills by opening a ticket and submitting a patch? I'll review it David On Mon, Mar 26, 2012 at 02:41, Ben

Re: [sage-devel] Re: Deprecated is_AlgebraElement function

> More importantly, what happens if coercion etc. fails? Will Sage then > potentially make false mathematical statements, or raise an > exception / return "unknown" or "undecidable" etc. No. It catches the ValueErrors and TypeErrors, and returns False (so ZZ['x'].gen() is not in QQ). David --

Re: [sage-devel] Deleting depreciated is_functions

How much are these functions used in the Sage library? I would be supportive of removing them all if possible David On Tue, Mar 27, 2012 at 18:29, Starx wrote: > This discussion stems from: > > http://groups.google.com/group/sage-devel/browse_thread/thread/979bdce4e002cd05/e8061b2ff21a4cdf?

Re: [sage-devel] Call for vote: remove MoinMoin?

> On Tue, Mar 27, 2012 at 6:10 PM, John H Palmieri > wrote: > > This topic has been brought up here before as side notes in various > threads, > > but I'd like to discuss it more officially: > > > > Should we remove MoinMoin as a standard package? > [X] Yes [ ] No > If "yes", I'm assuming we

Re: [sage-devel] Re: Deleting depreciated is_functions

I think the idea was that if you cared about speed you would just use Fields(), but that it wasn't an important point in discussing whether QQ in Fields should be valid. David On Thu, Mar 29, 2012 at 09:06, Simon King wrote: > Hi Florent! > > On 2012-03-28, Florent Hivert wrote: > >> For parame

Re: [sage-devel] Witt vectors

There are a few places I would suggest looking: Simon King's worksheet at http://flask.sagenb.org/home/pub/82/ and the Sage Reference manual section on coercion at http://www.sagemath.org/doc/reference/coercion.html. I am starting to work to implement Witt vectors in Sage. I think I > have most

Re: [sage-devel] Re: Physical constants

I'm confused by what you mean by "error propagation class." Should you just inherit from Exception, ValueError, etc? David On Fri, Mar 30, 2012 at 03:17, Eviatar wrote: > Hello, > > I'm working on implementing an error propagation class, which is quite > easy. However, the type system/coercion

Re: [sage-devel] which sage should i download for evaluation purposes on Snow Leopard?

You can't run a 64-bit build on a 32-bit machine. I don't think that there's a pre-build binary for 32-bit Snow Leopard, so you'll need to build it from source. David On Wed, Apr 4, 2012 at 10:03, Anthony Durity wrote: > Hi Sage people, > > Scenario: clean install > > I have the sage-4.8-OSX-64b

Re: [sage-devel] Benchmarks for sage...

> Starting with the huge work of Simon, an in depth optimization of the > infrastructure of Sage is under way (Categories, Caching...). I'd like to > be > able to measure somehow the benefits for the end user. Unfortunately right > now > there is no systematic way to measure the variation of speed

Re: [sage-devel] Broken links in Doc

I assume there's no way to automatically add only those private functions that are referred to within Sphinx? If not, I think having "_included_private_doc_" class attribute as a list of strings giving the private functions to include sounds like a fine solution. David On Sun, Apr 8, 2012 at 11:2

Re: [sage-devel] Re: Broken links in Doc

I agree that it would be nice if __*__ and _*_ showed up in the documentation. David On Mon, Apr 9, 2012 at 14:00, Andrey Novoseltsev wrote: > > > On Apr 9, 2:51 pm, "Nicolas M. Thiery" > wrote: > > On Mon, Apr 09, 2012 at 10:06:32AM -0700, Andrey Novoseltsev wrote: > > > I think "_included_pri

Re: [sage-devel] Re: working on animation for 3d objects

I think it's fine to change it, since we actively discourage users from using is_* functions outside of library code. David On Mon, Apr 9, 2012 at 17:42, Niles Johnson wrote: > > On Monday, April 9, 2012 5:02:45 PM UTC-4, Niles Johnson wrote: >> >> But I haven't found a Trac ticket for it -- cou

[sage-devel] Including pari and znpoly in the same file

I'm working on some p-adic modular symbols code, and am writing a file that uses zn_poly. Unfortunately, when I try to compile, I get the following error from gcc: $SAGE_ROOT/local/include/zn_poly/zn_poly.h:72: error: redefinition of typedef 'pari_ulong' $SAGE_ROOT/local/include/pari/parigen.h:19

Re: [sage-devel] Including pari and znpoly in the same file

ry.ac.nz> wrote: > On Tue, 17 Apr 2012 16:56:52 David Roe wrote: > > I'm working on some p-adic modular symbols code, and am writing a file > that > > uses zn_poly. Unfortunately, when I try to compile, I get the following > > error from gcc: > > > >

Re: [sage-devel] Re: Including pari and znpoly in the same file

That would be great. David On Thu, Apr 19, 2012 at 13:27, leif wrote: > On 17 Apr., 23:30, David Roe wrote: > > Patching zn_poly in Sage sounds good to me > > I could include such a patch into the zn_poly spkg at > > http://trac.sagemath.org/sage_trac/ticket/12433 >

Re: [sage-devel] Re: Created "plotting" component on Trac

I can probably do it, if we decide on a list of changes we want to make. David On Thu, Apr 19, 2012 at 13:44, leif wrote: > On 19 Apr., 22:34, Jeroen Demeyer wrote: > > On 2012-04-19 21:05, leif wrote: > > Can you rename the porting "subcomponents" as suggested? > > > > No, but maybe somebody w

Re: [sage-devel] trac bug?

I've seen this as well, but I don't know what causes it. David On Sat, Apr 21, 2012 at 04:13, John Cremona wrote: > After some recent changes in the trac version we use (I think) I find > the following, but only when I use it with chromium on my small-screen > netbook: The text box into which o

Re: [sage-devel] Artithmetics in p-adic extensions?

Sage currently supports arithmetic in totally ramified p-adic extensions defined by an Eisenstein polynomial. There is progress in more general extensions in the last few months, but I've been really busy with other projects as well. What kind of extensions do you need? David On Tue, Apr 24, 201

Re: [sage-devel] ticket #12068 : normalizing rational expressions

So we need an updated GiNaC spkg? If nothing else can you wrap the call to GiNaC with a sig_on() / sig_off() so that you can Ctl-C? David On Fri, Apr 27, 2012 at 21:23, Ben Goodrich wrote: > Hi, > > The patches attached to ticket #12068 (Numerator for symbolic expression > shouldn't use maxima)

Re: [sage-devel] Re: Help with detecting "glibc detected"

For what it's worth, I'm working on allowing debugging to initiated from within doctesting. But it's not ready yet. I'm stuck on the redirection of standard out; I've started another thread to see if anyone has ideas. David On Thu, May 3, 2012 at 3:10 PM, Simon King wrote: > Hi Martin, > > On

Re: [sage-devel] Some images are not shown in tutorial

I don't see the images either. I'm not sure where in the documentation a needs to be inserted though David On Wed, May 2, 2012 at 1:54 AM, Nicu Tofan wrote: > Hi, again! > > I have a virtual machine running XP and Chrome shows same behaviour. It's > "console" does not report any error rela

Re: [sage-devel] weird difference in performance

> Yep. Since this is such a common case, I wonder if we should modify > the Sage integer __richcmp__ method to be more sophisticated, and > allow direct comparisons with builtin Python types, without first > requiring them to be converted to Sage integers? That's such a good idea that I did it. h

Re: [sage-devel] Re: weird difference in performance

I think that while we're still using Python 2.x, where 2r/3r = 0, we absolutely need the preparser. The coercion framework can work with Python ints just fine: it's the automatic rounding that kills us. Much better speed for large integers is another benefit that you mentioned. Also, there are l

Re: [sage-devel] CompositConstructionFunctor [sic]

Seems fine to me. David On Wed, Nov 24, 2010 at 10:16, John Cremona wrote: > In reviewing #8807 I spotted what looked like a typo: > "CompositConstructionFunctor". But in fact that is the way this class > name is defined. There are many occurrences of this, almost all in > categories/pushout.p

[sage-devel] sage-padics mailing list

I've created a mailing list for working on p-adics in Sage, and more generally polynomials, matrices and modules over local rings (such as p-adics and power series rings). http://groups.google.com/group/sage-padics You can apply to join on that website, or e-mail me and I'll add you (in case you

[sage-devel] Cython elements and categories

Xavier Caruso and I are trying to implement some methods on matrices by using the category code. I think some of the functions in matrix2.py should get moved to categories, but that's a topic for another day... For now, we're trying to implement smith_form for matrices over certain kinds of base

Re: [sage-devel] When is a test not a valid test?

I disagree that doctests should need to be independently verified. Of course, if we had an arbitrarily large amount of time to write doctests, then it would be a laudible goal. Even now, I think there are situations where it would be reasonable to ask this of the author of a patch: if there was s

Re: [sage-devel] When is a test not a valid test?

> > So you admit it would improve stage to check the tests. > Of course. My argument is that imposing the requirement to have such consistency checks in order to get a positive review will make me less likely to contribute to Sage. If you are going to give an example, how much longer does it tak

Re: [sage-devel] Re: Buildbot - does not seem to get much use

That's awesome. This will make me far more likely to review tickets. David On Fri, Dec 3, 2010 at 04:08, Robert Bradshaw wrote: > On Thu, Dec 2, 2010 at 7:00 PM, kcrisman wrote: > > > >> > I completely agree. And with quick, automated feedback they can go and > >> > take care of anything they m

Re: [sage-devel] Re: Buildbot - does not seem to get much use

ise_log_name, "w") as concise_log: concise_log.write(clog) On Fri, Dec 3, 2010 at 09:47, David Roe wrote: > That's awesome. This will make me far more likely to review tickets. > David > > > On Fri, Dec 3, 2010 at 04:08, Robert Bradshaw < > rober...@m

Re: [sage-devel] Re: How is comparison implemented in Cython?

See #10130. I have some more work on that ticket beyond what I posted, but it's pretty widespread throughout the Sage library. I think the right approach may be to set up a framework to do the shift gradually, as we eventually did for coercion. David On Fri, Dec 10, 2010 at 16:13, Simon King wr

Re: [sage-devel] diagonal_matrix and numpy arrays

Yep. It's just something that hasn't been implemented yet. David On Tue, Dec 14, 2010 at 07:18, Dan Drake wrote: > diagonal_matrix() does not seem smart enough to deal with 1-dimensional > numpy arrays: > > sage: s > array([ 7.10977223,  2.10977223]) > > Both values are numpy floats: > > sage: [

Re: [sage-devel] Re: Listing infinite sets using never-ending iterators

+1 On Wed, Dec 15, 2010 at 00:55, Simon King wrote: > On 15 Dez., 01:55, Robert Bradshaw > wrote: >> I would strongly object to removing the ability to iterate over >> infinite sets, sometimes it's very useful to iterate until something >> is found, or to grab a certain number of elements. > > +

Re: [sage-devel] Proposal for new trac component: scripts

+1 On Sat, Dec 18, 2010 at 04:48, Jeroen Demeyer wrote: > I think there should be a component "scripts" on Trac. > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more op

Re: [sage-devel] Deprecated function alias in Cython file?

Cython classes by default don't have a __dict__ (which is why you're seeing the error below). Maybe the deprecated_function_alias should be modified to allow for deprecated aliases in cython classes. David On Sun, Dec 19, 2010 at 16:42, Rob Beezer wrote: > I'm trying to use deprecated_function_a

Re: [sage-devel] Conversion PARI GEN -> NumberFieldElement

Take a look at sage.rings.number_field.number_field.NumberField_absolute._coerce_non_number_field_element_in sage.rings.number_field.number_field_element.NumberFieldElement.__init__ (under if isinstance(f, pari_gen)) sage.rings.polynomial.polynomial_integer_dense_flint.Polynomial_integer_dense_flin

Re: [sage-devel] Re: Free advertising on Stack Overflow

I agree with William on "Eviatar 2": it's clear and concise. David On Sat, Jan 29, 2011 at 00:25, William Stein wrote: > On Thu, Jan 27, 2011 at 10:16 AM, Harald Schilly > wrote: > > Here is my idea, svg sources are in the same dir. > > > http://boxen.math.washington.edu/home/schilly/marketing/

Re: [sage-devel] Re: FAQ suggestion: I'm a programmer, how can I contribute to Sage?

On Tue, Feb 1, 2011 at 03:27, luisfe wrote: > On Feb 1, 3:41 am, "Dr. David Kirkby" wrote: > > On 01/30/11 03:27 PM, Jonathan wrote: > > Put another way, there should be a discussion about what Sage needs, how > urgent > > it is, and a plan drawn up. > > > > I thought porting Sage to Windows via

Re: [sage-devel] Re: cannot exponentiate a Python int by a real number

But int(2)**(1.5) causes the same bug that Dan observed. I think it's actually a bug and should have a trac ticket. David On Wed, Feb 2, 2011 at 22:51, Jason Grout wrote: > int(2)^(1.5) -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send

Re: [sage-devel] Re: distributed reviews for large patches (e.g. multivariate power series)

+1 As someone who writes large patches sometimes, I will try to use this idea. David On Tue, Feb 8, 2011 at 13:40, Rob Beezer wrote: > On Feb 8, 6:24 am, Niles wrote: > > So that my work and theirs can be fruitful, I have a suggestion for > > distributing the review effort. > > Niles, > > I th

Re: [sage-devel] Re: Sage Days 29

I'm potentially interested. The deadline for my thesis is March 31 though, so it would depend on how that goes in the next month. If you needed an answer right now, I'd probably say no, but I might be able to say yes in 3 weeks or so. David On Tue, Feb 8, 2011 at 23:02, William Stein wrote: >

Re: [sage-devel] sage thoughts

> >> (1) gcd is broken.http://trac.sagemath.org/sage_trac/ticket/10459 > [..] > > I'm personally OK either way with this. > > IMO a*b = gcd(a,b)*lcm(a,b) should be maintained wherever possible. > There are pari codes whose direct Sage equivalent silently breaks for > this reason, and I can't br

Re: [sage-devel] Re: sage thoughts

> Well, I used to use gcd for obtaining the primitive integral vector > with a specified rational direction. My concern on Trac 3214 was that > gcd(a1, ..., ak) depended on the order of arguments and I wanted it to > be fixed. The eventual solution was to agree that gcd as the "greatest > common di

Re: [sage-devel] Using Mercurial rebase extension to manage trac patches with mq when upgrading

> It will sometimes happen that the rebase extension can't figure out > how to merge your patches, so then it should launch whatever 3-way > merge tool you have configured for mercurial to use (such as kdiff3 or > vimdiff), allowing you to supervise the merge process. If you quit the > merge withou

Re: [sage-devel] Re: Coercion between polynomial rings

Mike is correct about your first question: your confusion is between coercion maps and conversion maps. The function you're looking for is _mpoly_base_ring, which is written in sage.rings.polynomial.multi_polynomial_ring_generic.pyx David On Wed, Feb 16, 2011 at 13:06, mmarco wrote: > I already

[sage-devel] Re: [sage-nt] Re: gcd lcm and numberfields

I just ran across a MathOverflow threaddiscussing gcds of algebraic integers living in rings with class number bigger than 1. We may not have the tools in Sage to implement it yet, but if someone's interested in

Re: [sage-devel] Proposal - Add notes of "verification" as comments to doctests

As I've mentioned on a related thread, I think that increasing the quality of doctests is a valuable goal, but that we shouldn't add more impediments to getting code accepted into Sage. In particular, I'm strongly against requiring such justifications for each doctest before code can get a positiv

Re: [sage-devel] Sage special session at AMS/MAA joint meetings in 2012?

Having not been to the joint meetings, what does this involve? I will probably make it to next year's, despite just having moved away from Boston. David On Tue, Mar 15, 2011 at 18:06, William Stein wrote: > Hi, > > I'm curious if anybody was planning on organizing a special session on > Sage at

Re: [sage-devel] Re: Sage special session at AMS/MAA joint meetings in 2012?

d." > > The page is here: > http://www.ams.org/meetings/national/jmm2012/2138_ssrequest > > Basically you email Michel Lapidus: lapi...@math.ucr.edu. > > -Marshall > > On Mar 15, 6:43 pm, David Roe wrote: > > Having not been to the joint meetings, what does

Re: [sage-devel] Proposal - Add notes of "verification" as comments to doctests

On Thu, Mar 17, 2011 at 05:14, Nicolas M. Thiery wrote: >Hi Dave! > > As Robert said, thanks for your continuous suggestions on how we could > possibly increase Sage's quality! > > On Mon, Mar 14, 2011 at 06:07:03AM +, Dr. David Kirkby wrote: > > On 03/12

Re: [sage-devel] The hash function for matrices suffers from many collisions with permutation matrices

> > > for is a function of the hash of its elements to > > satisfy equal matrices over different parents having the same hash. > > Err, sorry, I don't manage to parse the end of the sentence. Do you > mind reformulating? I think what Robert was trying to say is that if R and S are different rings

Re: [sage-devel] Re: Failed tests for accuracy reasons

On Thu, Mar 17, 2011 at 01:35, Robert Bradshaw wrote: > On Wed, Mar 16, 2011 at 6:15 PM, Jason Grout > wrote: > > On 3/16/11 3:04 PM, Peter Jeremy wrote: > > > >> Overall, I believe the abs(actual-expected) >> the only practical way to handle doctests. The expected numeric > >> result is still

Re: [sage-devel] sage -coverage on cdef methods raising exceptions

The coverage script doesn't handle functions that end with "except BLAH" very well. I have an old patch up somewhere, which I'd be up for trying to get into Sage once I finish my thesis. David On Thu, Mar 10, 2011 at 01:10, Nathann Cohen wrote: > Hello everybody !! > > I am trying to fill some d

Re: [sage-devel] Re: Summer of Code

My guess is that nobody stepped up to submitting the required materials, and the GSOC results have already been announced. David On Sat, Mar 19, 2011 at 02:31, David Kirkby wrote: > On 18 March 2011 19:06, Harald Schilly wrote: > > Sage won't be a host organization in the GSoC program. Submitti

Re: [sage-devel] Re: Refactoring of posets

> > In the process of refactoring / categorifying the poset code, I am > creating a category for posets which are lattices. What should be the > name for this category? Lattices() would be natural, but might get > into conflict with other kind of lattices. Should we use > LatticePosets() instead? >

Re: [sage-devel] Re: Patch submitting procedures

If the script automatically prepended: > > Trac #: > > to the start of every commit message, then: > > 1. the ticket number text would be uniform > > 2. if a wrong ticket number was indicated, it would be obvious which was > the correct ticket number, as it's always first in the standard forma

Re: [sage-devel] Re: How to cope with a long method resolution order?

I think that base_ring and parent are cpdef'd methods (I don't want to look it up at the moment). You want to be a little careful overriding such methods with Python functions living in the dictionary, because then the functions called by Cython code that knows the type of your object, and the cod

Re: [sage-devel] new group sage-trac-account for managing trac accounts

> > > It would seem wise to me that the email is initially at least the same one > as they have used to post to sage-devel or sage-support. If they have never > posted there, I don't feel they need a trac account. > I disagree. I've had examples of colleagues who use sage (but never posted) and h

Re: [sage-devel] Q.lift()(x) or Q.lift(x)?

Why not have Q.lift() return the morphism and Q.lift(x) return the morphism applied to x? I think I've seen this paradigm applied elsewhere David On Wed, Apr 20, 2011 at 11:46, Robert Bradshaw wrote: > On Wed, Apr 20, 2011 at 5:15 AM, Nicolas M. Thiery > wrote: > > On Wed, Apr 20, 2011 at 02:3

Re: [sage-devel] Re: progress on sage on python-2.7

Does hitting Enter again not do it? David On Wed, Apr 20, 2011 at 22:04, Francois Bissey < francois.bis...@canterbury.ac.nz> wrote: > > On Wed, Apr 20, 2011 at 06:41:26PM -0700, François wrote: > > > > This test reduces to: > > > > > > > > sage: class CCls(Parent): > > > > ... def

Re: [sage-devel] matrices for the univeral cyclotomic field

> > Is there a fast way to store the data as a 2-dim array with entries > being dictionaries with keys being basis elements in the Zumbroich > basis, and with rational values? Any other suggestions? I don't have any particularly insightful ideas, but are you thinking about a 2d C array of Python

Re: [sage-devel] Some comments about the notebook's home page.

On Thu, Apr 28, 2011 at 05:17, Dr. David Kirkby wrote: > Here's a few comments about the home page of the notebook. > > http://localhost:8000 > > I'd appreciate what others think. > > 1) I was always taught that if you list items, you don't put a comma before > the last "and". i.e. one should writ

Re: [sage-devel] Is there a sparse univariate polynomial ring implemented with NTL?

All sparse polynomials are implemented within Sage, in sage.rings.polynomial.polynomial_generic_sparse. It would be good if the constructor only used the implementation as part of the key for dense polynomials. David On Wed, May 11, 2011 at 04:37, Simon King wrote: > Hi! > > When constructing a

[sage-devel] Problem building ppl in sage-4.7.1.alpha4

Hi everyone, I got this problem building both alpha2 and alpha4. I'm running OS X (10.6.7) on a 64-bit Macbook Pro. libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../src -I/Users/roed/sage/sage-4.7.1.alpha4/local/include -g -O2 -frounding-math -I/Users/roed/sage/sage-4.7.1.alpha4/local/in

Re: [sage-devel] Re: Problem building ppl in sage-4.7.1.alpha4

It looks like it was memory. I was thrown off because it crashed at the same point each time, but I guess that makes sense. Thanks, David On Sun, Jun 12, 2011 at 05:49, Volker Braun wrote: > Do you use some non-standard compiler? Or did you run out of memory/disk > space? Something killed g++

Re: [sage-devel] How to delete files on trac?

I would like this as well. I don't know if files attached to a trac ticket keep track of who added them though; if not there are some technical hurdles to overcome. David On Tue, Jun 14, 2011 at 17:51, Christian Stump wrote: > Hi, > > I wonder if there could be the option to delete (your own, un

Re: [sage-devel] How to delete files on trac?

>> Is there any reason (theoretical or technical) for not having such a > >> feature? > > I think that Trac simply does not support this. > > It does support this. It is a permission. For example, *I* can delete > any attached files, since I'm a TRAC_ADMIN. The default permissions > don't allow t

Re: [sage-devel] No patch applied

Did you rebuild Sage? After typing hg_sage.apply("") you need to quit sage and type sage -br at the command line. David On Thu, Jun 23, 2011 at 13:14, Rolf wrote: > To be honest, I the Sage review process seems cumbersome to me. > > Following the instructions (http://www.sagemath.org/doc/develo

Re: [sage-devel] patchbot down?

Yes, I was having a similar problem last night. David On Fri, Jun 24, 2011 at 11:43, Maarten Derickx wrote: > It seems that I can't reach it anymore by going to > http://sage.math.washington.edu:21100/ > > Do other people have the same problem > > -- > To post to this group, send an email to sage

Re: [sage-devel] Sequence() with vector spaces

Why aren't you just using python lists? David On Sat, Jun 25, 2011 at 01:44, Rob Beezer wrote: > I'm having trouble with the construction of a list of vector spaces > with the Sequence() command. > > Is this a bug, or misuse/abuse? Failure, followed by a bit of a > workaround. > > sage: T=[QQ^2

Re: [sage-devel] Problems with symbolic vector arithmetic

The implementation in sage/modules/vector_symbolic_dense just inherits from FreeModuleElement_generic_dense, without overriding any methods like _add_ or _new_c. In particular, the arithmetic operations in FreeModuleElement_generic_dense hard-code the class, so that arithmetic always creates a new

Re: [sage-devel] patchbot down?

pages > to make sure it has up-to-date information). > > On Fri, Jun 24, 2011 at 3:07 AM, David Roe wrote: > > Yes, I was having a similar problem last night. > > David > > > > On Fri, Jun 24, 2011 at 11:43, Maarten Derickx < > m.derickx.stud...@gmail.com> &

Re: [sage-devel] Re: Importing units into module

One solution to circular imports is to do one of the imports inside a function, rather than at the top level. David On Thu, Jul 21, 2011 at 17:36, Eviatar wrote: > I can't see how to solve this. > > I import units, which import sage_eval, which imports symbolic, which > imports physical_constant

Re: [sage-devel] Witt vectors

Here are a couple problems with those files, though I'm not getting exactly the same problems you observe. * You need to define the element class in the parent. So for example, class RingOfWittVectors(CommutativeRing): element_class = WittVector def __init__(self, base, n, p=None, catego

Re: [sage-devel] Re: Witt vectors

> No, that's wrong. In that way, you would make it impossible to merge the > methods defined in the category framework into the element class. It > should be >Element = WittVector > and then element_class would be automagically created. > You're right. David -- To post to this group, send an

Re: [sage-devel] Re: Witt vectors

You have a circular import error. One way to solve it is to import RingOfWittVectors inside the __init__ method of WittVector rather than at the top level of the module. David On Thu, May 17, 2012 at 3:45 PM, Luis Finotti wrote: > Dear Simon, > > Firstly, thank you for your help. > > On Thu, May

Re: [sage-devel] doctest coverage & testsuites

The sage-coverage script doesn't handle cython files very well. I have an OLD ticket http://trac.sagemath.org/sage_trac/ticket/1795 addressing some of these issues. But I'm sure it doesn't currently apply. David On Fri, May 25, 2012 at 2:39 PM, john_perry_usm wrote: > Hello > > (1) I'm trying

Re: [sage-devel] Poll: Making sage-mode a standard package

[X ] Don't make it standard and close the ticket. ** Include it as an > optional package.** > +1 David -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this gro

Re: [sage-devel] please complain

On the complaint form it defines spam as "Using our service to send mass unsolicited emails (spam)." As far as I know, sagetrac.com hasn't been doing that David On Sun, May 27, 2012 at 10:48 AM, William Stein wrote: > Hi, > > Here's what happens when you don't renew a domain name. Somebody

Re: [sage-devel] Gap packages

A number of people are working on transitioning Sage to git (see #13015), and the meaning of spkg will likely change dramatically in a way that affects 2 and 3. In particular, spkg install scripts for both standard and optional spkgs will be included in the sage repository, as will pointers to ups

Re: [sage-devel] sage-git mailing list

There's now a google group sage-git. Go to http://groups.google.com/group/sage-git?lnk=gcimh if you're interested in joining. David On Fri, Jun 1, 2012 at 7:48 AM, Jeroen Demeyer wrote: > If it's not too much trouble, can we have a sage-git mailing list to > discuss the transition to git? I thi

Re: [sage-devel] Re: trac's "report upstream" options

Done. David On Thu, May 31, 2012 at 8:40 AM, Nils Bruin wrote: > On May 31, 1:42 am, John Cremona wrote: > > On trac there are various options in a drop-down menu under "Report > > upstream", but no option for "Reported upstream, no response yet" > > which I wanted to use for #13065. It's not

Re: [sage-devel] Re: trac's "report upstream" options

On 2012-06-01 19:59, David Roe wrote: > > Done. > > David > > Was it easy to do that? > > Because I would also suggest cleaning up "Components" as was discussed > some time ago on sage-devel. > > For example, I would like components > "porting: AI

Re: [sage-devel] header files in hgignore

I think they're generated by Cython to interface with external C code. According to http://docs.cython.org/src/userguide/external_C_code.html#public-declarations, these files are autogenerated and thus we shouldn't need to include them David On Fri, Jun 8, 2012 at 2:28 PM, R. Andrew Ohana wrot

Re: [sage-devel] sip package - optional or experimental

If the optional one is functional, then I agree that the experimental one should be removed. Go for it! David On Wed, Jun 13, 2012 at 11:44 PM, Rajeev Singh wrote: > Hi, > > I was going through the list of optional and experimental packages for > Sage and discovered that sip appears twice (diff

Re: [sage-devel] Re: Inconsistent behaviour with solve and precision

If you did this you'd need to tell maxima to assume various things about the variables (real, in between floatvalue - epsilon and floatvalue + epsilon...). I don't know maxima well enough to determine how feasible this idea is if you made such assumptions, but it's worth investigating. David On T

Re: [sage-devel] Re: projective space over rings and rational maps

> Note that the integers (which should probably be treated as a special > case) > does have sufficient general ideal theory code available: > > sage: I = ZZ.ideal(2) > sage: I = ZZ.ideal(2) > sage: ZZ.ideal(1) == I + J > True > > but the p-adics apparently do not: > > sage: ZZp = pAdicRing(2) > sag

[sage-devel] New doctesting framework

Hi everyone, For a few months I've been working on a new doctesting framework (based on code by Robert Bradshaw), which is now ready for review at #12415. Some highlights include: * eliminate Sage startup time per-file, which drops the time to run all tests dramatically, especially on OS X. * add

Re: [sage-devel] Re: New doctesting framework

> * eliminate Sage startup time per-file, which drops the time to run all > tests > > dramatically, especially on OS X. > > Why especially on OS X? > Maybe I'm wrong, but I thought the startup time per file was higher on OS X. It was just a vague recollection though: I haven't done tests. David

Re: [sage-devel] Huge number of warnings "local variable '...' referenced before assignment in sage 5.1.beta6

It's due to a change in Cython. Cython now emits warnings for things like cdef mpz_t a mpz_init(a) since a hasn't been initialized. I don't know if anyone's working on getting rid of the warnings; I agree that they're annoying. David On Mon, Jun 25, 2012 at 6:04 PM, Julien Puydt wrote: > Hi,

Re: [sage-devel] coercion vs conversion between polynomial rings

This is a bug in the __call__ method of multivariate polynomial rings, which doesn't respect user-defined coercions. The offending lines are 805-813 in sage/rings/polynomial/multi_polynomial_libsingular.pyx: if isinstance(element, MPolynomial_libsingular) and element.parent() is not self

Re: [sage-devel] Bug in nth_root() for finite rings (related to p_adic printing)

Thanks for catching that. #13172 is ready for review. David http://trac.sagemath.org/sage_trac/ticket/13172 On Tue, Jun 26, 2012 at 11:51 PM, Bohua wrote: > An example that triggers the bug is: > > roots = mod(-1, 4489).nth_root(2, all=True) > > Note 4489=67^2 and 67^2 is the first prime >62.

[sage-devel] Vote: adding speaklater as a standard spkg

Hi everyone, The new doctesting code (#12415) needs a change to the way Sage handles temporary files, which is described at #13147. We can either 1. change every use of temporary files within the sage library, or 2. depend on the speaklater project and use a lazy string. Everyone working on the t

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