>> Type inference is a well investigated problem already, so it's useful >> to explore the prior art before using too much time on own research.
I would love to have a lint-like tool that points out type-compatibility problems. Pylint does this, but very slowly. I agree with Guido that pylint is an extremely important part of the Python world. I've studied pylint in detail, and I think it may be possible to do significantly better. Of course, I could be utterly wrong about that. The coding is going well now. I expect to have preliminary results in a few days. If I get another "nasty surprise" like last year nothing much will have been lost. But there is a real chance that the new approach will be much faster... The stuff about pyrex/cython is just something extra. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
