#37995: mapnik and py26-mapnik ---------------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mapnik py26-mapnik | ---------------------------------+------------------------ Comment (by petr@…): Could we get rid of the `py26-mapnik` code by now? It is quite dated now, and mapnik is around for some while. Not sure I understand the issue regarding `replaced_by mapnik`, why this should create any problems due to the API changes. Mapnik seems to have no dependents. The only issue I could think of is that `py26-mapnik` would correspond to mapnik +python26, while the default is +python27. So what would be a smooth exit strategy? -- Ticket URL: <https://trac.macports.org/ticket/37995#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X