Hi Franco,
Is it possible that your patch under positive review in the sage-combinat queue
trac_13243-new_methods_for_compositions-fs.patch
breaks the queue for sage-5.2.rc0 due to an import error in
/combinat/compositions.py.
sage.categories.graded_enumerated_sets import GradedEnumeratedSets
Hi Andrew and Martin,
For me with all patches applied on sage-5.1, the tests for partition.py also
pass!
Anne
On 7/19/12 6:58 PM, Andrew Mathas wrote:
> Hi Martin,
>
> I am curious as to exactly what you did to get these doc test errors. Am I
> right in thinking that you applied all of the pat
Hi Martin,
I am curious as to exactly what you did to get these doc test errors. Am I
right in thinking that you applied all of the patches currently in the
queue (hg qpush -a) and then ran all of the doc tests to get these
failures? Which version of sage are you using?
The reason that I am as
On Thursday, July 19, 2012 2:45:09 PM UTC-7, Martin wrote:
>
> Anne Schilling writes:
>
> > Here are several *ideas*:
> >
> > * We should run daily tests on the "needs review" section and pop
> patches
> > off that section if the tests do not pass (or people are not actively
> working
>
Anne Schilling writes:
> Here are several *ideas*:
>
> * We should run daily tests on the "needs review" section and pop patches
> off that section if the tests do not pass (or people are not actively
> working
> on making them pass).
>
> * Everyone should try to get their patches into main-
Dear All!
Given Martin's questions about the doc test failures on the queue and also
some discussions I had last week at the Sage Days and by e-mail with Franco,
perhaps we need to discuss some issues about the sage-combinat queue.
First of all, the queue is meant for active development of code i
Anne Schilling writes:
> Hi Martin,
>
> If you want to run tests on your own patch, I suggest to apply it to a clean
> version of sage-5.2.rc0. All tests in a clean version of sage-5.2.rc0 should
> pass! The ones that fail would then be due to your patch.
Well, what I was doing depends on most o
Hi Martin,
If you want to run tests on your own patch, I suggest to apply it to a clean
version of sage-5.2.rc0. All tests in a clean version of sage-5.2.rc0 should
pass! The ones that fail would then be due to your patch.
If you run sage -t on the sage-combinat queue, it is not guaranteed that
t
I just wanted to test whether some experimental changes wouldn't break
anything and ran
sage -t devel/sage-combinat/sage/combinat/
I get quite a few failures, ugly errors, etc.
Which of these should I expect?
eg.
File
"/groups/comb/rubey/sage-5.1/devel/sage-combinat/sage/combinat/subsets_pai
Hi!
I'd like to draw your attention to
https://groups.google.com/forum/?fromgroups#!topic/sage-devel/Ue5g73lN4KQ
The topic is: How to represent groups in Sage.
We would like to have an abstract group that is able to provide us with
different realisations of itself (permutation presentation, fai
10 matches
Mail list logo
