RuntimeError: Bad magic number in .pyc file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. after install
2. first open
3.

What version of the product are you using? On what operating system?
i have ubuntu 9.04 beta
i386
and i use the version 3.0.1

Original issue reported on code.google.com by dansa...@gmail.com on 2 Apr 2009 at 1:46

[GoogleCodeExporter]

Exactly the same problem.
fresh install of ubuntu 9.04 beta

Original comment by Tanga...@gmail.com on 14 Apr 2009 at 8:12

[GoogleCodeExporter]

I am having exactly the same problem under Jaunty :(

Original comment by kos...@gmail.com on 14 Apr 2009 at 7:51

[GoogleCodeExporter]

Exactly the same here! :-(

Original comment by papp...@gmail.com on 15 Apr 2009 at 11:45

[GoogleCodeExporter]

~/$ sopcast-player
RuntimeError: Bad magic number in .pyc file

using sopcast-player_0.2.1-1_i386.deb and sp-auth_3.0.1_i386.deb. medibuntu and 
vlc
up to date and using ubuntu 9.04 jaunty.

Original comment by goo...@post.blinkiz.com on 15 Apr 2009 at 9:27

[GoogleCodeExporter]

Exactly the same issue using sopcast-player_0.2.1-1_i386.deb and 
sp-auth_3.0.1_i386.deb.

Original comment by scou...@gmail.com on 21 Apr 2009 at 9:27

[GoogleCodeExporter]

Guys - solution from the ubuntu forums here
(http://ubuntuforums.org/showthread.php?t=1032901&page=16):

**************
http://ubuntuforums.org/showthread.php?t=1032901&page=16

I saw the same problem since python was updated in Jaunty. Because when Python
compiles, it embeds its magic number in the resulting .pyc, so when that is 
loaded
against another version of python, things go boom.

To fix the problem, go to /usr/share/sopcast-player/lib/ and delete all of the 
.pyc
files. But there is a direct reference to .pyc in the launcher, so you must 
also go
to /usr/bin/sopcast-player, and change .pyc to .py. After that, it should run 
for you.
**************

Tried and worked!

Original comment by scou...@gmail.com on 21 Apr 2009 at 9:32

[GoogleCodeExporter]

Tried what scourou said above and it worked!  Thanks!

Original comment by michael....@gmail.com on 22 Apr 2009 at 3:33

[GoogleCodeExporter]

Thank You scourou!
It works for me too!

Original comment by shaib...@gmail.com on 4 May 2009 at 6:08

[GoogleCodeExporter]

Thanks scourou!
It works for me as well :)

Original comment by druid...@gmail.com on 14 May 2009 at 6:07

[GoogleCodeExporter]

I added a fix to source available via svn. Please verify, thanks.

Original comment by flyguy97 on 17 May 2009 at 8:36

• Changed state: Fixed
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by flyguy97 on 17 May 2009 at 8:39

• Changed state: Started

[GoogleCodeExporter]

Python 2.6+ issues has been fixed and verified with Version 0.3.0.

Original comment by flyguy97 on 6 Jun 2009 at 7:02

• Changed state: Verified

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

For this error message generally:

The magic number comes from UNIX-type systems where the first few bytes of a 
file held a marker indicating the file type.

Python puts a similar marker into its pyc files when it creates them.

Then the python interpreter makes sure this number is correct when loading it.

Anything that damages this magic number will cause your problem. This includes 
editing the pyc file or trying to run a pyc from a different version of python 
(usually later) than your interpreter.

If they're your pyc files, delete them and let the interpreter re-compile the 
py files.

If they're not yours, you'll have to either get the py files or an interpreter 
that can run the pyc files with that particular magic value.

Source: 
http://stackoverflow.com/questions/514371/whats-the-bad-magic-number-error
(08.03.2012, 18:00)

Original comment by Max.matt...@gmail.com on 8 Mar 2012 at 4:59