[PEAK] Socket existence probleme (`v.errno` instead of `v`)

[Phillip J. Eby]

At 11:20 AM 4/22/05 +0200, Alain Poirier wrote:
>Oups, it seems I inverted my diff comparaison. Sorry.
>
> > I find that odd, to say the least; on both Windows and Linux, Python 2.3
> > and 2.4 both end up with 'v' being an OSError instance having an 'errno'
> > attribute equalling ENOENT, when os.unlink is called on a nonexistent
> > filename.
>
>Right. Into the current peak code, the comparaison is `if v<>errno.ENOENT`.
>I changed it by `if v.errno<>errno.ENOENT`.

Weird; I could've sworn that I fixed this specific bit of code a long time 
ago, which is why I was confused by your diff.  Anyway, I've checked in a fix.