[MacPorts] #30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ----------------------------------+----------------------------------------- Reporter: jon.tirsen@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: ----------------------------------+----------------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/30187> MacPorts <http://www.macports.org/> Ports system for Mac OS
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ----------------------------------+----------------------------------------- Reporter: jon.tirsen@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: py26-mapnik, py27-mapnik ----------------------------------+----------------------------------------- Changes (by ryandesign@…): * cc: dbsgeo@…, ryandesign@… (added) * port: => py26-mapnik, py27-mapnik Comment: This new py27-mapnik port installs tons of files that conflict with the existing py26-mapnik port, which is not how py* ports are supposed to behave; they're supposed to be simultaneously installable. I'm rather confused why the existing port is called py26-mapnik at all. Why isn't it just called mapnik? We could then discuss whether it should have variants allowing the user to choose the desired python version. The problem with doing so is that it depends on boost having been installed with the corresponding python variant. And of course only one variant of a given port can be active at once. But mapnik is not the only software that uses boost's python features. Therefore all ports using boost's python features must simultaneously be updated to have such python variants. Or we could just decide to update all such ports from python26 to python27 and not give the user a choice. -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ----------------------------------+----------------------------------------- Reporter: jon.tirsen@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: py26-mapnik, py27-mapnik ----------------------------------+----------------------------------------- Comment(by jon.tirsen@…): Maybe the simplest solution is to have just a mapnik port which has two options +python26 and +python27? There's no _simple_ way to install mapnik for two different python versions. (It's possible but would require a lot more work.) -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ----------------------------------+----------------------------------------- Reporter: jon.tirsen@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: py26-mapnik, py27-mapnik ----------------------------------+----------------------------------------- Comment(by dbsgeo@…): Replying to [comment:1 ryandesign@…]:
This new py27-mapnik port installs tons of files that conflict with the existing py26-mapnik port, which is not how py* ports are supposed to behave; they're supposed to be simultaneously installable.
I'm rather confused why the existing port is called py26-mapnik at all. Why isn't it just called mapnik?
because mapnik's python binding are written in C++ (using boost python) and only one version of boost python (per python version) can be installed (at least that is what I though back when the port was submitted). Ideally their should be a libmapnik pure C++ port and a python-mapnik (just the bindings) port.
We could then discuss whether it should have variants allowing the user
to choose the desired python version. The problem with doing so is that it depends on boost having been installed with the corresponding python variant. having boost python be a separate port (or a separate port per python version) would begin to solve this perhaps.
And of course only one variant of a given port can be active at once. But mapnik is not the only software that uses boost's python features. Therefore all ports using boost's python features must simultaneously be updated to have such python variants. Or we could just decide to update all such ports from python26 to python27 and not give the user a choice.
btw, I no longer use macports because I found it way easier to install boost (just the bits mapnik needs) and I know provide binaries for users: http://dbsgeo.com/downloads/#mapnik-0.7.1. So, trying to help here but I'm not an active macports users to not going to be of much help. -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ---------------------------------------+-------------------------------- Reporter: jon.tirsen@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: | Keywords: Port: py26-mapnik, py27-mapnik | ---------------------------------------+-------------------------------- Comment (by petr@…): There is a `mapnik` port @2.2.0 now. So this ticket can probably be closed. And maybe `py26-mapnik` should be deprecated. -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ---------------------------------------+---------------------- Reporter: jon.tirsen@… | Owner: petr@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: | Keywords: Port: py26-mapnik, py27-mapnik | ---------------------------------------+---------------------- Changes (by petr@…): * status: new => assigned * cc: Peter.Danecek@… (removed) * owner: macports-tickets@… => petr@… Comment: Can we close this ticket as wontfix? Any objections? -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ---------------------------------------+---------------------- Reporter: jon.tirsen@… | Owner: petr@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: | Keywords: Port: py26-mapnik, py27-mapnik | ---------------------------------------+---------------------- Comment (by macports@…): Seems to have been overcome by events. I'm okay with closing it. -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
#30187: py27-mapnik 0.7.1 Support python 2.7 for Mapnik ---------------------------------------+-------------------- Reporter: jon.tirsen@… | Owner: petr@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: wontfix | Keywords: Port: py26-mapnik, py27-mapnik | ---------------------------------------+-------------------- Changes (by petr@…): * status: assigned => closed * resolution: => wontfix -- Ticket URL: <https://trac.macports.org/ticket/30187#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts