To my mind: * backend and base ring should be preserved by default. Of course it should make sense: a translation by sqrt(2) would break the base ring QQ.
* no need to create one ticket for each method if this is mostly the same action to be done for each of them. If some method needs special care or give rise to discussions, a specific ticket could be open. Vincent Le 03/06/2019 à 23:25, 'Jonathan Kliem' via sage-devel a écrit :
At the moment the backend setting is lost, when constructing a pyramid of a Polyhedron. Same holds for all other constructions. I think that all constructions should respect the backend of self. I intend to create tickets (one by one) for each construction in Polyhedron_base (that gives a new Polyhedron). Any thoughts on this? Also I think the base ring should be respected as well (as is done in Polyhedron.translation). At the moment it can happen, that the base ring shrinks, when constructing a pyramid for example (if the user forced base ring QQ, there might have been good reason for doing so, and I would say it is not nice, if one has to change base ring again along the way).
-- 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 https://groups.google.com/group/sage-devel. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/c7a13664-9927-0e9c-f51d-4979aa014318%40gmail.com. For more options, visit https://groups.google.com/d/optout.
