[Python-Dev] [PEPs] Rebooting PEP 394 (aka Support the /usr/bin/python2 symlink upstream) (original) (raw)
Éric Araujo merwok at netwok.org
Tue Jul 26 18:15:15 CEST 2011
- Previous message: [Python-Dev] [PEPs] Rebooting PEP 394 (aka Support the /usr/bin/python2 symlink upstream)
- Next message: [Python-Dev] [PEPs] Rebooting PEP 394 (aka Support the /usr/bin/python2 symlink upstream)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le 26/07/2011 18:05, Antoine Pitrou a écrit :
Le mardi 26 juillet 2011 à 10:56 -0500, Kerrick Staley a écrit :
I'm indifferent either way. python3 is a hard link to python3.2, so I thought we'd make everything that way for consistency. Is it? Yikes, I didn't know about that.
Yikes for me too. I’ve had a quick look at the Makefile (look for $(LN)) and found that all scripts use symbolic links, but the python3 to python3.y link is hard. I wonder why this is.
FTR, downstream packagers may change this. Example on Debian:
/usr/bin/python3: symbolic link to python3.2' /usr/bin/python3.2: symbolic link to python3.2mu'
Cheers
- Previous message: [Python-Dev] [PEPs] Rebooting PEP 394 (aka Support the /usr/bin/python2 symlink upstream)
- Next message: [Python-Dev] [PEPs] Rebooting PEP 394 (aka Support the /usr/bin/python2 symlink upstream)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]