A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116438.html below:

[Python-Dev] PEP 394 request for pronouncement (python2 symlink in *nix systems)

[Python-Dev] PEP 394 request for pronouncement (python2 symlink in *nix systems) [Python-Dev] PEP 394 request for pronouncement (python2 symlink in *nix systems)Antoine Pitrou solipsis at pitrou.net
Sun Feb 12 17:04:39 CET 2012
Le dimanche 12 février 2012 à 16:52 +0100, "Martin v. Löwis" a écrit :
> > Why hard links? Symlinks are much more introspectable. When looking at
> > a hard link I have no easy way to know it's the same as whatever other
> > file in the same directory.
> 
> There actually *is* an easy way, in regular ls: look at the link count.
> It comes out of ls -l by default, and if it's >1, there will be an
> identical file.

This doesn't tell me which file it is, which is practically useless if I
have both python3.3 and python3.2 in that directory.

> If you look at the patch, you'll notice that the only change is to
> make the links hard links.

This begs the question: why?

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4