Hi, Brett Cannon wrote: > On Thu, Mar 5, 2009 at 12:52, Stefan Behnel wrote: >> Benjamin Peterson wrote: >>> it depends on Cython, which is wonderful normally, but maybe >>> difficult to deal with in language evolution since we wouldn't have >>> direct control over the C sources. >> I see the point, although I think that this can be dealt with by >> >> a) using a specific, stable release version of Cython for a specific Python >> release, so that this Cython version can be bug fixed if required (it's >> implemented in Python, after all) > > So including Cython source in the stdlib and then check in the generated C > code?
Did I give the impression that a) was my preferred solution? ;) >> b) adding Cython to the stdlib and building with that > > That's an entirely separate discussion (for which my initial answer is to > not consider it until it has stabilized to a 1.0 release). Yes, that *is* an entirely separate discussion - for which my initial answer is to consider it as soon as it is in a state where the compiler is good enough to be useful and the language it compiles is stable enough to be future proof. The language is almost Python, and the core syntax extensions (compared to Python 2.6/3.0) haven't changed for a couple of releases (except for the buffer syntax, which I personally don't consider core but really nice to have). The official goal for a 1.0 release is to compile Python programs, BTW. I don't think the stdlib needs to wait for that. Stefan _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
