If I have a script 
foo/bar.py
  import baz

and create a symlink to it, called barhere.py
ln -s foo/bar.py barhere.py

when I run it, it behaves unexpectedly, specifically it behaves differently than if I had copied it here. It prefers to import baz from foo/baz, not from the current folder.

Apparently Python (2.7.2-r3) handles symlinks differently than just looking at the content (everything is a file philosophy in UNIX).

The content of a symbolic symlink is a symbolic reference to another location in the file system.  If you had used a hard link it would certainly work as you expected.

The behavior with respect to symbolic links ought to be documented here:

  http://docs.python.org/using/cmdline.html

but doesn't seem to be.

Specifically, we end up calling os.realpath() (or the C level equivalent) when initialising __main__.__file__ and sys.path[0].

Agreed this behaviour should be documented (and tested!) explicitly.

I've removed Tests from the components list as I don't think it belongs there.

hello guys 
I am facing problem with my sqlite3 database when i make changes it saves the changes for almost 13 hours and then retakes back all the changes that i made, i am using two threads in my code and i am not committing the data but i set the isolation mode to None,
i was using the same queries with mysql database with setting autocommit to on and it was working fine what could be the problem in your opinion?
we searched and ask a lot about this issue but nothing was helpful.