Hi Sébastien,
I have been active in the sage-combinat queue for a little over a year.
Here is my impression of how the sage-combinat queue works. It could be
that how I think that the queue works, or how it is supposed to work, is
just wrong but to summarise I think that the queue currently wor
On Sat, Nov 24, 2012 at 9:57 AM, Sébastien Labbé wrote:
> Hi,
>
> I have been using the sage-combinat branch from 2008 to 2010 (all of my
> patches were in sage-combinat before getting on the sage trac) and then stop
> using it. Here is my view of this. First I believe the following principle
> is
Hi,
I have been using the sage-combinat branch from 2008 to 2010 (all of my
patches were in sage-combinat before getting on the sage trac) and then
stop using it. Here is my view of this. First I believe the following
principle is simple but very important :
Principle #1 : The priority (orderi
Hello !!
> Nathan, I think that this is the whole point that you are not seeing: we
> do work with sage and we do use trac. Extensively. Personally, I want my
> patches posted to trac as quickly as possible and merged into sage.
Yeah, perhaps I am wrong on that. I said a lot of things
> YES, but if you were working with the Sage TRAC server the patches would
> HAVE to be finalised. Please please, that's the whole point !
>
> Nathan, I think that this is the whole point that you are not seeing: we
do work with sage and we do use trac. Extensively. Personally, I want my
patch
Hi all,
In very short:
> You are totally independent of Sage, you don't *NEED* to
> contribute to have your version of it evolve
Not quite true: we do pay a heavy price for each and every patch that
is not merged: we have to keep rebasing them. I can tell you that it
*hurts*. We all
Helloo Andrew !
> I'm sure that I should drop this but...
At this level it may not hurt anymore :-)
> When ever anything gets big enough I think this starts to break down. For
> example, when I whined about the lack of documentation for the pickle jar
> the people who put this is place d
Hi Nathan,
I'm sure that I should drop this but...
I don't know. People usually pay attention to the code they wrote even much
> later. I still write to Robert Miller when I have questions on the graph
> backends, and I like to have his advice on Sage things from time to time.
When ever anyt
> 1) I will try to upload a patch this very week-end that changes the dfault
> behaviour of Poset as mentionned there :
Done ! It is now patch 13747 :
http://trac.sagemath.org/sage_trac/ticket/13747
And it is also very, very late... :-P
Good night everybody !
Nathann
--
You received this mess
Helloo !!!
> Would you mind taking a break and stop spreading FUD?
Ok, so let's get to work. I created #13742 yesterday and it is waiting for
a review :
http://trac.sagemath.org/sage_trac/ticket/13742
> You are not
> being fair.
I know. You know. Florent knows. I always speak too mu
It's certainly going to be exciting meeting several of you in
Edinburgh in January (at
http://www.aimath.org/ARCC/workshops/onlinedata.html) !
John
On 23 November 2012 14:38, Paul-Olivier Dehaye
wrote:
> Purkayashta: this would only address (in good or bad) a tiny part of the
> development issue
Purkayashta: this would only address (in good or bad) a tiny part of the
development issues, those that have to do with version control.
Paul
On Fri, Nov 23, 2012 at 2:01 PM, P Purkayastha wrote:
> On 11/23/2012 08:37 PM, Andrew Mathas wrote:
>
>> Does anyone have any /concrete suggestions/ fo
On Friday, November 23, 2012 1:50:08 PM UTC, Nathann Cohen wrote:
> Well. You have the right to like abstracton and generalizations. I prefer
> to duplicate code to make things independent, and easy to understand.
Code duplication is a bug, plain and simple. If it doesn't fail outright
then i
Hi Nathann,
Would you mind taking a break and stop spreading FUD? You are not
being fair. I totally know and care about all the crap in the combinat
code. It hurts me everyday. More than you think. There is just a
bounded amount of manpower and not everything can be tackled at once.
There
Hellooo !!
> I share your frustrations. I think we all do, to some extent. It would be
> very nice if all of these problems, major an minor, could be fixed but the
> reality is that until some one cares enough about a particular problem
then,
> as you say, it isn't going to happen. I t
H Nathan,
I share your frustrations. I think we all do, to some extent. It would be
very nice if all of these problems, major an minor, could be fixed but the
reality is that until some one cares enough about a particular problem
then, as you say, it isn't going to happen. I think this
Nicolas, I know you respect his job very much and I have nothing against
Mike Hansen of course. But these days I have been using Posets and
Permutations a bit, and with Florent we found several problems already, and
I am pretty sure you know muuuch more of them.
This thing with the permutations.
Hey Nathann,
The main reason why I stalled on the permutations input was mainly
trying to figure out how to handle generalized permutations (a.k.a.
bi-words, two-line arrays, in bijection with N-matrices) so the RS(K)
examples will still work (and as a 2fer, getting the full RSK working), and
Hi Nathann,
On Thu, Nov 22, 2012 at 06:13:52AM -0800, Nathann Cohen wrote:
>Vincent, Travis, Dima : there's a new patch at #13742. It does nothing. It
>just checks input. It adds tests and warnings. And I lost half a day and a
>lunch because of very bad work.
>Feel free to
19 matches
Mail list logo
