Hi all,
A few others and me have been working for some time now to get matroids
into Sage. We are getting close to the stage where we can submit the code
to Trac for review. Testing today revealed one failing doctest elsewhere in
Sage after we add our code. The reason is that, in our code, we do the
following in some of our Cython modules:
GF3 = GF(3)
GF3_one = GF(3)(1)
This is to achieve a speedup:
sage: GF3 = GF(3)
sage: GF3_one = GF(3)(1)
sage: timeit('x = GF(3)(1)')
625 loops, best of 3: 30.7 µs per loop
sage: timeit('x = GF3(1)')
625 loops, best of 3: 499 ns per loop
sage: timeit('x = GF3_one')
625 loops, best of 3: 38.5 ns per loop
Note that returning such values is something our code spends a major amount
of time on for every single computation, so we absolutely don't want to
slow this part down. Is it ok to change the docstring for the other module
(categories/homset.py) afterwards or should we seek another workaround?
--Stefan.
--
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.
