librsvg incompatible with Python 3

[gale@…]

The python script rsvg uses the shell bang

#!/usr/bin/env python

to access the python interpreter. So it gets whatever version of python is currently selected as current in MacPorts. But this script is not compatible with version >= 3.0 of Python: the script contains a print statement, but print has changed to a function in version >= 3.0 of Python. There may be additional incompatibilities, I have not checked.

Note that this also implies that this port has a runtime dependency on Python which is missing from the portfile.

See also #19441.

[nox@…]

That should be reported upstream instead of here.

[gale@…]

Replying to nox@…:

That should be reported upstream instead of here.

OK, reported as ​http://bugzilla.gnome.org/show_bug.cgi?id=580325 .

But I'm not sure they'll fix it so fast, it is more of a problem on MacPorts; see my comments to #199441.

[(none)]

Milestone Port Bugs deleted

[tobypeterson]

This is not really a bug - setting your default 'python' to Python 3.x is just asking for trouble.

[gale@…]

Why? Various versions of Python 3 have been considered "stable production versions" of Python for a long time now. Anyone doing serious development in Python will consider doing this.

When a package/port depends on a legacy version, the standard behavior for packaging systems is to provide that dependency to the specific package, not to downgrade the entire system. That's why upstream considers this a MacPorts bug.

But if it's really true that MacPorts won't support setting Python 3 as the default, then doing that should be removed as an option. As long as MacPorts officially supports setting Python 3 as the default - which I maintain it should - then this is certainly a bug in my opinion.

Fact - when I configure my MacPorts in a reasonable and supported way, this package fails to build. Please explain why that's not a bug.

[blb@…]

Should be fixed in r55356.