On Thu, Mar 5, 2009 at 12:52, Stefan Behnel <stefan...@behnel.de> wrote:
> Benjamin Peterson wrote: > > 2009/3/5 Guido van Rossum <gu...@python.org>: > >> On Thu, Mar 5, 2009 at 2:39 AM, Stefan Behnel <stefan...@behnel.de> > wrote: > >>> And, BTW, I wouldn't mind getting lxml into the stdlib either. > >> No matter how beautiful and fast lxml is, it has one downside where it > >> comes to installing it into the stdlib: it is based on large, complex > >> 3rd party libraries, libxml2 and libxslt. > > > > And 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? I don't think that adding another build dependency for the stdlib, especially for one already with several external dependencies itself, is a good idea. > > or > > 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). -Brett
_______________________________________________ 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
