This appears to be a change in behavior from Python 2.4 to Python 2.5,
which I can't find documented anywhere. It may be windows only, or
related to Windows behavior.
In 2.4, the current directory (os.curdir) was on sys.path. In 2.5, it
appears to be the base directory of the running script. For
On Feb 26, 7:44 pm, Chris Mellon [EMAIL PROTECTED] wrote:
This appears to be a change in behavior from Python 2.4 to Python 2.5,
which I can't find documented anywhere. It may be windows only, or
related to Windows behavior.
In 2.4, the current directory (os.curdir) was on sys.path. In 2.5,
On 26 Feb 2007 13:00:55 -0800, Ziga Seilnacht [EMAIL PROTECTED] wrote:
On Feb 26, 7:44 pm, Chris Mellon [EMAIL PROTECTED] wrote:
This appears to be a change in behavior from Python 2.4 to Python 2.5,
which I can't find documented anywhere. It may be windows only, or
related to Windows
Chris Mellon wrote:
Considering that it's a backwards incompatible breaking change
(although I understand why it was done), you'd think it deserved
mention in the more prominent Whats new in Python 2.5 section on the
website, in addition to a one-liner in the NEWS file. Ah well, while
I'm
