getcwd problem does not return cwd

[fif0]

BPO	13980
Nosy	@bitdancer
Files	maybe_a_bug.py

^{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 2012-02-09.22:40:50.992>
created_at = <Date 2012-02-09.22:12:58.072>
labels = ['interpreter-core', 'invalid']
title = 'getcwd problem does not return cwd'
updated_at = <Date 2012-02-09.22:40:50.990>
user = 'https://bugs.python.org/fif0'

bugs.python.org fields:

activity = <Date 2012-02-09.22:40:50.990>
actor = 'r.david.murray'
assignee = 'none'
closed = True
closed_date = <Date 2012-02-09.22:40:50.992>
closer = 'r.david.murray'
components = ['Interpreter Core']
creation = <Date 2012-02-09.22:12:58.072>
creator = 'fif0'
dependencies = []
files = ['24472']
hgrepos = []
issue_num = 13980
keywords = []
message_count = 2.0
messages = ['152991', '152995']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'fif0']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue13980'
versions = ['Python 2.7']

[fif0]

Please take a look at the detached file.

At the first call of the methode foo(), path and the second getcwd are the same. After the directory change, the default value path is not the the current working directory.

[bitdancer]

That's just how function definitions in Python work. The prototype is evaluated when the function is defined, not when it is run, so the default value of path will always be the value of getcwd at the time the function *defintion* is done (which will generally be the CWD when python starts, unless you are defining functions at runtime).