Hello, I don't know if this is the right place to submit bugs.
I have consistently reproduced the following bug: using set_block when matrix space is on a given NumberField or an extension field (at least when there are multiple generators) works as expected the first time (in a sage session) but fails the second time (with the same base field) and then ever after until "restart" is called. Here is an example code snipet: F.<r2,r3> = NumberField([x^2 - 2, x^2 - 3]) M = Matrix(F, 8, 8) block = Matrix(F, [ [r2, r3 ] ]) M.set_block(2, 2, block)) # OK the first time M = Matrix(F, 8, 8) block = Matrix(F, [ [r2, r3 ] ]) M.set_block(2, 2, block)) # KO this time #refresh the session/sheet restart F.<r2,r3> = NumberField([x^2 - 2, x^2 - 3]) M = Matrix(F, 8, 8) block = Matrix(F, [ [r2, r3 ] ]) M.set_block(2, 2, block)) # OK again After some investigation with the help of SageMathCell, it seems that at some point the test: M.parent().base_ring() is block.parent().base_ring() fails this test is used by (some function called by the) set_block method which raises an exception I never reproduced this with basic fields (QQ, RR, QQbar...) and when the extension was monogenic -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
