> > So I'd suggest: > > - to open a trac ticket for the particular issue you have (if you don't > > have a Trac account yet, I can do that for you) > > I don't have a Trac account yet, so that would be good, thanks.
This is now http://trac.sagemath.org/sage_trac/ticket/3892 > > - we open another Trac ticket with the task to 'fix' all the > > random_element methods by adding *args and **kwds. > > > > Thoughts? > > I guess that seems reasonable, modulo the fact that, in order to > determine what keywords you're allowed to specify in a call to > random_element(), you must find out which one is actually being > called, which might not always be straight forward. For example, what > parameters can I specify in a call to random_element() on a matrix > space over a polynomial ring over a quaternion algebra over a finite > field? But probably most of the time it won't be as difficult as that > fictitious example. The alternative would be inventing some kind of > common interface to all random_element() methods, but that is > unlikely to capture all of different possible combinations of > parameters. I don't think we can build a one-size-fits-all interface. The *args, **kwds addition would allow users to pass through args and kwds though, which I assume is good enough for most cases. This is now http://trac.sagemath.org/sage_trac/ticket/3893 Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _www: http://www.informatik.uni-bremen.de/~malb _jab: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
