[MacPorts] #50569: Error in pygments after upgrade from 2.0.2_0 to 2.1_0
MacPorts
noreply at macports.org
Mon Feb 8 07:47:13 PST 2016
#50569: Error in pygments after upgrade from 2.0.2_0 to 2.1_0
----------------------------+------------------------
Reporter: rpspringuel@… | Owner: stromnov@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords:
Port: py27-pygments |
----------------------------+------------------------
Comment (by rpspringuel@…):
`/usr/local/bin/pygmentize` is a symlink to
`/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pygmentize`.
I don't recall putting it there, but it actually works, invoking pygments
2.1 after upgrade. It is the `/opt/local/bin/pygmentize` which is
creating the problems. That is not a symlink, and is attempting to invoke
pygments 2.0.2 according to the error traceback (posted above).
Both `PYTHONPATH` and `PYTHONSTARTUP` are empty on my system.
`~/Library/Python` does not exist on my system. Neither does
`~/Library/Frameworks/Python.framework`. As I noted above, I did a
system-wide search for folders named `pygments` and got only two hits (one
inside the calibre application bundle, the other the MacPorts installed
package). A systeme-wide search for folders called `site-packages`
reveals a few more in application bundles, the OS packaged ones
(`/Library/Python/2.7/site-packages` and `/Library/Python/2.6/site-
packages`, both of which contain only the `README`), a
`/opt/local/lib/python2.7/site-packages` (which only contains a folder
called `xcbgen`), the 3.4 folder (another MacPorts installation, well
populated, but not with pygments), and `/opt/X11/lib/python2.6/site-
packages` (which only contains `xcb` and `xcbgen`).
--
Ticket URL: <https://trac.macports.org/ticket/50569#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list