Haoyu Bai, 06.04.2010 08:52:
> I just thinking what could I help for improving Cython. Maybe I am
> thinking the wrong way since I'm not such familiar with the Cython
> design concept yet. However, no one intend to chase non-problems.
I know, sorry if I sounded a bit harsh. What you described certainly
belongs to the issues that we keep dealing with while designing both the
compiler and the language. It's clear that you can't be as familiar with
the design as those who have been working on it for years - no-one expects
you to be, and as Robert said, fresh ideas are always appreciated, and they
often arise from taking an innocent look at existing structures.
There is a certain grey area between the adherence to Python language
principles and what we allow or enforce in the Cython language. The issues
you mentioned can be dealt with by restricting the Cython language, which
simplifies them considerably. It's always a good design principle to keep
things simple, and the solution I proposed ("imports from the 'cython'
module are fixed") keeps things simple to understand for users and simple
in the compiler. They also do not restrict any obvious use cases - why
should you assign something else to a special name that you imported?
Stefan
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
