I noticed that in pari.qfminim; from 9.3 to 9.4 there was a trivial change: the second parameter changed name from 'b' to 'B'. This breaks code that calls it with 'b' as a keyword. I had trouble tracing this change, but it looks like this is in some automatically generated interface.
It's generally not a good idea to break compatibility with such trivial changes. Is this indeed stemming from pari? In that case how does pari get away with it? Do they only have positional arguments? Or do they have a different place where they save their allowed names/aliases for keywords? If this really is a peculiarity of pari that we have to live with, we should perhaps document to not depend on keyword arguments [which, when I checked, people haven't really done for the 'b' parameter, but are doing for the 'flags' parameter]. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/9a9b098a-55f3-4675-968b-3caf77fa607bn%40googlegroups.com.
