On Wed, Apr 6, 2011 at 1:32 PM, Ville M. Vainio <[email protected]> wrote:
> Better just to convert stuff to cython and start optimizing as appropriate. The problem with pyrex/cython is that we must create the files by hand. Besides being risky, it discourages further development. > 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. pylint seems like the best prior art. It does an adequate job of finding types by double interpretation, but it's too slow to part of every-day workflow. The pypy project is another interesting project, but I am unaware of any part of its tool chain that does what I am attempting. Are there other projects I should know about? > The harder problem is how to make stuff fast once you know the types, > not finding what the types are. To my knowledge, there is nothing that quickly and accurately determines the types of objects in Python programs. Do you of any such tool? Edward -- 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.
