Robert Brewer wrote: > Eric Smith wrote: >> Robert Brewer wrote: >>> Postgres bytea coercion is a frequent use case for oct() in my > world. >>> But I agree we don't need two versions. >> Unless you're trying to write code to work with both 2.6 and 3.0. > > Who would try that when PEP 3000 says (in bold type no less): > > There is no requirement that Python 2.6 code will run unmodified > on Python 3.0. Not even a subset. > > ?
Yes, but it also describes the "recommended development model for a project that needs to support Python 2.6 and 3.0 simultaneously". That is to run 2to3 on 2.6 code (which is -3 clean), and not edit the resulting code. I'm trying to enable that for code which wants to use some (small) 3.0 features. I don't see the harm in that. I think this means that the existing oct and hex builtins should raise a -3 warning. The future_builtins version would not raise a warning. Eric. _______________________________________________ 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
