search

mapproxy / mapproxy-webconf

Small Webconfigruation for MapProxy
Apache License 2.0
11 stars 6 forks source link

MapProxy webconf support for Python 3 #1

Open inglese0026 opened 9 years ago

inglese0026 commented 9 years ago

I appears that mapproxy webconf is not supported in Python 3 currently through one of the dependencies, scriptine-0.2.0. I've opened an issue within the scriptine project noting the discrepancy (https://github.com/olt/scriptine/issues/2). Are there any plans to support webconf within Python 3?

olt commented 9 years ago

We removed scriptine as a dependency. You now need to use mapproxy-webconf serve-develop instead of the manage.py script. Though, MapProxy-WebConf still does not support Python 3 and we currently have no plans to add support for it.

inglese0026 commented 9 years ago

Thank you Oliver,

The serve-develop is using the internal webserver that comes with MapProxy, how do you link it into an external http server? Also, are there any plans to integrate webconf with mapproxy? Being that mapproxy has added support for Python 3, I'm curious as to the reason that webconf is not projected at this point to support Python 3?

Respectfully,

Charlie Inglese charles.inglese@rgi-corp.commailto:charles.inglese@rgi-corp.com Business: 443.564.5055

From: Oliver Tonnhofer notifications@github.com Sent: Thursday, May 28, 2015 10:48 AM To: mapproxy/mapproxy-webconf Cc: Inglese, Charlie Subject: Re: [mapproxy-webconf] MapProxy webconf support for Python 3 (#1)

We removed scriptine as a dependency. You now need to use mapproxy-webconf serve-develop instead of the manage.py script. Though, MapProxy-WebConf still does not support Python 3 and we currently have no plans to add support for it.

Reply to this email directly or view it on GitHubhttps://github.com/mapproxy/mapproxy-webconf/issues/1#issuecomment-106371067.

olt commented 9 years ago

There is a make_wsgi_app in mapproxy_webconf.app similar to MapProxy.

We started with WebConf before we started porting MapProxy to Python 3. That's the only reason it doesn't support Python 3 right now.

We have plans to improve the integration with MapProxy. But there is currently no roadmap. It largely depends on feedback from customers, new sponsors and contributors.