Re: A couple of questions about pyrex

Changing features dramatically could cause a lot of troubles. I wonder if everybody will be happy with this:

Simply allow 'class MyClass' to be equivalent to 'cdef class MyClass' when appropriate (e.g. when the body of the class contain some 'cdef' statements).


yingjie


--- On Tue, 5/12/09, Stefan Behnel <[email protected]> wrote:

> From: Stefan Behnel <[email protected]>
> Subject: Re: [Pyrex] A couple of questions about pyrex
> To: [email protected]
> Cc: "Greg Ewing" <[email protected]>, [email protected]
> Date: Tuesday, May 12, 2009, 5:18 PM
> Yingjie Lan wrote:
> > If 'cdef' define a function hidden from
> python,
> > why 'cdef class' define a class for python?
> > I would expect 'cdef class' define an
> invisible
> > class (for internal use of the module) in a
> > pythonic way (making things easier).
> 
> This is a major FAQ in Pyrex. Yes, this is inconsistent,
> but it's the way
> it is and it will not change. It also makes it hard to find
> a syntax to
> define 'private' (module-internal) classes,
> although there will hopefully
> be such a syntax one day (this has also been discussed
> many, many times).
> 
> Stefan