pydev debugger: CRITICAL WARNING: This version of python seems to be incorrectly compiled (internal generated filenames are not absolute)

Hi, I've run into the warning above and can't find any information on how to fix it.  I've recently migrated my account to a new Macbook.  Thanks.

Here's a little more from the console:

Connected to pydev debugger (build 117.663)

/System/Library/Frameworks/Python.framework/Versions/2.5/bin/python /Applications/PyCharm.app/helpers/pydev/pydevd.py --client 127.0.0.1 --port 52392 --file /usr/local/google_appengine/dev_appserver.py --high_replication --address=0.0.0.0 --port 8080 .

-------------------------------------------------------------------------------

pydev debugger: CRITICAL WARNING: This version of python seems to be incorrectly compiled (internal generated filenames are not absolute)

pydev debugger: The debugger may still function, but it will work slower and may miss breakpoints.

pydev debugger: Related bug: http://bugs.python.org/issue1666807

-------------------------------------------------------------------------------

pydev debugger: warning: psyco not available for speedups (the debugger will still work correctly, but a bit slower)

pydev debugger: starting

pydev debugger: Unable to find real location for: /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/threading.py

pydev debugger: Unable to find real location for: /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/posixpath.py

pydev debugger: Unable to find real location for: /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/stat.py

12 comments
Comment actions Permalink

Hi Leon, the problem can be caused by corrupted *.pyc files. See http://bugs.python.org/issue1180193 for details.

Try to remove all pyc files from your project.

Please, report if that helped.

0
Comment actions Permalink

Dmitri, thanks again.  After the following steps, I still get the same problem:

  1. Deleted all the .pyc files in my project using: find . -name '*.pyc' -delete
  2. Removed the 2.5 interpreter from PyCharm and then added it back and made it the Project Interpreter
  3. Ran my project in Debug mode and still get similar output to what I provided before.(I did notice it doesn't seem to have generated any new .pyc files?)

Afterwards, I did also run the Python 2.5.4 installer (on top of 2.5.6 which was is was on my machine).  But when I then go into Python Interpreters, and remove and add 2.5 back, it still shows as 2.5.6.  I assume it should show 2.5.4?  Do I need to uninstall 2.5.6 first?  And if so, for this Mac newbie, what's the simplest way to do that?

0
Comment actions Permalink

The Python installed by user should be located in different place then system default python, namely /Library/Frameworks

0
Comment actions Permalink

I'm having trouble getting Mac Python 2.5.4 installed and configured into PyCharm. I thought I had found the files Mac Python installed at /usr/local/bin, and pointed PyCharm to the file, "python", in that directory.  But it looks like that file just points to the original 2.5.6 python that I'm trying to switch away from.  I attached a screen shot of my python debug configuration dialog.  you can see that it shows that it's python2.5.4, but it's pointing to the original 2.5 framework directory.  And when i debug, the console still has all the same out as i posted before.  Clearly i'm missing something.  thanks again.



Attachment(s):
screenShotPyCharmDebugConfigDialog.jpg
0
Comment actions Permalink

I thought I'd send a little more information -- still having this problem.  Please see attachment. Any help appreciated.  Thanks.



Attachment(s):
pythoncriticalwarning.jpg
0
Comment actions Permalink

Hi Leon,

what is your Mac OSX version?

Thanks

Vaclav

0
Comment actions Permalink

10.7.4.  thanks.

0
Comment actions Permalink

Hi Leon,

your Python configuration should look like following output. If you have other values, your Python environment is incorrect:

+ which python

/usr/bin/python

+ ls -la /usr/bin/python

-rwxr-xr-x  2 root  wheel  62752  1 úno 19:32 /usr/bin/python

+ python --version

Python 2.7.1

+ file /usr/bin/python

/usr/bin/python: Mach-O universal binary with 2 architectures

/usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64

/usr/bin/python (for architecture i386): Mach-O executable i386

+ which python2.7

/usr/bin/python2.7

+ ls -la /usr/bin/python2.7

lrwxr-xr-x  1 root  wheel  75  1 úno 19:32 /usr/bin/python2.7 -> ../../System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7

+ python2.7 --version

Python 2.7.1

+ file /usr/bin/python2.7

/usr/bin/python2.7: Mach-O universal binary with 2 architectures

/usr/bin/python2.7 (for architecture x86_64): Mach-O 64-bit executable x86_64

/usr/bin/python2.7 (for architecture i386): Mach-O executable i386

+ which python2.6

/usr/bin/python2.6

+ ls -la /usr/bin/python2.6

lrwxr-xr-x  1 root  wheel  75  1 úno 19:32 /usr/bin/python2.6 -> ../../System/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6

+ python2.6 --version

Python 2.6.7

+ file /usr/bin/python2.6

/usr/bin/python2.6: Mach-O universal binary with 2 architectures

/usr/bin/python2.6 (for architecture x86_64): Mach-O 64-bit executable x86_64

/usr/bin/python2.6 (for architecture i386): Mach-O executable i386

+ which python2.5

/usr/bin/python2.5

+ ls -la /usr/bin/python2.5

lrwxr-xr-x  1 root  wheel  75  1 úno 19:32 /usr/bin/python2.5 -> ../../System/Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5

+ python2.5 --version

Python 2.5.6

+ file /usr/bin/python2.5

/usr/bin/python2.5: Mach-O executable i386

Regards
Vaclav
0
Comment actions Permalink

Vaclav, and Dmitry, thanks for the information.  I wanted to give you an update -- I reinstalled OSX this morning hoping a reinstall of the OS-supplied python would fix it, but it didn't. 

Is it a good idea to reinstall PyCharm?  And google app engine as well?  If so, do i need to uninstall first?  Thanks again.  -Leon

0
Comment actions Permalink

Sorry, I didn't see this first post of yours earlier.  Here are the results of running the same terminal commands.  I'm currently using python 2.5 -- please let me know if any of these values look problematic:

Leons-MacBook-Pro:~ lcampise$ which python

/Library/Frameworks/Python.framework/Versions/Current/bin/python

Leons-MacBook-Pro:~ lcampise$ ls -la /usr/bin/python2.7

lrwxr-xr-x  1 root  wheel  75 Jul 16 11:52 /usr/bin/python2.7 -> ../../System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7

Leons-MacBook-Pro:~ lcampise$ which python

/Library/Frameworks/Python.framework/Versions/Current/bin/python

Leons-MacBook-Pro:~ lcampise$ ls -la /usr/bin/python

-rwxr-xr-x  2 root  wheel  62752 Jul 16 11:52 /usr/bin/python

Leons-MacBook-Pro:~ lcampise$ python --version

Python 2.5.4

Leons-MacBook-Pro:~ lcampise$ file /usr/bin/python

/usr/bin/python: Mach-O universal binary with 2 architectures

/usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64

/usr/bin/python (for architecture i386): Mach-O executable i386

Leons-MacBook-Pro:~ lcampise$ which python2.7

/usr/bin/python2.7

Leons-MacBook-Pro:~ lcampise$ ls -la /usr/bin/python2.7

lrwxr-xr-x  1 root  wheel  75 Jul 16 11:52 /usr/bin/python2.7 -> ../../System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7

Leons-MacBook-Pro:~ lcampise$ python2.7 --version

Python 2.7.1

Leons-MacBook-Pro:~ lcampise$ file /usr/bin/python2.7

/usr/bin/python2.7: Mach-O universal binary with 2 architectures

/usr/bin/python2.7 (for architecture x86_64): Mach-O 64-bit executable x86_64

/usr/bin/python2.7 (for architecture i386): Mach-O executable i386

Leons-MacBook-Pro:~ lcampise$ which python2.6

/usr/bin/python2.6

Leons-MacBook-Pro:~ lcampise$ ls -la /usr/bin/python2.6

lrwxr-xr-x  1 root  wheel  75 Jul 16 11:52 /usr/bin/python2.6 -> ../../System/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6

Leons-MacBook-Pro:~ lcampise$ python2.6 --version

Python 2.6.7

Leons-MacBook-Pro:~ lcampise$ file /usr/bin/python2.6

/usr/bin/python2.6: Mach-O universal binary with 2 architectures

/usr/bin/python2.6 (for architecture x86_64): Mach-O 64-bit executable x86_64

/usr/bin/python2.6 (for architecture i386): Mach-O executable i386

Leons-MacBook-Pro:~ lcampise$ which python2.5

/Library/Frameworks/Python.framework/Versions/Current/bin/python2.5

Leons-MacBook-Pro:~ lcampise$ ls -la /usr/bin/python2.5

lrwxr-xr-x  1 root  wheel  75 Jul 16 11:52 /usr/bin/python2.5 -> ../../System/Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5

Leons-MacBook-Pro:~ lcampise$ python2.5 --version

Python 2.5.4

Leons-MacBook-Pro:~ lcampise$ file /usr/bin/python2.5

/usr/bin/python2.5: Mach-O executable i386

0
Comment actions Permalink

I'm happy to report that the Critical Warning issue is gone.  I just re-cloned my repository, then re-installed google app engine.  And after that, it was fixed.  I wish I could say more specifically what was broken and what fixed it.  Thanks again for all the help.

0

Please sign in to leave a comment.