This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author valhallasw
Recipients brian.curtin, dawidjoubert, ezio.melotti, tim.golden, valhallasw
Date 2012-05-22.14:20:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAL2-1hBoxJEj5SNswDZ4PBCPmKJc=fuM7RKzdCQfz8CJkVzOFw@mail.gmail.com>
In-reply-to <1337651968.09.0.643192521266.issue4198@psf.upfronthosting.co.za>
Content
OK, I did some quick tests. Given a samba share with the following files

A (contents: 'test: A')
a (contents: 'test: a')
B (contents: 'test: B')

1) opening \\share\files\A or \\share\files\a opens the same file - in my
case 'test: A'
2) opening \\share\files\B or \\share\files\b both work.

As such, the behaviour is at least not incorrect. In addition, it means
that the "if normcase(path1) == normcase(path2):" option to check if two
files are the same is actually correct (if normcase(path1) ==
normcase(path2) then open(path1).read() == open(path2).read() - at least on
the share I tested). Interestingly, os.path.samefile suggests this would
not be the case:

True
>>> os.path.samefile("u:\\a", "u:\\A")
False

On 22 May 2012 03:59, Ezio Melotti <report@bugs.python.org> wrote:

>
> Changes by Ezio Melotti <ezio.melotti@gmail.com>:
>
>
> ----------
> nosy: +brian.curtin, tim.golden
> stage:  -> needs patch
> versions:  -Python 3.4
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue4198>
> _______________________________________
>
History
Date User Action Args
2012-05-22 14:20:09valhallaswsetrecipients: + valhallasw, tim.golden, ezio.melotti, dawidjoubert, brian.curtin
2012-05-22 14:20:09valhallaswlinkissue4198 messages
2012-05-22 14:20:08valhallaswcreate