#15448: cartesian products of projective space
-------------------------------------+-------------------------------------
Reporter: bhutz | Owner: bhutz
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: algebraic | Resolution:
geometry | Merged in:
Keywords: | Reviewers:
Authors: Ben Hutz | Work issues:
Report Upstream: N/A | Commit:
Branch: | 1a84aa7bd51de2ecf645d0e293398b14ef1df3e7
u/bhutz/ticket/15448 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by bhutz):
After some more looking, the biggest difference is that I've based
everything off of projective_space functionality. I really do prefer that
approach (this makes affine patches, morphisms, etc. much easier to work
with) and I don't think it will have much, if any, affect on how you've
done complete intersections.
Here is what I'd like to do in an ideal world:
- take your first commit and basically move it into my branch. However,
I'd still like to build off of projective space. I can integrate any of
your additional functionality and merge the differences in our approaches.
- then you could have your ticket be just the complete intersection
portion with this ticket as a dependency. You'll probably have to make a
few minor adjustments, but I don't think it will be too much.
As I said above, I'm also open to other suggestions.
--
Ticket URL: <http://trac.sagemath.org/ticket/15448#comment:14>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
