Bruno Grenet wrote:
> My questions: Is my understanding correct? If not, what are supposed
> these arguments to be for? And if I understand correctly, is the
> behavior I mention a bug?
I'd say you are right, and the reason for the bug is that ETuple changed
after Polydict was written. Compare 5c
Dear all,
I am trying to implement a class of polynomials with very large
exponents. For this, I'd like to reuse the functionalities offered by
sage/rings/polynomial/polydict.pyx.
The __init__ method of the class PolyDict has arguments
force_int_exponents and force_etuples that I don't fully
Am 2015-03-12 um 10:51 schrieb Nathann Cohen:
>> There is nothing specific to our git setup as far as merging and rebasing is
>> concerned. So there is no need to reinvent a git-trac wheel here, its just
>> about making communicating with trac easier.
>
> I was thinking of some entry like "Merging
Hello,
> Where & when do you see something in red?
Sorry, I was talking of the trac ticket. Here is one for instance:
http://trac.sagemath.org/ticket/16534
There is some comment here about it there:
http://www.sagemath.org/doc/developer/trac.html#the-ticket-fields
Nathann
--
You received this
On 12 March 2015 at 09:51, Nathann Cohen wrote:
> Hell !
>
>> There is nothing specific to our git setup as far as merging and rebasing is
>> concerned. So there is no need to reinvent a git-trac wheel here, its just
>> about making communicating with trac easier.
>
> I was thinking of som
Hell !
> There is nothing specific to our git setup as far as merging and rebasing is
> concerned. So there is no need to reinvent a git-trac wheel here, its just
> about making communicating with trac easier.
I was thinking of some entry like "Merging with the latest release
(i.e. what s
There is nothing specific to our git setup as far as merging and rebasing
is concerned. So there is no need to reinvent a git-trac wheel here, its
just about making communicating with trac easier.
On Thursday, March 12, 2015 at 8:28:45 AM UTC+1, Nathann Cohen wrote:
>
> Hello everybody,
>
> I
Helloo !
I was pondering moving them en-masse to needs_info, but that's obviously
> neither a very helpful nor tactful way to handle things, so I prefer
> discussing the matter here.
>
It may be a good decision for some tickets, but it could be dangerous for
some others, like bugfixes
Somehow I thought I had lost a previous post so I posted it again, but then
I found the post: it had been minimized on screen while the first two posts
were not minimized. clearly I am still learning this Google Groups
interface
--
You received this message because you are subscribed to the G
Hello everybody,
I just noticed that we do not seem to have in our developer's manual
instructions about how to rebase/merge a branch when it becomes
incompatible with the latest beta.
I do not use 'git trac' myself, but it would be cool if anybody who
does could add such an entry in the develope
10 matches
Mail list logo
