> So how about making it explicit, have separate Permutation and Permutation0 > (instead of tuple vs list). They can share most of the backend, its just a > slightly different set that they operate on. In Code, you just call sigma = > Permutation0(sigma) on user input in the beginning to convert it to your > desired presentation if you depend on the actual integers.
This would be cool, but how do we write the code afterwards ? What are the objects returned by Permutation1 and Permutation0 ? The functions of this class have been written with a standard in mind, and if you let it deal with 0-based permutations and 1-based ones some functions will break. And if we make 1-based permutations be 0-based permutations with a diferent __repr__, a different __call__ and a different __getitem__ we will run into problem too.. How could we make this strategy work ? Nathann -- 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 this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
