Peter Hansen blathered [about whether a .pyc will be regenerated if the path encoded in it changes]: > I take it back... that could be the reason. I just checked and the path > to the .py file is encoded in the .pyc. I don't know if it's actually > used in the decision whether to recompile the .pyc or not (it could just > be for use in showing tracebacks with source), but it's a possibility... > pretty easy to test too.
Well, it doesn't look like that's the case. I have a system happily importing (without regenerating it) a .pyc file that has a now-nonexistent path encoded in it. Even shows tracebacks properly... (now I'm curious what the embedded path is actually used for). -Peter -- http://mail.python.org/mailman/listinfo/python-list
