[sage-combinat-devel] Re: fast vector partitions algorithm

Hi Denis, in the past, sage-combinat-devel was a very active list and certainly the topic of your post fits well, but it seems to me that it would be a good idea to re-post on sage-devel. Did you read the developer's guide? Certainly people could help you contributing the code. In particular if

[sage-combinat-devel] Re: fast vector partitions algorithm

PS: Sorry, I just notice that you did answer my question: It is 60 lines of python code. That shouldn't be a problem to include in the Sage library (i.e., in relevant parts of src/sage/..., maybe in the same location than the current implementation. Do you have a trac account? Best regards, Simo

[sage-combinat-devel] Re: fast vector partitions algorithm

Hi Denis, That is great that it can have a faster implementation. Do you have the code available for us somewhere? Some thing to also note is that VectorPartitions creates a Sage Element instance instead of a simple Pyhton list, which has extra overhead. However, this should not account for m

[sage-combinat-devel] Re: fast vector partitions algorithm

Thanks to everybody for the friendly replies. I could paste the code right here, is that the proper way to do it? How is the license transferred to Sage? I have a trac account because I once contributed a small bugfix but nothing happened with it, so it

[sage-combinat-devel] Re: fast vector partitions algorithm

Thanks to everybody for the friendly replies. > > I could paste the code right here, is that the proper way to do it? How is > the license transferred to Sage? > The way to submit code is to push a git branch to our trac server and then update the ticket to include that branch name under the b