I'm working on Trac:16838 to clean up/fix the affine_patch and projective_embedding functionality. It is all reasonably straight forward so far, but there was an existing behavior that I've come across that I'd like to change, so I'm checking in here to see if there is a particular reason why it is the way it is.
When calling X.projective_embedding() on an affine subscheme you can pass in an optional parameter which is a projective subscheme which will be the image of the resulting morphism. It seems to me that one would rather pass in the projective space where you want it to live, since if you already knew the projective subscheme why would you be calling this function? Whereas, it seems reasonable that you would want to be sure that it was in the 'right' ambient projective space. Comments? -Ben -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
