Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

diamond is not py3k ready

See original GitHub issue

python3 setup.py build works fine but then running the result:

$ PYTHONPATH=build/lib/ python3 build/scripts-3.5/diamond
  File "build/scripts-3.5/diamond", line 112
    print "Diamond version %s" % (get_diamond_version())
                             ^
SyntaxError: invalid syntax

this is likely just the tip of the iceberg, and there is more work to do to make diamond really py3k ready

Issue Analytics

State:
Created 8 years ago
Comments:19 (12 by maintainers)

Top GitHub Comments

9reactions

jantmancommented, Jan 5, 2020

Python 2.7 is now EOL as well. I’m not sure if Diamond is even still maintained, but it seems like if this project is going to continue than py3 support is pretty much a necessity…

6reactions

sandrotosicommented, Feb 15, 2016

python 2.5/2.6 are dead, so keeping their compatibility (and doing so preventing “progress”) seems the wrong way for a python project.

other than then usual boilerplate of the advantage of py3k, it is anyway the future of the language and a huge amount of work has been done to allow developers to write code that could be executed -without any change- both in 2.7 and 3.3+

There might be also people that would like to only run python3 on their machine (Arch switched /usr/bin/python to python3 long time ago), and given it’s possible to extend with additional collectors, those might be easier written with a py3k-friendly syntax and/or you could gather more collaborations not closing that door in the code.

I wont use expressions like “0 value”/ no value, as it is discouraging and shortsighted.

thanks anyway for your attention