Closed dummys closed 5 years ago
It doesn't support yet Python 3.
ok so why you didnt use as shebang: #!/usr/bin/env python2
?
Because on ubuntu default now is python2 and on arch for example default is python3
Because I've never considered it a problem and it doesn't support exclusively Linux but also *BSD and MacOSX. Let me search what is the truly multi-platform portable shebang if any...
Oh yeah, let me try to search for it too.
Found it: https://blogs.gnome.org/mcatanzaro/2018/02/16/on-python-shebangs/
So, according to this and other articles, the one that works everywhere is "#!/usr/bin/env python2.7". Patching...
yes same information here: https://stackoverflow.com/questions/2429511/why-do-people-write-the-usr-bin-env-python-shebang-on-the-first-line-of-a-pyt
Another question, under PEP8 it is statuated to use 4 spaces for indent. why use only 2 ?
PS: I relaunched on my other source code where I had the utf8 problem, it is solved. thanks
Extracted from this link: "Fun fact: Google's internal style guideline dictates indenting by 2 spaces!"
ahahahah, google is evil.
quick question not related, where is the best way to contact you to have a rapid chat on diaphora ? tried twitter...
Iirc, PEP also states using whatever currently exists is preferable so it's only ever an argument for when starting a new project, not updating an existing one.
-> $ ./srcbindiff.py -create Traceback (most recent call last): File "./srcbindiff.py", line 7, in
import popen2
ModuleNotFoundError: No module named 'popen2'