Re: [sage-devel] Re: Hermite normal form of matrix over polynomial ring

Hi Vincent, Thank you for your expert comments and cutting-edge references. My target is to get hermite normal forms for square matrices over polynomial rings over finite fields, underlying function field arithmetic. What is available in Sage for this is only "A._hermite_form_PID()", which is v

[sage-devel] Hermite normal form of matrix over polynomial ring

Hi, The current Hermite normal form algorithm in Sage for matrices over k[x] seems embarrassingly slow. It is a generic algorithm for matrices over PIDs. What would be possible ways to improve the situation? Any reference to literature or implementations or like would be welcome. Thanks. -- Y

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

I expect that (1) If M is not square, then there is no ".is_similar" method attached to M. (2) If M is square and N has different size, then raise an error. If False is returned in the case (2), then the user needs to make additional efforts to find the cause (either N has the same size but is

Re: [sage-devel] Conversion bug: field to vector space

Ok. Now this is https://trac.sagemath.org/ticket/21723#ticket -- 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

[sage-devel] Conversion bug: field to vector space

Hi, I think this is a bug: sage: F.=GF(9) sage: V=F.vector_space() sage: V(a) (0, 1) sage: G.=GF(3) sage: W=G.vector_space() sage: W(b) ... TypeError: can't initialize vector from nonzero non-list The cause is sage: a._vector_() (0, 1) sage: b._vector_() ... AttributeError: 'sage.rings.finite_r

Re: [sage-devel] Re: Finite fields coercion bug

On Thursday, October 13, 2016 at 9:59:50 PM UTC+2, David Roe wrote: > > > In order to create finite fields with arbitrary variable names that fit > into a lattice of fields, one possibility would be able to give an > algebraic closure explicitly as an argument to GF. Is that what you're > sugge

Re: [sage-devel] Re: Finite fields coercion bug

Hi David, First, thank you for technical explanations. They are compelling. On Thursday, October 13, 2016 at 9:59:50 PM UTC+2, David Roe wrote: > > > In order to create finite fields with arbitrary variable names that fit > into a lattice of fields, one possibility would be able to give an > al

[sage-devel] Re: Finite fields coercion bug

Hi, On Thursday, October 13, 2016 at 7:14:27 PM UTC+2, Peter Bruin wrote: > > Even though there is no coercion map in this situation, simply trying to > discover a coercion "taints" the target parent by registering the fact > that there is no coercion. Then should we consider this behavior as

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

> > I was only trying to help but if I cause problems to others I'll just not > bother. > I stopped hades. Is the fault with the patchbot, not with Sage 7.4.rc0? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

[sage-devel] Re: Graceful shutdown of patchbot

rectly: Commit: c57069e9c66ad4f28038744f370fe6aac9c574d0 (7.4.beta4 + 9 commits) I cannot understand exactly how this happened... Frederic Le jeudi 15 septembre 2016 09:49:13 UTC+2, Kwankyu Lee a écrit : Dear all, A patchbot is supposed to run forever, but realistically I should stop it from time to time.

[sage-devel] Graceful shutdown of patchbot

Dear all, A patchbot is supposed to run forever, but realistically I should stop it from time to time. Pushing ctrl-c stops the patchbot abruptly, and the subsequent run seems sometimes to show somewhat erroneous behavior, perhaps due to the spurious state of the files. Is there a way to stop

[sage-devel] Re: How about automatic install of all possible optional packages by a patchbot?

> > Note that we'd have to do both, testing with *and* without (each) > optional package. Obviously we cannot test for all possible combinations of packages. But I think that every patch must be tested against at least one vanilla Sage and one full-featured Sage with "all" optional package i

[sage-devel] How about automatic install of all possible optional packages by a patchbot?

This happened to me. My patch for a ticket passed the doctesting by a patchbot A but afterward failed by another patchbot B. The reason was that the patchbot B has an optional package installed, and hence ran the optional doctests for the installed package, and my patch failed some of the optio

Re: [sage-devel] Re: Declaring a parent in a category as a finite enumerated set

On Thursday, September 1, 2016 at 4:53:00 PM UTC+2, Daniel Krenn wrote: > > On 2016-09-01 01:47, Kwankyu Lee wrote: > > I am playing with an experimental implementation of "enumerated" axiom. > > From what I guess is, that this axiom implies an implementation of &g

Re: [sage-devel] Re: Declaring a parent in a category as a finite enumerated set

One more nice example. sage -t src/sage/combinat/integer_vector_weighted.py ** File "src/sage/combinat/integer_vector_weighted.py", line 125, in sage.combinat.integer_vector_weighted.WeightedIntegerVectors_all.__init__ Failed exa

Re: [sage-devel] Re: Declaring a parent in a category as a finite enumerated set

I am playing with an experimental implementation of "enumerated" axiom. The results are interesting. sage -t src/sage/combinat/posets/posets.py ** File "src/sage/combinat/posets/posets.py", line 755, in sage.combinat.posets.pose

Re: [sage-devel] Re: Declaring a parent in a category as a finite enumerated set

> > Output of join categories definitely could use some love. :-) > A first improvement could be to use: > > Category of X an enumerated sets. > Alternatively: Category of enumerable X > should be trivial to implement. Good news. But I have to study more of the internals of

[sage-devel] Re: Declaring a parent in a category as a finite enumerated set

Right. Perhaps I was just thinking of "cosmetics". Lots of parents in Sage should be finite enumerated sets. If their category is a join of some category X and the category of finite enumerated sets, then it is printed as Join of some category X and the category of finite enumerated sets. I tho

Re: [sage-devel] Declaring a parent in a category as a finite enumerated set

> > Yes. In your case it will be one of .Finite() or .Finite().Enumerated() > or .Enumerated() Hmm. I get {{{ sage: m=FreeModule(GF(*2*),*2*) sage: c=m.category() sage: c.Finite() Category of finite finite dimensional vector spaces with basis over (finite fields and subquotients of monoid

Re: [sage-devel] Declaring a parent in a category as a finite enumerated set

This is about so-called categories with axioms. Right? I think ".Finite().Enumerated()" is a nice construct. But this seems not implemented yet... Am I right? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and sto

Re: [sage-devel] Declaring a parent in a category as a finite enumerated set

For (1): Joining categories works. However, this seems not a standard nor an elegant way... -- 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..

Re: [sage-devel] Declaring a parent in a category as a finite enumerated set

> > For example, have a look at sage/combinat/free_module.py lines 1170-1175. > Are you referring specifically the construct ".FiniteDimensional()" to get a subcategory? Then can I use ".FiniteEnumerable()" for my case? I guess not... On the other hand, in other examples, I see ".Finite()" giv

[sage-devel] Declaring a parent in a category as a finite enumerated set

I am not familiar with the category framework. My questions are (1) I want certain parents in a category C to be also in the category of finite enumerated sets such that I can use .list() method. Not all objects in the category C is not finite. What is the standard way to implement that? (2) Al

Re: [sage-devel] Doc-testing ouptut with dots

> > But one's interface shouldn't be dictated by what the doctester can > and can't do. I agree. > Does anyone know if there's a reason the standard > doctest flags (like #doctest: -ELLIPSES) don't work properly in Sage's > tests? > I investigated this. The doctest options(flags) is imp

[sage-devel] Re: inverse of units

For inverting in the original parent ("internally"), the name "m.inverse_of_unit()" is used widely in Sage, e.g. in integer rings, polynomial rings, p-adic rings, etc. The name "m._invert_unit()" seems to be used only for matrices. I now understand the "unit" in the name for differentiating fro

[sage-devel] Re: inverse of units

How about "m.multiplicative_inverse()" or just "m.inverse()" which already works for matrices? Or those with a hyphen prepended, for "internal" use. On the other hand, "inverse" or "invert" implies that m is(should be) a unit. Then "unit" in the name seems redundant... -- You received this me

[sage-devel] Re: ssh fail

I ran ssh -v k...@trac.sagemath.org. It also fails :-) But I have no problem in pushing changes to trac... On Wednesday, June 29, 2016 at 11:49:31 AM UTC+9, tara fife wrote: > > Thanks, > > I went into the known_host file, and deleted everything, since I should > only have things for Sage. Then

[sage-devel] Re: ssh fail

Perhaps you had the same issue with mine. Then the correct fix was just to remove the line for trac.sagemath.org in the file .ssh/known_hosts, not resetting your own ssh keys. Now that you seem to have changed your ssh private/public key pair, you need to register your new ssh public key to tra

[sage-devel] Re: A strange bug in the category framework

It is also strange why the pasted text copied from terminal looks double spaced... -- 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...@googlegr

[sage-devel] A strange bug in the category framework

I found a strange bug that has existed at least from Sage 7.1 In a fresh start of Sage, sage: GF(2)^2 Vector space of dimension 2 over Finite Field of size 2 sage: CyclicPermutationGroup(10).algebra(FiniteField(5)) --- T

[sage-devel] Re: Current best practice for LaTeX of function names

It is _latex_(self) according to the developer manual http://doc.sagemath.org/html/en/developer/coding_in_python.html#latex-representation On Wednesday, June 15, 2016 at 8:18:51 AM UTC+9, Paul Masson wrote: > > I'd like to add LaTeX support to special functions that do not yet have > it. Before

[sage-devel] Re: Evaluation of beta() in Sage 7.2

> sage: x=-.9 > > sage: y=.1 > > sage: gamma(x)*gamma(y)/gamma(x+y) > > 17.5241239902668 > > sage: beta(x,y) > > NaN > I get the same on Sage 7.3 beta3 on Mac. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and s

Re: [sage-devel] Users can permanently modify GF(5).list()

As the discussion of this thread seems to converge to the conclusion that we need to transfer the function of X.list() to X.elements() or like to avoid confusion, I still like to add to the following separate issue >> (For matrix X), X.list() returns a list of all the > >> entries of the matri

Re: [sage-devel] Users can permanently modify GF(5).list()

> > Suppose that our object X has a basis consisting of four 2x2 matrices, > in some abstract sense. Then your > >X.list() > > might very well return a tuple of four *mutable* 2x2 matrices. Then > this X.tuple() is still very much mutable, and the original problem > has not been solved

Re: [sage-devel] Re: print to python3

I am wondering why no one mentions the "six" package to maintain a temporary py2/py3-compatible codebase. I have an experience of moving my own small project from python 2 to python 3 with the "six" package quite successfully. The strategy was to add "import six" at every file and make the file

[sage-devel] Re: Let's "make ptestalllong"

Equivalent line that works for file xxx is sage -tp --optional=sage,optional,external --long xxx -- 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+unsu

[sage-devel] Let's "make ptestalllong"

Dear Sage developers, As Sage 7.2 just released, we can now use its new feature to test optional doctests that depend on external software and resources *available on your system* by issuing make ptestalllong instead of "make ptestlong", which has long been used to test a Sage release, discre

[sage-devel] Re: On development workflows for sharing (experimental) code

Thank you for starting and sharing this. -- 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

[sage-devel] Re: Optional doctest failure

As the author of #20182, I don't think that the behavior of `sage -t` changed. #20182 triggers a new behavior only if you put "optional=...,external,..." in the argument list. On the other hand, new definitions of make (p)testoptional(long) make (p)testall(long) indeed include "optional=sage,o

Re: [sage-devel] Let's talk specifics (was Re: how we develop sage)

This discussion is hardening the terms: Sage core and external packages. But from the point of view of the people developing the would-be external packages, the official term would better be Sage extension, Sage library extension, Sage library extension package, or SLEP. Or simply extension pa

Re: [sage-devel] Code vs codes

I didn't know this. Thank you! -- 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-d

[sage-devel] Code vs codes

Which one is correct? (1) "This is based on code by A and B" (2) "This is based on codes by A and B" (3) "This is based on the codes by A and B" I am just curious. I am not a native English speaker. -- You received this message because you are subscribed to the Google Groups "sage-devel" grou

[sage-devel] Re: Coming SageMathCell upgrade - please test!

The webpage from the Madrid server opens but contains no Sage cell. My web browser is Chrome on Mac. Accessing from Asia might be a cause. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fr

[sage-devel] Re: Using custom Singular lib

I guess I could never figure out this by myself. Thank you! -- 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 thi

[sage-devel] Re: Proposal: move SageNB back to Sage

+1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit

[sage-devel] Using custom Singular lib

I want to write a Sage module, say "function_field.py", that uses Singular functions defined in a library, say "singular_core.lib". My questions are (1) Where should I put the library file? I guess it should be along with the Sage module file. (2) If so, then how should I load the library? I kn

[sage-devel] Re: Request for review: Trac #19084

Not anyone, but experts on Sage's Singular interface. -- 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 gro

[sage-devel] Request for review: Trac #19084

I would appreciate if anyone is interested enough to review: http://trac.sagemath.org/ticket/19084 -- 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+unsu

[sage-devel] Re: how we develop sage

On Friday, April 15, 2016 at 8:46:44 AM UTC+9, Chris Swierczewski wrote: > > I felt like writing this up: > > https://gist.github.com/cswiercz/c632d920565a2da519b73bd2b79d7920 > > Please suggest improvements and corrections. > Sorry. I didn't see your post before I wrote mine :-) That is a nice s

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

On Friday, April 15, 2016 at 6:54:44 AM UTC+9, kcrisman wrote: > > > > These packages are nearly impossible to found from the sagemath website! >> >> Chris -- who wrote abelfunctions -- is a Univ of Wash grad student I >> know. I recently ran into him and he told me that he had spent years >>

Re: [sage-devel] Docstring-wide "# optional" markup (#20427)

Then "OPTIONAL - foo" gets the same status with "EXAMPLES" (or "INPUT", "OUTPUT", etc). This conveys a misconception since "OPTIONAL" does not mean anything with the method or function that this docstring is attached to. I prefer Dima's suggestion or some variant of that. -- You received this

[sage-devel] Re: how we develop sage

It would be nice if (1) Sage library consists of core + optional parts (2) An optional part is dependent on core + other optional parts (3) Optional parts to install can be selected at build time. (4) An optional part has its own documentation, but accessible through a single interface in Sage.

Re: [sage-devel] ptestall tests all optional packages

> > Yes, it is a feature. I agree that it might be a silly feature. > After having fully merged: http://trac.sagemath.org/ticket/20182, how about changing the meaning of "all" in "make testall" and "sage -t --optional=all" to "--optional=sage,optional,external"? -- You received this message

[sage-devel] Re: ptestall tests all optional packages

The behavior of `make ptestall` is at least consistent with that of `make testall`. It is silly to test for not installed optional packages. Kwankyu -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivi

[sage-devel] Re: Special markup to influence the doctesting

A ticket for this: http://trac.sagemath.org/ticket/20176#ticket -- 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 t

[sage-devel] Special markup to influence the doctesting

The "Special markup to influence (doc)tests" section of the developer's guide claims that it is comprehensive. But I could not find any explanation on the use of ellipsis "..." and on "# latex output" comment. I interpreted the comment as requiring latex system installed on the system where doc

Re: [sage-devel] Re: "Möbius": to 'mobius' or to 'moebius'?

I am an asian. I prefer "moebius". It is practically impossible to type umlaut on a Korean keyboard. -- 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+un

Re: [sage-devel] Re: "Möbius": to 'mobius' or to 'moebius'?

I am a asian. I prefer .moebius(). It is practically impossible to type umlaut. -- 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...@googlegroup

[sage-devel] Re: Getting output of libsingular when it gives several objects

I heard from the author of the libSingular interface that multiple return values were not considered in the initial design. So I guess you need to revise Sage's libSingular interface first. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsu

[sage-devel] Re: libSingular functions require a ring parameter.

The ticket is waiting for a reviewer. Please! -- 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

Re: [sage-devel] SPKG Maintainers??

I am not that developer :-) How about this system? We trim the AUTHOR blocks by just listing the names of contributors to the given module (to give credits to the contributors); And we recommend a new contributor to add his/her name to the end of the list (to give more credits to the initial

Re: [sage-devel] Re: SPKG Maintainers??

I have written a couple of AUTHORS-blocks, but I think I did it not to have a credit but to be responsible for the code. AUTHORS blocks are rather for developers, not for end users. These blocks are rather hindrance for end users as they usually appear at the head of a documentation but these

[sage-devel] Re: SPKG Maintainers??

On Friday, September 18, 2015 at 9:06:55 PM UTC+9, Marc Mezzarobba wrote: > > Tangentially related: wouldn't it be better to also remove the "AUTHORS" > sections from docstrings? Big +1! Kwankyu -- You received this message because you are subscribed to the Google Groups "sage-devel" grou

[sage-devel] libSingular functions require a ring parameter.

This problem is tackled in http://trac.sagemath.org/ticket/19084 Would you review? On Thursday, August 6, 2015 at 6:36:54 PM UTC+9, Martin Albrecht wrote: > > Hi, > > On Wednesday 05 Aug 2015 23:35:26 Kwankyu wrote: > > My Singular procedures do not need a ring (they internally construct > >

[sage-devel] Re: Default ipython profile

This is a one-line ticket waiting for review, but is in pending state for patchbots since it touches an "unsafe file" (sage-ipython). Would any of you review? http://trac.sagemath.org/ticket/19021 -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

[sage-devel] Re: Trac Server Issue

I looked into this thread because I have the same issue with the following ticket. http://trac.sagemath.org/ticket/18807 Anyway, your ticket URL seems to have no problem :-) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from th

Re: [sage-devel] Default ipython profile

On Wednesday, August 5, 2015 at 11:27:56 AM UTC+9, François wrote: > > It is not a new behavior. We had that for quite some time now: True. But the official location for ipython user configuration was profile_sage at least 2 years ago (yeah I am a sporadic Sage user :-): http://trac.sagemath

[sage-devel] Default ipython profile

Hi, As of version 6.8, Sage seems to read "profile_default" in $DOT_SAGE/ipython-* directory by default. As I remember, the default profile was "profile_sage". Is this change official? Or should we view it as a bug? I would appreciate a reply. Kwankyu -- You received this message because yo

[sage-devel] Re: Trouble in updating to 6.4.1

On Monday, December 15, 2014 2:26:59 PM UTC+9, Soomin Jeon wrote: > > I installed sage 5.9 last year and I found that sage 6.4.1 is released. > So I try to update the sage version 5.9 to 6.4.1 using the command 'sage > -upgrade', however, it just upgraded the sage version to 5.13. > If I want to

[sage-devel] Re: "Sage for Undergraduates" is released

Wow! It looks nice. Thank you for sharing this. Kwankyu -- 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 g

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

Congratulations! -- 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@googlegro

[sage-devel] Re: Consistent failure of zn_poly in latest Sage

> > For example, can you stop everything on the computer and remote log in to > it from another machine, so you're hardly running anything on it? If not, > quit all possible applications and try building again. By the way, how much > RAM does this machine have (this may not be relevant, but jus

[sage-devel] Re: Consistent failure of zn_poly in latest Sage

> I think it is intermittent in the sense that on computers with the > problem, it fails consistently when building Sage in parallel; the fix is > to then quickly do that one package in series, then remain doing things in > parallel (see the ticket or other discussions for details). Are you s

[sage-devel] Re: Consistent failure of zn_poly in latest Sage

Hi, Sorry that I was not clear. Reading the comments for the Trac ticket, I thought that for others, this happens intermittently, so they succeed in building Sage eventually after a couple of failures. For my case, it always fails. I was asking if others experience the same consistent failures.

[sage-devel] Consistent failure of zn_poly in latest Sage

Hi, I am experiencing consistent failure in building the latest Sage including just released 5.9 at zn_poly. My system is MacPro Quad-Core Intel Xeon with OS X 10.7.5 and latest Xcode (I think). Are there others experiencing the same? Here is the log: Now running zn_poly's self-tuning progra

[sage-devel] Re: An apparent error in the start of making Sage

> Nope, this originates from > > if [ -f "$SAGE_ROOT/spkg/bin/sage-spkg" ]; then > if $MAKE -q "$@"; then > echo "Nothing to (re)build / all up-to-date." > exit 0 > fi > fi > > and is (harmless and) completely unrelated to the zn_poly issue (#13947). > > (We sh

[sage-devel] An apparent error in the start of making Sage

Hi all, This is a question. Is the apparent error in the output below a genuine error? What does it mean? I am experiencing the same error when making several previous versions of Sage, which all failed (seemingly) by the issue trac #13947. I am wondering whether this failure at the end is rel

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

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 and was not compatible with the latest noteboo

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

I solved the problem by moving out the ".sage" folder. Thanks for all your attention! > > > -- 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..

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

I had the following error in installing Sage 5.6 on MacBook Pro with Lion. Any help? Thanks in advance. ... Finished processing dependencies for webassets==0.7.1 running develop error: --egg-path must be a relative path from the install directory to /Users/kwankyu/Sage/sage-5.6/devel/sagenb-main

[sage-devel] --egg-path error in installing Sage 5.6

I had the following error while installing Sage 5.6 on MacBook Pro with Lion. Any help? Thanks in advance. ... Finished processing dependencies for webassets==0.7.1 running develop error: --egg-path must be a relative path from the install directory to /Users/kwankyu/Sage/sage-5.6/devel/sagenb-

[sage-devel] Re: list(matrix) vs. matrix.list()

How about m.entries()? I think "entry" is quite standard. -- 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@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googl

[sage-devel] Re: sign of permutations

Signature means to me a hand-written name. So ++1 to .sign() -- 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@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@g

Re: [sage-devel] Soliciting reviewers...

Hi, If you want to put some time (e.g., an hour a day) into being an > editor, I think that would be really cool. You could send personal > emails asking people to referee tickets you think they would be likely > to help with. Personally, I cannot do it. I don't expect anyone to volunteer.

[sage-devel] Soliciting reviewers...

Hi, This is a question and suggestion. Are our tickets in "needs review" status being timely reviewed? Judging from my own (limited) experiences, it seems not. I again find myself soliciting a reviewer for my simple ticket #11593. If this is the case, how about adopting a policy similar to the

[sage-devel] Re: Sage whitespace policy

Hi, I use the following script to check newly added trailing whitespaces just before I upload a patch. It uses the same code in the patchbot trailing whitespaces plugin. :-) Just put it into an executable file, say, "check_spaces" #!/usr/bin/env python import sys import re import os def trai

Re: [sage-devel] Re: Wanted: a reviewer for ticket #12503

> my point is that it should be customizable. One wants bash (resp. GAP, > resp. Magma) behavior, (s)he can get it. > > The patch only provides extra new readline commands. You bind those commands with your favorite keys only if you want those behaviors. Merging the patch to Sage does not cha

Re: [sage-devel] Re: Wanted: a reviewer for ticket #12503

On Tuesday, July 17, 2012 3:13:18 AM UTC+9, Dima Pasechnik wrote > > > More or less. > Specifically, I want the same behaviour as in GAP. In GAP one can go to A > using (say) arrows keys. Then, after executing A, you get GAP prompt, just > as if you execute the "normal" command. But if you then

[sage-devel] Re: Wanted: a reviewer for ticket #12503

Hi, > By the way, is there a sorely missed by me feature of getting the next > command in the history? > I.e. I often do something like this: > > sage: A... > sage: B... > sage: C... > oops, wrong answer; editing code... > sage: A... > sage: B... > sage: C... > oops, wrong answer; editing code.

[sage-devel] Wanted: a reviewer for ticket #12503

Hi, This ticket is long abandoned at Trac without a reviewer. http://trac.sagemath.org/sage_trac/ticket/12503 The feature that the patch provides is indispensable to me when I use command line interface of Sage. I think it is also very useful to you. Would you be a reviewer of the ticket? Kw

[sage-devel] Re: Understanding the patchbot's ApplyFailed

Ah, so it is a bug. Thanks. I should not have included # in the patch file name. On the other hand, it is strange that the patchbot tries to fetch an old patch file "trac#12503.patch" rather than the new patch file named "trac_12503_v3.patch" though I placed the comment "apply trac_12503_v3.p

[sage-devel] Understanding the patchbot's ApplyFailed

Hi, The patchbot is failing(ApplyFailed) on my patch for ticket #12503. I want to understand the reason. According to the log below, the patchbot seems to try to fetch the file at http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12503/trac#12503.patch I copied this line into the brow

[sage-devel] Re: A weiredness in Sage 5.0rc0

Hi Simon, The result is that the hash is broken by default, since the string > representation can be changed *after* creation of the object, which > means that the hash value would change as well. There is a ticket fixing > it, though. > > > I think the problem lies in that the hash is calcula

[sage-devel] Re: A weiredness in Sage 5.0rc0

Hi Simon, Thank you for the explanation. However, during the category initialisation, self is used as key in > some cache. Hence, it is needed that its hash value is available. By > default in sage.rings.ring.Ring, hash(self) is the self as > hash(repr(self)) > (which I don't like, by the wa

[sage-devel] A weiredness in Sage 5.0rc0

In Sage 5.0rc0, I observe a weird phenomenon. See the following code - from sage.rings.ring import CommutativeAlgebra class NA(CommutativeAlgebra): """ """ def __init__(self, i): """ """ CommutativeAlgebra.__init__(self, i.base_ring()) self._ideal

[sage-devel] Re: Acknowledging Sage components

Here is the link http://wiki.sagemath.org/Publications_using_SAGE -- 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 group at http://groups.google.com/group

[sage-devel] Acknowledging Sage components

Hi, In the Publications_using_SAGEwiki page, I find the following passage: ``Also, be sure to find out what components of Sage, e.g., NumPy, PARI, 'GAP, that your calcul

Re: [sage-devel] A couple of patchbot questions

Anyway, I just noticed that many of the patches with positive reviews have the red swirling symbol with "Apply Failed" on Sage 4.8. Then I wonder the patchbot is working correctly now... Kwankyu -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this gr

Re: [sage-devel] A couple of patchbot questions

The second patch is small, but the doctest takes quite a bit of time. So I changed the doctest and uploaded the patch again. Let me see this helps... Kwankyu -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+uns

Re: [sage-devel] A couple of patchbot questions

Hi Robert, > (1) I uploaded a new patch of the same name with the previous patch, but > the > > patchbot doesn't seem to be triggered. I already tried "?kick", with no > > help. Is there other way to kick the patchbot? Do I need to upload the > same > > patch with other name? > > Has it ever bee

<    3   4   5   6   7   8   9   >