ipython3 port not working ?

Ryan Schmidt ryandesign at macports.org
Tue Dec 4 23:30:29 PST 2012

On Dec 4, 2012, at 00:50, Sean Farley wrote:
> On Mon, Dec 3, 2012 at 11:06 PM, Trémouilles David wrote:
>> I "sudo install py33-ipython" without any issue but
>> when I try to launch ipython3 I get an error:
>> ~ $ ipython3-3.3
>> -bash: /opt/local/bin/ipython3-3.3:
>> /Volumes/work/macports/Library/Frameworks/Python.framework/Versions/3.3/bin/py:
>> bad interpreter: No such file or directory
> This looks odd to me: /Volumes/work/macports. You have
> /opt/local/bin/ipython3-3.3 installed but it's looking for something
> in /Volumes/.../macports?

Yes this is odd. /Volumes/work/macports is part of the infrastructure the buildbots use. This path should not be appearing in ports, but you can verify by downloading the packages from http://packages.macports.org/py33-ipython/ that for some reason this path is baked into several of the scripts:


I see this problem in both py33-ipython-0.13_1.darwin_10.noarch and py33-ipython-0.13_1.darwin_11.noarch, so the problem does not appear limited to one buildbot or OS version.

I do not see the problem in py27-ipython-0.13_1+scientific.darwin_11.noarch or py32-ipython-0.13_1.darwin_11.noarch, so the problem may be limited to Python 3.3.

It's also possible that there was coincidentally a misconfiguration of the buildbots on October 4 when the py33-ipython ports were built (in response to r98398) and that rebuilding them would fix it.

Please file a bug report in our issue tracker as usual.

I don't know if updating ipython to 0.13.1 might help but that would be a good first step, since it would have the side effect of causing the buildbots to rebuild the ports:


More information about the macports-users mailing list