#18555: Pickling and otherwise enhancing global options
---------------------------------+------------------------
Reporter: andrew.mathas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.8
Component: interfaces | Resolution:
Keywords: options | Merged in:
Authors: Andrew Mathas | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
---------------------------------+------------------------
Comment (by andrew.mathas):
As I am cleaning this up a related question comes to mind: the name
`GlobelOptions` is a slightly unfortunate because instances of this class
are really just options for an associated family of objects. I can sort of
forgive myself for using this name for the class, but in all of the
instances of this class the associated "parent" classes have a
`global_options` method that points back to its options class. This method
is now being enshrined more firmly inside the code because it is exploited
to allow pickling. I would be happier if these methods were simply called
`options`, rather than `global_options`, even though this change would
necessitate deprecating the existing `global_options` methods.
Thoughts?
--
Ticket URL: <http://trac.sagemath.org/ticket/18555#comment:3>
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.
