Porting 3.0 to 2.6 - from __future__ import super missing?

[andrew cooke]

Hi,

I have some 3.0 code, which I would like to make work with 2.6.
However, there does not seem to be support for the new super() (no
args) via __future__. Is that correct? If so, what's the best way to
handle this?

Thanks,
Andrew

 

[Benjamin Peterson]

Hi,

I have some 3.0 code, which I would like to make work with 2.6.
However, there does not seem to be support for the new super() (no
args) via __future__. Is that correct? If so, what's the best way to
handle this?

Just use the two argument super(): super(MyClass, instance) It's supported in
both versions.

 

[andrew cooke]

andrew cooke <andrew <at> acooke.org> writes:





Just use the two argument super(): super(MyClass, instance) It's supported in
both versions.

Thanks. Any idea how to deal with ABCs? It's sufficient to use a
simple class, but I want to expose an ABC in 3.0 as it will make it
easier for others to extend.

Unfortunately, "metaclass=" is a syntax error in 2.6 so the following
still fails:

from sys import version

if version.startswith('2.'):
class Matcher():
pass
else:
class Matcher(metaclass=ABCMeta):
pass

Andrew

 

[Benjamin Peterson]

Unfortunately, "metaclass=" is a syntax error in 2.6 so the following
still fails:

from sys import version

if version.startswith('2.'):
class Matcher():
pass
else:
class Matcher(metaclass=ABCMeta):
pass

I would suggest that you use the 2.6 syntax, and run "2to3 -f metaclass" on your
code. (ABCs have been backported to 2.6.)

 

[andrew cooke]

I would suggest that you use the 2.6 syntax, and run "2to3 -f metaclass" on your
code. (ABCs have been backported to 2.6.)

Thanks - with that hint I found this -
http://mikewatkins.ca/2008/11/29/py...es/#using-the-metaclass-in-python-2-x-and-3-x

Andrew