[issue14547] Python symlink to script behaves unexpectedly

2021-06-08 Thread ِAbdulrahman ِShawa
ِAbdulrahman ِShawa added the comment: 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

[issue14547] Python symlink to script behaves unexpectedly

2019-03-15 Thread Mark Lawrence
Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14547] Python symlink to script behaves unexpectedly

2014-06-29 Thread Mark Lawrence
Mark Lawrence added the comment: I've removed Tests from the components list as I don't think it belongs there. -- components: -Tests nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker

[issue14547] Python symlink to script behaves unexpectedly

2012-04-13 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14547 ___ ___ Python-bugs-list

[issue14547] Python symlink to script behaves unexpectedly

2012-04-11 Thread Johannes Buchner
New submission from Johannes Buchner buchner.johan...@gmx.at: 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

[issue14547] Python symlink to script behaves unexpectedly

2012-04-11 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: 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

[issue14547] Python symlink to script behaves unexpectedly

2012-04-11 Thread Nick Coghlan
Nick Coghlan ncogh...@gmail.com added the comment: 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. -- assignee: - docs@python