On 17-mrt-2006, at 22:14, M.-A. Lemburg wrote: > Martin v. Löwis wrote: >> Thomas Heller wrote: >>> I'm not sure if this is what Marc-Andre means, but maybe these >>> definitions >>> could go into a new include file: >> >> How would that include file be used? You would have to copy it >> into your >> own source base, and include it, right? > > We could put it into a b/w compatibility header file, e.g. > > #include "pycompat.h"
But wouldn't this header be needed on versions of python before 2.5? That would make inclusion of a pycompat.h header with python 2.5 less useful. Including the completed block into the pep would be useful. Ronald > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Mar 17 > 2006) >>>> Python/Zope Consulting and Support ... http:// >>>> www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http:// >>>> zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http:// >>>> python.egenix.com/ > ______________________________________________________________________ > __ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for > free ! :::: > _______________________________________________ > 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/ > ronaldoussoren%40mac.com _______________________________________________ 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
