[sage-combinat-devel] Re: Cythoning sage.categories.homset?

2013-03-02 Thread Simon King
On 2013-03-01, Simon King wrote: > Hence, I think I will leave it at a partial cythonisation. ... which is #14214 and needs review. -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails

[sage-combinat-devel] Re: Cythoning sage.categories.homset?

2013-03-01 Thread Simon King
Hi Nicolas, On 2013-03-01, Simon King wrote: >> Altogether, I would aim toward having EndomorphismSubring only inherit >> from the concrete class HomsetWithBase, unless it *really* needs some >> of the speed critical methods of Ring. Or unless, in the short run, it >> depends too much from stuff

[sage-combinat-devel] Re: Cythoning sage.categories.homset?

2013-03-01 Thread Simon King
Hi Nicolas, On 2013-03-01, Nicolas M. Thiery wrote: > In principle +1 on cythoning homset.py. Note: homset.py is mostly > pre-categories code written by non-combinat people; we want them to be > involved in the discussion as they would have more insight. So, ask sage-devel instead? > Altogether

Re: [sage-combinat-devel] Re: Cythoning sage.categories.homset?

2013-03-01 Thread Nicolas M. Thiery
Hi Simon! On Fri, Mar 01, 2013 at 02:50:17PM +, Simon King wrote: > On 2013-03-01, Simon King wrote: > > Is there a reason why the > > transition to Cython should be difficult? Note that @lazy_attribute > > and @cached_method became available to .pyx files, if I am not mistaken. > > S

[sage-combinat-devel] Re: Cythoning sage.categories.homset?

2013-03-01 Thread Simon King
Hi! On 2013-03-01, Simon King wrote: > Is there a reason why the > transition to Cython should be difficult? Note that @lazy_attribute > and @cached_method became available to .pyx files, if I am not mistaken. > So, if such decorators where the only original reason to use Python, then > I certain