bad magic number in 'six' about six HOT 4 CLOSED

@chrisdamato I ran into this today. The culprit ended up being a /usr/bin/six.pyc file. This seems to have been created by the VMware Perl SDK installation process. Go figure.

Once I removed that file, the error went away.

from six.

When you run e.g. dnf or any other commend that is written in Python and installed in /usr/bin, Python adds /usr/bin as sys.path[0]. When a file called six.pyc exists in there, it is imported instead of six and the import fails.

We (Fedora) would like to start using a flag in shebang lines of Python scripts installed in /usr/bin that would prevent this undesired behavior, but such flag does not exist yet (-I does that, but it also does other things). I've asked for such flag many winters ago in https://discuss.python.org/t/python-flag-envvar-not-to-put-current-directory-to-sys-path-but-dont-ignore-pythonpath/4235

from six.

I've opened rpm-software-management/dnf#1815 for dnf specifically, but this can happen to any Python script residing in a directory like /usr/bin.

from six.

I've also opened https://discuss.python.org/t/should-console-scripts-entry-points-exclude-the-scripts-directory-from-sys-path/13896 for console_scripts entry points (which dnf is not)

from six.