The looming Python 3(000) monster

[Daniel P. Berrange]

On Fri, Dec 05, 2008 at 03:11:34PM +0000, Richard W.M. Jones wrote:
> On Fri, Dec 05, 2008 at 09:56:39AM -0500, Michael DeHaan wrote:
> > So it means we can't dual maintain code easily between two  
> > branches/versions.
> 
> Isn't it the case that you can use 3.x features in 2.6, using the
> 'from future import ...' syntax?

Which isn't much help if python 2.3, 2.4 and 2.5 don't support
'from future import' and you care about shipping stuff that works
on the 99% of deployed Linux boxes today which don't have 2.6
let alone 3.0.


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|