inspect.findsource fails after directory change

[kgabor79]

BPO	15931
Nosy	@bitdancer, @1st1
Files	instest.py: Test script

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2014-01-29.20:52:50.038>
created_at = <Date 2012-09-12.15:32:21.978>
labels = ['type-bug', 'library']
title = 'inspect.findsource fails after directory change'
updated_at = <Date 2014-01-30.02:09:18.081>
user = 'https://bugs.python.org/kgabor79'

bugs.python.org fields:

activity = <Date 2014-01-30.02:09:18.081>
actor = 'yselivanov'
assignee = 'none'
closed = True
closed_date = <Date 2014-01-29.20:52:50.038>
closer = 'yselivanov'
components = ['Library (Lib)']
creation = <Date 2012-09-12.15:32:21.978>
creator = 'kgabor79'
dependencies = []
files = ['27179']
hgrepos = []
issue_num = 15931
keywords = []
message_count = 6.0
messages = ['170389', '209678', '209693', '209694', '209697', '209698']
nosy_count = 3.0
nosy_names = ['r.david.murray', 'yselivanov', 'kgabor79']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue15931'
versions = ['Python 2.6', 'Python 2.7']

[kgabor79]

The attached script works in 2.6(.4) but not in 2.7(.3); the script cannot locate its own source code if invoked by relative path and work directory has changed. If line 8 uncommented, everything is fine due to caching.

I think this is related to issue bpo-4050 changes in inspect.py.

~ kgabor$ python ./instest.py

None ./instest.py
Traceback (most recent call last):
  File "./instest.py", line 10, in <module>
    print inspect.getsourcefile(A), inspect.getfile(A),inspect.findsource(A)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/inspect.py", line 529, in findsource
    raise IOError('source code not available')
IOError: source code not available

~ kgabor$ pwd
/Users/kgabor

~ kgabor$ python /Users/kgabor/instest.py

/Users/kgabor/instest.py /Users/kgabor/instest.py (['import inspect\n', 'import os\n', '\n', 'class A:\n', ' def __init__(self):\n', ' self.a=1\n', '\n', '#print inspect.getsourcefile(A),inspect.getfile(A),inspect.findsource(A)\n', "os.chdir('/')\n", 'print inspect.getsourcefile(A), inspect.getfile(A),inspect.findsource(A)\n'], 3)

[1st1]

Sadly, there is nothing we can do about it, as we simply don't have absolute paths in __file__ attributes in your case.

[bitdancer]

Note that this is fixed in 3.4. That is, in 3.4 __file__ paths are made absolute when the import happens.

[1st1]

Hm, maybe just for the imports? This simple script, run it directly:

test.py:

   def foo(): pass
   print(foo.__code__.co_filename)

"$ python3.4 test.py" will still print relative path "test.py".

Hence, if you do 'os.chdir' in the above script, the introspection code will break. There are many similar issues on the tracker, btw.

[bitdancer]

__file__ is absolute for imports, yes. I didn't check co_filename, maybe that needs to be fixed too.

[1st1]

Yes. I'll create an issue for that.