-
-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modularization of sagelib: Break out a separate package sagemath-polyhedra #32432
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
comment:3
Initial draft. Needs more work to get integers/rationals to work, and need to include vectors/matrices Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
One of the next issues is use of |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
This version compiles now (I had to butcher |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:16
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Removed the branch from the issue description; replaced by #35095 |
…trix_integer_dense` <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes #1234" use "Introduce new method to calculate 1+1" --> ### 📚 Description <!-- Describe your changes here in detail --> <!-- Why is this change required? What problem does it solve? --> This is for the distribution sagemath-polyhedra (#32432) so that it does not have to depend on the flint library. <!-- If it resolves an open issue, please link to the issue here. For example "Closes #1337" --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. - [ ] I have linked an issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open pull requests that this PR logically depends on --> <!-- - #xyz: short description why this is a dependency - #abc: ... --> URL: #35135 Reported by: Matthias Köppe Reviewer(s): Jonathan Kliem, Matthias Köppe
We define a superset of the distribution sagemath-categories (from #29865), called https://pypi.org/project/sagemath-polyhedra/, which is large enough to work with rational polyhedra, including running most doctests
In:
ZZ
,QQ
,RDF
sage.modules
,sage.matrix
to do linear algebra over these ringsinstall_requires
onpplpy
Out:
RDF
sage.symbolic
sage.combinat
(we conditionalize out doctests that use combinatorial examples such as associahedra)sage.graphs
sage.plot
To test:
To run more of the testsuite afterwards:
Follow-up steps:
Depends on #32779
Depends on #34855
Depends on #34849
Depends on #32709
Depends on #34849
Depends on #34931
Depends on #34941
CC: @kliem @tscrim @anneschilling
Component: refactoring
Work Issues: git blame -b --first-parent 32432-base.. src/sage/geometry/polyhedron/base.py
Author: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/32432
The text was updated successfully, but these errors were encountered: