Another person also had this problem at first, and when he removed the files (rm *.pyc */*.pyc) the problem was solved. I have also tested it and it seems to work for me too. Are you absolutely sure that there are no .pyc files left somewhere? does find . -iname "*.pyc" return no result? I sure hope some .pyc files were left, because I cannot seem to reproduce this error.
- Mar 26 2008
Another person also had this problem at first, and when he removed the files (rm *.pyc */*.pyc) the problem was solved. I have also tested it and it seems to work for me too. Are you absolutely sure that there are no .pyc files left somewhere? does find . -iname "*.pyc" return no result? I sure hope some .pyc files were left, because I cannot seem to reproduce this error.
- Mar 26 2008
Thank you for your comment! I really appreciate feedback. I'm was so stupid as to provide the .pyc bytecode files in the tarball, I forgot to remove them. The new tarballs on the website are correct. You could also do, in th eggy directory: rm *.pyc */*.pyc
Please let me know if this solves your problem.
Apologies for the inconvenience. - Mar 26 2008
Please let me know if this solves your problem.
Apologies for the inconvenience. - Mar 26 2008