It would be nice if we could implement the syntax in the IPython
configuration stuff:
A.options.foobar = 1
in addition to
A.options(foobar=1)
This would require us to rename the existing methods of GlobalOptions with
underscores.
Also, for consistency we should recommend / enforce a name for the options.
Should it be A.options or A.global_options or what? The docs use various
conventions.
On Friday, April 12, 2013 2:17:35 AM UTC+1, Andrew Mathas wrote:
>
> Dear Developers,
>
> As part of the clean up of the partitions code by Travis (Trac
> 13605<http://trac.sagemath.org/sage_trac/ticket/13605>)
> I implemented a generic options interface in sage which can be used for
> controlling (global) options for sage objects. See
> sage.structure.global_options for details. This patch, including the
> global_options, was merged in sage-5.8.beta3.
>
> Novosel has just complained, quite justifiably, on the ticket above that
> the global options should have been given their own ticket rather than
> being hidden in a large patch. Apologies for this, but these options just
> grew as part of my review patch with fine tune-tuning (and reviewing) from
> Travis and Nicolas at ICERM...
>
> Given the obscure manner in which this options framework has entered sage,
> and Novosel's comment on the ticket, I now take the opportunity to
> advertise them.
>
> Andrew
>
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
