[EMAIL PROTECTED] ha escrito: > At http://www-03.ibm.com/developerworks/blogs/page/davidmertz David > Mertz writes > > "Presumably with 2.7 (and later 2.x versions), there will be a means of > warning developers of constructs that are likely to cause porting > issues [to Python 3000]. In the simplest case, this will include > deprecated functions and syntax constructs. But presumably the warnings > may cover "potential problems" like the above example." > > The current beta version of Python is 2.5 . How can a Python programmer > minimize the number of changes that will be needed to run his code in > Python 3000? In general, he should know what is being removed from > Python 3000 and if possible use the "modern" analogs in Python. A > manager of Python programmers might want external evidence of > portability, though (such as an absence of interpreter warnings). > > Some basic syntax such as > > print "hello world" > > is going away to make print look like a function. IMO, fixing what is > not broken because of the aesthetic tastes of the BDFL is a bad idea. > His reasoning is at > http://mail.python.org/pipermail/python-dev/2005-September/056154.html > .
Check this out: http://video.google.com/videoplay?docid=-6459339159268485356 Additionaly, you can make a simple Google search: "guido python 3000" There is quite a lot of information. Hope this helps... LUIS -- http://mail.python.org/mailman/listinfo/python-list