Nicolas, > Instead, we need a mantra for requesting what the class is for > (uni/multi)variate polynomial rings in over ... > > As a temporary measure, one could do: > > def parent_class_of_multivariate_polynomial_ring(K): > return type(PolynomialRing(K,['x','y']))
There are additional hurdles. For example, what methods should one assume will be provided by one of those random low-level polynomial classes? They should really all be subclasses of a very generic abstract polynomial ring class. More seriously for me at the moment, there is type enforcement going on somewhere. If __init__ is called with a custom class, failure occurs because the actual class instance is not received. This happens for sage.rings.polynomial.multi_polynomial_ring.MPolynomialRing_polydict which seemed like the most friendly class of general-purpose multivariate polynomial ring that I could find. Dunno how to get around this issue. The documentation is terrible. --Mark -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.