python27 cannot be selected

[wsiegrist@…]

After installing python27 and python_select, port select python python27 fails:

# port select python python27 
Selecting 'python27' for 'python' failed: could not create new link "/opt/local/share/man/man1/python.1": target "/opt/local/share/man/man1/python2.7.1" doesn't exist

[wsiegrist@…]

The symlinks in /opt/local/bin do get created, so "fail" is perhaps too strong. I guess it is just the manpage that doesn't get selected.

[snc@…]

I don't get this error. I successfully switched to python27 from each of these: none python24 python25 python26 python26-apple python27.

[wsiegrist@…]

I am on a fresh install of 10.6.4 and MacPorts 1.9.1 and did a selfupdate right before installing. I had no other python ports installed. I notice that I have the following symlink:

/opt/local/share/man/man1/python2.7.1 -> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/share/man/man1/python.1

but the target is missing:

# ls /opt/local/Library/Frameworks/Python.framework/Versions/2.7/share/man/man1/
python2.7.1

... note that the symlink is pointing to python.1 and not python2.7.1

[vince@…]

Python.1 is the expected name for a man 1 file, I think.

[jwa@…]

I don't get this, so I'll close this, will reopen, if need arises

[wsiegrist@…]

Yes, it is still happening.

[jwa@…]

Ok, now I see this, too, will look into it. It is actually bad, because the following steps are not done...

[ryandesign@…]

Did r78352 fix this?

[jmr@…]

Yes.

[glen.henshaw@…]

I'm getting this error again:

ghenshaw$ sudo port select python python27
dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid
Password:
Selecting 'python27' for 'python' failed: could not create new link "/opt/local/bin/python": target "/opt/local/bin/python2.7" doesn't exist
ghenshaw$ ls /opt/local/bin/python2.7
/opt/local/bin/python2.7
ghenshaw$ port installed python*
The following ports are currently installed:
  python27 @2.7.3_1 (active)
  python_select @0.3_2 (active)

However, selecting other port variants works:

ghenshaw$ sudo port select virtualenv virtualenv27
Selecting 'virtualenv27' for 'virtualenv' succeeded. 'virtualenv27' is now active.

Should this be reopened, or am I confused?

[ryandesign@…]

Should this be reopened, or am I confused?

Please file a new ticket. It's a different error message. And the error in this ticket was already resolved almost two years ago.

Also, remember to use WikiFormatting when writing in Trac, and to preview before submitting.