Simon King wrote: > Dear Robert, > > On Nov 29, 7:43 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: >> You can't call cdef functions from the Python interpreter. You can >> write a test function, e.g. "_test_mulint." > > Good idea! > > On the other hand, after writing "I wouldn't like to make the method > public", I asked myself *why* I wouldn't. Dunno. > So, I made it 'cpdef', and then the doc test works.
Question for all: is there a good reason for writing cdef functions? Or should we make all cython functions cpdef? Python convention seems to be to expose the internals of the class, but just mark (with "_" or "__") the functions that are considered internal and may change without warning. I'm facing the doctesting dilemma brought up here with some other cdef functions in another class. Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@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-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
