#18514: Upgrade of group cohomology spkg
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-6.8
Component: packages: | Resolution:
optional | Merged in:
Keywords: group cohomology | Reviewers:
Authors: Simon King | Work issues: Create a new-style
Report Upstream: None of the above | package with least effort
- read trac for reasoning. | Commit:
Branch: | cd644a301bd2a9c57b5c719bb47a4733c75e347b
u/SimonKing/upgrade_of_group_cohomology_spkg| Stopgaps:
Dependencies: #12103 |
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:119 jdemeyer]:
> Does it really have to be a pickle? Why not just a Python file?
Well, I could also put it directly into the code (the file is loaded in
exactly one spot in the cohomology code). So, right, I could get rid of
the pickle.
But can the shared database remain in SAGE_SHAR/pGroupCohomology? I think
it is reasonable that the new modular_resolution package shall provide the
cohomology ring data base, even though the actual code to access the data
will only be in the Sage library.
--
Ticket URL: <http://trac.sagemath.org/ticket/18514#comment:120>
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.
