The problem of not being able to select python34 has been fixed with the latest
update to python34.
On 2 Nov 2013 21:54:47 -0500, Ryan Schmidt wrote:
> On Nov 2, 2013, at 21:53, Murray Eisenberg wrote:
>
>> On Nov 2, 2013, at 8:49 PM, Ryan Schmidt wrote:
>>
>>> On Nov 2, 2013, at 19:21, Murra
On Nov 2, 2013, at 21:53, Murray Eisenberg wrote:
> On Nov 2, 2013, at 8:49 PM, Ryan Schmidt wrote:
>
>> On Nov 2, 2013, at 19:21, Murray Eisenberg wrote:
>>
>>> But
>>>
>>> sudo port select —set python python34
>>>
>>> give error:
>>>
>>> Selecting ‘python34' for 'python' failed: could not c
Bug for what: python34? python_select?
On Nov 2, 2013, at 8:49 PM, Ryan Schmidt wrote:
>
> On Nov 2, 2013, at 19:21, Murray Eisenberg wrote:
>
>> In a clean install of MacPorts 2.2.1 into OS X Mavericks, I’ve installed
>> ports python34 (as well as python33 and python27) and python_select.
On Nov 2, 2013, at 19:21, Murray Eisenberg wrote:
> In a clean install of MacPorts 2.2.1 into OS X Mavericks, I’ve installed
> ports python34 (as well as python33 and python27) and python_select. And
>
> sudo port select —list python
>
> gives:
>
> Available versions for python:
> no
In a clean install of MacPorts 2.2.1 into OS X Mavericks, I’ve installed ports
python34 (as well as python33 and python27) and python_select. And
sudo port select —list python
gives:
Available versions for python:
none
python25-apple
python26-apple
python27