Unified Python portgroup

Freek Dijkstra software at macfreek.nl
Thu Jan 10 15:04:20 PST 2013


On 10-01-2013 23:57, Jeremy Lavergne wrote:

>> [...] "python.versions 25 26 27". To my surprise the
>> following command was accepted:
>>
>>> [root at lampje] Code/macports/py-pdfrw# port install subport=py32-pdfrw
>>> --->  Computing dependencies for py32-pdfrw
[...]
>>> --->  Configuring py32-pdfrw
>>> --->  Building py32-pdfrw
>>> --->  Staging py32-pdfrw into destroot
>>> --->  Installing py32-pdfrw @0.1_1
>>> --->  Activating py32-pdfrw @0.1_1

> Unexpected, I should think. I'd also check that the files installed are actually for python32:
> port contents py32-pdfrw

Yes, they are:

> [root at lampje] Code/macports/py-pdfrw# port contents py32-pdfrw
> Port py32-pdfrw contains:
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw-0.1-py3.2.egg-info
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__init__.py
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__pycache__/__init__.cpython-32.pyc
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__pycache__/buildxobj.cpython-32.pyc
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__pycache__/compress.cpython-32.pyc
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__pycache__/errors.cpython-32.pyc
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__pycache__/tokens.cpython-32.pyc
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/__pycache__/toreportlab.cpython-32.pyc
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/buildxobj.py
>   /opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pdfrw/compress.py
[...]

I don't see this as a big issue, but perhaps a warning is in order.

Regards,
Freek



More information about the macports-dev mailing list