I have started #27926.
I think I leave the base ring business as it is for now. I belive it is
taken care of in many (if not all) places, where the base ring of the
vertices might differ.
Am Dienstag, 4. Juni 2019 11:20:07 UTC+2 schrieb jplab:
>
> Hi Jonathan,
>
> Le lundi 3 juin 2019 23:31:29
Hi Jonathan,
Le lundi 3 juin 2019 23:31:29 UTC+2, vdelecroix a écrit :
>
> 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.
>
+1
> * no need to create one ticket for
Actually, base ring is preserved already. Just assumed it gets lost as well.
The backend is lost though.
Something as
sage: polytopes.dodecahedron(backend='normaliz').pyramid()
will create a polyhedron with backend 'field'.
Am Montag, 3. Juni 2019 23:31:29 UTC+2 schrieb vdelecroix:
>
> To my m
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
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
